PWS_Tech DataandProvisioning.pdf

CUI

Performance Work Statement for

USAF Special Operations Forces Technical Data Management, Development, and Provisioning Project

Purchase Request: FD2060-26-33314

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their Contractors (Administrative or Operational Use) (01 October 2026). Other requests for this document shall be referred to AFLCMC/WIUAA, Robins AFB, GA 31098-1670.

Controlled by: Department of the Air Force Controlled by: AFLCMC/WIUAA CUI Category: CTI Distribution/Dissemination Controls: Distribution Statement C POC: Catherine Revell, DSN 472-0880, catherine.revell@us.af.mil mailto:catherine.revell@us.af.mil

PR: FD2060-26-33314 PWS REVISION: - CUI

Change Page

Rev Date Author Change

- 1 October 2026 Catherine Revell Original

PR: FD2060-26-33314 PWS REVISION: - CUI 1

1.0 Description of Services

1.1 Objective(s): This Performance Work Statement (PWS) describes the professional engineering, technical-writing, and configuration-management services required to support the Special Operations Forces (SOF) Technical Data Management and Development Project. These services include engineering and technical-writing support for subsequent Technical Order (TO) development and drawing updates; and Configuration Management (CM), in accordance with Appendix A, to evaluate and manage proposed changes, track approved changes, and update drawings, TOs, and Time Compliance Technical Orders (TCTOs) in accordance with the Technical Manual Contract Requirements (TMCR). The desired outcome is accurate, current, and configuration-controlled technical documentation.

The Contractor shall provide provisioning support exclusively for the AC-130J by identifying and recommending spare and repair parts required to support system operation and sustainment, in accordance with the Air Force Initial Provisioning Performance Specification (IPPS). The Contractor shall develop and submit provisioning data compatible with the Government’s D220 system, using GEIA-HB-0007B as guidance and in accordance with applicable Quality of Contract Data Requirements List (CDRL)s and Data Item Descriptions. The Contractor shall support AC-130J provisioning and configuration-guidance conferences and incorporate Government-approved outcomes into depot maintenance recommendations and affected integrated logistics support elements.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by providing safe, accurate, effective, and timely TOs to support sustainment of SOF C-130J aircraft (AC, MC, and HC) and applicable components, support equipment, and modifications. It will improve warfighter capability, reduce demand on the low-density, high-demand SOF C-130J fleet, and reduce Contractor Logistics Support (CLS) costs. These outcomes directly support the USAF mission by enabling ready, reliable, and capable forces to conduct global operations.

1.3 Background: This project supports the sustainment, modernization, and continued evolution of the Special Operations Forces (SOF) C-130J aircraft fleet, encompassing the AC-130J Ghostrider, MC-130J Commando II, and HC-130J Combat King II capabilities. This effort supports the continued modernization of Air Force Special Operations Command (AFSOC) and United States Special Operations Command (USSOCOM) tactical capabilities.

2.0 Services Summary

Performance Objective PWS Reference

Performance Threshold

Quality of Contract Data Requirements List (CDRL) deliverable

4.2.1 There shall be no more than one rejection of any

deliverable. There shall be no more than 3 total rejection(s) of deliverables per contract year. The government will reject a deliverable if 2 or more technical errors or 3 or more minor errors are found within the deliverable. The rejected deliverable shall

PR: FD2060-26-33314 PWS REVISION: - CUI 2

Performance Objective PWS Reference

Performance Threshold be corrected and resubmitted within 10 business days of notification of government rejection.

Receipt of CDRL deliverable

4.2.2 There shall be no more than 2 late submission(s) of

deliverables per contract year. The contractor shall notify the government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the government.

3.0 Government Property: Government property includes Government Furnished Property (GFP), Government Furnished Material, Government Furnished Equipment, special tooling, special test equipment, etc. GFP does include assets furnished for repair, maintenance, overhaul or modification.

3.1 Contractor Responsibility: The contractor shall be responsible for government property in accordance with the Revolutionary FAR Overhaul (RFO) and as specified in the contract/order.

3.2 Government Property to be Provided: Government property to be provided includes applicable engineering and technical data; vendor manuals; existing TOs, TCTOs, operational supplements, and support-equipment TOs; and other available source data necessary to perform contract requirements. The Government will also provide, as required and authorized, access to applicable Government systems, databases, licensed software, supporting documentation, training, and user account approvals needed for TO/TCTO development, certification, and verification. Government-Furnished Information (GFI) will be provided by the Program Office or geographically separated Combat Acquisition Detachments (CADs) on an available, required, or authorized basis.

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

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the https://piee.eb.mil/ https://dodprocurementtoolbox.com/

PR: FD2060-26-33314 PWS REVISION: - CUI 3

property useless for its intended purpose or Beyond Economical Repair (BER). Loss of government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of government property does not include normal and reasonable inventory adjustments, i.e. losses of low-priority consumable material, such as common hardware, as agreed to by the contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property: The contractor shall report loss of government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

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

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend five years, consisting of a base period and four one-year ordering periods.

4.1.2 Place of Performance: These services will be performed at the contractor’s facility.

4.2 Contract Data Requirements List(s) (CDRL)

Document Identifier Base Year

Option Year 1

Option Year 2

Option Year 3

Option Year 4

DID Title PWS Reference(s)

A001 B001 C001 D001 E001 DI-MGMT-

80368A

Monthly Status Report

4.4.1

A002 B002 C002 D002 E002 DI-ADMIN-

81250C

Meeting Minutes 4.4.2

A003 B003 C003 D003 E003 DI-TMSS-

80607

Technical Order Verification Recommendation

(TOVR)

4.4.3

A004 B004 C004 D004 E004 TMCR TM

86-01

Technical Manual Contract Requirements

(TMCR)

4.4.4

A005 B005 C005 D005 E005 DI-MGMT-

81861D/T

Integrated Program Management Data

4.4.5 https://piee.eb.mil/piee-landing/

PR: FD2060-26-33314 PWS REVISION: - CUI 4

Document Identifier Base Year

Option Year 1

Option Year 2

Option Year 3

Option Year 4

DID Title PWS Reference(s) and Analysis Report

(IPMDAR)

A006 B006 C006 D006 E006 DI-QCIC-

81722

Quality Program Plan

(QPP)

5.9

A007 B007 C007 D007 E007 DI-ADMIN-

81249C

Meeting Agenda 4.4.2

A008 B008 C008 D008 E008 DI-SESS-

81758

Logistics Product Data

4.4.6

A009 B009 C009 D009 E009 DI-SESS-

81874

Engineering Data for Provisioning (EDFP)

4.4.7

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than 3 total rejection(s) of deliverables per contract year.

The government will reject a deliverable if 2 or more technical errors or 3 or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of government rejection.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area Workflow (WAWF) and/or submitted directly to the Multi-Functional Team member identified on the CDRL. Separately priced data must be submitted and accepted in WAWF in order for the contractor to receive payment. There shall be no more than 2 late submission(s) of deliverables per contract year. The contractor shall notify the government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date.

The data/document shall be delivered by the revised delivery date acceptable to the government.

4.3 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as authorized for government personnel. Contractor/subcontractor personnel shall only be permitted access to Government facilities when government personnel are present.

4.4 Program Management Support: The Contractor shall manage the program while maintaining clear Government visibility into program schedule, technical and logistical performance, configuration management initiatives, risks, and financial information.

4.4.1 Status Reports: The Contractor shall submit a monthly status report (MSR) detailing current program status, milestone schedules, and task-level actions. The report must concisely address key accomplishments, innovations, manpower, recruiting, security, subcontracting limitations, organizational conflicts of interest, and quality assurance. Additionally, it must document any travel summaries and identify all problem areas, challenges, or source data shortfalls, providing recommended solutions and tracking their implementation outcomes.

[CDRL A/B/C/D/E001, Monthly Status Report, DI-MGMT-80368A]

PR: FD2060-26-33314 PWS REVISION: - CUI 5

4.4.2 Meeting Documents: For all scheduled meetings or conferences, the Contractor shall provide an agenda and minutes unless directed otherwise in writing by the Government. [CDRL A/B/C/D/E002, Meeting Minutes, DI-ADMN-81250C ; CDRL A/B/C/D/E007, Meeting Agenda, DI-ADMN-81249C;]

4.4.3 Certification/Validation and Verification: The Contractor shall perform Certification/Validation and in accordance with TO 00-5-1, TO 00-5-3 and the TMCR. The Government will perform Verification and will have approval rights for final deliverable technical orders. The Contractor shall attend all verification meetings until the final deliverable TOs are verified. [CDRL A/B/C/D/E003, Technical Order Verification Recommendation

(TOVR), DI-TMSS-80607]

4.4.4 Technical Orders: The Contractor shall develop and deliver technical orders in accordance with the applicable TMCR. The Contractor shall use the documentation in Appendix C and other necessary sources to produce complete technical orders. Technical data shall be delivered in a digital format suitable for use on and off the aircraft and compatible with standard desktop personal computers. The Government will have unlimited rights to all technical orders and associated technical data developed under this contract. [CDRL A/B/C/D/E004, Technical Manual Contract Requirements (TMCR), TM-86-01]

4.4.5 Integrated Master Schedule (IMS): The Contractor shall develop and maintain an IMS containing the networked, detailed tasks necessary to ensure successful program execution. The IMS shall be used to verify attainability of contract objectives, to evaluate progress toward meeting program objectives and to integrate the program schedule activities with all related components. [CDRL A/B/C/D/E005, Integrated Program Management Data and Analysis Report (IPMDAR), DI-MGMT-81861D/T]

4.4.6 Logistics Product Data (LPD): The Contractor shall generate and submit Logistics Product Data (LPD) exclusively for AC-130J depot maintenance reparable program-of-record configurations. The Contractor shall identify and recommend logical spare, repairable, and consumable parts necessary to support system and equipment operation and sustainment in accordance with the Air Force IPPS, using GEIA-HB-0007B, Logistics Product Data Handbook, as guidance. All provisioning data shall be formatted for compatibility with the Government’s existing D220 provisioning data system and shall include, as applicable, Provisioning Parts Lists (PPLs), Short Form Provisioning Parts Lists (SFPPLs), Long Lead Items Lists (LLILs), and Design Change Notices (DCNs).

Within 45 business days after contract award, the Contractor shall plan and conduct an Initial Provisioning Guidance Conference (IPC) at the Contractor’s facility, with participation by the Procuring Contracting Officer (PCO), Government Program Manager (PM), USSOCOM, and AFSOC, to discuss provisioning requirements and program status; the Contractor shall prepare and submit meeting minutes. The Contractor shall support AC-130J provisioning and configuration guidance conferences, whether conducted at Government depot facilities or the Contractor facility, and shall incorporate Government-approved conference decisions into

PR: FD2060-26-33314 PWS REVISION: - CUI 6

affected logistics, sustainment, and depot maintenance capability elements to support complete Integrated Logistics Support (ILS). [CDRL A/B/C/D/E008, Logistics Product Data, DI-SESS- 81758]

4.4.7 Engineering Data for Provisioning (EDFP): The Contractor shall develop and submit Engineering Data for Provisioning (EDFP) for AC-130J depot maintenance reparable program-of-record configurations in support of Government review and approval. The EDFP shall support identification of material requirements and recommendations for Source, Maintenance, and Recoverability (SMR) codes. The Contractor shall update provisioning-related depot maintenance capability recommendations and associated sustainment elements, as required, to reflect Government-approved provisioning conference decisions, including approved SMR code changes. [CDRL A/B/C/D/E009, Engineering Data for Provisioning (EDFP), DI-SESS- 81874]

4.5 Travel: Travel requests for contractor/subcontractor personnel shall be submitted for approval to the Contracting Officer prior to costs being incurred and a minimum of 10 business days in advance of departure. Receipts must be presented with the invoice for reimbursement of actual travel costs.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander/Director has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 Security Regulations: The contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The contractor shall ensure contractor/subcontractor personnel who perform work on a government facility comply with the security requirements of the facility.

5.2.2 Cybersecurity Maturity Model Certification (CMMC): The contractor shall achieve and maintain a CMMC Level 2 (Self) or higher and provide the CMMC unique identifier(s) (CMMC UIDs) issued by Supplier Performance Risk System (SPRS) for each contractor information system that will process, store, or transmit Federal Contract Information (FCI) or Controlled Unclassified Information (CUI) during performance of the contract.

5.2.3 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. DoDD 5205.02E and DoD Manual 5205.02-M require contractors supporting DoD activities use OPSEC to protect critical information for specified contracts, subcontracts, and information used in the performance of duties in support of Air Force requirements/missions. The contractor shall ensure contractor personnel who perform work on (or in) a government facility comply with the OPSEC procedures and training requirements of the facility as specified in AFI 10-701.

PR: FD2060-26-33314 PWS REVISION: - CUI 7

5.2.4 Communications Security (COMSEC): The Contractor shall transmit or transfer all classified information and CUI using only secure, approved communications methods and equipment. The Contractor shall safeguard, maintain, and operate all applicable COMSEC equipment. All actions must comply with 32 CFR Part 117, § 117.7.

5.2.5 Security Clearance: It is not expected contractor/subcontractor personnel will require security clearances for proper accomplishment of contract/order requirements.

Contractor/Subcontractor personnel shall not be authorized to access classified information and classified items or be permitted to work on classified projects and/or programs without an appropriate security clearance and a need-to-know.

5.2.6 Security Incident or Violation: The contractor shall immediately notify the government Security Office of any potential or actual security incident or violation.

5.2.7 Access to Government System(s): The government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a Tier 1 (T1) background investigation (formerly NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the contractor shall ensure the system account(s) are closed.

5.2.8 Access to Robins Air Force Base (AFB): The contractor shall ensure contractor/subcontractor personnel who require access to Robins AFB comply with the security requirements of the installation. The contractor shall provide the CO a list of all contractor/subcontractor personnel requiring access to Robins AFB, the contract/order number and the period of performance. The contractor shall also provide, if possible, the location of the work site and the days/hours during which the contractor/subcontractor personnel will require access to Robins AFB.

5.2.9 Common Access Card (CAC)

5.2.9.1 The contractor shall ensure a Common Access Card (CAC) is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the CO. The government will provide the contractor instruction on how to utilize Mission Partner Identity, Credential and Access Management (MP-ICAM) and notify the contractor of approval/disapproval of contractor/subcontractor personnel application.

contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

PR: FD2060-26-33314 PWS REVISION: - CUI 8

5.2.9.2 The contractor shall immediately report a lost or stolen CAC as directed by local government policy. The contractor shall notify the CO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The contractor shall return an expired CAC within five business days after the expiration date. The contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local government policy.

5.3 Environmental Management System (EMS): These services shall not be performed at a government facility; therefore, the EMS requirement does not apply.

5.4 Agency Programs: This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.

5.5 Safety Requirements

5.5.1 Contractor Environmental, Safety, and Occupational Health Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoD Directive 4715.1E, Environmental, Safety, and Occupational Health (ESOH). The Contractor shall require all subcontractors to comply with required safety, health and fire standards.

5.5.2 Mishap Notification/Investigation: In accordance with DODI 6055.07 and DAFI91-204, Safety Investigations and Reports, the Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations.

The Contractor shall contact the organizations listed below within four business hours. The Contractor shall immediately secure the mishap scene (and damaged property) and impound pertinent maintenance and training records until released by the Government’s Safety Office.

Such release shall be accomplished through the Contracting Officer. The Contractor shall cooperate and assist Government personnel in the investigation of the mishap and submit an Accident/Incident Report within 24 hours of the mishap. There shall be no more than one (1) instance of late mishap notification per contract year. The Contractor shall ensure the following are notified:

a. CO

b. MFT (COR, if available, or another MFT member)

c. Robins AFB command post (478-327-2612)

The following information shall be provided in support of the Mishap notification as soon as it becomes available:

a. Contract, contract number, name and title of person(s) reporting

b. Date, time and exact location of accident/incident

c. Brief narrative of accident/incident (events leading to accident/incident)

d. Cause of accident/incident, if known

PR: FD2060-26-33314 PWS REVISION: - CUI 9

e. Estimated cost of accident/incident (material and labor to repair/replace)

f. Nomenclature of equipment and personnel involved in accident/incident

g. Corrective actions (taken or proposed

h. Other pertinent information

5.6 Inspection of Services: In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the government reserves the right to inspect contractor performance.

5.7 Service Contract Reporting: In accordance with R-DFARS 204.303, Reporting Requirements for Contracted Services, the contractor shall provide a Service Contract Report for each contract/order that meets the DoD Contract Reporting criteria and has obligations in excess of $3,000,000. The contractor shall report the total amount invoiced and contractor labor hours expended on the services performed during the previous fiscal year. Prime contractor labor hours, including any required Tier 1 subcontractor information, shall be reported in the System for Award Management (SAM). The contractor shall report annually, by October 31, on the services performed during the preceding government fiscal year. SAM will only enable reporting for entities with contracts that meet the SCR criteria and thresholds. Additional information and user manuals for government personnel and contractors is available at https://www.sam.gov.

SCR eligibility, reporting rules and criteria is located on the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr.

5.8 Invoicing/Payment and Receipt/Acceptance: The contractor shall submit/process payment requests and receipt/acceptance documents via WAWF.

5.9 Quality Program Plan/Quality Management System (QMS): The contractor shall ensure the quality of services through a quality and/or inspection system. The contractor shall submit a Quality Program Plan (QPP) addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The plan shall include the schedule of quality assurance/control inspections planned by the contractor. The contractor shall permit the program office or its designated representative to periodically review its quality program. [CDRL A/B/C/D/E006, Quality Program Plan (QPP), DI-QCIC-81722]

5.10 Trafficking in Persons: The contractor shall comply in accordance with the RFO and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons. https://www.state.gov/ https://www.sam.gov/ https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr https://www.state.gov/bureaus-offices/under-secretary-for-foreign-assistance-humanitarian-affairs-and-religious-freedom/office-to-monitor-and-combat-trafficking-in-persons/

PR: FD2060-26-33314 PWS REVISION: - CUI 10

6.0 Appendices

6.1 Appendix A, Reference(s)

Publication Title of Publication Date of Publication Sections(s) that Apply

32 CFR

Part 117

National Industrial Security Program Operating Manual

(NISPOM).

July 28 2025

DoDD 4715.1E

Environment, Safety, and Occupational Health (ESOH) March 19, 2005

DoDD 5205.02E

DoD Operations Security (OPSEC) Program June 20, 2012

DoD Manual 5205.02-M

DoD Operations Security (OPSEC) Program Manual November 3, 2008 Change 2, October 29, 2020

FAR and supplements

Federal Acquisition Regulation www.acquisition.gov

Public Law 91-596 as amended by Public Law 116- 92-552

Occupational Safety and Health Act of 1970 December 29, 1970 as amended through December 20, 2019 http://www.acquisition.gov/