DRAFT - APD_ APAC MAC IDIQ SOW.pdf

DRAFT DRAFT DRAFT

1 | P a g e

CUI

United States Air Force Life Cycle Management Center

Propulsion Directorate

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

Indefinite Delivery Indefinite Quantity (IDIQ)

APAC MAC IDIQ

Draft Statement of Work (SOW)

Contract Number TBD

21 May 2025

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and U.S. DoD Contractors only; Critical Technology, 10 October 2024. Other requests shall be referred to AFLCMC/LP Security Office.

WARNING – This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App 2401 et seq.).

Violation of these export laws are subject to severe criminal penalties. Dissemination in accordance with provisions of DoD Directive 5230.25.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the plan.

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 Cyber Security

4.0 Additional Information

4.1 Intellectual Property

4.2 Exclusivity Agreements

4.3 Data Rights

4.4 Data

4.4.1 Data Management

4.4.2 Data Accession List

4.4.3 Technical Orders(TOs)

4.5.4 (Option) Digital Enterprise

5.0 Applicable Documents (not all-inclusive)

3 | P a g e

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, and c) advance new technologies and system concepts that provide evolutionary, revolutionary, and disruptive capabilities for the United States Air Force and strategic partners. The contract aims to enable 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. Assembly and Integration

5. Production and Fielding

6. Operations and Sustainment (O&S)

7. Modernization

8. Prototyping

9. Experimentation

10. Assessments, Demonstrations, and Testing of Prototypes

11. Hardware and Software Modifications

12. Propulsion Design

13. Modeling and Simulation

14. 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).

4 | P a g e

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.

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-level maintenance 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.

5 | P a g e

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:

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:

6 | P a g e

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.

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 to demonstrate that engineering designs and development are complete, risks are deemed acceptable by the Government, and that the system/capability performs as required. The Contractor shall assess, plan, and execute test and evaluation activities, as defined at the DO/TO level.

Example tasks include, but not limited to:

1. Plan and execute development, test, and evaluation (DT&E) activities to include but not limited to uninstalled/installed ground test and flight test.

2. Plan and execute operational, test, and evaluation (OT&E) activities. to include but not limited to installed ground test and flight test.

3. Develop, deliver and execute detailed test plans with supporting information sheets to support development test objectives via various artifacts to include but not limited to components, rigs, prototypes and product demonstrators.

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.

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

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

7 | P a g e

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 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 DD254.

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 Form 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:

a. DoDM 5200.01, Vol 1, DoD Information Security Program: Overview, Classification, & Declassification, 17 Jan 2025

b. DoDM 5200.01, Vol 2, DoD Information Security Program: Marking of Classified Information, 28 Jul 2020

8 | P a g e

c. DoDM 5200.01, Vol 3, DoD Information Security Program: Protection of Classified Information, 17 Jan 2025

d. DoDI 5200.02, DoD Personnel Security Program (PSP), 24 Sep 2020

e. DoDM 5200.02, Procedures for the DoD Personnel Security Program (PSP, 29 Oct 2020

f. DoDI 5205.11, Management, Administration and Oversight of DoD Special

Access Programs, 12 Sep 2024

g. DoDM 5205.07, Special Access Program Security Manual, 17 Jan 25

h. DoDM 5205.07, Vol 4, SAP Security Manual: Marking, 08 Sep 2020

i. DAFI 16-701, DAF Guidance Memorandum to DAFI, 16-701, Management, Administration, and Oversight of SAPs, 15 Feb 2023

j. DoDI 5200.48, Controlled Unclassified Information (CUI), 06 Mar 2020

k. DoDD 5400.07, DoD Freedom of Information Act (FOIA) Program, 05 Apr

l. DoDM 5400.07_ Air Force Manual 33-302, Freedom of Information Act

Program, 27 Apr 2018

m. DoDI 8510.01, Risk Management Framework for DoD Systems; 19 Jul 2022

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

o. 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 the 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 Contracting Officer immediately.

4. Controlled Unclassified Information: The Contractor shall identify, mark, and handle CUI according to applicable laws, regulations, and policies (see Table 2 – References 1, 2, 3). 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.

9 | P a g e

• 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.

3.7 Cyber Security

1. The Contractor shall develop and implement cybersecurity protection measures for the engine, its components, subsystems, supporting systems, design and development networks, and test facilities throughout all phases of the contract. The Contractor shall work with the Government to prioritize and implement additional security controls.

2. The Contractor shall integrate cybersecurity into Systems Security Engineering (SSE), program protection, and design processes.

3. The Contractor shall architect, design, implement and test cybersecurity requirements in the same manner as all other program requirements.

4. The Contractor shall identify known cybersecurity requirement gaps, threats, and vulnerabilities along with milestones for mitigation.

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 delivery/task order level.

4.3 Data Rights

The Contractor shall identify, document, compile, reproduce, and deliver all technical data and computer software (binaries, source code, software documentation, and software tools) as required by individual DOs/TOs. This effort may include up to Production Level Technical Data Packages (TDPs) to support competitive sustainment. All technical data must indicate asserted rights IAW DFAR Part 227. The Contractor shall provide a TDP that reflects the final product baseline as required by individual Order. The TDP Option Selection Worksheet shall completed for each effort and shall be used to provide the Contractor with the appropriate information to provide for each requested TDP.

10 | P a g e

License rights of intellectual property including technical data includes any recorded information of a scientific or technical nature (e.g., product design or maintenance data, computer databases, and computer software documentation), and computer software including executable code, source code, code listings, design details, processes, flow charts, and related material.

The Contractor shall provide unlimited rights for Form, Fit, Function (FFF) and Operations, Maintenance, Installation, and Training (OMIT) data.

4.4 Data

4.4.1 Data Management

The Contractor shall submit all Contract Data Requirement List (CDRL) documentation through electronic media. The Contractor shall ensure adequate numbers of personnel possess and utilize 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.4.2 Data Accession List

The Contractor shall maintain and deliver a list of all data to be generated during the performance of the contract.

4.4.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.

4.5.4 (Option) 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 shall deliver previously developed, existing models, drawings, and data, excluding Contractor proprietary data (e.g. special manufacturing processes, process controls) that will be utilized by the Government and the Contractor in fulfillment of the Department of Defense (DoD) Digital Engineering Strategy goals.

11 | P a g e

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. DODD 5134.09, Missile Defense Agency (MDA), 25 April 2025

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

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

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

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

25. AFPD 10-9, Lead Command Agent Designation and Responsibilities for United

States Air Force Weapon Systems, Non-Weapon Systems, and Activities, 25 May 2021

12 | P a g e

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

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

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

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

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

Management, 02 December 2022

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

32. DODI 5000.89_DAFI 99-103, Capabilities-Based Test & Evaluation, 07 March

33. AS6500, Manufacturing Management Program, 05 August 2021

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

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

Acquisition Programs, September 2023

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

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

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

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

Information in Nonfederal Information Systems and Organizations, May 2024

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

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

Apr 2009

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

BP-99-06,

43. Aircraft Gas Turbine Engine Flight Safety Risk Management Process, 12 Feb

44. PCoE BP 99-06E, Aircraft Gas Turbine Engine Flight Safety Risk Management

Process, 1 March 2016

3.7 Cyber Security

5.0 Applicable Documents (not all-inclusive)