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

the various contractors' portions of the system or construction effort. When an integration contractor does
not exist, and the managing authority procures the subsystems directly, this responsibility is given to the
managing authority. In situations where an integration contractor exists, the managing authority must
clearly and contractually define the role and responsibilities of the integration contractor for the associate
contractors. Management is responsible for assisting the integrator in these efforts to ensure that all
contractors and firms mutually understand the system safety requirements and their respective
responsibilities in order to comply with them.
Many
Associate
Contractors
?
SSPP
See
Chapter 5
No
Yes
Establish
ISSPP
Structure
Contract
Analysis
Requirement
for Systems
Interfaces
Risk
Analysis
of System
Provide
Guidance
to all
Contractors
Associate
Contractor
Conflict
Procedures
Safety
Information
Exchange
Procedures
Safety
Program
Audit
Procedures
Precise
SOW
Language
To be Included in ISSPP
Figure 6-4 ISSPP Additional Tasks
The following is a list of tasks from which the managing authority may choose the systems integration
contractor's responsibilities. Those selected should be included in the RFP and SOW.
1. Prepare ISSPP following the requirements. The ISSPP will define the role of the systems integration
contractor and the effort required from each associate contractor to help integrate system safety
requirements for the total system. In addition, the plan may address and identify:
(a) Definitions of where the control, authority, and responsibility transitions from the integrating
contractor to the subcontractors and associate contractors
FAA System Safety Handbook, Chapter 6: System Safety Guidelines for Contracting
August 2, 2000
6 -
16
(b) Analyses, risk assessment, and verification data to be developed by each associate contractor
with format and method utilized
(c) Data each associate contractor is required to submit to the integrator and scheduled delivery
keyed to program milestones
(d) Schedule and other information considered pertinent by the integrator
(e) The method of development of system-level requirements to be allocated to each associate
contractor as a part of the system specification, end-item specifications, and other interface
documents
(f) Safety-related data pertaining to off-the-shelf items
(g) Integrated safety analyses to be conducted and support required from associate contractors and
subcontractors
(h) Integrating contractor's roles in the test range or other certification processes
(i) SSP milestones
2. Initiate action through the managing authority to ensure each associate contractor is required to be
responsive to the ISSPP. Recommend to the management contractual modification where the need exists.
3. Examine the integrated system design, operations, and specifically the interfaces between the products
of each associate contractor during risk assessment. This requires using interface data that can often only
be provided by an associate contractor.
4. Summarize the mishap risk presented by the operation of the integrated system during safety
assessments.
5. Provide assistance and guidance to associate contractors regarding safety matters.
6. Resolve differences between associate contractors in areas related to safety, especially during
development of safety inputs to systems and item specifications. When the integrator cannot resolve
problems, notify the managing authority for resolution and approval.
7. Initiate action through the managing authority to ensure information required by an associate contractor
from the integrating contractor (or other associate contractors) to accomplish safety tasks is provided in an
agreed-to format. Establish associated logs to prevent such requests from "becoming lost."
8. Develop a method of exchanging safety information between contractors. If necessary, schedule and
conduct technical meetings between all associate contractors to discuss, review, and integrate the safety
effort. Provide for informal one-on-one telephone contact. Consider establishing system safety databases
at the systems integration contractor with telephone access and/or the distribution of monthly safety reports
featuring contributions from each contractor. These may be extracted from monthly progress reports, if the
progress report requirements are specified accordingly.
9. Implement an audit program to ensure that the objectives and requirements of the SSP are being
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：System Safety Handbook系統安全手冊下(4)