14_30815_PWS_as_of_1Jul14.pdf

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S Page 1

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

H-60/H-1 SUSTAINING ENGINEERING SUPPORT

Revision 0

DATE: 26 Mar 2014

CONTENTS

SECTION 1 DESCRIPTION OF SERVICES 2

SECTION 2 SERVICES SUMMARY 3

SECTION 3 GOVERNMENT FURNISHED PROPERTY & SERVICES 4

SECTION 4 GENERAL INFORMATION 5

SECTION 5 APPENDICES 18

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

Prepared by: Joshua Lee/AFLCMC/WIUBB/472-1332

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 2

PERFORMANCE-BASED WORK STATEMENT (PWS)

1.0 DESCRIPTION OF SERVICES: This Performance Based Work Statement defines the services needed to provide engineering, programmatic and technical support services to support the AFLCMC/WIU rotary aircraft (H-60 variants/H-1 variants) Acquisition and Sustainment Life Cycle Management per AFI 63-101, Product and System Integrity. It mandates Aircraft Structural Integrity Program (ASIP) in accordance with (IAW) Military Standard 1530C (MIL-STD-1530C), and Mechanical Equipment and Subsystem Integrity Program (MECSIP) per MIL-STD-1798B as part of an overall aging aircraft life cycle management sustainment effort.

This effort will focus on identifying and solving structural integrity issues, especially issues associated with the increasing age of the aircraft such as fatigue cracking, damage tolerance, and corrosion. Implementation of a Condition Based Maintenance (CBM) Program is also a critical part of the Aging Aircraft sustainment effort. Engineering and technical support throughout implementation, fielding and sustainment of a Health Usage Monitoring System (HUMS) on the United States Air Force (USAF) rotary wing fleet and ensuring integration of resultant data in establishing the Rotorcraft Dynamic Component Tracking (RDCT) program will enable successful implementation of the CBM Program. Additionally, this effort will include USAF Net worthiness Certification for all software required to support data management and utilization for the Integrated Vehicle Health Management System (IVHMS) program. The contractor shall provide complete and accurate, Monthly Status Reports (MSRs), deliver punctual and correct Technical Interchange Meeting (TIM) Agenda and Minutes, and provide technical reports on time as required. The contractor shall conduct an acceptable Safety Program and be punctual with mishap notification and reporting.

1.1 SCOPE: Concern about the structural and mechanical soundness of the AFLCMC/WIU rotary aircraft has been raised as they continue to age and are expected to be in service past 2035.

This effort addresses those concerns through investigation of life predictions and failure analyses that are a direct concern of long-term aircraft use. It includes consideration of fatigue effects or corrosion that are seen on aircraft after a substantial time in service, consideration of the effects of new structure that has been added to the aircraft due to modifications, upgrades, and investigation of aircraft usage over its service life and comparison of that usage to original design intent. The contractor shall update existing AFLCMC/WIU rotary-wing aging aircraft ASIP/MECSIP models to reflect current configuration and loadings. The contractor shall identify (through computer models, records surveys, non-destructive inspections, and other methods as appropriate) specific high fatigue areas, perform life predictions on the aging aircraft, and suggest solutions to extend/maintain the airframe’s economically viable life as the aircraft continues to age. The contractor shall also assist the program office with any in depth engineering analysis required to sustain the aircraft, such analysis will be required to assist Air Force engineers with repairs and maintenance of the aircraft. Requirements specific to these tasks are outlined in this PWS.

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 3

2.0 SERVICES SUMMARY: The contractor shall support the AFLCMC/WIU rotary engineering office (AFLCMC/WIUEC) in the performance and maintenance of rotary ASIP /MECSIP efforts. The contractor shall perform the tasks listed below, based upon priorities established by AFLCMC/WIUEC points of contact.

Performance Objectives PWS Para.

Performance Threshold

Monthly Status Reports (MSRs)

4.1.2 4.1.4

4.2.5.1 4.3.3 4.4.5

The contractor shall prepare monthly status reports describing the status and progress of task efforts in work. The report shall contain no more than a total of five (5) typographical errors and/or technical inaccuracies. Errors shall be corrected within five

(5) workdays. Results will be summarized on a quarter Performance Assessment Report (PAR).

Technical Interchange Meeting (TIM) Agenda and Minutes

4.1.3 4.1.7.1 4.1.10 4.1.11 4.2.2 4.2.3 4.4.2 4.4.3 4.4.4

The contractor shall submit an agenda at least three

(3) workdays in advance of the meeting. Minutes shall be submitted no more than five (5) workdays after the meeting. The contractor’s minutes shall be complete and accurate; the number of rejections shall not exceed one per six (6) month period.

Rewritten minutes shall be resubmitted within five

(5) workdays.

Technical Reports 4.1.2 4.1.4

4.1.7.1 4.1.7.2 4.1.7.3

4.1.7.3.1 4.1.7.3.2

4.1.9 4.1.12 4.1.13 4.1.14 4.1.15 4.1.16 4.2.1

4.2.5.1 4.2.5.1.3 4.2.5.1.4

4.2.6 4.3.1 4.3.2 4.4.5

Upon notification, the contractor shall provide the date for report submittal within two workdays.

Government will review submitted reports, submit changes/corrections within five (5) days. Rewritten reports shall be resubmitted within five (5) workdays. The contractor shall deliver a final technical report that documents the technical tasks, data acquired, and updates to existing documentation. A draft final technical report shall be submitted complete and accurate no later than thirty (30) calendar days prior to the end of the period of performance (POP), the number of report rejections shall not exceed one (1) per submittal.

The government will submit changes/corrections within five (5) workdays. The final copy of the final technical report shall be submitted no later than the end of the POP.

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 4

Mishap Notification and Reporting

4.6 4.6.1 4.6.2

No more than two (2) Class C mishaps per contract per year and zero (0) Class A or B mishaps. No more than one (1) instance of late mishap notification per calendar year.

3.0 GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, MATERIAL, and

SERVICES (GFP/GFE/GFM/GFS).

3.1 GOVERNMENT FURNISHED INFORMATION (GFI): During the POP of this task, AFLCMC/WIU will provide the data necessary, on an as-available basis, for the accomplishment of this task. This may include engineering reports, the most current AFLCMC/WIU rotary aircraft ASIP/MECSIP Master Plans, Technical Orders (TO) for inspections, maintenance, Individual Aircraft Tracking (IAT) airplane usage data, Joint Airframe Condition Evaluation crack and corrosion data, service life reports, finite element models and analyses, Reliability Centered Maintenance data etc. All data, whether hard or electronic copy, remains the property of the USAF and shall be returned to AFLCMC/WIUB upon completion of the contract. Data may only be retained by the contractor if a follow-on effort has already been established.

3.2 GOVERNMENT FURNISHED PROPERTY (GFP): During the POP, the

government will provide contractor access to government equipment for the accomplishment of required tasks. Access will be provided on an as-available basis and unless otherwise specified, all equipment will remain at its current location. Equipment may include aircraft and/or components, maintenance test equipment, jigs, fixtures, etc. All equipment, regardless of location, remains the property of the U.S. Government and must be returned to the government within ten (10) days of completion of the task requiring the equipment or within ten (10) days of completion of the contract unless a follow-on effort is coordinated, whichever comes first.

3.3 GOVERNMENT FURNISHED MATERIAL (GFM): No GFM will be provided by AFLCMC/WIUB; however, material can be purchased using the material line item of the contract. Any material obtained in this manner is considered property of the U.S. Government and shall be returned within ten (10) days of completion of the contract unless a follow on effort is coordinated. Expendable items will not need to be returned to the government. It is also understood that software licenses will be purchased under this effort and will be turned over to the government. All purchases must be coordinated through the contracting officer. When possible, purchase request should be consolidated into a monthly request and submitted for government approval.

a. GFM/GFE is not authorized.

b. Contractor shall furnish all material and parts necessary for the completion of effort.

3.4 REPORTING LOSS OF GOVERNMENT PROPERTY:

a. Definitions. As used in this clause—

“Government property” is defined in the clause at Federal Acquisition Regulation (FAR) 52.245-1(a), Government Property. “Loss of Government property” means unintended, unforeseen, or accidental loss, damage, or destruction of government property that reduces the government’s expected economic benefits of the property. Loss of

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 5 government property does not include purposeful destructive testing, obsolescence, normal wear and tear, or manufacturing defects. Loss of government property includes, but is not limited to—

1) Items that cannot be found after a reasonable search;

2) Theft;

3) Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition; or

4) Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair.

“Unit acquisition cost” means—

1) For government-furnished property, the dollar value assigned by the government and identified in the contract; and

2) For contractor-acquired property, the cost derived from the contractor’s records that reflect consistently applied, generally acceptable accounting principles.

b. Reporting loss of government property.

(1) The contractor shall use the Defense Contract Management Agency (DCMA) eTools software application for reporting loss of government property. Reporting value shall be at unit acquisition cost. The eTools “Loss Theft Destruction Damage of Government Property” toolset can be accessed from the DCMA home page External Web Access Management application at http://www.dcma.mil/aboutetools.cfm.

(2) Unless otherwise provided for in this contract, the requirements of paragraph (b)(1) of this clause do not apply to normal and reasonable inventory adjustments, i.e., losses of low-risk consumable material such as common hardware, as agreed to by the contractor and the Government Property Administrator. Such losses are typically a product of normal process variation. The contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation.

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

(4) This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this delivery order.

4.0 GENERAL INFORMATION:

4.1 GENERAL REQUIREMENTS:

4.1.1 The contractor shall provide a single task order manager with authority and responsibility for this task.

4.1.2 MONTHLY STATUS REPORTS (MSRs): The contractor shall deliver MSRs in electronic format by electronic mail no later than fifteen (15) calendar days after the beginning of each month. The reports shall cover services provided by the contractor during the previous monthly period. The contractor shall document task status, data deliverables, contract issues and

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 6 actions, expenditure data, and anticipated future task requirements during the next reporting period. Regular updating of cumulative cost versus estimated total cost in the form of a “Burn Rate” chart(s) that plots actual expenditures, planned expenditures, and man-hours against time shall be included with each monthly status report. A report of monthly purchased items shall be included in the MSRs. Included with the MSR will be all technical reports that may have been generated during the month of performance. Technical reports will be those reports generated as a result of a special government request such as detail engineering work requested to support Air Force engineers in response to Technical Assistance Requests (TARs) and AFMC form 202 requests or other tasks requested to assist in maintaining the aircraft. The contractor’s reports shall be complete and accurate, so that the number of report rejections shall not exceed one per each six (6) month period. If a report is rejected, it will be returned to the contractor within five

(5) workdays. The rewritten report shall be resubmitted to WIUEC within five (5) workdays.

WIUECs final approval will be reported to the contractor within five (5) workdays. (DI-MISC-

80508B, DI-MGMT-80368A)(A001, A002)

4.1.3 TECHNICAL INTERCHANGE MEETINGS (TIMs): The contractor shall hold TIMs quarterly. These TIMs shall provide status to the government of progress, problems and issues. All meetings shall be held at the contractor’s facility, unless requested by the government to be held at AFLCMC or another location. The contractor shall provide an agenda for the meeting at least three (3) workdays in advance. The contractor shall attend and document minutes of task reviews and TIMs related to this task. Minutes must be submitted to the government within ten (10) workdays after the meeting. The contractor’s minutes shall be complete and accurate; the number of rejections shall not exceed one (1) per each six (6) month period. If a report is rejected, it will be returned to the contractor within five (5) workdays, the revised report shall be resubmitted to AFLCMC/WIUB within five (5) workdays with final approval reported to the contractor within five (5) workdays. (DI-ADMIN-81249A, DI-

ADMIN-81250A, DI-ADMIN-81373)(A005,A006,A007)

4.1.4 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 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 traveling outside OCONUS. The applicable rates are those in effect at the time of travel and are subject to the limitations outlined in FAR Part 31.205-26. Airfare shall be limited to 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) workdays 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/WIKA, Robins Air Force Base (RAFB) Georgia, has not been received. All travel shall be IAW Department of Defense (DoD) JTR. Trip Reports shall be submitted to AFLCMC/WIUB no later than (NLT) five (5) workdays upon return from the trip. (DI-MISC-80508B, DI-MGMT-

80368A, DI-FNCL-80331A)(A001, A002, A004)

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 7

4.1.5 PLACE OF PERFORMANCE: The place of performance for this contract will be a combination of a U.S. Government installation Robins AFB and not on a U.S. Government installation. Access to Robins AFB by contactor shall be required to attend technical meetings.

4.1.6 DIGITAL DELIVERY: All data shall be delivered on electronic media in a current version of a Microsoft® Office® product format. Per DoD policy, every attempt shall be made to provide "paperless" electronic or digital deliveries. For example, MSRs and the Final Report shall be submitted by electronic mail in a Microsoft® Office® and/or Adobe® Acrobat compatible format.

4.1.7 TECHNICAL OBJECTIVES AND GOAL

4.1.7.1 ASIP and MECSIP MASTER PLAN, FORCE STRUCTURAL MAINTENANCE PLANS (FSMPs) and CBM: The contractor shall update and maintain the AFLCMC/WIU rotary-wing aircraft ASIP and MECSIP Master Plans to include corrosion plans and FSMPs.

The contractor shall update and maintain the AFLCMC/WIU rotary aircraft Master Plans and FSMPs based on IVHMS/VMS/HUMS data as it supports CBM. The contractor shall provide support to the CBM Working Group (WG) Lead for the development of CBM for the HH-60 fleet. The contractor shal support the CBM WG and Analysis Meetings through participation of weekly meetings, interfacing with the Army and Navy CBM programs, and all meetings designated by the USAF HH-60 System Program Office. This shall include the preparation, tracking, and execution of all agendas, action item lists, component/aircraft watch lists and provide technical expertise in analysis and the evaluation of HUMS equipped aircraft. This shall include leading and actively participating in the CBM WG in order to identify and execute the PM’s implementation plan for CBM. The contractor shall support all briefings, meetings, conferences, and liaison with other organizations as directed by the government. The contractor shall execute the CBM WG Charter and Roles and Responsibilities as defined by those documents. The contractor shall work to establish, update and maintain the CBM Manual as required by the addition of new CBM initiatives. The contractor shall also assist the Air Force with depot maintenance work requirements as they apply to ASIP and MECSIP. (DI-MISC-

80508B, DI-ADMIN-81249A, DI-ADMIN-81250A, DI-ADMIN-81373) (A001, A005, A006,

A007)

4. 1.7.2 STRUCTURAL LOADS ANALYSIS: The contractor shall develop updated structural loads for the aircraft as directed. Measured strains and deflections for ground and flight loads shall be used to validate global and local structural models and to provide input to static, fatigue, and D/DTA. The contractor shall be required to use structural load analysis it assist in special government projects such as detail engineering work requested to support Air Force engineers is responses to Technical Assistance Requests (TARs) and AFMC form 202 requests or other tasks requested to assist in maintaining the aircraft.

contractor responses to special engineering requests will be provided in simple format so that the government engineers can complete the work related to the special requests. Structural analysis reports will be generated that support the responses to the special request and be provided within thirty (30) days of the special request. (DI-MISC-80508B, DI-MISC- 81384/T ) (A001, A00D)

4.1.7.3 DURABILITY AND DAMAGE TOLERANCE ANALYSIS (D/DTA): The contractor shall implement damage tolerance concepts on selected AFLCMC/WIU rotary-wing

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 8 aircraft airframe components. Contractor shall review, update, and create damage tolerance analysis as required to support ASIP. (DI-MISC-80508B, DI-MISC-81384/T ) (A001, A00D)

4.1.7.3.1 PROBLEM AREA ASSESSMENTS: The contractor shall provide the government with an assessment of the specified problem areas and an indication of the magnitude of the problem in terms of margin of safety, cycles to failure, cycles to initial detectable crack length, estimated hours to failure, estimated hours to initial detectable crack length, and/or other commonly understood measure of expected life (as appropriate to the structure being analyzed).

The contractor shall recommend inspection intervals, maintenance actions, and inspection procedures. (DI-MISC-80508B) (A001)

4.1.7.3.2 GLOBAL AND LOCALIZED STRUCTURAL ANALYSIS: The contractor shall review and update the global and localized structural analysis of the AFLCMC/WIU rotary-wing aircraft airframes by evaluating structural analysis reports and defined structural hotspots, collecting failure data on structural hotspots, and accomplishing structural and fatigue analysis on isolated components. As required, the contractor shall accomplish mechanical testing to substantiate analysis results. D/DTA analysis and Stress, Fatigue, and Fracture Analysis shall be documented in the form of a technical reports for each area studied and provided at the end of the analysis or within thirty (30) days of when analysis is completed and shall be delivered with the MSRs. Past D/DTA and Stress, Fatigue and Fracture Analysis shall be evaluated and updated.(DI-MISC-80508B, DI-SESS-81704,DI-SESS-81939,DI-MISC-81485) (A001, A003,A00B,A00C)

4.1.8 AIRCRAFT COMPUTER-AIDED DESIGN (CAD) MODELS: The contractor shall create CAD models of aircraft as tasked. Purposes for these models will include fleet configuration control, structural modeling, engineering analysis, modification support, or other purposes as directed. Level of detail and purpose of these models shall be coordinated with the ASIP manager of the specific weapon system and the contractor. The contractor shall update CAD models used for configuration control as modifications are added to the aircraft.

Modifications will be brought to the contractor’s attention after the modification Preliminary Design Review (PDR) and finalized at Critical Design Review (CDR). The contractor shall assist the program office is configuration control using CAD models established in the HH- 60G Configuration Tool. The configuration tool will be kept up to date to reflect the current configuration of the aircraft. An HH-60G configuration tool has been established and the contractor shall work to establish H-1 configuration tools using CAD modeling similar to the HH-60G models, these configuration models shall be used within the AFIRM database. (DI-

SESS-81000E/T)(A008)

4.1.9 ECONOMIC SERVICE LIFE: The contractor shall assist in maintaining and updating the economic service life of the aircraft by identifying components that will increase economic service life or aircraft availability, conducting analysis as necessary to substantiate predictions, and maintaining risk assessments for critical structures. (DI-MISC-80508B)(A001)

4.1.10 REVIEWS: The contractor shall assist with AFLCMC/WIU related Program Management Reviews, Aircraft Structural Integrity Team and Mechanical Equipment and Subsystem Integrity Team annual reviews, and shall assist with developing budgetary inputs for ASIP and MECSIP projects as necessary. (DI-ADMIN-81249A, DI-ADMIN-81250A, DI-

ADMIN-81373)(A005, A006, A007)

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 9

4.1.11 TECHNICAL EXPERTISE, SUPPORT AND TRAINING: The contractor shall provide subject matter expert support to AFLCMC/WIU and users in the field with respect to operations, maintenance and troubleshooting of the IVHMS/VMS/HUMS. This support will include providing guidance for improving current maintenance processes through exploitation of IVHMS/VMS/HUMS data both on-board the aircraft and on the Ground Station System. The contractor shall provide user training and support via telecommunications, as well as technical support site visits, and on-site training at units equipped with IVHMS/VMS/HUMS. The contractor shall provide technical expertise in analysis and evaluation of IVHMS/VMS/HUMS equipped aircraft. The contractor shall proactively develop IVHMS/VMS/HUMS related algorithms and analysis tools as directed by the CBM WG Lead. The contractor shall be responsible for the development of presentations and white papers in support of all algorithms and analysis tools. With support from AFLCMC/WIU and coordination with appropriate government agencies; the contractor shall complete the steps necessary to receive a US Air Force Certificate of Net worthiness for all software required to support IVHMS/VMS/HUMS data management and utilization. (DI-ADMIN-81249A, DI-ADMIN-81250A, DI-ADMIN- 81373)(A005, A006, A007)

4.1.12 SITE SURVEYS: The contractor shall supplement engineering drawing data and TO data with site surveys of actual aircraft as necessary. The purpose of these site surveys shall be to identify the locations and magnitudes of actual damage, and to clarify for modeling purposes, those drawings or other technical data that may not be fully correct.

(DI-SESS-81000E/T)(A008)

4.1.13 MISSION USAGE: The contractor shall develop a process to maintain an accurate AFLCMC/WIU rotary-wing aircraft mission usage spectrum by collecting operational usage data, evaluating the impact of operational changes to the usage spectrum and airframe, and implementing a cost effective program to comply with IAT requirements. (DI-MISC- 80508B)(A001)

4.1.14 LOADS/ENVIRONMENT SPECTRA SURVEY (L/ESS) AND INDIVIDUAL

AIRCRAFT TRACKING (IAT): The contractor shall develop a process to maintain an accurate AFLCMC/WIU rotary aircraft mission usage spectrum and IVHMS/VMS/HUMS data by collecting operational usage data, evaluating the impact of operational changes to the usage spectrum and airframe and implementing a cost effective program to comply with L/ESS, IAT and RDCT requirements per paragraphs 5.5.1 and 5.5.2 of MIL-STD-1530C. The contractor shall continue development of the L/ESS system and support the installation of the system on additional aircraft as available. L/ESS systems for rotorcraft shall incorporate similar principles as HUMS that exist on the commercial market for rotorcraft such as the IVHMS/VMS. HUMS devices can be used to satisfy all of the requirements of MIL- STD-1530 for rotorcraft data collection. The contractor shall use the AFIRM (Aging Fleet I ntegrity and Reliability Management) database for the IAT requirement. Processing of data collected as a result of L/ESS and HUMS to support overall L/ESS and HUMS programs shall be i ncorporated as outlined in MIL-STD-1530C. The contractor shall provide data and database management to include the setup and operation of the government provided servers.

The contractor shall interface with all necessary network sites as directed by the government in order to access and download aircraft data or other relevant files required for IVHMS/VMS/HUMS analysis. The contractor shall establish a database of the aircraft data that provides ready access to the Air Force CBM WG and other internal members of the analysis

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 10 team. This data and database shall be under configuration management as defined by the government. Data shall not be deleted unless specifically directed, in writing, by the government. All software utilized by the contractor shall be pre-approved by the government before installation on the server. The contractor shall maintain 100% backups of the data and provide the government with an initial draft of a Data Management Plan. (DI-MISC- 80508B)(A001)

4.1.15 HH-60G FUSELAGE STATION (FS) 308 BEAM STUDY: The contractor shall develop a repair for the FS 308/Left Buttline 34.5 WL 261 attachment in order to reduce maintenance downtime due to structural failures in this area. The contractor shall perform follow-on structural analysis of the design and testing of representative components in order to substantiate the design effort and provide technical guidance for the installation of the repair kit. The contractor shall support the installation of the right side repair as the newly released repair is fielded. (DI-MISC-80508B, DI-SESS-81704, DI-SESS-81000E/T) (A001, A003, A008)

4.1.16 ENGINEERING AND TECHNICAL DATA: The contractor shall develop engineering and technical data as needed to support this contract. The requirement for engineering and tech data will be a reflection of efforts and support of ASIP and Aging aircraft related problems as addressed during the POP. Only tech data and engineering data directly supporting this effort will be developed. (DI-MISC-80508B, DI-SESS- 81000E/T) (A001, A008)

4.1.17 TECHNICAL ORDER DISTRIBUTION OFFICE ACCOUNT: The contractor shall establish Contractor Owned and Contractor Operated (COCO) Technical Order Distribution Office (TODO) accounts to support electronic viewing and/or paper copy requirements for the (UH-1N, TH-1H, HH-60G) Technical Orders (TOs) and Flight Manuals (FMs) with a distribution statement B, C, D, E, F and X (as applicable le). For maintenance, testing, and research TO/FM efforts see attached Appendix A section 5.1 or for development TO/FM efforts see attached TO 0-0-1H-TOC-1 and TM-86-01 for a listing of applicable TOs/FMs. ETIMS access is required to establish and manage TODO accounts, prospective TODO POCs must first obtain a CAC or an External Certificate Authority (ECA) with a minimum of a favorable National Agency Check and Inquiries (NACI) to establish Air Force Portal access needed for ETIMS. The AF portal ID of the prospective primary TODO POC is entered into block 6 of the AFTO Form 43. The designated Contracting Officer Representative (COR) must confirm an approved DD Form 2345, Militarily Critical Technical Data Agreement (AFI 61-204, Disseminating Scientific and Technical Information) is on file prior to approving the AFTO Form 43. The approved AFTO Form 43 is then submitted to the

AFLCMC/EZG. (TM-86-01N) (A009)

4.2 SPECIFIC DATA REQUIREMENTS:

4.2.1 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

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 11 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. 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 L (CAGE 98752), reference attached DD Form 1423 Block 16. (DI-MISC-80508B, DI-SESS-81704, DI-SESS- 81000E/T) (A001, A003, A008)

4.2.2 ENGINEERING DATA GUIDANCE CONFERENCE: The contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. 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: (DI-ADMIN-81249A, DI-ADMIN-81250A, DI-ADMIN- 81373) (A005, A006, A007)

a. Understanding of all CDRL requirements, applicable DIDs, specifications and standards.

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

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

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

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

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

h. Digital TDP deliverables.

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

4.2.3 IN-PROCESS REVIEW (IPR) OF THE TDP: The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., 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

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 12 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.

(DI-ADMIN-81249A, DI-ADMIN-81250A, DI-ADMIN-81373)(A005, A006, A007)

4.2.4 RELATIONSHIP OF CONTRACTOR WITH SUBCONTRACTORS/VENDORS:

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

4.2.5 ENGINEERING DATA UPDATES AND REVISIONS: The contractor shall (and shall cause subcontractors and vendors to) update and maintain engineering data for the item(s) designed/ developed/modified/produced and funded by this contract for the life of this contract and shall incorporate all changes IAW the following:

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

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

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

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

4.2.5.1 TECHNICAL DATA: Contractor shall develop the Technical Order (TO) change pages necessary for the operation, maintenance, and support of the program IAW the requirements of TM-86-01N as required by the contract. The government will retain the right of approval of the formal TOs through the Certification and Verification process and the pre-pub review. (DI-MISC-80508B, DI-MGMT-80368A, TM-86-0lN) (A001, A002,A009)

4.2.5.1.1 OPERATIONAL TECHNICAL ORDERS (TOs): Contractor shall review the applicable Operational TOs and prepare properly formatted data IAW the TM-86-01N, Technical Manual Contract Requirements (TMCR). (TM-86-01N) (A009)

4.2.5.1.2 MAINTENANCE MANUALS: Contractor shall review the applicable Maintenance TOs and prepare properly formatted data lAW the TM 8601J, Technical Manual Contract Requirements (TMCR). (TM-86-01N) (A009)

4.2.5.1.3 CERTIFICATION/VERIFICATION: Government will be permitted to witness Data Certification. Contractor shall notify the government two (2) weeks prior to

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 13

Certification beginning. A Certification shall be conducted on the Trial Installation aircraft, 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. (DI-MISC-80508B, DI-SESS-81704) (A001, A003)

4.2.5.1.4 TIME COMPLIANCE TECHNICAL ORDER (TCTO): Contractor shall develop 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 Performance Specifications 38804C, and the applicable Air Force Materiel Command (AFMC) Form 873. The TCTO Verification shall be accomplished during kit proof installation. (TM-86-01N) (A009)

4.2.6 PHYSICAL CONFIGURATION AUDIT (PCA): Any modification, redesign of aircraft structure or repair design shall be subject to a PCA as determined by the government. The PCA examines the actual configuration of an item being produced. It verifies that the related design documentation matches the item as specified in the contract.

In addition to the standard practice of assuring product verification, the PCA confirms that the manufacturing processes, quality control system, measurement and test equipment, and training are adequately planned, tracked, and controlled. (DI-MISC-80508B, DI-SESS- 81704) (A001, A003)

4.3 TECHNICAL REPORTS:

4.3.1 The contractor’s analysis, updates and/or any technical solution(s) being recommended for all of the above technical objectives shall be provided to WIUEC in a report that includes all rationale behind the analysis and technical solutions(s). The date of report submittal must be submitted no later than two (2) workdays after the report requirement has been identified. Included in each report shall be a description of each of the assumed loads, the assumed initial flaws, and the technical references (reports) that brought the contractor to these conclusions. The contractor shall provide the rationale and describe the methodology used in performing the analysis. Reports must be complete and accurate;

the number of rejections shall not exceed one (1) per report. WIUEC will submit changes within five (5) calendar days for corrections. The final copy of the report must be resubmitted within five (5) workdays. (DI-MISC-80508B) (A001)

4.3.2 The contractor shall deliver a final technical report that documents the technical tasks, data acquired, and updates to existing documentation. The contractor shall also identify any deficiencies discovered in the AFLCMC/WIU rotary ACIP/MECSIP programs during investigations and recommend improvements and provide plan updates. A draft of the final technical report must be submitted no less than thirty (30) calendar days before the end of the POP. Report must be complete and accurate; the number of rejections shall not exceed one

(1) per final report submission. WIUEC will submit changes/corrections within five (5) calendar days. The final report including changes/corrections must be submitted no later than the end of the POP. (DI-MISC-80508B) (A001)

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 14

4.3.3 STATUS/FINANCIAL REPORTS: The contractor shall prepare and submit status reports detailing work performed the previous month. 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 (burn rate). The financial status shall be reported as both cumulative and for the specific reporting month. This report should compare program progress with the program schedule milestones and shall identify problems, risks, and propose effective solutions. (DI-MGMT-80368A, DI-FNCL-80331A)(A002, A004)

4.4 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. The contractor shall serve as the 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.

The contractor shall be responsible for selecting the correct components, ensuring they meet performance and integration specifications.

4.4.1 DOCUMENTATION: All data shall be delivered on electronic media in a current version of a Microsoft® Office® product format. IAW DoD policy, every effort shall be made to provide “paperless” electronic or digital deliveries. For example, MSRs and the final report shall be submitted by electronic mail in a Microsoft® Office® and/or Adobe® Acrobat compatible format.

4.4.2 MEETINGS: The contractor shall be responsible for attending/hosting meetings IAW the following paragraphs. In support of the meetings and conferences, the contractor shall furnish agendas, presentation materials and resulting meeting minutes as required.

(DI-MGMT-80368A, DI-ADMIN-81249A, DI-ADMIN-81250A, DI-ADMIN-81373)

(A002, A005, A006, A007)

4.4.3 KICKOFF MEETING: A Kickoff meeting shall be hosted at the contractor’s facility no later than thirty (30) days after contract awarded. 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. (DI-ADMIN-81249A, DI-ADMIN-81250A, DI-ADMIN- 81373)(A005, A006, A007)

4.4.4 PROGRAM REVIEW: The government and the contractor shall participate in quarterly Program Reviews and technical meetings as defined and required by the government. The location of these meetings will be determined by the government. The kickoff/requirements review will be conducted NLT thirty (30) days after contract is awarded. An engineering guidance conference will be conducted no later than sixty (60) days after contract awarded. (DI-ADMIN-81249A, DI-ADMIN-81250A, DI-ADMIN- 81373) (A005, A006, A007)

4.4.5 FINAL REPORT: The results of the contract activities shall be documented in a final report. This report shall detail the activities and evaluations accomplished during the completion of this task. The report shall include trip reports for any trips taken. The document shall contain

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 15 no more than five (5) typographical errors or technical inaccuracies. Errors shall be corrected within five (5) workdays. (DI-MISC-80508B, DI-MGMT-80368A)(A001, A002)

4.4.6 PERFORMANCE OF SERVICE DURING CRISIS: The Functional

Commander/Director has determined, by placing in writing their decision, that this requirement is not Mission Essential IAW DoD Instructions 1100.22, Policy and Procedures for Determining Workforce Mix and Defense FAR Supplement 237.76, Continuation of Essential Contractor Services.

4.4.7 INSPECTION OF SERVICES CLAUSE: The FAR 52.246-5 Inspection of Services – Cost-Reimbursement and 52.246-6 Inspection , gives the government the right to inspect contractor performance.

4.4.8 GREEN PROCUREMENT PROGRAM (GPP): GPP is a mandatory federal acquisition program that focuses on the purchase and use of environmentally preferable products and services. GPP requirements apply to all acquisitions using U.S. Government appropriated funds, including services and new requirements. FAR 23.404(b), Agency Affirmative Procurement Program, applies and states the GPP requires 100% of Environmental Protection Agency designated product purchases that are included in the Comprehensive Procurement Guidelines list that contains recovered materials, unless the item cannot be acquired: (a) competitively within a reasonable timeframe; (b) to meet appropriate performance standards, or

(c) at a reasonable price. The prime contractor shall be responsible for ensuring that all subcontractors comply with this requirement.

4.5 SECURITY REQUIREMENTS (UNCLASSIFIED):

4.5.1 GENERAL: Actual knowledge of, generation, or production of classified information is not required for performance of the contract. Cleared personnel are required to perform this service because security measures which are in force do not preclude access to classified information.

4.5.2 OPERATIONS SECURITY (OPSEC): Contractor personnel shall participate in the OPSEC program locally administered by the Air Force (AF) activity.

4.5.3 EMPLOYEE CLEARANCES: Contractor employees that need access to government owned Automated Information Systems will require the minimum of a Favorable National Agency Check. Submit a Standard Form 85P, Questionnaire for Public Trust Positions, (fingerprint cards if available) to the AFLCMC/WIU Security Office for processing.

4.5.4 PHYSICAL SECURITY: The contractor shall be responsible for safeguarding all government property provided for contractor use. At the end of each work period, contractor personnel shall ensure that all equipment and materials provided for their use shall be secured.

4.5.5 SECURITY INCIDENTS AND VIOLATIONS: The contractor shall immediately notify the AFLCMC/WIU Security Office of any actual security violation, security incident, or of any indication of a potential unauthorized disclosure or compromise of classified or sensitive but unclassified information.

4.5.6 ACCESS TO U.S. GOVERNMENT FACILITIES: The contractor shall ensure

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 16 contractor personnel who require access to a U.S. Government facility comply with the security procedures and security education requirements of the facility. If contractor personnel require repeated access to a U.S. Government facility over the life of the contract/order, the contractor shall ensure they complete, as applicable, a DD Form 1172-2 (Application for Department of Defense Common Access Card – DEERS Enrollment) to obtain a Common Access Card (CAC) or an Air Force Materiel Command (AFMC) Form 496 (Application for AFMC Identification Card) to obtain a contractor identification card. The DD Form 1172-2 or AFMC Form 496 shall be submitted as directed by AFLCMC/WIU. Upon completion/termination of the contract/order or transfer/termination of the contractor personnel, the CAC or contractor identification card shall be returned as directed by AFLCMC/WIU.

4.5.7 ACCESS TO ROBINS AIR FORCE BASE (RAFB): Requirements for Common Access Card (CAC) - The employee's Contracting Company's Security Point of Contact shall forward a CAC request to the appropriate government Contracting Officer. The government Contracting Officer will sign and submit letter to the Government Contracting Officer Representative (COR) requesting concurrence for the issuance of a CAC. The COR will forward the CAC request to the Government Trusted Agent (TA) for processing. Email notification will be provided by the TA to contract employee once information is loaded in Trusted Associate Sponsorship System (TASS). Contractor has thirty (30) days to complete application process.

User ID and Temporary Password will be provided - contractor has seven (7) days to initially log into TSS system.

F D 2 0 6 0 - 1 4 - 3 0 8 1 5 P W S R e v i s i o n : 0 Page 17

4.5.8 The CAC shall be worn or prominently displayed in such a manner as to be visible at all times while performing work on or visiting the government installation. Upon completion or termination of the contract or termination/transfer of the employee, the CAC shall be returned to the TA that processed the application.

4.6 SAFETY REQUIREMENTS: The contractor shall comply 100 percent of the time.

(DI-ENVR-81375) (A00A)

4.6.1 CONTRACTOR COMPLIANCE: The contractor shall comply with Public Law 91- 596 (Occupational Safety and Health Act (OSHA)) and the Environmental, Safety, and Occupational Health (ESOH) (DODD 4715.1E) and these requirements shall be incorporated into the contractor’s safety and health program. The Air Force participates in the OSHA Voluntary Protection Program (VPP). The contractor shall be familiar with VPP tenets.

Information on the VPP is available at http://www.osha.gov/dcsp/vpp/index.html. The contractor shall be responsible for the safety and health of all subcontractor employees. (DI-

ENVR-81375) (A00A)

4.6.2 MISHAP NOTIFICATION AND INVESTIGATION: The contractor and its subcontractors (if applicable) shall promptly report pertinent facts regarding mishaps involving Government property damage or injury to Air Force personnel and to cooperate IAW AFI 91- 204 (Safety Investigations and Reports) in any Air Force safety investigation. The contractor shall notify (via telephone) the cognizant contracting officer, the contracting officer’s representative, and/or the cognizant program manager within four (4) hours of all mishaps or incidents to DoD property entrusted by this contract operation. The Government person notified by the contractor will in-turn notify the Safety office. Contractor notifications made after duty hours shall be reported to the appropriate installation Command Post (Note: the Robins AFB Command Post Phone Number is (478) 327-2612, and they can connect with any DoD Command Post worldwide).