曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
· Acceptable systems and operational hazards analysis
· Operational procedures/technical orders are complete and verified
· All hazards are controlled effectively and controls verified as effective
· Checklists are completed and actions verified
· All hazard records in the SAR database are reviewed and the residual risk accepted by
the MA.
· Demonstrated a complete validation, verification, and if applicable certification
program, to the FAA
System Safety Program Reviews
SSP status and results to date should be on the agenda of all major program milestone reviews such as the
preliminary and critical design reviews. The criticality of some systems under development may be
important enough for the managing authority to require special safety reviews or audits. Such special
meetings are appropriate for many National Airspace System (NAS) programs.
The purpose of such meetings is to provide greater emphasis on the details of the SSP progress and
analyses than is practical at a major milestone review. Given that they are required, the schedule duration,
the pace of development, and the phase of the program should determine the frequency. One scenario for a
two-year full-scale development program might include a kick-off safety meeting shortly after contract
award and one safety review prior to Preliminary Design Review (PDR). Special meetings during the T&E
phase would be held when test results suggest a need. Since one of the primary purposes of a special safety
review is to discuss safety program tasks in greater detail than is compatible with a major program
milestone schedule, some cost savings may be achieved by requesting parallel safety sessions at a major
milestone review. This approach permits the desired detail to be discussed without accumulating the costs
of an independent meeting.
All program reviews and audits provide an opportunity to review and assign action items and to explore
other areas of concern. A mutually acceptable agenda/checklist should be negotiated in advance of the
meeting to ensure all system safety open items are covered and that all participants are prepared for
meaningful discussions.
SSP reviews to be specified in the SOW shall include, as applicable:
6.4.2 System Safety Working Groups/Work Group Support
FAA System Safety Handbook, Chapter 6: System Safety Guidelines for Contracting
August 2, 2000
6 -
29
The acquisition of expensive, complex, or critical systems, equipment, or major facilities requires
considerable interaction between the integration contractor and associate contractors simultaneously. In
these situations, the managing authority may require the formation of a System Safety Working
Group/System Safety Working Group (SSWG). The SSWG is a formally chartered group of staff,
representing organizations participating in the acquisition process. This group exists to assist the managing
authority system program manager in achieving the system safety objectives. Contractor support of an
SSWG is useful and may be necessary to ensure procured hardware or software is acceptably free from
risks that could injure personnel or cause unnecessary damage or loss of resources.
The contractor, as an active member of the SSWG, may support the managing authority by providing or
supporting presentations to the government certifying activities such as phase safety reviews or safety
review boards. The following list provides management with SSWG support options to selectively impose
on contractors:
· Present the contractor safety program status, including results of design or operations risk
· Summarize hazard analyses, including identification of problems and status of resolution
· Present results of analyses of prior mishaps or accidents, and hazardous malfunctions,
including recommendations and action taken to prevent recurrences
· Respond to action items assigned by the chairman of the SSWG
· Develop and validate system safety requirements and criteria applicable to the program
· Identify safety deficiencies of the program and providing recommendations for corrective
actions or prevention of recurrence
· Plan and coordinate support for a required certification process
· Document and distribute meeting agendas and minutes
SSWG details to be specified in the SOW should include, as applicable:
· Contractor membership requirements and role assignments (e.g., recorder, member,
alternate, or technical advisor)
· Frequency or total number SSWG meetings and probable locations
· Specific SSWG support tasks required
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
System Safety Handbook系统安全手册下(11)
