MEMORANDUM FOR A1 - Air Force E-Publishing
MEMORANDUM FOR A1 - Air Force E-Publishing
MEMORANDUM FOR A1 - Air Force E-Publishing
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
94 AFI91-202 5 AUGUST 2011<br />
11.2.5.9. Works with the Center for Systems Engineering (CSE) to maintain an<br />
―acquisition and design system safety lessons learned‖ database and makes it available to<br />
users to ensure that they apply appropriate lessons learned to new programs.<br />
11.2.5.10. Chairs System Safety Engineering Analysis (SSEA) efforts as required by<br />
each system.<br />
11.2.6. <strong>Air</strong> <strong>Force</strong> Space Command (AFSPC):<br />
11.2.6.1. Establishes and maintains the <strong>Air</strong> <strong>Force</strong>'s capability to conduct system safety<br />
programs for space facility, launch and on-orbit activities. The Space and Missile Center<br />
(SMC) is the focal point for these system safety and acquisition functions.<br />
11.2.6.2. Maintains close coordination with SMC to ensure that launch and on-orbit<br />
hazards are identified.<br />
11.2.6.3. Appoints a trained System Safety manager to act as the point of contact to<br />
facilitate system safety matters.<br />
11.2.6.4. For Space Systems, all mission assurance personnel shall be trained in System<br />
Safety and support System Safety efforts, consistent with their particular job<br />
responsibilities.<br />
11.2.7. System Safety Officers, Managers and engineers monitor operational experience,<br />
mission changes, environmental effects or system modifications to identify and correct<br />
hazards throughout the life cycle of a system or facility. When a program (e.g., an aircraft)<br />
has an embedded sub-program (e.g., an aircraft engine) which could create inter-related<br />
safety risk at the higher system level, both program managers will ensure their Systems<br />
Engineering Plans include processes to identify inter-related safety risks and to integrate risk<br />
management and mitigation efforts for High or Serious safety risks.<br />
11.2.7.1. When assigned to Program Offices, System Safety Officers, Managers and<br />
engineers:<br />
11.2.7.1.1. According to their particular job requirements, individuals in System<br />
Safety positions will complete an approved System Safety Course within 90 days of<br />
assignment (or first available course thereafter). Safety offices must document<br />
reasons for assigned individuals who have not completed training within 120 days of<br />
assignment.<br />
11.2.7.1.2. Must have introductory space safety course training when assigned to a<br />
program involved in the acquisition of a space system.<br />
11.2.7.1.3. Works within the Program Manager’s Integrated Product Team (IPT)<br />
structure to establish and maintain a System Safety program according to the<br />
principles of MIL-STD 882D.<br />
11.2.7.1.4. Participates in the development and maintenance of the Programmatic<br />
Environment, Safety, and Occupational Health Evaluation (PESHE) document.<br />
11.2.7.1.5. Integrates System Safety efforts with systems engineering and other<br />
functional areas within the program.