RMCD ROAR PWS 6 Dec 23_Final.docx

PERFORMANCE WORK STATEMENT FOR

C-5M SUPER GALAXY

REPLACEMENT MULTI-FUNCTIONAL CONTROL DISPLAY (RMCD) PROGRAM

Air Force Life Cycle Management Center/ C-5M Super Galaxy Division System Program Office (SPO) (AFLCMC/WLS) 06 December 2023

Controlled by: AFLCMC Controlled by: C-5M Super Galaxy Division CUI Category: CUI Basic Distribution/Dissemination Controls: FEDCON POC: Jennifer Strickland, jennifer.strickland.1@us.af.mil

CUI

CUI

TABLE OF CONTENTS

4.10 4.11

HUMAN FACTORS ENGINEERING (HFE)

RMCD TEST & EVALUATION

GENERAL INFORMATION 45

1. DESCRIPTION OF SERVICES

This PWS encompasses a range of Contractor-executed tasks for the Replacement of Multi- Functional Controls and Displays (RMCD) program. This modification shall span the development, integration, testing, kitting, pre-production, Prototype Installation (per a Time Compliance Technical Order (TCTO)) and development testing of an integrated RMCD design into the latest C-5M configuration. Two aircraft will be modified from a Block 4.1 configuration to an RMCD configuration.

1.1. Objectives: This Performance Work Statement (PWS) describes the services required for the Replacement of Multi- Functional Controls and Displays (RMCD) program. These services include embedded development, integration, kitting, pre-production, installation, and verification requirements. The C-5M configuration shall comprise the following:

· Hardware: C-5M aircraft retrofitted with "CNS/ATM Production configuration which is made up of the following: Core Mission Computer/Weather Radar; Communications, and Navigation, Surveillance/Air Traffic Management modifications for the EMD program.

· Software: Operational Flight Program (OFP) 4.2.0 software configuration. Throughout this PWS, the terms “product baseline,” “functional baseline,” and “trial kit installation” are applied. The following definitions shall apply to all Contractor actions taken in support of this PWS.

· Product Baseline: Documentation describing all of the physical characteristics of the C-5M RMCD design and configuration components; the physical characteristics designated for pre-production acceptance testing; and tests necessary for installation, operation, support, training, and disposal of the configuration item. The product baseline includes “build-to” specifications for hardware (e.g., product, process, material specifications, engineering drawings, and other related data) and software.

· Functional Baseline: Definition of the required system functionality describing functional and interface characteristics of the overall system, and the verification required to demonstrate the achievement of those specified functional characteristics. For the C-5M RMCD program, the functional baseline shall derive from the Government’s System Requirements Document (SRD) and be translated into the Contractor’s update to System Specification and an RMCD Technical Data Package (TDP).

· Prototype Installation: The initial C-5M installations confirming platform integration per a TDP and a detailed TCTO.

1.2. Benefit to the United States Air Force (USAF):

This acquisition will benefit the United States Air Force (USAF) by a permanent sustainment modification to the C-5M platform under the authority of an approved Air Mobility Command (AMC) 1067 requirement document 16-020 (MFDU Replacement), 18-067 (Power Supply for Mission Planning and Execution), and 14-052 (C-5M MFDU Ethernet Load Capability). This effort will resolve known diminishing manufacturing sources and obsolescence issues of the current MFDU on the C-5M aircraft. Replacing the current MFDU will avoid a projected aircraft Mission Impaired Capability Awaiting Parts (MICAP) grounding issues in FY 2029), extend the C-5M fleet life through 2040 (all 52 aircraft), and improve overall aircraft availability metrics.

1.3. Background

In 2016, a study identified projected obsolescence issues starting in 2021 for the C-5M Multifunction Display Units (MFDU). As the primary flight references, these Line Replaceable Units (LRU) control several functions of the aircraft and display critical flight information required to maintain safety of flight while meeting global mission requirements.

To mitigate this obsolescence, the RMCD program shall integrate a Government-Furnished Property (GFP) Visual Display Terminal (VDT) and General Data Processor (GDP) with a contractor update to the GFP Operational Flight Program (OFP) that provides a fully functional modification to the C-5M product baseline. This modification shall involve the replacement of six Multi-Functional Display Units (MFDUs) that provide the pilot and copilot situation awareness during missions and a seventh unit at the flight engineer station. This modification shall support changes to the MFDU provisions at the Navigator Station to afford dual formats at the Flight Engineer station. Also included in this modification is the introduction of COTS power converters to facilitate power outlets to be installed on the flight station at agreed upon locations. The supported information includes, but is not limited to, navigation, datalink, Built-In-Test, Caution and Warning Annunciations, engine status, and video from the weather radar and Enhanced Ground Proximity Warning System (EGPWS). The Engineering, Manufacturing and Development phase (i.e., from point of award to completion of Developmental Test and Evaluation (DT&E) and test report delivery) shall be approximately 36 months.

2. SERVICES SUMMARY

Pre-Production Kit Fabrication, Procurement, Assembly, and Kitting

Contractor shall support a physical inspection and crosscheck (against the BOM) of the kit, and the delivery schedule for the Prototype Installation.

Contractor shall ensure there are no deviations between the BOM and the physical inspection of the kit.

Contractor shall ensure any required corrective actions are completed and responses provided to the Government PCO by email, NLT ten (10) business days after audit completion.

Receipt of CDRL Deliverable

3. GOVERNMENT PROPERTY

3.1. Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2. Government Property to be Provided: The Government will provide Government Furnished Property (GFP). The GFP list will be developed/produced by the Government with the aid of the contractor 30 days after contract award and made part of the contract via modification. The Contractor shall manage all Government Property in accordance with FAR 52.245-1, FAR Part 45 and DFARS Part 245 as supplemented. The Contractor shall provide necessary Product Quality Deficiency Report (PQDR) information for deficient Government Furnished Equipment (GFE) / Government Furnished Property (GFP) in accordance with TO 00-35D-54. CDRL Reference in paragraph 4.2, DI-QCIC- 80736, Quality Deficiency Report; DI-QCIC- 80736, Quality Deficiency Report; and DI-MGMT-80441D, Government Property (GP) Inventory Report – Reporting of Government Furnished Property.

3.3. Base Support: The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment and office supplies.

3.4. Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7002. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.5. Loss of Government Property:

3.5.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.5.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil.

3.6 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4. TECHNICAL REQUIREMENTS

4.1 PERIOD AND PLACE OF PERFORMANCE

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend 31 July 2024 through 30 July 2027.

4.1.2 Place of Performance: Place of performance will be at contractors’ facility.

4.2 CONTRACT DATE REQUIREMENTS LIST(s) (CDRL)

Document Identifier Base Year Ordering Period Ordering Period

(FMECA)

4.14.9.b.

VALIDATION AND VERIFICATION REPORT

4.15.2.10

SERD - Standard/Modified Hand Tools List 4.3.1.7, 4.6.1, 4.16.2, 4.16.3

Provisioning Tech Documentation 4.15.1.a., 4.15.1.b.

Recommended Spares List-OT&E Spares 4.15.2.2

Initial Sparing Support 4.15.2.3

Reporting of Government Furnished Property 3.2

Depot Level Source of Repair Capability Requirements 4.14.12

Facilities Summaries 4.16.5

and Analysis Report (E3IAR) 4.11.10.1

4.2.1 Quality of CDRL Deliverable There shall be no more than one rejection of any individual deliverable. There shall be no more than one total rejection(s) of an individual deliverable per quarter. The Government will reject a deliverable if one or more major technical errors or three or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc.

4.2.2 Receipt of CDRL The Contractor shall implement data management procedures for the preparation, quality control, administration, and delivery of data required by CDRLs, and shall maintain data status and delivery schedules for all CDRL items. The Contractor shall electronically deliver all CDRL data using the Multi-user ECP-Automated Review System (MEARS). The Contractor shall ensure an adequate number of Contractor personnel obtain Public Key Infrastructure certification from an accepted United States Government (USG) source. There shall be no more than one late submission(s) of deliverables per quarter. Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 RMCD Design and Configuration

4.3 RMCD Design and Integration into C-5M Configuration

4.3.1. Design and Integration: The Contractor shall design, integrate, and verify the RMCD product baseline, per the specifications of the Government’s Weapon System and Air Vehicle System Specifications and the contract Integrated Master Schedule (IMS). The Contractor’s design and integration shall conform to C-5M configuration defined in Section 1 of the PWS. The Contractor shall reduce integration and implementation schedules as much as possible.

4.3.1.1. The Contractor shall integrate GFP hardware and contractor-modified GFP software into a material solution that functions within the current C-5M avionics architecture and meets all performance parameters. The integrated design and installation shall not interfere with the location or functionality of any pre-existing aircraft system or subsystems per the baseline definition in Section 1. Should the proposed installation cause any interference or interoperability issues, the Contractor shall immediately notify the Government.

4.3.1.2. The Contractor shall develop a derivative work of the MFDU Application Client software (MAC) for use on the Graphics & Data Processing Unit (GDP) in order to minimize the impacts associated with the Primary Flight Reference (PFR) endorsement. Any Government involvement in the development or qualification of the MAC derivative work shall be in accordance with SLA-13-C5-001 and the roles of each party shall be identified in the partnership and implementation agreement that is part of this contract. CDRL Reference in paragraph 4.2, DI-AVCS-80700A/T, Computer Software Product End Items.

4.3.1.2.1. The Contractor shall develop source code changes of the Display Services (DS) and Communication, Navigation, Surveillance Integration (CNSI) software for use on the VIA/AIU, as required, in order to minimize the impacts associated with the Primary Flight Reference (PFR) endorsement. Any Government involvement in the development or qualification of the DS and CNSI computer software work shall be in accordance with SLA-13-C5-001 and the roles of each party shall be identified in the partnership and implementation agreement that is part of this contract. CDRL Reference in paragraph 4.2, DI-AVCS- 80700A/T, Computer Software Product End Items.

4.3.1.3. The Contractor shall ensure and verify that all aircraft software is field- loadable. Software shall be loadable using the on-aircraft Embedded Diagnostic System (EDS) and existing support equipment. This shall include software and test requirement documentation data required to test systems, subsystems and/or components.

4.3.1.4. The Contractor shall ensure and verify (consistent with applicable DoD and Air Force regulations and directives) the RMCD integration meets applicable standards to support the Government’s attainment of Military Flight Releases and/or updates to the Military Type Certification, and Primary Flight Reference (PFR) approvals. All airworthiness and PFR artifacts shall comply with MIL- HDBK-516C, AFPD 62-6, and AFI 62-601. The timing of deliverables shall be documented within the program IMS and shall ensure on-time support for the installation and flight test schedules.

4.3.1.5. The Contractor shall ensure the design, integration, and installation of the RMCD product baseline complies with Department of Defense Instruction (DoDI) 8500.01, DoDI 8510.01, and Committee on National Security Systems, Instruction (CNSSI) No. 1253.

4.3.1.5.1. In support of the RMCD design, the Contractor shall conduct and maintain a Supply Chain Risk Management analysis IAW National Institute of Standards and Technology Interagency Report 7622, and NIST Special Publication 800-161.

4.3.1.5.2. The timing of cybersecurity-related deliverables shall be documented within the program IMS and shall ensure on-time delivery to support the Government’s attainment of Interim Authority to Test and Authority to Operate approvals.

4.3.1.6. The Contractor shall ensure and verify (consistent with applicable DoD and Air Force regulations and directives) that the C-5M RMCD integration does not introduce any safety issues or hazardous materials into the aircraft configuration. All safety artifacts shall comply with MIL- STD-882E and the provisions of Section 5.10. CDRL Reference in paragraph 4.2, DI-SAFT-80101C/T, System Safety Hazard Analysis Report (SSHAR).

4.3.1.7. The Contractor shall ensure the RMCD product baseline limits the need for Peculiar Support Equipment (PSE) to the maximum extent. If required, the Contractor shall update the Support Equipment Recommendation Data deliverable (SERD) for all PSE that may be identified or changed during kitting developmental test. The Contractor shall identify and incorporate all PSE, Common Support Equipment (CSE), bench stock, and/or special test equipment required to complete an RMCD kit installation into the installation TCTO. CDRL Reference in paragraph 4.2, DI-SESS- 81759A/T, Logistics Product Data Summaries - SERD-Standard/Modified Hand Tools List.

4.3.2. DMSMS Though Modification: Throughout the design, integration, and verification phases of the RMCD modification, the Contractor shall be responsible for monitoring the Diminishing Manufacturing Sources and Material Shortages (DMSMS) and technology refresh status of all RMCD modification components with the exception of the GFE Visual Display Terminal (VDT) and Graphics & Data Processor (GDP). The Contractor shall flow-down these requirements to all subcontractors/vendors and ensure they are provided the required data to fulfill the Diminishing Manufacturing Sources (DMS) management requirements. If a component should go DMS, the Contractor shall adapt the RMCD product baseline to incorporate a form, fit, and function replacement. The Contractor shall ensure that such incorporation or adaptation of new Group B components does not cause any negative impact to the RMCD functional baseline.

4.3.2.1. The Contractor shall integrate Unitron (PN PS-94944-16) to facilitate the introduction of single phase 115VAC/60Hz power to the flight deck via frequency converters making use of existing 3 phase 115VAC/400Hz aircraft power sources. The number and location of the standard 3 prong power outlets to be introduced shall be agreed upon at PDR. The Contractor shall perform an electrical load analysis and evaluation of the electrical and environmental effects to support wiring design and installation. The Contractor shall determine Fault Isolation and Fault Detection impacts to support the aircraft wiring system. CDRL Reference in paragraph 4.2, DI-MISC-80508B/T, Technical Report-Study/Services – Electrical Load Analysis, Power Load Analysis and Thermal Load Analysis; DI-SESS-80198B/T, Internal Loads and Static Strength Analysis Report.

4.3.3 RMCD System Integration: The Contractor shall address design, development, interface and integration of hardware and software onto the C-5M aircraft. The major elements of this effort shall include all interface, modification and any required changes for structural mounting, electrical power and distribution, environmental control and human factors for the modified or added components, both separately and as a system. Impacts to the aircraft electrical power and distribution system shall be analyzed in accordance with MIL-E-7016F and defined with the resultant design, development and integration of electrical system component interface equipment, component modifications or additional equipment. The Contractor shall host two Crew Station Working Groups. The Contractor shall update the Human Engineering Design Approach Document – Operator (HEDAD-O) and Human Engineering Design Approach Document – Maintainer (HEDAD-M).The Contractor shall track the weigh and center of gravity changes and update the mass properties of the modified C-5M. Impacts to the aircraft environmental control system and environment shall be analyzed and defined including design, development and integration of environmental control system interface equipment, component modifications or additional components. The Contractor shall provide design information for the mounting, routing, and installation of the VDT+ monitors and Graphics & Data Processors (GDPs). Analysis of the weight and balance changes shall be included in the analysis documentation. Structural and mounting provisions shall be designed and developed along with the human factor’s considerations for component accessibility and human interface in adherence with PWS paragraph 4.4.1. The Contractor is permitted to combine separate test plans, analysis, or results into single documents as appropriate for submittal to the Government for review and approval. CDRL Reference in paragraph 4.2, DI-MISC-80508B/T, Technical Report-Study/Services – Electrical Load Analysis, Power Load Analysis and Thermal Load Analysis and DI-SESS-80198B/T, Internal Loads and Static Strength Analysis Report.

4.4 RMCD Upgrade Computer Resources

4.4.1 Software Loading: The Contractor shall ensure that all aircraft equipment software provided for the C-5M RMCD Upgrade program is field-loadable. Field- loadable software shall be loadable using the Embedded Diagnostics System (EDS) or similar existing aircraft support equipment. Loader software newly developed for loading the RMCD Operational Flight Programs (OFPs) shall be delivered with the documentation and source code. CDRL Reference in paragraph 4.2, DI-IPSC-81488/T, Computer Software Product; DI-SESS-81248B/T, Interface Control Document (ICD); DI-IPSC-81438A/T, Software Test Plan (STP); and DI-QCIC-81536A/T, Test Information Sheet (TIS) – VTIS, ITIS and Regression.

4.4.2 RMCD Integrated Diagnostics: The Contractor shall analyze and test the integrated diagnostics features of the RMCD modification at the aircraft level to ensure the Air Vehicle fault detection, fault isolation and false alarm requirements are not degraded and meet C-5M requirements. The Government reserves the right to witness any and all tests/verification methods associated with these requirements on a noninterference basis. The Contractor shall also establish a regression test baseline to demonstrate that the new software and associated diagnostics do not adversely impact the existing functionality of the C-5M. CDRL Reference in paragraph 4.2, DI-SESS- 81248B/T, Interface Control Document (ICD); DI-IPSC-81438A/T, Software Test Plan (STP) and DI-QCIC-81536A/T, Test Information Sheet (TIS) – VTIS, ITIS and Regression.

4.4.3 RMCD Embedded Diagnostic Systems (EDS): The contractor shall provide the government with requirements for EDS, including but not limited to, fault insertion information, fault detection information, fault identification and a schedule of software and documentation deliveries. The Contractor shall plan and conduct technical activities and regression testing, to ensure the RMCD does not degrade the functionality and performance capability of EDS. CDRL Reference in paragraph 4.2, DI-SESS-81248B/T, Interface Control Document (ICD); DI-IPSC-81438A/T, Software Test Plan (STP); and DI-QCIC- 81536A/T, Test Information Sheet (TIS) – VTIS, ITIS and Regression.

4.4.4 Software Documentation: The Contractor shall deliver aircraft equipment software with certification pedigree and all supporting documentation which includes software documentation and test plans/reports to show the software has been tested to the applicable DAL level for each CSCI. This includes, at a minimum, System/Subsystem Specification, Software Test Reports, Software Design Description, Software Product Specification, Software Requirements Specification, Interface Requirements Specification, Software Version Description, and Test/Inspection Reports. This shall include software and test requirement documentation data required to test systems, subsystems and/or components. CDRL Reference in paragraph 4.2, DI-IPSC-81442A, Software Version Description (SVD); DI-NDTI-80809B, Test/Inspection Report; DI-IPSC- 81431A/T, System/Subsystem Specifications; DI-IPSC-81434A, Interface Requirements Specification; DI-IPSC-81443A, Software Requirements Specification; DI-IPSC-81441A, Software Product Specification; DI-IPSC-81435B, Software Design Description; DI-IPSC-81431A, Software Test Report (STR); DI-IPSC-81431A/T, System/Subsystem Specification (SSS); and DI-IPSC-81431A/T, System/subsystem Specification (SSS).

4.5 RMCD Delta System Requirements Review (SRR) Planning/Execution for Flight Engineer Display Format

4.5.1 Delta SRR: The Contractor shall coordinate the scheduling of a Delta SRR and SRAR IAW the program IMS. The Contractor shall provide the C-5M SPO a minimum of twenty (20) business days’ notice of the meeting date. The Contractor shall provide a meeting agenda and briefing materials at least ten (10) business days in advance of the meeting. The Contractor shall host the SRR at the Contractor’s facility. CDRL Reference in paragraph 4.2, DI-MGMT-81605, Briefing Material; DI-ADMN-81249B/T, Conference Agenda - Meeting Agenda; DI-ADMN-81250B/T, Conference Minutes

4.5.2 System/Subsystem Specifications: The Contractor shall present the systems engineering methodology used to translate the system requirements (i.e., from the SRD into an update to the C-5M System Specification) and the associated specifications down to configuration items, logistics, training, manufacturing, and test elements at the Delta SRR. This presentation shall confirm the traceability of all requirements and the adherence of the specification across all sub-tier suppliers and vendors. CDRL Reference in paragraph 4.2, DI-IPSC-81431A, System/Subsystem Specification (SSS).

4.5.3 Delta SRR Minutes: The Contractor shall submit minutes summarizing the meeting findings and Contractor mitigations, as applicable following the delta SRR. The Contractor shall also complete all corrective actions and address all questions and deliver an updated briefing package to the Government Procuring Contracting Officer (PCO) via E-Mail, no later than (NLT) ten (10) business days after the completion of the delta SRR. CDRL Reference in paragraph 4.2, DI-MGMT-82133, Requirements Traceability Verification Matrix (RTVM); DI-MGMT-81605, Briefing Material; DI-ADMN-81249B/T, Conference Agenda - Meeting Agenda; DI-ADMN-81250B/T, Conference Minutes

4.6. RMCD CDR Planning/Execution

4.6.1 RMCD IMS: The Contractor shall coordinate the scheduling of a CDR. The Contractor shall give the C-5M SPO personnel a minimum of thirty (30) business days notice of the meeting date. The Contractor shall provide a CDR meeting agenda and briefing materials at least ten (10) business days in advance of the meeting. The Contractor shall prepare and deliver a Scorecard outlining the exit criteria for CDR completion. A preliminary product shall be delivered to the Government for review and comment twenty (20) business days in advance of the CDR. Government will review and comment within 5-7 business days and submit to Contractor for correction if necessary. Upon receipt of Government feedback, the Contractor shall submit a final Scorecard to the Government ten (10) business days in advance of the CDR.

At the CDR, the Contractor shall host, present, and deliver a final C-5M RMCD product baseline documenting, at a minimum, the RMCD design architecture (to include software integration and Group A elements) and interface points within the current avionics architecture, the planned installation location for all Group A/B hardware, the projected impacts to or dependencies with current aircraft systems/subsystems, and a final TDP (to include all engineering drawings). The Contractor shall also identify the final test and certification strategy, final software fielding plan, and summary risks and/or integration challenges (to include mitigations) that impinge upon the functional baseline, installation, and flight testing. CDRL Reference in paragraph 4.2, DI-MGMT-81605, Briefing Material; DI-ADMN-81249B/T, Conference Agenda - Meeting Agenda; DI-ADMN-81250B/T, Conference Minutes; DI-SESS-81000F/T, Product Engineering Design Data and Associated List - Product Drawings, Models and Associated Lists; and DI-SESS-81845, Design Review Information Package (DRIP).

The Contractor shall provide a summary of the final logistics-related analyses and planning and support requirements (e.g., test sets, spares, maintenance manuals, technical orders, support equipment, etc.) that will culminate in a field-supportable PSP. CDRL Reference in paragraph 4.2, DI-SESS-81759A/T, Logistics Product Data Summaries.

Following the CDR, the Contractor shall submit minutes summarizing the meeting findings and mitigations, as applicable. The Contractor shall also complete all corrective actions, responses, and an updated briefing package to the Government PCO via E-Mail, NLT ten (10) business days after the completion of the CDR.

4.7 RMCD TDP Preparation

4.7.1 TDP: The Contractor shall develop and deliver updates to the TDP for the RMCD product baseline. This TDP shall incorporate all products required to characterize, integrate, install, and support the hardware and software components of the design. TDP validation will occur for each milestone; final prior to Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA). All final documentation artifacts shall be delivered on physical media for configuration control. All drawings and routing diagrams requiring build up information shall be incorporated into the drawing as much as possible. Drawings shall refer to Military Standards as much as possible. At a minimum, the TDP shall include: Detailed TCTO, Level-III Drawings, Wiring Diagrams and Wire Routing Illustrations (CDRL Reference in paragraph 4.2, DI-SESS-81000F/T, Product Engineering Design Data and Associated Lists - Technical Data Package (TDP).)

4.7.2 Engineering Data: The Contractor shall develop and deliver a preliminary TDP to the Government, for review and comment, ten (10) business days in advance of each milestone and final prior to FCA/PCA. The Contractor shall be responsible for adjudicating all Government comments with the author and updating the TDP, as required. The contractor shall develop / produce /maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. TDP 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 provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s).

Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be created IAW the American Society of Mechanical Engineers (ASME) standards: ASME Y14.100-2017, Appendix B, sections B6 through B9.1 and Appendices C, D, E, and F in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35 and ASME Y14.41 and as defined in the corresponding CDRL for this task to create and deliver Product Drawings Models and Associated Lists (Engineering Data) under this contract.

Data set classification code marking IAW Appendix F of ASME Y14.100-2017 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 contractor shall submit an Engineering Drawing Tree identifying all system, subsystem, and equipment drawings as part of the drawing package. CDRL Reference in paragraph 4.2, DI-DRPR-81961B, Engineering Drawing Tree, component of DI-SESS-81000F/T, Product Engineering Design Data and Associated Lists - Technical Data Package (TDP).

Relationship of Contractor with Subcontractors/Vendors: The contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program. CDRL Reference in paragraph 4.2, DI-SESS- 81000F/T, Product Engineering Design Data and Associated Lists - Technical Data Package (TDP); and DI-SESS-81248B, Interface Control Document (ICD) - PRELIMINARY TDP.

4.7.3 Final TDP: The Contractor shall develop and deliver a final TDP to the Government, for review and comment, in advance of each milestone; final prior to FCA/PCA. The final TDP shall be delivered 14 days prior to In Process Reviews, Verification, and Prepublication Review. Written Government comments/disposition on the data shall be within 15 days after receipt of data. When comments are provided, the Contractor shall provide an updated submittal 15 days after receipt of Government comments/change requests. All final documentation artifacts shall be delivered on physical media for configuration control. CDRL Reference in paragraph 4.2, DI-SESS-81000F/T, Product Engineering Design Data and Associated Lists - Technical Data Package (TDP); and DI-SESS-81248B/T, Interface Control Document (ICD) - FINAL TDP.

4.8 Pre-Production Kit Fabrication, Procurement, Assembly, and Kitting

4.8.1 Installation Kits: The Contractor shall fabricate, procure, and assemble the CDR-verified, RMCD product baseline into installation kits.

4.8.2 Bill of Materials: The Contractor shall develop a Bill of Materials (BOM) MIL-STD-3018 w/CHANGE 2 for each installation kit. At a minimum, the BOM shall specify the Standard Base Supply System (SBSS) number for each stock-listed Group A or B component, the vendor part number (for non-SBSS components),), and Group A/B component quantities per kit. Group A Kits are the items, parts, or components to be permanently or semi-permanently installed in a CI to support, secure, interconnect, or accommodate the equipment provided in the modification Group B kit. Group B Kits are the equipment which, when installed in a CI with a Group A kit, completes a modification. The kits shall also include a detailed, installation TCTO. The Contractor shall use the vendor part number in lieu of a Contractor identified part number. CDRL Reference in paragraph 4.2, DI-SESS-82294, Logistics Management Information (LMI) – Bill of Materials.

4.8.3 Kit Component Audit: At the conclusion of the initial kit completion and per the IMS, the Contractor shall coordinate the scheduling of a Kit Component Audit with the C-5M SPO personnel. The Contractor shall provide the C-5M SPO personnel with an agenda, within a minimum of ten (10) business days’ notice of the meeting date. At this audit, the Contractor shall support a physical inspection and crosscheck (against the BOM) of the kit, and the delivery schedule for the Prototype Installation. No more than one (1) error in each kit shall be identified. Contractor shall ensure there are no deviations between the BOM and the physical inspection of the kit. Contractor shall ensure that any required corrective actions are completed and responses provided to the Government PCO by email, NLT ten (10) business days after audit completion Following this review, the Contractor shall submit meeting minutes summarizing all findings/issues and Contractor mitigations, as applicable. CDRL Reference in paragraph 4.2, DI-MGMT-81605, Briefing Material; DI-ADMN-81249B/T, Conference Agenda - Meeting Agenda; DI-ADMN-81250B/T, Conference Minutes

4.9 RMCD Prototype Installation/Planning/Execution

The Contractor shall execute a trial-kit install for the RMCD Upgrade modification kit.

4.9.1 Installation Readiness Review: Per the IMS, the Contractor shall coordinate the scheduling of an Installation Readiness Review (IRR). The Contractor shall schedule the IRR NLT twenty (20) business days in advance of first Prototype Installation start. The Contractor shall give the C-5M SPO personnel a minimum of ten (10) business days’ notice of the meeting date.

The Contractor shall provide a meeting agenda and briefing materials for the IRR within ten (10) business days of the meeting. At the IRR, the Contractor shall present a Prototype Installation Execution Plan (for two C-5M installs)—to include installation location, ferry configuration, maintenance of aircraft records, pre-induction inspection, and associated induction and completion timelines.

The Plan shall assume Contractor completion of the Prototype Installation, and technical assistance for completion of a TO verification—with all actions overseen by the Defense Contract Management Agency (DCMA) and the C-5M SPO. The Plan shall outline the procedures and facility certifications involved in physical security of the C-5M aircraft (from point of acceptance to post-retrofit departure). The Contractor shall prepare and deliver meeting minutes following the IRR that summarize findings and Contractor mitigations, as applicable. The Contractor shall ensure corrective actions are completed and responses are submitted to the Government PCO by E-Mail, NLT ten (10) business days after meeting completion. CDRL Reference in paragraph 4.2, DI-MGMT-81605, Briefing Material; DI-ADMN-81249B/T, Conference Agenda - Meeting Agenda; DI-ADMN-81250B/T, Conference Minutes; DI-SESS-80198B, Internal Loads and Static Strength Analysis Report (ILSSAR); and TM-86-01Q, Technical Manuals – Organizational Level (O-Level) and Programmed Depot Maintenance (PDM) Technical Orders (TOs); DI-SESS-81785A/T, System Engineering Management Plan (SEMP).

4.9.2. Prototype Installation: Consistent with the Execution Plan, the Contractor…