PURPOSE
|
Hazard Analyses are used to systematically identify and evaluate hazards, both real and potential, for their elimination or control. The System Safety Hazard Analysis Report documents these hazard analyses.
| |
System Description
|
Summary descriptions of the physical and functional characteristics of the system and its components.
| |
Reference to more detailed system and component description, including specifications and detailed review documentation shall be supplied when such documentation is available.
| |
The capabilities, limitations and interdependence of these components shall be expressed in terms relevant to safety.
| |
The system and components shall be addressed in relation to its mission and its operational environment.
| |
System block diagrams or functional flow diagrams may be used to clarify system descriptions. Software and its role(s) shall be included in this description.
| |
Data
|
This will consist of summaries of data used to determine the safety aspects of design features.
| |
Hazard analysis results
|
This consists of a summary or a total listing of the results of hazard analysis
| |
summary of results
| |
listing of identified hazards, in narrative or matrix (sometimes called columnar or tabular) format, to include the following information:
| |
System/subsystem/unit. The particular part of the system that this analysis is concerned with. For example, if this item(s) applies to a radar system modulator, use "modulator". If there are several modulators in the system, be sure to clearly specify which one the analysis pertains to.
| |
Component(s) failure mode(s). All component failure modes which can result in a hazard. Failure modes generally answer the question of "how" it fails.
| |
Subsystem failure mode(s). The subsystem failure mode descriptions for the system hazard analysis (SHA) are similar to the component descriptions provided in the Sub-System Hazard Analysis (SSHA). However, emphasis is now placed on failure affecting interfacing subsystem operations.
| |
System component/phase. The particular phase/component that the analysis is concerned with. This could be a system, subsystem component, software ,m operating/maintenance procedure or environmental condition.
| |
System event(s) phase. The configuration or phase of the mission the system is in when the hazard is encountered: for example, during maintenance, during flight, during pre-flight, full-power applied, etc., or it could be encountered in all system events.
| |
System operation description. A description of what is normally expected to occur as the result of operating the component/subsystem or performing the operating/maintenance action.
| |
Hazard description
| |
A brief description of the hazard or hazardous material: for example, "Radiation leakage from radar set waveguide."
| |
A complete description of the potential/actual hazards inherent in the item being analyzed, or resulting from normal actions or equipment failure, or handling of hazardous materials.
| |
Hazard identification/indication. A description of operator/crew indications which include all means of identifying the hazard to operational/maintenance personnel.
| |
Effect of hazard. The detrimental effects which could be inflicted on the subsystem, system, other equipment, facilities or personnel, resulting from this hazard. Possible upstream and downstream effects shall also be described.
| |
Risk assessment. A risk assessment for each hazard (classification of severity and probability of occurrence). This is the assessment of the risk prior to taking any action to eliminate or control the hazard.
| |
Recommended action. The recommended action acquired to eliminate or control the hazard. Sufficient technical detail is required in order to permit the design engineers and the customer to adequately develop and assess design criteria resulting from the analysis. Include alternative designs and life cycle cost impact where appropriate.
| |
Effect of recommended action. The effect of the recommended action on the assigned risk assessment. This is the risk assessment after taking action to eliminate or control each hazard. If the recommended action will result in cost/schedule/performance penalties to the extent that the contractor requires government approval prior to incorporation, then these considerations shall be addressed.
| |
Remarks. Any information relating to the hazard not covered in other blocks; for example, applicable documents, previous failure data on similar systems, or administrative directions.
| |
Status. The status of actions to implement the recommended, or other, hazard controls. The status shall include not only an indication of "open" or "closed", but also reference to the drawing(s), specification(s), procedure(s), etc. That support closure of the particular hazard.
| |
Caution and warning notes., A complete list of warning, cautions and procedures required in operating and maintenance manuals and for training courses.
| |