PURPOSE
|
The purpose of Task 202 is to perform and document a Preliminary Hazard Analysis (PHA) to identify safety critical areas, to provide an initial assessment of hazards, and to identify requisite hazard controls and follow-on actions
| |
TASK DESCRIPTION
|
The contractor shall perform and document a preliminary hazard analysis to obtain an initial risk assessment of a concept or system. Based on the best available data, including mishap data (if assessable) from similar systems and other lessons learned, hazards associated with the proposed design or function shall be evaluated for hazard severity, hazard probability, and operational constraint. Safety provisions and alternatives needed to eliminate hazards or reduce their associated risk to a level acceptable to the MA shall be included. The PHA shall consider the following for identification and evaluation of hazards as a minimum
| |
Hazardous components (e.g., fuels, propellants, lasers, explosives, toxic substances, hazardous construction materials, pressure systems, and other energy sources).
| |
Safety related interface considerations among various elements of the system (e.g., material compatibilities, electromagnetic interference, inadvertent activation, fire/explosive initiation and propagation, and hardware and software controls). This shall include consideration of the potential contribution by software (including software developed by other contractors/sources) to subsystem/system mishaps. Safety design criteria to control safety-critical software commands and responses (e.g., inadvertent command, failure to command, untimely command or responses, inappropriate magnitude, or MA-designated undesired events) shall be identified and appropriate action taken to incorporate them in the software (and related hardware) specifications.
| |
Environmental constraints including the operating environments (e.g., drop, shock, vibration, extreme temperatures, noise, exposure to toxic substances, health hazards, fire, electrostatic discharge, lightning, electromagnetic environmental effects, ionizing and non-ionizing radiation including laser radiation).
| |
Operating, test, maintenance, built-in-tests, diagnostics, and emergency procedures (e.g., human factors engineering, human error analysis of operator functions, tasks, and requirements; effect of factors such as equipment layout, lighting requirements, potential exposures to toxic materials, effects of noise or radiation on human performance; explosive ordnance render safe and emergency disposal procedures; life support requirements and their safety implications in manned systems, crash safety, egress, rescue, survival, and salvage). Those test unique hazards which will be a direct result of the test and evaluation of the article or vehicle.
| |
Facilities, real property installed equipment, support equipment (e.g., provisions for storage, assembly, checkout, prooftesting of hazardous systems/assemblies which may involve toxic, flammable, explosive, corrosive or cryogenic materials/wastes; radiation or noise emitters; electrical power sources) and training (e.g. training and certification pertaining to safety operations and maintenance).
| |
Safety related equipment, safeguards, and possible alternate approaches (e.g., interlocks; system redundancy; fail safe design considerations using hardware or software controls; subsystem protection; fire detection and suppression systems; personal protective equipment; heating, ventilation, and air-conditioning; and noise or radiation barriers).
| |
Malfunctions to the system, subsystems, or software. Each malfunction shall be specified, the causing and resulting sequence of events determined, the degree of hazard determined, and appropriate specification and/or design changes developed.
| |
REPORT REQUIREMENTS
|
The contractor shall prepare a Report that contains the results from the work task described by paragraph 202.2 above to include the following information:
| |
System Description
|
This will consist of summary descriptions of the physical and functional characteristics of the system and its components. Reference to more detailed system and component descriptions, 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 will consist of a summary or a total listing of the results of hazard analysis. Contents and formats may vary according to the individual requirements of the program. The following are the content and format requirements for Hazard Analysis Results:
| |
A listing of identified hazards, in narrative or matrix (sometimes called columnar or tabular) format, to include the following information
| |
System/Subsystem/Unit
|
Enter the particular part of the system that this analysis is concerned with. For example, if this item(s) applies to a radar system modulator, enter "modulator." If there are several modulators in the system, be sure to clearly specify which one the analysis pertains to.
| |
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.
| |
Hazard Description
|
A brief description of the hazard or hazardous material; for example, "Radiation leakage from radar set waveguide."
| |
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 required 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.
| |
DETAILS TO BE SPECIFIED IN THE SOW
| |
Imposition of Tasks 101 and 202.
| |
Minimum hazard probability and severity reporting thresholds.
| |
Any selected hazards, hazardous areas, or other specific items to be examined or excluded
| |