MEMORANDUM FOR A1 - Air Force E-Publishing
MEMORANDUM FOR A1 - Air Force E-Publishing
MEMORANDUM FOR A1 - Air Force E-Publishing
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
90 AFI91-202 5 AUGUST 2011<br />
11.1.3.1.5. Current status of the risk reduction effort.<br />
11.1.3.1.6. A record of user concurrence and risk acceptance by appropriate<br />
authorities.<br />
11.1.3.2. To mitigate risks, the following order of precedence is used to satisfy System<br />
Safety requirements and resolve identified hazards according to MIL-STD-882D, DoD<br />
Standard Practice for System Safety:<br />
11.1.3.2.1. Design for minimum risk.<br />
11.1.3.2.2. Incorporate safety devices.<br />
11.1.3.2.3. Provide warning devices.<br />
11.1.3.2.4. Develop procedures and training.<br />
11.1.3.3. Every hazard that cannot be eliminated must be accepted by the appropriate<br />
level of leadership as specified in AFI 63-101, Acquisition and Sustainment Life Cycle<br />
Management.<br />
11.1.4. The acquisition and sustainment communities implement the System Safety process<br />
as an integral part of a system program office's Systems Engineering activity as defined in<br />
AFI 63-101 and AFI 63-1201, Life Cycle Systems Engineering.<br />
11.1.5. Program Managers are solely responsible for organizing their offices to execute the<br />
System Safety requirements elaborated in the DoD and <strong>Air</strong> <strong>Force</strong> policy and instructions<br />
listed in paragraph 11.1.3 In particular, Acquisition and Sustainment Program Managers must<br />
integrate system safety risk management into their program’s overall Systems Engineering<br />
effort at the Integrated Product Team (IPT) level where day-to-day engineering decisions are<br />
being made. This allows System Safety to most effectively influence system design.<br />
11.1.6. For risks requiring CAE or PEO acceptance, program managers prepare a written<br />
safety risk assessment describing the hazards, predicted risks (stating both consequences and<br />
probabilities), available mitigation measures, costs or other limitations, proposed action(s),<br />
alternatives, resulting net mishap risk and the total of expected adverse consequences for the<br />
period of acceptance. For high risks, coordination with the lead command(s), PEO and<br />
AF/SE is required before submission for acceptance. Program managers are required to<br />
reassess CAE- or PEO-accepted mishap risks at least every four years and for milestone<br />
reviews or key decisions following risk acceptance, with consideration given to actual<br />
incident and loss experiences for the period and advances in mitigation technologies and<br />
methods. Re-validated risk assessments are then coordinated and submitted for acceptance by<br />
the appropriate authority for the new predicted risk levels. Attachment 15 guidance is<br />
mandatory for the risk assessments that accompany High risk acceptance packages and<br />
recommended for all other risk assessments. Formats for risk assessment packages and tools<br />
to help identify baseline risk, actions already taken, interim risk, potential options and<br />
residual risk associated with each potential option may be found on the AFSC web-site.<br />
11.2. Responsibilities.<br />
11.2.1. The Assistant Secretary of the <strong>Air</strong> <strong>Force</strong> for Acquisition (SAF/AQ):<br />
11.2.1.1. Establishes engineering and technical policy and procedures for <strong>Air</strong> <strong>Force</strong><br />
Space and non-Space Systems Acquisition and Sustainment, including policy and