曝光臺(tái) 注意防騙 網(wǎng)曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費(fèi)者

review.
·  Requirement for contractor participation in special certification activities, such as for
aircraft. The FAA may anticipate that support from a communications supplier may
be necessary for the aircraft certification process.
·  Procedures for reporting hazards. The CDRL will specify the format and delivery
schedule of hazard reports. Note that permitting contractor format can save
documentation costs but, in the case where there are multiple contractors may make
integration difficult.
FAA System Safety Handbook, Chapter 6: System Safety Guidelines for Contracting
August 2, 2000
6 -
7
·  Definition of required analyses to be performed, such as the preliminary hazards list,
preliminary hazard analysis, and system hazard analysis. The contract data
requirements list specifies the format and delivery schedule of required analyses.
·  The specification of required safety testing, i.e., special test of specific components or
subsystems or monitoring specific other tests.
·  Basic risk management criteria. Specify a set of conditions that state when the risk of
the hazard is acceptable and that require the contractor to specify alternate methods
for satisfying the acceptable risk requirement. (See Chapter 3 for examples of criteria
for severity, likelihood, and risk acceptability.)
·  Special safety training or certification that might be needed for safe operation of
critical systems.
·  Reviews of engineering change proposals and deviations and waivers to make sure
design changes do not degrade the safety level of the system.
·  Techniques for doing analyses, such as the fault hazard analysis and fault tree
analysis. If included, specify on which system and subsystems the contractor should
do these analyses. Specify the candidate top events for fault tree analyses, such as
flight control or power systems. (See Chapters 8 & 9 for a discussion of analysis
techniques and analytical tools.)
6.2.5 Contract Data Requirements List
A Contract Data Requirements List (CDRL) is usually appended to the SOW. Contractual data to be
delivered falls into two general categories:
·  Financial, administrative, or management data. The procuring activity requires these
data to monitor contractor activities and to control the direction contractor activities
are taking. Contractors that require the use of the Cost Schedule Control System
(CS)2 or equivalent permit the FAA to monitor expended safety engineering effort and
progress on a monthly basis. This type of system makes it clear whether or not a
contractor is only applying safety resources to major program milestones.
·  Technical data required to define, design, produce, support, test, deploy, operate, and
maintain the delivered product.
Preparing data submissions can be expensive and represent a major portion of the contractor's safety
resources. The system safety data requirements listed on the CDRL, therefore, should represent only the
absolute minimum required to manage or support the safety review and approval process. Two choices are
to be made and reflected in the CDRL: 1) Should the contractor prepare the data in a format specified by a
data item description (DID) or in contractor format. 2) Which submittals require approval for acceptance
and payment.
The contractor does not get paid for data not covered by the CDRL/DID. He is not obligated to deliver
anything not required by a CDRL. It is advantageous to effectively utilize the DIDs when available. When
specifying DIDs they should be examined carefully, sentence by sentence, to assure applicability. It is
FAA System Safety Handbook, Chapter 6: System Safety Guidelines for Contracting
August 2, 2000
6 -
8
suggested that the data review and approval cycle be 30-45 days. Longer review cycles force the
contractor, in many cases, to revise an analysis of an obsolete configuration.
6.2.6 Bidders' Instructions
The bidder's instructions reflect how the proposal will be evaluated. There are a few instructions that,
when included in the instructions for the management and technical sections of the proposal, simplify
evaluation. The bidders' response should be keyed to specific Specification and SOW requirements and
evaluated by means of a RFP required compliance matrix (reference Figure 6-2). Proposed costs should be
supplied against the Work Breakdown Structure (WBS) permitting visibility of the SSP costs. For large
programs, the costs should be separable by major SSP tasks.
RFP PROPOSAL
Specification
3.6.3 Acceptable Hazard Level
Electrical Design Criteria
　
中國航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：System Safety Handbook系統(tǒng)安全手冊(cè)上(117)