Draft APAC SOW.pdf

UNCLASSIFIED

1 | P a g e

United States Air Force Life Cycle Management Center

Propulsion Directorate

Advanced Propulsion Acquisition Contract (APAC) Multiple Award Contract (MAC)

Indefinite Delivery Indefinite Quantity (IDIQ)

Statement of Work (SOW)

FA8626-25-R-B008

8 January 2026

2 | P a g e

1.0 Introduction

2.0 Scope

3.0 Delivery/Task Order (DO/TO) Requirements

3.1 Program Management

3.2 Logistics

3.3 Systems Engineering

3.3.1 Configuration Management

3.4 Test and Evaluation

3.5 Production

3.6 Security

3.6.1 Operations Security (OPSEC)

3.7 Cybersecurity

4.0 Additional Information

4.1 Intellectual Property

4.2 Exclusivity Agreements

4.3 Data

4.3.1 Data Management

4.3.2 Data Accession List

4.3.3 Technical Orders (TOs)

4.3.4 Digital Enterprise

4.4 Data Rights

5.0 Applicable Documents (not all-inclusive)

3 | P a g e

UNCLASSIFIED

1.0 Introduction

The Advanced Propulsion Acquisition Contract (APAC) MAC Indefinite Delivery Indefinite Quantity (IDIQ) Contract is designed to provide the Air Force Life Cycle Management Center Propulsion Directorate (AFLCMC/LP) with the capacity to: a) rapidly develop technologies for novel propulsion capabilities, b) implement unique solutions and innovative ideas, c) advance new technologies and system concepts that provide evolutionary, revolutionary, and disruptive capabilities for the United States Air Force and strategic partners, and d) enables a rapid response applicable to all areas and lifecycle phases of propulsion development including technology maturation, concept development, concept demonstrations, integration, procurement, production, fielding, operations, and sustainment to quickly meet current and future propulsion system requirements, while maximizing the use of the digital environment.

2.0 Scope

This contract focuses on the enhancement of propulsion technology across the life cycle including, but not limited to:

1. Science and Technology (S&T)

2. Research and Development (R&D)

3. Test and Evaluation (T&E)

4. Integration and Assembly

5. Production and Fielding

6. Operations and Sustainment (O&S)

7. Modernization

8. Prototyping

9. Experimentation

10. Hardware and Software Modifications

11. Propulsion Design

12. Data Mining, Collection, and Analysis

3.0 Delivery/Task Order (DO/TO) Requirements

The following tasks may apply to orders issued under this contract; common activities and example deliverables are identified below. Additional activities and deliverables may be required by delivery/task orders issued under the contract. Orders placed under this MAC IDIQ will be competitively awarded using FAR 16.505(b)(1) fair opportunity processes, or sole-sourced IAW FAR 16.505(b)(2).

Data shall be delivered in accordance with the Contract Data Requirements Lists (CDRLs). A listing of common CDRLs is located in Exhibit A. Specific deliverables including (hardware, software, etc.) will be included at the DO/TO levels.

4 | P a g e

UNCLASSIFIED

3.1 Program Management

The Contractor shall provide comprehensive program management, including planning, coordination, organization, and execution, as defined at the DO/TO level. Example tasks include, but are not limited to:

1. Develop, document, and report program management processes, products, and artifacts.

2. Perform digital management, including data management, risk identification, and issue management.

3. Document and report financial and contract performance.

4. Manage and report on subcontractor’s activities.

5. Manage Diminishing Manufacturing Sources and Material Shortages (DMSMS), to include development of alternative sources of supply/design.

6. Track and report of cost, schedule, and performance of efforts.

3.2 Logistics

The Contractor shall provide logistics tasks as defined at the DO/TO level. Example tasks include, but are not limited to:

1. Develop, document, and deliver concepts related to advanced repair/maintenance, predictive maintenance, increased sustainment speed/agility, sustainment engineering, and reducing the operational sustainment footprint, including consideration for incorporation into Contractor Logistics Support Type Agreements.

2. Identify, manage, and report Environmental, Safety, and Occupational Health issues and risks (including noise) as part of, and not separate from, the system engineering risk management process.

3. Develop, deliver, and maintain technical orders required for Organizational-, Intermediate, and/or Depot-level maintenance.

4. Model, document and deliver recommended initial spares packages needed for propulsion end items.

5. Design, develop, and document support equipment for propulsion end items.

6. Develop, maintain, update, and implement a Hazardous Materials Management

Plan (HMMP) in accordance with MIL-STD-882E, Department of Defense (DOD) Standard Practice for System Safety, Task 108.

3.3 Systems Engineering

The Contractor shall provide systems engineering tasks as defined at the DO/TO level, in accordance with applicable engineering documents. Example tasks include, but are not limited to:

5 | P a g e

UNCLASSIFIED

1. Perform systems engineering elements: life-cycle cost analysis, reliability engineering, maintainability and human factors engineering, safety engineering, producibility analysis, survivability analysis, hazardous material analysis, system security.

2. Perform systems engineering processes and activities: requirements analysis and allocation, affordability, risk, engine platform interface, engine systems and design integration, trade studies, and technical performance measurement.

3. Utilize digital engineering tools, processes, and methods to the maximum extent practicable within a collaborative environment.

4. Plan and develop designs for new, developmental, existing and/or modified hardware and software.

5. Support all design activities and cybersecurity.

6. Perform disciplined technical planning, coordination and execution of systems engineering to ensure product development includes strict application of technical metrics and processes, data analytics, risk reduction, and incorporating maintainability and supportability into the design.

7. Provide technical documentation, data models, engineering tools, and support all technical reviews and airworthiness tasks.

8. Develop propulsion requirements, exploring advanced materials and energy-saving concepts, design alternatives, signature/power/thermal technologies, digital twins, early systems engineering plans, and models.

9. Perform requirements management to manage, track and trace all system requirements.

10. Develop, document, and deliver concepts related to advanced repair/maintenance, predictive maintenance, increased sustainment speed/agility, sustainment engineering, and reducing the operational sustainment footprint.

11. Perform assessments, analyses, and investigations.

3.3.1 Configuration Management

The Contractor shall perform configuration management and data management assuring systematic tracking, controlling, and reporting activities for change control, to include evaluation, review, coordination, approval, documentation, implementation, and verification of changes to approved baselines for configuration control. Example tasks include, but are not limited to:

1. Support configuration and data management planning, including configuration identification, product configuration, interface control, nomenclature, computer program identification numbers, product identification/markings, and engineering release processes.

6 | P a g e

UNCLASSIFIED

2. Generate, maintain, and control concise reports for configuration change management, including configuration changes and variances, change incorporation, engineering change proposals, requests for variance, and specification change notices.

3. Conduct audits, including creating audit plans, performing functional and physical configuration audits, generating deficiency reports, conducting Deficiency, Reporting, Investigation & Resolution (DRI&R) processes, managing configuration status accounting, and utilizing product lifecycle management to capture, store, and report product configuration information.

4. Develop, deliver, and maintain Product Support Engineering products, including model-based definitions, engineering drawing trees, acquisition and sustainment data packages, technical publications and manuals, digital technical data, form, fit, and function data, and operations, maintenance, installation, and training plans.

3.4 Test and Evaluation

The Contractor shall participate in Test and Evaluation (T&E) activities to validate and verify Government requirements as defined at the DO/TO level. Additionally, Contractor shall participate in the government risk processes as defined at the DO/TO level. Example of products and activities may be required include, but not limited to:

1. Integrated test team recurring meetings

2. Test planning meetings

3. Test plan

4. Technical Review Board

5. Safety Review Board

6. Test Readiness Review

7. Test Execution

8. Test Execution Participation

9. Test Data

10. Test Data Evaluation

11. Test Report

12. Subject Matter Expert Support

13. Contractor Testing

14. Support Government Testing

3.5 Production

The Contractor shall complete production tasks as defined at the DO/TO level. Example tasks include, but are not limited to:

1. Manufacture and deliver propulsion end items.

7 | P a g e

UNCLASSIFIED

2. Manufacture and deliver spare parts to support propulsion end items.

3. Manufacture and deliver support equipment to support propulsion end items.

3.6 Security

1. Deliverable Security Requirements: Deliverables will range from Controlled

Unclassified Information (CUI) to Top Secret/Sensitive Compartmented Information/Special Access Required (TS//SCI//SAR). For classified deliverables, the Contractor shall notify the Procuring Contracting Officer (PCO) at least five business days prior to delivery, specifying the delivery method. The government will issue a DD 254 Security Classification Specification at the DO/TO level for all classified work to be completed. The DD 254 will also be coordinated through PCO, PM's, Security Office, SCI, Program Security Officer and issued to the contractor.

If classified work is to be by a Sub-Vendor, a DD 254 will be issued from the Prime Contractor to the Sub-Prime and coordinated with the Government stakeholders for approval. If an appropriate unclassified specification cannot be written, a classified specification should be issued under separate cover as a supplement to the unclassified DD 254. Program Managers, contracting officer’s representatives, and contracting officers shall involve their unit security manager/security specialists/OPSEC coordinator/COMSEC officer/Government Special Access Program Security Officer/Program Security Officer early in the acquisition process to ensure accurate security requirements are incorporated.

2. Personnel and Facility Security Requirements: The Contractor shall ensure personnel possess appropriate security clearances at the DO/TO level, obtained in accordance with DD 254. Personnel with suspended or revoked clearances shall be denied access to classified information, CUI, and classified items. The Contractor shall provide protection for classified information up to TS//SAR//SCI, as required. The Government may sponsor the Contractor for Facility Clearance upon award, if necessary. The Contractor will have three months post-award to achieve compliance. Subcontractors shall adhere to the same standards, with the prime contractor acting as the sponsoring authority.

3. The National Industrial Security Program Operating Manual (NISPOM), 32 CFR Part 117 is the authoritative manual concerning baseline standards for the protection of classified information in connection with classified contract and activities under the National Industrial Security Program. The contractor shall comply with: DoDD 5205.07, Special Access Program Policy, 1 Jul 10, w/Chg 2, 4 Feb 20; DoDI 5200.02, DoD Personnel Security Program, 21 Mar 14, w/Chg 3, 24 Sep 20; DoDI 5205.11, Management, Administration and Oversight of DoD Special Access Programs, 6 Feb 13, w/Chg 2, 4 Feb 20; DoDI 8510.01, Risk Management Framework for DoD Information Technology (IT), 12 Mar 13, w/Chg 2, 28 Jul 17;

DoD Joint Special Access Program Implementation Guide (JSIG), 11 Apr 16;

8 | P a g e

UNCLASSIFIED

DoDM 5205.07, Vol 1, DoD SAP Security Manual: General Procedures, 18 Jun 15, w/Chg 2, 30 Sep 20; DoDM 5205.07, Vol 2, SAP Security Manual: Personnel Security, 24 Nov 15, w/Chg 2, 30 Oct 20; DoDM 5205.07, Vol 3, SAP Security Manual: Physical Security, 23 Apr 15, w/Chg 3, 8 Dec 20; DoDM 5205.07, Vol 4, SAP Security Manual: Marking, 10 Oct 13, w/Chg 2, 8 Sep 20; DoDM 5205.07. Vol 3_AFMAN16-703, Vol 3, DoD SAP: Physical Security, 23 Apr 15, w/Chg 1, 21 Sep 15; AFI 16-701, Management, Administration, and Oversight of SAPs, 18 Feb 14;

DoDM 5200.01, Vol 1, DoD Information Security Program: Overview, Classification, & Declassification, 24 Feb 12, w/Chg 2, 28 Jul 20; DoDM 5200.01, Vol 2, DoD Information Security Program: Marking of Classified Information, 24 Feb 12, w/Chg 4, 28 Jul 20; DoDM 5200.01, Vol 3, DoD Information Security Program: Protection of Classified Information, 24 Feb 12, w/Chg 3, 28 Jul 20; DoDI 5200.48, Controlled Unclassified Information (CUI), 6 Mar 20; DoDM 5200.02/AFMAN 16-1405, Air Force Personnel Security Program, 1 Aug 18; DoDM 5400.07-Air Force Manual 33-302, DoD Freedom of Information Act (FOIA) Program, 27 Apr 18; AFMAN 14-403, Sensitive Compartmented Information Security and Intelligence, Surveillance, and Reconnaissance Systems Cybersecurity and Governance, 3 Sep 19. Supersession of any of the above documents will not require immediate revision of this DD Form 254. The updated document will be deemed to be on contract as of the date of supersession.

Additional costs incurred due to updated guidance will be brought to the attention of the GCO immediately.

4. Controlled Unclassified Information: The Contractor shall identify, mark, and handle Controlled Unclassified Information (CUI) according to applicable laws, regulations, and policies IAW DoDI 5200.48. This includes identifying decontrol requirements, safeguarding requirements, destruction methods, access / dissemination controls, incident reporting procedures, and implementation guidelines.

3.6.1 Operations Security (OPSEC)

The Contractor shall implement OPSEC measures to protect sensitive unclassified information. The Contractor shall not confirm, deny, or forward classified information appearing in the media via unclassified channels.

• Public Release of Information Request: The Contractor shall submit public release requests to the designated Public Affairs Point of Contact, following the established Clearance Request process.

9 | P a g e

UNCLASSIFIED

3.7 Cybersecurity

1. Cybersecurity Program Foundation: The Contractor shall establish and maintain a comprehensive cybersecurity program that addresses the engine, its components, subsystems, supporting systems, design and development networks, and test facilities across all contract phases. This program shall align with industry best practices and applicable government standards (e.g., NIST Cybersecurity Framework, DFARS 252.204-7012).

2. Integration with Systems Engineering: The Contractor shall integrate cybersecurity considerations into the Systems Security Engineering (SSE) process, program protection planning, and design processes, treating cybersecurity as an integral aspect of system functionality and safety.

3. Requirement-Driven Security: Cybersecurity requirements shall be architected, designed, implemented, and tested using the same rigor and processes applied to all other program requirements. This includes defining specific, measurable, achievable, relevant, and time-bound (SMART) cybersecurity requirements.

4. Vulnerability Management: The Contractor shall proactively identify, document, and manage cybersecurity requirement gaps, threats, and vulnerabilities. This includes developing and implementing mitigation plans with clear milestones and reporting progress to the Government.

5. Collaboration and Government Oversight: The Contractor shall collaborate with the Government to prioritize and implement security controls and participate in periodic security reviews and audits.

4.0 Additional Information

4.1 Intellectual Property

The preferred approach for data rights is unlimited use, modification, reproduction, release, performance, display, and disclosure. Deliverables shall be provided according to the data rights specified at the DO/TO level.

4.2 Exclusivity Agreements

The Contractor shall not require exclusivity agreements that could restrict further activity at the DO/TO level.

4.3 Data

4.3.1 Data Management

The Contractor shall submit all Contract Data Requirement List (CDRL) documentation through electronic media and ensure adequate numbers of personnel possess and utilize

10 | P a g e

UNCLASSIFIED

the Government’s propulsion security data delivery tool (i.e., PCOL+) as authorized by the Government Contracting Officer to ensure task traceability and facilitate team awareness of activity. The Contractor shall ensure the requirements and restrictions of the SOW are flowed down to vendors and subcontractors.

4.3.2 Data Accession List

The Contractor shall maintain and deliver a list of all data to be generated during the performance of the contract. CDRL A030, DI-MGMT-81453C, Data Accession List (DAL)

4.3.3 Technical Orders (TOs)

The Contractor shall deliver source data for incorporating Propulsion System unique technical data contents into existing Government organizational, intermediate and depot level TOs to include the illustrated parts breakdown. Specific requirements will be defined at the DO/TO level.

4.3.4 Digital Enterprise

The Contractor shall deliver data and information that will enable and enhance the Government’s continued organic sustainment activities for the Propulsion System throughout the engine lifecycle, to include digital thread and digital twin technology areas.

“The Contractor may be required to deliver models, drawings, and data that will be utilized by the Government and the Contractor in fulfillment of the Department of Defense (DoD) Digital Engineering Strategy goals.

4.4 Data Rights

All technical data delivered under this contract will be subject to the data rights provisions of FAR Part 27 and DFARS Subparts 227 and 227.71, which outlines various rights the government can obtain, and defines the terms under which contractors provide data and software. All technical data delivered under this contract will be subject to the provisions in DFARS 252.227-7013, DFARS 252.227-7037, and DFARS 252.227-7014/7019, which outlines the marking of technical data and the Government’s rights to challenge the validity of any asserted restrictions on technical data. The Government intends to acquire data rights for the majority of solutions developed under this contract, whether commercial or non-commercial. Specific data rights and CDRL requirements will be defined at the DO/TO level. The Government intends to include H-clauses for future data that do not conform to the appropriate markings. More specific details on requirements will be provided at the DO/TO level.

11 | P a g e

UNCLASSIFIED

5.0 Applicable Documents (not all-inclusive)

1. AFMC Guiding Principles for Fair Opportunity Selection Under Federal

Acquisition Regulation (FAR) 16.505(b)(1)

2. AFMAN 20-116, Propulsion Life Cycle Management for Aerial Vehicles, 15

January 2025

3. Department of Defense Instruction 5200.48, Controlled Unclassified

Information (CUI), 6 March 2020

4. Executive Order 13556, Controlled Unclassified Information, 4 Nov 2010

5. Code of Federal Regulations Title 32, Part 2002 – CUI, 14 Sept 2016

6. Department of Defense Product Support Management Guidebook, 24 May

7. MIL-HDBK-61B Configuration Management Guidance, 7 Apr 2020

8. 15288.1-2014 IEEE Standard for Application of Systems Engineering on

Defense Programs, 10 Dec 2014

9. MIL-HDBK-516C Airworthiness Certification, 7 October 2019

10. DAFI 63-113 Technology and Program Protection to Maintain Technological

Advantage, 17 October 2024_supercedes AFPAM 63-113

11. DODI 2040.03, End Use Certificates (EUCs), 15 July 2020

12. DODI 3000.09, Autonomy in Weapon Systems, 25 January 2023

13. DODD 3150.01, Joint DoD –Department of Energy/National Nuclear Security

Administration (DoD-DOE/NNSA) Nuclear Weapon Life Cycle Activities, 4 August 2016

14. DODI 4151.18, Maintenance of Military Materiel, 30 August 2024

15. DODD 4275.5, Acquisition and Management of Industrial Resources, 31

August 2018

16. DODD 4400.01E, Defense Production Act Programs, 31 August 2018

17. DODD 5000.01, The Defense Acquisition System, 28 July 2022

18. DODD 5000.71, Rapid Fulfillment of Combatant Commander Urgent

Operational Needs, 18 October 2022

19. DODI 5000.66, Defense Acquisition Workforce Education, Training, Experience, and Career Development Program, 25 March 2022

20. DODI 5010, Intellectual Property (IP) Acquisition and Licensing, 16 October

21. DODD 5134.09, Missile Defense Agency (MDA), 25 April 2025

22. DODD 5200.47E, Anti-Tamper (AT), 28 August 2017

23. DODI 5000.02, Operation of the Adaptive Acquisition Framework, 8 June 2022

24. AFI 33-360, Publications and Forms Management, 15 February 2018

25. AFMAN 33-363, Management of Records, 31 May 2019

12 | P a g e

UNCLASSIFIED

26. AFPD 10-9, Lead Command Agent Designation and Responsibilities for United States Air Force Weapon Systems, Non-Weapon Systems, and Activities, 25 May 2021

27. AFI 10-601, Operational Capability Requirements Documentation and Validation, 27 April 2021

28. AFPD 99-1, Test and Evaluation, 20 June 2018

29. AFRLI 61-103, Scientific/Research and Development, 05 October 2020

30. DAFI 63-101/20-101, Integrated Life Cycle Management, 23 October 2024

31. AFMCI 63-1201, Integrated Life Cycle Systems Engineering and Technical

Management, 02 December 2022

32. AFI 65-503, US Air Force Cost and Planning Factors, 13 July 2018

33. DODI 5000.89, DAFI 99-103, Capabilities-Based Test & Evaluation, 07 March

34. AFI 91-202, The U.S. Air Force Mishap Prevention Program, 22 February 2023

35. AS6500, Manufacturing Management Program, 05 August 2021

36. DoD IMP and IMS Preparation and Use Guide, May 2023

37. DoD Risk Issues and Opportunities (RIO) Management Guide for Defense

Acquisition Programs, September 2023

38. FAR 52.245-01, Government Property, September 2021

39. MIL-STD-3024, Propulsion System Integrity Program (PSIP), 13 July 2015

40. MIL-STD-882E, DoD Standard Practice for System Safety, 27 September

41. NIST Special Publication 800-171 r3, Protecting Controlled Unclassified

Information in Nonfederal Information Systems and Organizations, May 2024

42. PCoE BP-02-13, Engine Trending and Diagnostics, 15 August 2012

43. PCoE BP-06-24B, Propulsion Systems Modification Management Process, 6

Apr 2009

44. PCoE BP-99-04C, Reliability Centered Maintenance, 1 September 2010 PCOE

BP-99-06, Aircraft Gas Turbine Engine Flight Safety Risk Management Process, 12 Feb 2014

45. PCoE BP 99-06E, Aircraft Gas Turbine Engine Flight Safety Risk Management Process, 1 March 2016

3.7 Cybersecurity

5.0 Applicable Documents (not all-inclusive)