324_TES PWS_ Mar 2024_Final.pdf

CUI PWS 24-WLSE-01

PR: FD2060-23-30952 PWS Revision: CUI Distribution Statement C

Performance Work Statement (PWS) 24‐WLSE‐01

For

C‐5M Technical & Engineering Services (TES)

Date: 21 March 2024

AFLCMC/WLS

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (Critical Technology) (4 Jan 2024). Other requests for this document must be referred to the C-5M Super Galaxy Contract Management Team, AFLCMC/WLS, 235 Byron Street, Suite 19A, Robins AFB, GA 31098-1670.

Controlled by: AFLCMC Controlled by: Mobility & Training Aircraft CUI Category: SP-PROCURE Distribution/Dissemination Controls: FEDCON POC: AFLCMC.WLS.Admin@us.af.mil

PR: FD2060-23-30952 PWS Revision: CUI Distribution Statement C

1.0 DESCRIPTION OF ENGINEERING SERVICES

1.1 OBJECTIVES

1.2 BENEFIT TO UNITED STATES AIR FORCE (USAF)

1.3 BACKGROUND

2.0 SERVICES SUMMARY

2.1 OVERARCHING OBJECTIVES ................................................................................ Error! Bookmark not defined.

2.2 ADDITIONAL PROGRAM-SPECIFIC OBJECTIVES ............................................... Error! Bookmark not defined.

3.0 GOVERNMENT-FURNISHED PROPERTY (GFP), GOVERNMENT FURNISHED SERVICES AND ACCESS

TO GOVERNMENT SYSTEMS

3.1 FACILITIES AND AIRCRAFT ................................................................................... Error! Bookmark not defined.

3.2 COMPONENTS AND SYSTEMS .............................................................................. Error! Bookmark not defined.

3.3 MATERIALS AND EQUIPMENT ............................................................................... Error! Bookmark not defined.

3.4 BASE SUPPORT ...................................................................................................... Error! Bookmark not defined.

3.5 GOVERNMENT INFORMATION SYSTEMS ACCESS AND DATA ......................... Error! Bookmark not defined.

4.0 OVERARCHING REQUIREMENTS AND DELIVERABLES

4.1 PERIOD AND PLACE OF PERFORMANCE

4.2 CONTRACT DATA REQUIREMENTS LIST(S) (CDRL)

4.3 CERTIFICATION SUPPORT

4.4 SYSTEM SAFETY PROGRAM

4.5 TECHNICAL DATA

4.6 DRAWINGS AND MODELS

4.7 TECHNICAL ORDER (TO) SOURCE DATA

4.8 PROGRAM MANAGEMENT

4.9 TRAVEL

4.10 HOLIDAYS AND FACILITY CLOSINGS

5.0 TECHNICAL & ENGINEERING SERVICES

5.1 ASIP

5.2 ASIP DATA INTEGRATION

5.3 CPCP

5.4 FSIP

5.5 TDS

5.6 Engineering Investigations (EI)

5.7 CLS EI

6.0 CONTRACTOR AIRCREW SUPPORT

6.1 AIRCREW SUPPORT AND CURRENCY

6.2 CURRENCY RECORDS

6.3 JOINT REVIEWS

6.4 AIRCREW FINAL REPORT

7.0 DEPOT MAINTENANCE TECHNICAL AND ENGINEERING SUPPORT

7.1 TECHNICAL AND ENGINEERING SUPPORT

7.2 MEETINGS AND REVIEWS

8.0 GENERAL INFORMATION

8.1 CONTINUATION OF MISSION ESSENTIAL SERVICES DURING CRISIS

8.2 SECURITY REQUIREMENTS

8.3 ENVIRONMENTAL MANAGEMENT SYSTEM (EMS)

8.4 AFFIRMATIVE PROCUREMENT PROGRAMS (APP)

8.5 SAFETY REQUIREMENTS

8.6 VPP

8.7 DEPARTMENT OF LABOR (DOL) INSPECTION OF CONTRACTOR OPERATIONS

8.8 INSPECTION OF SERVICES

8.9 SERVICE CONTRACT REPORTING (SCR) ............................................................. Error! Bookmark not defined.

8.10 INVOICING/PAYMENT AND RECEIPT/ACCEPTANCE

8.11 TRAFFICKING IN PERSONS

9.0 APPENDICES

9.1 APPENDIX A: ACRONYMS

9.2 APPENDIX B: APPLICABLE DOCUMENTS

9.3 APPENDIX D: FRACAS CLS MONITORED PARTS LIST

9.4 APPENDIX E: DMS FORECASTING EXCERPT

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 1 of 56

DISTRIBUTION STATEMENT C

FY24 C-5M Technical & Engineering Services (TES)

1.0 DESCRIPTION OF ENGINEERING SERVICES

1.1 OBJECTIVES

This Performance Work Statement (PWS) describes services required to provide technical and engineering services in support of the C-5M Super Galaxy aircraft.

Engineering services include, but are not limited to, performing engineering investigations and analyses, formulating deficiency resolution concepts, designing proof-of-concepts, and laboratory and on- and off-aircraft testing. Areas to receive engineering support unique to the Original Equipment Manufacturer (OEM) within this PWS include, but are not limited to, Aircraft Structural Integrity Program (ASIP), Functional Systems Integrity Program (FSIP), Corrosion Prevention and Control Program (CPCP), specific Engineering Investigations (EIs), specific Contractor Logistics Services (CLS) EIs, Contractor Aircrew Support, and Depot Maintenance Technical and Engineering Support.

Technical Data Sustainment (TDS) services are also supported to acquire missing or incomplete historical technical data which the Government does not otherwise have access to, in order to fill in the C-5M baseline repository and sustain the C-5M.

1.2 BENEFIT TO UNITED STATES AIR FORCE (USAF)

These services will benefit the USAF by continuing to maintain the operational life cycle readiness and ensure the safety of the C-5M fleet. This will support keeping the C-5M fleet on time and on mission in accordance with the USAF Core Mission of Rapid Global Mobility.

1.3 BACKGROUND

These technical and engineering services are a follow-on to services provided under the previous Sustaining Engineering and Technical Support Services (SETSS) contract, FA8525-19-D-0001. The scope of work has been expanded from Sustaining Engineering Services to Engineering Services to encompass similar engineering services that may be be performed using Research, Development, Testing and Evaluation (RDT&E) or Investment types of funding.

ASIP and CPCP are mandatory In Accordance With (IAW) Department of the Air Force Instruction (DAFI) 63-140, Aircraft Structural Integrity Program and Air and Space Equipment Structural Management, and Air Force Instruction (AFI) 63-101/20-101, Integrated Life Cycle Management, and shall meet the intent of requirements established IAW MIL-STD-1530D with Change 1, Aircraft Structural Integrity Program. FSIP is mandatory IAW AFI 63-101/20-101, Integrated Life Cycle Management, and shall meet the intent of requirements established in MIL-STD-1798D, Mechanical Equipment and Subsystems Integrity Program. RRP is required to ensure the C-5M maintains Operational Safety, Suitability and Effectiveness (OSS&E) in relation to safety and is compliant with the requirements in AFI 91-202, The US Air Force Mishap Prevention Program, AFI 91-202 AFMCSUP (Air Force Materiel Command Supplement), DAFI 91-204, Safety Investigations and Reports, DODI 5000.88, Engineering of Defense Systems, and MIL-STD-882E, System Safety.

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 2 of 56

2.0 SERVICES SUMMARY

Performance Objective

Reference Paragraphs

Performance Threshold

Quality of Technical Data/Documents via CDRLs

4.2.2

There shall be no more than one (1) rejection of any deliverable. There shall be no more than four (4) total rejections of deliverables per contract year. The Government will reject a deliverable if one (1) or more technical errors or six (6) or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within 21 calendar days of notification of Government rejection.

Receipt of Technical Data/Documents via CDRLs

4.2.1

There shall be no more than one (1) late submission of data/document(s) IAW the CDRLs per quarter and four (4) late submissions per year on a task order basis. The Contractor shall notify the PCO/COR if the delivery of any data/document will not meet the required delivery date and negotiate a revised date for delivery approved by the PCO/COR.

Engineering solution(s) for Rapid Response Taskings

5.6.1.1.8

Initial plan for assessing the task shall be submitted within 24 hours of PCO phone or email tasking and contractor acknowledgement. Final plan for assessing the task shall be submitted within 48 hours of PCO formal written tasking. The Contractor’s final assessment plan shall be submitted and accepted by COR with no more than one revision per submission.

Deficiency Report (DR) investigations

5.6.2

For investigations conducted under section 5.6.2 during the period of performance, identify root cause IAW TO 00-35D-54.

Provide initial response to DR investigations as an interim report within the following time periods after Contractor is assigned DR and is notified by JDRS:

CAT I: 20 clock hours CAT II: 7 calendar days

Provide final resolution response or resolution plan, including new Estimated Completion Date (ECD), as an interim report with a notification to the COR within the following time periods:

CAT I: 45 calendar days CAT II: 100 calendar days COR requested corrective action to interim report shall be completed within 48 hours.

DRs in open status which have been referred to the Contractor shall be updated with an interim report every 80 calendar days with a notification to the COR, with the exception of DRs in open awaiting funds status.

COR requested corrective action to interim report shall be completed within 48 hours. DRs in open awaiting funds status shall be updated every 350 calendar days.

Responses for all categories shall meet the requirement 100% of the time.

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 3 of 56

3.0 GOVERNMENT-FURNISHED PROPERTY (GFP)

The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 GOVERNMENT PROPERTY TO BE PROVIDED

Government property to be provided may include off aircraft components as required in order to support activities outlined in this PWS. Availability of parts shall be subject to C-5 fleet requirements and the approval of the responsible organization at WR-ALC, Oklahoma City Air Logistics Complex (OC-ALC), Ogden Air Logistics Complex (OO-ALC) and any other Government agency. Any aircraft components or other materials within the supply chain that are provided outside of a Government facility for activities outlined in this PWS shall utilize shipping containers which meet the requirements of the AFMC Form 158, Packaging Requirements, and which shall be in accordance with MIL-STD-2073-1E, Standard Practice for Military Packaging, and/or MIL-STD-129R, Military Marking for Shipment and Storage. Shipping containers which meet the requirements of the AFMC Form 158 and are suitable for return of serviceable assets shall be reclaimed and stored for reuse.

Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.

3.3 Base Support

For the Contractor’s personnel to complete some tasks, AFLCMC/WLSE will provide facilities to support up to eight (8) Contractor personnel (to include subcontractors) required to be collocated at Robins Air Force Base (RAFB) at any one time. AFLCMC/WLSE will provide office space, desks, chairs, telephones and access to copying machines at RAFB. Computers and monitors will be provided by AFLCMC/WLSE; however, shredders, fax and any other office supplies will not be provided by the Government. AFLCMC/WLS will provide access to Government facilities and aircraft as required in order for the Contractor to perform various tasks including reasonable access on a noninterference basis to discuss issues with repair technicians. Aircraft will be made available based on fleet requirements and with the approval of Air Mobility Command (AMC), Air Force Reserve Command (AFRC) and AFLCMC/WLSE.

3.4 Reporting 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 FAR 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 Government Furnished Property (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 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/ . (CDRL A/B/C/D/E009, DI-MGMT- 80441D, Government Property (GP) Inventory Report)

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 4 of 56

3.5 Loss of Government Property

3.5.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 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.5.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.6 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 Procuring Contracting Officer (PCO) 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 PCO. 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 PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 OVERARCHING REQUIREMENTS AND DELIVERABLES

4.1 PERIOD AND PLACE OF PERFORMANCE

4.1.1 Contract Period of Performance

The ordering periods for this contract will extend over 5 years and an extension of services clause will provide an option for an additional 6 months. Contract closeout activities will be completed no later than 30 calendar days after end of each task order in order to allow time for the Government to confirm approval of all deliverables.

4.1.2 Place of Performance

These services shall be performed at a combination of U.S. Government installations, as necessary (including RAFB), and at the Contractor’s facility.

4.2 CONTRACT DATA REQUIREMENTS LIST(S) (CDRL)

Data Item # DID Title PWS References A/B/C/D/E001 DI-MGMT-80368A/T Status Report 4.8.3, 5.4.5, 5.4.6, 5.6.2, 5.6.2.2, 5.6.3, 5.6.5, 5.7.1, 5.7.2, 6.3, 6.4, 7.1.7 A/B/C/D/E002 DI-ADMN-81249C Meeting Agenda 4.6.2, 4.6.3, 4.8.4 A/B/C/D/E003 DI-ADMN-81250C Meeting Minutes 4.6.2, 4.6.3, 4.8.4, 4.8.7

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 5 of 56

A/B/C/D/E004 DI-MGMT-81605 Briefing Material 4.6.2, 4.6.3, 4.8.4, 4.8.7, 6.3, 7.1.5, 7.1.7 A/B/C/D/E005 DI-MGMT-81797/T Program Management

Plan 4.8.3, 4.8.6

A/B/C/D/E006 DI-MISC-80748/T Engineering Services Memorandum

4.8.6, 5.6

A/B/C/D/E007 DI-MGMT-81468A Contract Funds Status Report (CFSR)

4.8.3

A/B/C/D/E008 DI-SESS-81000F/T Product Engineering Design Data and Associated Lists

4.6.1, 5.5.7, 5.6.1.9, 5.6.6, 5.6.7, 5.6.8.5, 5.6.10, 5.6.11, 5.6.15

A/B/C/D/E009 DI-MGMT-80441D Government Property (GP) Inventory Report

3.4

A/B/C/D/E00A DI-GDRQ-80650 Design Data and Calculations

5.1.1

A/B/C/D/E00B DI-MISC-80711A Scientific and Technical Reports

4.7, 5.1.1, 5.1.4, 5.2.1, 5.2.2, 5.2.3, 5.3.9, 5.4.1, 5.4.2, 5.4.4, 5.4.7, 5.5.3, 5.5.7, 5.6.1, 5.6.1.8, 5.6.2, 5.6.6, 5.6.7, 5.6.8.5, 5.6.9, 5.6.10, 5.6.11, 5.6.12, 5.6.13, 5.6.14, 5.6.15, 5.7.1, 5.7.2, 6.4

A/B/C/D/E00C DI-SESS-81956A/T Aircraft Structural Integrity Program (ASIP) Master Plan

5.1.2

A/B/C/D/E00D DI-SESS-82039/T Force Structural Maintenance Plan

(FSMP)

5.1.1

A/B/C/D/E00E DI-MISC-80711A/T Scientific and Technical Reports - Annual Report

5.1.5, 5.4.8

A/B/C/D/E00F DI-IPSC-81756 Software Documentation 5.2.1, 5.2.2 A/B/C/D/E00G DI-NDTI-80566A Test Plan 5.1.1, 5.4.1, 5.4.2, 5.6.2, 5.6.9, 5.6.10, 5.6.11, 5.6.13, 5.6.14 A/B/C/D/E00H DI-NDTI-80603A Test Procedures 5.1.1, 5.2.2, 5.4.1, 5.4.2, 5.6.2, 5.6.9, 5.6.10, 5.6.11, 5.6.13, 5.6.14 A/B/C/D/E00J DI-NDTI-80809B Test/Inspection Report 5.1.1, 5.4.1, 5.4.2, 5.6.2, 5.6.9, 5.6.10, 5.6.11, 5.6.13, 5.6.14 A/B/C/D/E00K DI-SAFT-80101C System Safety Hazard

Analysis Report

(SSHAR)

4.4

A/B/C/D/E00L DI-SAFT-80102C Safety Assessment Report

(SAR)

4.4

A/B/C/D/E00M DI-PSSS-81656B Bill of Materials (BOM) for Logistics and Supply Chain Risk Management

5.4.6, 5.6.3, 5.7.2

A/B/C/D/E00N DI-MGMT-81453B Data Accession List 4.5.2, 4.5.3, 5.6.1.9, 6.2, 7.1.5 A/B/C/D/E00P DI-SESS-82397 Airworthiness Plan 4.3 A/B/C/D/E00Q DI-SESS-81766A Airworthiness

Certification Basis 4.3

A/B/C/D/E00R DI-SESS-81768A Airworthiness Compliance Report

4.3

A/B/C/D/E00S DI-SAFT-81563 Accident/Incident Report 8.5.2

4.2.1 Receipt of CDRL Deliverable: There shall be no more than one (1) late submission of data/document(s) IAW the CDRLs per quarter and four (4) late submissions per year on a task order

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 6 of 56 basis. The Contractor shall notify the PCO and Contracting Officer’s Representative (COR) if the delivery of any data/document will not meet the required delivery date and negotiate a revised date for delivery approved by the PCO/COR.

4.2.2 Quality of CDRL Deliverable: There shall be no more than one (1) rejection of any deliverable.

There shall be no more than four (4) total rejections of deliverables per contract year. The Government will reject a deliverable if one (1) or more technical errors or six (6) 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 21 calendar days of notification of Government rejection.

4.2.3 The Contractor shall electronically submit all CDRL deliverables through MEARS, with exceptions as noted in CDRLs or as directed by the PCO/COR. The Contractor shall utilize MEARS to submit contract data and ensure timely data deliveries. The Contractor shall work with the government to ensure that an adequate number of Contractor personnel obtain and possess Public Key Infrastructure (PKI) certification from an accepted Government source. MEARS classroom training will be made available to Contractor personnel upon request.

4.3 CERTIFICATION SUPPORT

The Contractor shall perform Airworthiness certification activities IAW MIL-HDBK-516C, Airworthiness Certification Criteria. The Contractor shall maintain an Airworthiness Certification Management Plan to guide engineering process and activities. If potential impacts are identified, the Contractor shall support the System Program Office IPT and Certification Lead to jointly determine impacted certification requirements and method of verification IAW DAFI 62-601, Airworthiness.

The Contractor shall perform Cybersecurity Risk Management activities IAW DoDD 5000.01 guidance for ensuring security requirements are addressed and verified for all Platform Information Technology (IT) systems, as defined by AFI 17-101, Risk Management Framework (RMF) for Air Force Information Technology (IT). The Contractor shall review C-5 configuration cybersecurity and vulnerability documentation for corrective action planning with AFLCMC/WLSE.

The Contractor shall apply the established certification processes for taskings under this PWS. The Contractor shall hold an annual Certification Working Group with AFLCMC/WLSE to review process updates, if any, and certification activities planned.

Certification personnel shall be available to support field issues, as required. Field generated DRs assigned to the Contractor shall be monitored for certification impacts as well. (CDRL A/B/C/D/E/F00P, DI-SESS-82397 Airworthiness Plan; CDRL A/B/C/D/E/F00Q, DI-SESS-81766A, Airworthiness Certification Basis; CDRL A/B/C/D/E/F00R, DI-SESS-81768A, Airworthiness Compliance Report)

As requested by the Government, the Contractor shall review taskings under this PWS to determine potential impacts to C-5 aircraft certifications, including airworthiness, information assurance, joint interoperability, and frequency allocation. If potential impacts are identified, the Contractor shall

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 7 of 56 support the System Program Office IPT and Certification Lead to jointly determine appropriate certification requirements and method of verification IAW DAFI 62-601, Airworthiness. Certification personnel shall be available to support field issues, as required. Field generated DRs assigned to the Contractor shall be monitored for certification impacts as well. (CDRL A/B/C/D/E00P, DI-SESS- 82397 Airworthiness Plan; CDRL A/B/C/D/E00Q, DI-SESS-81766A, Airworthiness Certification Basis; CDRL A/B/C/D/E00R, DI-SESS-81768A, Airworthiness Compliance Report)

4.4 SYSTEM SAFETY PROGRAM

The Contractor shall conduct a System Safety Program IAW MIL-STD-882E, System Safety;

Department of the Air Force Instruction (DAFI) 91-202, The US Airforce Mishap Prevention Program, Department of the Air Force Manual (DAFMAN) 91-203, Air Force Occupational Safety, Fire, and Health Standards; Airworthiness Bulletin 150 Revision B (AWB-150B), Risk Assessment and Acceptance, and State and Federal OSHA requirements.

The Contractor shall review taskings under this PWS which alter form, fit, or function to determine potential impacts to safety IAW MIL-STD-882E and DAFI 91-202. Contractor shall submit a System Safety Program Plan annually, if the Contractor plan has changed since previous ordering period.

The Government reserves the right to identify additional hazards and report them to the contractor for investigation and recommendation. System Safety Assessments (SSA) are generated and delivered to the Government via CDRL, as required given fleet operational findings and investigations and/or engineering change programs.

The Contractor shall support a quarterly AFLCMC/WLSE chaired System Safety Working Group.

The Contractor shall conduct a System Safety Program IAW MIL-STD-882E, System Safety;

Department of the Air Force Instruction (DAFI) 91-202, The US Airforce Mishap Prevention Program, Department of the Air Force Manual (DAFMAN) 91-203, Air Force Occupational Safety, Fire, and Health Standards; Airworthiness Bulletin 150 Revision B (AWB-150B), Risk Assessment and Acceptance, and State and Federal OSHA requirements. The Contractor shall review taskings under this PWS which alter form, fit, or function to determine potential impacts to safety IAW MIL-STD- 882E and DAFI 91-202. Contractor shall submit a System Safety Program Plan and Hazard Tracking Database annually to account for all safety analyses/reports and requirement changes during the ordering period. The Government reserves the right to identify additional hazards and report them to the contractor for resolution. (CDRL A/B/C/D/E00K, DI-SAFT-80101C, System Safety Hazard Analysis Report (SSHAR); CDRL A/B/C/D/E00L, DI-SAFT-80102C, Safety Assessment Report

(SAR))

4.5 TECHNICAL DATA

4.5.1 All technical data delivered under this contract shall be marked in accordance with DFARS 252.227-7013, DFARS 252.227-7014, and/or DFARS 252.227-7015. Accordingly, all technical data and reports delivered to the Government with ‘other than unlimited rights’ shall be subject to ‘Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data.’ The Government reserves the right of validation of any assertion in accordance with DFARS 252.227-7019 and DFARS 252.227-7037.

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 8 of 56

4.5.2 The Contractor shall flow data requirements down to subcontractors to ensure contractor and Government access to data generated in accordance with this PWS. The Contractor shall maintain a data system, including subcontractor data, which shall be readily available to the Government. The data system shall contain program documents and support electronic delivery, storage, and archiving of both informal documents and formal supporting documents of taskings under this contract. The Contractor shall provide a list of data applicable to all efforts. (CDRL A/B/C/D/E00N, DI-MGMT-81453B, Data Accession List)

4.5.3 The Contractor shall maintain a Data Accession List (DAL). The DAL is an index of programs or work products generated or modified under the contract but are not covered by existing CDRLs. Generated data included in the DAL shall be comprehensive and cumulative in nature and shall be tied to the overarching TES contract number. Data items and programs listed on the DAL shall be made available to the Government upon request. (CDRL A/B/C/D/E00N, DI-MGMT- 81453B, Data Accession List)

4.5.4 Any request for information or support of any system covered by work performed under this PWS that requires contractor or subcontractor intellectual property to fully define and sustain a Technical Data Package (TDP) shall be appropriately identified with conforming markings IAW DFAR guidance and contract clauses. The PCO may validate technical data markings and rights IAW: DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions; DFARS 252.227-7019, Validation of Asserted Restrictions – Computer Software;

DFARS 252.227-7037, Validation of Restrictive Markings on Technical Data. Any limited rights data determined to be unreleasable to the Government shall be made available for Government review at the contractor or subcontractor facility.

4.6 DRAWINGS AND MODELS

4.6.1 Engineering Data

The Contractor shall create/produce/maintain and deliver a TDP that accurately depicts the final product, as required by taskings performed under this contract. TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, model based definition data sets, Gerber data and Master Bill of Materials (BOM). Each TDP shall provide the design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort. Each TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). For new drawings, Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements). All Lockheed Martin Aeronautics (LMA) and subvendor engineering product definition data created using Government funding as a result of this contract shall be considered a part of the TDP and shall be delivered to the Government with unlimited rights. The TDP shall be created IAW the following American Society of Mechanical Engineers (ASME) standards: ASME Y14.100- 2013, Appendix B, sections B6 through B9.1 and Appendices C, D and E in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35 and ASME Y14.41 and as defined in the corresponding CDRL for the task to create and deliver Product Drawings Models and Associated Lists (Engineering

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 9 of 56

Data) under this contract. CAD model file name and extension identification is required on drawing graphic sheets. TDP data shall specify parts marking requirements for item identification IAW MIL- STD-130N, other applicable documents referenced therein, and as specified in this contract. Test Criteria for Electrical and Avionics Items shall be IAW document 9579777 Revision B (CAGE 98752). The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision N (CAGE 98752). Any models and associated products generated shall meet the intent of MIL-HDBK-539, Digital Engineering and Modelling Practices, and MIL-STD-3022, Documentation of Verification, Validation, and Accreditation (VV&A) for Models and Simulations, if applicable. (CDRL A/B/C/D/E008, DI-SESS-81000F/T, Product Engineering Design Data and Associated Lists)

4.6.2 Engineering Data Guidance Conference

The Contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award in preparation for the event that drawings may be required by future taskings. The conference shall be convened at a site and on a date agreed upon by the Government PCO and the Contractor and may be held in conjunction with other meetings or conferences. The Contractor shall prepare an agenda and record the minutes of the Guidance Conference. The Contractor shall address, discuss, and provide status on the following:

a. Understanding of all CDRL requirements, applicable Data Item Descriptions (DIDs), specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

d. Contractor's drafting practices/procedures/TDP drawing formats/CAD programs.

e. The Contractor's quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.

f. The role of subcontractors and vendors who may deliver TDP documents under this contract.

g. The Contractor's configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.

h. Digital TDP deliverables.

(CDRL A/B/C/D/E002, DI-ADMN-81249C, Meeting Agenda; CDRL A/B/C/D/E003, DI-ADMN- 81250C, Meeting Minutes; CDRL A/B/C/D/E004, DI-MGMT-81605, Briefing Material)

4.6.3 In-Process Review (IPR) of the TDP

If applicable, the Contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in each TDP. The IPR shall be conducted only after the Contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review.

IPR may be scheduled when data has reached the 50% completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR). Concurrent with the IPR, the contractor shall submit four (4) representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752). These representative samples shall consist of the Native, Neutral, Word Searchable PDF, HPGL, Metadata Spreadsheet, BOM, Gerber Data, and Software/memory Device Data. The Contractor shall notify AFLCMC/LZPEM a minimum

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 10 of 56 of 30 days prior to the anticipated date of completion point. The IPR shall focus on the Contractor's progress in the preparation of the TDP. The Contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The Contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review.

If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility. (CDRL A/B/C/D/E002, DI-ADMN-81249C, Meeting Agenda; CDRL A/B/C/D/E003, DI-ADMN-81250C, Meeting Minutes; CDRL A/B/C/D/E004, DI-MGMT-81605, Briefing Material)

4.6.4 Relationship of Contractor with Subcontractors/Vendors

The Contractor shall levy on sub-contractors and sub-vendors the same requirements for TDPs and data rights as are levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.

4.6.5 Engineering Data Updates and Revisions

The Contractor shall (and shall cause subcontractors and vendors to) provide updates and maintain engineering data for the item(s) designed/created/modified/produced and funded by this contract and shall incorporate all changes in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 days after engineering release/Air Force concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.

c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media.

d. Revisions to existing engineering drawings/models and associated lists and other documentation to be included in the TDP for which the contractor is the current design activity shall result in the delivery of the entire revised document and associated data file. For example, when a portion of a document is revised the entire document shall be delivered.

Recommendations of changes to technical data not produced within this PWS shall be provided to the COR.

4.7 TECHNICAL ORDER (TO) SOURCE DATA

Technical Order research and analysis source data in contractor format shall be delivered for technical review NLT 30 calendar days after completion of analysis or investigation. Government review comments will be provided NLT 20 calendar days after submittal of draft. Final source data shall be submitted NLT 20 calendar days after receipt of Government comments. The Contractor will not be required to provide formal submissions of TO-formatted pages or supplements unless there is a separately negotiated EI and a Technical Manual Contract Requirements (TMCR) CDRL is added to the contract. (CDRL A/B/C/D/E00B, DI-MISC-80711A, Scientific and Technical Reports)

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 11 of 56

4.8 PROGRAM MANAGEMENT

4.8.1 The Contractor shall assign a qualified Program Manager to plan and execute the tasks required. The Engineering Program Manager shall be the single point of contact for the Government.

4.8.2 The Program Manager assigned shall:

a. Understand in detail the contractual requirements, terms and conditions of awarded and proposed tasks.

b. Assign, track progress and review performance in relation to the latest approved Program Management Plan (PMP).

c. Review all deliverables for accuracy and completeness.

d. Hold a Kick-Off Meeting (KOM) once contract is awarded.

e. Hold bi-weekly Program Coordination calls, to discuss urgent Contract, Program and

Engineering topics.

f. Hold Semi-Annual Program Management Reviews (PMRs).

4.8.3 The Contractor shall submit status reports. The Contractor shall provide a summary and status of work being performed during the reporting period to include funds expended, progress in relation to the latest approved PMP, cost and budgeted work, and all analyses. (CDRL A/B/C/D/E001, DI- MGMT-80368A/T, Status Report; CDRL A/B/C/D/E005, DI-MGMT-81797/T, Program Management Plan; CDRL A/B/C/D/E007, DI-MGMT-81468A, Contract Funds Status Report

(CFSR))

4.8.4 The Contractor’s Program Manager shall hold Technical Interchange Meetings (TIMs) as necessary with Government personnel. (CDRL A/B/C/D/E002, DI-ADMN-81249C, Meeting Agenda; CDRL A/B/C/D/E003, DI-ADMN-81250C, Meeting Minutes; CDRL A/B/C/D/E004, DI- MGMT-81605, Briefing Material)

4.8.5 Engineering Task Planning and Priority Management

The Government and the Contractor will establish a Engineering Investigation Working Group (EIWG) for task and priority planning meetings for each of four Engineering discipline teams (Structures, Mechanical Systems, Avionics & Software, Systems Engineering), either in person or virtually as mutually agreed quarterly. Required participants include: Engineering (technical) and the appropriate IPT/Project leads. The product of the task planning meeting will be a LM TES task list by discipline, including priority, revised and maintained with updates from each quarterly session. The Contractor shall include the current TES task list in the Monthly Status Report.

a. CLIN where the work will be performed

b. Primary Contractor engineering IPT/Project lead to perform the work

c. SPO cognizant IPT/Project lead

d. Desired objective and deliverable of the task

e. Overall and task objective deliverable if task is part of a phased project

f. Contractor-estimated hours to meet objective and known costs

g. Next step

h. SPO Need Date and LM ECD

i. State: Planning, In Work, Complete or On Hold designation

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 12 of 56

The Government and the Contractor engineering teams shall exchange detailed task coordination memoranda via LM EDCS program dropbox area (Correspondence folder, with Govt to LM and LM to Govt subfolders). For example, Govt may send ECM with technical background on aircraft issue to LM for review and discussion in advance of EIWG for task planning; LM may send ECM to Govt for heading check on analysis tasking or to request feedback.

Any urgent tasking or re-prioritization efforts shall be coordinated through an out-of-cycle EIWG.

4.8.6 The Contractor shall submit Project Plans via Engineering Services Memorandums (ESMs) and sub-ESMs for each task order inclusive of all Cost Reimbursable Contract Line Item Numbers (CLINs), with the exception of the TDS, Material and Travel CLINs. Initial PMP and ESMs shall be submitted concurrently no later than 60 calendar days after award of task order with updates made on a quarterly basis. For individual taskings, the ESM shall, at a minimum, include:

a. Estimated total man-hours and/or estimated cost of services, materials and equipment;

b. Summary level description of each task in the approved TES task list, deliverable, expected milestone and estimated period of performance or completion date; and

c. Assumptions, issues and concerns with associated recommendations.

Quarterly changes to the approved Project Plan baseline shall be submitted by the Contractor to the PCO/COR for approval prior to enacting any change. Changes to the Project Plan baseline requiring approval include: deletion or deferral of previously approved project plans, a change in the estimated total man-hours and/or estimated cost, a change in the task description and/or deliverables, and/or a change in the estimated completion date. If a project is expected to exceed the previously estimated total man-hours or estimated cost, then the updated ESMs shall reflect both the increased project plan and the project plan from which the hours/cost are taken and any impacts. Only urgent updates to Project Plans stemming from immediate safety impacts or mishaps may be enacted outside of the quarterly update for ESMs and PMP. (CDRL A/B/C/D/E005, DI-MGMT-81797/T, Program Management Plan; CDRL A/B/C/D/E006, DI-MISC-80748/T, Engineering Services Memorandum)

4.8.7 Prepare and present briefings to management on engineering services support performed under this contract. (CDRL A/B/C/D/E003, DI-ADMN-81250C, Meeting Minutes; CDRL A/B/C/D/E004, DI-MGMT-81605, Briefing Material)

4.8.8 Support various reviews, working groups and boards (for example, quarterly Computer Resource Working Group, semi-annual/annual Aircraft Information Working Group, Configuration Control Board (CCB), annual Product Improvement Working Group, and other meetings) related to tasks under this contract.

4.9 TRAVEL

Contractor personnel may be required to travel to perform tasks within this PWS, tasks within the approved TES task list or as directed by the Government. Travel may be within the Continental United States (CONUS) or Outside the Continental United States (OCONUS). All travel shall be approved in advance by the authorized AFLCMC/WLSK PCO no less than five business days in advance of departure for a routine tasking and no less than 24 hours prior to travel for an urgent tasking. The Contractor shall submit a bulk travel request for planned ordering period requirements at the beginning

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 13 of 56 of each period. The Contractor shall identify travel for annual or recurring support for conferences, SPO meetings and base visits separately from unplanned but anticipated activities in support of aircraft troubleshooting and engineering investigations as tasked by the SPO. Travel by the Contractor shall be conducted in accordance with FAR 31.205-46, Travel Costs and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

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

5.0 TECHNICAL & ENGINEERING SERVICES

5.1 ASIP

The Contractor shall support ASIP to maintain the structural integrity of the C-5 aircraft and manage the economic life cycle costs. These efforts shall meet the intent of the most recent revision of MIL- STD-1530D, Aircraft Structural Integrity Program, and JSSG-2006, Aircraft Structures. Tasks involved include, but are not limited to, structural analysis, maintaining and updating the Force Structural Maintenance Plan (FSMP) and Durability and Damage Tolerance Analysis (DADTA). To accomplish these functions the Contractor shall have capability to perform static, fail-safe, linear and non-linear finite element, residual strength, probabilistic risk, DADTA and other airframe design analyses.

5.1.1 FSMP

The Contractor shall maintain the currency of the FSMP for the C-5 fleet. The updated plan shall be in accordance with the guidance in MIL-STD-1530D, and JSSG-2006. The FSMP shall provide a comprehensive evaluation of the structural requirements versus existing/ongoing inspections, procedures and operational usage. Additional analysis may be required to ensure optimal inspection intervals.

The Contractor shall maintain the FSMP to identify inspection, repair and modification requirements including criteria, schedules and procedures for use at field or depot levels. The FSMP shall contain recommendations concerning the life of critical parts, inspection methods and procedures required to maintain safety, inspection intervals and the rationale behind them and recommended modifications or replacements. The FSMP shall be updated by the contractor no later than 30 calendar days, or a mutually agreed completion date.

As structural issues arise, the Contractor shall perform detailed linear and non-linear finite element analysis, and performing static, fail-safe, risk and damage tolerance analyses to determine their safety and economic impact on the fleet and suggested fleet management actions to mitigate risks.

This analysis is the basis for updates to the FSMP. Analysis shall be in accordance with MIL- STD-1530D and JSSG-2006. The FSMP shall be updated by the contractor no later than 30 calendar days, or a mutually agreed completion date,. (CDRL A/B/C/D/E00A, DI-GDRQ-80650, Design Data and Calculations; CDRL A/B/C/D/E00B, DI-MISC-80711A, Scientific and Technical Reports; CDRL A/B/C/D/E00D, DI-SESS-82039/T, Force Structural Maintenance Plan (FSMP))

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 14 of 56

The Contractor shall provide engineering and technical support for the C-5 Non-Destructive Inspection (NDI) program as directed by the ASIP Manager.

The Contractor shall support the ASIP Manager as required for structural analyses and customized composite repairs of primary structure, including use of finite element modeling. (CDRL A/B/C/D/E00A, DI-GDRQ-80650, Design Data and Calculations; CDRL A/B/C/D/E00B, DI- MISC-80711A, Scientific and Technical Reports)

The Contractor shall deliver updates to FSMP in a format that is exportable to the AFIRM website as new analyses are completed.

The Contractor shall submit FSMP documentation as part of the ASIP report. The FSMP shall be updated by the contractor no later than 30 calendar days, or a mutually agreed completion date, after a proposed change is approved by COR.

(CDRL A/B/C/D/E00B, DI-MISC-80711A, Scientific and Technical Reports; CDRL A/B/C/D/E00D, DI-SESS-82039/T, Force Structural Maintenance Plan (FSMP); CDRL A/B/C/D/E00G, DI-NDTI- 80566A, Test Plan; CDRL A/B/C/D/E00H, DI-NDTI-80603A, Test Procedures; CDRL A/B/C/D/E00J, DI-NDTI-80809B, Test/Inspection Report)

5.1.2 ASIP Master Plan

The C-5 ASIP Master Plan shall be reviewed and updated, at a minimum, annually throughout the service life of the aircraft as required per MIL-STD-1530D, paragraph 5.1.1. The C-5 Master Plan shall incorporate all C-5 Mission Design Series into subject document and shall be exportable to AFIRM. The ASIP Master Plan shall, at a minimum, consist of the followings sections:

Introduction (e.g. General Information, Aircraft Background, Aircraft Description, Weight and Operating Limitations)

Summary (e.g. General Information, Analysis, Testing, Data Recording Programs, Data Recording Systems, Tracking Programs)

ASIP Tasks (IAW MIL-STD-1530D, Section 1.2) A. Design Information (Task I) B. Design Analysis and Development Testing (Task II) C. Full-Scale Testing (Task III) D. Certification and Force Management Development (Task IV) E. Force Management Execution (Task V)

The ASIP Master Plan shall maintain a revision history and clearly identify any changes in current documentation with past releases of the subject document. The Contractor shall submit the ASIP Master Plan (Appendices included) annually.

(CDRL A/B/C/D/E00C, DI-SESS-81956A/T, Aircraft Structural Integrity Program (ASIP) Master Plan)

5.1.3 ASIP Scientific and Technical Reports

5.1.4 The Contractor shall submit individual ASIP engineering reports generated from tasking

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 15 of 56 performed under this PWS.as requested by C-5 ASIP Manager. (CDRL A/B/C/D/E00B, DI- MISC-80711A, Scientific and Technical Reports)

5.1.5 Final ASIP Report

The Contractor shall submit a final ASIP engineering report annually. Report shall document the results of all significant analyses and studies conducted during ordering period, including those conducted under ASIP Data Integration (Section 5.2), and any technical drawings generated, and contain as appendices Individual Aircraft Tracking (IAT), Loads/Environmental Spectra Survey (L/ESS), FSMP and Structural Audit. (CDRL A/B/C/D/E00E, DI-MISC-80711A/T, Scientific and Technical Reports [Annual Report])

5.2 ASIP DATA INTEGRATION

Contractor efforts shall meet the intent of MIL-STD-1530D and JSSG-2006to maintain the structural integrity of the C-5 aircraft and manage the economic life cycle costs. Required ASIP Data Integration tasks include, but are not limited to, IAT, L/ESS and Structural Audits (See Para. 5.1.5).

5.2.1 Fleet Usage IAT

The Air Force will provide the Contractor all data required for IAT runs on a monthly basis. After receipt of data, the Contractor shall perform IAT monthly for each C-5 aircraft to track aircraft usage for the purpose of establishing and adjusting inspection, maintenance and repair intervals for each critical airframe location. IAT fleet or individual aircraft data shall be in a format that is exportable to the AFIRM website. Monthly IAT runs are completed within 30 days of receipt of data.

The C-5 IAT system currently resides on the Air Force computer facility system at OC-ALC. OC- ALC personnel are routinely operating the system. The Contractor shall provide support to OC- ALC in the operation of the IAT system as needed.

The Contractor shall utilize existing and modified IAT programs to produce coordinated output of IAT usage.

The Contractor shall review usage annually to identify and quantify fleet flying trends which may impact recommended structural inspections and fleet service life. The Contractor shall document the resultsof the analysis in the applicable monthly status report and recommended changes, if applicable.. Review shall be completed no later than 5 weeks after receipt of data for each annual period.

The Contractor shall monitor and process flight-by-flight usage data provided by the Government for completeness and accuracy and shall inform the ASIP manager and OC-ALC of erroneous data or other problems and document the results of the analysis in the applicable monthly status report.

Data corrections are the responsibility of the Government. Processing of the flight-by-flight data shall consist principally of assimilating the data into representative mission profiles and determination of usage statistics by individual aircraft, force average (all Mission Design Series) and operator (AMC and AFRC).

PR: FD2060-23-30952 PWS Revision: Basic CUI Page 16 of 56

The Contractor shall deliver an IAT report, computer programs and documentation on an annual basis if changes are made to the IAT programming. (CDRL A/B/C/D/E00B, DI-MISC-80711A, Scientific and Technical Reports; CDRL A/B/C/D/E00F, DI-IPSC-81756, Software Documentation)

(CDRL A/B/C/D/E00B, DI-MISC-80711A, Scientific and Technical Reports)

5.2.2 L/ESS

The Contractor shall support the AFLCMC/WLSE ASIP manager and OC-ALCin maintaining an effective L/ESS program. L/ESS data resides in parallel at OC–ALC and at the Contractor.