DRAFT_SOW_for_C-17_ROCC_(FBO,_24_Apr).pdf

STATEMENT OF WORK

ROLL-ON CONFERENCE CAPSULES for the

C-17A GLOBEMASTER III AIRCRAFT

Draft, 24 April 2017

Prepared by:

AFLCMC/WLM C-17 SYSTEM PROGRAM OFFICE

MOBILITY DIRECTORATE

4950 Loop Road West, B558 Wright Patterson AFB, OH

Authored by: Approved by:

Mr. Edward Moore Col Amanda Myers Program Manager System Program Director

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

CONTENTS

Section Paragraph Page

1.0 Scope 3

2.0 Applicable Documents 3

3.1 General Requirements 5

3.2 Technical Objectives and Goals 5

3.3 Security Requirements 5

3.3 Specific Requirements 5

3.4.1 Program Management 5

3.4.2 Systems Engineering 6

3.4.3 Configuration Management 7

3.4.4 System Safety 8

3.4.5 Production Planning 9

3.4.6 Risk Management 9

3.4.7 Testing 9

3.4.8 Reliability, Maintainability and Availability 10

3.4.9 Integrated Logistics Support Package 10

3.4.10 Training 12

3.4.11 Interim Contractor Support and Warranty 12

3.4.12 Other Contractor Services 12

4.0 Deliverables 13

Statement of Work

ROLL‐ON CONFERENCE CAPSULES for the

C‐17A GLOBEMASTER III Aircraft

1.0 SCOPE

1.1 The Statement of Work (SOW) defines contractor work required to manufacture, test and deliver the Roll‐On Conference Capsule (ROCC) and associated data to the United States Government (USG). It also describes USG requirements for various integration and support activities.

1.2 ROCC is part of a deployable roll‐on/roll off system that will be transported on the USAF C‐17A Globemaster III aircraft (hereafter referred to as the C‐17 or aircraft). When connected to the Steel Eagle Power and Communications Pallet (Steel Eagle) on the C‐17, ROCCs will provide integrated command and control capability for USG senior leaders and their travel teams. Refer to the C‐17 Systems Requirement Document (SRD), Roll‐On Conference Capsule for the C‐17A Globemaster III Aircraft, for additional system description.

1.3 The ROCC will replace legacy Silver Bullet Modules, which are modified Airstream trailers that the USG has certified for transportation on mobility aircraft as cargo only. The project sponsor is Air Mobility Command. The acquirer is C‐17 Systems Program Office (SPO), which is part of the Air Force Life Cycle Management Center (AFLCMC) Mobility Directorate. End user customers of the ROCC are senior leaders of the US Department of Defense and their travel teams. Other USG agencies such the State Department may also use the ROCC. Supporting agencies include the Air Force Research Laboratory (AFRL) and the Air Transportation Test Loading Agency (ATTLA). The planned operating site for ROCC is at Joint Base Andrews, MD, and the planned depot maintenance site is at Wright Patterson AFB, OH.

1.4 . Qualitative and quantitative performance and design requirements for the ROCC are contained in the SRD, in lieu of this SOW.

2.0 APPLICABLE DOCUMENTS

2.1 SPECIFICATIONS, STANDARDS, AND HANDBOOKS. The following specification, standards, and handbooks form a part of this SOW to the extent specified herein. Unless otherwise specified, the versions of these documents are those cited in the solicitation or contract.

NOTE: When a cancelled or revised government document is canceled by another document, the superseding document will be in effect unless otherwise specified. In the event there is no superseding document, the manufacturer may submit, at their discretion, alternatives to the cancelled government documents cited in this SOW.

Unless the alternative is specifically approved by the Government, the cancelled document shall remain fully applicable for the life of the contract.

Specifications, Standards and Handbooks (Table 1)

Specification Title

MIL-HDBK-516C Department of Defense Handbook: Airworthiness Certification

MIL-HDBK-514 Department of Defense Handbook: Operational Safety, Suitability, & Effectiveness for the Aeronautical Enterprise

MIL-STD-881C Department of Defense Interface Standard: Work Breakdown Structures (WBS) for Defense Materiel Items

MIL-STD-882E Department of Defense Military Standard: Standard Practice for System Safety

MIL-STD-461F Department of Defense Interface Standard: Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment

MIL-STD-1366 Department of Defense Interface Standard: Transportability Criteria

MIL-STD-31000C Technical Data Packages

2.2 OTHER GOVERNMENT DOCUMENTS, DRAWINGS, AND PUBLICATIONS. The following

Government documents, drawings, and publications form a part of this SOW to the extent specified herein. Unless otherwise specified, the versions of these documents are those cited in the solicitation or contract.

Other Government Documents (Table 2)

Document Title

DFARS 252.246-7008 Sources of Electronic Parts

AFPAM 63-128 Integrated Life Cycle Management

AFI 11-202 Standard- Aircrew Training

SSC-13-SB-TM Rev B Silver Bullet Technical Manual

AFLCMC/WLM C-17 Configuration Management Plan TO 1C-17A-9 C-17 Loading Instructions

2.3 NON‐GOVERNMENT PUBLICATIONS. The following documents form a part of this SOW to the extent specified herein. Unless otherwise specified, the versions of these documents are those cited in the solicitation or contract.

Non-Government Publications (Table 3)

Standard Title

SAE EIA 649-1 Configuration Management Requirements for Defense Contracts

NOTE: Documents not readily available to bidders will be posted to a Bidders Library, as described in the Request for Proposal.

3.0 REQUIREMENTS

3.1 GENERAL REQUIREMENTS

3.1.1 The contractor shall utilize commercially available, standard components and materials for the ROCC. No development of any new hardware or capability that does not already exist in industry is desired by the USG for manufacturing of the ROCC.

3.1.2 Program Meetings, Reviews and Events: The contractor shall host, conduct and support ROCC Program meetings, reviews and events, as described in this SOW. ROCC meetings will primarily be telephonic / electronic, except when face‐to‐face meetings at the contractor’s facility or other designated location are required by the USG. The contractor shall provide a meet‐me telephone line for USG‐contractor ROCC meetings.

3.1.3 The contractor shall provide an agenda to the USG no later than five business days prior to USG‐contractor meetings for major ROCC Program events, except where noted below (CDRL ___, DI‐ADMIN 81429B). The contractor shall send the USG minutes within seven business days after these meetings (CDRL ___, DI‐ADMIN 814503).

3.2 TECHNICAL OBJECTIVES AND GOALS

3.2.1 The ROCCs shall be certified to permit personnel occupancy and use of all functioning equipment during all phases of flight on the C‐17. Refer to the SRD for additional technical objectives and goals.

3.3 SECURITY REQUIREMENTS

3.3.1 The USG has no requirement for the contractor to have access to classified equipment or data.

3.4 SPECIFIC REQUIREMENTS The remainder of this section contains specific work requirements needed to execute the contract. Refer to the SRD for specific technical performance and design requirements.

3.4.1 Program Management

3.4.1.1 The contractor shall direct program efforts via a management system that provides USG visibility into the cost, schedule and performance of the ROCC Program. The contractor shall provide the USG with program status via monthly program management reviews (PMR) until all production ROCCs are delivered. More frequent status teleconferences or meetings to address specific versions may be requested by the USG as needed.

3.4.1.2 The contractor shall provide a work breakdown structure (WBS) for the ROCC Program in accordance with (IAW) MIL‐STD‐881 (CDRL ___, DI‐MGMT‐81334D).

3.4.1.3 Integrated Master Plan (IMP) The contractor shall prepare an IMP (CDRL ___, DI‐MGMT 81650 or DI‐MGMT‐81334D) that identifies all required activities, events and documents needed to deliver ROCCs to the USG and then maintain the modules during the Interim Contractor Support (ICS) period.

3.4.1.4 Integrated Master Schedule (IMS): The contractor shall prepare an IMS (CDRL ___, DI‐ MGMT 81650) which depicts significant ROCC Program milestones and events from contract award to formal USG acceptance (DD Form 250) of the ROCCs. The IMS shall include applicable USG ROCC events needed to support the overall ROCC Program.

3.4.2 Systems Engineering

3.4.2.1 The contractor shall utilize Systems Engineering (SE) processes and tools to ensure the ROCC meets overall system performance requirements when connected to Steel Eagle and when carry‐on electronic equipment is connected to ROCC provisions. The contractor shall conduct all Systems Requirements Reviews (SRR), Preliminary Design Reviews (PDRs), Critical Design Reviews (CDRs), and Specification Requirements Verification Summary Report (SRVSR) meetings IAW the IMP. The Contractor shall provide minutes from these meetings (CDRL ___, DI‐ADMIN 814503).

Note: The CDR and proposed design are successfully completed when the USG formally approves the contractor’s CDR minutes in writing and resolution of action items assigned at CDR are accepted by the USG.

3.4.2.2 The contractor shall provide a draft System Engineering Management Plan (SEMP) (CDRL ___, DI‐SESS 81785A) at PDR. Contractor format is acceptable. A final SEMP shall be provided to the USG at the CDR. The contractor shall review the SEMP every six months thereafter and provide updates to the USG as required.

3.4.2.3 EMI/EMC: The contractor shall ensure that C‐17 Electromagnetic Interference / Compatibility (EMI/EMC) certification of all electronically‐powered equipment in the ROCC is accomplished as part of the USG Certification Basis (CB) for the ROCC.

3.4.2.4 Airworthiness: The contractor shall support the formal USG airworthiness certification process for the ROCC. The contractor shall assist the USG with development of the CB document. Tailored MIL‐HDBK‐516C criteria are used to define the CB and identifies required artifacts to support the USG airworthiness decision. The contractor shall assist the USG with the Airworthiness Certification Compliance Report by providing artifacts and verification results as requested.

3.4.2.5 The contractor shall provide agendas to the USG for Technical Interchange Meetings (TIM), PDR, CDR, Test Readiness Review (TRR) no later than five business days prior to the event (CDRL ___, DI‐ADMIN 81429B). Technical data contained in briefings, drawings, manuals or other technical documents shall be provided to the USG no later than two weeks prior to the meeting (CDRL ___, DI-SESS-8100E/T).

3.4.2.6 After CDR, the contractor shall request C‐17 Program Office approval for all proposed ROCC configuration changes.

Note: Technical and operational compatibility between the ROCC and Steel Eagle must be maintained throughout the contract.

3.4.2.7 Operational, Safety, Suitability & Effectiveness (OSS&E): The contractor shall support the USG in accomplishing OSS&E per MIL‐HDBK‐514. This includes providing access to contractor OSS&E data and other information as necessary to help the USG sustain the operational mission of the ROCC.

3.4.3 Configuration Management

3.4.3.1 The contractor shall utilize a configuration management system IAW Society of Automotive Engineers (SAE) EIA 649‐1 to support the ROCC Program. The system shall include the procedures, responsibilities, and resources to perform configuration identification (CI), control, audits, status accounting, interface management, and subcontract management. The contractor’s system shall be compatible (integrate) with the C‐17 Configuration Management Plan.

3.4.3.2 The contractor shall provide a draft Configuration Management Plan (CMP) for ROCC at PDR and a final plan at CDR (CDRL ___, (SAE) EIA 649‐1).

3.4.3.3 The contractor shall conduct and support Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs) with the USG for each new or modified parts. FCAs/PCAs shall be addressed in the contractor’s CMP. The contractor shall notify the USG of upcoming suppliers/vendors FCAs/PCAs. The contractor shall prepare minutes from formal FCA/PCAs and provide them to the USG within 7 business days after each audit (CDRL ___, DI‐ADMIN 81453A).

3.4.3.4. At PDR, the contractor shall provide a draft System/Sub‐System Specification (SSS) containing all design and performance requirements for the ROCC as designed. The final SSS shall be provided at CDR for USG review and approval (CDRL ___, DI‐IPSC‐81431A).

3.4.3.5. After CDR, the contractor shall provide Engineering Change Proposals (ECP) when requested by the USG (CDRL ___, DI‐SESS‐80639SD). After CDR, the contractor shall submit Requests for Variance from the SS to the USG when required (CDRL ___, DI‐SESS‐80640D).

3.4.3.6. After contract award, the contractor shall provide Contract Change Proposals (CCP) when requested by the USG (CDRL ___, DI‐ADMN‐81401B).

3.4.3.7. After delivery of the first production ROCC, the contractor shall provide written assessments and recommendations for USG‐authored Deficiency Reports (DRs) when requested by the USG (CDRL ___, DI‐PSSS‐81535A).

3.4.3.8. The contractor shall establish a Data Accession List (DAL) for posting of USG‐requested contractor data no later than one month after completion of CDR (DI‐MGMT‐81453A). If the DAL is hosted on a contractor web site, the site shall be password‐controlled and selected USG personnel shall be given access.

3.4.4 System Safety

3.4.4.1 The contractor shall provide a System Safety Program (SSP) IAW MIL‐STD‐882E (CDRL ___, DI‐SAFT‐81626). The SSP shall emphasize formal safety analyses of ROCC system hardware and interfaces proposed under the subject contract.

3.4.4.2 The contractor shall maintain and update the following additional tasks as defined in

MIL‐STD‐882E:

TASK 205 System Hazard Analysis (CDRL ___, DI‐SAFT‐80101C)

TASK 206 Operating and Support Hazard Analysis (CDRL ___, DI‐SAFT‐81841)

TASK 301 Safety Assessment Report (CDRL ___, DI‐SAFT‐80102C)

TASK 304 Review of Engineering Change Proposals, Change Notices, Deficiency Reports, Mishaps and Requests for Variance

3.4.4.3 Safety assessment data for commercial items installed in the ROCC shall be made available to the USG upon request. Where equivalent data cannot be made available, the contractor shall assess the impact (risk) of utilizing commercial items in the military environment and provide that assessment to the USG (CDRL ___, DI‐MGMT‐81453A).

3.4.5 Production Planning

3.4.5.1 The contractor shall provide a manufacturing plan (CDRL ___, DI‐MGMT 81889) for the prototype and production ROCCs. The contractor shall sponsor and support production planning reviews at the USG’s request.

3.4.5.2 Supply Chain Risk Management

‐ The contractor shall source all electronic parts IAW DFARS 252.246‐7008

‐ At CDR, the contractor shall identify the source(s) of supply to the USG for all electronic parts. This information shall be included in the manufacturing plan.

‐ The contractor shall utilize NIAP‐certified electronic equipment if equipment that meets design requirements is available.

3.4.5.3 The contractor shall define how the prototype and production ROCCs will be transported from the contractor’s facility to a C‐17‐suitable military or commercial airfield for integration testing and delivery to the USG. This information shall be included in the manufacturing plan.

3.4.6 Risk Management

3.4.6.1 The contractor shall conduct and implement a Risk Management Program (RMP) (CDRL ___, DI‐SESS 81883) in accordance with AFPAM 63‐128 Chapter 12. Risks may be documented in contractor format, or the USG Probability/Consequence (P/CS) freeware tool may be used.

Contractor risks for executing the contract shall be provided to the USG, as part of the monthly Program Management Reviews.

3.4.6.2 The contractor shall include Supply Chain Risk Management in the RMP (refer to Production Planning in §3.4.5).

3.4.7 Testing

3.4.7.1 The contractor shall participate in USG ROCC Integrated Test Team (ITT) meetings to coordinate test activities.

3.4.7.2 The contractor shall conduct all testing with USG oversight as required. USG test facilities should be used to the maximum extent practical. The USG program manager or test manager will help the contractor coordinate use of USG test facilities if needed. For testing that directly involves USG test organizations, the contractor shall provide support to the USG as requested.

3.4.7.3 Additional guidance for contractor test effort is as follows:

‐ EMI/EMC laboratory testing should be performed by the USG Research Laboratory (AFRL/RY) and approved by USG Research Laboratory Avionics Engineering Branch (AFLCMC/EZAC), IAW AFI 11‐202 (V3) and MIL‐STD‐461F. If these USG facilities are unavailable or cost‐prohibitive, EMI/EMC testing may be performed at a non‐USG test facility and the contractor shall provide test artifacts to the USG for review and approval.

‐ The contractor shall support integration testing of the ROCC prototype connected to the Steel Eagle at a designated military or commercial airfield. Integration testing shall include physically connecting the ROCC to the Steel Eagle and verifying all functional interfaces.

Integration testing will also require loading the ROCC into a C‐17 and may require ground and flight testing the ROCC with the Steel Eagle in the aircraft.

‐ The contractor shall support personnel egress testing from the modules, which may be accomplished in conjunction with the integration testing described above.

‐ The contractor shall conduct dynamic load testing of the entire ROCC system to simulate a 9 G‐force forward load impact. The prototype ROCC may have scaled‐down components (e.g., mock‐up seats, flat screen monitor, etc.) that replicate full production equipment if not required for airworthiness certification results.

3.4.7.4 The contractor shall provide a draft test plan at CDR (CDRL ___, DI‐NDTI‐80566A). A final test plan is required two weeks prior to the TRR meeting. After the TRR, the contractor shall update the test plan monthly until all testing is completed.

3.4.7.5 The contractor shall submit a formal report to the USG within 15 days after the completion of each sub‐system and functional test listed in the test plan (CDRL ___, DI‐NDTI‐ 80566A). The Data Accession List (DAL) may be used.

3.4.7.6 Within 15 days after completion of the dynamic impact load test, the contractor shall submit a written technical assessment to the USG and a recommendation on the feasibility of repairing and upgrading the prototype ROCC to the airworthy, production configuration (CDRL

B___, DI‐NDTI‐80566A).

3.4.7.7 A final test report of all contractor testing shall be submitted within 45 days after completion of the dynamic load impact test (CDRL ___, DI‐NDTI‐80566A).

3.4.8 Reliability, Maintainability and Availability

3.4.8.1 A production ROCC shall be fully mission capable for C‐17 operational mission taskings at the operating site an average minimum of 723 hours (out of 730 hours) per month; the ROCC may undergo required maintenance during the remaining 7 hours. The other production ROCC may be down for scheduled maintenance or technical refresh upgrades as required.

3.4.8.2 The contractor shall provide a Minimum Equipment List (MEL) of components required to keep at least one set of the production ROCCs mission‐ready at the capability rate stated above (CDRL ___).

3.4.8.3 The contractor shall write maintenance tasks in the technical manuals to enable USG maintainers to keep the ROCC in an operational, mission‐ready state without contractor on‐site support.

3.4.8.4 The contractor shall provide a draft reliability, maintainability and availability (RM&A) plan at PDR and the final plan at CDR (CDRL ___, DI‐ILSS 80095). The plan shall include recommendations on how to sustain the production ROCCs during their entire service life at the capability rate specified above. The RM&A plan should assume no contractor on‐site support while the ROCC is at the operating location and contractor support when the ROCC is in depot maintenance or technical upgrade status.

3.4.9 Integrated Logistics Support Package

3.4.9.1 The contractor shall provide an integrated logistics support (ILS) package for the production ROCCs. The contractor shall sponsor and support reviews for logistics support planning at the USG’s request.

3.4.9.2 The contractor shall provide Level II drawings of the ROCC IAW MIL‐STD‐31000C. The contractor shall provide to the USG a separately priced option for Level III drawings, which will include diagrams, schematics and any special tooling drawings and models.

3.4.9.3 The contractor shall provide complete technical manuals (CDRL ___, TM‐86‐01) in the style and format comparable to a USAF Technical Order or an actual Technical Order, to cover field Level and Level 2 maintenance.

‐ The tasks, format, and level of detail in the ROCC manuals may be similar to those in SSC‐ 13‐SB‐TM Revision B, Silver Bullet Technical Manual. The manuals shall include guidance for servicing and repair of electrical cabling, environmental system, structural components and other installed equipment.

‐ An Illustrated Parts Breakdown (IPB) Manual(s) for the ROCC shall be included. The IPB shall list all parts used in the construction of the ROCC, no lower than the line replaceable unit (LRU) level.

‐ A fault isolation manual or procedures shall be provided.

‐ Vendor for supplied ROCC components shall be provided, and shall be listed in the primary ROCC maintenance manual.

‐ Procedures for connecting Steel Eagle electrical and communications cables to the ROCC shall be included.

‐ Operational procedures shall be included. A draft TO 1C‐17A‐9 procedure for loading and restraining the ROCC into the C‐17 shall be provided at the final TRR (CDRL ___, TM‐86‐01).

Existing TO 1C‐17A‐9 Section 6 procedures for loading and restraining the Senior Leader In‐ transit Conference Capsule System (SLICC) and Senior Leader In‐transit Pallet (SLIP) may be used as a template for developing the ROCC procedure.

‐ Separate Weight and Center of Gravity (CG) data for the Senior Leader Suite (SLS) and Conference Room / Staff Area (CR/SA) shall be supplied to enable USG load planning of the modules into the C‐17 aircraft.

3.4.9.4 The contractor shall provide the required quantity of spare parts at the operating site to support 24/7 operations for both sets of production ROCCs. Required quantities of parts shall be identified in the RM&A plan. The contractor shall identify any suitable substitute spare parts if available commercially or in USG supply inventories.

3.4.9.5 The contractor shall not require any support equipment (SE), test equipment or consumable supplies to operate and maintain ROCC that are not already available in industry or USG supply inventories. Equipment and consumables currently available in USG supply inventories are preferred. The contractor shall identify any required ROCC support equipment at CDR.

3.4.9.6 The contractor shall deliver a draft ILS plan (CDRL ___, DI‐ILSS 80095) at PDR and the final plan at CDR . This ILS plan shall detail how the logistics support package elements described above will be delivered and sustained from delivery of the first production ROCC until the end of the two‐year Interim Contractor Support period.

3.4.9.7 The contractor shall support the ROCC Integrated Logistics Support Management Team (ILSMT), which shall provide a continuous interface between the contractor’s logistics element manager and the USG. The contractor shall facilitate communication between all logistics disciplines and stakeholders to provide a fully integrated approach that ensures ROCC maintainability and supportability.

3.4.10 Training

3.4.10.1 The contractor shall provide a training plan (CDRL ___, DI‐ILSS 81070) for the production ROCCs at CDR.

3.4.10.2 Contractor shall provide a hands‐on training course and Computer Based Training (CBT) for servicing, operations and maintenance of the ROCCs.

3.4.10.3 The contractor shall train the initial cadre of operators and maintainers and provide them training materials. Operators are defined as communication systems operators who deploy with the senior leaders. Maintainers are defined as operational level technicians at the ROCC operating site.

3.4.11 Interim Contractor Support and Warranty

3.4.11.1 The contractor shall provide an Interim Contractor Support (ICS) commencing at delivery of each set of the production ROCCs to the USG, lasting for a period of two (2) years for each ROCC set.

3.4.11.2 After delivery to the USG, the contractor shall provide 24/7 reach‐back telephonic support for the entire ICS period of each ROCC set.

3.4.11.3 If on‐site maintenance is required during the ICS period, the contractor response time shall be within 48 hours of the request when the ROCC is located in the continental United States (CONUS). If the ROCC requiring on‐site contractor maintenance is located outside the CONUS, response time will be within 72 hours.

3.4.11.4 The contractor shall accomplish depot‐level maintenance annually at the depot maintenance site after USG acceptance of each ROCC, for the duration of this contract. The contractor shall identify depot maintenance tasks that should be performed annually or at some other proposed interval in the ROCC RM&A plan.

Note: The USG plans to schedule annual ROCC depot maintenance work concurrently with Steel Eagle depot maintenance and configuration upgrades, to ensure continued technical compatibility between both sets of modules after all work is completed. The USG will transport the ROCC to the depot maintenance site.

3.4.11.5 Each set of ROCCs shall be warranted against defects in structure and manufacturing for a minimum period of 24 months after formal USG acceptance.

3.4.12 Other Contractor Services

3.4.12.1 The Contractor shall enter into an Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the ROCC Program which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

3.4.12.2 The ACA shall include the following general information:

‐ Identify the associate contractors and their relationships.

‐ Identify the program involved and the relevant Government contracts of the associate contractors.

‐ Describe the associate contractor interfaces by general subject matter.

‐ Specify the categories of information to be exchanged or support to be provided.

‐ Include the expiration date (or event) of the ACA.

‐ Identify potential conflicts between relevant Government contracts and the ACA;

include agreements on protection of proprietary data and restrictions on employees.

3.4.12.3 A copy of such agreement (CDRL ___, DFARS 252.246) shall be provided to the USG Contracting Officer for review one month prior to execution of the document by the cooperating contractors.

3.4.12.4 The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

3.4.12.5 Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

3.4.12.6 All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended as required by the Government during the performance of this contract.

3.4.12.7 The following contractors are associate contractors with whom agreements are required:

Contractor Address Program / Contract

SelectTech Services Corporation (Cage Code 7W030)

8045 Washington Village Dr.

Centerville, OH 45458‐1847

Steel Eagle Sustainment / Contract FA8650‐15‐C‐4030

4.0 DELIVERABLES The contractor shall deliver the following documents to the USG, as described in Section 3 above. The contractor shall submit documents called out in ROCC Program CDRL‘s via the USG’s MEARS system (Multi‐User Engineering Change Proposal Automated Review System).

Contractor Deliverables (Table 4)

Document SOW Paragraph

DID CDRL Remarks

Conference Agendas 3.1.3, 3.4.2.5 DI-ADMN 81249B

Major program events/meetings.

Contractor format is acceptable

Conference Minutes 3.1.3, 3.4.3.3, 3.4.2.1

DI-ADMN

81250D

Major program events/meetings.

Contractor format is acceptable

Work Breakdown Structure (WBS) 3.4.1.2 DI-MGMT- 81334D

IAW MIL-STD-881

Integrated Master Plan (IMP) 3.4.1.3 DI-MGMT 81650 or 81334A

Integrated Master Schedule (IMS) 3.4.1.4 DI-MGMT 81650

System Engineering Management Plan 3.4.2.2 DI-SESS 81785A

Contractor format is acceptable

Configuration Management Plan 3.4.3.2 n/a (SAE) EIA 649-1 format

System/Sub-System Specification (SSS) 3.4.3.4 DI-IPSC- 81431A

Request for Variance (RFV) 3.4.3.5, 3.4.4.2 DI-SESS- 80640D

Contract Change Proposals 3.4.3.6 DI-ADMN- 81401B

Deficiency Report Recommendations 3.4.3.7 DI-PSSS- 81535A

System Safety Program Plan 3.4.4.1, 3.4.4.2 DI-SAFT- 81626

System Hazard Analysis Report 3.4.4.2 DI-SAFT- 80101C

Operating, Support, Health and Safety (OSH&S) Hazard Analysis Report

3.4.4.2 DI-SAFT-

81841

Safety Assessment Report 3.4.4.3 DI-MGMT 81453A

Manufacturing Plan 3.4.5.1 DI-MGMT 81889

Plan to include Supply Chain Risk Management

Change Notices

3.4.4.2 n/a Issued for USG-approved SS changes

Engineering Change Proposals (ECP)

3.4.3.5, 3.4.4.2 DI-SESS

80639D

When requested by the

USG

Risk Management Plan (RMP) 3.4.6.1 DI-SESS 81883

Test Plan 3.4.7.4 DI- NDTI - 80566A

Technical Assessment of Prototype

ROCC

3.4.7.6 Contractor format is

acceptable

Sub-System and Functional Test Reports 3.4.7.5 DI-NDTI-

Prototype ROCC Repair Feasibility Report

3.4.7.6 DI- NDTI -

Final Test Report 3.4.7.7 DI- NDTI -

After all airworthiness testing completed

Minimum Equipment List 3.4.8.2 May be delivered in the ILS Plan

Reliability, Maintainability and Availability (RM&A) Plan

3.4.8.4 DI-ILSS

80095

May be delivered in the ILS Plan

Training Program Development and Management Plan

3.4.10.1 DI-ILSS

81070

Product Drawings and Models 3.4.9.2 *DI-SESS- 8100E/T

*includes Associated Lists

Illustrated Parts Breakdown 3.4.9.3 Technical Manuals 3.4.8.3, 3.4.9.3, TM-86-01

System Interface Design System 3.4.5.2 DI-IPSC 81432A

Draft TO 1C-17A-9 Loading Procedure 3.4.9.3 TM-86-01 Integrated Logistics Support Plan 3.4.9.6 DI-ILSS

80095 May include RM&A plan.

Weight and CG Data for SLS and

CR/SA

3.4.9.3 Submit via

DAL

Associate Contractors Agreement 3.4.12.3 DFARS 252.246 Data Accession List 3.4.3.8, 3.4.7.5 DI-MGMT-

81453A