1. FD2060-21-32087 PWS with Appendices_Rev 4c (27 April 22).pdf

PR: FD2060-21-32087 PWS REVISION: 0 1

Distribution Statement: C

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

RELIABILITY AND MAINTAINABILITY (R&M) ENGINEERING SUPPORT FOR

ROTARY-WING WEAPON SYSTEMS

FD2060-21-32087

27 April 2022

Prepared by:

AFLCMC/WIUBC

235 Byron Street, Suite 19A Robins AFB, GA 31098-1670

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

PR: FD2060-21-32087 PWS REVISION: 0 2

TABLE OF CONTENTS

SECTION TITLE PAGE

SECTION 1 DESCRIPTION OF SERVICES 3

SECTION 2 SERVICES SUMMARY 3

SECTION 3 GOVERNMENT FURNISHED PROPERTY & SERVICES 5

SECTION 4 TECHNICAL REQUIREMENTS 6

SECTION 5 GENERAL INFORMATION 17

SECTION 6 APPENDICES 21

SECTION 7 APPENDICES D&E 27

PR: FD2060-21-32087 PWS REVISION: 0 3

1.0 Description of Services

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to provide Reliability and Maintainability (R&M) support to the USAF Rotary-wing aircraft.

These services include R&M engineering functions necessary to sustain rotary-wing aircraft and related deficiencies revealed in the operation and maintenance of United States Air Force (USAF) rotary wing aircraft. This effort will focus on R&M issues specific to the HH-60G, HH- 60W, MH-139, UH-1N, and TH-1H rotary-wing aircraft. The Government requires engineering services in support of rotary-wing systems R&M responsibilities.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by sustainment of rotary-wing aircraft that includes a wide range of analysis, to include engineering research integration and technical support services, isolation and analysis of R&M deficiencies, supporting the development, implementation and sustainment of robust rotary-wing reliability centered maintenance (RCM) and Age Exploration (AE) programs, performing maintenance data trend analysis, failure mode and effects analysis updates, preventative maintenance package task updates, AE candidate follow-up, updating existing RCM databases, and producing any engineering data required to implement solutions, in addition to other tasks as noted below in section 4.0. This effort includes preparing monthly status reports, preparing agenda and meeting minutes, quarterly data reviews, and several reports IAW section

2.0. and 4.0.

The Rotary Wing (RW) Engineering Requirements Review (ERR) Support program is being developed in order to document a standardized methodology to fully define, develop, and approve a requirement that ensures scheduled maintenance tasks (for field, depot, or any other level of maintenance) are valid with supportability elements identified at the outset. The RW ERR Support program is comprised of disciplined processes and procedures, organizational, and systematic operating elements designed to improve aircraft repair productivity, with the overall goal of increasing aircraft mission capability, reliability, and maintainability by efficiently executing supportable maintenance tasks. As a result, the RW ERR Support program workload can be broken out into three main areas: Engineering Analysis, Supportability Analysis, and Process Management.

1.3 Background: Air Force Life Cycle Management Center (AFLCMC) has the responsibility within Air Force Materiel Command (AFMC) for all weapon system planning, management, documentation, evaluation and implementation of sustainment support programs.

AFLCMC/WIUE is the engineering component of the System Program Office for AF rotary-wing aircraft. Scarce organic engineering resources and the rapid responses required are the basis for this requirement.

2.0 Services Summary (SS):

Performance Objective PWS Reference

Performance Threshold

Technical Assistance Requests

4.17, 4.17.1

The contractor’s report shall be delivered complete and accurate by the date negotiated with the Government COR. The report shall contain no more

PR: FD2060-21-32087 PWS REVISION: 0 4

than five typographical errors or technical inaccuracies. Rewritten reports shall be resubmitted to WIUB within five business days after notice of rework required. The number of report rejections shall not exceed one per submittal.

Receipt of CDRL deliverable

4.2.1, 4.2.2 There shall be no more than (2) 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.

Quality of CDRL deliverable

4.2.1, 4.2.2 There shall be no more than one rejection of each deliverable. There shall be no more than (2) total rejection(s) of deliverables per quarter. 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 (5) five business days of notification of Government rejection.

Reliability Centered Maintenance (RCM) Target Analysis

4.3.2 The contractor’s report shall be delivered complete

and accurate by the date negotiated with the Government Contracting Officer Representative (COR). The report shall contain no more than five typographical errors or one technical inaccuracy.

Rewritten reports shall be resubmitted to WIUB within five business days after notice of rework required. The number of report rejections shall not exceed one per submittal.

Rapid (“no notice”) response

4.3.2.1, 4.5.1, 4.6.2, 5.5.2

The contractor’s recommendation for problem resolution shall be delivered by email within 24 hours of receipt of notice of grounded aircraft or a safety or mishap issue to include travel plans if directed. A solution recommendation shall be delivered within 72 hours of receipt of notice. No more than one late intent for problem resolution is allowed per quarter. No more than two late problem solution recommendations are allowed per quarter.

For safety or mishaps, no late receipts of recommendations are allowed.

Deficiency Reporting 4.5.2, 4.6.2, 4.6.3, 4.6.4

The contractor’s report shall be delivered complete and accurate by the date negotiated with the Government COR. The report shall contain no more than five typographical errors or one technical

PR: FD2060-21-32087 PWS REVISION: 0 5

inaccuracy. Rewritten reports shall be resubmitted to WIUB within five business days after notice of rework required. The number of report rejections shall not exceed one per submittal.

3.0 Government Property

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

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

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 FAR 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: 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/. Training on how to utilize the GFP module can be found at https://dodprocurementtoolbox.com.

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 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 https://dodprocurementtoolbox.com/

PR: FD2060-21-32087 PWS REVISION: 0 6

no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

3.6 Government System(s): The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract.

4.0 Technical Requirements

4.1 Period and Place of Performance:

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend from 15 August 2022 for a Basic one-year contract and continue with four (4) additional annual option periods through 14 August 2027.

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

However, as the need arise, services maybe performed at Robins, AFB or other government facilities.

4.2 Contract Data Requirements List (CDRL):

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than (2) two total rejection(s) of deliverables per quarter.

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 exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within (5) five business days of notification of Government rejection.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area WorkFlow (WAWF) and submitted directly to the MFT member identified on the CDRL. There shall be no more than (2) 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.

DATA

ITEM

AUTHORITY TITLE/SUBTITLE PWS Reference

A001 DI-ILSS-82114 Reliability-Centered Maintenance Analysis Data

4.3.2

A002 DI-MISC-80508B/T Technical Report - Study/Services 4.3.2.1, 4.3.3, 4.4.1, 4.4.2, 4.5.2, 4.5.3, 4.6.1, 4.6.2, PR: FD2060-21-32087 PWS REVISION: 0 7

4.6.3, 4.6.4, 4.7.4, 4.7.5, 4.14, 4.15, 4.17, 4.1.7.1, 4.17.1.3, 4.18, 4.19, 4.20, 4.21, 4.22

A003 DI-SESS-81000F/T Product Drawings/Models and Associated Lists

4.6.1, 4.8.4, 4.8.5, 4.9, 4.10, 4.11, 4.12, 4.15, 4.16, 4.20

A004 DI-MGMT-80368A Status Report 4.7.2, 4.15, 4.21 A005 DI-FNCL-80331A Funds and Man-Hours Expenditure

Report 4.7.2

A006 DI-ADMN-81249C Conference Agenda 4.7.3, 4.8, 4.8.1, 4.8.2, 4.8.3, 4.8.4, 4.8.5

A007 DI-ADMN-81250C Conference Minutes 4.7.3, 4.8, 4.8.1, 4.8.2, 4.8.3, 4.8.4, 4.8.5

A008 DI-ADMN-81373 Presentation Material 4.7.3, 4.8, 4.8.1, 4.8.2, 4.8.3, 4.8.4, 4.8.5

A009 DI-MISC-81943 Trip/Travel Report 4.22 A00A DI-MGMT-80061A/T Engineering and Technical Services

Accomplishment Report 4.8.3

A00B DI-SESS-81495B Failure Modes, Effects, and Criticality Analysis Report

4.14.2

A00C DI-SESS-81766 Data Item Description Airworthiness Specification

4.5.4

A00D DI-SESS-81768 Airworthiness Certification Criteria Report

4.5.4

A00E DI-ENVR-81840 Programmatic Environmental Safety and Health Evaluation (PESHE) Plan

5.5.2

4.3 Engineering Services Details

4.3.1 Engineering Support Task Request (ESTR) When tasked by the Government, the Contractor shall perform analyses which includes but is not limited to engineering research, rapid solutions, prototypes, integration and technical support services required to isolate and analyze system deficiencies, identify appropriate solutions and produce all engineering data required to implement the improvements to prevent an adverse impact to rotary-wing aircraft reliability and maintainability. The aforementioned tasking will be submitted via an ESTR form shown in Appendix C of this PWS and assigned task number. 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 for the task. A response is due within 10 calendar days of a routine ESTR request receipt and two days for all urgent ESTR requests. The Contractor is not approved to execute the tasks until the contractor has received Attachment 1 form which has been signed by the Government Sustainment Contracting Officer's Representative (COR) /Program Manager (PM). The Contractor shall deliver solution within the cost and timeframe as stated in the associated ESTR quote. The Contractor shall not exceed the ceiling price, except at their risk. In event additional man-hours/cost are required to complete a task, the Contractor shall then submit a requoted form to the COR for review.

4.3.2 RCM Sustainment: The contractor shall provide engineering services to support AFLCMC/WIUB in sustaining rotary-wing aircraft RCM and AE programs. This support includes performing maintenance data trend analysis, failure mode and effects analysis updates, preventative maintenance package task updates, AE candidate follow-up and updating existing

PR: FD2060-21-32087 PWS REVISION: 0 8

RCM databases. RCM and AE programs use information from Failure Mode Effects and Criticality Analysis (FMECA); fracture mechanics analysis reports; stress analysis reports;

Failure Reporting and Corrective Action System reports; fatigue test and fatigue substantiation reports; AF Core Automated Maintenance System data; and in-service engineering data to reduce man-hours and operating costs, while increasing aircraft availability. Analysis will justify existing PM tasks; eliminate unnecessary and redundant tasks; optimize task intervals; document rationale for PM revisions; and serve as the baseline for Integrated Maintenance Concept (IMC) tasks and intervals.

(CDRL A001: DI-ILSS-82114)

4.3.2.1 Target Analysis: Contractor shall provide analysis for rapid response “no notice” engineering support (target analysis) requests. Contractor shall provide failure analysis, follow-up analysis, and independent technical reviews by the date negotiated with the government program manager. (CDRL A002: DI-MISC-80508B/T)

4.3.3 Cyber Security Impact Assessment: The contractor shall provide engineering support to determine whether proposed modifications affect the aircraft cybersecurity posture by completing a Security Impact Assessment (SIA) for other tasks completed under this contract.

The government will provide the appropriate template and instructions. The contractor shall submit the completed SIA to the Rotary Wing ISSM for approval. (CDRL A002: DI-MISC- 80508B/T)

4.4 Electrical, Avionics and Electromagnetic Interference/ Electromagnetic Compatibility (EMI/EMC) Analysis:

4.4.1 Analysis: The contractor shall provide engineering support to resolve electrical, avionics and EMI/EMC deficiencies on rotary-wing aircraft. The contractor shall provide engineering support to identify, isolate analyze and resolve deficiencies related to these weapon systems and produce all required engineering data including data for an updated Electrical Load Analysis by the date negotiated with the Government program manager. (CDRL A002: DI-MISC- 80508B/T)

4.4.2 Test Plan/Data Analysis: In the cases of EMC/EMI compatibility or where proposed mechanical or electrical solutions do not comply with form, fit, function, and interface requirements, the contractor shall analyze the test plan(s) and other existing TDPs that define the platforms to ensure possible deficiencies are detected and resolved. (CDRL A002: DI-MISC- 80508B/T)

4.5 System Safety:

4.5.1 The contractor shall assist AFLCMC/WIUB with executing the system safety program responsibilities IAW Air Force Instructions (AFI) 91-202, The USAF Mishap Prevention Program and Military Standard (MIL-STD) 882, System Safety Program Requirement. The AFLCMC/WIUB Safety program is responsible to ensure, among other things, 1) a safety hazard analysis, as appropriate, is conducted for all new projects, 2) hazard risk assessments are evaluated to determine if all residual risk has been mitigated satisfactorily and is acceptable to

PR: FD2060-21-32087 PWS REVISION: 0 9

the appropriate Government approval authority, 3) mishaps and incidents are investigated and recommended actions are tracked until implemented, 4) flight and ground test operations are assessed for safety risk, and 5) safety communication is maintained between Special Operations Forces/Personnel Recovery PM, contractor and using command safety personnel.

4.5.2 The contractor shall provide hazard identification through safety analysis conducted on system/subsystem modifications, engineering change proposals, mishap data and deficiency reports by the date negotiated with the Government program manager. (CDRL A002: DI-

MISC-80508B/T)

4.5.3 System Safety Hazard Analysis Report (SSHA): Analyses which result in a Military Standard 882 Revision E (MIL-STD-882E), System Safety, Table III, Risk Assessment Matrix, Risk Assessment Code (RAC) of 1A, 1B, 1C, 1D, 2A, 2B, 2C, 3A or 3B shall require an SSHA.

For other RACs, an SSHA shall be generated as required by the AFLCMC/WIU SSM. Each SSHA shall be submitted to AFLCMC/WIU SSM for Government review and acceptance. The SSHA shall be in the format outlined in AFI 91-202, Mishap Prevention Program, Attachment 15, Preparation of Risk Assessments. (CDRL A002: DI-MISC-80508B/T)

4.5.4 System Safety Airworthiness: The contractor shall assist AFLCMC/WIUB with the development and management of modified airworthiness certification criteria (MACC) basis and compliance reports IAW MIL-HDBK-516C, and AWB-150B. (CDRL A00C: DI-SESS-

81766), (CDRL A00D: DI-SESS-81768)

4.6 Reliability & Maintainability Improvement:

4.6.1 The contractor shall provide engineering support to isolate and analyze aircraft functional system deficiencies, identify appropriate solutions and produce all engineering data required to implement the improvements to prevent an adverse impact to rotary-wing aircraft reliability and maintainability. (CDRL A002: DI-MISC-80508B/T), (CDRL A003: DI-SESS-81000F/T)

4.6.2 Field Support: In addition to routine technical support to the operators of fielded rotary-wing aircraft, a rapid response may be directed for “no notice” deficiency, grounded aircraft and mishap support for issues such as, but not limited to, paragraphs 4.3.1.1, 4.7.4, Section 4.4 (all), Section 4.5 (all), paragraphs 4.6.2 through 4.6.4, and 4.10 through 4.19 of this PWS. The contractor’s recommendation for problem resolution shall be delivered by email within 24 hours of the receipt of notice of grounded aircraft, safety or mishap issue to include travel plans if directed. Solution recommendation shall be delivered with 72 hours of receipt of notice. This rapid response support includes recommendations for updating and maintaining the accuracy of operational data in the flight and technical manuals up to travel of contractor personnel to the aircraft or other problem site. The depots and/or the fielded units use several forums to identify problems. The forums include Joint Depot Level Maintenance (JDLM) Document changes, TO changes, Product Quality Deficiency Reports (PQDRs), Product Improvement Working Group (PIWG) action items, Technical Manual Change Recommendation and Reply (AFTO 22) Preliminary. Technical Order (PTO) Publication Change Request (PCR)/TO Verification

PR: FD2060-21-32087 PWS REVISION: 0 10

Record/Approval (AFTO 27), Source, Maintenance, Recoverability Code Change Request (AFTO 135), Recommendation for Change of Publication (AFTO 847), Critical Item Lists, requests for engineering support from the field, safety or hazard reports, accident or incident reports, aircraft fuel contamination reports, or any other deficiency and engineering support report submitted. (CDRL A002: DI-MISC-80508B/T)

4.6.3 Configuration Management: The contractor shall assist in maintaining configuration management for rotary-wing weapon systems per Department of Defense Instructions (DoDI)

5000.02 and AFI 63-1201. Contractor shall perform activities to include, but not limited to, analysis of aircraft systems to establish weapons systems baselines, functional and physical configuration audits, analysis and support of configuration control boards and deficiency report review board investigations. Reports will be delivered by the date negotiated with the Government program manager. (CDRL A002: DI-MISC-80508B/T)

4.6.4 Production Engineering Support: The contractor shall review document changes and deficiency reports submitted by the depot facility. Reports include JDLM document changes, TO changes, PQDRs, safety or hazard reports, accident or incident reports, aircraft fuel contamination reports or any other deficiency report submitted. Reports will be delivered by the date negotiated with the Government program manager. (CDRL A002: DI-MISC-80508B/T)

4.7 Program Management: The contractor shall have the responsibility for the management, administration, financial control, engineering, manufacturing, procurement, testing and quality assurance activities associated with this effort. All program management requirements of the contract shall extend to the effort required by this PWS. The contractor shall be responsible for selecting the correct components and ensuring they meet performance and integration specifications.

4.7.1 Documentation: All documentation shall be delivered electronically in a current version of a Microsoft Office product. In accordance with DoD policy, every effort shall be made to provide “paperless” electronic or digital deliveries.

4.7.2 Monthly Status Reports: The contractor shall provide status reports to the Government no later than the 15th day of each month. The reports shall cover engineering and technical support provided by the contractor during the previous monthly period. The contractor shall document task status, data deliverables, problems and expenditure data. Expenditure data from report shall match invoice for each billing period. At a minimum, a milestone chart, actual/projected spending rate and estimated man-hours for each aircraft platform supported should be included to provide tracking from each fund source. There are potentially five major fund sources Air Combat Command (ACC), Air Force Global Strike Command (AFGSC), Air Education and Training Command (AETC), Air National Guard (ANG) and Air Force Reserve Command (AFRC) that must be separately tracked by labor hours, Material and Subcontractors and Travel. In addition, all problem areas will be covered, with recommended solutions and the outcome expected after solutions are implemented. The contractor shall assign and track action items for each unresolved program problem or issue. The contractor shall assign action item numbers based on the program and action item source. The contractor shall provide a list of projected travel requirements in the MSRs. Regular updating of cumulative cost versus estimated

PR: FD2060-21-32087 PWS REVISION: 0 11

total cost shall be submitted in the MSRs. A “burn rate” chart that plots actual and planned expenditures and man-hours by labor category against time shall be included with each monthly status outcome after solutions are implemented. The contractor shall ensure the status report is delivered on the appropriate delivery date. Every attempt shall be made by the contractor to provide “paperless” electronic or digital deliveries. Monthly Status Reports shall be submitted as e-mail attachments in a Microsoft Office-compatible format. (CDRL A004: DI-MGMT-

80368A), (CDRL A005: DI-FNCL-80331A)

4.7.3 Quarterly Data Reviews: The contractor shall participate in quarterly data reviews.

These reviews shall include status summarizing the analysis performed during the reporting period, including the identification of program savings/costs. For all data reviews/technical meetings, conferences and the like that are necessary, the contractor shall also furnish the proposed agenda, presentation materials and the resulting minutes. (CDRL A006: DI-ADMN-

81249C), (CDRL A007: DI-ADMN-81250C), (CDRL A008: DI-ADMN-81373)

4.7.4 Technical Reviews/Reports: The contractor shall perform independent technical reviews of analysis and/or data submitted for Government review and approval. The intent of these reviews is to ensure the data is accurate and complete. The analysis shall consider all appropriate performance and sustainment requirements of the RCM and AE program. This review shall provide the government with a recommendation to accept or disapprove, with deficiencies identified and rationale thoroughly explained. (CDRL A002: DI-MISC- 80508B/T)

4.7.5 Final Report: The contractor shall create and submit a final report to the government for review and approval. The report shall summarize all tasks the contractor has performed under this effort. The report shall include, but not be limited to, all findings, deficiencies, conclusions and recommendations for repairs, and a list of tasks not yet completed. The final report shall be submitted at the end of the current PoP. (CDRL A002: DI-MISC-80508B/T)

4.8 Meetings: The contractor shall be responsible for attending/hosting meetings at their local office IAW the following paragraphs. In support of the meetings and conferences, the contractor shall furnish agendas, presentation materials and resulting meeting minutes, as required. (CDRL

A006: DI-ADMN-81249C), (CDRL A007: DI-ADMN-81250C), (CDRL A008: DI-ADMN-

81373)

4.8.1 Kick-Off Meeting: The contract activities shall begin with a face-to-face “kick off” meeting within thirty (30) days after receipt of contract award. The meeting shall be convened at Robins Air Force Base or nearby location as determined by the government PM. The specific times and dates will be negotiated by the contractor and government PM. The government PM will make the appropriate arrangements for the contractor’s personnel access to Robins AFB as required. A task schedule shall be developed during this initial meeting. The contractor shall furnish the proposed agenda and presentation material for the meeting, and the resulting minutes.

(CDRL: DI-ADMN-81249C), (CDRL A007: DI-ADMN-81250C), (CDRL A008: DI-

ADMN-81373)

PR: FD2060-21-32087 PWS REVISION: 0 12

4.8.2 Conferences: The contractor, if required by the government PM, shall attend the annual Helicopter PIWG. In performing this service, the contractor shall identify solutions to resolve action items assigned to AFLCMC/WIUB during the conference. In support of the Helicopter PIWG and other meetings and conferences, the contractor shall furnish the agenda, presentation material and resulting meeting minutes as required. (CDRL A006: DI-ADMN-81249C), (CDRL A007: DI-ADMN-81250C), (CDRL A008: DI-ADMN-81373)

4.8.3 Program Review: The government and the contractor shall participate in Program Reviews and technical meetings. Program reviews will be conducted quarterly, and an engineering guidance conference will be conducted 60 days ARO. The program reviews shall be convened at Robins Air Force Base or nearby location as determined by the government PM.

The times and dates will be negotiated by the contractor and government PM. The government PM will make the appropriate arrangements for the contractor’s personnel access to Robins AFB as required. The contractor shall furnish the proposed agenda and presentation material for the meeting, and the resulting minutes. (CDRL A006: DI-ADMN-81249C), (CDRL A007: DI-

ADMN-81250C), (CDRL A008: DI-ADMN-81373), (CDRL A00A: DI-MGMT-80061A/T)

4.8.4 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) Contract data requirements list (CDRL), applicable data item description, specifications and standards.

b) TDP review requirements and schedules.

c) TDP delivery requirements and schedules.

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

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

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

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

h) Digital TDP deliverables.

(CDRL A003: DI-SESS-81000F/T), (CDRL A006 : DI-ADMN-81249C), (CDRL A007:

DI-ADMN-81250C), (CDRL A008: DI-ADMN-81373)

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

4.8.5 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

PR: FD2060-21-32087 PWS REVISION: 0 13

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 A003: DI-SESS-81000F/T), (CDRL A006: DI-ADMN-81249C), (CDRL A007: DI-

ADMN-81250C), (CDRL A008: DI-ADMN-81373)

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

(CDRL A003: DI-SESS-81000F/T)

4.10 Engineering Data: The contractor shall develop/produce/maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product. 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. 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 delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision M (CAGE 98752), reference attached DD Form 1423 Block 16. (CDRL A003: DI-SESS-81000F/T)

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

PR: FD2060-21-32087 PWS REVISION: 0 14

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.

(CDRLA003 : DI-SESS-81000F/T)

4.12 Engineering Drawing Deliverables: The contactor shall review, revise, and update all drawings provided by the government and deliver to the Engineering Data Management Office for uploading into the Joint Engineering Data Management Information and Control System.

The delivered drawings shall meet the proper format provided in the CDRL. All engineering product definition data created as a result of this contract shall be delivered to the government with unlimited rights. The drawings shall be delivered IAW AF Product Data Specification drawing 9579776 (CAGE 98752), reference attached DD Form 1423 Block 16.

(CDRL A003: DI-SESS-81000F/T)

4.13 Technical Data: Contractor shall develop the TO change pages necessary for the operation, maintenance, and support of the program requirements will be referred to the TO manager (TOMA) in accordance with this PWS. The government will retain the right of approval of the formal TOs through the certification and verification process and the pre-pub review.

4.13.1 Operational Technical Orders (TOs): Contractor shall review the applicable Operational TOs and prepare properly formatted data IAW the TOMA’s instructions and in accordance with this PWS.

4.13.2 Maintenance Manuals: Contractor shall review the applicable Maintenance TOs and prepare properly formatted data IAW the TOMA’s instructions and in accordance with this PWS.

4.13.3 Certification/Verification: Government will be permitted to witness Data Certification.

Contractor shall notify the government two (2) weeks prior to certification beginning. A certification shall be conducted on the prototype, and Air Force verification of hands-on procedures shall be conducted on the kit proof aircraft. Contractor shall provide support in all areas prescribed by the government for the verification phase.

4.13.4 Time Compliance Technical Order (TCTO): Contractor shall develop source data for a new TCTO to document the final configuration of the modification and instructions for removal of the existing systems (if required). The TCTO shall be prepared IAW TO 00-5-15, Military Detail Specifications 38804C, and the applicable Air Force Materiel Command (AFMC) Form 873. The TCTO Verification shall be accomplished during kit proof installation.

PR: FD2060-21-32087 PWS REVISION: 0 15

4.14 Failure Modes: The contractor shall investigate failure modes for low Mean Time Between Failure (MTBF) components and develop/recommend solutions to improve MTBF via component redesign, material changes and/or maintenance practice changes by the dates negotiated by the contractor and government PM. The focus shall be on high maintenance drivers and safety issues, as assigned by engineering AFLCMC/WIUE. (CDRL: DI-MISC- 80508B/T)

4.14.2 Failure Modes, Effects and Criticality Analysis Report: Contractor shall submit a FMECA report as required detailing all analyses of independent single item failures and the resulting potential impact on mission success, performance, safety, and maintainability in order that appropriate corrective actions may be taken to eliminate or control high risk items.

(CDRL A00B: DI-SESS-81495B)

4.15 Engineering Data Revisions: The contractor shall also provide support for drawing corrections, engineering change orders and revisions. When deficiency resolution requires creating or updating drawings and specifications the contractor shall update and submit to the requesting activity, based on information furnished or previously available and provide as an attachment to the monthly status report. Engineering drawings and associated lists shall be design documents and shall conform to established military specifications and standards. In the event the drawings and specification do not conform to the established standards, the affected data shall be revised to conform to basic specifications for which the data was originally prepared. Data shall be IAW paragraph 4.3.4. unless otherwise specified by the government.

(CDRL A002: DI-MISC-80508B/T), (CDRL A004: DI-MGMT-80368A), (CDRL A003:

DI-SESS-81000F/T)

4.16 Data Packages: The contractor shall provide support in updating existing TDPs, reviewing drawings, updating qualification requirements and qualified vendor status to allow competitive parts procurement as required. Updated data shall be IAW paragraph 4.13 unless otherwise specified by the Government. (CDRL A003: DI-SESS-81000F/T)

4.17 Technical Assistance Requests: The contractor shall perform failure analysis, follow-up analysis and independent technical reviews of requests for technical assistance from the field and Depot as requested by the Government. (CDRL A002: DI-MISC-80508B/T)

4.17.1 Engineering Requirements Review (ERR) Support (Initiation to Requirements Review Board (RRB)) The Contractor is responsible for ensuring each maintenance task completes the process, and serves as the champion for individual maintenance tasks as they move through the process.

4.17.1.1 The contractor shall perform data analysis and support sustainment of Structural Significant Items (SSI), Other Structural Items (OSI), Maintenance Significant Items (MSI) and Zonal tasks as they relate to both structures, systems, and zonal analysis consistent with Maintenance Steering Group-3 (MSG-3) philosophy. These analyses and supporting documentation shall be delivered in a technical report. (CDRL A002: DI-MISC-80508B/T)

PR: FD2060-21-32087 PWS REVISION: 0 16

4.17.1.2 The Contractor shall support review and generation of ERRs for all MSG-3 tasks (both new and old) and any new tasks that arise out of reviews of existing tasks. All reviews and the generation of new ERRs will be done using the ERR Form and instructions depicted in Para 3.14

– 3.16 of AFMAN 63-143 as shown in Section 7 of this PWS. For example, if an inspection task is reviewed and the review process determines that the sustainment strategy should change to a time change requirement, the resulting new MSG-3 task to establish the maintenance requirements for the time change is included in the scope of work for this PWS. Excluded from this scope are major modifications to existing systems or development of new sub-systems for which legacy maintenance requirements never existed.

4.17.1.3 The Contractor shall support investigations into deficiencies that are identified throughout the fleet and make recommendations for RAM improvements once identified for existing or new RW ERRs. The Contractor shall support Operational Safety, Suitability and Effectiveness (OSS&E) in accordance with Air Force Materiel Command (AFMC) AFLCMC/WIU requirements while performing analysis. (CDRL A002: DI-MISC-80508B/T)

4.17.1.4 The Contractor shall ensure that all reviews, findings, and recommendations are documented in the appropriate ERR data repository provided by Government.

4.18 Software Deficiencies: The contractor shall provide engineering assistance with software deficiencies including, but not limited to: providing thorough reviews, engineering design and analysis, review and analysis of technical data, supporting user requests, and attending reviews and work group meetings as required. The contractor shall also identify solutions to deficiencies revealed in the operations and maintenance of rotary-wing aircraft. The contractor may be tasked to evaluate these new requirements and designs by altering materials and/or combining components into a new assembly or system as a prototype/proof of concept.

(CDRL A002: DI-MISC-80508B/T)

4.19 The contractor shall work with the Government to analyze and develop corrective actions for design-related supportability and maintenance deficiencies. (CDRL A002: DI-MISC- 80508B/T)

4.20 The contractor shall serve as POC for resolving engineering issues and correct existing engineering data, as required. (CDRL A002: DI-MISC-80508B/T), (CDRL A003: DI-SESS- 81000F/T)

4.21 The contractor shall track inbound and outbound engineering field calls to determine problematic trend areas, respond to service-related deficiencies and report this to AFLCMC/WIUBC in the MSRs. (CDRL A002: DI-MISC-80508B/T), (CDRL A004: DI-

MGMT-80368A)

4.22 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 IAW the assigned tasks. Travel will be reimbursed according to the rates outlined in the Federal Travel

PR: FD2060-21-32087 PWS REVISION: 0 17

Regulations for travel within the CONUS; Joint Travel Regulations for travel to Alaska, Hawaii and outlying areas of the US; and the rates established by the Department of State for travel outside of the OCONUS. Airfare shall consist of 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 business days in advance from both the Procuring Contracting Officer (PCO) and the 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/WIUKB, Robins AFB GA has not been received. Travel by Contractor personnel shall be conducted in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance, JTR, and clauses listed in the contract. Trip Reports shall be submitted to AFLCMC/WIUBC NLT five business days upon return from the trip. (CDRL A002: DI-MISC-80508B/T), (CDRL A009: DI-MISC-81943)

4.24 Counterfeit Electronic Parts:

4.24.1 The Contractor shall establish and maintain a counterfeit electronic part detection and avoidance system to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory.

4.24.2 The system shall incorporate processes/procedures to address the requirements listed in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The Government's review of the Contractor’s system will be accomplished as part of the evaluation of the Contractor’s purchasing system in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

4.25 Holidays and facility closings: Contractor personnel shall observe the ten federal holidays and facility closings, e.g., energy down days, authorized by the Government in accordance with AFMC MP5337.1, Service Contracts - General. Contractor personnel will only be permitted access to Government facilities when Government personnel are present.

4.26 Local Office: Contractor shall document the business has an office facility with a City of Warner Robins address. The place of business may not be a post office box but a physical address maintained for the duration of the contract PoP. The contractor shall be responsible for attending/hosting meetings at their local office.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander (FC) or civilian equivalent has determined these services are not mission-essential and services will not continue in the event of a crisis.

5.2 Security Requirements

PR: FD2060-21-32087 PWS REVISION: 0 18

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. The Contractor shall comply with the following security regulations: Department of Defense (DoD) 5200.2-R, Personnel Security Program; DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program, DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual, and Robins Air Force Base Integrated Defense Plan (RAFB IDP) 31-101.

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. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.)

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

5.2.4 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 DoD 5220.22- M. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

5.2.5 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.6 Security Incident or Violation: The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.2.7 Access to Government System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted.