Atch-1_PWS_CY17_CLS_20151023.pdf

FOR OFFICIAL USE ONLY

PR: FX2399-17-00101 PWS REVISION: 0 Page i

PERFORMANCE WORK STATEMENT (PWS)

For

Support and Services (CY17)

MQ-1 (Predator)/MQ-9 (Reaper)

23 OCT 2015

APPROVED BY:

X Jamie B. Whewell, AFLCMC/WIILR

Support & Services Program Manager

Revision Page

Reproduction, disclosure, or dissemination of this document in whole or part, is prohibit-ed except with permission from the ROBINS AFLCMC/WIILR. Authority: AFR 205–1, and the MQ-1/MQ-9 Predator Security Classification/Declassification Guide.

PR: FX2399-17-00101 PWS REVISION: 0 Page ii

Reviewer Date Page # Section # Your Change

PR: FX2399-17-00101 PWS REVISION: 0 Page iii

TABLE OF CONTENTS

1 DESCRIPTION OF SERVICES

1.1 OBJECTIVES:

1.2 BACKGROUND:

1.3 BENEFITS TO THE GOVERNMENT (USAF):

2 SERVICES SUMMARY

2.1 QUALITY MEASURES:

3 GOVERNMENT PROPERTY & SERVICES

3.1 CONTRACTOR RESPONSIBILITY

3.2 GOVERNMENT PROPERTY TO BE PROVIDED

3.3 LOSS OF GOVERNMENT PROPERTY

3.4 GOVERNMENT SYSTEM(S)

4 TECHNICAL REQUIREMENTS

4.1 PERIOD AND PLACE OF PERFORMANCE

4.2 ITEM UNIQUE IDENTIFICATION (IUID)

4.3 PACKAGING

4.4 COUNTERFEIT ELECTRONICS PARTS

4.5 GOVERNMENT-INDUSTRY DATA EXCHANGE PROGRAM (GIDEP)

4.6 TRAVEL

4.7 PRODUCT SUPPORT

4.8 MATERIAL MANAGEMENT

4.9 FLIGHT TEST OPERATIONS SUPPORT

4.10 DEPOT MAINTENANCE

4.11 ACCEPTANCE TESTING

4.12 DATA ACCESSION LIST (DAL)

5 GENERAL INFORMATION

5.1 SPECIAL CONTRACT REQUIREMENTS

5.2 CONTINUATION OF MISSION-ESSENTIAL SERVICES DURING A CRISIS

5.3 SECURITY REQUIREMENTS

5.4 ANTHRAX INFORMATION

5.5 ENVIRONMENTAL MANAGEMENT SYSTEM (EMS)

5.6 GREEN PROCUREMENT PROGRAM (GPP)

5.7 SAFETY REQUIREMENTS

5.7.5 INSPECTION OF SERVICES

5.8 TRAFFICKING IN PERSONS

5.9 CONTRACT MANPOWER REPORTING

5.10 INVOICING/PAYMENT AND RECEIPT/ACCEPTANCE

6 APPENDICES

6.1 REFERENCES

6.2 DATA REQUIREMENTS LIST:

6.3 ACRONYMS

6.4 ATTACHMENTS

PR: FX 2399-16-00102 Page 1

1 DESCRIPTION OF SERVICES

This is a performance-based (PB) work statement that defines the services needed to include program management, urgent repairs and services, logistics support, configuration management, technical manual and software maintenance, engineering technical services, contractor field ser-vice representative support, contractor inventory control point and supply support/spares man-agement, depot repairs, flight operations support, reliability and maintainability stud-ies/enhancements, maintenance data collection/entry and depot field maintenance for the MQ-1 and MQ-9 (Predator/Reaper) Remotely Piloted Aircraft (RPA) program. The requirements listed in this PWS are required to support Air Combat Command (ACC), Air National Guard (ANG), Air Force Special Operations Command (AFSOC), Air Education and Training Command

(AETC), and United States Air Force Central Command (USAFCENT) efforts unless specifical-ly stated. To evaluate the size of this effort, the following assumptions (listed in tables 5.1 and

5.2 should be used for anticipated flying hours for the Continental United States (CONUS) and outside CONUS (OCONUS) during the period of performance, 1 January 2017 through 31 De-cember 2017

1.1 Objectives: The objective of this contractual action is to accomplish Contractor Logistics

Support (CLS) for the Predator/Reaper program, including the sustainment logistics necessary to support Predator/Reaper operations while meeting the Performance Objectives listed in Table 2.1 below. The Contractor shall provide logistics resources necessary to support all elements of the

Predator/Reaper program, including those elements necessary to support the Hybrid Strategy and in accordance with established funding guidelines. In addition, the Contractor shall plan, manage, schedule, and provide support at CONUS and OCONUS operational sites, Flight Test facilities, contractor facilities, and organic government depot facilities. The Contractor shall be fully responsible for obtaining required materials and expertise to execute efforts, including support from subcontractors and organic government depots. For the purpose of this PWS, systems supported are all air vehicles (both MQ-1 and MQ-9), all types/configurations of Ground

Control Stations (GCS), all SATCOM equipment including Predator Receive Terminals (PRTs), Peculiar Ground Support Equipment (GSE), Flight Test Operations, Fixed Site Satellite

Terminals (FSSTs) and associated Radomes, SATCOM Earth Terminal Subsystems (SETSSs), L-3 Com Test Stands, Internet Protocol Systems Architecture (IP Migration), Extended Range

Hardware, and Ground Data Terminals (GDTs), Predator Mission Aircrew Training System

(PMATS) software/GCS common hardware as well as subsystems and components that are in production or have been accepted by the Air Force, and are not being used for other contractual efforts.

1.2 Background: The MQ-1 (Predator) air vehicle is a multi-role asset with the capability of near real-time target acquisition and stopping power. The MQ-1 provides real-time video and

Hellfire missile capabilities. The MQ-9 (Reaper) air vehicle is a multi-role asset with the near real-time target acquisition and weapons employment capability. Current weapons capability includes Hellfire missile, Joint Direct Attack Munitions, and other munitions capabilities. Both the MQ-1 and MQ-9 systems can be operated via either line-of-sight or satellite communication

(SATCOM). They have evolved into multi-role systems, capable of executing all aspects of the find, fix, track, target, engage, and assess kill chain. AFMC AFLCMC/WIILR has direct oversight of contractor operations and procedures, with assistance from the Medium Altitude

UAS Division Detachment 3 (Det 3), co-located at General Atomics Aeronautical Systems

PR: FX2399-17-00101 PWS REVISION: 0 Page 2

Incorporated (GA-ASI) in San Diego, CA, to ensure the Air Force receives the required support and capability required under this contract. Medium Altitude UAS Division Det 3 has a standing

Memorandum of Agreement with the local Defense Contract Management Agency (DCMA) regarding the specific roles and duties of each organization in the contract oversight role.

1.3 Benefits to the Government (USAF): This effort benefits the Government because it provides end-to-end system sustainment, enhanced supply chain processes, increased system availability, enhanced Engineering/Field level support, and improved Predator/Reaper

Operational/Mission rates.

2 SERVICES SUMMARY

2.1 Quality Measures: The Contractor shall meet the following performance work statement quality measures (Table 2.1) to comply with system level requirements. These metrics are for the total fleet minus Air Force Materiel Command(AFMC) assets.

Table 2.1 Performance Work Statement Quality Measures

Performance

Objectives PWS Para. Performance Threshold

Provide timely responses to

AF Form 107

Engineering/depot assistance requests.

Para 4.7.12.2 On time responses to request for engineering/depot assistance IAW TO-00-

25-107 for emergency, immediate, urgent, and routine AF Forms 107’s

Accurate and Timely delivery of CDRLs

This applies to

CDRL Table of

Contents, paragraph 6.2

On time delivery per CDRL and quality of the delivered item as identified by the DID.

98% - 100% Exceptional

95% - 97% Good

90% - 94% Satisfactory

85% - 89% Marginal

Below 85% Unsatisfactory

Resolve AFTO Form 22, AFMC 252 and AF Form

847s within established timelines as stated in the

TMCR

Para 4.7.10 Emergency change request recommendations shall be provided within 24 hours of receipt. Closure for emergency requests, consisting of a Rapid

Action Changes or Safety/Operational Supplement, as instructed by

AFLCMC/WII-Det 3, shall be provided within 48 hours of initial receipt.

Urgent change request recommendations shall be provided within 15 days of receipt. Closure for Urgent requests, consisting of a Rapid Action

Change or Safety/ Operational Supplement, as instructed by AFLCMC/WII-

Det 3 shall be provided within 40 days of initial receipt. Routine changes approved by AFLCMC/WII-Det 3 shall be incorporated into the next scheduled change or revision cycle. 100% on-time for urgent/emergency updates and 90% on-time for routine updates.

Repair Turnaround Time

(TAT) requirements

Para 4.10.2.2 95% TAT on average time rate: The aggregate TAT with repair completions in that quarter, shall be 45 calendar days or less for in-house repairs and 60 calendar days or less for those items returned to vendor or subcontractors for repair. TAT for items with fewer than 6 repairs completed in a quarter will be added to a pool average for tracking purposes.

MICAP Services

Para 4.8.3 Contractor shall ensure available assets to support MICAP requests are promptly processed for the carriers’ next scheduled pickup to requiring activity 95% of the time.

Material Management Para 4.8 The contractor shall provide support actions for CONUS and OCONUS requisitions IAW the priorities established in AFMAN 23-101 with a 95% on-time fill rating from on-hand assets during normal duty hours

PR: FX2399-17-00101 PWS REVISION: 0 Page 3

3 GOVERNMENT PROPERTY & SERVICES

3.1 Contractor Responsibility: 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:

http://farsite.hill.af.mil.

3.2 Government Property to be Provided: Government property to be managed is

Government Furnished Equipment (GFE)/Government Furnished Property (GFP) which includes

Contractor Acquired Government Property. The contractor shall be responsible for modifying, repairing, and overhauling of equipment or components that are used during this contract.

3.2.1 Return of Government Property: Upon completion/termination of this contract, all

GFE/GFP will remain at the contractor’s facility until disposition is provided by the Procuring

Contracting Officer (PCO). The Government will retain ownership of all government provided material and equipment upon contract completion/termination. All Government property shall be returned to the Government in the condition provided unless approved in advance by the

Procuring Contracting Officer (PCO). All Department of Defense (DD) Form 1423, Contract

Data Requirements List (CDRL), and deliverables become the property of the Government upon receipt.

3.2.2 Maintenance of GFE/GFP: The Contractor shall maintain the GFE/GFP identified under this Contract. The Government will furnish related data and information needed for the intended use of the property. The warranties of suitability of use and timely delivery of

GFE/GFP do not apply to property acquired or fabricated by the contractor as contractor-acquired property and subsequently transferred to another contract with GA-ASI. In the event property is received by the Contractor, or for GFE/GFP after receipt and installation, in a condition not suitable for its intended use, the Contracting Officer will, upon the Contractor’s timely written request, advise the Contractor on a course of action to remedy the problem. Such action may include repairing, replacing, modifying, returning, or otherwise disposing of the property at the Government’s expense.

3.2.3 Records of Government Equipment and Property: The Contractor shall create and maintain records of all Government Property (GP) accountable to the contract, including

(Weekends and Holidays are an exception from this criteria).

FSR Minimum Medical

Screening Requirement

Para 4.10.1.3.3 Contractor shall ensure FSR’s deploying OCONUS meet the minimum medical screening requirements prior to deploying. IAW DFARS clause

252.225-7040 paragraph (e), subparagraph (1), clause (ii). Contractor shall maintain medical screenings of all FSR’s deployed OCONUS 100% of the time

All MISHAP and DR failure analysis reports delivered

IAW TO 00-35D-54

Para 4.7.12.3.1 90% on-time response to DRs (JDRS) and/or MISHAPs with accurate and complete information/data http://farsite.hill.af.mil/

PR: FX2399-17-00101 PWS REVISION: 0 Page 4

Government-Furnished Property (GFP) and Contractor-Acquired Property (CAP). This accountability of GP shall be accomplished IAW the contractor’s approved Government

Property System. Information contained within the contractor’s database shall be made accessible by the Government upon request. The Contractor shall deliver a report of all GP to the customer annually. Property records shall enable a complete, current, and auditable record of all transactions. (A001, DI-MGMT-80269)

3.3 Loss of Government Property

3.3.1 Definition of 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.3.2 Reporting Loss 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.4 Government System(s): The Government will provide Contractor personnel access to automated logistics supply support systems necessary to maintain an auditable account for all equipment/property and is subject to a government authorized annual inventory. Upon completion/termination of the contract or transfer/termination of Contractor personnel, the system account(s) will be closed.

3.4.1 Contractor Access to Maintenance Data Collection Systems: The Contractor shall take necessary action to obtain access to required Maintenance Data Collections Systems through the request of Common Access Cards for access to the Air Force Portal. Access to some systems may require the Contractor to complete a DD Form 2875 and a non-disclosure statement. The form must be signed by a government sponsor. The Government will provide the Contractor access to the maintenance data management systems listed in below subparagraphs. Depot-level

Maintenance Data Documentation (MDD) shall be submitted directly to REMIS, IMDS, and

CEMS. The Government will periodically evaluate and audit organic and non-organic depot-level MDD for accuracy.

3.4.2 Reliability and Maintainability Information Systems (REMIS): REMIS is the primary Air Force data system for collecting, validating, editing, processing, integrating, standardizing, and reporting equipment maintenance data, including reliability and http://www.dcma.mil/aboutetools.cfm

PR: FX2399-17-00101 PWS REVISION: 0 Page 5 maintainability data, on a global, world-wide basis. REMIS provides authoritative information on weapon system availability, reliability and maintainability, capability, utilization, and configuration. For access procedures, send an email to: OSSG.LRXUserAdmin@wpafb.af.mil.

REMIS is designed to accumulate data and provide information necessary to support the AF equipment maintenance program outlined in AFI 21-101. The Contractor shall make inputs into

REMIS for accurate, near-real-time data accessibility to all levels of management.

3.4.3 Integrated Maintenance Data Systems (IMDS): The Integrated Maintenance Data

System (IMDS) is a single logical database that accesses historical and legacy data currently stored in other databases. The design of IMDS is flexible to support changes in logistics infrastructure size, quantity, and mission orientation, whether at home base or deployed. IMDS flexibility allows unit-level selection of system functions. All maintenance information should be accessible for collection, storage, and dissemination of critical data for repair and improvement of Air Force weapon systems and equipment. The Contractor shall ensure that the Maintenance

Data Documentation (MDD) in IMDS, regarding aircraft discrepancies, is accurate in accordance with AFI 21-101, chapter 4.

3.4.4 Joint Deficiency Reporting Systems (JDRS): JDRS provides a common, seamless solution for deficiency reporting and resolution management across the Aeronautical Enterprise.

JDRS is a cross-service web enabled automated tracking system designed to initiate, process and track deficiency reports from the war fighter through the investigation process. The Contractor shall have access to JDRS system via the following link: https://jdrs.mil/. New users may request access by visiting link at www.jdrs.mil/jdrs.html.

3.4.5 Comprehensive Engine Management System (CEMS): The primary objective of

CEMS (Propulsion Unit Centralized Accountable Record (D042), Stock Record Account

Number (SRAN) (FJ2031)) is to obtain accurate information on the status, condition, and location of aircraft engines in Air Force inventory.

4 TECHNICAL REQUIREMENTS

This section outlines the specific contract requirements. The Contractor shall not deviate from the requirements of this PWS without direct approval from the PCO. The place of performance for this contract will be a combination of Contractor/Sub-Contractor’s facilities and Contractor

Field Service Representatives (CFSR) at the various Government activities listed in Exhibits C-F

4.1 Period and Place of Performance

4.1.1 Contract Period of Performance: The period of performance for this one year contract is 1 January 2017 – 31 December 2017.

4.1.2 Place of Performance: These services shall be performed at the

Contractors/Subcontractor’s facilities and Contractor Field Service Representatives at various

Government activities (CONUS and OCONUS) listed in Exhibits C-F.

4.2 Item Unique Identification (IUID)

mailto:OSSG.LRXUserAdmin@wpafb.af.mil https://jdrs.mil/ http://www.jdrs.mil/jdrs.html

PR: FX2399-17-00101 PWS REVISION: 0 Page 6

4.2.1 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.2.2 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.2.3 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 Department of Defense (DoD) IUID Registry. The Government user or

Contractor representative 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.3 Packaging

4.3.1 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.3.2 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.3.3 Palletization: The Contractor shall palletize loads for shipment in accordance with MIL-

STD-147E, Department of Defense Standard Practice: Palletized Unit Loads.

4.4 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

PR: FX2399-17-00101 PWS REVISION: 0 Page 7 the USAF/DoD inventory in accordance with Aerospace Standard (AS)5553A, Counterfeit

Electronics Parts; Avoidance, Detection, Mitigation, and Disposition.

4.5 Government-Industry Data Exchange Program (GIDEP): The Contractor shall participate in GIDEP in accordance with Air Force Joint Instruction (AFJI) 63-108, Government-

Industry Data Exchange Program (GIDEP), and GIDEP Operations Manual S0300-BT-PRO-

010, Government-Industry Data Exchange Program.

4.6 Travel

4.6.1 All required and expected travel under this program shall comply with the Joint Forces

Travel Regulations. SPOT or Letter of Intent travel request process is used to authorize and manage the transport and lodging of contractor support personnel for OCONUS FSR travel support. Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46, Travel Costs.

4.6.2 OCONUS Travel: SPOT or Letter of Intent travel request process is used to authorize and manage the transport and lodging of contractor support personnel for OCONUS FSR travel support.

4.7 Product Support

4.7.1 Program Management:

The Contractor shall identify and provide the management, technical, and logistics support to execute, sustain, support, maintain and improve the overall life cycle sustainment for the weapon systems identified in paragraph 1.1. This will include improved processes, work products, adequate availability, and reduced logistics footprint, adequate logistics response times, and reduced total life cycle cost. The Contractor shall designate a program manager to be the focal point for management and direction of contractor activities and interface with AFMC

AFLCMC/WIILR. The Program Manager shall be responsible for tracking the progress of this contract, managing it to completion, and maintaining workable interfaces and relationships with subcontractors and associate contractors. The Contractor Program Manager shall ensure that

Cost/Schedule/Performance is maintained within the scope of this contract. Any deviations to

Cost/Schedule/Performance resulting in critical impacts to overall program shall be immediately communicated to the PCO and AFMC AFLCMC/WIILR. The Contractor shall update the

Management Plan as necessary that outlines at a minimum the aspects of the program as identified in this paragraph. The Contractor shall update the CY16 Contract Work Breakdown

Structure (CWBS) for tasks accomplished under this contract IAW Data Item Description.

(A002, DI-MGMT-80004A; A003, DI-MGMT-81334D)

The Contractor shall provide responsive focal points for:

a) Software Integration Lab configuration control & maintain daily operation

b) Tech Order Integration Lab configuration control & maintain daily operation

c) Contractor Supported Weapon System (CSWS)/Contractor Inventory Control Point

(CICP)

d) Technical Order (TO) sustainment

e) Reliability and Maintainability (R&M) enhancements

PR: FX2399-17-00101 PWS REVISION: 0 Page 8

f) Engineering support services

i. Deficiency Reporting (DR)

ii. TO 00-25-107 Requests

iii. Accident Investigation Board/Safety Investigation Board supports

iv. Emergency/Urgent action flight safety requirements

v. Configuration Management

g) Field Service Representative (FSR) deployment

h) Software sustainment

i) Depot repair

j) Contractor Mission Systems Support

k) Reliability, Maintenance Information System (REMIS)

l) Maintenance actions

The Contractor shall provide status of funds programmed to support this contract. In addition, Contractor shall provide an annual labor obligation, material obligations, and labor hours for

Remotely Piloted Aircraft (RPA) no later than 29 Nov 2017 for the previous FY. These costs shall be further defined by a percentage breakout between Contractor and Government for labor and material as public private partnerships are implemented. PM and Finance will support prior

CLS years CDRLs and reporting requirements. (A004, DI-MGMT-81466A/T, A005, DI-

FNCL-80912)

4.7.2 Contractor Management

4.7.2.1 Contractor Cost and Software Data Reporting (CSDR): The Contractor shall systematically collect and report actual contract costs to provide DoD cost analysts with needed data to estimate future costs. The Contractor reports shall be prepared in accordance with the instructions contained in the following CDRLs (A006, DI-FNCL-81565C; A007, DI-FNCL-

81831). IAW DODI 5000.02 AND DFARS 252.234-7003, Notice of Cost and Software

Reporting System:

I. This solicitation includes:

a) The Government-approved cost and software data reporting (CSDR) plan for the contract, DD Form 2794; and

b) The related Resource Distribution Table.

II. The contractor as part of the response to the solicitation will:

a) Describe the process to be used to satisfy the requirements of the DOD 5000.04-M-1, CSDR Manual, and the Government-approved CSDR plan for the proposed contract;

b) Demonstrate how contractor cost and data reporting (CCDR) will be based, to maximum extent possible, upon actual cost transactions and not cost allocations;

c) Demonstrate how contractor Demonstrate how the data from its accounting system will be mapped into the standard reporting categories required in the CCDR data item descriptions

d) Describe how recurring and nonrecurring costs will be segregated;

e) Accept or propose changes to the approved Contract CSDR plan and related Resource

Distribution Table;

PR: FX2399-17-00101 PWS REVISION: 0 Page 9

i. The Contract CSDR plan will include level 3 of the contract WBS and lower level

WBS elements designated by the Government as being high risk, high value, or high technical interest.

ii. The contractor may further extent the WBS for its own reporting or management purposes.

iii. If proposed changes are accepted, a revised Government-approved CSDR plan will be incorporated into the contract;

f) Submit the DD Form 1921, Cost Data Summary Report, and summary DD Form 1921–1, Functional Cost-Hour Report, with its pricing proposal.

g) The contractor will identify any subcontractor at any tier with a subcontract that exceeds

$50 million, by providing comments on the Resource Distribution Table, the subcontractors, or, if the subcontractors have not been selected, the subcontracted effort in this category and provide to the Government.

III. In the performance of this contract, the Contractor shall use:

a) A documented standard cost and software data reporting (CSDR) process that satisfies the guidelines contained in the DoD 5000.04–M–1, CSDR Manual;

b) Management procedures that provide for generation of timely and reliable information for the contractor cost data reports (CCDRs) and software resources data reports

(SRDRs) required by the CCDR and SRDR data items of this contract;

c) The Government-approved CSDR plan for this contract, DD Form 2794, and the related

Resource Distribution Table as the basis for reporting in accordance with the required

CSDR data item descriptions (DIDs).

d) The Contractor shall require and flow down the requirement for CSDR reporting from subcontractors at any tier with a subcontract that exceeds $50 million or any subcontracts valued between $20 million and $49 million that are designated by the Government as being high risk, high value, or high technical interest. If, for subcontracts that exceed $50 million, the Contractor changes subcontractors or makes new subcontract awards, the

Contractor shall notify the Government.

IV. Post Award Conference: A post award conference will be held after contract award to include a discussion of the contractor’s standard cost and software data reporting (CSDR) process that satisfies the guidelines contained in the DoD 5000.04-M-1, CSDR Manual, and the requirements in the Government-approved CSDR plan for the contract, DD Form 2794, and related Resource Distribution Table. This conference will be held at the contractor’s facility and can be planned for two days because of the additional contractual discussion that will take place. A telecom capability may be required for those that will only be required for certain topics.

4.7.3 Meetings and Reviews

4.7.3.1 The Contractor shall schedule Semi-annual technical interchange meetings (MQ-1 and

MQ 9 independent), quarterly program management reviews, and support annual product improvement working groups for both MQ-1 and MQ-9. One of the quarterly program management reviews will include all sustainment stakeholders to discuss the activities within this

PR: FX2399-17-00101 PWS REVISION: 0 Page 10

PWS effort and overall Predator/Reaper contract requirements. Every effort will be made to minimize routine meetings through teleconferences/video teleconferences and maximizing use of established meetings. The Contractor shall support a continuous and collaborative set of activities that require integration of current logistics concepts into the preliminary planning to evaluate various options for maintenance concepts and supply support to ensure a balanced life cycle strategy. Approximately twelve (12) information exchange meetings are expected to occur annually as part of this contract effort. Every effort will be made to align these activities with product improvement working groups, program management reviews and technical interchange meetings. The contractor shall prepare and distribute the agenda, presentation material and the meeting minutes (A008, DI-ADMN-81250A); (A009, DI-ADMN-81249A)

4.7.3.2 Aircraft Information Working Group: The contractor shall host and provide management and technical support for the MQ-9 Aircraft Information Working Group (AIWG) on a semiannual basis. The contractor shall also support a minimum of two (2) three-day aircraft

Technical Interchange Meetings (TIMs) per fiscal year. The contractor shall maintain and update the Aircraft Information Program database. The contractor shall prepare and distribute the agenda,presentation material and the meeting minutes. (A008, DI-ADMN-81250A); (A009, DI-

ADMN-81249A)

4.7.4 Sustaining Logistics: The Contractor shall manage areas that impact sustainment such as configuration management, maintenance data collection, tech order changes and revision support, software changes and revision support, material and equipment management, Support

Equipment Requirements Documents (SERDs), depot repairs and organic depot standup, and

Diminishing Manufacturing Sources and Material Shortages (DMSMS). The Contractor shall capture all pertinent sustaining logistics data consisting of integrating activities from intra-system and inter-system integration with other DOD customers and subcontractors. At a minimum this data will include impacts from scheduled system modifications, initial provisioning deliveries under Medium Altitude UAS Division contracts, Organic Depot

Maintenance, and Public-Private Partnerships (PPP).

4.7.4.1 Data Collection {Integrated Maintenance Data System (IMDS), Reliability and

Maintainability Information System (REMIS), and Comprehensive Engine Management

System (CEMS)}: The Contractor shall use maintenance data collection systems to document all maintenance actions performed by the Contractor or subcontractor on all government-owned aircraft and GCSs, to include government owned aircraft and GCSs operated by the Contractor

IAW AFI 21-101, TO 00-20-1, and TO 00-20-2. This guidance applies to all contractor locations, CONUS and OCONUS. The Contractor may use government printed AFTO 781 series forms when IMDS terminals are not available.

4.7.4.2 Aircraft Maintenance Production/Compression Reporting: IAW AFMC Instruction

(AFMCI) 21-118, the contractor shall notify Weapon System Program Manager (WSPM), AFMC AFLCMC/WII, and designated primary/alternate office of responsibility (OPR), AFMC

AFLCMC WII DET 3 within one workday of arrival of an MQ-1 or MQ-9 unmanned aerial vehicle at contractor repair facility for depot inspection, repair or modification. Notification shall be via email.

PR: FX2399-17-00101 PWS REVISION: 0 Page 11

4.7.4.2.1 Maintenance Data Collection: The Contractor shall create, update, and maintain

REMIS edit tables required for maintenance data collection of MQ-1/MQ-9 systems and associated GSE. This includes MQ-1B, MQ-9A, O0101102 Rotax 914 engine, T0102100

TPE331 engine, MD-1A/B/C/D, RQ-1W, GDTUPA96100 4 foot Ground Data Terminal (GDT) antenna, PGDTUXP96100 Portable GDT antenna, FSC-140 Fixed Site SATCOM terminal, TSC-184 SATCOM Earth Terminal Subsystem, PRTUPA96239-1 Predator Receive Terminal, GWP000X5 Predator support equipment, and Ruggedized Aircraft Maintenance Test Set.

Additional equipment designations may be added by the Government as new system requirements and configuration changes are identified. Tables to be maintained include master job standard, part number master, periodic maintenance master, repair facility assignment, time change inspection inventory, work center validation, work unit code, interim part number and

Time Compliance Technical Order (TCTO) master data table.

4.7.4.2.2 Time Compliance Technical Order (TCTO) Entry: The Contractor shall input

TCTO data into the REMIS/IMDS/CEMS systems for depot TCTO maintenance actions. An annual or rescission date reconciliation of TCTO records shall be accomplished as required by

TO 00-5-15.

4.7.4.2.3 Serial Numbering Assignment System: The Contractor shall ensure aircraft, GCSs, engines, and SATCOM part number/serial number inventory lists are accurate and loaded into

REMIS/IMDS prior to return to the field units after depot repair IAW applicable service guidance on tech data. A serial numbering assignment system that precludes duplication is required.

4.7.4.2.4 System Integration Lab (SIL) Sustainment: The Contractor shall ensure sustainment of government owned assets within the labs used for System Development, Integration, and Qualification. These labs shall support System software and Technical Order releases. The Contractor shall ensure the hardware and software configurations for the aircraft, GCSs, mock-ups, data link(s), and simulation equipment are compliant to support USAF

Software Development, Integration, and other SIL lab requirements such that the capabilities are in-place to ensure timely software updates/releases. Configuration changes to production hardware (i.e. assets delivered to the lab from production and properly entered into IMDS) shall be documented via AFLCMC/Det 3 approved modified AF Form 1067 processes. Maintenance actions shall be documented in the aircraft/GCS AFTO Form 781s for eventual documentation in

IMDS (data entry will not be considered time critical).

PR: FX2399-17-00101 PWS REVISION: 0 Page 12

4.7.4.2.5 Hardware In The Loop Lab (HILL) Sustainment: The Contractor shall ensure the hardware and software configuration for all systems within the Lab are compliant to support

USAF Tech Order development/changes/updates as well as Qualification testing on the next planned release of the System. Aircraft/ equipment will be maintained in the field approved baseline software and hardware configurations. Configuration changes outside of baseline shall use AFLCMC/WII Det 3 approved modified AF Form 1067 processes. Maintenance actions shall be documented in the aircraft/GCS AFTO Form 781s and documented in IMDS. Personnel staffing the lab shall be trained in accordance with section 4.4.5 Contractor Safe for Flight

Certification Personnel List including reporting. Furthermore, the Contractor shall keep the authorization list to a minimum consistent with requirements to assure continuity of daily operations and shall immediately notify AFLCMC/WII Det 3 of any changes.

4.7.5 Contractor Manpower Reporting: The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the MQ-1/ MQ-9 via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will be for labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported anytime during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to CMRA help desk.

4.7.6 Engine Management Responsibilities:

4.7.6.1 MQ-9A: The Contractor shall perform as Prime Engine Management Office (PEMO) and AFLCMC Engine Manager (EM) for CEMS for the MQ-9A engine. The PEMO is responsible for the accuracy, completeness, timeliness of initialization, and file maintenance of new part number data into CEMS. The Contractor shall establish, load, and monitor TCTO master records in CEMS until completed or rescinded. The Contractor shall assist field CEMS technicians in correcting erroneous transactions and shall ensure that all duplicate serial numbers are processed. The Contractor shall appoint an EM to be responsible for and maintain the depot engine EJ Stock Record Account Number IAW TO 00-25-254-1. The EM shall establish local procedures to insure accuracy and timeliness of information reporting to CEMS including quarterly TCTO and inventory reporting to CEMS Program Management Office.

4.7.6.2 MQ-1B: The Contractor shall perform as AFLCMC Engine Manager for IMDS for the

MQ-1B engine. These engines are to be maintained in REMIS and IMDS. At the end of their engine life, the engine records for scrapped assets shall be retained in REMIS.

4.7.7 Wing Scheduling, Analysis and Maintenance Operation Center (MOC) Support:

The Contractor shall perform as Medium Altitude UAS Division Det 3 Wing Scheduling, Analysis, and MOC support for use of REMIS and IMDS at AFMC Poway depot and 214th

Reconnaissance Group Arizona ANG, Sheppard AETC, 178 th

Reconnaissance Group Ohio

ANG, and 132 nd

Attack Wing Iowa ANG, 111 th

Attack Wing Pennsylvania ANG, 188 th

Attack

Wing ANG Fort Smith Arkansas, 110 th

Attack Wing ANG Battle Creek Michigan, 107 th

Attack

Wing ANG Niagara New York, 118 th

Operations Group Tennessee Air National Guard. Tasks inclusive of this Det 3 specified requirement from AFI 21-101 are: Air Vehicle Distribution http://www.ecmra.mil/

PR: FX2399-17-00101 PWS REVISION: 0 Page 13

Officer; Air Vehicle Utilization Monitor; developing standardized core scheduling practices;

managing the special inspections, time change, TCTO and configuration management programs;

establishing/maintaining job standards and profile job standards; performing Maintenance

System Data Analysis; maintaining Job Data Documentation subsystem; performing analysis and identifying trends as required by the Government; maintaining data integrity; performing special studies and developing analysis reports as required by the Government; acting as focal point for new Det 3 and for contractor IMDS/REMIS users; and maintaining current status records for equipment.

4.7.8 Configuration Management (CM): The contractor shall conduct configuration management in accordance with the current approved GA-ASI Configuration Management Plan

(CMP) ASI-00015. Major contract changes, engineering changes and deviations/waivers shall require Government approval. The contractor shall maintain the existing CM program and shall flow down the same CM requirement to their subcontractors. The contractor shall maintain and update production drawings, Production Test Plans (PTPs), and Acceptance Test Plans (ATPs).

4.7.8.1 Configuration Changes and/or Deviations: All requests for changes, and/or deviations/waivers to hardware and software/firmware shall be submitted in accordance with the

Configuration Management Plan.

4.7.8.1.1 Request for Deviation (RFD)/Request for Waiver (FW): The Contractor shall not manufacture items for acceptance by the Government that incorporate a known deviation from the approved specifications, unless an RFD or RFW has been submitted and approved in accordance with the requirements of this PWS. The deviation request shall be processed and submitted in accordance with Configuration Management Plan. (A010, DI-SESS-81732-RFW;

A011, DI-CMAN-80640C-RFD)

4.7.8.2 Engineering Change Proposal (ECP) and Contract Change Proposal (CCP): An

ECP or CCP shall include the documentation by which the change is described and recommended. The ECP shall also include a complete analysis of the technical, interface, cost, schedule and logistic impacts of the proposed change. All ECPs and CCPs shall be prepared in accordance with this PWS, the Configuration Management Plan and approved MAUAS

Engineering Change Processes. (A012, DI-CMAN-80639C/T; A013, DI-ADMN-81401B)

4.7.8.3 Data Management: The Contractor shall perform Data Management using the

Contractor’s existing Data Management System. The Contractor shall develop and submit all data in accordance with contract requirements and shall maintain revision/version control over delivered data. The Contractor shall maintain the data at their facility and at an on-line data library with controlled access for all data formally submitted under this contract. The

Government will have access to the data during the Contractor’s normal working hours.

4.7.9 Acceptance Test Plans (ATPs): The Contractor shall update new and existing

Acceptance Test Plans (ATPs) concurrent with all permanent software or hardware changes and also publish all ATPs with the USAF Mission Design Series and Block Number for affectivity tracking on the title pages. If applicable, the Contractor shall identify the part number on the title page for affectivity tracking. The Contractor shall submit all new, revised, or changed ATPs to

AFLCMC/WII-Det 3 and AFMC AFLCMC/WIILR for approval and signature prior to

PR: FX2399-17-00101 PWS REVISION: 0 Page 14 publishing and permanently changing equipment physical configuration or software on an “as required” basis. The Contractor shall submit an ATP with all changes indicated since the previous year. (A015, DI-QCIC-80553A)

4.7.10 Technical Order Sustainment: The Contractor shall maintain MQ-1B Predator, MQ-9A

Reaper and MD-1A Ground Control Station Technical Orders (TOs) as specified in the attached

Technical Manual Contract Requirements (TMCR), (A016, TM-86-01N). Emergency change request recommendations shall be provided within 24 hours of receipt. Closure for emergency requests, consisting of a Rapid Action Changes or Safety/Operational Supplement, as directed by

AFMC AFLCMC/WIILR and AFLCMC/ WII-Det 3, shall be provided within 48 hours of initial receipt. Urgent change request recommendations shall be provided within 15 days of receipt.

Closure for Urgent requests, consisting of a Rapid Action Change or Safety/ Operational

Supplement, as directed by AFMC AFLCMC/WIILR and AFLCMC/WII-Det 3 shall be provided within 40 days of initial receipt. Routine changes approved by the TOMA, AFMC

AFLCMC/WIILR and/or AFLCMC/ WII-Det 3 shall be incorporated and released not later than

365 days into the next scheduled change or revision cycle as reflected in the approved Technical

Order Status and Schedule (TOSS). Tech Orders published in digital format shall only be updated using revisions. Flight Manuals, Weapon’s delivery manuals, and the MQ-9 maintenance IETM are specifically exempt from this direction. While packaged as part of the

MQ-9 IETM, IPDF documentation including work cards and the 2-4 manual are not exempt from this direction and shall only be updated using revisions. 100% on-time for urgent/emergency updates and 90% on-time for routine updates. The Contractor shall also maintain the Depot Level Technical Data required for organic government depot repair actions.

4.7.11 Software Maintenance: The Contractor shall review, evaluate, revise, and publish software modifications/updates IAW approved Medium Altitude UAS Division software release schedule for sustainment software only. (Software development and capabilities upgrades shall be charged to the development contracts accomplishing the efforts). The Contractor shall support

Government software requirements working group meetings to prioritize software sustainment to determine the software requirements for all MQ-1 and MQ-9 systems. (A008, DI-ADMN-

81250A) (A017, DI-IPSC-81442A)

4.7.11.1 MQ-1 Software Support: The Contractor shall provide costs of software sustainment and Tech Orders for each MQ-1 sustainment software block release. Costs shall be provided from prior block release to current block release. Costs shall include direct software block release costs and associated software release costs (i.e., associated SCR initial planning and associated software management costs). Tech Order costs shall include all aircraft, Flight and

GCS costs from prior sustainment release to current sustainment release. Metrics shall be developed and delivered in accordance with established guidelines to report process, progress, testing, and costs. (A014, DI-MGMT-81453A)

4.7.11.2 MQ-9 Software Support: The contractor shall provide software support for MQ-9 software in accordance with the MQ-9 Software Process Guide. Metrics shall be developed and delivered in accordance with established guidelines to report process, progress, testing, and costs.

(A014, DI-MGMT-81453A)

PR: FX2399-17-00101 PWS REVISION: 0 Page 15

4.7.11.3 Predator Receive Terminal (PRT) Sustain/Support: The Contractor shall sustain, support, and distribute software upgrades/patches for the Predator Receive Terminal systems as required and ensure software is compatible with Ground Control Stations (GCSs).

4.7.11.4 Predator Mission Aircrew Training System Software (PMATS) Sustain/Support:

The Contractor shall sustain, support, and distribute PMATS-compatible versions of Preda-tor/Reaper Operational Flight Program software. The Contractor shall sustain all hardware that is common between the GCSs and PMATs systems.

4.7.11.5 Predator/Reaper Difference Training (Type1) The contractor shall provide the difference training on new capability and for the maintenance corrections wherever they effect

TO changes or HMI changes to the system. Difference training shall be provided for the MQ-1 on sustainment corrections as they affect TO’s or HMI.

4.7.12 Core Sustaining Engineering: The Contractor shall provide core engineering support to provide status reporting on approved engineering projects and/or core engineering support actions. Core support will include support of hardware/software elements of the MQ-1 and MQ-9 systems, and resolution of other engineering issues. Core support will include travel to each of

USAF CONUS locations to provide direct liaison support for Product Improvement Working

Groups (PIWGs), and JRMET conferences. Core engineering support will include requirement development and requirement management for all MQ-1 efforts and for applicable portions of

MQ-9 not included in Production or Development contracts. This will also include new efforts originating from USAF, Ground Control Stations (GCSs) and Ground Support Equipment for fielded systems. Upon conclusion of an Engineering Study, contractor shall deliver within 30 days an appropriate report or engineering memo containing results/findings of the study. In the event that AFMC AFLCMC/WIILR and the contractor agree that an engineering support task warrants a follow on R&M project, the contractor shall deliver an R&M SOW containing a defined project scope, requisite Basis of Estimate (BOE) and matching period of performance schedule based on After Receipt of Order (ARO) with a timeline agreed upon by both parties.

Contractor shall, in all situations, give preference to utilization of Government owned and managed assets as a first choice when evaluation units being replaced for DMS, new requirements, or other sustainment. (A018, DI-MGMT-80368A/T), (A019, DI-MISC-80711A)

4.7.12.1 Reliability Database: The contractor shall maintain a reliability and/or LMI database that will include depot returns (scheduled and unscheduled) and will assist in targeting future

Engineering Studies and R&M efforts. The LMI database shall be revised to include updates resulting from R&M driven changes, DMSMS driven changes or other changes. MQ-9 specific activity shall include reliability growth planning and execution.

4.7.12.2 Urgent Engineering Support: The Contractor shall accomplish engineering support and shall be available upon notification of an engineering related problem. Failure to resolve field reported issues through telephone and email communication between the Contractor and deployed Field Service Representative will require notification to Medium Altitude UAS

Division AFLCMC/WII-Det 3 and AFMC AFLCMC/WIILR for further guidance. The

Contractor’s…