27-30005_PWS (Draft).pdf

PR: FD2060-27-30005 PWS REVISION: 0 1

Distribution Statement: C

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GA 31098-1670

PERFORMANCE-BASED WORK STATEMENT

FOR

H-1 Sustaining Engineering Support Services

Purchase Request: FD2060-27-30005

2 April 2026

Prepared by:

AFLCMC/WIHBC

370 Richard Ray Blvd.

Robins AFB, GA 31098-1670

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors (Administrative or Operational Use) (2 April 2026). Other requests for this document shall be referred to USAF AFLCMC/WIHBC.

DRAFT

PR: FD2060-27-30005 PWS REVISION: 0 2

Revision History

Revision Date Changes Comment

0 2 April 2026 --Rev 0-- --Rev 0--

PR: FD2060-27-30005 PWS REVISION: 0 3

Table of Contents

1.0 Description of Services

1.1 Objective(s)

1.2 Benefit to United States Air Force (USAF)

1.3 Background

2.0 Services Summary

3.0 Government Property

3.1 Contractor Responsibility

3.2 Government Property to be Provided

3.3 Reporting of Government Property

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property

3.4.2 Reporting Loss of Government Property

3.5 Return or Retention of Government Property

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract Period of Performance

4.1.2 Place of Performance

4.2 Contract Data Requirements List(s) (CDRL)

4.2.1 Quality of CDRL Deliverable

4.2.2 Receipt of CDRL Deliverable

4.3 Engineering Services

4.3.1 Item Unique Identification

4.3.2 Packaging

4.3.3 Validation of Component Retirement Times (CRT)

4.3.4 Proprietary Data

4.3.5 Urgent/Routine Response

4.3.6 New/Unique Operational Requirements

4.3.7 Aircraft Sustainment and Reliability/Maintainability Support

4.3.8 Logistics Reachback Support

4.3.9 Engineering Data

4.3.10 Project Engineering Management

4.3.11 Flight Testing/Engineering Support

4.3.12 Other Services

PR: FD2060-27-30005 PWS REVISION: 0 4

4.4 Program Management

4.4.1 Monthly Status/Financial Report

4.4.2 Meetings

4.4.3 Travel

5.0 General Information

5.1 Continuation of Mission-Essential Services during a Crisis

5.2 Security Requirements

5.2.1 Security Regulations

5.2.2 Operations Security (OPSEC)

5.2.3 Communications Security (COMSEC)

5.2.4 Security Clearance

5.2.5 Security Incident or Violation

5.2.6 Access to Government System(s)

5.2.7 Access to Government Facility or Military Installation

5.2.8 Common Access Card (CAC)

5.3 Environmental Management System (EMS)

5.4 Agency Affirmative Procurement Programs

5.5 Safety Requirements

5.5.1 Contractor Environmental, Safety, and Occupational Health Compliance

5.5.2 Mishap Notification/Investigation

5.6 Inspection of Services

5.7 Service Contract Reporting

5.8 Invoicing/Payment and Receipt/Acceptance

5.9 Contractor’s Quality Program

5.10 Trafficking in Persons

PR: FD2060-27-30005 PWS REVISION: 0 5

1.0 Description of Services

1.1 Objective(s)

A multi-disciplined engineering team with expert knowledge and reach back to corporate Bell resources is needed to provide repair instructions which may require modification support, accident investigation support, re-qualification data, and technical order changes in support of the TH-1 and UH-1 rotary platforms referred to in this document as H-1. Life-cycle sustainability for the H-1 necessitates Bell engineering support available through this contractual agreement. While the government had a full data package delivered with the aircraft in the 1960’s, the data was/has not been maintained over the years to a level that sufficiently captures all design changes since aircraft delivery.

At any given time, the H-1 depots require engineering assistance to resolve Programmed Depot Maintenance (PDM) issues beyond the published Technical Orders. This Original Equipment Manufacturer (OEM) engineering support contract enables the United States Air Force (USAF) Helicopter Program Office (HPO) engineers access to expertise and engineering data to effectively resolve any PDM issues and manage requirements.

This contract is to obtain engineering and logistical support from the OEM. This support will provide the USAF HPO technical expertise greater than that possessed and access to OEM proprietary data, including but not limited to structural/component data, drawings, qualification data, and analysis techniques as required to adequately maintain Operational, Safety, Suitability, and Effectiveness (OSS&E) for the H-1 platform. The specific tasks will require the expertise, analysis techniques, and proprietary data held only by the OEM.

1.2 Benefit to United States Air Force (USAF)

This effort will accomplish sustaining engineering tasks in accordance with individual tasks required to support the existing fielded H-1. These tasks include providing support for resolving associated operational problems and providing technical reports for the H-1. Tasks include:

- Field Support;

- Government System Interfaces;

- Sustaining Engineering Tasks;

- Logistics Reachback Support;

- Project Engineering Management.

1.3 Background

The Air Force UH-1N model was developed from Bell Model 212 Twin Huey, which was first flown in April 1969. The Air Force UH-1N helicopters were manufactured by the Bell Helicopter Company of Fort Worth, Texas and evolved as a result of a Class V modification via TO 1H-1(U)F-545. The Air Force TH-1H model is the result of three modifications to the UH-1N. The modifications included engine drive train, structural, and rotor modification as part of the Bell Model UH-1H II (Huey II) kit, as well as avionics upgrade, glass cockpit displays and crashworthy seat modifications. The primary mission of the aircraft is to support undergraduate helicopter pilot training. This effort allows the HPO access to the OEM’s technical personnel and proprietary data to maintain the OSS&E of the baseline configurations.

PR: FD2060-27-30005 PWS REVISION: 0 6

2.0 Services Summary

Performance Objective PWS Reference Performance Threshold

Receipt of Contract Data Requirements List (CDRL) Deliverables

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

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

Rapid “Urgent” and Routine “Non-Urgent” Responses

4.3.5 The Contractor’s recommendation for problem

resolution shall be delivered within one business day of receipt of notice of grounded aircraft or a safety mishap issue to include travel plans, if directed. A solution recommendation shall be delivered within three business days of receipt of notice. No more than one late intent for problem resolution is allowed per quarter. For safety or mishaps, no late receipts of recommendations are allowed. For Urgent Engineering Service Task Requests (ESTR), the Contractor shall deliver a response within 24 business hours upon receipt of notice with accurate information for HPO Engineering to take action.

Routine ESTR shall be responded to with proposed solution within five business days upon receipt of

ESTR.

Provide Accurate Status Reports and Meeting Agendas / CDRL Submissions

4.2.1 There shall be no more than two total rejection(s) of

deliverables per quarter, no more than one rejection per each deliverable. 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 within five business days of notification of Government rejection.

Prepare an Agenda and Minutes for each Meeting

4.2.1 The agenda shall be submitted no later than five

business days prior to the date of the meeting or conference, and minutes no later than five business days after the date of the meeting.

PR: FD2060-27-30005 PWS REVISION: 0 7

3.0 Government Property

3.1 Contractor Responsibility

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

3.2 Government Property to be Provided

The Contractor shall procure all material and parts necessary for the modification of the end items. Any material and parts purchased under this contract becomes Government property.

3.3 Reporting of Government Property

The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with 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/.

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 or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property

The Contractor shall report loss of Government property in the GFP Module located in the Procurement Integrated Enterprise Environment (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

PR: FD2060-27-30005 PWS REVISION: 0 8

the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements

The Contractor shall be required to perform analysis, compile technical reports, conduct studies and provide support for urgent and routine response requirements for the USAF H-1 fleet.

4.1 Period and Place of Performance

4.1.1 Contract Period of Performance

The Period of Performance (PoP) for the contract will extend five years after contract award assuming all options are exercised with one 12-month basic option followed by four 12-month option periods.

4.1.2 Place of Performance

These services will be performed at various locations depending on the task order and requirement. Possible performance locations include the following:

- Contractor site;

- Military facilities

- Other locations to be determined (TBD).

PR: FD2060-27-30005 PWS REVISION: 0 9

4.2 Contract Data Requirements List(s) (CDRL) 1

Document Identifier Base Year

Option Year 1

Option Year 2

Option Year 3

Option Year 4 Authority Title / Subtitle PWS Reference

A001 B001 C001 D001 E001 DI-MISC-80508B Technical Report – Study/Services

4.3.3, 4.3.4, 4.3.12, 4.4.2.3

A002 B002 C002 D002 E002 DI-MGMT-80368A Status Report 4.4.2, 4.4.3

A003 B003 C003 D003 E003 DI-SESS-81000F/T Product Engineering Design Data and Associated Lists

4.3.9, 4.3.9.5

A004 B004 C004 D004 E004 DI-FNCL-80331A Funds and Man-Hours Expenditure Report

4.4.1

A005 B005 C005 D005 E005 DI-ADMN-81249C Meeting Agenda 4.3.9.1, 4.3.9.2, 4.4.2,

4.4.2.1 4.4.2.1

A006 B006 C006 D006 E006 DI-ADMN-81250C Meeting Minutes 4.3.9.1, 4.3.9.2, 4.4.2, 4.4.2.1, 4.4.2.2

A007 B007 C007 D007 E007 DI-ADMN-81373 Presentation Material 4.3.9.1, 4.3.9.2, 4.4.2, 4.4.2.1, 4.4.2.2

A008 B008 C008 D008 E008 DI-MISC-81943 Trip/Travel Report 4.4.2, 4.4.2.1, 4.4.2.2, 4.4.2.3, 4.4.3

A009 B009 C009 D009 E009 DI-MGMT-

80061A/T

Engineering and Technical Services Accomplishment Report

4.4.2, 4.4.2.2, 4.4.2.3

A00A B00A C00A D00A E00A DI-DRPR-81961C Acquisition and Sustainment Data Package (ASDP) Engineering Drawing Tree

4.3.9

A00B B00B C00B D00B E00B DI-SAFT-81563 Accident/Incident Report 5.5.2

PR: FD2060-27-30005 PWS REVISION: 0 10

4.2.1 Quality of CDRL Deliverable

There shall be no more than two total rejection(s) of deliverables per quarter, no more than one rejection per each deliverable. 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 exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection. Upon scheduling a meeting/conference an agenda shall be submitted no later than five business days prior to the date of the meeting or conference, and minutes no later than five business days after the date of the meeting.

4.2.2 Receipt of CDRL Deliverable

CDRL deliverables shall be submitted via Wide Area Workflow (WAWF) or be submitted directly to the Multi-Functional Team (MFT) member identified on the CDRL. Separately priced data must be submitted and accepted in WAWF in order for the Contractor to receive payment.

There shall be no more than one late submission(s) of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Engineering Services

The OEM contract is intended to be highly flexible and broad in scope in order to allow quick reaction and adaptation to the demands of a highly dynamic and unpredictable operating environment. The engineering services contract line item supports all engineering services areas.

All engineering tasks issued through Engineering Service Task Requests (ESTR) within the period of performance are intended to be short-term projects, estimated at typically less than 100 hours.

4.3.1 Item Unique Identification

4.3.1.1 Marking Requirement:

Unique Item Identification is required for all items to be delivered to the Department of Defense (DoD) that meet the criteria established by the FAR.

4.3.1.2 Reporting in IUID Registry

4.3.1.2.1 Transmission of Government property must be recorded in the IUID Registry. The Government is required to record the transfer of GFP to the Contractor. The Contractor is required to record the receipt of GFP from the Government. The Contractor is required to record the return of GFP to the Government.

4.3.1.2.2 The Government or contractor/subcontractor personnel responsible for causing a “life cycle event” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign government, sold – historic, sold – nongovernment, sold – other federal, sold – state/local, and stolen) will update the item record in the IUID Registry.

PR: FD2060-27-30005 PWS REVISION: 0 11

4.3.2 Packaging

The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, and applicable Government regulations. The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM).

4.3.3 Validation of Component Retirement Times (CRT)

On an as-needed basis, the Contractor shall validate the CRT and overhaul times for USAF H-1 platform components (prioritized component list shall be provided by HPO engineering through ESTR) using updated usage survey, existing flight loads most representative of each specific aircraft, updated component fatigue strengths, and current damage hypothesis methods (i.e. cycle counting). The Contractor shall provide substantiating fatigue data. Existing aircraft/component reliability shall not be affected. The Government will reject a deliverable if two or more technical errors or five or more minor errors are found within the deliverable. Revisions shall be completed within five business days.

(CDRL Reference in paragraph 4.2, DI-MISC-80508B, Technical Report – Study/Services)

4.3.4 Proprietary Data

The Contractor shall provide to the HPO Engineering access to proprietary data as required to maintain operation, safety, suitability, and effectiveness of the baseline configurations. The Contractor shall submit a technical report by the ESTR date. The Government will reject a deliverable if two or more technical errors or five or more minor errors are found within the deliverable. Errors shall be corrected within five business days.

(CDRL Reference in paragraph 4.2, DI-MISC-80508B, Technical Report – Study/Services)

4.3.5 Urgent/Routine Response

For urgent requests, the Contractor shall make an initial response consisting of the proposed solution, or the status thereof, within one business day with accurate information for HPO Engineering to take action. If required by the Contractor, Government-owned drawings to support an ESTR will be supplied via electronic means within one working day. The Contractor shall provide drawings as needed to the Government within one working day.

For routine requests, the Contractor shall make an initial reponse with a proposed solution within five business days. The exception to this shall be Mylar drawings which will be treated on a case-by-case basis to be defined by the HPO engineering and the Contractor.

4.3.6 New/Unique Operational Requirements

The Contractor shall provide technical support for fielded H-1 platform unique system configuration as originally delivered by Bell or assist with unique systems delivered by Bell but modified by the HPO. This will involve evaluating the impact of unique Air Force mission requirements on basic H-1 platform systems to ensure that established safe baselines are not being compromised. The major systems of concern are electrical, avionics, aeromechanics, structural, mechanical, flight control and dynamic systems. If a unique aftermarket installation is identifiable or the system has been modified by the HPO, the Government will provide the Contractor with all necessary information required to complete the task by attaching these

PR: FD2060-27-30005 PWS REVISION: 0 12

documents to the ESTR. A specific example is the possible implementation of the Boundary Layer Research (BLR) Fast Fin and any impact it makes on CRTs. The Contractor shall submit an ESTR response by the specified due date.

4.3.7 Aircraft Sustainment and Reliability/Maintainability Support The Contractor shall work with the HPO to analyze and develop corrective actions and remediate service-revealed deficiencies and USAF-related Technical Order deficiencies. Deficiencies may be identified via:

a. Product Quality Deficiency Reports (PQDR);

b. Product Improvement Working Group (PIWG) action items;

c. AFTO 22s;

d. AFTO 135s;

e. AFTO 847s;

f. Critical item lists;

g. Corrosion Prevention Advisory Board (CPAB) action items;

h. Field or depot requests for engineering support;

i. Requests from HPO engineering.

The Contractor shall respond to initiatives as directed by HPO engineering to determine design and/or technical manual changes required for their improvement and initiate documentation of appropriate design changes under these sustaining engineering efforts. The Contractor shall also conduct assessments on components in order to avert future problems (e.g. obsolete parts, aging aircraft studies), operating and support cost reduction initiatives, and identify technology insertion opportunities.

4.3.8 Logistics Reachback Support

The Contractor shall provide Logistics Subject Matter Expert (SME) support and planning within the requested support areas. The Contractor shall provide and facilitate responses to questions and/or issues from the USG and provide technical support and resolves discrepancies for H-1 and/or Bell Logistics products. As issues arise, the Contractor shall investigate the root cause and provide recommendations, review drawings and applicable data, and coordinate with USG, Engineering, and other H-1 technical experts to respond to fleet issues. The Contractor shall attend applicable meetings and provide supply status updates when requested through an approved Contractor format. The Contractor Logistics Support will be in direct support of engineering efforts/tasks.

4.3.9 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

PR: FD2060-27-30005 PWS REVISION: 0 13

requirement documentation data required to test systems, subsystems and/or 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 Drawings Models 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, Option 10(CAGE 98752), reference attached DD Form 1423 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 CDR.

(CDRL Reference in paragraph 4.2, DI-SESS-81000F/T, Product Engineering Design Data and Associated Lists) (CDRL Reference in paragraph 4.2, DI-DRPR-81961C, Acquisition and Sustainment Data Package (ASDP) Engineering Drawing Tree)

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

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 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 Technical Data Package (TDP) deliverables.

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

(CDRL Reference in paragraph 4.2, DI-ADMN-81249C, Meeting Agenda)

PR: FD2060-27-30005 PWS REVISION: 0 14

(CDRL Reference in paragraph 4.2, DI-ADMN-81250C, Meeting Minutes) (CDRL Reference in paragraph 4.2, DI-ADMN-81373, Presentation Material)

4.3.9.2 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., PDR, 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 Reference in paragraph 4.2, DI-ADMN-81249C, Meeting Agenda) (CDRL Reference in paragraph 4.2, DI-ADMN-81250C, Meeting Minutes) (CDRL Reference in paragraph 4.2, DI-ADMN-81373, Presentation Material)

4.3.9.3 Relationship of Contractor with Subcontractors/Vendors The Contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (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.3.9.4 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

PR: FD2060-27-30005 PWS REVISION: 0 15

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.3.9.5 Existing Engineering Data

The Contractor shall provide to the HPO Engineering requested engineering data as required to maintain operation, safety, suitability, and effectiveness of the baseline configurations. HPO Engineering will request pre-existing engineering data in the form of drawings. In the case where engineering data was developed under previous Government contracts the data shall be delivered with unlimited data rights. Drawings that were not produced under a Government contract or were produced with a combination of Government funding and private funding shall be delivered with either Government Purpose Rights, or Limited rights as defined in MIL-STD-31000 and DFARS clauses 252.227. HPO Engineering may request older revisions of drawings in an effort to acquire data rights to the drawings if the data is for a specific part number or an older revision of the data will satisfy HPO engineering purposes. In cases where previously provided engineering data had unlimited rights and the Contractor believes newly requested revised engineering data has limited rights then the Contractor will provide a brief explanation for the change in rights.

(CDRL Reference in paragraph 4.2, DI-SESS-81000F/T, Product Engineering Design Data and Associated Lists)

4.3.10 Project Engineering Management

The Contractor shall provide the part-time/full-time services of an individual (PM or Engineer) to serve as the point of contact for H-1 platform technical/design issues and direct the sustaining effort activities described in the PWS.

4.3.11 Flight Testing/Engineering Support

The Contractor shall provide qualified test pilots and flight engineers as required by AFLCMC/WIH. The qualified personnel shall be utilized when the Government does not possess the expertise to accomplish the task, such as mishap investigations, re-qualification of components and subsystems. Estimated hours expended for Flight Test shall not exceed 50 hours in the basic ordering period and 50 hours for each optional year ordering period.

4.3.9.1. The Contractor shall comply with the operating procedures contained in the combined regulation 48 CFR 252.228-7001, entitled “Ground and Flight Risk” and Defense Contract Management Agency Instruction 8210.2 entitled “Aircraft Operations” in effect on the date of contract award

4.3.12 Other Services

The Contractor shall provide the support services as required for other tasks that may surface during the contract service tenure. These tasks may include providing: on- site weapon system support personnel to field activities, conducting technical studies, investigation of specific failures, analytical studies, feasibility studies, fabrication or procurement of items required to model proposed solution, fabrication of test specimens, conducting testing including flight of aircraft during Program Depot Maintenance, fatigue testing technical report by the specified due date.

PR: FD2060-27-30005 PWS REVISION: 0 16

(CDRL Reference in paragraph 4.2, DI-MISC-80508B, Technical Report – Study/Services)

4.4 Program Management

The Contractor shall be responsible for providing the m anagement, administration, financial control, engineering, manufacturing, procurement, testing, and quality assurance activities associated with this effort. The Contractor shall identify a liaison point of contact on all contractual and technical matters. All program management requirements of the contract shall extend to the effort required by this PWS. AFLCMC/WIHC will authorize and convey tasks in writing to the Contractor through ESTR. The Contractor’s response and expenditures shall be limited to the authorized task requirements.

4.4.1 Monthly Status/Financial Report

The Contractor shall prepare and submit status reports detailing work performed during the previous month. This requirement is for the basic contract period and any additional ordering periods. The Contractor shall identify tasks to be performed during the next reporting period in each status report. The status report shall include financial expenditure information. The financial status shall be reported as both cumulative and for the specific reporting month.

(CDRL Reference in paragraph 4.2, DI-MGMT-80368A, Status Report) (CDRL Reference in paragraph 4.2, DI-FNCL-80331A, Funds and Man- Hours Expenditure Report)

4.4.2 Meetings

The Contractor shall be responsible for attending/hosting meetings in accordance with (IAW) the following paragraphs. In support of the meetings and conferences, the Contractor shall furnish agendas, presentation materials and resulting meeting minutes, as required. At a minimum, the Contractor shall participate in semi-annual Program Management Reviews and PIWG meetings.

The Contractor shall also participate in the annual CPAB meeting.

(CDRL Reference in paragraph 4.2, DI-ADMN-81249C, Meeting Agenda) (CDRL Reference in paragraph 4.2, DI-ADMN-81250C, Meeting Minutes) (CDRL Reference in paragraph 4.2, DI-ADMN-81373, Presentation Material) (CDRL Reference in paragraph 4.2, DI-MISC-81943, Trip/Travel Report) (CDRL Reference in paragraph 4.2, DI-MGMT-80061A/T, Engineering and Technical Services Accomplishment Report)

4.4.2.1 Kick-off Meeting

A kick-off meeting shall be hosted at a location determined by the Government no later than 30 days after contract award. The purpose of the meeting is to review and evaluate the Contractor’s interpretation of the basic contractual requirements and to provide necessary direction and guidance.

(CDRL Reference in paragraph 4.2, DI-ADMN-81249C, Meeting Agenda) (CDRL Reference in paragraph 4.2, DI-ADMN-81250C, Meeting Minutes) (CDRL Reference in paragraph 4.2, DI-ADMN-81373, Presentation Material) (CDRL Reference in paragraph 4.2, DI-MISC-81943, Trip/Travel Report)

PR: FD2060-27-30005 PWS REVISION: 0 17

4.4.2.2 Program Review

The Government and the Contractor shall participate in semi-annual Program Reviews and technical meetings as defined and required by the Government as needed. The location of these meetings will be determined by the Government. The kick-off/requirements review will be conducted no later than (NLT) 30 days after receipt of order at a location determined by the Government. At the Government’s discretion, Program Reviews and the kick-off meeting may be accomplished through alternate means (i.e. teleconference, etc.).

(CDRL Reference in paragraph 4.2, DI-ADMN-81249C, Meeting Agenda) (CDRL Reference in paragraph 4.2, DI-ADMN-81250C, Meeting Minutes) (CDRL Reference in paragraph 4.2, DI-ADMN-81373, Presentation Material) (CDRL Reference in paragraph 4.2, DI-MISC-81943, Trip/Travel Report) (CDRL Reference in paragraph 4.2, DI-MGMT-80061A/T, Engineering and Technical Services Accomplishment Report)

4.4.2.3 Final Report

The results of the contract activities shall be documented in a final report. This report shall detail the activities and evaluations accomplished during the completion of this task. The report shall include trip reports for any trips taken. The Contractor shall submit a final report at the completion of the period of performance.

(CDRL Reference in paragraph 4.2, DI-MISC-80508B, Technical Report – Study/Services) (CDRL Reference in paragraph 4.2, DI-MISC-81943, Trip/Travel Report) (CDRL Reference in paragraph 4.2, DI-MGMT-80061A/T, Engineering and Technical Services Accomplishment Report)

4.4.3 Travel

Travel requests for contractor/subcontractor personnel shall be submitted for approval to the Contracting Officer prior to costs being incurred and a minimum of five business days in advance of departure. Receipts must be presented with the invoice for reimbursement of actual travel costs. Trip Reports shall be submitted NLT five business days upon return from the trip.

(CDRL Reference in paragraph 4.2, DI-MISC-81943, Trip/Travel Report)

5.0 General Information

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

5.2 Security Requirements

5.2.1 Security Regulations

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

PR: FD2060-27-30005 PWS REVISION: 0 18

5.2.2 Operations Security (OPSEC)

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

5.2.3 Communications Security (COMSEC)

The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a). Applicable equipment shall be safeguarded, maintained and operated in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a).

5.2.4 Security Clearance

The Contractor shall ensure applicable contractor/subcontractor personnel have security clearance(s) at the secret level for proper accomplishment of contract/order requirements. The security clearance(s) shall be obtained in accordance with the Department of Defense (DD) Form 254, Department of Defense Contract Security Classification Specification.

5.2.5 Security Incident or Violation

The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.6 Access to Government System(s)

The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.7 Access to Government Facility or Military Installation

The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

5.2.8 Common Access Card (CAC)

5.2.8.1 The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order.

PR: FD2060-27-30005 PWS REVISION: 0 19

The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to utilize Mission Partner Identity, Credential and Access Management (MP-ICAM) and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

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

5.3 Environmental Management System (EMS)

These services shall not be performed at a Government facility; therefore, the EMS requirement does not apply.

5.4 Agency Affirmative Procurement Programs

In accordance with FAR 23.107, Agency Affirmative Procurement Programs, 100% of purchases of Environmental Protection Agency (EPA)-designated products included in the Comprehensive Procurement Guidelines (CPG) list (https://www.epa.gov/smm/comprehensive-procurement-guideline-cpg-program#products) and/or United States Department of Agriculture (USDA)-designated products included in the bio-based product listings [http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for recovered materials or bio-based content, respectively, unless an item cannot be acquired competitively within a realistic timeframe, meet appropriate performance standards, and/or be acquired at a reasonable price.

5.5 Safety Requirements

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

5.5.2 Mishap Notification/Investigation

In accordance with DAFI91-204, Safety Investigations and Reports, the Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations. 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

PR: FD2060-27-30005 PWS REVISION: 0 20

Contracting Officer. The Contractor shall cooperate and assist Government personnel in the investigation of the mishap and submit an Accident/Incident Report within 24 hours of the mishap. There shall be no more than one instance of late mishap notification per contract year.

The Contractor shall ensure the following are notified:

a. PCO;

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

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

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

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

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

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

d. Cause of accident/incident, if known;

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

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

g. Corrective actions (taken or proposed);

h. Other pertinent information.

(CDRL Reference in paragraph 4.2, DI-SAFT-81563, Accident/Incident Report)

5.6 Inspection of Services

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

5.7 Service Contract Reporting

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

5.8 Invoicing/Payment and Receipt/Acceptance

The Contractor shall submit/process payment requests and receipt/acceptance documents via

WAWF.

5.9 Contractor’s Quality Program

The Contractor's Quality Management System (QMS) shall meet the requirements of AS9100, Quality Management Systems Requirements for Aviation, Space, and Defense Organizations, PR: FD2060-27-30005 PWS REVISION: 0 21 which is based on the standards of ISO 9001. The contractor must establish an AS9100 compliant quality management system, ensure its functionality and compliance through internal auditing, and undergo a certification audit conducted by an external registrar. The Contractor shall allow the Government access to the records and data collected to demonstrate the suitability and effectiveness of the quality management system. The Government reserves the right to request corrective action if the quality system fails to meet objectives. The Contractor shall permit the program office or its designated representative to periodically review its quality program.

5.10 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

PR: FD2060-27-30005 PWS REVISION: 0 22

Appendices Unless otherwise specified, the version of the following specifications, standards, handbooks, technical orders, and engineering reports current on the award date of the contract form a part of this PWS to the extent specified herein. Unless otherwise specified, copies and any other supplements thereto required by the supplier in connection with specified procurement functions should be obtained from the Department of Defense Index of Specification and Standards (DoDISS) or the Information Handling System (IHS). Any documents required by contractors in connection with specific acquisition functions should be obtained from the contracting activity or as directed by the contracting officer. In the event of a conflict between the documents referenced herein and the contents of this PWS, the contents of this PWS shall govern.

Bell must have a Technical Order Distribution Office (TODO) account in order to obtain copies of the referenced H-1 publications. If an account has not been established, the Offeror must establish a TODO account upon contract award by processing an AFTO Form 43, USAF TODO Assignment or Change Request in accordance with TO 00-5-1. The IBM Lotus version of the AFTO Form 43 can be downloaded at http://www.e-publishing.af.mil/.