C-17_ROCC_SOW.pdf

STATEMENT OF WORK

ROLL-ON CONFERENCE CAPSULES for the

C-17A GLOBEMASTER III AIRCRAFT

19 Apr 2018

Prepared by:

AFLCMC/WLM C-17 SYSTEM PROGRAM OFFICE

MOBILITY DIRECTORATE

4950 Loop Road West, B558

Wright Patterson AFB, OH

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

DRAFT

CONTENTS

Section Paragraph Page

1.0 Scope 3

2.0 Applicable Documents 3

3.0 Requirements 5

3.1 General Requirements 5

3.2 Technical Objectives and Goals 6

3.3 Security Requirements 6

3.4 Specific Requirements 7

3.4.1 Program Management 7

3.4.2 Systems Engineering 8

3.4.3 Configuration Management 12

3.4.4 System Safety 13

3.4.5 Production Planning 13

3.4.6 Risk Management 14

3.4.7 Testing 15

3.4.8 Reliability, Maintainability and Availability 17

3.4.9 Integrated Logistics Support Package 18

3.4.10 Training 19

3.4.11 Contractor Operations and Maintenance Support 20

3.4.12 Quality of Services 21

4.0 Deliverables 23

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 (Government). It also describes Government requirements for various integration and support activities.

1.2 The ROCC will be 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 occupants. 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 Government has certified for transportation on mobility aircraft as cargo only. The project sponsor and operating command is Air Mobility Command (AMC). The acquirer is the C-17 Systems Program Office (SPO), which is part of the Air Force Life Cycle Management Center (AFLCMC) Mobility Directorate. Supporting the SPO is the Air Transportation Test Loading Agency (ATTLA). The Lead Development Test Organization (LDTO) is the Air Force Flight Test Center, 412th Test Wing, at Edwards AFB, CA.

1.4 The primary end users of the ROCC will be US national senior leaders and their travel teams. The operating site will be at Joint Base Andrews, MD. The depot maintenance / modification site is currently planned to be co-located with the operating site. Depot level maintenance (referred to hereafter as “depot Mx”) is defined in H001.

1.5 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 referenced 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-461G 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 for Transportability Criteria

MIL-STD-31000A Technical Data Packages

MIL-STD-129R Department of Defense Standard Practice, Military Marking for Shipping and Storage

MIL-STD-464C Department of Defense Interface Standard: Electromagnetic Environmental

Effects for Systems

MIL-STD-130N Identification Marking of U.S. Military Property

Drawing 9579776, Revision N (CAGE 98752)

Product Data Specification

Drawing 9579777, Revision B (CAGE

98752)

Clarification of Detailed Test Criteria for Electrical and Avionics Items

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 DoDM 5200.01, Volume 4

DoD Information Security Program: Controlled Unclassified Information

(CUI), Enclosures 3 and 4

DoDM 5400.07 DoD Freedom of Information Act (FOIA) Program

Air Force Manual 33-

Freedom of Information Act (FOIA) Program

DoDI 5200.02 Procedures for the DoD Personnel Security Program

DoDI 8582.01, Enclosure 3.

Security of Unclassified DoD Information on non‐DoD

Information Systems

AFI 31-501/

AFGM2016-01

Personnel Security Program Management

AFI 16-1404 Air Force Information Security Program

DFARS 252.246-7008 Sources of Electronic Parts

AFPAM 63-128 Integrated Life Cycle Management

TO 00‐20‐1 Aerospace Equipment Maintenance Inspection, Documentation, Policies and Procedures

AFI 11-202, Volume 3 General Flight Rules

TO 00-35D-54 USAF Deficiency Reporting and Investigating System

Edwards AFBI 99-224 Deficiency Reporting

DTR 4500.9-R, Part VI Management and Control of Intermodal Containers and System 463-L

Equipment.

TM-86-01P Air Force Technical Manual Contract Requirements (TMCR) for C-17 Roll-On Conference Capsule

FAA Advisory

Circular No. 20-176

Service Letters / Service Bulletins

DoDI 8582.01 Security of Unclassified DoD Information on non-DoD Information

Systems

DoDI 1322.26 Distributed Learning (DL)

*Documents not readily available to bidders will be posted to a password-protected location on

FedBizOpps, as described in the Request for Proposal.

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

ASME Y14.24-2012 Types and Applications of Engineering Drawings

ASME Y14.100-2013 Engineering Drawing Practices

ASME Y14.34 Associated Lists

ASME Y14.35 Engineering Product Definition and Related Documentation Practices

ASME Y14.41 Digital Product Definition Data Practices

3.0 REQUIREMENTS

3.1 GENERAL REQUIREMENTS

3.1.1 The contractor shall provide two fully-configured ROCCs in accordance with the SRD.

Commercially available, standard components and materials shall be utilized for the ROCC, where practicable. The first article (FA) ROCC shall be used for verification testing of SRD requirements and to prove airworthiness when flown on the C-17. After airworthiness certification, the Government plans to have the contractor prepare the FA to the approved production configuration, followed by delivery of the FA to the operating command as ROCC P-1, the first production ROCC unit.

In conjunction with P-1 delivery, the contractor shall provide a logistics support package (LSP) that includes spares, technical manuals, Level III drawings and depot Mx bench equipment. The contractor will also train operating command personnel at the operating site on how to operate and maintain the ROCC, to include storage activities. The second article ROCC, termed the PROD ROCC in this document, will be designated ROCC P-2 upon delivery to AMC. Three years of Contractor Operations and Maintenance Support (CO&MS) shall also be provided to the Government after delivery of P-1. Refer to the remainder of this SOW and the CDRLs for data delivery requirements.

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, and will occur weekly through the delivery of the second ROCC, and monthly thereafter. The contractor shall support face-to-face meetings at the contractor’s facility or other designated location when required by the Government. The contractor shall provide a meet-me telephone line for Government-contractor ROCC meetings.

3.1.2.1 Shortly after contract award, the contractor shall attend a kickoff meeting hosted by Government ROCC Integrated Product Team (IPT) representatives. This meeting will be held at Wright Patterson Air Force Base (WPAFB), OH, where the Government may provide access to the following if desired by the contractor: AF material handling equipment (MHE), a tour inside the C-17 cargo compartment and an orientation tour of the legacy Silver Bullet modules and Steel Eagle if on station. The duration of the kickoff meeting will be approximately three days, not counting travel to and from WPAFB. The Systems Requirements Review (SRR) will be conducted during this meeting.

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 Government has no requirement for the contractor to have access to classified equipment or information. However, because the contractor is required to perform on Government installations, designated contractor personnel shall obtain a T1 Favorable Background Investigation (formerly known as a National Agency Check with Written Inquiries (NACI)) in accordance with DoDM 5200.02, Procedures for the DoD Personnel Security Program, or screening in accordance with AFI31-501_AFGM2016-01, Personnel Security Program Management. Successful completion of this investigation will enable either a Base Identification card or a Government Common Access Card (CAC) to be issued to contractor personnel for base entry and access to unclassified Government facilities where ROCC work will be performed. Contractor access to any Government controlled or restricted area such as a flight line shall require escort by Government personnel at all times.

3.3.2 No requirement currently exists for the contractor to have access to classified Government information systems containing sensitive program information. Contractor personnel who are issued a CAC may be permitted to have computer access to the Government’s Non-classified Internet Protocol Router Network (NIPRnet), when working on Government installations.

3.3.3 Operations Security (OPSEC): To reduce program vulnerability from successful adversary collection and exploitation of critical information, OPSEC will be applied throughout the contract performance period in accordance with DFFARS Clauses 252.204-7012 and 252.204- 7008 and the Government’s ROCC OPSEC Program Plan. OPSEC surveys to measure the effectiveness of the contractor’s OPSEC program may be conducted by the Government.

3.3.4 Controlled Unclassified Information (CUI): The Contractor will be responsible for control and distribution of CUI (For Official Use Only, Personnel Privacy and Company Proprietary Information). The Contractor shall comply with DoDM 5200.01, Volume 4, DoD Information Security Program: Controlled Unclassified Information (CUI), Enclosures 3 and 4, for identification, protection and training requirements of CUI. The contractor shall be responsible for training their personnel and accomplishment of the out-processing procedures identified in DoDM 5200.01, Volume 4, Enclosure 4. The contractor shall comply with DoDM 5400.07, DoD Freedom of Information Act (FOIA) Program, Air Force Manual 33-302, Freedom of Information Act (FOIA) Program, and AFI 16-1404, Air Force Information Security Program, requirements.

Protection of unclassified DoD information not approved for public release on non-DoD Information Systems will be protected in accordance with (IAW) DoDI 8582.01, Security of Unclassified DoD Information on non-DoD Information Systems, Enclosure 3.

3.3.5 The Contractor shall safeguard CUI stored on non-DoD information systems to prevent the loss, misuse, and unauthorized access to or modification of this information. The Contractor shall ensure that Contractor-owned and operated unclassified information technology (IT) network assets (including assets used for Contractor teleworkers) used to process sensitive Government CUI are managed and maintained IAW commercial best practices, vendor-specific, or other nationally or internationally-recognized IT configuration and management standards.

3.4 SPECIFIC REQUIREMENTS The remainder of this section contains specific work requirements needed to execute the contract.

3.4.1 Program Management

3.4.1.1 The contractor shall direct program efforts via a management system that provides Government visibility into the cost-type portions of the contract, schedule and performance of the ROCC Program.

3.4.1.2 The contractor shall provide ROCC program status to the Government via semi-annual program management reviews (PMR) until all production ROCCs are delivered. The contractor shall provide an agenda for Government-contractor program management reviews (PMRs), (CDRL A001, DI-ADMIN-81429B). PMR’s will normally be conducted telephonically, but face-to-face PMR’s will be conducted at least annually at Wright Patterson AFB. The contractor shall send minutes to the Government after conferences and PMR’s (CDRL A002, DI-ADMIN-81250B).

3.4.1.3 The contractor shall provide a contract work breakdown structure (WBS) for the ROCC Program in accordance with (IAW) MIL-STD-881C (CDRL A003, DI-MGMT-81334D).

3.4.1.4 Program Management Plan (PMP): The contractor shall submit a PMP (CDRL A004, DI- MGMT 81797/T). The PMP shall contain an integrated master plan (IMP) and an integrated master schedule (IMS) for the ROCC program.

3.4.1.4.1 The contractor shall submit forecast costs, to include subcontractor and equipment and material purchases, as specified in CDRL A010, DI-MGMT 81797/T.

3.4.1.4.2 The contractor shall upload invoices into the Government Wide Area Work Flow (WAWF) Invoice, Receipt, Accepting and Property (iRAPT) system.

3.4.1.5 The contractor shall provide a High Level Operational Concept graphic (OV-1) that shows the ROCC in its planned operational environment. The OV-1 shall feature a graphical display of ROCC interfaces with Air Force MHE, the C-17 aircraft, Steel Eagle communication and electrical cabling, servicing vehicles and equipment (CDLR A005, DI-IPSC-81432A/T).

3.4.2 Systems Engineering

3.4.2.1 The contractor shall utilize its Systems Engineering 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.

3.4.2.2 The contractor shall deliver a system and subsystem design description (SSDD), which shall be approved by the USAF prior to system build (CDRL A005, DI-IPSC-81432A/T). The SSDD shall include a scalable system interface diagram that identifies the distances between all wiring and electronic components. The diagram shall include at a minimum:

- All data, voice and power wiring entering and transitioning throughout the ROCC Senior Leader Suite (SLS) and Crew Rest/Staff Area (CR/SA) Capsules

- The type of wiring being used (Fiber, Ethernet, etc.)

- All internal and external connection points

- All electronic components

3.4.2.3 The contractor shall provide a System Engineering Management Plan (SEMP) for the ROCC program (CDRL A006, DI-SESS-81785A).

3.4.2.4 EMI/EMC: The contractor shall ensure that C-17 Electromagnetic Interference / Compatibility (EMI/EMC) testing of all electronically-powered equipment in the ROCC is accomplished. Refer to the SRD and Section 3.4.7 in this SOW for additional guidance.

3.4.2.5 The contractor shall host and conduct up to four (4) Technical Interchange Meetings (TIMs) each year. TIMs include meetings such as Systems Requirements Reviews (SRR), Preliminary Design Reviews (PDRs), Critical Design Reviews (CDRs), Engineering Data Guidance Conference, TDP In-Process Review (IPR), but do not include ROCC technical order IPRs IAW TM-86-01P/T. The contractor shall provide agendas for TIMs. Engineering data to be presented at the TIMs shall be provided to the Government before the meetings (CDRL A007, DI-ADMIN- 81429B).

3.4.2.5.1 The Contractor shall provide minutes from TIMs (CDRL A002, DI-ADMIN- 814503).

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

3.4.2.6 Level III Drawings and TDP: The contractor shall provide Level III drawings, which will include diagrams, schematics and any special tooling drawings and models IAW H001 and CDRL A008, DI-SESS-8100E/T. The contractor shall develop, produce and maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. All engineering product definition data exclusively created using Government funding as a result of this contract shall be included as part of the TDP and shall be delivered to the Government with unlimited rights.

All engineering product definition data created using Government funding shall be developed using only public commercial or military processes and specifications. TDP product definition data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall include all test requirement documentation data required to test systems, subsystems and/or components.

3.4.2.6.1 Data set classification code marking IAW Appendix F of ASME Y14.100-2013 is required. CAD model file name and extension identification is required on drawing graphic sheets. TDP data shall specify parts marking requirements for item identification IAW MIL-STD-130N, other applicable documents referenced therein, and as specified in this contract. Test Criteria for Electrical and Avionics Items shall be IAW document 9579777 Revision B (CAGE 98752) The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision N (CAGE 98752), reference attached DD Form 1423 Block 16. [DI-SESS-81000E/T] The contractor shall submit an engineering drawing tree identifying all system, subsystem and equipment drawings as part of the drawing package prior to CDR. [DI-DRPR-81961].

3.4.2.6.2 Engineering Data Guidance Conference: The contractor shall host and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 90 days after contract award. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following: [DI-ADMN-81249B, DI-ADMN-81250B]

a. Understanding of CDRL requirements, applicable DIDs, specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/TDP drawing formats/CAD programs.

e. The contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital Technical Data Package (TDP) deliverables.

Note: The Guidance Conference may be held in conjunction with other technical meetings or conferences.

3.4.2.6.3 In-Process Review of the TDP: The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review.

IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR).

Concurrent with the IPR, the contractor shall submit four (4) representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752). These shall consist of the Native, Neutral, Word Searchable PDF, HPGL, Metadata Spreadsheet, BOM, Gerber Data, and Software/memory Device Data. The contractor shall notify AFLCMC/LZPEM a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively.

The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility. [DI-ADMN-81249B, DI-ADMN- 81250B]

3.4.2.6.4 Engineering Data Updates and Revisions: The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/ developed/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media.

d. Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file. For example, when a portion of a document is revised the entire document shall be delivered.

NOTE: The hardware configurations and Level III drawings of the FA and PROD ROCCs shall exactly match. Any configuration differences between the two sets of capsules shall be approved by the Government before delivery of the ROCCs and drawings to the SPO. Separate sets of FA and PROD drawings shall be provided for any configuration difference that is approved by the Government.

3.4.2.7 The contractor shall provide a System/Sub-System Specification (SSS) that reflects the ROCC as designed (CDRL A009, DI-IPSC-81431A).

3.4.2.8 The SLS and CR/SA Capsules shall be designed to be interchangeable between the FA and PROD ROCCs. For example, if the SLS from P-1 is not available for an operational mission, the Air Force will be capable of pairing the SLS from P-2 with the CR/SA from P-1 for loading, mating, and operational use with the Steel Eagle on the C-17.

3.4.2.9 Any requested configuration changes to the ROCC made after CDR shall be requested and coordinated through the SPO.

Note: Technical and operational compatibility between the ROCC and Steel Eagle, C-17 and Air Force MHE must be maintained throughout the life of this contract.

3.4.2.10 At CDR, the contractor shall supply an Interface Control Document (ICD) that documents the detailed connectivity interfaces between the ROCC and Air Force MHE, the C-17 aircraft, Steel Eagle communication and electrical cabling, servicing vehicles and other equipment. The ROCC ICD shall be included in the ROCC TDP (CDRL A008, DI-SESS-8100E/T).

3.4.2.11 Airworthiness: The contractor shall support the formal Government airworthiness certification process for the ROCC on the C-17. Tailored MIL-HDBK-516C criteria are used to define the ROCC certification basis and identify required artifacts to support the Government airworthiness decision. The contractor shall assist the Government with the Airworthiness Certification Compliance Report by providing artifacts and verification results as requested

(CDRL A016, DI-MGMT-81453A/T).

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.

3.4.3.2 The contractor shall provide a Configuration Management Plan (CMP) for the ROCC (CDRL A011, DI-SESS-80858C). The contractor shall specify parts numbers for each SLS and CR/SA Capsule of the production ROCCs in the Supplier’s CMP. The SPO will request national stock numbers (NSN) for the production ROCCs.

3.4.3.3 After CDR is completed, the contractor shall provide Engineering Change Proposals (ECP), if requested by the Government to modify the ROCC (CDRL A012, DI-SESS-80639SD).

The contractor shall provide a Notice of Revision (NOR) in conjunction with any ECP that is requested (CDRL A013, DI-SESS-80642D/T).

3.4.3.4 The contractor shall submit Requests for Variance from the approved SSS to the Government when required (CDRL A014, DI-SESS-80640D).

3.4.3.5 The contractor shall provide Contract Change Proposals (CCP) when requested by the Government (CDRL A015, DI-ADMN-81401B).

3.4.3.6 If requested by the Government, the contractor shall conduct and support Functional Configuration Audits (FCAs) and Physical Configuration Audits (PCAs) with the Government for each new or modified part. FCAs/PCAs shall be addressed in the contractor’s CMP. The contractor shall notify the Government of upcoming suppliers/vendors FCAs/PCAs.

3.4.3.7. ROCC deficiencies as defined in T.O. 00-35D-54 shall be reported in the Joint Deficiency Reporting System (JDRS) with the assistance of the Government Deficiency Report (DR) Manager. All DRs will be resolved IAW T.O. 00-35D-54. When requested by the Government, the contractor shall investigate DRs to help determine root cause and corrective/preventative action. The contractor shall provide findings and resolution recommendations for each investigation.

3.4.3.8 The contractor shall establish a Data Accession List (DAL) for providing non-CDRL contractor data (CDRL A016, DI-MGMT-81453A/T). Documents shall be made available to the Government via the DAL upon request. If the DAL is hosted on a contractor web site, the site shall be password-controlled and selected Government personnel shall be given access. DAL-accessible documents shall include the following:

3.4.3.8.1 Contractor-internally generated data in compliance with and/or implementing the work effort described in this SOW

3.4.3.8.2 Contractor-internally generated and vendor-externally generated documents when the document(s) are referenced within a CDRL deliverable.

3.4.4 System Safety

3.4.4.1 The contractor shall establish a System Safety Program IAW MIL-STD-882E (CDRL A017, DI-SAFT-81626/T). The SSP shall emphasize formal safety analyses of ROCC system hardware and interfaces proposed under the subject contract. The Contractor’s system safety plan shall address hazard identification, mitigation and residual risk acceptance.

3.4.4.2 The contractor shall accomplish the following additional tasks IAW MIL-STD-882E:

3.4.4.2.1 (TASK 205) The contractor shall systematically identify and evaluate hazards, both real and potential, for their elimination or control. (CDRL A018, DI-SAFT-80101C)

3.4.4.2.2 (TASK 206) The contractor shall systematically identify and evaluate health hazards, evaluate proposed hazardous materials, and propose measures to eliminate or control these hazards through engineering design changes or protective measures to reduce the risk to an acceptable level (CDRL A019, DI-SAFT-81841).

3.4.4.2.3 (TASK 301) The contractor shall provide a comprehensive assessment of the safety risks being assumed prior to Government participation in testing of the FA ROCC and operation of the production ROCCs (CDRL A020, DI-SAFT-80102C).

3.4.4.2.4 (TASK 304) The contractor shall review Engineering Change Proposals, Change Notices, Deficiency Reports, Mishaps reports and Requests for Variance for system safety impacts.

3.4.4.3 Vendor safety assessment data for commercial items installed in the ROCC shall be made available to the Government upon request, via the DAL. 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 in the ROCC System Safety Hazard Analysis Report (CDRL A018, DI-SAFT-80101C).

3.4.5 Production Planning

3.4.5.1 The contractor shall maintain a manufacturing plan that ensures product quality and prevents defects (both at the prime and subcontractor levels) for the ROCCs. The manufacturing plan shall describe and illustrate the facility space planned to manufacture, assemble, and test each ROCC, including a floor plan showing the production machinery and a basic work flow. The plan shall also describe the facility planned to store each ROCC until delivery to the Government. (CDRL A021, DI-MGMT 81889/T)

3.4.5.2 The contractor shall have and maintain one of the following quality certifications: ISO 9001 or AS9100D.

3.4.5.3 The contractor shall sponsor and support up to one (1) production planning review at the Government’s request.

3.4.5.4 The contractor shall store manufactured ROCCs in a secure, temperature and humidity-controlled facility until formally accepted by the Government via DD Form 250. The facility shall be protected from adverse environmental impacts such as rain, mold, dust, rodents, etc.

3.4.5.5 The contractor shall define how the FA and PROD ROCCs will be transported from the contractor’s facility to a C-17-suitable military or commercial airfield for integration testing and/or delivery to the Government. This information shall be included in the manufacturing plan. The contractor shall transport the FA ROCC to Edwards AFB, CA for formal Government acceptance and for Air Force integration testing as described in the SRD and this SOW.

3.4.5.6 The Government requires both the FA and PROD ROCC’s to be built IAW the SRD and delivered in the same airworthy-certifiable configuration. After ROCC verification testing is completed and airworthiness certification is approved, the contractor shall ensure FA is in the required production configuration for operational service. Minor repair of the SLS and/or CR/SA resulting from integration testing may be required. Cleaning and preparation of the FA ROCC for transportation to the operating location shall be performed. After all work on the FA is completed and approved by the Government, the contractor shall deliver the FA Capsule to the operating location as ROCC P-1.

3.4.6 Risk Management

3.4.6.1 The contractor shall conduct and implement a Risk Management Program (RMP) that identifies contractor risks for executing the contract in accordance with AFPAM 63-128, Chapter

12 (CDRL A022, DI-MGMT-81809).

3.4.6.2 The contractor shall include Supply Chain Risk Management in the RMP, and shall accomplish the following supply chain risk management tasks for the ROCC:

- Source all electronic parts IAW DFARS 252.246-7008.

- At CDR, identify the source(s) of supply to the Government for all electronic parts.

This information shall be included in the manufacturing plan.

- Utilize NIAP-certified electronic equipment if equipment is available and meets design requirements

3.4.7 Testing

3.4.7.1 The ROCC shall be subject to verification requirements described in the Systems Requirements Document, Section 4. Verifications will be accomplished by one or more specified methods: analysis, inspection, demonstration or test; these verification methods are collectively referred to as “tests” in the remainder of this document. The contractor shall conduct all testing, except for testing conducted by the Government as described in the SRD and this section. The contractor shall provide or arrange for all test equipment and facilities.

Unless specified otherwise in the SRD or this SOW, tests may be combined wherever practical.

3.4.7.2 Government test facilities should be used to the maximum extent practical. The contractor shall coordinate use of Government test facilities with the LDTO. Costs for testing on Government facilities will be borne by the Government, not the contractor. The LDTO will provide work space and access to base telephones at Edwards AFB, CA, but contractor personnel must provide their own internet connectivity. The contractor is responsible for costs associated with transit of the ROCC FA and personnel travel for testing planned at a Government facility. The contractor shall provide technical support to the Government before and during these tests as requested.

3.4.7.3 The contractor shall participate in recurring Government ROCC Integrated Test Team (ITT) meetings to coordinate test activities.

3.4.7.4 The contractor shall provide a test plan for the tests required in the SRD (CDRL A023, DI-NDTI-80566A).

3.4.7.5 The contractor shall provide onsite support for the following integration testing of the ROCC at Edwards AFB, CA:

- Connecting the ROCC to the Steel Eagle and verifying all electronic power, communication and other functional interfaces.

- Interfacing and transporting the ROCC on designated Air Force MHE

- Loading and securing the ROCC into the C-17’s Aerial Delivery System

- Connecting the C-17’s intercom/PA system to the ROCC to include functional testing

- Connecting the ROCC to ground servicing vehicles to include functional testing of ROCC subsystems (lavatory water tanks, etc.)

- Ground and flight testing the ROCC with the Steel Eagle in the C-17.

3.4.7.6 The following SRD verification tests will be conducted at a CONUS C-17 base(s), which will be designated after contract award. Refer to the ROCC SRD Appendix A Test Matrix for tentative test locations. These locations and other planning data in the Test Matrix are subject to change after contract award. The contractor shall provide on-site support for the testing of these SRD requirements, as required by the Government:

ROCC Tests Required at CONUS C-17 Base(s) (Table 4)

SRD Requirement Test /Demonstration SRD Verification

3.1 Required States and Modes 4.1

3.3.1 Aircraft Interfaces 4.3.1

3.3.2 Steel Eagle Interfaces 4.3.2

3.3.3 Material Handling Equipment 4.3.3

3.3.4 Maintenance 4.3.4

3.3.5 Ground Transportation 4.3.5

3.4.1 Noise Attenuation 4.4.1

3.4.4 Emergency Egress 4.4.4

3.5.1 Electrical Power Source 4.5.1

3.5.5 Electrical Appliance Outlet

Requirements

4.5.5

3.6.3 EMI, EMC, Rapid Decompression 4.6.3

3.3.3, 3.8.1.5 Winching of ROCC into C-17 / Loading Demonstration

4.8.1.5

3.8.5 Pressurization 4.8.5.1

3.8.6 Water Tanks 4.8.6

3.8.7.1 Communication with Loadmaster 4.8.7.1

3.9.4.3 Connection Port to Aircraft PA 4.9.4.3

3.10.6.8 GFI circuit 4.10.6.8

3.4.7.7 Additional guidance for the contractor’s test effort is as follows:

3.4.7.7.1 Any EMI laboratory testing required for ROCC electrical components will be performed by the Air Force Research Laboratory (AFRL/RY), at the Government’s expense.

Approval of EMI testing results, regardless of which facility is used, rests with the Avionics Engineering Branch (AFLCMC/EZAC), IAW AFI 11-202 (V3) and MIL-STD-461G.

3.4.7.7.2 The contractor is responsible for performing all requirement verifications as described within section 4.0 of the SRD. Designated contractor verifications shall be witnessed by a Government authority and must be coordinated in advance. The contractor and SPO shall develop a coordinated test plan which will include all required verification tests, the testing schedule and location. The Contractor shall manage and perform the verification testing per the coordinated plan. Post verification test, the contractor shall provide all verification results per the Government-contractor coordinated test plan to the Government Authority for review.

Those results shall be signed/stamped off as Passed/Failed by the designated Government authority. If the test is marked as "Failed" by the authority, the contractor shall submit a written plan to the SPO within five business days, detailing the corrective actions to be implemented by the contractor to correct the issue that caused the failure. It will be the SPO Subject Matter Expert's (SME) decision if re-testing is required to obtain a "Passed" test or if the corrective action completes the verification process. The Government will make re-test decisions based on the criticality of the item being tested, and the corrective actions taken by the contractor.

NOTE: For any design deficiencies found during testing and determined by the Government to not meet SRD requirements, redesign costs shall be borne by the contractor IAW CLIN 001 for the FA.

3.4.7.7.3 The contractor shall conduct personnel emergency egress testing from the Capsules IAW MIL-HDBK-516C. Refer to the SRD for more information.

3.4.7.7.4 The contractor shall submit individual reports for sub-system or functional test results that are specified in the SRD Section 4 (CDRL A024, DI-NDTI-80809B/T). A summary report of all testing the contractor conducted shall be submitted after development testing is completed.

3.4.7.8 The Government’s LDTO will conduct the following test activities, with contractor support as required:

3.4.7.8.1 Generate test and safety plans for the ROCC integration testing described in this section. The test and safety plans will require independent review at a Government Technical Review Board (TRB) and Safety Review Board (SRB), respectively. The SRB will be chaired by an individual from the LDTO’s safety office.

3.4.7.8.2 Conduct ROCC on-aircraft EMC testing IAW MIL-STD-464C, and also ensure electronic compatibility with Steel Eagle.

3.4.7.8.3 Develop the test and safety plans, create test cards, attend and/or electronically participate in the TRB and SRB, conduct test execution and oversight and analyze any quick look data.

3.4.7.8.4 Identify any watch items/deficiencies discovered during the ROCC integration testing. Deficiency reports will be written as problems are identified during testing per the Deficiency Reporting system for Test and Evaluation, as defined in Chapter 2 of USAF T.O. 00- 35D-54, USAF Deficiency Reporting, Investigation, and Resolution, and flight test center deficiency reporting, Edwards AFBI 99-224, Deficiency Reporting.

3.4.7.8.5 Prepare an Air Force test report in accordance with the testing identified in the Government’s test plan and include any significant findings. The LDTO’s report will be submitted to the C-17 SPO within 60 days after receipt of the contractor’s final test report.

3.4.8 Reliability, Maintainability and Availability

3.4.8.1 Each production ROCC shall be designed to require no more than seven (7) hours of maintenance per month at the operating site to be fully capable for flights on C-17 operational missions. The other production ROCC may be down for periodic maintenance as required.

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

3.4.8.3 The contractor shall provide a reliability, maintainability and availability (RM&A) plan (CDRL A025, DI-SESS- 81613A). The plan shall include recommendations on how to sustain the production ROCCs during their entire service life at the capability rate specified above. The contractor shall identify the required quantities of ROCC spare parts for storage at the operating site in the plan. The RM&A plan shall assume no contractor on-site support is required while the ROCC is at the operating location, and that no contractor work will be directly performed on a production ROCC except when the ROCC is in depot Mx status.

3.4.8.3.1 The recommended frequency and criteria for inspection and refurbishment of common wear and tear items for the production ROCCs shall be described in the RM&A plan. The plan shall recommended whether refurbishment of certain ROCC equipment should be accomplished by the contractor in lieu of organizational maintenance personnel.

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 Government’s request. Government ILS reviews with the Contractor will typically be electronic meetings conducted monthly; in-person meetings may be required up to twice a year.

3.4.9.2 The contractor shall provide complete technical manuals to field level operators and maintainers (CDRL A026, TMCR TM-86-01P/T). The manuals shall be in the style and format comparable to a USAF Technical Order.

3.4.9.3 The contractor shall provide the quantity of spare parts necessary to support 24 hours / 7 days a week operations of both sets of production ROCCs for the first year after delivery.

The contractor shall maintain the same inventory level of these spares throughout the period of performance. The contractor shall identify any suitable substitute spare parts if available commercially or in Government supply systems. The contractor shall deliver spare parts to the operating site at the same time as delivery of the first production ROCC.

3.4.9.4 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 Government supply systems. The contractor shall provide a preliminary list of any required ROCC support equipment, test equipment or consumable supplies at PDR and identify the final list at CDR.

3.4.9.5 The contractor shall provide an Integrated Logistics Support (ILS) plan (CDRL A027, DI- ILSS-80095/T). The ROCC ILS plan shall detail how the logistics support package elements described above will be delivered and sustained from delivery of ROCC P-1 until three years after ROCC P-2 is delivered to the Air Force. The contractor’s ILS plan shall include description of how the contractor will provide CO&MS IAW paragraph 3.4.11.

3.4.9.6 The contractor shall package, handle, store and transport the ROCCs, ROCC materials and spare parts IAW MIL-STD-129R and DTR 4500.9-R, Part VI.

3.4.9.7 The contractor shall participate in the ROCC Integrated Logistics Support Management Team (ILSMT), a group that will provide a continuous interface between the contractor’s logistics manager and the Government. 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 training to Air Force personnel concurrent with the delivery of the first production ROCC. Training will be a combination of classroom instruction and demonstration(s) in the Capsules. The contractor shall train up to 8 Air Force maintainers, 10 operators and 15 flight attendants to include provision of training materials. Operators are defined as communication systems operators (CSO) who deploy with the senior leaders.

Maintainers are operational level technicians at the ROCC operating site. Flight attendants (FA) are safety and comfort system specialists who deploy with the senior leaders. The location of the training will be at the operating location. The period of performance for the training shall not exceed 60 calendar days.

3.4.10.2 The contractor shall provide a hands-on training course and Computer Based Training (CBT). The CBT(s) should be in Microsoft PowerPoint or Adobe Acrobat PDF format, and shall comply with the DOD Shareable Content Object Reference Model (SCORM) IAW DODI 1322.26.

The CBT shall include embedded hot links in the tables of contents for entry to selected sections, and links in text to and from diagrams in the file (CDRL A029, DI-SESS-81526C/T).

3.4.10.3 All contractor training shall instruct Government personnel on how to safely and effectively perform the following functions, using technical manuals required in SOW Paragraph 3.4.9.2.

3.4.10.3.1 Operators - connection of all voice/data/video systems between the ROCC and Steel Eagle, operation of all installed ROCC communications systems components and connections (e.g., Wi-Fi devices, monitors, network/phone/printer ports, and associated electrical connections for communications devices) for use with carry-on communication and other electronic equipment.

3.4.10.3.2 Maintainers - perform loading/unloading of the ROCC capsules (SLS and CR/SA) on MHE and the C-17 ADS rails/locks, connecting ROCC electrical and communications cables to the Steel Eagle and between ROCC capsules, powering on/off the ROCC, servicing the ROCC Environmental Control System (ECS) and lavatory, minor component removal and replacement of all ROCC systems and subsystems (e.g., ECS, lavatory, water systems, lighting, clocks, seats, divan, closets/drawers, etc.), and final preflight and post-flight checks. This list of systems, subsystems, components or other required work tasks is not all-inclusive.

3.4.10.3.3 Flight Attendants - Connection to C-17 intercom and operation of the ROCC PA system, use of safety devices/restraints, doors, clocks, lighting, lavatory, seats, divan, and egress of all ROCC occupants from the ROCC in the event of an emergency. This list of systems, subsystems, components or other required work tasks is not all-inclusive.

Note: The Government will be permitted to retain all training materials.

3.4.10.4 After the contractor provides the required Type-1 training to personnel, the USG operating command (AMC) will develop local detailed ROCC training plans. The contractor shall provide reach-back telephonic support, to answer questions or provide clarification of training materials or technical manual source data, for up to 12 instances over a 12 month period following Type-1 training. Questions from AMC regarding technical manual source data do not replace the normal communications that will occur between the Government and contractor within the ROCC Technical Order IPT (TO IPT), into which the contractor will be integrated.

3.4.10.5 The contractor shall provide a ROCC training plan that addresses the requirements above (CDRL A028, DI-ILSS-81070/T).

3.4.11 Contractor Operations and Maintenance Support

3.4.11.1 The contractor shall be prepared to provide Contractor Operations and Mx Support (CO&MS) commencing at delivery of the first production ROCC to the Government’s operating / depot Mx site. Initially, the contractor shall perform all operational level maintenance to include handling and storage of the ROCC until Government maintainers are trained. For six (6) months after delivery of P-1, further contractor assistance may be required for tasks in ROCC TOs that are not yet verified by Government personnel IAW TMCR TM-86-01P/T. All depot Mx (programmed, modifications and required repairs to the Capsules) shall only be accomplished and documented by the contractor at the designated facility IAW AFI 00-20-1.

3.4.11.2 After delivery to the Government, the contractor shall provide 24/7 reach-back telephonic support during the CO&MS period of each ROCC set.

3.4.11.3 If on-site maintenance is required in the CONUS during the CO&MS period, the contractor response time for travel to the CONUS location of the ROCC shall be within 48 hours of the request. When working at the operating site, the contractor will have access to base telephones and laptops shared with Government personnel, but no office space or dedicated work stations will be provided.

3.4.11.4 The contractor’s RM&A plan shall identify depot Mx tasks that should be performed annually or at some other recommended interval during CO&MS for each production ROCC.

The Government and contractor will jointly schedule programmed depot Mx after the required work tasks are established. If the depot Mx site is not co-located with the operating site, the Government will transport the ROCC to the depot Mx airfield.

3.4.11.5 The contractor shall provide and transport all tools and bench equipment necessary to conduct depot Mx, repairs or modifications on delivered ROCC product(s), to the designated Government maintenance / modification site for the duration of the contract. This equipment shall be in place no later than delivery of the first production ROCC to AMC, and shall be maintained by the contractor for the period of performance. The equipment shall only be used by the contractor for significant depot Mx, repair or modifications that cannot be performed by Air Force operational level maintainers due to a lack of technical data, parts and/or training.

Depot Mx bench equipment shall be identified by the contractor in the ILS plan.