MEMORANDUM FOR A1 - Air Force E-Publishing

96 AFI91-202 5 AUGUST 2011
part-time individual, depending on the local system safety efforts.) If a
center/laboratory has a full-time system safety staff, the chief of this staff will be the
CSSM or laboratory SSM. All center/laboratory SSMs will document safety criteria
and hazard identification and resolution for in-house and for contractual programs.
CSSMs will identify program/project documents to be coordinated by the
center/laboratory SSM.
11.2.7.2.3. CSSMs should be members of the center Acquisition Strategy Panel and
the Senior Engineering Council.
11.2.7.2.4. CSSMs or their designated staff members will be members or advisors of
SSGs and MSTGs and CCBs. (Full-time SSMs may represent system safety in lieu of
the CSSM on program-unique CCBs, MSTGs, and SSGs.)
11.2.7.2.5. CSSMs will conduct annual meetings with all center system safety
personnel to cover refresher training, cross-tell items, and new developments in
system safety.
11.2.7.2.6. The CSSM will coordinate on the safety portion of PESHEs for programs
managed at the Center.
11.2.7.2.7. CSSMs must provide annual overviews to the MAJCOM/SE and AF/SE
on the safety risk management policies and status of all risks requiring PEO or CAE
action for all programs managed at their Center.
11.2.7.3. When assigned to Lead/Using Command, System Safety Officers, Managers,
and engineers:
11.2.7.3.1. Must be familiar with System Safety policy and guidance.
11.2.7.3.2. Support the Initial Capabilities Document (ICD), Capability Development
Document (CDD) and Capability Production Document (CPD) development effort by
IAW AFPD 90-8, Environment, Safety, and Occupational Health. Safety personnel
must work with the Environmental and Bioenvironmental Engineering staffs to
identify ESOH constraints as early as possible to prevent adverse impacts on
command mission, base locations, operational use, support concepts or
meteorological operating environments associated with systems.
11.2.7.3.3. Assist in coordinating user concurrence for safety risk acceptance
decisions.
11.2.7.3.4. Interpret hazard data provided by the program manager for the system
users.
11.2.8. Major Commands. Each MAJCOM with acquisition responsibilities must appoint a
trained System Safety manager to act as the point of contact to facilitate System Safety
matters. Major Command Safety Offices and System safety personnel:
11.2.8.1. Specify any requirements for safety features that could reduce risk, hazards or
their effects. Safety personnel must identify particular safety constraints as early as
possible to the Program Office, preferably as a part of a formal requirements document,
endorsed by the Lead Command’s proponent office for the system. These System Safety
constraints could affect the command mission, base locations, unique operational use,