System Safety Summary

1. System safety is a basic requirement of the total system.

2. System safety must be planned

• Integrated and comprehensive safety engineering effort
• Interrelated, sequential, and continuing effort
• Plan must influence facilities, equipment, procedures, and personnel
• Applicable to all program phases
• Covers transportation and logistics support
• Covers storage, packaging, and handling
• Covers Non-Development Items (NDI).

3. Design safety precedence:

1. Design to minimum hazard
2. Use safety devices
3. Use warning devices
4. Use special procedures.

4. System Safety requirements must be consistent with other program requirements. Performance, cost, etc., requirements may have priority over safety Requirements.

5. System analyses are basic tools for systematically developing design specifications. Ultimate measure of safety is not the scope of analysis but in satisfied Requirements. Analyses are hazard not safety analyses. Analyses are performed to:

• Identify hazards and corrective actions
• Review safety considerations in tradeoffs
• Determine/evaluate safety design requirements
• Determine/evaluate operational, test, logistics requirements
• Validate qualitative/quantitative requirements have been met.

6. Level of risk assumption and criteria are an inherent part of risk management.

7. Safety Management defines functions, authority, and interrelationships. Exercises appropriate controls.

8. The degree of safety effort and achievements are directly dependent upon management emphasis by the host employer and contractors.

9. Results of safety effort depend upon clearly stated safety objectives/requirements.

10. Authorized manager responsibilities:

• Plan, organize, and implement SSP
• - Establish safety requirements for system design
• - State safety requirements in contract
• - Requirements for activities in Statement of Work (SOW)
• - Review and insure adequate and complete system safety program plan (SSPP)
• - Supply historical data
• - Review contractor system safety effort/data
• - Ensure specifications are updated with test analyses results
• - Establish and operate system safety groups.
• • Software hazard analyses are a flow down requirements process followed by an upward flow verification process

11. Four elements of an effective System Safety Program:

1. Planned approach to accomplish tasks
2. - Qualified people
3. - Authority to implement tasks through all levels of management
4. - Appropriate manning/funding

Source: FAA Office of System Safety

Certisafety Section Home Page