Air Force System Safety Handbook - System Safety Society

2.1 DoD Directives.
DODD 5000.1 states overall policies and principles for all DOD
acquisition programs and identifies key DOD acquisition
officials and forums. DOD 5000.2-R spells out the specific
acquisition procedures for major defense acquisition
programs. It is a streamlined document that spells out overall
top-level requirements.
Para 3.3.7, Environmental, Safety, and Health Considerations,
states:
The acquisition strategy shall include a programmatic
environmental, safety, and health (ESH) evaluation. The PM
shall initiate the ESH evaluation at the earliest possible time in
support of a program initiation decision (usually Milestone I)
and shall maintain an updated evaluation throughout the lifecycle
of the program. The ESH evaluation describes the PM's
strategy for meeting ESH requirements (see 4.3.7),
establishes responsibilities, and identifies how progress will be
tracked.
Para 4.3.7, Environment, Safety, and Health, states:
All programs, regardless of acquisition category, shall comply
with this section and be conducted in accordance with
applicable federal, state, interstate, and local environmental
laws and regulations, Executive Orders (EOs), treaties, and
agreements. The PM shall ensure that the system can be
tested, operated, maintained, and repaired in compliance with
environmental regulations and the requirements of this
section.
Environmental, safety, and health (ESH) analyses shall be
conducted, as described below, to integrate ESH issues into
the systems engineering process and to support development
of the Programmatic ESH Evaluation (see 3.3.7).
Para 4.3.7.3, System Safety and Health, states in part:
The PM shall identify and evaluate system safety and health
hazards, define risk levels, and establish a program that
manages the probability and severity of all hazards associated
with development, use, and disposal of the system. All safety
and health hazards shall be managed consistent with mission
requirements and shall be cost-effective. Health hazards
include conditions that create significant risks of death, injury,
or acute chronic illness, disability, and/or reduced job
performance of personnel who produce, test, operate,
maintain, or support the system.
Each management decision to accept the risks associated
with an identified hazard shall be formally documented. The
CAE shall be the final approval authority for acceptance of
high risk hazards. All participants in joint programs shall
approve acceptance of high risk hazards. Acceptance of
serious risk hazards may be approved at the PEO level.
It should be noted that the regulation does not define High or
Serious risk hazards. Accordingly, AFI 91-202, Chapter 9,
provides specific definition to these levels of hazards.
2.2 USAF Policy.
USAF Responsibilities. Historically, Air Force responsibilities
had been defined in DODI 5000.36, System Safety
Engineering and Management. DODI 5000.36 was replaced
by DODI 5000.2, Part 6, Section I, and later by DOD5000.2-R,
para 4.3.7. which did not specifically call out DoD
CHAPTER 2
SYSTEM SAFETY POLICY AND PROCESS
13
components’ responsibilities. However, the USAF system
safety duties are still valid. They are:
(1) Establish system safety programs for each system
acquisition.
(2) Summarize system safety at design and program
reviews.
(3) Establish programs to ensure application of MIL--
STD-882.
(4) Maintain historical system safety data for use by all
DoD components and contractors.
(5) Support DoD system programs with trained system
safety personnel.
(6) Maintain records of system safety lessons learned.
(7) Develop guidelines for evaluating contractors’ safety
efforts.
(8) Consider safety technologies which could reduce
risk.
(9) Integrate system safety and human factors
engineering.
(10) Consider contractor incentives for lower mishap
rates.
(11) Establish a system safety point of contact.
(12) Develop and promote improved system safety
engineering techniques.
USAF Program Requirements. These requirements remain
valid for system safety programs.
(1) Define safe operating limits.
(2) Ensure that historical safety data are considered.
(3) Provide for preliminary hazard analyses during
system concept exploration to define the scope and
level of detail of the required system safety effort.
(4) Apply MIL-STD-882 to identify hazards and associated
risk with the system and determine remedial
priorities.
(5) Establish procedures to ensure timely follow-up on
identified hazards and implement corrective action.
(6) Formally document each management decision to
accept the risks associated with an identified
hazard.
(7) Ensure that the Test and Evaluation Master Plan
addresses safety-critical issues to validate the
results of system safety analyses. When normal
testing cannot demonstrate safe system operation,
prepare and monitor special safety tests and
evaluations.
(8) Integrate system safety engineering and
management into the total system acquisition
program.
(9) Ensure that system safety requirements are consistent
with the technology of other disciplines, such
as reliability, maintainability, and human factors
engineering.
(10) Eliminate or control hazards in systems before the
production and deployment phase.
(11) Ensure, when applicable, the transfer of the system
safety program and its associated documentation
from the developing organization to the appropriate
support organization after system deployment.
(12) Require a follow-on system safety effort after initial
operational capability to ensure that:
(a) Mission or design changes made after deployment
do not introduce hazards or degrade