1. PWS.pdf

PR: FD2060-22-30072 PWS REVISION: 0 1

Distribution Statement: A

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

HH-60 Sustaining Engineering Support

Services

FD2060-22-30072

12 October 2022

Prepared by:

AFLCMC/WIUBC

370 RICHARD RAY BLVD

ROBINS, AFB, GA 31098

Distribution Statement A: Approved for public release: distribution unlimited.

PR: FD2060-22-30072 PWS REVISION: 0 2

TABLE OF CONTENTS

SECTION TITLE PAGE

SECTION 1 DESCRIPTION OF SERVICES 3

SECTION 2 SERVICES SUMMARY 4

SECTION 3 GOVERNMENT FURNISHED PROPERTY & SERVICES 4

SECTION 4 TECHNICAL REQUIREMENTS 6

SECTION 5 GENERAL INFORMATION 14

SECTION 6 APPENDICES 18

PR: FD2060-22-30072 PWS REVISION: 0 3

1.0 Description of Services:

1.1 Objective(s): This Performance-Based Work Statement describes the services needed to obtain sustaining engineering support for the United States Air Force (USAF) HH-60G and HH-60W helicopters, hereby referred to collectively as HH-60, from the Original Equipment Manufacturer (OEM). This support will provide the USAF HH-60 System Program Office (SPO) technical expertise greater than that possessed, as well as 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 HH-60 platform. The effort provides mishap analysis in support of Air Force (AF) Safety Investigation Boards. These specific tasks require the expertise, analysis techniques, and limited use data only held by the OEM. This effort will accomplish sustaining engineering tasks in accordance with (IAW) individual engineering support task required to support existing fielded HH-60 fleet such as engineering support, validation of Component Retirement Times (CRT), Engineering Support Task Request (ESTR), sustainment support, reliability and maintainability support, Engineering Change Proposal (ECP) preparation, project engineering management, flight testing, program management, on-site technical support, monthly status and financial reports, and developing engineering data.

These tasks include providing support as directed by the HH-60 SPO technical personnel for resolving associated operational problems and providing technical data for the HH-60 helicopter.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by providing technical and engineering support needed to sustain and maintain OSS&E for the HH-60 in order to meet its Air Force mission to recover isolated personnel from hostile or denied territory.

1.3 Background:

1.3.1 HH-60G: The USAF aircraft HH-60G Pave Hawk fleet are UH-60 Black Hawk variants with a basic airframe structure of approximately half A-Model and half L-Model airframes. The Pave Hawk was outfitted with a permanently mounted Aerial Refueling Probe and hydraulic hoist at Pensacola Naval Air Depot with a rollout in December 1987 to meet the USAF Combat Search and Rescue mission. Subsequent modifications were primarily for additions of avionics equipment for locating survivors and communicating with friendly aerial and ground support vehicles. Currently, all the HH-60G have been upgraded to an L-Model structure to include the dynamic components which allow the aircraft to support current loads and flight regime demands of deployments. The HH-60G has been based lined to the Pave Hawk IV configuration (Block - 152 modifications). These modifications are documented on Drawing Number 9582102 and the SPS. Current modifications in various stages of completion have evolved the Pave Hawk into a Block -152 configuration. To compensate for the loss of aircraft, the OLR program replaced/added 21 additional aircraft to the Total Aircraft Inventory (TAI). This was accomplished by converting UH-60L aircraft to the HH- 60G configuration by removing the equipment standard to the Army UH-60L, installing 71 previously demonstrated modifications, and another 6 new comparative solution system modifications. These modifications created a Block -162 configuration. This effort allows the SPO access to the original equipment manufacturers technical personnel and limited use data to maintain the OSS&E of the baseline configurations.

PR: FD2060-22-30072 PWS REVISION: 0 4

1.3.2 HH-60W: The USAF aircraft HH-60W Jolly Green II fleet, which is currently in production by Sikorsky Aircraft, are UH-60M Black Hawk variants that add capability advancements to better support the full range of combat rescue and other special missions. The HH-60W features advanced and improved defense systems, vulnerability reduction, hover performance, electrical capability, avionic, cooling, weapons, cyber-security, environmental and net-centric requirements. The primary mission of the HH-60W helicopter will be conducting day or night combat search and rescue operations into different environments to include recovering isolated personnel, civil search and rescue, medical evacuation, disaster response, humanitarian assistance, security cooperation/aviation advisory, NASA space flight support, and rescue command and control. The HH-60W expands upon the legendary Black Hawk by doubling the internal fuel capacity without the use of space hungry auxiliary fuel tanks.

2.0 Services Summary:

Performance Objective PWS

Reference Performance Threshold

Quality of CDRL deliverable

4.2.1

There shall be no more than (1) one rejection of any deliverable. There shall be no more than (2) two total rejection(s) of deliverables per contract year. The Government will reject a deliverable if there are (1) one or more technical or (5) five or minor errors found within the deliverable.

The rejected deliverable shall be corrected and resubmitted within (3) three business days of notification of Government rejection.

Receipt of CDRL deliverable

4.2.2 There shall be (0) zero late submission(s) of

deliverables per contract quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date.

ESTR Response Time

4.3.1 There shall be (0) zero late urgent ESTRs per

contract year. There shall be no more than (1) one late routine ESTR per contract year.

On-Site Technical Support Response Time

4.3.9 Contractor shall have technical support onsite

within (10) ten business days of notification of requirement.

3.0 Government Furnished Property and Services –

3.1 Government Property: Government Furnished Material (GFM) and Government Furnished Equipment (GFE) is authorized. GFM will be identified and accounted for in each task order as needed.

3.2 Government Property to be Provided: Contractor shall procure all material and parts

PR: FD2060-22-30072 PWS REVISION: 0 5

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-7002. 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/task 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

3.4.2.1 The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.4.2.2 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/task 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/task order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/task order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

3.4.2.3 The Contractor shall report losses of Government property outside normal process variation, e.g. losses due to Theft; inadequate storage; Lack of physical security; or “Acts of God.”

3.4.2.4 This reporting requirement does not change any liability provisions or other https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/

PR: FD2060-22-30072 PWS REVISION: 0 6

reporting requirements that may exist under this contract.

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

4.0 Technical Requirements

4.1. Period and Place of Performance:

4.1.1 Contract Period of Performance (PoP): The PoP for this contract will be (5) five years including a (1) one-year basic with (4) four annual ordering periods.

4.1.2 Place of Performance: These services will be performed at different locations depending on the task and requirement. Possible performance locations include the following:

a) Contractor Site

b) Operational bases including Kirtland AFB, Davis-Monthan AFB, Moody AFB, Nellis AFB, Kadena Air Base, Patrick SFB, Moffett Field, Joint Base Elmendorf-Richardson, Gabreski Field, and Aviano AB, Italy

4.2 Contract Data Requirements List (CDRL):

4.2.1 Quality of CDRL Deliverable: The Contractor shall deliver all data/reports associated with all CDRLs, with no more than (1) one rejection of each deliverable. There shall be no more than (2) two total rejection(s) of deliverables per contract year. The Government will reject a deliverable if (1) one or more technical errors or (5) 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 (3) business days of notification of Government rejection in accordance with the associated DD Form 1423 instructions/requirements. The contractor shall prepare an agenda and minutes for each meeting/conference and shall be submitted no later than five (5) business days prior to the date of the meeting or conference, and minutes no later than five (5) business days after the date of the meeting.

4.2.2 Receipt of CDRL Deliverable: The Contractor shall deliver all CDRLs with (0) zero late submission(s) of deliverables per contract 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.

PR: FD2060-22-30072 PWS REVISION: 0 7

4.3 Engineering Support: 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 Government will utilize an Engineering Support Task Request (ESTR), shown in Appendix C, to task the Contractor with specific requirements described within this PWS. The Contractor shall complete the form providing a thorough response description, estimated cost, estimated calendar days, and estimated man-hours to complete all work required identified on the ESTR. The Contractor shall deliver a solution within the cost and timeframe as stated in the associated ESTR.

Document Identifier Base Year

Ordering Period

Ordering Period

Ordering Period

Ordering Period

DID TITLE/SUBTITLE PWS Reference

A001 B001 C001 D001 E001 DI-MISC-

80508B

Technical Report - Study/Services

4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.3.5.1, 4.3.5.2, 4.3.6, 4.3.9, 4.4.3.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

Product Engineering Design Data and Associated Lists

4.3.1, 4.6.1, 4.6.2

A004 B004 C004 D004 E004 DI-FNCL-

80331A

Funds and Man- Hours Expenditure Report

4.4.2

A005 B005 C005 D005 E005 DI-ADMN-

81249C

Conference Agenda 4.4.3, 4.4.3.1, 4.4.3.2, 4.6.3, 4.6.4

A006 B006 C006 D006 E006 DI-ADMN-

81250C

Conference Minutes 4.4.3, 4.4.3.1, 4.4.3.2, 4.6.3, 4.6.4

A007 B007 C007 D007 E007 DI-ADMN-

81373

Presentation Material 4.4.3, 4.4.3.1, 4.4.3.2, 4.6.3, 4.6.4

A008 B008 C008 D008 E008 DI-MISC-

81943

Trip/Travel Report 4.4.3, 4.4.3.1, 4.4.3.2, 4.4.3.3, 4.5, 4.6.3, 4.6.4

A009 B009 C009 D009 E009 DI-MGMT-

80061A/T

Engineering and Technical Services Accomplishment Report

4.4.3, 4.4.3.2, 4.4.3.3

A00A B00A C00A D00A E00A DI-MGMT-

82135

Cybersecurity RMF Artifacts

4.6.1, 5.7

A00B B00B C00B D00B E00B DI-IPSC-

81427B

Software Development Plan

4.6.1

A00C B00C C00C D00C E00C DI-IPSC-

81433A

Software Requirements Specification

4.6.1

A00D B00D C00D D00D E00D DI-IPSC-

81438A

Software Test Plan

4.6.1

A00E B00E C00E D00E E00E DI-IPSC-

81440A

Software Test Report

4.6.1

A00F B00F C00F D00F E00F DI-SAFT-

81563

Accident/Incident Report

5.5.2

PR: FD2060-22-30072 PWS REVISION: 0 8

4.3.1. Urgent/Routine ESTR Response Time: When an ESTR has indicated a grounded aircraft in field or programmed depot maintenance work stoppage (urgent), the contractor shall make an initial response consisting of the proposed solution, or the status thereof, within (1) one working day with accurate information for SPO Engineering to take action. There shall be

(0) zero late urgent ESTR’s per contract year. If required by the contractor, Government-owned drawings to support an ESTR will be supplied via electronic means within (1) one working day. The contractor shall provide drawings as needed to the Government within (1) one business day. For routine requests, the contractor shall make an initial response with a proposed solution within (7) seven working days. The exception to this shall be Mylar drawings which will be treated on a case by case basis to be defined by the SPO Engineering and contractor. There shall be no more than (1) one late routine ESTR per contract year.

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

4.3.2 Proprietary Data: The contractor shall provide to the SPO 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.

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

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 HH-60 aircraft components (prioritized component list shall be provided by SPO engineering through ESTR) using updated usage survey, new and existing flight loads, updated component fatigue strengths (i.e. S-N curves), and current damage hypotheses methods (e.g. cycle counting). The contractor shall provide substantiating fatigue data.

(CDRL Reference in paragraph 4.2, Technical Report - Study/Services, DI-MISC-80508B) (CDRL Reference in paragraph 4.2, Product Engineering Design Data and Associated Lists, DI-SESS- 81000F)

4.3.4 New/Unique Operational Requirements: The contractor shall provide technical support for fielded helicopters with HH-60 unique system configurations as originally delivered by Sikorsky or assist with unique systems delivered by Sikorsky but modified by the SPO. This will involve evaluating the impact of unique AF mission requirements on basic HH-60 airframe 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 SPO, the Government will provide the contractor with all necessary information required to complete the task. The contractor shall submit a technical report by the specified due date.

4.3.5 Aircraft Sustainment and Reliability/Maintainability Support:

4.3.5.1 This sustainment support primarily comes in the form of responding to service revealed deficiencies and USAF related Technical Order deficiencies. Several forums are used by fielded units to identify problems or deficiencies to the SPO. Some of these are product quality deficiency reports (PQDR), product improvement working group (PIWG) action items, AFTO 22, AFTO135, AFTO 847, requests from SPO engineering, critical item lists, corrosion

PR: FD2060-22-30072 PWS REVISION: 0 9

prevention advisory board (CPAB) action items, and field or depot requests for engineering support. The contractor shall work with the Government to analyze and develop corrective actions for these design-related supportability and maintenance deficiencies; investigate reliability/maintainability issues identified through PQDR’s, PIWG action items, and initiatives as directed by SPO engineering to determine design and/or technical manual changes required for their improvement; initiate documentation of appropriate design changes under this sustaining effort. The contractor shall submit a technical report by the specified due date. The report shall contain no more than a total of five typographical errors and/or technical inaccuracies. Errors shall be corrected within 3 (three) business days from receipt of the Governments comments/corrections.

4.3.5.2 The contractor shall conduct assessments on the other components not identified in these forums in order to avert future problems (obsolete parts, aging aircraft studies, etc.), technology insertion or operating and support cost reduction initiatives as directed by SPO engineering. The contractor shall submit a technical report by the specified due date.

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

4.3.6 Engineering Change Proposal (ECP) Preparation: The contractor shall provide the resources required in Government preparation of ECPs. The contractor shall submit a technical report by the specified due date.

The Contractor, and any subcontractors, shall 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, as needed, in accordance with the following:

a. All engineering changes shall be incorporated into the applicable engineering data within

90 calendar days after engineering release/USAF concurrence or at intervals of (5) 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 Technical Data Package (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 document is revised the entire document shall be delivered.

Note: Engineering Data is a model, a drawing, or some other depiction of either an aircraft part or a repair to an aircraft part and will be defined when each task estimate is requested. Changes will only be incorporated prior to Engineering Release when a safety issue is involved.

4.3.7 Project Engineering Management: The contractor shall provide the full-time services of an individual (PM or Engineer) to serve as the point of contact for HH-60 technical/design issues and direct the sustaining effort activities described in the PWS.

PR: FD2060-22-30072 PWS REVISION: 0 10

4.3.8 Flight Testing/Engineering Support: The contractor shall provide qualified test pilots and flight engineers as required by AFLCMC/WIU. 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.

4.3.8.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.9 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, fatigue testing to validate proposed solutions, and other support services. The contractor shall submit a technical report by the specified due date.

The contractor shall have technical support onsite within (10) ten business days of notification of requirement.

4.4 Program Review/Support

4.4.1 Program Management: The contractor shall have the responsibility for providing the management, 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/WIUBC will authorized 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.2 Monthly Status/Financial Reports: 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, Status Reports, DI-MGMT-80368A) (CDRL Reference in paragraph 4.2, Funds and Man-Hours Expenditure Report, DI-FNCL- 80331A)

4.4.3 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, Status Reports, DI-MGMT-80368A)

PR: FD2060-22-30072 PWS REVISION: 0 11

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

4.4.3.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 meeting may be conducted via teleconference/videoconference. 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, Conference Agenda, DI-ADMN-81249C) (CDRL Reference in paragraph 4.2, Conference Minutes, DI-ADMN-81250C) (CDRL Reference in paragraph 4.2, Presentation Material, DI-ADMN-81373) (CDRL Reference in paragraph 4.2, Trip/Travel Report, DI-MISC-81943)

4.4.3.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 Program 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, Conference Agenda, DI-ADMN-81249C) (CDRL Reference in paragraph 4.2, Conference Minutes, DI-ADMN-81250C) (CDRL Reference in paragraph 4.2, Presentation Material, DI-ADMN-81373) (CDRL Reference in paragraph 4.2, Trip/Travel Report, DI-MISC-81943) (CDRL Reference in paragraph 4.2, Engineering and Technical Services Accomplishment Report, DI-MGMT-80061A/T)

4.4.3.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 period of performance. 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, Technical Report - Study/Services, DI-MISC-80508B) (CDRL Reference in paragraph 4.2, Trip/Travel Report, DI-MISC-81943) (CDRL Reference in paragraph 4.2, Engineering and Technical Services Accomplishment Report, DI-MGMT-80061A/T)

4.5 Travel: The Contractor may be required to travel for the performance of the work described within this PWS. Travel may include locations within the continental United States (CONUS) and outside the continental United States (OCONUS). The number of trips and personnel traveling shall be limited to the minimum required to accomplish work assignments in accordance with the assigned tasks. Travel will be reimbursed according to the rates outlined in the Federal Travel Regulations for travel within the CONUS; Joint Travel Regulations (JTR) for travel to Alaska, Hawaii and outlying areas of the United States; and the rates established by the Department of State for traveling OCONUS. Airfare shall consist of

PR: FD2060-22-30072 PWS REVISION: 0 12

no more than coach class seating while vehicle rentals shall be consistent with the most economic and reasonable rates available. In most circumstances, economy class vehicles will suffice. All Contractor travel, when required, shall require prior written approval a minimum of five (5) business days in advance from the Procuring Contracting Officer (PCO) and concurrence by the Program Manager (PM) prior to costs being incurred. The Government is under no obligation to reimburse the contractor for any travel in which prior written approval from AFLCMC/WIUK, Robins AFB, GA, has not been received. All travel shall be in accordance with DoD JTR. Trip Reports shall be submitted to AFLCMC/WIUBC NLT five

(5) business days upon return from the trip.

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

4.6 Engineering Data: The contractor will be required to provide engineering drawings to in support of sustaining engineering. The primary purpose of requiring engineering data to support this effort will be to provide the Air Force with existing HH-60 drawings that the Air Force either does not currently have in possession or the data that the Air Force possesses is illegible or incomplete. It is not anticipated at this time that the contractor will have to develop new engineering data. All engineering data requirements will be requested via an ESTR and at that time a discussion will be made as to whether the data requested is existing data or will be newly developed data. Existing engineering data can be delivered in original format.

4.6.1 Non-Existent Engineering Data: If engineering data is not currently existent and needs to be developed, the contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product developed under this PWS. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). 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. Software engineering data includes software development plans, software requirements specifications, software test plans and reports, and software executable/binary files or OFP image files, and cybersecurity software scan reports.

Additional software engineering data may be added by any efforts funded by this contract. 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. All data delivered under this contract will be in accordance with the DFARS Requirements. The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision M (CAGE 98752), reference attached DD Form 1423 Block 16.

(CDRL Reference in paragraph 4.2, Product Engineering Design Data and Associated Lists, DI-SESS-81000F) (CDRL Reference in paragraph 4.2, Cybersecurity RMF Artifacts, DI-MGMT-82135) (CDRL Reference in paragraph 4.2, Software Development Plan, DI-IPSC-81427B) (CDRL Reference in paragraph 4.2, Software Requirements Specification, DI-IPSC- 81433A)

PR: FD2060-22-30072 PWS REVISION: 0 13

(CDRL Reference in paragraph 4.2, Software Test Plan, DI-IPSC-81438A) (CDRL Reference in paragraph 4.2, Software Test Report, DI-IPSC-81440A)

4.6.2 Existing Engineering Data: The contractor shall provide to the SPO Engineering requested engineering data as required to maintain operation, safety, suitability, and effectiveness of the baseline configurations. SPO 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 may be delivered with either Government Purpose Rights, or Limited rights as defined in MIL-STD-31000 and DFARS clauses 252.227. SPO 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 SPO 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, Product Engineering Design Data and Associated Lists, DI-SESS-81000F)

4.6.3 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:

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

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

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

4.6.4 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

PR: FD2060-22-30072 PWS REVISION: 0 14

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

4.6.5 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 subcontractor/vendor levels associated with the program.

4.6.6 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 (5), 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.

5.0 General Information

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

PR: FD2060-22-30072 PWS REVISION: 0 15

5.2 Security Requirements

5.2.1 General: Actual knowledge and/or generation of classified information and/or Controlled Unclassified Information (CUI) are required for the performance of the contract/order.

However, Contractor personnel are required to comply with security requirements to preclude potential security incidents or violations. The Contractor shall ensure applicable Contractor personnel have security clearances at the appropriate level.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and security requirements are met. The Contractor shall comply with security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security Program;32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program, DoD Manual 5205.02-M, and DoD Operations Security (OPSEC) Program Manual.

5.2.3 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. DoDD 5205.02E and DoD Manual 5205.02-M require contractors supporting DoD activities use OPSEC to protect critical information for specified contracts, 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.4 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/or CUI.

5.2.5 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/or CUI. The unauthorized disclosure of CUI will be reported In Accordance With (IAW) DFARS 204.252-7012.

5.2.6 Access to Government Facility or Military Installation: 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 Contractor shall ensure the system account(s) are closed. The Contractor shall ensure Contractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation. The Contractor shall ensure Contractor personnel who require access to a USAF installation comply with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

PR: FD2060-22-30072 PWS REVISION: 0 16

5.3 Common Access Card (CAC): 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. 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 complete a Trusted Associate Sponsorship System (TASS) application 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.3.1 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 (5) five business days. The Contractor shall return a CAC within (5) 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 (5) five business days after the expiration date. The Contractor shall return any and all CACs within (5) five business days after completion/termination of the contract as directed by local Government policy.

5.4 Affirmative Procurement Programs (APP): In accordance with FAR 23.404(b)(1), 100% of purchases of Environmental Protection Agency (EPA)-designated products included in the Comprehensive Procurement Guidelines (CPG) list [http://www.epa.gov/cpg/products.htm] and/or United States Department of Agriculture (USDA)-designated products included in the biobased product listings [http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for recovered materials or biobased 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: 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 (4) 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 http://www.epa.gov/cpg/products.htm http://www.biopreferred.gov/

PR: FD2060-22-30072 PWS REVISION: 0 17

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. There shall be (0) zero late submissions.

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

5.5.2.1. PCO,

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

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

5.5.3 Voluntary Protection Program (VPP): Contractor personnel performing work on a USAF installation shall participate in the local VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html.

5.6 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

5.7 Cybersecurity: The contractor shall comply in accordance with Air Force Instruction 17- 101 ‘Risk Management Framework (RMF) For Air Force Information Technology (IT)’ by providing the technical data required for the Government to maintain or obtain any applicable cybersecurity authorizations including Interim Authorizations to Test (IATTs), Authorizations to Operate (ATOs), and Authorizations to Connect (ATCs).

(CDRL Reference in paragraph 4.2, Cybersecurity RMF Artifacts, DI-MGMT-82135)

5.8 Service Contract Reporting: In accordance with 10 United States Code 2330(a), and DFARS 252.204-7023 (Reporting Requirements for Contracted Services), the Contractor shall provide a Service Contract Report for each contract that meets the DoD Contract Reporting criteria and is 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.9 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via Wide Area Work Flow in accordance with all applicable clauses located in the basic contract.

http://www.osha.gov/dcsp/vpp/index.html http://www.state.gov/j/tip https://www.sam.gov/ https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr

PR: FD2060-22-30072 PWS REVISION: 0 18

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

Offeror must have a Technical Order Distribution Office (TODO) account in order to obtain copies of the referenced HH-60 publications.