FD2060-23-33442 SES PWS.pdf

PR: FD2060-23-33442 PWS REVISION: 0

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

SPECIAL OPERATIONS FORCES (SOF) PERSONNEL RECOVERY (PR) FIXED

WING (FW) SUSTAINMENT ENGINEERING SUPPORT

Purchase Request Number

FD2060-23-33442

26 April 2024

Prepared by: AFLCMC/WIUA 370 Richard Ray Blvd

Robins AFB, GA 31098-1670

TABLE OF CONTENTS

1.0 DESCRIPTION OF SERVICES 3

2.0 SERVICES SUMMARY 3

3.0 GOVERNMENT PROPERTY 4

4.0 TECHNICAL REQUIREMENTS 5

5.0 PERIOD AND PLACE OF PERFORMANCE 8

6.0 GENERAL INFORMATION 13

7.0 CONTRACTOR TASKING/ RESPONSIBILITIES 17

8.0 APPENDIX 24

1.0 Description of Services

The contractor shall provide cyber support, continuing engineering services, structural support, analytical engineering studies, prototyping, and structural testing to support the SOF/PR C-130 aircraft and systems. The contractor shall provide short notice/emergency reports for critical engineering support issues. Existing aircraft structural models and usage databases will be updated and improved to reflect the current mission profiles, hardware configurations, and usage.

As tasked, the contractor shall also continue the analysis of several known problematic areas on SOF/PR C-130 aircraft. The contractor shall conduct studies and data acquisition as tasked by the Government. The contractor shall analyze and provide recommendations for the airworthiness, configuration management and system safety processes for all SOF/PR C-130 platforms and systems. The contractor shall provide for the study and analysis of other as yet unknown engineering issues found during routine maintenance and operations of SOF/PR C-130 aircraft and systems. Finally, the contractor shall provide technical and engineering support to ongoing activities of SOF/PR C-130 System Program Office (SPO).

1.1 Objective(s): This PWS describes the Sustaining Engineering support for the WIU Fixed Wing Branch. These services are required to maintain an acceptable operational functionality and survivability of both physical and functional integrity of the avionics and mechanical elements of SOF/PR unique aircraft systems. The contractor shall provide Cyber support, Mechanical Equipment and Subsystems Structural Integrity Program (MECSIP) support, and Avionics Integrity Program (AVIP) and Electrical Wiring Interconnect System Integrity Program (EWISIP) support for SOF/PR C-130 aircraft and sub-systems. The contractor shall provide short notice/emergency reports for critical engineering support issues and without delays for MECSIP, AVIP, EWISIP, engineering support requests, studies, and analyses.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by addressing, mitigating and reducing operational risk for all SOF/PR specific managed C-130 aircraft and equipment that would inhibit the aircraft from performing their primary missions.

Further, these services will meet the Department of Defense (DoD) requirement to maintain compliance with current cyber security directives, the Risk Management Framework (RMF), and the Air Force mandated Integrity programs.

1.3 Background: Previous engineering sustainment contract (FA8509-20-D0015) provided continuing engineering services, structural support, analytical engineering studies, prototyping, and structural testing to support the SOF/PR Legacy C-130s and EC-130J systems. The contractor provided a short notice/emergency report for critical engineering support issues.

Existing aircraft structural models and usage databases were updated and improved to reflect the current mission profiles, hardware configurations, and usage. As tasked, the contractor provided analysis of several known problematic areas. The contractor conducted studies and data acquisition as tasked by the Government for the airworthiness, configuration management and system safety processes for all platforms and systems. The contractor also provided for the study and analysis of other engineering issues found during routine maintenance and operations of aircraft and systems. The contractor provided cyber sustainment support for mission-based risk assessment and risk management framework and technical and engineering support to multiple activities for the SPO.

2.0 SERVICES SUMMARY

Performance Objective PWS Reference

Performance Threshold

Provide short notice/emergency report for critical engineering support issues for any Class A Mishap(s)

4.2 4.6 7.1.8

The contractor shall provide time critical response within five business days of short notice/emergency request for engineering support resulting from a reportable mishap classification criteria Class A Event.

Response will be to the degree necessary to determine pertinent facts and circumstances relating to the occurrence, to identify factors and recommend actions to prevent recurrence of a similar event.

Quality of Contract Data Requirements List (DD Form 1423-1) (CDRL) deliverable

5.2 No more than one rejection of any

deliverable per quarter. The Government will reject a deliverable if two or more technical errors or five or more minor errors are found within the deliverable and not corrected within five business days of notification. 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 defined as a typographical or grammatical error. Rejections shall be corrected and resubmitted in accordance with the (DD Form 1423-1,CDRL).

Receipt of CDRL deliverable

5.3 No more than one late submission(s) of any

deliverable(s) per quarter. The contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and may negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

3.0 GOVERNMENT PROPERTY

3.1 Government Property: All Government Furnished Property (GFP) or Contractor Furnished Material (CFM), equipment, facilities and services shall be managed in accordance with Federal Acquisition Regulation (FAR) Part 45, Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, and the applicable contract clauses. The Government will retain ownership of all GFP provided for this effort. Unless otherwise specified, the contractor shall return all GFP for this effort at the end of the contracted period of performance unless otherwise specified by the Contracting Officer. The contractor shall request disposition and shipping instructions from the Program Manager (PM) through a letter or official e-mail to the Contracting Officer or Contracting Officers Representative (COR).

3.2 Government Property to be Provided: Government property will be provided in accordance with the GFP attachment, attached to the task order.

3.3 Reporting of Government Property: The contractor shall create and maintain records of all property accountable to the contract, including GFP and Contractor-Acquired Property (CAP) in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

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 property useless for its intended purpose. Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or authorized destructive testing.

Unless otherwise specified, loss of Government property does not include authorized usage of low priority consumable material, such as common hardware.

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

3.6 Government System(s): The Government will provide contractor personnel access to system(s) necessary to perform tasks under the contract. Specific systems may include but not limited to Reliability & Maintainability Information System (REMIS), Joint Engineering Data Management Information Control System (JEDMICS) and all other Government systems required to update Automated Inspection, Repair, Corrosion & Aircraft Tracking (AIRCAT) and Aging Fleet Integrity & Reliability Management Multi-Platform (AFIRM-M).

4.0 TECHNICAL REQUIREMENTS

4.1 Cyber Support: The contractor shall document processes to achieve and maintain Authorization to Operate (ATO), Risk Management Framework (RMF) artifact development and https://piee.eb.mil/piee-landing/ https://piee.eb.mil/piee-landing/ other cyber related artifact development such as white papers and research exploitation of aircraft systems. The contractor shall provide engineering services creating and maintaining aircraft baseline configuration testing center/lab, testing of avionics equipment such as testing Line Replacement Unit (LRU)’s for vulnerabilities, penetration testing of LRU’s and other aircraft systems. The contractor shall document results of vulnerabilities and penetration testing, technical data support, development of solutions for vulnerable and exploited LRU’s, proof of concept, hardening techniques and standards, third part assessment of aircraft LRU’s, information systems and sub-systems. (CDRL A-H00A, DI-MGMT-82135A)

4.2 MECSIP, AVIP and EWISIP: The contractor shall provide data pertaining to structural support, electrical wiring interconnection system, analytical engineering studies, modeling, and structural testing support. The contractor shall collect and analyze aircraft reliability data to further maximize weapon system safety, reliability, and availability. The contractor shall maintain existing aircraft structural models and update databases to improve and reflect the current mission profiles, hardware configurations, and usage. The contractor shall provide short notice/emergency structural reviews and studies to respond to events that impact mission readiness. As directed by the Government, the contractor shall identify and analyze those areas known to be fatigue critical, corrosion prone, highly stressed, and poorly designed from a structural standpoint, as well as other areas needing study. (CDRL A-H007, DI-MISC-80508B)

4.2.1 Structural Model: The contractor shall develop, maintain and deliver structural models of SOF/PR C-130 aircraft.

4.2.1.1 The contractor shall maintain and refine as needed, the Global Finite Element (FE) models for all SOF/PR C-130 aircraft.

4.2.1.2 The contractor shall initiate development of additional Global FE models of SOF/PR C130 aircraft with one (1) major component annually.

4.2.1.3 FE models shall be used in support of engineering tasks listed in this document.

4.2.1.4 FE models shall be updated, when necessary, as a result of the studies performed.

4.2.1.5 FE models shall incorporate best practices for mesh sizing, attachments, and conform to methods and formats used in previously developed Global C-130 models. Configuration control shall be maintained as a result of changes made to the non SOF/PR C-130 aircraft. (CDRL

AH008, DI-IPSC-81488)

4.2.3 Modeling

The contractor shall develop improved design solutions and proof of concepts. The improved design solutions shall support the following:

• Eliminate cracking causes

• Improvement of damage tolerance

• Improvement of maintenance operations

The contractor shall provide scanning and modeling of complex components to account for documentation gaps in loft data, contour data, and antiquated drawing details. The contractor shall provide these services in support of efforts and to support modeling of components. Models shall be made available in Initial Graphics Exchange Specification (IGES) format.

(CDRL A-H004, DI-NDTI-80809B)

4.2.4 SOF/PR C-130 MECSIP and AVIP Master Plan: The contractor shall update the MECSIP and AVIP Master Plans that will cover the SOF/PR related C-130 subsystems In Accordance With (IAW) MIL-STD-1798D and MIL-STD-1796A These master plans will identify all subsystems and equipment covered by SOF/PR C-130 MECSIP and AVIP, establish analysis prioritization, develop a SOF/PR unique subsystem Reliability Centered Maintenance (RCM) analysis completion tracking/schedule, and detail how SOF/PR RCM analyses are to be integrated with the Tactical Airlift C-130 RCM analyses. At the conclusion of development of the SOF/PR portion of the C-130 MECSIP and AVIP Master Plans, the contractor shall review all previous C-130 RCM analyses for SOF/PR unique issues and recommend options to implement the approved actions. (CDRL A-H007, DI-MISC-80508B)

4.3 Software Development: The contractor shall develop and integrate software packages in support of cybersecurity, MECSIP, AVIP, EWISIP efforts. Examples of possible use-cases include, but are not limited to; software updates to existing engineering tool-kits, AI/ML code to discover vulnerabilities, identify trends, risk in aircraft systems and bugfixes in existing engineering tool-kits. The contractor shall follow a secure code development process and provide source code, code scans, and code configuration data to the Government as required. (CDRL A-H008, DI-IPSC-81488).

4.4 Computer Software Product: The contractor shall deliver any software product on media of sufficient size to contain all products from the Task Period. All deliverables shall be at the level of detail sufficient to provide to a developer with comparable levels of expertise for further development. (CDRL A-H008, DI-IPSC-81488)

4.5 Aging Fleet Integrity and Reliability Management system (AFIRM-M): The contractor shall modify and maintain SOF/PR C-130 AFIRM-M database to include current Time Compliance Technical Order (TCTO) and modification implementation status; Reliability- Centered Maintenance (RCM), Mechanical Structural Integrity Program (MECSIP), and other available data (especially as it relates to SOF/PR-peculiar aircraft configurations and including but not limited to IR shields, all guns, counter-measures dispensers, and SOF/PR-specific avionics/electronics/electronic warfare hardware and configurations and cybersecurity issues.) Modifications to AFIRM- M shall include automation of data pulls from the various sources to the maximum extent practical. Modification to AFIRM-M shall also include development of AFIRM-M tools for TCTO configuration status updates, reporting for SOF/PR-specific concerns such as gunfire rates and firing orbit dwell time (if practical), and other tools to support SOF engineering monthly status reporting.

4.6 Technical Study/Services: The contractor shall perform independent technical studies as directed by the SPO to support all SOF/PR C-130 aircraft as outlined in this PWS. The intent of the studies is to provide the Government with an assessment of the specified areas of interest and an indication of the magnitude of the problem in terms of margin of safety, cycles to failure, cycles to initial detectable crack length, estimated hours to failure, estimated hours to initial detectable crack length, and other useful technical parameters (as appropriate to the structure or system being analyzed). This assessment shall also provide the Government with recommendations to resolve the problem areas, such as inspection intervals, potential repair methods, or, if requested, potential design changes. The contractor shall summarize all studies in a technical report(s) as directed by the Government. These technical reports shall discuss the contractor’s analysis and any technical solution(s) being recommended. Included in each such report shall be a description of each of the assumed and known loads, the assumed and known initial flaws, and the technical references or reports (if any) that brought the contractor to these conclusions. These technical reports shall discuss the contractor’s analysis and any technical solution(s) being recommended. Included in each such report shall be a description of each of the assumed and known loads, the assumed and known initial flaws, and the technical references or reports (if any) that brought the contractor to these conclusions. Contractor shall build a/or multiple prototype(s) based on these finding to correct or resolve the issue or flaw identified from such studies or analysis.

Prototypes shall also be built based on field request for system/equipment flaws identified from the using organization. (CDRL A-H004, DI-NDTI-80809B)

4.6.1 Prototyping: The contractor shall develop prototype hardware as required to validate and test alternative designs, integrate equipment into SOF/PR C-130 aircraft, update aircraft trainers, update support equipment, and conduct qualification testing that shall be witnessed by Government personnel. This shall include supporting T-1 and T-2 test requirements for proposed modifications. Prototype hardware shall be production representative documented by engineering drawings and specifications. The contractor shall obtain design concept approval of all assembly and installation drawings prior to the prototype installation. Prototype installation will be accomplished for the purpose of proving the validity of the contractor’s design, verification of the kit component design, completeness of kit contents, checking Electromagnetic Effects (EME), testing of system performance, and verification of the preliminary TCTO. (CDRL

AH006, DI-SESS-81000F/T)

4.7 Developmental Design Drawings and Associated Lists: Per DoD policy, the contractor shall provide “paperless” electronic or digital data deliveries unless otherwise directed by the Government. Specific CDRL items contain email and physical delivery addresses for digital and electronic deliveries. Unless otherwise directed by the Government, all documents shall be submitted in a Microsoft Office®- compatible format. Exception: MS project files shall be exported to MS Word, MS Excel, Adobe PDF, or other common file format, at Government request, and the Government will coordinate with the contractor for delivery of Finite Element

Analysis (FEA) and other engineering models/data. At the Government’s discretion, drawings/models may be delivered in AutoCAD format or other format to be determined prior to the delivery of draft drawings. (CDRL A-H006, DI-SESS-81000F/T )

4.7.1. Engineering Data: The contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. 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). The TDP shall provide the necessary 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 or recourse to the original design activity or any third party. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). This shall include software and all test requirement documentation data required to test systems, subsystems and components. 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 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-2017, Appendix B, sections B6 through B9.1 and Appendices C, D, E, and F 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 this task to create and deliver Product Engineering Design Data and Associated Lists (Engineering Data) under this contract. Data set classification code marking IAW Appendix F of ASME Y14.100-2017 is required. 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), reference attached DD Form 1423-1 Block 16. The contractor shall submit an engineering drawing tree identifying all system, subsystem and equipment drawings as part of the drawing package prior to Critical Design Review (CDR). (CDRL A-H006, DI-SESS- 81000F/T)

4.7.2 Engineering Data Guidance Conference: The contractor shall support and cochair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. 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:

(CDRL A-H002, DI-ADMN-81250C)

a. Understanding of all CDRL requirements, applicable 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.

Note: Guidance Conference may be held in conjunction with other meetings or conferences.

4.7.3 In-Process Review (IPR) of the TDP: The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the 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% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., Preliminary Design Review (PDR), Critical Design Review (CDR).

Concurrent with the IPR, the contractor shall submit four representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752), These 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 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-H002, DI-ADMN-81250C)

4.7.4 Relationship of Contractor with Subcontractors/Vendors: The contractor shall levy on sub-contractors and sub-vendors the same requirements for TDPs 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.7.5 Engineering Data Updates and Revisions: The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/developed/modified/produced and funded by this contract for the life of 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.

4.8 Configuration Management (CM)/ Airworthiness / System Safety (SS): IAW applicable government standards and Air Force Instructions (AFI), the contractor shall analyze and provide recommendations for the airworthiness, configuration management and system safety processes for all SOF/PR C-130 platforms. The contractor shall provide for the study and analysis of other as yet unknown engineering problems found during routine maintenance and operations of the aforementioned aircraft. (CDRL A-

H004, DI-NDTI-80809B)

4.9 Engineering Data: Product Data shall reflect the approved, tested and accepted configuration of the defined delivery item. All engineering product definition data created as a result of this contract shall be considered a part of the Test Data Package. This data includes, but is not limited to, CAD data, models, model-based definition data sets and Gerber data. (CDRL A-H008, DI-IPSC-81488)

4.10 Site Surveys: The contractor shall supplement its efforts under this task with site surveys and tests and surveys of actual aircraft related equipment and components as required with prior approval of the Government.

4.11 Raw Data Requirements: Time and spatial-domain tabular-type data (temperature distributions, load/stress vs. time, accelerometer vs. time, etc.) derived from instrumentation efforts shall be delivered to the Government in table format and in a Microsoft Word-compatible file type). The contractor shall not deliver raw numerical data as scanned images, Portable Document Format (.PDF) files, or in graph/chart format without the actual data points. Should the volume of data make it impractical to deliver by email, the contractor shall consult with the Technical Point of Contact for alternate digital formats and delivery options. (CDRL A-H004, DI-NDTI-80809B)

4.12 Technical Orders: The contractor shall reference USAF Technical Orders as additional technical data to supplement drawings in determining the details of the area to be analyzed. The contractor shall notify the Government of any technical errors or discrepancies discovered in those Technical Orders. A brief summary of these errors shall be included in the contractor’s report; however, the contractor shall not modify, add to, subtract from, or publish any new or existing Technical Order (T.O), or any portion of a T.O. in performance of this task order. (CDRL A-H004, DI-NDTI-80809B)

5.0 PERIOD AND PLACE OF PERFORMANCE

5.0.1 Contract/Order Period of Performance

The period of performance for this requirement will extend from 22 July 2024 – 21 July 2029

• Basic: 22 July 2024 – 21 July 2025

• Ordering Period 1: 22 July 2025 – 21 July 2026

• Ordering Period 2: 22 July 2026 – 21 July 2027

• Ordering Period 3: 22 July 2027 – 21 July 2028

• Ordering Period 4: 22 July 2028 – 21 July 2029

5.0.2 Place of Performance: The place of performance for this effort shall be primarily at the contractor’s facility. However, the contractor may be required to travel, as determined by the Government, to several installations, both in the Continental United States (CONUS) and Outside the Continental United States (OCONUS).

5.1 Contract Data Requirements List(s) (CDRL)

Document Identifier Base Year

Document Identifier Ordering Period 1

Document Identifier Ordering Period 2

Document Identifier Ordering Period 3

Document Identifier Ordering Period 3

Document Identifier Ordering Period 4

Document Identifier Ordering Period 5

Document Identifier Ordering Period 6

Data Item Description (DID)

Title PWS Reference(s)

A001 B001 C001 D001 E001 F001 G001 H001 DI-ADMN-81373 Presentation Material 7.1.1

A002 B002 C002 D002 E002 F002 G002 H002 DI-ADMN-

81250C Meeting Minutes 4.7.2, 4.7.3, 7.1.2

A003 B003 C003 D003 E003 F003 G003 H003 DI-MGMT-

81791/T

Key Events Schedule 7.1.3

A004 B004 C004 D004 E004 F004 G004 H004 DI-NDTI-80809B Test/Inspection Report 4.2.3, 4.6, 4.8, 4.11, 4.12, 7.1.7,7.1.8

A005 B005 C005 D005 E005 F005 G005 H005 DI-MGMT-

80368A Status Report 7.1.5, 7.2.1

A006 B006 C006 D006 E006 F006 G006 H006 DI-SESS-

81000F/T

Product Engineering Design Data and Associated Lists

4.6.1, 4.7, 4.7.1

A007 B007 C007 D007 E007 F007 G007 H007 DI-MISC-80508B Technical Report – Study/Services

4.2, 4.2.4, 7.1.7, 7.1.8, 7.2.2, 7.2.4, 7.2.7, 7.2.8, 7.2.9

A008 B008 C008 D008 E008 F008 G008 H008 DI-IPSC-81488 Computer Software Product

4.2.1.5, 4.3, 4.4, 4.9

A009 B009 C009 D009 E009 F009 G009 H009 DI-MGMT-

81453B

Data Accession List 7.1.4

A00A B00A C00A D00A E00A F00A G00A H00A DI-MGMT-

82135A

Naval Aviation Cybersecurity Risk Management Framework (RMF) Assessment and Authorization Products, and CYBERSAFE Objective Quality Evidence, Assessment & Authorization (A&A) Products

4.1

5.2 Quality of CDRL Deliverable: There shall be no more than one total rejection of deliverables per quarter. The Government will reject a deliverable if two or more technical errors or five 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 defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted IAW applicable

CDRL.

5.3 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area Work Flow (WAWF) to the Government PM listed in the CDRL. There shall be no more than one late submission(s) of any deliverable(s) per quarter. The contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and shall negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

5.4 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.5 Travel: The contractor may be required to travel to Government installations or to other contractor facilities. Routine travel requests shall be submitted to the Government PM/COR for review no later than 10 Business Days prior to the date of departure; routine requests that do not meet this minimum requirement will not be approved. Urgent travel requests may be submitted for approval in a shorter timeline and will be considered on a case by case basis; urgency of travel will be determined by the Government. All travel requests must be approved by the PCO prior to departure. The contractor shall provide a list of any projected travel requirements. The contractor shall be responsible for arranging all travel of contractor personnel during the period(s) of performance. The contractor shall use the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles.

6.0 GENERAL INFORMATION

6.1 Continuation of Mission-Essential Services During a Crisis: The Functional Service Manager (FSM) has determined these services are not mission-essential and will not continue in the event of a crisis.

6.2 Security Requirements:

6.2.1 Knowledge and generation of classified information and Controlled Unclassified Information (CUI) are required for performance of the contract/order. The contractor shall ensure applicable contractor personnel have security clearances at the Top Secret/Sensitive Compartmentalized Information level.

6.2.2 Security Regulations: The contractor shall ensure personnel, information, system, property, facility and international security requirements are met. The contractor shall comply with Government security regulations including, but not limited to, 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM); Department of Defense Manual (DoDM) 5200.02_Air Force Manual (AFMAN) 16-1405_AF Guidance Memorandum (AFGM) 2022-01, Personnel Security Program; DoD 5220.22-M, NISPOM; DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual 5205.02, DoD OPSEC Program Manual; and Robins Air Force Base Integrated Defense Plan (RAFB IDP) 31-101; DoD Instruction (DoDI) 5200.48_Department of the Air Force Instruction (DoDI) 16-1403.

6.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. The contractor shall ensure compliance with DoDD 5205.02E and DoD Manual 5205.02 to protect U.S.

Government interests. The contractor shall ensure contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

6.2.4 Communications Security (COMSEC): The contractor shall use only secure communications methods and equipment to transmit or otherwise transfer classified information and CUI in accordance with DoD 5220.22-M. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

6.2.5 Security Clearance: The contractor shall ensure applicable contractor personnel have security clearances at the Top Secret/Sensitive Compartmental Information level as well as Special Access Programs (SAP) for proper accomplishment of contract/order requirements. The security clearance shall be obtained in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified information and CUI and classified items.

NOTE: The contractor shall be responsible for obtaining proper employee security clearances.

Contractor’s inability to obtain proper employee security clearances shall not constitute an excusable delay in contract performance.

6.2.6 Security Incident or Violation: The contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified information and CUI.

6.2.7 Security of Contractor System(s): The contractor shall ensure the security of Automated Information System(s) (AIS) at the contractor’s facility to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of classified information and CUI.

6.2.8 Access to Government System(s): The Government will provide contractor personnel access to system(s) necessary to perform tasks under the contract/order. The contractor shall ensure contractor personnel who require access to an unclassified or classified Government AIS have the appropriate background check or security investigation conducted. The Government will provide system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract/order or transfer/termination of contractor personnel, the system account(s) will be closed.

6.2.9 Access to Government Facility: The contractor shall ensure contractor personnel who require access to a Government facility comply with the security requirements of the facility.

6.2.10 Access to Robins Air Force Base (AFB)

6.2.10.1 Background Check: In accordance with AFI 31-113, Installation Perimeter Access Control, all non-DoD personnel requiring frequent or recurring access to Robins AFB must have a background check completed by the 78th Security Forces Squadron (78 SFS)/S5P Visitor Control Center (VCC) or Base Defense Operations Center (BDOC) before they will be granted qualified base access.

6.2.10.2 Entry to Robins AFB: In accordance with RAFB IDP 31-101, contractor personnel granted qualified base access may receive installation entry and circulation privileges under limited circumstances or conditions. They do not have the authority to sponsor anyone for access to Robins AFB or vouch for anyone to enter Robins AFB.

6.2.10.3 Identification of Contractor Personnel Requiring Access: In accordance with RAFB IDP 31-101, a contractor awarded a contract/order that requires services to be performed on Robins AFB shall provide the badging agent and PCO a list of all contractor 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 personnel will require access to Robins AFB.

6.2.10.4 Defense Biometric Identification System (DBIDS) Identification (ID) Card: In accordance with RAFB IDP 31-101, contractor personnel requiring access to Robins AFB, but not Local Area Network ( LAN) access, shall complete the Robins AFB Access Affidavit to obtain a DBIDS ID card and return it to the badging agent. After verification by the badging agent, contractor personnel shall come to the VCC to claim their DBIDS ID card.

6.2.10.5 Common Access Card (CAC): In accordance with RAFB IDP 31-101, contractor personnel requiring access to Robins AFB and LAN access will be entered in the contractor Verification System (CVS) by the Trusted Agent (TA). The TA will email their user ID/password and instructions on accessing the Robins AFB public website to the contractor personnel.

Contractor personnel shall access the website and complete all applicable forms as directed.

After this process is completed, contractor personnel shall make an appointment with the closest facility to schedule and claim their CAC.

6.2.10.6 Loss of Card: In accordance with RAFB IDP 31-101, if contractor personnel lose their CAC, they shall notify the badging agent immediately.

6.2.10.7 Retrieval of Card(s): In accordance with RAFB IDP 31-101, the contractor shall notify the badging agent immediately upon contractor personnel being transferred/terminated.

The contractor is responsible for retrieving Contractor CAC(s) (including restricted/controlled area badges) upon transfer/termination of contractor personnel or completion/termination of the contract/order. The contractor shall return all retrieved CAC(s) to 78 SFS.

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

6.4 Agency Affirmative Procurement 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.

6.5 Safety Requirements

6.5.1 Contractor Environmental, Safety, and Occupational Health (ESOH) 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 DoDD 4715.1E, ESOH. The contractor shall establish and maintain a safety and health program detailed in a written contractor’s Safety and Health Plan. The contractor shall require all subcontractors to comply with required safety, health and fire standards.

6.5.2 Mishap Notification/Investigation: The contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or offduty 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.

In the event of a mishap, the contractor shall ensure the USAF is notified of the mishap. 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 (AFLCMC/SE). 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.

6.5.2.1. PCO,

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

6.5.2.3. The closest USAF base command post (to relay notification to AFLCMC/SE).

6.5.3 Voluntary Protection Programs (VPP): Contractor personnel performing work on a USAF installation shall participate in the local VPP.

6.5.4 VPP Description: In 1982, OSHA created the VPP to recognize and partner with worksites that implement exemplary systems to manage worker’s safety and health. These sites implement comprehensive Safety and Health Management Systems that exceed basic compliance with OSHA standards. VPP applies to all personnel at Robins AFB - civil servants (both bargaining and non-bargaining), active duty (officer and enlisted), reservists and contractor employees. The contractor shall ensure its employees and managers have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. The contractor, whether regularly involved in routine site operations or engaged in temporary projects such as construction or repair, shall follow the safety and health rules of the installation or VPP site.

Detailed information on VPP is available on the OSHA website at http://www.osha.gov/dcsp/vpp/index.html. The contractor shall access the site to ensure their understanding of VPP and how their performance is linked to the Air Force installation’s pursuit of VPP recognition.

6.5.5 Department of Labor (DoL) Inspection of Contractor Operations: The contractor is subject to DoL inspections and enforcement by OSHA health and safety officials while performing work on a Government installation. OSHA health and safety officials may access workplaces on Government installations at any time, scheduled or unscheduled, during regular work hours. OSHA health and safety officials must meet security requirements to enter restricted or classified areas. The contractor shall immediately notify the COR and the contracting unit’s Safety Office upon notification of a visit.

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

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

6.9 Trafficking in Persons: The contractor shall comply in accordance with the FAR 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. http://www.state.gov/j/tip

6.10 Service Contract Reporting (SCR): The contract does not meet the DoD Contract Reporting criteria or reporting dollar threshold; therefore, SCR does not apply.

7.0 CONTRACTOR TASKING/RESPONSIBILITIES

7.1 General Contractor Responsibilities

7.1.1 Presentation Material: The contractor shall deliver presentation material to the Government prior to any formal meeting. All scheduled meetings shall be reflected in the Key Events Schedule. Only the Kickoff Program Management Review (PMR), Mid-Point PMR and Closeout Meeting PMR, will be considered formal unless otherwise noted by the Government PM. Location of the meetings will be at the discretion of the Government, in the event that in person meetings are not an option, the contractor shall use suitable electronic means to host the meeting. (CDRL A-H001, DI-ADMN-81373)

7.1.2 Conference Minutes: The contractor shall document any formal meetings with minutes.

Location of the meetings will be at the discretion of the Government, in the event in person meetings are not an option, the contractor shall use suitable electronic means to host the meeting.

(CDRL A-H002, DI-ADMIN-81250C)

7.1.3 Key Events Schedule: The contractor shall submit a Key Events Schedule at the beginning of the period of performance and update every four months after first submission.

(CDRL A-H003, DI-MGMT-81791/T)

7.1.4 Data Accession List (DAL)

The contractor shall submit the DAL to the Government PM at the end of the PoP. This DAL shall contain the indexed list of all of the deliverables. The data contained on the DAL deliverable shall be organized by any logical fashion that the contractor deems necessary to allow its use by the Government as a reliable, organized, permanent list of work performed.

(CDRL A-H009, DI-MGMT-81453B)

7.1.5 Monthly Status Report (MSR): The contractor shall deliver MSRs in accordance with the accompanying CDRL. These reports shall cover the technical support provided by the contractor during the previous monthly reporting period and shall individually address all current efforts. The contractor shall, as applicable, provide updates regarding task status, deliverables, contract issues and actions, as well as anticipated future task requirements for the next reporting http://www.state.gov/j/tip http://www.state.gov/j/tip period. In all cases the contractor shall address financial status such as original budget vs funding remaining on task and the report shall include an overall funding burn rate of CLINS X001, X002 and X003 in and excel spreadsheet format. (CDRL A-H005, DI-MGMT-80368A)

7.1.6 Site Surveys: The contractor shall supplement its efforts under this task with site surveys and tests and surveys of actual aircraft related equipment and components as required with prior approval of the Government.

7.1.7 Aircraft Structural Analysis: The contractor shall evaluate current and proposed designs using analytical methods as directed by the Government PM. Types of analyses shall include but not limited to: FEA with static, Thermal, impact, or dynamic (shock, transient, and vibration) loading. Results of analyses shall include stress, strain, displacements, temperature, frequencies and modes of vibration. The Government anticipates seven analyses and tests per year based on projections of historical needs. All analysis of designs shall be documented in a report with supporting data. (CDRL A-H004, DI-NDTI-80809B A-H007, DI-MISC-80508B)

7.1.8 Repair Design, Analysis, and Testing: The contractor shall perform failure/damage analysis of aircraft structural members to determine the underlying causes. The contractor shall provide design, analysis, testing, modeling, and tooling support as necessary for repair or manufacture of structural components as directed by the Government based on the results of the structural analysis. (CDRL A-H004, DI-NDTI-80809B A-H007, DI-MISC-80508B )

7.2 Specific Contractor Responsibilities

7.2.1 Flight/Ground Testing Support: Contractor shall support design efforts with flight testing where required. Flight testing support will include test plan generation, AF Form 1067 Modification Proposal, where required, Configuration Control Board (CCB) support (where required), instrumentation selection/installation, and test monitoring. All tests shall be documented with a test report containing results, conclusions and recommendations, and supporting data. The contractor shall be capable of recording and processing strain, acceleration, thermal, analog, and data bus inputs for ground/flight testing. The contractor shall provide independent technical review of data/reports/designs.