Final_PWS_.pdf

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GEORGIA 31098-1670

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

Engineering Support Services for TH-1H Avionics Suite

FD2060-16-94408

29 July 2016

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.

LEE.JOSHUA.

H.1186083748

Digitally signed by LEE.JOSHUA.H.1186083748 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=LEE.JOSHUA.H.1186083748 Date: 2016.08.08 15:40:04 -04'00'

PR: FD2060-16-94408 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 16

SECTION 6 APPENDICES 21

PR: FD2060-16-94408 PWS REVISION: 0 3

1.0 Description of Services

1.1 Objective(s): This Performance-based Work Statement (PWS) describes the services required to acquire sustaining engineering support for the USAF TH-1H aircraft instrument, avionic, communication and navigation systems along with all associated electrical and wiring systems. Sustaining engineering support will be provided for detail components as well as the integration of these components in the TH-1H. The primary components of the flight instrument system, commonly called the Avionics Suite, include the Multi-Function Displays (MFDs), the Engine Data Concentrator Unit (EDCU), the Air Data Computers (ADCs) and the Attitude and Heading Reference System (AHRS). The primary components of the avionics, communication and navigation systems include the receivers, transceivers, control heads, transmitters, transponder, and associated antennas. Sustaining engineering will also include support for any additional subsequent modification design and integration activity accomplished on the TH-1H.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by allowing the SPO access to the design activity’s technical personnel and data to maintain the operational, safety, suitability, and effectiveness (OSS&E) of the baseline configurations. The scope of this effort includes a wide range of analysis, to include engineering research, integration and technical support services required to isolate and analyze deficiencies related to the TH-1H rotary-wing weapon system and produce any engineering data required to implement solutions, in addition to other tasks.

1.3 Background: The U.S. Air Force TH-1H helicopter is a modified U.S. Army UH-1H/V Huey single engine utility helicopter acquired and operated by the Air Force Air Education Training Command (AETC). The Air Force TH-1H Avionics Suite consists of the commercial Bell Helicopter Textron, Inc. (BHTI) UH-1H-II (Huey II) kit, with the Honeywell T53-L-703 commercial engine upgrade. Additionally, communications (COMM) and navigation (NAV) systems avionics upgrades were accomplished as well as the installation of an electronic MFD glass cockpit.

2.0 Services Summary (SS):

Performance Objective PWS Reference

Performance Threshold

Provide quality and timely response to Routine Response Technical Support requests.

4.3.1 The Contractor’s intent for problem resolution to include travel plans shall be delivered to the Contracting Officer Representative (COR) and Procuring Contract Officer (PCO) in writing, email preferred, within 10 calendar days of the receipt of a routine response technical support requests. Should the initial recommendation be rejected, the contractor shall deliver an acceptable solution within 5 calendar days. First time acceptance rate shall be 90% or greater.

PR: FD2060-16-94408 PWS REVISION: 0 4

Provide quality and timely response to Rapid Response Technical Support Requests

4.3.2 The Contractor’s intent for problem resolution to include travel plans shall be delivered by email within 24 hours of the receipt of a rapid response support request. The Contractor shall deliver a recommended solution within 72 hours of receipt of notice. Should the initial recommendation be rejected, the contractor shall deliver an acceptable solution within 24 hours. First time acceptance rate shall be 95% or greater.

Provide cost and timely response to Support Task Requests

4.3.3 The Contractor shall deliver a solution within the cost and timeframe as quoted for each Support Task Request. The number of report rejections shall not exceed one (1) per submittal.

Provide timely response to Tasks Quote Requests

4.3.4 For all support task requirements, within 10 calendar days of request receipt, the Contractor shall complete the tasking form by providing a not–to–exceed ceiling price and timeframe to complete all work required by the task except where more stringently noted in this PWS.

Provide timely response to General Engineering Phone Support Request

4.3.5 The Contractor shall respond with plans to resolve the

issue and a timeframe to deliver solution to General Engineering Support Requests from field users and System program Officer (SPO) technical personnel within 48 hours of receipt of request.

Provide quality Engineering Data

4.5 – 4.5.3 The Contractor shall develop / produce / maintain and deliver a Technical Data Package (TDP) that accurately depicts the final product as required for all support requests. The TDP shall represent the approved, tested, and accepted configuration of the delivered item(s). The TDP shall be delivered in accordance with Air Force Product Data Specification drawing 9579776 Revision M (CAGE 98752). The TDP shall have no more than five

(5) errors or technical inaccuracies. Errors shall be corrected within five (5) business days after notice of rework required unless an extension is approved by the

SPO.

Provide quality and timely delivery of Monthly Status Reports (MSR)

4.12.2 The Contractor shall provide status reports to the

Government no later than the 15th day of each month.

The report shall contain no more than five (5) typographical errors or technical inaccuracies. Errors shall be corrected within five (5) business days after notice of rework required.

Establish and maintain Contractor Manpower Reporting

5.6 Within 30 calendar days of contract/order award, the

Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location Data and make the annual report no later than October 31 of the following fiscal year.

PR: FD2060-16-94408 PWS REVISION: 0 5

3.0 Government Property and Services

3.1 Government Property: The Contractor shall be responsible for Government property in their possession in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements including, but not limited to, FAR Part 45, Government Property; FAR 52.245-1, Government Property; and Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, Government Property. The FAR and applicable supplements can be accessed at the site below.

http://farsite.hill.af.mil

3.2 Government Property to be Provided: Government property to be provided includes Air Force Technical Orders (AFTOs). See Appendix 2 for a list of AFTOs.

3.3 Loss of Government Property: In accordance with DFARS 252.245-7002, Reporting 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, theft, loss due to lack of security, 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 Reporting of Government Property: The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

http://www.dcma.mil/aboutetools.cfm

3.5 Return of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract/order. All Government property shall be returned to the Government in the condition provided unless approved in advance by the Procuring Contracting Officer (PCO). All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRL), and deliverables become the property of the Government upon receipt.

3.6 Government System(s): The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account(s) will be closed.

PR: FD2060-16-94408 PWS REVISION: 0 6

The contractor shall establish Contractor Owned and Contractor Operated (COCO) Technical Order Distribution Office (TODO) account to support electronic viewing and/or paper copy requirements for the TH-1H Technical Orders (TOs) and/or Flight Manuals (FMs) with a distribution statement B, C, D, E, and F. For maintenance, testing, and research TO/FM efforts see attached Appendix 2, Technical Order and Flight Manual, for a listing of applicable TOs/FMs.

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 extends 36 months; 1- 12 month basic and 2-12 month options.

4.1.2 Place of Performance: Services shall be performed at the Contractor’s facility. Travel may be required to the aircraft located at Cairns Army Airfield, AL and/or the depot facility (Bell Ozark, AL).

4.2 Contract Data Requirements List (CDRL):

DATA

ITEM

AUTHORITY TITLE/SUBTITLE PWS Reference

A001 DI-MISC-80508B Technical Report-Study/Services 4.3.1, 4.3.2, 4.3.3, 4.3.5, 4.3.6, 4.4, 4.5.3, 4.6, 4.7, 4.12.4

A002 DI-MGMT-80368A Status Report 4.3.5, 4.3.6, 4.4, 4.5.3, 4.12.2

A003 DI-FNCL-80331A Funds and Man-Hours Expenditure Report

4.12.2

A004 DI-ADMN-81249B Conference Agenda 4.5.1, 4.5.2. 4.12.3, 4.13, 4.13.1, 4.13.2, 4.13.3

A005 DI-ADMN-81250B Conference Minutes 4.5.1, 4.5.2. 4.12.3, 4.13, 4.13.1, 4.13.2, 4.13.3

A006 DI-ADMN-81373 Presentation Material 4.5.1, 4.5.2. 4.12.3, 4.13, 4.13.1, 4.13.2, 4.13.3

A007 DI-SESS-81000E/T Product Drawings/Models And Associated Lists

4.3.5, 4.5, 4.5.3, 4.6, 4.7, 4.12.2

A008 DI-MISC-81832 Counterfeit Prevention Plan 4.17 A009 DI-MISC-81807 Software/Firmware Change Request 4.4

4.3 Engineering Services Details: The Contractor shall provide engineering resources required to support routine response technical support requests, rapid response technical support request, task quote requests, engineering phone support requests, and task quote requests via Attachment 1: Engineering Task Order Request Form or other forms and communications. The Contractor may be tasked to evaluate new requirements and designs by altering materials and/or combining components into a new assembly or system as a prototype/proof of concept. If requested by the

PR: FD2060-16-94408 PWS REVISION: 0 7

Program Manager (PM) and/or Contracting Officer Representative (COR), an Integrated Master Schedule (IMS) shall be submitted for tasks requests.

4.3.1 Routine Response Technical Support: This sustainment support primarily comes in the form of responding to service revealed deficiencies. Several forums are used by fielded units to identify problems or deficiencies to the System program office (SPO). Some of these are preliminary product quality deficiency reports (PQDRs), Product Improvement Working Group (PIWG) action items, AFTO 22, AFTO 135, AFTO 847, Critical Item lists, and Corrosion Prevention Advisory Board (CPAB) action items. The contractor shall work with the government to analyze and develop corrective actions for these design-related supportability and maintenance deficiencies. The contractor shall also conduct assessments on other components not identified in these forums but as seen as an aversion in order to avert future problems (obsolete parts, aging aircraft studies, etc.), technology insertion or operating and support cost reduction initiatives (i.e., HUMS). For all forums the contractor shall determine design and/or technical manual changes required for their improvement as well as initiate implementation of appropriate design changes under this sustaining effort. The Contractor’s intent for problem resolution to include travel plans shall be delivered to the COR and PCO in writing, email preferred, within 10 calendar days of the receipt of a routine response technical support requests. Should the initial recommended resolution be rejected, the contractor shall deliver an acceptable solution within 5 calendar days. First time acceptance rate shall be 90% or greater The Contractor shall deliver solution within the cost and timeframe as quoted in the associated task quote. The Contractor shall not exceed the quoted prices for any task, except at their risk. The COR will provide approval and direction to proceed for all task requests. A technical report shall be provided upon completion of all the tasks. The number of report rejections shall not exceed one (1) per submittal. (A001, DI-MISC-80508B) Technical Report - Study/Services

4.3.2 Rapid Response Technical Support: In addition to routine technical support to the operators of fielded USAF TH-1H rotary-wing aircraft, a rapid response may be directed for a “no notice” deficiency, grounded aircraft and mishap support or issues arising during Programmed Depot Maintenance (PDM) causing a work stoppage. The Contractor’s intent for problem resolution to include travel plans shall be delivered by email within 24 hours of the receipt of a rapid response support request. Work stoppage, grounded aircraft, safety or mishap issue are some examples where rapid response support will be requested. The Contractor shall deliver a recommended solution within 72 hours of receipt of notice. Should the initial recommended solution be rejected, the contractor shall deliver an acceptable solution within 24 hours. First time acceptance rate shall be 95% or greater. This rapid response support includes recommendations for updating and maintaining the accuracy of operational data in the flight and technical manuals. The depots and/or the fielded units use several forums for rapid response, identical to those used for routine response, to identify problems These include Depot Work Specification Document changes, TO changes, PQDRs, PIWG action items, AFTO 22’s, AFTO 135’s, AFTO 847’s, Critical Item Lists, Field Request for Engineering Support (TO 00-25-107), safety or hazard reports, accident or incident reports, or any other deficiency and engineering support report submitted. A technical report shall be provided upon completion of all the tasks.

The number of report rejections shall not exceed one (1) per submittal. (A001, DI-MISC- 80508B) Technical Report - Study/Services

PR: FD2060-16-94408 PWS REVISION: 0 8

4.3.3 Support Task Requests: When tasked by the Government, the Contractor shall perform analyses which include but is not limited to engineering research, 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 Contractor shall deliver solution within the cost and timeframe as quoted in the associated task quote. The Contractor shall not exceed the quoted prices for any task, except at their risk. The COR will provide approval and direction to proceed for all task requests. A technical report shall be provided upon completion of all the tasks. The number of report rejections shall not exceed one

(1) per submittal. (A001, DI-MISC-80508B) Technical Report - Study/Services

4.3.4 Task Quote Requests: When tasked by the Government, the Contractor shall complete the tasking form utilizing a form similar to that shown in Attachment 1 (Engineering Task Order) of this PWS. For all support task requirements, within 10 calendar days of request receipt, the Contractor shall complete the tasking form by providing a not–to–exceed ceiling price and timeframe to complete all work required by the task except where more stringently noted in this PWS. The Contractor shall submit its estimate of cost to be incurred under the task. The Contractor shall not exceed the ceiling price, except at their risk. The Contractor shall then submit said form to the PM for collection. The PCO will provide approval and direction to proceed. See paragraph 4.2.2 for task response time relating to rapid response technical support.

4.3.5 General Engineering Phone Support: General Engineering Phone Support shall consist phone support to users and SPO technical personnel for all issues relating to the design and integration of the TH-1H instrument, avionic, communication and navigation systems as well as all subsequent modifications performed by L-3 Comm/TCS.. The Contractor shall accept and provide a response to technical inquiries from the Government via telephone, teleconference, email, fax or any other form of correspondence. The Contractor shall serve as POC for resolving engineering issues and correcting existing engineering data, as requested. The Contractor shall work with the government to analyze and develop corrective actions for design-related supportability and maintenance deficiencies. The Contractor shall respond with plans to resolve the issue and a timeframe to deliver solution to General Engineering Support Requests from field users and SPO technical personnel within 48 hours of receipt of request. The Contractor shall track all technical inquiries to determine problematic trend areas and document the summary status of each inquiry in MSRs. The Contractor shall assist technical personnel with maintaining configuration management for the USAF TH-1H aircraft 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. A technical report shall be provided upon completion of all the tasks. The number of report rejections shall not exceed one (1) per submittal.

(A001, DI-MISC-80508B) Technical Report - Study/Services (A002, DI-MGMT-80368A) Status Report (A007, DI-SESS-81000E/T) Product Drawings/Models and Associated Lists

PR: FD2060-16-94408 PWS REVISION: 0 9

4.3.6 Resolution of Safety Issues: As tasked by the government, the contractor shall validate and investigate safety actions identified in by the AFLCMC/WIU/WIUED material safety task group (MSTG) and the System Safety Group (SSG). The contractor shall determine design and/or technical manual changes required for correction of these action items. Initiate implementation of appropriate design changes under this sustaining effort. A technical report shall be provided upon completion of all the tasks. The number of report rejections shall not exceed one (1) per submittal.

(A001, DI-MISC-80508B) Technical Report - Study/Services (A002, DI-MGMT-80368A) Status Report

4.4 Software Maintenance: The Contractor shall provide software maintenance including, but not limited to, providing thorough reviews; identification or evaluation of new software requirements; engineering design and analysis; implementation and test of software changes;

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 software deficiencies revealed in the operations and maintenance of the USAF TH-1H aircraft. The Contractor may be tasked to evaluate new requirements and designs by altering materials and/or combining components into a new assembly or system as a prototype/proof of concept. The Contractor shall maintain a Configuration Management process using best practices considering guidance provided in Military Handbook (MIL-HDBK)-61A Configuration Management Guidance, Electronic Industries Alliance’s (EIA)-649 National Consensus Standard for Configuration Management, and International Standards Organization (ISO) 12207 Standard for Information Technology - Software Life Cycle Processes, to include subsets.

All proposed software changes and results shall be documented in a final report.

Results from software changes, to include test results, shall be documented via DI-MISC-80508.

(A001, DI-MISC-80508B) Technical Report - Study/Services (A002, DI-MGMT-80368A) Status Report (A009, DI-MISC-81807) Software/Firmware Change Request

4.5 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

PR: FD2060-16-94408 PWS REVISION: 0 10

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. The TDP shall have no more than five (5) errors or technical inaccuracies.

Errors shall be corrected within five (5) business days after notice of rework required unless an extension is approved by the SPO.

(A007, DI-SESS-81000E/T) Product Drawings/Models And Associated Lists

4.5.1 Engineering Data Guidance Conference: The contractor shall support and co-chair a Guidance Conference with AFLCMC/LZPEM for engineering data within 60 days after contract award. The Conference shall be convened at a site and on a date agreed upon by the Government contracting officer and the contractor. The contractor shall prepare an agenda and record the minutes of the Guidance Conference. The contractor shall address, discuss, and provide status on the following:

(A005, DI-ADMN-81250B) Conference Minutes (A004, DI-ADMN-81249B) Conference Agenda (A006, DI-ADMN-81373) Presentation Material

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

b. TDP review requirements and schedules.

c. TDP delivery requirements and schedules.

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

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

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

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

h. Digital Technical Data Package (TDP) deliverables.

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

4.5.2 In-Process Review (IPR) of the TDP The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that

PR: FD2060-16-94408 PWS REVISION: 0 11

Government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 50% percent completion point and shall be held, when possible, in conjunction with other reviews (i.e., PDR, CDR). The contractor shall notify AFLCMC/LZPEM a minimum of 30 days prior to the anticipated date of completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, i.e., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the Government may schedule a separate IPR at the subcontractor's/vendor's facility.

(A004, DI-ADMN-81249A) Conference Agenda (A006, DI-ADMN-81373) Presentation Material (A005, DI-ADMN-81250B) Conference Minutes

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

Shall incorporate all changes IAW:

a. All engineering changes shall be incorporated into the applicable engineering data within 90 calendar days after engineering release/AF concurrence or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.

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

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

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

e. When deficiency resolution requires creating or updating drawings and specifications the Contractor shall update and submit reproducible copy to the requesting activity, based on information furnished or previously available and provide as an attachment to the monthly status report.

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

PR: FD2060-16-94408 PWS REVISION: 0 12

specifications for which the data was originally prepared. Data shall be CDRL requirement unless otherwise specified by the Government.

g. The Contractor shall provide support in updating existing Spares TDPs, reviewing drawings, updating qualification requirements and qualified vendor status to allow competitive parts procurement as required.

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

(A001, DI-MISC-80508B) Technical Report - Study/Services (A002, DI-MGMT-80368A) Status Report (A007, DI-SESS-81000E/T) Product Drawings/Models and Associated Lists

4.6 Physical Configuration Audit (PCA): Any modification, redesign of aircraft structure or repair design will be subject to a PCA as determined by the government. The PCA examines the actual configuration of an item being produced. It verifies the related design documentation matches the item as specified in the contract. In addition to 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.

(A001, DI-MISC-80508B) Technical Report - Study/Services (A007, DI-SESS-81000E/T) Product Drawings/Models and Associated Lists

4.7 Production Engineering Support: The Contractor shall review document changes and deficiency reports submitted by the depot facility. Reports include Joint Depot Level Maintenance (JDLM) document changes, TO changes, PQDRs, safety or hazard reports, accident or incident reports, aircraft fuel contamination reports or any other deficiency report submitted.

(A001, DI-MISC-80508B) Technical Report - Study/Services (A007, DI-SESS-81000E/T) Product Drawings/Models and Associated Lists

4.8 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 Reliability Centered Maintenance (RCM) and Age Exploration (AE) program. This review shall provide the government with a recommendation to accept or disapprove, with deficiencies identified and rationale thoroughly explained.

4.9 Task Management Description: The Contractor shall provide a single project manager with authority and responsibility for this task.

4.10 Personnel: The Contractor shall provide the Technical Services to perform this task. At a minimum, the Contractor shall have engineering expertise that includes a thorough understanding of Mechanical, Electrical, Aerospace and R&M engineering of rotary-wing aircraft.

PR: FD2060-16-94408 PWS REVISION: 0 13

4.11 Performance of Tasks: The Contractor shall perform services provided herein, and use reasonable efforts to accomplish the services within the total estimated price set forth herein.

The Government will have no obligation to make payment to Contractor in excess of the total estimated price, and the Contractor shall have no obligation to continue to perform work beyond the total estimated price, even if the service is not completed. The parties may, by mutual written agreement/modification, change the total estimated price. The Contractor may take the following actions in its discretion, so long as the Contractor does not exceed the total estimated price: Use fewer hours of one labor category and more hours of another labor category or categories.

4.12 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 (POC) 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 and ensuring they meet performance and integration specifications.

4.12.1 Documentation: All data shall be delivered electronically in a current version of a Microsoft Office product. Every effort shall be made to provide “paperless” electronic or digital deliveries.

4.12.2 Monthly Status Reports: The Contractor shall provide status reports to the Government no later than the 15th day of each month. The report shall contain no more than five (5) typographical errors or technical inaccuracies. Errors shall be corrected with in five (5) business days after notice of rework required. The reports shall cover engineering and technical support provided by the Contractor during the previous monthly period. The Contractor shall document task status, schedule, data deliverables, contract issues and actions, problems and expenditure data, as well as anticipated future task requirements during the next reporting period. At a minimum, a milestone chart, actual/projected spending rate and estimated man-hours should be included to provide tracking from each fund source. 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 Monthly Status Reports (MSR). Regular updating of cumulative cost versus estimated 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.

(A002, DI-MGMT-80368A) Status Report (A003, DI-FNCL-80331A) Funds and Man-Hours Expenditure Report

PR: FD2060-16-94408 PWS REVISION: 0 14

(A007, DI-SESS-81000E/T) Product Drawings/Models and Associated Lists

4.12.3 Quarterly Data Reviews: For task requests requiring data deliverables, the Contractor shall participate in quarterly data reviews. These dates will be approved by the acceptance of the Integrated Master Schedule (IMS). 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 and the resulting minutes.

(A004, DI-ADMN-81249A) Conference Agenda (A005, DI-ADMN-81250B) Conference Minutes (A006, DI-ADMN-81373) Presentation Material

4.12.4 Final Report: The Contractor shall create and submit a final report to the government for review and approval. The report shall contain no more than five (5) typographical errors or technical inaccuracies. Errors shall be corrected with in five (5) business days after notice of rework required. 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 basic and all option periods.

(A001, DI-MISC-80508B) Technical Report - Study/Services

4.13 Meetings: The Contractor shall be responsible for attending/hosting meetings in accordance with (IAW) the following paragraphs. In support of the meetings and conferences, the Contractor shall furnish agendas, presentation materials and resulting meeting minutes, as required.

(A004, DI-ADMN-81249A) Conference Agenda (A005, DI-ADMN-81250A) Conference Minutes (A006, DI-ADMN-81373) Presentation Material

4.13.1 Kick-Off Meeting: The contract activities shall begin with a face-to-face “kick off” meeting within three weeks after receipt of order (ARO). The meeting shall be convened at a site and on a date agreed upon by the Government contracting officer and the Contractor. The Contractor shall furnish the proposed agenda and presentation material for the meeting, and the resulting minutes.

(A004, DI-ADMN-81249A) Conference Agenda (A005, DI-ADMN-81250A) Conference Minutes (A006, DI-ADMN-81373) Presentation Material

4.13.2 Conferences: The Contractor shall attend the annual Helicopter Week. 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 week and other meetings and conferences, the Contractor shall furnish the agenda, presentation material and resulting meeting minutes as required.

(A004, DI-ADMN-81249A) Conference Agenda (A005, DI-ADMN-81250A) Conference Minutes

PR: FD2060-16-94408 PWS REVISION: 0 15

(A006, DI-ADMN-81373) Presentation Material

4.13.3 Program Review: The Government and the Contractor shall participate in Program Reviews and technical meetings. The kickoff/requirements review will be conducted no later than (NLT) three weeks ARO. Program reviews will be conducted quarterly and an engineering guidance conference will be conducted 60 calendar days ARO.

(A004, DI-ADMN-81249A) Conference Agenda (A005, DI-ADMN-81250A) Conference Minutes (A006, DI-ADMN-81373) Presentation Material

4.14 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 with the assigned tasks. The Contractor shall be responsible for arranging all Contractor personnel travel during the program effort. The Contractor shall use the lowest cost mode of transportation commensurate with mission requirements and good traffic management principles.

Travel will be reimbursed according to the rates outlined in the Federal Travel Regulations for travel within the CONUS; Joint Travel Regulations (JTR) for travel to Alaska, Hawaii and outlying areas of the United States; and the rates established by the Department of State for travel outside of the 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-46, Travel Costs. 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 the PCO and concurrence by 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/WIU, WIUB or WIUKB, Robins AFB GA has not been received. All travel shall be IAW DoD JTR. Trip Reports shall be submitted to AFLCMC/WIUBC NLT five business days upon return from the trip.

4.15 Item Unique Identification (IUID): In accordance with DFARS 252-211.7003(a), Item Identification and Valuation / Definitions, “DoD unique item identification’ means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items.” Unique item identification is required for all items that meet the criteria established by DFARS 211.274-2, Policy for unique item identification.

4.15.1 The Contractor shall mark items in accordance with DFARS 211.274-2, DFARS 252- 211.7003, and Military Standard (MIL-STD)-130N, Department of Defense Standard Practice / Identification Marking of U.S. Military Property.

4.15.2 In accordance with the Department of Defense Guide to Uniquely Identifying Items Assuring Valuation, Accountability and Control of Government Property, the Government user will add item(s) to the DoD IUID Registry. The Government user or Contractor representative

PR: FD2060-16-94408 PWS REVISION: 0 16

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

4.16 Packaging: The Contractor shall package and mark end items and components in accordance with the contract (basic or order, as applicable) Air Force Materiel Command (AFMC) Form 158, Packaging Requirements; MIL-STD-129P, Department of Defense Standard Practice / Military Marking for Shipment and Storage; MIL-STD-130N, Department of Defense Standard Practice / Identification Marking of U.S. Military Property; and MIL-STD-2073-1D, Standard Practice for Military Packaging. The Contractor shall ensure that classified material is packaged, marked and shipped in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM). The Contractor shall package and mark material in accordance with other applicable Government regulations including, but not limited to, those regarding security, safety and environmental concerns.

4.16.1 The Contractor shall package and mark material for movement, shipment, receipt and storage in a manner that ensures the protection and preservation of the material for shipment to and storage at the destination. The Contractor shall package electronic parts susceptible to static discharge damage in accordance with MIL-STD-1686C, Military Standard: Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment (Excluding Electrically Initiated Explosive Devices).

4.16.2 In accordance with MIL-STD-2073-1D, shipping containers received, which meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed and stored for reutilization. Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.

4.17 Counterfeit Electronics Parts: The Contractor shall establish policy and procedures to mitigate the risk of counterfeit electronics parts being installed in end items or otherwise entering the USAF/DoD inventory in accordance with Aerospace Standard (AS)5553A, Counterfeit Electronics Parts; Avoidance, Detection, Mitigation, and Disposition.

(A008, DI-MISC-81832) Counterfeit Prevention Plan

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis

5.1.1 Designation of Services as Mission-Essential: In accordance with DFARS 237.7602(a), The Continuation of Essential Contractor Services / Policy, DFARS 252.237-7023(a)(2), and Air Force Instruction (AFI) 10-403, Deployment Planning and Execution, paragraph 1.9.1.33.2, the Functional Commander (FC) or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis

PR: FD2060-16-94408 PWS REVISION: 0 17

5.2 Security Requirements

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

However, Contractor personnel are required to comply with security requirements to preclude potential security incidents or violations.

5.2.2 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and security requirements are met. The Contractor shall comply with security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security Program; 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.3 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall ensure compliance with DoDD 5205.02E and DoD Manual 5205.02-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 CUI in accordance with DoD 5220.22-M, National Industry Security Program. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

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

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

5.2.7 Access to Government Facility or Military Installation: The Contractor shall ensure Contractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation. The Contractor shall ensure Contractor personnel who require access to a USAF installation comply with the FAR and

PR: FD2060-16-94408 PWS REVISION: 0 18

applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.2.8 Common Access Card (CAC): The Contractor shall ensure a CAC is obtained / maintained and managed by all contractor/subcontractor personnel who require a CAC for access to DoD computer networks and systems, for DoD installation entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

5.2.9 Common Access Card (CAC) for Air Force Base (RAFB): The employee's Contracting Company's Security Point of Contact shall forward a CAC request to the appropriate Government Contracting Officer (CO). The Government CO will sign and submit request 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 and the contractor has seven (7) days to initially log into TASS system.

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

5.2.11 Access to Robins AFB: If access to Robins AFB will be required to perform services/tasks supporting this contract effort(s), refer to Robins AFB Integrated Defense Plan (IDP) 31-101, Paragraph 3.18.

Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished, contractor identification badges while visiting or performing work on the installation. If a vehicle pass is required, contact the Robins AFB Pass and Registration office for instructions and issuance of the pass.

5.3 Affirmative Procurement Programs (APP)

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

PR: FD2060-16-94408 PWS REVISION: 0 19

In accordance with FAR 23.404(a)(iii), the Contractor shall provide estimates and verification of recovered material for EPA-designated CPG products and certification for…