(CUI) C-130H FPS SOW v4 - 8 May 2026.pdf

CUI

DA

STATEMENT OF WORK (SOW)

FOR

C-130H FORMATION POSITIONING SYSTEM (FPS)

ENGINEERING AND MANUFACTURING DEVELOPMENT (EMD)

AND PRODUCTION & DEPLOYMENT (P&D) SUPPORT

FAXXXXXXXX

Version 2.0

XX May 2026

PREPARING ORGANIZATION:

AFLCMC/MOBILITY DIRECTORATE

C-130 HERCULES DIVISION

C-130H LEGACY AVIONICS BRANCH

WRIGHT-PATTERSON AFB OH 45433-7233

Controlled by: AFLCMC

Controlled by: AFLCMC/WLNM CUI Category: General Procurement, Acquisition, and Controlled Technical Information Distribution Statement D: Distribution authorized to the Department of Defense (DoD) and U.S. DoD contractors only, acquisition sensitive, 30 April 2026.

Other requests shall be referred to Air Force Life Cycle Management Center (AFLCMC) C-130H Branch, AFLCMC/WLNM, Wright-Patterson AFB, OH POC: Mrs. Danielle Weeks, danielle.weeks@us.af.mil

TABLE OF CONTENTS

1.0 SCOPE AND BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 REQUIREMENTS

3.1 PROGRAM MANAGEMENT (PM)

3.1.1 Integrated Master Plan (IMP)/Integrated Master Schedule (IMS)

3.1.2 Risks, Issues, & Opportunities Management Plan (RIOMP)

3.1.3 Reviews

3.1.3.1 Kick-Off Meeting

3.1.3.2 Program Management Reviews

3.1.3.3 Risk Review Board

3.1.3.4 Technical Interchange Meetings

3.1.4 Monthly Status Reports

3.1.5 Small Business Subcontracting Report

3.2 Security Requirements

3.2.1 Data Protection

3.2.2 Controlled Unclassified Information (CUI)

3.2.3 Operations Security (OPSEC)

3.2.4 Security Incidents and Violations

3.2.5 Security Education

3.2.6 Physical Security

3.2.7 Safeguarding Covered Defense Information and Cyber Incident Reporting

3.2.8 Pass and Identification

3.3 General Requirements

3.3.1 Sustainable Procurement Program (SPP)

3.3.2 Travel

3.4 BUSINESS MANAGEMENT

3.4.1 Contract Work Breakdown Structure (CWBS)

3.4.2 Integrated Performance Measurement:

3.4.3 Over Target Baseline Restructure:

3.4.4 Associate Contractor Agreement (ACA)

3.5 Configuration and Data Management

3.5.1 Configuration Management

3.5.2 Data Management

3.5.2.1 Licenses

3.6 Diminishing Manufacturing Sources and Material Shortages Management (DMSMS) Program

3.6.1 DMSMS Implementation Plan

3.6.2 DMSMS Notification and Impact Assessment

3.6.3 Diminishing Manufacturing Sources and Material Shortages Health Assessment

3.6.4 Diminishing Manufacturing Sources and Material Shortages Resolution

3.6.5 Diminishing Manufacturing Sources and Material Shortages

4.0 ENGINEERING MANUFACTURING DEVELOPMENT (EMD)

4.1 SYSTEMS ENGINEERING

4.1.1 Technical Management

4.1.1.1 Specification Management

4.1.1.2 Systems Engineering Management Plan (SEMP)

4.1.1.3 Technical Reviews

4.1.2 Metrics

4.1.2.1 Deficiency Reporting

4.1.3 Systems Requirements and Analysis

4.1.3.1 System/Subsystem Specification (S/SS) and System/Subsystem Design Description (SSDD)

4.1.3.2 Requirements Management Database

4.1.3.3 Interface Control Document (ICD) and Integration

4.1.3.4 TCAS Integration

4.1.3.5 Modular Open Source Approach (MOSA)

4.1.3.6 Model Based Systems Engineering

4.1.3.7 Modeling and Simulation

4.1.3.8 Analyses and Integration

4.1.4 Software Development

4.1.4.1 Software Development Program

4.1.4.2 Software Deliverables

4.1.4.3 Reserve Capacity Requirements

4.1.4.4 Software Data Rights

4.1.4.5 Cyber Resiliency

4.1.4.6 Firmware Development Plan

4.1.5 Manufacturing and Quality

4.1.5.1 Manufacturing Management Program

4.1.5.2 Quality Management System Requirements

4.1.5.3 Manufacturing Readiness Levels and Assessments

4.1.5.4 Quality and Manufacturing Metrics

4.1.5.5 First Article Inspection

4.1.5.6 Government-Industry Data Exchange Program

4.1.5.7 Tooling and Special Test Equipment

4.1.6 Reliability & Maintainability (R&M)

4.1.6.1 Reliability and Maintainability Program Plan

4.1.6.2 Reliability and Maintainability Allocations and Predictions

4.1.6.3 Reliability Model

4.1.6.4 Failure Modes, Effects, & Criticality Analysis

4.1.6.5 Failure Reporting, Analysis, and Corrective Action System

4.1.6.6 Failure Modes and Effects Testing

4.1.6.7 Aviation Critical Safety Items

4.1.6.8 Safety Critical Function Thread Analysis

4.1.6.9 Safety Interlock Analysis and Test

4.1.7 Engineering Data

4.1.7.1 Technical Data Package

4.1.7.2 Engineering Data Guidance Conference

4.1.7.3 In-Process Review (IPR) of the TDP

4.1.7.4 Engineering Data Updates and Revisions

4.1.8 System Security Engineering

4.1.8.1 Program Protection Implementation Plan

4.1.8.2 Counterfeit Parts - Counterfeit Prevention Plan

4.1.8.3 Cybersecurity Support

4.1.8.4 Software Assurance

4.1.8.5 Systems Security Working Groups

4.1.8.6 Radio Frequency Assignments

4.1.8.7 Spectrum Management Support

4.1.8.8 Communication, Navigation, Surveillance/Air Traffic Management (CNS/ATM)

4.1.8.9 Software Bill of Materials

4.1.9 Airworthiness Program

4.1.9.1 Airworthiness Certification Plan

4.1.9.2 Certification Basis and Compliance Report

4.1.9.3 Experimental Flight Release Basis

4.1.10 Human Systems Integration (HSI)

4.1.10.1 HSI Program

4.1.10.2 HSI Working Group (HSIWG)

4.1.10.3 Crew Station Working Group (CSWG)

4.1.10.4 Human Engineering Design Approach Document-Maintainer

4.1.11 Environment, Safety, and Occupational Health (ESOH)

4.1.11.1 Hazardous Material Management

4.1.11.2 System Safety

4.1.12 Systems Integration Lab

4.1.12.1 EMD Systems Integration Lab

4.1.13 Electromagnetic (EM) Environmental Effects (E3)

4.1.13.1 E3 Analysis and Verification

4.1.14 Environmental Verification

4.1.15 Design and Construction

4.1.15.1 Wiring

4.1.15.2 Materials and Processes

4.1.15.3 Parts Selection

4.1.16 Kit Installations

4.1.16.1 Trial Kit Installations

4.1.16.2 Verification Kit Installations

4.1.17 EMD Interim Contractor Support (ICS)

4.2 TEST & EVALUATION

4.2.1 Integrated Testing

4.2.2 Test Planning

4.2.3 Development Test/Operational Test Support

4.2.4 Common Test and Evaluation Data Repository

4.2.5 Contractor Reports

4.2.5.1 Developmental Test/Operational Test Reports

4.2.5.2 Engineering Verification Report

4.2.5.3 Problem Reports

4.2.5.4 Deficiency Report and Watch Item Review

4.2.6 Developmental Test/Operational Test Maintenance Support

4.2.7 Production-Representative Configurations

4.2.8 Operational Test & Evaluation (OT&E)

4.2.9 Spares and Peculiar Support Equipment (PSE)

4.2.10 Acceptance Test Plan

4.3 LOGISTICS

4.3.1 Technical Orders/Time Compliance Technical Order

4.3.1.1 Technical Orders

4.3.1.2 Time Compliance Technical Order

4.3.1.3 Technical Publications

4.3.1.4 Delivery

4.3.2 Item Unique Identification

4.3.3 Supply System

4.3.3.1 Provisioning

4.3.3.2 Support Equipment

4.3.4 Packaging, Handling, Storage, and Transportation

4.3.5 Government Furnished Property

4.3.5.1 Management and Reporting

4.4 INTEGRATED TRAINING SYSTEMS

4.4.1 Training System Requirements Analysis (TSRA)

4.4.2 Type 1 Training

4.4.3 Differences/Cadre Training

4.4.4 Aircrew Training System Device Modification

4.4.5 Training Systems Engineering

4.4.6 Analysis and Requirements Development

4.4.7 Training Device Design and Development

4.4.8 Training Device Technical Data Package

4.4.9 Training Device Interface Control Documents

4.4.9.1 Training System Configuration and Data Management

4.4.9.2 Technical Reviews

4.4.9.3 Training Device Delivery and Installation

4.4.9.4 Training Device Test and Evaluation

4.4.9.5 Integrated Logistics Support for Training Systems

5.0 PRODUCTION REQUIREMENTS – LRIP/FRP (OPTION)

5.1 KIT PRODUCTION AND AIRCRAFT MODIFICATION

5.1.1 Kit Production and Delivery

5.1.2 Kit Packaging Requirements

5.1.3 Kit Management

5.1.4 Kit Installation and Aircraft Acceptance

5.1.5 Peculiar Support Equipment

5.1.6 Tooling/ and Special Test Equipment

5.1.6.1 Tooling

5.1.6.2 Special Test Equipment

5.2 PRE-INDUCTION SURVEYS

5.2.1 Aircraft Surveys

5.2.1.1 Preparation for Surveys

5.2.1.2 Survey Timelines

5.2.1.3 Tail Number Specific Supplemental Kit Design

5.3 AIRCRAFT INDUCTION

5.3.1 Aircraft Inspection and Handling

5.4 AIRCRAFT KIT INSTALLATION

5.4.1 Aircraft Records

5.4.2 Maintenance Information Systems

5.4.3 Aircraft Checkout

5.4.3.1 Acceptance Testing

5.4.3.2 Weight and Balance

5.4.3.3 Government Acceptance Documentation

5.5 OVER and ABOVE

5.6 SYSTEMS ENGINEERING

5.6.1 Sustaining Engineering

5.6.2 Support for Kit Install and Checkout

5.6.3 Vendor/Supplier Support

5.6.4 Airworthiness Certification Support

5.6.4.1 Memorandum of Airworthiness

5.6.4.2 Certification Working Group (CERTWG)

5.6.5 Manufacturing and Quality

5.6.5.1 Manufacturing Management Program

5.6.5.2 Quality and Manufacturing Metrics

5.6.5.3 Failure Reporting, Analysis, and Corrective Action System

5.6.6 Environmental, Safety, and Occupational Health

5.6.6.1 Environmental, Safety, and Occupational Health Management

5.6.6.2 Hazardous Material Management

5.6.6.3 Environmental, Safety, and Occupational Health Hazards

5.6.7 System Safety

5.6.7.1 System Safety Program Plan

5.6.7.2 Safety Assessment Report

5.6.8 System Security

5.6.8.1 Program Protection Implementation Plan

5.6.8.2 Counterfeit Parts Counterfeit Prevention Plan

5.6.8.3 Architecture Analysis Report

5.6.9 Software Sustainment

5.7 LOGISTICS SUPPORT

5.7.1 Technical Orders

5.7.2 Logistics Support Representative

5.7.3 Interim Contractor Support (ICS)

5.7.4 Contractor - Inventory Control Point (C-ICP) and Source of Supply

5.7.5 Supply Phase-Out Services

5.7.6 Initial Spares

5.8 AIRCREW TRAINING SYSTEM DEVICE MODIFICATION

5.8.1 Training System Engineering

5.8.2 Training Device Integration

5.8.3 Training System Configuration and Data Management

5.8.4 Technical Reviews

5.8.5 Training Device Delivery and Installation

5.8.6 Training Device Test and Evaluation

5.8.7 Integrated Logistics Support for Training Systems

5.8.8 Integrated Contractor Support for Training Systems

6.0 Attachment 1: Acronyms

1.0 SCOPE AND BACKGROUND

This SOW establishes the requirements for the C-130H Formation Positioning System (FPS) modification of up to 54 C-130H3 aircraft and up to 7 C-130H flight training devices. This effort includes both the Engineering and Manufacturing Development (EMD) and Production and Deployment (P&D) acquisition phases.

The United States Air Force (USAF) must replace the C-130H FPS to address Diminishing Manufacturing Source (DMS) issues as well as operating frequency interference from commercial fifth generation (5G) signals. The Original Equipment Manufacturer (OEM) no longer manufactures current C-130H FPS equipment due to DMS issues, and the auction of Radio Frequency (RF) spectrum to the 5G industry constrains C-130 formation training and operations until the current systems are replaced and fielded.

The operational deficiency and need created by the 5G frequency interference is captured in the Modification Proposal, Form 1067, titled “Station Keeping Equipment (SKE) Vacate 5G Frequencies.” It states, “The United States Government (USG) offered industry full access to the 3450-3550 MHz frequency band for 5G wireless operation within the contiguous United States (US), but at reduced power levels in certain areas (Cooperative Planning Areas) to avoid C-130 operations interruption. This transition impacts two of the four SKE frequencies. Cooperative Planning Areas are only a temporary solution. Air Mobility Command (AMC) needs a long-term solution for C-130 aircraft to vacate the 3450-3550 MHz frequency band but still perform SKE operations. The current SKE system is also experiencing concerns with viability due to ongoing Diminishing Manufacturing Sources (DMS) issues. Currently AFSC estimates parts availability to become a concern by FY31.”

This modification enables the C-130H to operate in the future safely and effectively. Since no long-term FPS solution exists for all domains where 5G exists, C-130H3 aircraft cannot provide all-weather capability for the Global Response Force. FPS is also a requirement for safe aircraft formation operations in Instrument Meteorological Conditions. The next FPS solution must work in all C-130H3 aircraft deployment environments with full 5G capability. C-130H FPS replacement equipment must be interoperable with the FPS solution currently being worked for the C-130J fleet.

The EMD phase will include:

1. Design, integration, qualification, ground and flight test, production and installation of three (3) trial kits

2. Training development

3. Technical Data Package (TDP) [Technical Order (TO) changes, Time Compliance

Technical Orders (TCTO), engineering/installation drawings] development and delivery

4. Certification/Verification

5. Initial spares determination

6. ICS of the EMD aircraft

7. Support Equipment (SE) identification on the C-130H

8. Tooling required for install and repair

The P&D phase will follow the EMD phase activities. It will include:

1. Production of up to 51 kits for the C-130H aircraft

2. Contractor Field Team (CFT) installation on up to 51 aircraft

3. Providing Type 1 and installation training

4. Initial spares

5. SE deployment

6. Updates for 5 Weapon System Trainers (WSTs)

7. Training courseware updates

8. ICS for sustainment of the FPS system after installation during the contract period of performance

2.0 APPLICABLE DOCUMENTS

The following documents form a part of this SOW to the extent specified herein. If no version is specified, then the version current at the time of SOW release for Request for Proposal will apply.

The requirements of any document referenced within this SOW, but omitted herein, remain applicable.

42 US Code, National Environmental Policy Act, 7 July 2023 Air Force (AF)

Air Force Instruction (AFI) 10-701 OPERATIONS SECURITY (OPSEC), 9 June 2020

AFI 17-101, Risk Management Framework for Air Force Information Technology, 6 February

AFI 17-101_Department of the Air Force Guidance Memorandum (DAFGM)2024-01, Risk Management Framework (RMF) For Department of the Air Force Information Technology (IT), 5 September 2024

AFI 90-802, RISK MANAGEMENT, 1 April 2019

Department of the Air Force Instruction (DAFI) 17-220, Spectrum Management, 8 June 2021

DAFI 63-101/20-101_DAFGM2024-01, Integrated Life Cycle Management, (16 February 2024 with 23 October 2024 GM)

Air Education and Training Command Instruction (AETCI) 36-2651, Air Force Training Program 28 February 2025

DAFI 62-601, United States Air Force (USAF) Airworthiness, 10 June 2022

Department of Defense Instruction (DoDI) 5000.89_DAFI 99-103, Capabilities Based Test and Evaluation, 28 February 2025

Air Force Life Cycle Management Center (AFLCMC) Standard Process for Platform Information Technology (PIT) Certification & Accreditation (C&A), Version 3.4, 20 October 2022

AFLCMC Standard Process for Life Cycle Risk & Issue Management in Acquisition and

Sustainment Programs, 19 September 2024

Air Force Manual (AFMAN) 11-231, Flying Operations, Computed Air Release Point Procedures, 18 November 2020

Department of the Air Force (DAF) part 04, Notification of Government Security Activities, July

DAF part 42, Contractor Access to Air Force Installations, 7 July 2023

DAF part 42, Common Access Cards (CAC) for Contractor Personnel, 12 July 2024

Department of the Air Force Manual (DAFMAN) 23-119, Government Furnished Property (GFP), 05 April 2022

DAFMAN 63-119, Mission-Oriented Test Readiness Certification, 15 April 2021

Department of the Air Force Pamphlet (DAFPAM) 63-128, INTEGRATED LIFE CYCLE MANAGEMENT, 3 February 2021

DAFPAM 90-803, RISK MANAGEMENT (RM) GUIDELINES AND TOOLS, 23 March 2022

Air Force Materiel Command Instruction (AFMCI) 20-105 Diminishing Manufacturing Sources and Material Shortages (DMSMS), 12 July 2022

AFMCI 23-101, Air Force Provisioning, 8 August 2013

Air Force Materiel Command (AFMC) Manual 20-106, Provisioning, 11 August 2023

Air Force Manual (AFM) 36-2234, Instructional System Development, 1 November 1993

Air Force Policy Directive (AFPD) 62-6, USAF Airworthiness, 16 January 2019

Airworthiness Determination Form, ADF-516C

American Society for Testing and Materials (ASTM) D3951-10, Standard Practice for Commercial Packaging, 15 August 2010

AS9100C, Quality Management Systems, 1 January 2009

C-130H FPS System Requirements Document (SRD) Draft, v4.0, 31 Mar 2026

C-130 SUSTAINMENT MODIFICATION MANAGEMENT PLAN (MMP) 31 December 2024

Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6510.01F, 9 February 2011

COMMISSION IMPLEMENTING REGULATION EUROPEAN UNION (EU) No 1028/2014 of 26 September 2014; amending Implementing Regulation (EU) No 1207/2011 laying down requirements for the performance and the interoperability of surveillance for the single European sky Committee on National Security Systems Instruction (CNSSI) 1253, Security Categorization and Control Selection for National Security Systems, 27 March 2014

DI‑MGMT-82001A/T, DOD RISK MANAGEMENT FRAMEWORK (RMF) PACKAGE

DELIVERABLES

Defense Contract Management Agency (DCMA) Instruction (INST) 8210.1C, Contractor’s Flight and Ground Operations, 21 August 2013

Revolutionary Defense Federal Acquisition Regulation Supplement (R-DFARS) Part 245 – Government Property

DO-178C, Software Considerations in Airborne Systems and Equipment Certification, 31 December 2011

Department of Defense (DoD) 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), February 2006, Incorporating Change 2 as of 18 May 2016

DoD 5400.7-R AFMAN 33-302, Freedom of Information Act (FOIA) Program, 27 April 2018

DoD DMSMS SD-22 Guidebook, March 2024

DoD Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide, v0.9, May 2023

Department of Defense Directive (DoDD) 5000.01, THE DEFENSE ACQUISITION SYSTEM, Change 1, 28 July 2022

DoD Instruction (I) 8510.01, Risk Management Framework (RMF) for DoD Information Technology, 19 July 2022

DoD Instruction (DoDI) 5000.77, DoD Federally Funded Research and Development Center (FFRDC) Program, 13 December 2019

DoDI 5000.85, Major Capability Acquisition, 19 August 2022

DoDI 5200.48 CONTROLLED UNCLASSIFIED INFORMATION (CUI), 6 March 2020

DoDI 8500.01, Cybersecurity, 7 October 2019 support analysis

DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Non-Public DoD Information, 9 December 2019

DoD Manual (DoDM) 5200.01, DoD Information Security Program: Overview, Classification, and Declassification, 24 February 2012

DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs, September 2023

Revolutionary FAR Overhaul (RFO) 52.245-1, Government Property, 13 March 2026

Federal Aviation Administration (FAA) Advisory Circular (AC) 90-114A, Automatic Dependent Surveillance-Broadcast Operations, 28 October 2014

Government Electronics & Information Technology Association (GEIA)-Handbook (HB)- 0007A, Logistics Product Data Handbook (HDBK), 10 February 2014

Information Assurance (IA) and Support to Computer Network Defense (CND), 9 June 2015

Military (MIL)-HDBK-516C, Airworthiness Certification Criteria, 12 December 2014

MIL-HDBK-61A, Configuration Management Guidance, 7 February 2001

MIL-HDBK-896, DoD HDBK Manufacturing and Quality Program, Revision A, 25 August 2016

MIL-Standard (STD)-129R Change 3, Military Marking for Shipment and Storage, 25 February

MIL-STD-130N, Change 1, DoD Standard Practice Identification Marking of U.S Military Property, 16 November 2012

MIL-STD-461G DoD Interface Standard: Requirements for the Control of Electromagnetic (EM) Interference Characteristics of Subsystems and Equipment, 11 December 2015

MIL-STD-464 DoD Interface Standard: Electromagnetic (EM) Environmental Effects (E3), Requirements for Systems, 1 December 2010

MIL-STD-46855A, Human Engineering Requirements for Military Systems, Equipment, and Facilities, 24 May 2011

MIL-STD-881F, Work Breakdown Structures for Defense Materiel Items, 13 May 2022

MIL-STD-882E, DoD Standard Practice, System Safety, 27 September 2023

National Aerospace Standard (NAS) 411 3rd Edition, Hazardous Materials Management Program (HMMP), 30 September 2020

NAS 411-1, Hazardous Material Target List, 30 September 2020

National Institute of Standards and Technology (NIST) Special Publication (SP) 800-30, Revision 1, Guide for Conduction Risk Assessment, 1 September 2012

NIST Special Publication (SP) 800-37, Revision 2, Risk Management Framework for

Information Systems and Organizations: A System Life Cycle Approach or Security and Privacy, 1 December 2018

NIST Special Publication (SP) 800-53, Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations, 4 April 2013 (Includes updates as of 22 January 2015)

Notification of Government Security Activity and Visitor Group Security Agreements, March

Revolutionary Federal Acquisition Regulation Overhaul (RFO) 23.4, Pollution Prevention

RFO Part 45, Government Property

SAE AS5553, Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition, 2 April 2009

Technical Order (TO) 1-1A-14, Installation and Repair Practices, Aircraft Electric and Electronic Wiring, 15 September 2009

TO 00-5-16, Software Managers and User’s Manual for the USAF Automated Computer Program Identification Number System (ACPINS), 15 November 2015

United States Air Force (USAF) Airworthiness Bulletin (AWB)-005: Tailored Airworthiness Certification Criteria (TACC)/Modification Airworthiness Certification Document Construction and Format, 27 September 2010

USAF Initial Provisioning Performance Specification (IPPS), 3 September 2013

USAF AWB-013A: Risk Identification and Acceptance for Airworthiness Determinations, 29 June 2011

3.0 REQUIREMENTS

3.1 PROGRAM MANAGEMENT (PM)

The Contractor will exercise comprehensive program management, delineating clear lines of responsibility among organizational units. This clarity ensures disciplined, consistent, and integrated efforts, essential for maintaining overall program equilibrium and control, thus fostering the successful execution of the program. Additionally, the Contractor shall facilitate bi-weekly program status reviews via virtual platforms to ensure timely communication and alignment across all stakeholders. Items to be discussed in the bi-weekly meeting shall include:

• Upcoming short-term and long-term milestones

• Risks/opportunities

• Decisions/approvals needed

• Upcoming deliverables

• Action item review

• IMS overview

• Barriers/obstacles

• Other topics to be included at later dates to be modified via PCOL

3.1.1 Integrated Master Plan (IMP)/Integrated Master Schedule (IMS)

The Contractor shall develop and maintain an IMP and IMS, consistent with the guidance contained in the DoD IMP and IMS Preparation and Use Guide. The contractor shall manage program execution using the IMP and associated IMS as day-to-day execution tools to assess program progress in meeting program requirements. The IMP shall document program events, milestones, and entrance and exit criteria to be executed during the program. The IMP shall be updated when deemed necessary by the Government to reflect program changes.

The IMS shall include all planned events, tasks, resource loading, and milestones from contract award (CA) to the completion of all contracted activities. The Contractor shall report program progress in accordance with (IAW) the IMP at program management reviews, selected technical reviews, and other times as requested by the Government. The Contractor shall develop, submit, and maintain the IMS reflecting the IMP. The IMS shall include activities of the Contractor and its major subcontractors. The Contractor shall perform appropriate analysis of the IMS tasks to report existing/potential problem areas and recommend corrective action(s). (M004, DI-MGMT-

81797, PROGRAM MANAGEMENT PLAN - INTEGRATED MASTER PLAN (IMP); M005,

DI-MGMT-81861C, INTEGRATED PROGRAM MANAGEMENT DATA AND ANALYSIS

REPORT (IPMDAR) – INTEGRATED MASTER SCHEDULE (IMS))

The Contractor shall develop and maintain an IMP and IMS, consistent with the guidance contained in the DoD IMP and IMS Preparation and Use Guide, to allow Government oversight of progress. The contractor’s IMP shall demonstrate that the program is structured to provide a balanced technical approach, to minimize and control risk, to accomplish up-front summary planning and commitment, and to provide a basis for subsequent detailed planning. The IMP shall include program events, milestones entrance/exit criteria and measurable indicators that can be used to evaluate the contractor’s satisfactory progress toward being fully capable of delivering the defined deliverables and services. The IMP shall be updated when deemed necessary by the Government to reflect program changes.

The contractor shall manage program execution using the IMP and associated IMS as day-to-day execution tools to assess program progress in meeting program requirements. The IMS shall be created using a network capable Commercial Off-the-Shelf (COTS) scheduling software application. Unless otherwise provided in the Contract Data Requirements List (CDRL), the IMS shall be delivered electronically in Microsoft Project and the native digital format, e.g., Open Plan BK3 file. The IMS shall include all planned events, tasks, and milestones from CA to the completion of all contracted activities. The Contractor shall develop, submit, and maintain the IMS reflecting the IMP. The IMS shall include activities of the Contractor and its major subcontractors.

The schedule shall be an integrated, logical network-based schedule that correlates to the Contract Work Breakdown Structure (CWBS) and is vertically and horizontally traceable to the cost/schedule reporting instrument used to address variances such as the CPR (if applicable). The schedule shall have a numbering system that provides traceability to the IMP (if applicable) and SOW. It shall contain contractual milestones and descriptions and display summary, intermediate, and detailed schedules, and periodic analysis of progress to date. It shall include fields and data that enable the user to access the information by product, process, or organizational lines.

The Contractor shall report program progress IAW the IMP at program management reviews, selected technical reviews, and other times as requested by the Government. The Contractor shall perform appropriate analysis of the IMS tasks to report existing/potential problem areas and recommend corrective action(s).

3.1.2 Risks, Issues, & Opportunities Management Plan (RIOMP)

The Contractor shall develop, implement, submit, and maintain a RIOMP defining how the Contractor will establish a risk baseline, identify, monitor, mitigate, control, and track program risk. RIOMP shall ensure program management, technical, cost, schedule, and contract risks are identified, analyzed, managed, monitored, and tracked to help achieve program cost, schedule, and performance objectives throughout the life of the FPS program. Refer to the DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs. (M006, DI-MGMT-

81808/T, CONTRACTOR’S RISK MANAGEMENT PLAN)

3.1.3 Reviews

The Contractor shall convene and facilitate both major and minor reviews via virtual platforms (or in-person if directed) throughout the execution of the C-130H FPS Replacement program.

The Contractor shall propose and submit an agenda for all reviews. The Contractor shall provide a preliminary copy of all Contractor material to be presented during the review. The Contractor shall develop and submit minutes for all reviews detailing the review and track Action Items (AIs) generated with resolution status, Points of Contact (POC) identified and recommended closure dates. The Contractor shall submit all final presentation material presented at the review.

(M001, DI-ADMN 81249C, CONFERENCE AGENDA; M002, DI-ADMN-81250C/T,

CONFERENCE MINUTES; M003, DI-ADMN-81373/T PRESENTATION MATERIAL)

3.1.3.1 Kick-Off Meeting

Within 60 calendar days of CA, the Contractor shall host a kick-off meeting, presenting the approach to meeting the cost, schedule, and performance requirements of the contract. The kick-off meeting agenda, minutes, and presentation materials shall be submitted. (M001, DI-ADMN

81249C, CONFERENCE AGENDA; M002, DI-ADMN-81250C/T, CONFERENCE

MINUTES; M003, DI-ADMN-81373/T PRESENTATION MATERIAL)

3.1.3.2 Program Management Reviews

The Contractor shall convene and facilitate Program Management Reviews (PMRs) on a semi-annual basis to present comprehensive program status. The Contractor shall develop and submit a PMR agenda, presentation material, and minutes IAW Section 3.0 Paragraph(s) 3.1.3. As a minimum, the Contractor shall provide all applicable IPMR elements and formats as required by the Contract Line Item Number (CLIN) contract type; AI review, risks, and discuss and resolve http://www.assistdocs.com/search/document_details.cfm?ident_number=277164&StartRow=1&PaginatorPageNumber=1&title=RISK%20MANAGEMENT&status%5Factive=on&search%5Fmethod=BASIC http://www.assistdocs.com/search/document_details.cfm?ident_number=277164&StartRow=1&PaginatorPageNumber=1&title=RISK%20MANAGEMENT&status%5Factive=on&search%5Fmethod=BASIC http://www.assistdocs.com/search/document_details.cfm?ident_number=277164&StartRow=1&PaginatorPageNumber=1&title=RISK%20MANAGEMENT&status%5Factive=on&search%5Fmethod=BASIC program issues. PMRs shall be conducted at Government or Contractor facilities, as determined by the Government. The Contractor shall conduct reviews on short notice when the Government determines a priority situation requires a program review.

3.1.3.3 Risk Review Board (RRB)

The Contractor shall convene and support a quarterly RRB via virtual platform with the Government to review current program risks, potential risks, and identify new risks.

Corresponding risk mitigation activities shall be presented, and minutes shall be submitted for each RRB, detailing a summary of program risks, identifying risk/watch item numbers, titles, descriptions, levels, mitigation plans, and statuses. Individual risk discussions shall also be captured within the RRB minutes. (M001, DI-ADMN-81249C, CONFERENCE AGENDA, M002, DI-ADMN-81250C/T, CONFERENCE MINUTES).

3.1.3.4 Technical Interchange Meetings (TIM)

The Contractor shall participate in a virtual TIM, not to exceed one per month. The Contractor shall propose agendas for all TIMs IAW Section 3.0, Paragraph 3.1.3 and be prepared to lead discussions. The Contractor shall provide a preliminary and final copy of all Contractor briefing material to present during the TIMs IAW Section 3.0, Paragraph 3.1.3. The Contractor shall capture and share the meeting minutes and AIs with identified points of contact and recommended closure dates IAW paragraph 3.1.3. (M001, DI-ADMN 81249C, CONFERENCE

AGENDA; M002, DI-ADMN-81250C/T, CONFERENCE MINUTES; M003, DI-ADMN-

81373/T PRESENTATION MATERIAL)

3.1.4 Monthly Status Reports

The Contractor shall generate a Monthly Status Report (MSR) to include all technical activities completed, in progress, estimated start, current issues and resolution, schedule, travel performed, and other program status items applicable to Contractor, subcontractors, and suppliers’ performance.

Included in the MSR the contractor shall deliver an updated, baseline schedule with a narrative report providing an analysis of schedule health based on the DCMA 14-Point Assessment criteria and detail all baseline changes. Furthermore, it must identify any variances from the baseline exceeding twenty (20) work days, complete with an explanation of their root causes and the corrective actions being implemented. (M007, DI-MGMT-80368A/T, STATUS REPORT-

MONTHLY STATUS REPORT (MSR))

3.1.5 Small Business Subcontracting Report

The Contractor shall develop and submit a Small Business Subcontracting Report IAW Special Contract Provision H001. (M008, DI-MGMT-81642, SMALL BUSINESS SUBCONTRACTOR

REPORT)

3.2 SECURITY REQUIREMENTS

Contractor personnel with access to US Government unclassified information systems, containing sensitive program information, including e-mail, shall have at a minimum a favorable

Tier 1 investigation prior to being provided access. Contractor shall ensure those Contractor personnel requiring use of CACs comply with local guidance, as applicable. Personnel required to acquire CAC cards shall be responsible for completing required training and administrative requirements. Contractor's Contracting Officer (CO) shall identify Contractor personnel requiring CAC cards to the Procuring Contracting Officer (PCO) for approval/authorization.

Contractor personnel shall obtain a CAC from the nearest Real-time Automated Personnel Identification Documentation System (RAPIDS) Issuing Facility (typically the local Military Personnel Flight (MPF)). In the event travel is required to obtain a CAC, cost will be reimbursed to the Contractor on a Cost Reimbursable basis or as contracted.

3.2.1 Data Protection

The Contractor shall protect technical data and software IAW the Program Protection Plan (PPP) and Cybersecurity Strategy Annex. The Government reserves the right to witness all Contractor efforts to accomplish the SOW requirements and maintains the right to request that modifications be made to the Contractor’s processes. The Government PPP will identify the high-level Critical Program Information (CPI), Critical Technology (CT) and Critical Functions (CF). The Contractor's Program Protection Implementation Plan (PPIP) shall identify any additional CIs or CTs that are relevant for the C-130H FPS solution IAW DoDI 5200.39. (E084, DI-MISC-

80711A, SCIENTIFIC AND TECHNICAL REPORTS - PROGRAM PROTECTION

IMPLEMENTATION PLAN (PPIP))

3.2.2 Controlled Unclassified Information (CUI)

The Contractor shall comply with DoDI 5200.48_DAFI16-1403, Controlled Unclassified Information, DoDM 5200.01, Vol 1_AFMAN16-1404, Vol 1, Air Force Information Security Program, and DoDM 5400.07_AFMAN33-302, AFMAN, DoD FOIA Program. The contractor shall monitor CUI aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information.

The Contractor shall distribute controlled unclassified information IAW DoDI 3200.14, Principles and Operational Parameters of the DoD Scientific and Technical Information Program, and DoDI 2040.02, International Transfer of Technology, Articles, and Services. The Contractor shall properly mark all such documents IAW DoDI 5230.24, Distribution Statements on Technical Documents. Technical documents not subject to distribution are defined in DoDI 5230.24, DoD Directive (DoDD) 5230.25, and DoDM 5010.12-M, Procedures for the Acquisition and Management of Technical Data.

3.2.3 Operations Security (OPSEC)

The contractor shall ensure OPSEC is incorporated into the appropriate area of the contract IAW DoDD 5205.02E, DoD Operations Security (OPSEC) Program and AFI 10-701, Air Force OPSEC Program. The Contractor shall flow down all OPSEC requirements to subcontractors that handle Critical Information (CI). CI is defined as specific facts about friendly intentions, capabilities, or activities needed by adversaries to plan and act effectively against friendly mission accomplishment.

3.2.4 Security Incidents and Violations

The Contractor shall notify the Government Contracting Activity and the Government Security Manager within 72 hours of any incident involving the actual or suspected compromise/loss of classified information to enable the Government to conduct immediate assessments of potential impact pending formal inquiry/investigation. Actual or suspected compromise of Covered Defense Information will be reported IAW R-DFARS Clause 252.204-7012.

3.2.5 Security Education

All full-time contractor employees operating within Air Force Bases (AFBs) shall comply with the Security Education and Awareness program, comprising initial training, annual refresher training, and periodic tailored training sessions.

3.2.6 Physical Security

The Contractor shall be responsible for safeguarding all Government Property (GP) provided for Contractor use. The Contractor shall secure all GP at the end of each business day. The Contractor shall participate in locally administered physical security procedures.

3.2.7 Safeguarding Covered Defense Information and Cyber Incident Reporting

The Contractor shall provide adequate security to safeguard unclassified Controlled Technical Information (CTI) from compromise throughout the life of the contract. The Contractor shall comply with the clauses of this contract to ensure adequate security.

3.2.8 Pass and Identification

The Contractor shall work with the Government to obtain proper credentials, CAC, for Contractor personnel requiring long term access to Government facilities. The Contractor shall ensure those Contractor personnel requiring use of CACs comply with DAF Part 42 and local guidance, as applicable. Personnel required to acquire CAC cards shall be responsible for completing required training and administrative requirements. The Contractor shall identify Contractor personnel requiring CAC cards to the Government for approval/authorization.

If the Contractor requires a CAC, then a TIER 1 Security Clearance is required, which is initiated and completed by the Government.

The Contractor shall coordinate with local Government units to arrange unescorted access to the flight line, as necessary, to perform the requirements of this contract. Contractor personnel Rrequiring flight line access will need local training prior to being issued either a Restricted Area Badge (RAB) or placed on an Entry Authority List (EAL), as determined appropriate by the unit.

Either designation will authorize unescorted access to flight line areas necessary to perform duties. RABs must be surrendered to the unit security manager prior to final departure.

Appropriate background investigation requirements must be met before a person can be granted unescorted entry into restricted areas. There is an option for unescorted entry to be granted prior to the completion of the investigation, depending on the specifics of the situation and subject to Government approval (ref DAFI 31-101, Integrated Defense, DAFGM 2022-01 for additional information).

3.3 GENERAL REQUIREMENTS

3.3.1 Sustainable Procurement Program (SPP)

The Contractor shall adhere to the Sustainable Procurement Program (SPP), a mandatory federal acquisition initiative emphasizing environmentally preferable products and services. SPP requirements apply to all acquisitions funded by appropriated funds, encompassing services and new requisites. Compliance is governed by RFO 23.4, mandating the acquisition of Environmental Protection Agency (EPA) designated products listed in the Comprehensive Procurement Guidelines (CPG) containing recovered materials, unless competitive acquisition is unfeasible within a reasonable timeframe, fails to meet performance standards, or lacks a reasonable price.

3.3.2 Travel

Contractors may be required to travel for SOW-related activities, within the Continental United States (CONUS). Travel and personnel requirements shall be aligned with assigned tasks and coordinated with the Contracting Officer’s Representative and Government Program Manager.

Prior approval from the Government CO is mandatory for travel deviating from the Joint Travel Regulation (JTR). Reimbursement for travel expenses shall be in accordance with applicable rates outlined in Federal Travel Regulations (FTR) for CONUS travel and JTR for travel to Alaska, Hawaii, and outlying areas.

3.4 BUSINESS MANAGEMENT

3.4.1 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop, maintain, and submit the CWBS and CWBS Dictionary IAW guidance provided in MIL-STD-881F DoD Standard: Work Breakdown Structures (WBS) for Defense Material Items. The CWBS shall extend to the lowest appropriate level necessary for effective internal management and surveillance. It shall serve as the basis for tracking, controlling, measuring, and reporting all costs and schedule performance under the FPS System.

The Contractor shall update the CWBS as required during contract execution. (M009, DI-

MGMT-81334D, CONTRACT WORK BREAKDOWN STRUCTURE (CWBS))

3.4.2 Integrated Performance Measurement:

The Contractor shall conduct and submit Earned Value Management (EVM) and Contract Funds Status Report (CFSR) for all applicable CLINs, aligned with CWBS elements. Reporting elements in the CFSR shall reconcile with the Integrated Program Management Report (IPMR) when submitted concurrently. The Contractor shall provide the CFSR with IPMR reconciliation as an addendum to the IPMR. (F001, DI-MGMT-81468B, CONTRACT FUNDS STATUS

REPORT (CFSR); F002, DI-MGMT-81861C, INTEGRATED PROGRAM MANAGEMENT

DATA AND ANALYSIS REPORT (IPMDAR) – EARNED VALUE MANAGEMENT (EVM))

3.4.3 Integrated Baseline Reviews (IBRs):

The contractor shall engage jointly with the Government's program manager in Integrated Baseline Reviews (IBRs) to evaluate the risks inherent in the delivery order's planned performance measurement baseline. The IBR shall be a joint assessment conducted by the program team and the contractor to validate the Performance Measurement Baseline (PMB).

Initially, this shall occur no later than sixty days after contract award, and subsequently following all major changes to the baseline. An IBR must be successfully completed as a prerequisite for the formal approval of the contractor's schedule. Each IBR should verify that the contractor is using a reliable performance measurement baseline, which includes the entire contract scope of work, is consistent with Delivery Order schedule requirements, and has adequate resources assigned. IBRs should also be conducted on subcontracts that meet or exceed the EVM application threshold. The prime contractor shall lead the subcontractor IBRs, with active participation by the Government.

3.4.4 Over Target Baseline Restructure:

The Contractor may propose an Over Target Baseline/Over Target Schedule (OTB/OTS) restructure if the baseline no longer represents a realistic plan for budget/schedule execution. A formal request for baseline change shall be submitted via Contractor CO letter, including justification, detailed implementation procedures, and an implementation timeframe.

Government approval is required before implementing an OTB/OTS restructure action.

3.4.5 Associate Contractor Agreement (ACA)

When required, the Contractor shall enter into Associate Contractor Agreements (ACAs) for joint participation in fulfilling the Government’s requirements. ACAs shall specify the basis for sharing information, data, technical knowledge, expertise, and resources essential to integrating the C-130H FPS program. General information in ACAs shall include identification of associate contractors and relationships, relevant program and contract details, description of interfaces, categories of exchanged information or support, expiration date or event, potential conflicts, and agreements on proprietary data protection and employee restrictions. A copy of the agreement shall be provided to the Government for review before execution. The Contractor remains responsible for fulfilling all contract requirements, and costs associated with ACAs are included in the negotiated contract cost. Agreements may be amended as required by the Government during contract performance.

3.5 CONFIGURATION AND DATA MANAGEMENT

3.5.1 Configuration Management

The Contractor shall establish a configuration management and control process that encompasses hardware, software, and documentation which is consistent with the guidance provided in MIL- HDBK 61A and American National Standards Institute/Electronic Industries Association (ANSI/EIA)-649-1. The Contractor shall implement, maintain, and adhere to a SCMP, to include data management.

The Contractor shall implement and maintain a Configuration and Data Management program that includes a systematic change management process to develop, document, process, and submit Engineering Change Proposals (ECP), Contract Change Proposals (CCP), and Requests for Variance (RFV). The Contractor shall conduct Configuration Management and Planning necessary to establish and control the C-130H FPS allocated, functional, product and technical baselines for the system through the life of the contract or until the end of the PoP. The Contractor shall generate, implement, and submit a Supplier’s Configuration Management Plan (SCMP)

IAW the Government’s MMP and SEP. (C002, DI-SESS-80858D, SUPPLIER’S

CONFIGURATION MANAGEMENT PLAN (SCMP))

The Contractor’s configuration management process shall establish, maintain, and control the product and technical baselines throughout the contract PoP. The Contractor shall maintain traceability and currency among all product documentation and system software and equipment.

The Contractor shall apply these processes to control system products to include, but not limited to, flight manuals, operating manuals, maintenance manuals, temporary and permanent modifications, ECPs, CCPs, Request for Variances (RFVs), Deficiency Reports (DRs), and TDPs. The Contractor shall manage the Configuration Items (CIs) for which the Government is not the Current Document Change Authority (CDCA). The Contractor shall ensure compliance with all specifications and Interface Control Documents (ICDs) to which the CI was originally developed, tested, and procured. The Contractor shall apply configuration control to each CI/Computer Software Configuration Item (CSCI), its components, and its configuration documentation. The Contractor shall maintain configuration control throughout the life of the contract or until the end of the PoP. The Contractor shall submit the supporting TDPs and transfer control of the initial product baseline for all Class I (Major A) configuration changes to the Government at the completion of PCA.

The Contractor shall implement and maintain a Configuration and Data Management program that includes a systematic change management process to develop, document, process, and submit ECPs, CCPs, and Requests for Variance (RFV). The Contractor shall develop, document process, and submit ACPNS IAW TO 00-5-16, Software Managers and User’s Manual for the USAF ACPINS, for new releases or updates to CSCIs. (C003, DI-MISC-81454D, COMPUTER

PROGRAM IDENTIFICATION NUMBER (CPIN) CATALOG INFORMATION; C004, DI-

ADMN-81401C/T, CONTRACT CHANGE PROPOSALS (CCPs); C005, DI-SESS-80640E/T, REQUEST FOR VARIANCE (RFV); C006, DI-SESS-80639E/T, ENGINEERING CHANGE

PROPOSALS (ECP))

3.5.2 Data Management

The Contractor shall submit all program data IAW the CDRL or identified in the Data Accession List (DAL). The Contractor shall include data referenced within this SOW and all existing data, internally generated data and computer software used by the Contractor to develop, test, and manage the program in the DAL. The Contractor shall provide the Government access to all available DAL data. (C001, DI-MGMT-81453C, DATA ACCESSION LIST (DAL))

3.5.2.1 Licenses

The Contractor shall procure and manage all required licenses necessary to operate and/or maintain the C-130H FPS system to include hardware and software for the duration of the contract. The Contractor shall submit a Software License Requirements List (SLRL). Licenses procured under this contract shall be relinquished by the Contractor and transferable to the Government and other contractors as necessary to support program execution. The Contractor shall relinquish all licenses upon the contract’s termination and/or end of the PoP. (C007, DI-

PSSS-82046, SOFTWARE LICENSE REQUIREMENTS LIST (SLRL))

The Contractor shall provide appropriate technical data and license rights for the entire system.

For any unmodified COTS systems, this includes at least the deliverables and license rights as are typically provided to the customer or end user. For all other systems (e.g., noncommercial, military peculiar, or developmental - including any modifications to commercial systems that are funded in whole or in part by the Government), this includes:

a. The complete technical data package providing all production-level details

b. All computer modified software, including object/executable code, source code, and design information

c. The associated license rights consistent with the applicable data rights clauses in this contract (including/allowing specially negotiated license rights when appropriate)

3.6 DIMINISHING MANUFACTURING SOURCES AND MATERIAL

SHORTAGES MANAGEMENT (DMSMS) PROGRAM

The Contractor shall develop, plan, execute, and maintain a proactive DMSMS management program for the C-130H FPS Replacement through the life of the contract, which includes Line Replaceable Units (LRU), Shop Replaceable Units (SRU), parts, and materials, IAW AFMCI 20- 105 Diminishing Manufacturing Sources and Material Shortages, 15 July 2022.

The Contractor shall identify DMSMS solutions that analyze lowest life cycle cost and assess impacts to data rights, licenses, certification, training, TOs, Operational Manuals, and sustainment. The Contactor shall use the Advanced Components Obsolescence Management (AVCOM) system as the primary tool for execution of the C-130H FPS Replacement DMSMS issues, or equivalent DMSMS tool with Government approval. AVCOM is a commercially developed DMSMS predictive tool service that is the standard IT tool used by Air Logistics Complexes (ALCs) to proactively manage parts obsolescence for every organically managed system in the AF inventory. The Contractor shall submit a summary report of identified DMSMS issues, as well as proposed solutions for Government approval within 60 calendar days of discovery. (L002, DI-MGMT-82273, DIMINISHING MANUFACTURING SOURCES AND

MATERIAL SHORTAGES (DMSMS) HEALTH ASSESSMENT REPORT; L003 DI-MGMT-

81949, DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES

(DMSMS) IMPLEMENTATION PLAN)

3.6.1 DMSMS Implementation Plan

The Contractor shall develop, implement, deliver, and maintain a DMSMS Management Plan (DMP). The Contractor’s DMP shall describe and define the methods and predictive tools that will be used to categorize and quantify identification of DMSMS parts, problem resolution, and a recommended approach for mitigating risks associated with DMSMS throughout the life of the contract. The Contractor’s DMP shall establish guidance, assign responsibilities, and set into motion processes to minimize DMSMS impacts to the C-130H FPS Replacement and ensure continued availability of parts required for the manufacture, production, modification, repair, maintenance, and sustainment support. The Contractor’s DMP shall be developed IAW DoD DMSMS SD-22 Guidebook guidance.