DRAFT C-40C_FLT_EXP SOW.pdf

STATEMENT OF WORK – C-40C Fleet Expansion

Contents

1.0. Scope

1.1. Purpose

1.2. Background and Mission Overview

1.3. System-of-Systems Definition

1.4. Regulatory Framework and Airworthiness

1.5. Technical Integration Scope

1.5.1. Flight Deck and Avionics

1.5.2. Command Communication System

1.5.3. Mission Connectivity Backbone

1.6. Platform Information Technology (PIT) and Cybersecurity

1.7. Technical Data and Sustainment Support

1.8. Explicit Exclusions

2.0. Applicable Documents

2.1. General

2.2. Government Documents

2.2.1. Department of Defense and Air Force Regulations

2.2.2. Technical Orders and Handbooks

2.2.3. Program-Specific Technical Baselines

2.3. Other Documents

2.3.1. Civil Aviation Regulations and Standards

2.3.2. National Institute of Standards and Technology

2.3.3. Original Equipment Manufacturer Data

2.4. Order of Precedence

3.0. Requirements

3.1. Aircraft Acquisition and Baseline Establishment

3.1.1. Airframe Procurement

3.1.2. Configuration Baseline

3.1.3. Commercial Derivative Nature

3.2. Regulatory Compliance and Certification

3.2.1. FAA Airworthiness

3.2.2. Military Flight Release

3.3. Flight Deck and Avionics System Integration

3.3.1. Flight Management and Navigation

3.3.2. Surveillance and Safety

3.3.3. Flight Recording and Displays

3.4. Communications Systems

3.4.1. Radio Communications

3.4.2. Data Link Management

3.5. Mission Communications Backbone Integration

3.5.1. Connectivity Systems

3.5.2. Network Provisions

3.6. Cybersecurity and Platform Integration Technology Protection

3.6.1. Security Control Implementation

3.6.2. Supply Chain Risk Management

3.6.3. Information Protection

3.6.4. Security Sweep

3.7. Maintenance and Sustaining Engineering Data

3.7.1. Technical Manual Updates

3.7.2. Weight and Balance

3.7.3. Inspection Requirements

3.8. Test, Evaluation, and Acceptance

3.8.1. Acceptance Check Flights

3.8.2. EMI/EMC and EMSEC Verification

3.8.3. Ground Support Verification

4.0. Deliverables

4.1. General Data Requirements

4.2. Program Management and Engineering Data

4.3. Technical Orders and Publications

4.4. System Security and Cybersecurity Data

4.5. Test and Supportability Data

5.0. Special Requirements

5.1. Government Furnished Property/Equipment/Data

5.1.1. GFP for Installation

5.1.2. Support Equipment

5.1.3. GFI

5.2. Security and Clearance Requirements

5.2.1. Personnel Security

5.2.2. Operations Security

5.3. Environmental, Health, and Safety

5.3.1. Hazardous Materials and Ozone Depleting Chemicals

5.3.2. System Safety

5.4. Travel and Field Service Support

5.4.1. Technical Support Travel

5.4.2. Mission Essential Support

5.5. Transition, Handover, and Integration

5.5.1. Joint Inventory

5.5.2. Documentation Handover

5.5.3. Physical Configuration Audit

5.6. Interoperability and Net-Ready Requirements

6.0. Program Management & Quality Oversight

6.1. Program Management

6.1.1. Annual Program Management Review

6.1.2. Technical Interchange Meetings

6.1.3. Status Tag-Ups

6.2. Configuration Management and Baseline Control

6.2.1. Configuration Control Board

6.2.2. Service Action Review Board

6.2.3. Baseline Maintenance

6.3. Quality Management and Deficiency Reporting

6.3.1. Quality Management System

6.3.2. Deficiency Reporting

6.3.3. Product Quality Deficiency Reports

6.4. Over and Above Work Procedures

6.4.1. Work Request Process

6.4.2. O&A Documentation

6.4.3. Definitization

6.5. Performance Metrics and Delivery Standards

6.5.1. Delivery Quality Thresholds

6.5.2. Schedule Compliance

6.5.3. Technical Order Accuracy

6.6. Supply Chain and Obsolescence Management

6.6.1. Supply Chain Risk Management

6.6.2. DMSMS and Obsolescence Tracking

1.0. Scope

1.1. Purpose

The purpose of this contract is to procure one used Boeing 737-700 Increased Gross Weight (IGW) aircraft and perform the engineering, integration, and modification necessary to missionize the platform to a C-40C configuration. The final delivered product shall be functionally and technically equivalent to the Air Force Reserve Command (AFRC) C-40C aircraft currently stationed at Scott AFB, Illinois (Tails 05-0730, 05-0932, 05-4613, and 09-0540). Exceptions to this requirement will be explicitly stated in paragraph 1.8 of this SOW, and any further exceptions must be approved in writing by the Contracting Officer. This effort transforms a commercial aircraft into a Military Commercial Derivative Aircraft (MCDA) capable of meeting the high-priority requirements of the Distinguished Visitor (DV) Airlift mission.

1.2. Background and Mission Overview

The C-40 fleet supports the Air Force Concept of Operations (CONOPs) for Global Mobility. These aircraft provide safe, secure, and dedicated worldwide transportation for senior government and military officials, including the Secretary of War, Secretary of State, and Congressional Delegations (CODEL). Often referred to as an "office in the sky," the C-40C must provide the communications and Command and Control (C2) capabilities necessary for senior leaders to fulfill their responsibilities regardless of location, across the full spectrum of operating environments.

1.3. System-of-Systems Definition

The C-40C is a "system of systems" where the platform and its various missionized components must be integrated to maintain both civil and military standards. While the C-40 Program Office (AFLCMC/WVV) manages the overall platform, the Mission Communication System (MCS) and Aircraft Survivability Equipment (ASE) have historically fallen under the sustainment scope of the 645th Aeronautical Systems Group (Big Safari). Under this procurement, the Contractor shall be responsible for the physical and electrical integration of the "backbone" systems that enable these mission capabilities

1.4. Regulatory Framework and Airworthiness

The aircraft shall be procured and modified as a Commercial Derivative Aircraft (CDA) following Federal Aviation Administration (FAA) and Air Force Policy Directive (AFPD) 62-6 airworthiness policies.

o FAA Certification: The Contractor shall maintain the aircraft’s FAA Type Certification (TC) and obtain any necessary Supplemental Type Certificates (STCs) for military-unique modifications.

o Commercial Standards: To the maximum extent possible, commercial practices and Federal Aviation Regulations (FAR) Part 25 and Part 121 standards shall be utilized to ensure the platform's long-term sustainability through the commercial infrastructure.

o Military Flight Release: Portions of modifications that cannot meet civil FARs must be documented via FAA Form 8130-31 and accepted by the Chief Engineer prior to military flight release.

1.5. Technical Integration Scope

The Contractor shall provide all labor, materials, and technical expertise to integrate the C-40C "Authorization Boundary" into the procured airframe. This includes the following functional areas:

1.5.1. Flight Deck and Avionics

The Contractor shall install a commercial "Glass Cockpit" design functionally equivalent to the Scott AFB baseline. Core components include:

o Flight Management System (FMS): Dual FMS with integrated Flight Management Computers (FMC), Control Display Units (CDU), and digital flight data loaders.

Navigation Systems: Tactical Air Navigation (TACAN), Inertial Reference Systems (IRS), and

GPS.

o Surveillance Systems: Traffic Collision Avoidance System (TCAS II), Enhanced Ground Proximity Warning System (EGPWS) with wind-shear warning, and Radio Altimeters compliant with 5G interference standards.

o Military-Unique Avionics: Integration of the APX-119 Identification Friend/Foe (IFF) Transponder with Mode 5 and the ARC-210 UHF communication system.

1.5.2. Command Communication System

The Contractor shall install the aircrew communications suite to support unrestricted worldwide military and civil flight operations. This includes HF, VHF, and UHF radios, as well as the Aircraft Communications Addressing and Reporting System (ACARS) for datalink capability with Air Traffic Control (ATC) and airline operations centers.

1.5.3. Mission Connectivity Backbone

The Contractor shall provide the infrastructure to support passenger C2 and Business Enterprise (BE) responsibilities.

o Satellite Connectivity: Integration of International Maritime Satellite (INMARSAT) to provide worldwide non-secure voice, data, and facsimile communications.

o Internal Networking: Provisions for Starshield system (STC to be installed by a third-party contractor).

1.6. Platform Information Technology (PIT) and Cybersecurity

The C-40C is designated as a PIT system, requiring compliance with the Risk Management Framework (RMF) and NIST SP 800-53 security controls. The Contractor shall:

o Ensure all installed hardware and software facilitate the required Authority to Operate (ATO) status.

o Implement Supply Chain Risk Management (SCRM) to mitigate threats such as malicious logic insertion or counterfeit electronic parts.

o Provide all necessary system security engineering data to support the annual security assessments and re-authorization efforts.

1.7. Technical Data and Sustainment Support

The Contractor shall deliver a complete technical data package for the newly configured tail number.

o Technical Manuals: Provide support to Engineering Services Support (ESS) Contractor for the purposes of updates to the Aircraft Maintenance Manual (AMM), Illustrated Parts Catalog (IPC), Wiring Diagram Manuals (WDM), and Fault Isolation Manuals (FIM).

o Configuration Management: Maintain accurate configuration status accounting, including software versions, database numbers, and Part Number (P/N) tracking for all modified systems.

o Ground Support Equipment (GSE): Deliver any peculiar GSE required for the maintenance of the new tail number, such as specific hangar power units equivalent to the Scott AFB configuration

1.8. Explicit Exclusions

To clarify the boundaries of the Contractor's responsibility, the following items are expressly excluded from the scope of this procurement:

o Interior Cabin Items: Procurement or installation of executive furniture, divans, galleys, or specialized DV compartment furnishings.

o Exterior Paint: Delivery of the aircraft with a specific OSA/EA paint scheme is not required; the aircraft shall be delivered in an airworthy standard commercial paint, primer, or "green" state.

o Self-Defense Systems (SDS): The Contractor is not responsible for the installation of Large Aircraft Infrared Countermeasures (LAIRCM) or other defensive suites.

2.0. Applicable Documents

2.1. General

The following documents of the exact issue shown, and no other, form a part of this Statement of Work (SOW) to the extent specified herein. For any technical or regulatory conflicts that the Contractor believes drive unnecessary costs or impact the airworthiness and safety of the platform, the Contractor shall contact the C-40 Program Office (PO) through the Procuring Contracting Officer (PCO) for formal resolution prior to proceeding with the work effort.

2.2. Government Documents

2.2.1. Department of Defense and Air Force Regulations

o 32 CFR Part 117: National Industrial Security Program Operating Manual (NISPOM).

o DAFI 21-101: Aircraft and Equipment Maintenance Management.

o AFI 21-103: Equipment Inventory, Status, and Utilization

Reporting.

o AFPD 62-4 (or latest revision): Airworthiness of Commercial

Derivative Aircraft.

o AFI 91-204: Safety Investigation and Hazard Reporting.

o DoDI 5200.39: Identification and Protection of Critical Program

Information (CPI) in Suspended Research, Development, Test, and Evaluation.

o DoDI 5200.48: Controlled Unclassified Information (CUI).

o DoDI 8582.01: Security of Non-DoD Information Systems

Processing Unclassified Nonpublic DoD Information.

o DAFMAN 16-1406V2: National Industrial Security Program:

Industrial Security Procedures for Government Activities.

2.2.2. Technical Orders and Handbooks

o MIL-HDBK-245: Handbook for Preparation of Statement of Work

(SOW).

o MIL-STD-882E: Department of Defense Standard Practice:

System Safety.

o T.O. 00-5-1: AF Technical Order System.

o T.O. 00-20 Series: Maintenance Management Policy.

o T.O. 00-25-4: Depot Maintenance of Aerospace Vehicles and

Training Equipment.

o T.O. 00-35D-54: USAF Deficiency Reporting, Investigation, and

Resolution.

o DoD AIMS 97-1000: Performance/Design and Test Requirements for the Mark XIIA IFF System

2.2.3. Program-Specific Technical Baselines

o C-40 Architecture Analysis Report (AAR) 10.0: Defines the Authorization Boundary, physical architecture, and data flows for the missionized system.

o C-40 System Security Plan (SSP) 12.0 (Sep 2023): Outlines the cybersecurity controls, Assessment and Authorization (A&A) boundaries, and OPSEC policies.

o C-40 Continuous Monitoring Strategy (CMS) 6.0: Defines the Tier 1-3 requirements for ongoing security assessment of the PIT system.

o C-40B/C Security Classification Guide (May 2021): Provides the specific marking and handling instructions for classified programmatic and technical data.

o C-40 Program Protection Plan (PPP) Ver 3.0 (Jan 2026): Identifies CPI, Critical Components (CCs), and mandated countermeasures.

2.3. Other Documents

2.3.1. Civil Aviation Regulations and Standards

o 14 CFR Part 25: Airworthiness Standards: Transport Category Airplanes.

o 14 CFR Part 121: Operating Requirements: Domestic, Flag, and Supplemental Operations.

o 14 CFR Part 145: Repair Stations.

o FAA Advisory Circular (AC) 120-42B: Extended Operations

(ETOPS and Polar Operations).

o FAA DO-178B: Software Considerations in Airborne Systems and Equipment Certification.

o ATA-104: Specifications for Aircraft Maintenance Training.

2.3.2. National Institute of Standards and Technology

o NIST SP 800-37 R2: Risk Management Framework for Information Systems and Organizations.

o NIST SP 800-53 R5: Security and Privacy Controls for Information Systems and Organizations.

o NIST SP 800-137: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations.

o NIST SP 800-171: Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations.

2.3.3. Original Equipment Manufacturer Data

o Boeing 737-700 Aircraft Maintenance Manual (AMM):

Commercial baseline for organizational maintenance.

o Boeing 737-700 Illustrated Parts Catalog (IPC): Configuration baseline for common hardware and sub-components.

o Boeing 737-700 Fault Isolation Manual (FIM): Troubleshooting protocols.

o Boeing Flight Crew Operations Manual (FCOM): Core flight procedures

2.4. Order of Precedence

In the event of a conflict between the technical procedures or processes defined by the Air Force, the OEM, or the FAA, the following order of precedence shall apply:

1. Specific C-40B/C Applicable Commercial Aircraft Manuals.

2. The more stringent of the AF regulations, general technical orders, OEM guidance, or FAA requirements.

3. The Statement of Work (SOW).

3.0. Requirements

3.1. Aircraft Acquisition and Baseline Establishment

3.1.1. Airframe Procurement

The Contractor shall procure one used Boeing 737-700 Increased Gross Weight (IGW) airframe. The aircraft maintenance history and structural integrity must support continued service of at least 15 years.

3.1.2. Configuration Baseline

The Contractor shall modify the procured airframe to a C-40C configuration that is functionally and technically equivalent to the Air Force Reserve Command (AFRC) fleet stationed at Scott AFB, Illinois (Tails 05-0730, 05-0932, 05-4613, and 09-0540), with the exceptions listed in Section 1.8 of this SOW and any exceptions approved in writing by the PCO.

3.1.3. Commercial Derivative Nature

To the maximum extent possible, the Contractor shall utilize commercial best practices and infrastructure to maintain the platform's status as a Commercial Derivative Aircraft (CDA).

3.2. Regulatory Compliance and Certification

3.2.1. FAA Airworthiness

The Contractor shall maintain the aircraft’s Federal Aviation Administration (FAA) Type Certification (TC) and obtain necessary Supplemental Type Certificates (STCs) for all missionized modifications.

The aircraft must comply with 14 CFR Part 25 (Airworthiness Standards) and Part 121 (Operating Requirements).

3.2.2. Military Flight Release

For any military-unique modifications that cannot meet civil Federal Aviation Regulations (FARs), the Contractor shall provide the necessary airworthiness data to support a Military Flight Release (MFR). These items shall be documented via FAA Form 8130-31, “Statement of Conformity – Military Aircraft,” for acceptance by the Chief Engineer.

3.3. Flight Deck and Avionics System Integration

The Contractor shall install and integrate a modern "Glass Cockpit" avionics suite functionally equivalent to the Scott AFB baseline.

3.3.1. Flight Management and Navigation

o Dual Flight Management System (FMS): Install dual, independent commercial FMS with integrated Flight Management Computers (FMC) and Control Display Units (CDU).

Global Positioning System (GPS): Integrate dual GPS receivers.

o Inertial Navigation: Install dual Inertial Reference Systems (IRS) or Air Data Inertial Reference Units (ADIRU) integrated into the multi-sensor navigation solution.

o Tactical Navigation: Install an advanced digital TACAN system for polar coordinate navigation.

3.3.2. Surveillance and Safety

o Identification Friend or Foe (IFF): Install an APX-119 IFF Transponder with KIV-77 Cryptographic Applique supporting Modes S and 5.

o Collision Avoidance: Install a Traffic Alert and Collision Avoidance System (TCAS II) compliant with ICAO ACAS II standards.

o Terrain Awareness: Install an Enhanced Ground Proximity Warning System (EGPWS) with integrated wind-shear warning and a Class A Terrain Awareness and Warning System (TAWS).

o Radio Altimeter: Install Radio Altimeters immune to 5G interference.

3.3.3. Flight Recording and Displays

o Heads Up Display (HUD): Install the HUD to provide enhanced situational awareness during all phases of flight.

o Flight Data/Voice Recording: Install a standard commercial digital Cockpit Voice Recorder (CVR) and Flight Data Recorder (FDR) capable of continuous two-hour recording.

3.4. Communications Systems

The Contractor shall install a communications suite to enable unrestricted worldwide military and civil flight operations.

3.4.1. Radio Communications

o UHF Communications: Install the ARC-210 UHF communication system.

o HF Communications: Install dual HF radios with Selected Call (SELCAL) and High Frequency Data Link (HFDL) capabilities.

o VHF Communications: Install dual 8.33 kHz VHF voice radios with VHF Digital Link Mode 2 (VDLM2).

3.4.2. Data Link Management

o ACARS: Integrate an Aircraft Communications Addressing and Reporting System (ACARS) Communication Management Unit (CMU) for automated position reporting and clearance exchange via radio or satellite.

o SATCOM Support: Install the Cobham Aviator 700D system for non-secure voice and data communications.

3.5. Mission Communications Backbone Integration

While executive furnishings and cabin items are excluded, the Contractor shall install the underlying technical infrastructure for passenger communications.

3.5.1. Connectivity Systems

o Starlink/Starshield: Install provisions for Starlink/Starshield system. The Government will provide provisioning data.

3.5.2. Network Provisions

o Wired/Wireless Ports: Provide data ports at designated staff locations to support future Government-furnished carry-on equipment.

3.6. Cybersecurity and Platform Integration Technology Protection

As the C-40C is a PIT system, the Contractor shall implement cybersecurity protections in accordance with the Risk Management Framework (RMF).

3.6.1. Security Control Implementation

The Contractor shall implement and verify the security controls identified in the C-40 System Security Plan (SSP), derived from NIST SP 800-53 R5.

3.6.2. Supply Chain Risk Management

o Trusted Suppliers: The Contractor shall execute an SCRM program that utilizes Trusted Suppliers and implements attack vector prevention measures.

o Counterfeit Prevention: Implement a Counterfeit Parts Protection Plan to mitigate risks from counterfeit electronic components or malicious software.

3.6.3. Information Protection

o Media Sanitization: All storage media (USB, PCMCIA, Hard Drives) must be capable of sanitization per NIST SP 800-88 R1.

o Anti-Tamper: Protect all inherited Critical Program Information (CPI) with anti-tamper features and countermeasures commensurate with the originating program’s requirements.

3.6.4. Security Sweep

Prior to the beginning of aircraft modifications, the Contractor shall perform a security sweep of all aircraft software and firmware for any malicious software and report the results of the activity to the Government.

3.7. Maintenance and Sustaining Engineering Data

3.7.1. Technical Manual Updates

The Contractor shall support all efforts by the ESS Contractor to deliver a complete and tail-number-specific technical data package, including updates to the Aircraft Maintenance Manual (AMM), Illustrated Parts Catalog (IPC), Fault Isolation Manual (FIM), and Wiring Diagram Manuals (WDM).

3.7.2. Weight and Balance

The Contractor shall provide updated Weight and Balance Clearance Form F data (DD Form 365-4) reflecting the final modified configuration.

3.7.3. Inspection Requirements

The Contractor shall support all efforts by the ESS Contractor to update the Maintenance Inspection Requirements Document (MIRD) to include all newly installed mission systems and Life-Limited Parts (LLPs).

3.8. Test, Evaluation, and Acceptance

3.8.1. Acceptance Check Flights

The Contractor shall execute a comprehensive Acceptance Check Flight (ACF) program to verify the functional performance of all integrated systems against Scott AFB baseline requirements. The Contractor shall provide qualified test pilots to perform any necessary Functional Check Flights (FCF) or Operational Check Flights (OCF) prior to the ACF, which will be conducted by at least one Government pilot.

3.8.2. EMI/EMC and EMSEC Verification

The Contractor shall perform Electromagnetic Interference/Compatibility (EMI/EMC) testing and support Air Force-conducted Emissions Security (EMSEC) tests prior to operational release.

3.8.3. Ground Support Verification

Verify the compatibility of the new tail number with Scott AFB peculiar ground support equipment identified by the owning unit.

4.0. Deliverables

4.1. General Data Requirements

The Contractor shall deliver data in accordance with the Contract Data Requirements List (CDRL), DD Form 1423. All data delivered under this contract is considered a byproduct of the tasking described in Section 3, and the Contractor shall not interpret any tasking as a requirement to restate delivery instructions within the SOW. Each deliverable shall be prepared using the format and content requirements defined in the associated Data Item Descriptions (DID). The Contractor shall ensure that all technical data—including drawings, manuals, and reports—is provided with "Unlimited Rights" to the Government for Operation, Maintenance, Installation, Training, and Test (OMITT) data as defined in 10 USC § 2320.

4.2. Program Management and Engineering Data

The Contractor shall deliver management data to ensure Government oversight of the modification and integration efforts. This include a Program Management Plan (PMP) (CDRL A0xx) that addresses modification management, security, quality assurance, and risk management. The Contractor shall deliver a Systems Engineering Management Plan (SEMP) (CDRL A0xx) that details the requirements analysis and baseline management processes for the new aircraft. To support schedule transparency, the Contractor shall deliver an Integrated Master Schedule (IMS) (CDRL A0xx) reflecting all critical milestones, from induction through Acceptance Check Flights (ACF) and Return to Service (RTS). The Contractor shall also provide recurring Risk Management Status Reports (CDRL A0xx) identifying both unmitigated high risks and mitigated moderate risks.

4.3. Technical Orders and Publications

As a byproduct of the hardware and software integration tasking, the Contractor shall deliver a complete technical data package for the as-built configuration. This package shall include updates to the following commercial-derivative manuals:

o Aircraft Maintenance Manual (AMM) and Illustrated Parts Catalog (IPC): Updates shall reflect the tail-number-specific configuration, including all military-unique components.

o Wiring Diagram Manuals (WDM) and Lists: The Contractor shall maintain databases of all equipment lists, splices, and hook-up data necessary to develop these changes.

o Flight Manuals: The Contractor shall support all efforts by the ESS Contractor to update the Flight Crew Operations Manual (FCOM), Quick Reference Handbook (QRH), and Minimum Equipment List (MEL) to support aircrew operations.

o Weight and Balance Clearance: The Contractor shall deliver updated DD Form 365-4, Weight and Balance Clearance Form F – Transport, reflecting the modified center of gravity and payload capabilities.

4.4. System Security and Cybersecurity Data

To support the Platform Information Technology (PIT) Authorization to Operate (ATO), the Contractor shall deliver system security engineering data. Key deliverables include:

o Program Protection Implementation Plan (PPIP): (CDRL A0xx) This plan shall describe the Contractor's specific countermeasures to protect Critical Program Information (CPI) and Critical Components (CCs) during modification.

o System Security Plan (SSP) and Architecture Analysis Report (AAR):

Updates (CDRL A0xx) shall be provided to document the final physical and logical architecture within the authorization boundary.

o Supply Chain Risk Management (SCRM) Assessment: The Contractor shall deliver a list of all logic-bearing components and their associated vendors, including assessments of trusted suppliers and attack vector prevention.

o Media Sanitization Records: Documentation verifying that all storage media are capable of sanitization per NIST SP 800-88 R1 shall be delivered upon modification completion.

4.5. Test and Supportability Data

The Contractor shall deliver data resulting from the verification and validation of the aircraft’s mission systems.

o Test Procedures and Reports: (CDRL A0xx) These deliverables shall capture the results of ground tests, flight tests, EMI/EMC testing, and Air Force-conducted EMSEC verification.

o DMSMS and Parts Obsolescence Reports: (CDRL A0xx) The Contractor shall provide reports identifying any components installed on the aircraft that have reached end-of-life or present significant logistics supportability risks.

o Return to Service (RTS) Data Package: (CDRL A0xx) A comprehensive package including FAA Form 8130s, engine records, and a list of all backordered parts shall be delivered upon aircraft handover.

5.0. Special Requirements

5.1. Government Furnished Property/Equipment/Data

As this is a Military Commercial Derivative Aircraft (MCDA) program, the Government will provide specific military-unique equipment and data necessary to bridge the gap between the commercial Boeing 737-700 baseline and the C-40C mission configuration.

5.1.1. GFP for Installation

The Government will provide a limited amount of GFM to support the missionization effort. This includes specialized cryptographic components, such as the KIV-77 Cryptographic Applique required for the APX-119 Identification Friend or Foe (IFF) transponder.

5.1.2. Support Equipment

While the Contractor is generally responsible for furnishing SE, the Government may provide limited initial inventory of consumable or life-limited parts, such as built-up wheel and tire assemblies (WTA). Existing unit-owned support equipment at Scott AFB shall be leveraged to the maximum extent possible.

5.1.3. GFI

The Government will provide access to the technical baseline documentation, including the C-40 Architecture Analysis Report (AAR) and System Security Plan (SSP), to ensure the as-built configuration meets current Platform Information Technology (PIT) standards.

5.2. Security and Clearance Requirements

The Contractor shall comply with all security requirements identified in the DD Form 254 and the National Industrial Security Program Operating Manual (NISPOM) (32 CFR Part 117).

5.2.1. Personnel Security

All Contractor personnel working directly on the aircraft or mission systems must possess and maintain a minimum of a SECRET security clearance.

5.2.2. Operations Security

The Contractor shall implement an approved OPSEC plan to protect Critical Program Information (CPI) and prevent unauthorized disclosure of mission-sensitive data regarding aircraft capabilities or funding. This includes ensuring that unmanned aircraft are sanitized of all removable classified materials, including cryptographic keys and Navigation Database (NDB) disks.

5.3. Environmental, Health, and Safety

5.3.1. Hazardous Materials and Ozone Depleting Chemicals

The Contractor shall avoid the use of hazardous materials and Ozone Depleting Chemicals (ODCs) unless no FAA-certified substitutes are available. If such materials are required for modification or maintenance, the Contractor shall provide the Air Force with Safety Data Sheets (SDS) and instructions for safe handling and disposal.

5.3.2. System Safety

The Contractor shall conduct hazard analyses in accordance with MIL- STD-882E to ensure that interfaces between military-unique equipment and the commercial airframe do not degrade the overall safety of the system.

5.4. Travel and Field Service Support

5.4.1. Technical Support Travel

Contractor personnel, including Field Service Representatives (FSRs), may be required to travel to Scott AFB, IL, or other Government locations to support site surveys, technical interchange meetings (TIMs), or aircraft handover activities.

5.4.2. Mission Essential Support

If required for troubleshooting or urgent field repairs, Contractor personnel may be granted Mission Essential Ground Personnel (MEGP) status to utilize military air transportation.

5.5. Transition, Handover, and Integration

5.5.1. Joint Inventory

Upon completion of the modification and prior to final acceptance, the Contractor shall conduct a 100% joint physical inventory of all Government property (GFE/GFP) with a designated Government representative.

5.5.2. Documentation Handover

The Contractor shall deliver a comprehensive Return to Service (RTS) data package, including all serviceability and FAA certification documentation (e.g., FAA 8130-3 forms) and engine/APU shop visit records.

5.5.3. Physical Configuration Audit

The Contractor shall conduct a non-intrusive Physical Configuration Audit to verify that the as-built configuration is accurately reflected in the aircraft's records and technical manuals.

5.6. Interoperability and Net-Ready Requirements

The Contractor shall ensure that all mission systems are interoperable with U.S. joint and NATO forces. All system data intended for exchange must be tagged in accordance with the DoD Information Technology Standards Registry (DISR) and Net-Ready Key Performance Parameter (NR-KPP) requirements.

6.0. Program Management & Quality Oversight

6.1. Program Management

The Contractor shall establish a comprehensive program management structure to ensure mission success, schedule adherence, and technical transparency throughout the aircraft procurement and missionization lifecycle.

6.1.1. Annual Program Management Review

The Contractor shall host and lead annual PMRs to provide the Government with a detailed assessment of cost, schedule, and technical performance. These reviews shall involve key stakeholders including the C-40 Program Office (PO), Air Mobility Command (AMC), and relevant field units.

6.1.2. Technical Interchange Meetings

The Contractor shall conduct TIMs as necessary to resolve complex integration challenges. These meetings shall prioritize the resolution of high-visibility issues such as 5G altimeter roadmap compliance, Brake harmonization with commercial parts-pooling, and Enhanced Flight Vision System (EFVS) de-modification.

6.1.3. Status Tag-Ups

The Contractor shall participate in weekly Program Manager tag-ups and monthly Customer tag-ups to provide real-time updates on proposal status, contract actions, and ongoing modification progress.

6.2. Configuration Management and Baseline Control

The Contractor shall implement a rigorous configuration management process to ensure the aircraft’s "office in the sky" mission remains functional and FAA-certified.

6.2.1. Configuration Control Board

The Contractor shall manage configuration changes through the formally organized Government Configuration Control Board (CCB). Any proposed modification to hardware or software must be documented, validated, and approved by the CCB prior to implementation.

6.2.2. Service Action Review Board

The Contractor shall establish a SARB process to evaluate technical literature issued by the FAA, Boeing (OEM), or other vendors. The Contractor shall perform independent technical reviews of all service actions for applicability to the Scott AFB baseline and present recommendations to the Government on a quarterly basis.

6.2.3. Baseline Maintenance

The Contractor shall ensure that the modified tail number is baselined against the C-40C Scott AFB configuration, maintaining accuracy in the Aircraft Architecture Analysis Report (AAR) and the system's "Authorization Boundary".

6.3. Quality Management and Deficiency Reporting

6.3.1. Quality Management System

The Contractor shall maintain a Quality Management System (QMS) that meets industry standards (e.g., AS9100) and FAA Part 145 repair station requirements.

6.3.2. Deficiency Reporting

The Contractor shall utilize the Joint Deficiency Reporting System (JDRS) to identify, investigate, and resolve all hardware and software deficiencies encountered during the modification effort.

6.3.3. Product Quality Deficiency Reports

The Contractor shall perform root cause analysis on confirmed Product Quality Deficiency Reports (PQDRs), such as those related to paint chipping or intermittent avionics signals, and provide findings to the Government to maintain the fleet's high reliability standards.

6.4. Over and Above Work Procedures

Due to the procurement of a used commercial airframe, the Contractor shall follow standard procedures for Over and Above (O&A) work required to resolve non-routine defects discovered during the conversion process.

6.4.1. Work Request Process

The Contractor shall submit a formal Work Request (WR) for any maintenance or repair task not covered by the basic missionization scope.

Each WR must identify the specific manual or technical reference (e.g., AMM or SRM) used to justify the repair

6.4.2. O&A Documentation

WRs shall include a detailed description of the discrepancy, a 3-point airframe location, and a breakdown of "hands-on" labor hours multiplied by the contract fixed hourly rate.

6.4.3. Definitization

The Contractor shall provide all necessary receipts and justification data to the Administrative Contracting Officer (ACO) to allow for the definitization of O&A work within 10 business days of completion.

6.5. Performance Metrics and Delivery Standards

6.5.1. Delivery Quality Thresholds

The Contractor shall deliver the aircraft from the modification facility with zero critical defects, no more than one major defect, and no more than ten minor defects attributed to the Contractor per TO 00-35D-54.

6.5.2. Schedule Compliance

The Contractor shall deliver all Contract Data Requirements List (CDRL) items on or before the negotiated due date. Final aircraft delivery shall be made in accordance with the contract Turn-Around-Time (TAT) or the PCO-approved schedule

6.5.3. Technical Order Accuracy

The Contractor shall ensure that all technical data—including Illustrated Parts Catalog (IPC), Aircraft Maintenance Manual (AMM), and Wiring Diagram Manual (WDM) updates—reflect the 100% accurate as-built configuration of the modified aircraft.

6.6. Supply Chain and Obsolescence Management

6.6.1. Supply Chain Risk Management

The Contractor shall execute an SCRM assessment to ensure all logic-bearing components are procured through Trusted Suppliers, with active attack-vector prevention measures in place throughout the lifecycle.

6.6.2. DMSMS and Obsolescence Tracking

The Contractor shall proactively monitor Diminishing Manufacturing Sources and Material Shortages (DMSMS) for the C-40C unique avionics suite (e.g., ARC-210) and provide quarterly status reports on components with high supportability risk (CDRL A0xx).