曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
system design, including software, and specifically the subsystem interfaces. This analysis must include a
review of subsystem interrelationships for:
· Compliance with specified safety criteria
· Independent, dependent, and simultaneous hazardous events including failures of safety
devices and common causes that could create a hazard
· Degradation in the safety of a subsystem or the total system from normal operation of another
subsystem
· Design changes that affect subsystems
· The effects of reasonable human errors
· The potential contribution of software (including that which is developed by other
contractors) events, faults, and occurrences (such as improper timing) on safety of the system
· The determination that safety design criteria in the software specification(s) have been
satisfied
If no specific analysis techniques are directed, the contractor may obtain MA approval of technique(s) to
be used prior to performing the analysis. The SHA may be performed using similar techniques to those
used for the SSHA. When software to be used in conjunction with the system is being developed under
software standards, the contractor performing the SHA should be required to monitor, obtain, and use the
output of each phase of the formal software development process in evaluating the software contribution
to safety. (See Chapter 10, Software Safety Process) Problems identified that require the response of the
software developer should be reported to the MA in time to support the ongoing phase of the software
development process. A contractor should also be required to update the SHA when needed as a result of
any system design changes, including software, which affect system safety. In this way, the MA is kept
up to date about the safety impact of the design evolution and is in a position to direct changes.
When work is performed under contract, details to be specified in the SOW shall include, as applicable:
· Minimum risk severity and probability reporting thresholds
· Any selected hazards, hazardous areas, or other specific items to be examined or excluded
· Specification of desired analysis technique(s) and/or format
FAA System Safety Handbook, Chapter 8: Safety Analysis/Hazard Analysis Tasks
December 30, 2000
8- 17
8.4.6 Activity 6: Operating and Support Hazard Analysis
The Operating and Support Hazard Analysis (O&SHA) is performed primarily to identify and evaluate
the hazards associated with the environment, personnel, procedures, operation, support, and equipment
involved throughout the total life cycle of a system/element. The O&SHA may be performed on such
activities as testing, installation, modification, maintenance, support, transportation, ground servicing,
storage, operations, emergency escape, egress, rescue, post-accident responses, and training. Figure 8-3
shows O&SHA elements. The O&SHA may also be selectively applied to facilities acquisition projects
to make sure operation and maintenance manuals properly address safety and health requirements. Also,
see Chapter 12, Existing Facilities section.
All
Planned
Testing
Installation
Maintenance
Emergency
Actions
Storage
Training
Design
Documentation
Other
Hazard Analyses
O&SHA
Test
Plans &
Procedures
Prime
Equipment
Design
Training
Maintenance
Procedures
Test
Equipment
Design
Figure 8-3: Operating & Support Hazard Analysis (O&SHA) Elements
The O&SHA effort should start early enough to provide inputs to the design, system test, and operation.
This analysis is most effective as a continuing closed-loop iterative process, whereby proposed changes,
additions, and formulation of functional activities are evaluated for safety considerations prior to formal
acceptance. The analyst performing the O&SHA should have available:
· Engineering descriptions of the proposed system, support equipment, and facilities
· Draft procedures and preliminary operating manuals
· PHA, SSHA, and SHA reports
· Related and constraint requirements and personnel capabilities
· Human factors engineering data and reports
· Lessons learned, including a history of accidents caused by human error
FAA System Safety Handbook, Chapter 8: Safety Analysis/Hazard Analysis Tasks
December 30, 2000
8- 18
· Effects of off-the-shelf hardware and software across the interface with other system
components or subsystems.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
System Safety Handbook系统安全手册下(32)
