MEMORANDUM FOR A1 - Air Force E-Publishing

AFI91-202 5 AUGUST 2011 91
procedures for all Acquisition and Sustainment programs to execute System Safety as an
integrated part of Systems Engineering.
11.2.1.2. Performs periodic reviews of Acquisition and Sustainment programs. These
include required reviews of the results of each program’s System Safety and ESOH risk
management efforts. This ensures that System Safety is overseen within the context of
other cost, schedule and performance issues.
11.2.1.3. Represents the Air Force in Acquisition and Sustainment Program System
Safety matters with other DoD components and both Governmental and non-
Governmental agencies.
11.2.1.4. Ensures program offices support system-related Class A and Class B mishap
investigations to the extent necessary to analyze hazards that contributed to the accident,
and provide recommendations for materiel risk mitigation measures, especially those that
minimize potential human errors.
11.2.2. Program Executive Officers (PEO), Designated Acquisition Officials (DAO), and
Air Logistics Center Commanders (ALC/CC) are responsible for the execution of System
Safety across all programs within their portfolios. They perform periodic program and
technical reviews of programs within their portfolios. These reviews include required reviews
of the results of each program’s System Safety and safety risk management efforts. This
ensures that System Safety is overseen alongside other cost, schedule, and performance
issues. Finally, PEOs, DAOs, or ALC/CCs serve as acceptance authorities for program safety
risks classified ―Serious‖ as defined by DoDI 5000.02.
11.2.3. Acquisition and Sustainment Program Managers:
11.2.3.1. Program offices must clearly define, document and adopt safety risk
management matrices and/or tables, using MIL-STD-882D guidance, that detail
quantified probability and event consequence severity levels, and specify approval
authorities that will be used to manage major system/function risk within their specific
programs. (For example, MIL-HDBK-516 defines major functions for air vehicles;
program managers for other enterprise items may develop similar breakouts to define
major systems/functions for their specific items).
11.2.3.2. Program offices must document and report their safety risk management
policies, along with current status of all high and serious risks as part of their Risk
Management Planning. This information is required to be documented in the
Programmatic Environment, Safety and Occupational Health Evaluation (PESHE), and
current High- and Serious-level safety risks must be presented at each Program and
Technical Review.
11.2.3.3. For risks requiring CAE or PEO acceptance, program managers must prepare a
written risk assessment describing the hazards, predicted risks (stating both consequences
and probabilities), available mitigation measures, costs or other limitations, proposed
action(s), alternatives, resulting net mishap risk and the total expected consequences for
the period of acceptance. Attachment 15 guidance is mandatory for High risk acceptance
packages and recommended for all other risk assessments.