Safety Policy
- Safety Policy
- the safety work product
that formally documents an
endeavor’s policy regarding safety
As illustrated in the preceding figure, Safety Policy is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Document
- Subclasses:
The typical responsibilities of a Safety Policy are to:
- Communicate management’s commitment to safety program.
- Communicate management’s direction to achieving safety goals.
- Improves communication and understanding regarding the importance of (and management’s commitment to)
safety to all stakeholders.
- Lowers safety risks by lowering the frequency and severity of accidents and hazards.
- Improves collaboration between stakeholders in ensuring that safety goals are met.
- Provides a foundation on which to base a safety program.
- Provides a baseline from which evaluate compliance and progress.
The typical contents of a Safety Policy are:
- Importance of safety to the success of the endeavor and system
- Safety goals for the endeavor and system
- Commitment of senior management to safety and the safety program
- Commitment of the necessary resources to implement the safety program
- Contractual and legal requirements on the safety program
- Integration of safety with other activities
- Legal and organizational responsibilities and accountabilities of all stakeholders, especially management
- Commitment to the regular review of the policy
- Signature of executive management
The typical stakeholders of a Safety Policy are:
- Producer:
- Evaluators:
- Approvers:
- Maintainers:
- Users:
-
Safety Team
- Legal Department
- Stakeholders in the system
- People who may suffer harm as a result of system
safety risks
A Safety Policy typically can be started if the following
preconditions hold:
A Safety Policy typically has the following inputs:
- Work Products:
- Stakeholders:
- A safety policy is typically a short textual document with
little structure beyond a list of individual policy statements.
- The safety policy should be as concise as practicable to
ease communication, understanding, and remembering.
- The actual content of the safety policy will depend on
the organization, its size, and the criticality of the system
being developed, in use, or retired.
- The safety policy must be a living document that is
maintained and kept up to date as legislation and activities
change.
- The safety policy must balance the needs for safety with
other endeavor needs such as cost and productivity.
- Typical examples of safety policy statements include:
- Every system shall be considered to be potentially
unsafe (i.e., have unacceptable safety risks) until a
safety case has shown the system to be safe.
- The development or upgrade of every system shall
include a preliminary safety analysis (e.g., including
asset analysis, safety incident analysis, hazard analysis,
safety risk analysis) to determine if the system has safety
risks.
- A safety program shall be established for all projects
having safety ramifications.
- The overall approach to safety engineering will be
agreed to between the customer and developer organizations
prior to the commencement of development.
- The development organization shall be required to
undertake a safety analysis including asset analysis,
safety incident analysis, hazard analysis, and safety risk
analysis.
- The development organization shall be required to
reduce, eliminate, or mitigate the effects of identified
hazards in accordance with safety requirements and risk
assessment criteria.
- No system shall be delivered by the development
organization, accepted by the customer organization, and
placed into operation if it has any safety risks, the
safety integrity level of which is unacceptable.
- The development organization shall be required to
demonstrate that the final system satisfies all previously
identified safety requirements.
- Prior to acceptance of the system by the customer
organization, the development organization shall provide a
documented safety case presenting safety goals, arguments
that the goals have been achieved, and compelling evidence
to back up the arguments.
- The safety case shall be included as part of the
deliverable documentation and maintained as the system is
modified and new hazards are identified.
- It is our policy to take all reasonably practicable
steps to ensure safety.
- No job or function is so important and no request so
urgent that time cannot be taken to perform that function
safely and in compliance with appropriate safety
requirements.
- All activities will be conducted in a safe manner that
accidental harm will not occur to valuable assets.
- Safety is everyone’s responsibility and cannot be
delegated.
- Personnel are responsible for demonstrating leadership
in developing proper attitudes toward safety, and making
the necessary efforts and providing necessary resources to
conduct activities safety and ensure compliance with
appropriate safety requirements.
- All personnel must set personal examples of safety for
their students and other employees.
- Personnel must establish, follow and enforce safe
practices and procedures.
- Every individual must know the potential hazards
associated with their duties and follow all applicable
safety practices and procedures.
- All personnel are expected to carry out their
assignments in a way that prevents injury to themselves and
others.
- It is the incumbant of all personnel and visitors to
understand their own individual responsibility to be aware
of, and to comply with, all health and safety requirements
relevant to their activities.
The safety policy is typically constrained by the following
conventions:
-
Content and Format Standard
-
MS Word Template
-
XML DTD
-
Evaluation Checklist
