曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

6.4.3 Hazard Tracking and Risk Resolution
Each program with or without an active system safety effort can identify system hazards that require
control to an acceptable risk level. A system is required to document and track hazards and resolution
progress to ensure that each is controlled to an acceptable risk level.
Hazard tracking need not be a complex procedure. Any hazard tracking tool that tracks the information
contained in Section 6.2 and complies with the SSMP and SSPP is acceptable for hazard tracking in the
FAA at the program level. The managing authority, the system integrator, or each contractor may maintain
the Safety Action Record (SAR) database. Each risk that meets or exceeds the threshold specified by the
FAA System Safety Handbook, Chapter 6: System Safety Guidelines for Contracting
August 2, 2000
6 -
30
managing authority should be entered into the SAR database when first identified. Each action taken to
eliminate the risk or reduce the associated risk is documented. Management will detail the procedure for
closing out the hazard or acceptance of any residual risk. The SAR may be documented and delivered as
part of the system safety progress summary using, Safety Engineering Report, or it can be included as part
of an overall program engineering/management report.
Management has considerable flexibility in choosing a closed loop system to closing out a risk. See Figure
6-7. The key is the maintenance and accessibility of a SAR. The contractor can be required to establish the
SAR and include within it a description of the specific corrective action taken to downgrade a medium and
high risk hazards. The corrective action details and log updates can be included in monthly reports,
subsequent data submissions, and at major program milestones.
Hazard ID
SSWG Risk
Assessment
High/
or medium
Develop
SAR
IPT action
design
controls
Further
controls?
SSWG Risk
SEC Review Assessment
Risk Assessment
Review
Risk Accepted?
Archived
Data
Y
N
N
Y
Y N
Figure 6-7: Hazard Resolution System(s)
Management can review and approve/disapprove the corrective action or its impact by mail, at major
program milestones, SSWG meetings, safety reviews board meetings, or any other engineering control
process found to be effective. Although the method selected is flexible, a "paper trail" reflecting the
identification of medium and high risk, a summary of the corrective action alternatives considered,
conclusions, and the names of the review team is desirable.
Details to be specified in the SOW shall include, as applicable, the following:
·  Hazard threshold for inclusion in the hazard log
·  Complete set of data required on the hazard log, including format
FAA System Safety Handbook, Chapter 6: System Safety Guidelines for Contracting
August 2, 2000
6 -
31
·  Procedures to record hazards into the log and the level of detail of the log entry
·  Procedure by which the contractor shall obtain close out or risk acceptance by the MA
for each hazard
6.4.4 System Safety Progress Report
Comprehensive and timely communication between management, the system integrator (when applicable),
and each contractor is critical to an effective SSP. The system safety progress report provides a periodic
written report of the status of system safety engineering and management activities. This status report may
be submitted monthly or quarterly. It can be formatted and delivered as a Safety Engineering Report, or it
can be included as part of an overall program engineering/management report.
The contractor may prepare a periodic system safety progress report summarizing general progress made
relative to the SSP during the specified reporting period and projected work for the next reporting period.
The report should contain the following information.
·  A brief summary of activities, progress, and status of the safety effort in relation to the
scheduled program milestones. It should include progress toward completion of safety
data prepared or in work.
·  Newly recognized significant hazards and significant changes in the degree of control of
the remaining known hazards.
·  Status of all recommended corrective actions not yet implemented.
·  Significant cost and schedules changes that impact the safety program.
·  Discussion of contractor documentation reviewed by SSWG during the reporting period.
Indicate whether the documents were acceptable for safety content and whether or not
inputs to improve the safety posture were made.
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：System Safety Handbook系統安全手冊下(12)