Atch-2_PWS_4Oct16.docx

Performance-Based Work Statement for

Support and Services (CY18) MQ-1 (Predator)/MQ-9 (Reaper)

FD2399-18-00101

04 October 2016

Distribution Statement E:Distribution authorized to DoD Components: only ROBINS AFLCMC/WIILR. Specific Authority: AFR 205–1, and the MQ-1/MQ-9 Predator Security Classification/Declassification Guide. Other requests shall be referred to ROBINS AFLCMC/WIILR. Reproduction, disclosure, or dissemination of this document in whole or part, is prohibited except with permission.

1.0 Description of Services

This is a performance-based 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 service representative support, contractor inventory control point and supply support/spares management, depot repairs, flight operations support, reliability and maintainability studies/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 specifically 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 2018 through 31 December 2018.

1.1 Objective(s): This Performance-based Work Statement (PWS) describes the services required to provide 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.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by providing end-to-end system sustainment, enhanced supply chain processes, increased system availability, enhanced Engineering/Field level support, and improved Predator/Reaper Operational/Mission rates.

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

2.0 Services Summary

The Contractor shall meet the performance work statement quality measures shown in Table 2.1 to comply with system level requirements.

Immediate -Confirm receipt ≤ 24hrs; Proposed solution ≤ 3 days; Approved solution ≤ 5 days Urgent -Proposed solution ≤ 12 days; Approved solution ≤ 15 days Routine -Approved solution ≤ 45 days

Formatting -Maintain on contract formatting standards.

Maintenance Level -“D” level procedures must be substantiated as requiring special tools, training or facilities Re-Write -Disposition re-write to Contractor due to technical issues identified.

Provide Accurate and Timely delivery of CDRLs

Resolve AFTO Form 22, AFMC 252 and AF Form 847s within established timelines as stated in the TMCR

a. TE – Technical Error (inaqccurate or incorrect data) b. FE – Formatting Error (Failure to comply with government Tech Order governing regulations and standards, MIL-STD, etc.)

c. AD – Administrative Error (spelling, punctuation, grammar, etc.) d. MI – Missing Information (Items specifically identified by AFTO, TMCR, or other formal requirements document) The following will be recorded, however, they will not be counted as quality failures;

a. RC – Requirements Change (Additional items identified after final AFTO approval but prior to fielding)

b. PR – Preference Change (items deemed necessary which improve the TO for specific customer needs)

Establish and maintain Contractor Manpower Reporting

3.0 Government Property and Services

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. The Contractor shall follow the guidance outlined in DFARS 252.245-1; DFARS 252.211-7007; DODI 5000.64; AFI 63-101/20-101 para 6.15.4.2; DoDI 4161.02, DFARS 252.245-7001/7002/7003/7004, DFARS 252.211-7003/7008 when utilizing, maintaining, storing, and supporting GFP and requirements for Financial Improvement & Audit Readiness (FIAR).

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, The Contractor shall follow the guidance outlined in DFARS 252.245-1; DFARS 252.211-7007; DODI 5000.64; AFI 63-101/20-101 para 6.15.4.2; DoDI 4161.02, DFARS 252.245-7001/7002/7003/7004, DFARS 252.211-7003/7008 when utilizing, maintaining, storing, and supporting GFP and requirements for Financial Improvement & Audit Readiness (FIAR).

3.1.1 Government Property to be Provided: Government property to be managed is Government Furnished Equipment (GFE)/Government Furnished Property (GFP) which includes Contractor Acquired Property. The contractor shall be responsible for modifying, repairing, and overhauling of equipment or components that are used during this contract.

3.1.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 Base Support: Base support will be provided by the Government to the Contractor as appropriate and when necessary. Failure by the Contractor to comply with the requirements of this paragraph shall release the Government, without prejudice, from its obligation to provide base support by the date(s) required. If warranted, and if the Contractor has complied with the requirements of this paragraph, the contractor shall be entitled to request an equitable adjustment if the Government fails to provide base support by the date(s) required.

a) Base support includes Government-controlled working space, material, equipment, services (including automatic data processing), or other support (excluding use of the Defense Switched Network (DSN)) which the Government determines can be made available at, or through, any Air Force installation where this contract shall be performed. All Government property in the possession of the Contractor, provided through base support, shall be used and managed in accordance with the Government Property clauses.

b) Unless otherwise stipulated in the contract schedule, support shall be provided on a no charge- for-use basis and the value shall be a part of the Government's contract consideration.

c) The Contractor agrees to immediately report (with a copy to the cognizant Contract Administrative Officer) inadequacies, defective Government-Furnished Property (GFP) or non-availability of support stipulated by the contract schedule, together with a recommended plan for obtaining the required support. The Government agrees to determine (within 10 workdays) the validity and extent of the involved requirement and the method by which it shall be fulfilled (e.g., purchase, rental, lease, GFP, etc.). Facilities shall not be purchased. Additionally, the Contractor (or authorized representative) shall not purchase, or otherwise furnish any base support requirement provided by the contract (or authorize others to do so), without prior written approval of the Contracting Officer regarding the price, terms, and conditions of the proposed purchase, or approval of other arrangements.

d) AFLCMC/WII will maintain Memorandums of Agreement or Support Agreements with Air Force installations, as required, providing the support at the locations listed in the FSR tables.

e) This is a cost-reimbursement contract, the Contractor agrees that in the performance of this contract or any major subcontract no direct or indirect costs for property will be incurred if the Government determines that property is available at, or through any Air Force installation where this contract shall be performed. Only the prior written approval of the Contracting Officer can relieve the Contractor from this restriction.

f) The Contractor agrees to request written authorization from the Contracting Officer for support not later than 90 days before the required in-place dates at each Air Force installation, and immediately for any required changes. The Contracting Officer shall issue timely written authorization in response to a Contractor's request. Concurrently send support authorization to the Administrative Contracting Officer or to the contract administration office if re-delegated to the Air Force installation where the support is provided.

3.3 Reporting of Government Property: The Contractor shall create and maintain records of all Government Property (GP) accountable to the contract, including 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 Government IAW CDRL A001. Property records shall enable a complete, current, and auditable record of all transactions.

(A001, DI-MGMT-80269)

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

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 in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. 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/Retention of Government Property

3.5.1 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 unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. Retention of the property by the Contractor will require modification of both losing and gaining contracts in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO.

3.5.2 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 unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Department of Defense (DD) Form 1423-1, Contract Data Requirements List (CDRL), and deliverables become the property of the Government upon receipt.

3.5.3 For cost type and time-and-material contracts, the Government obtains title to CAP acquired or fabricated by the Contractor to perform tasks under the contract in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. CAP shall be returned to the Government upon completion of the contract unless retained by the Contractor for continued use under a successor contract. If retained by the Contractor for a successor contract, CAP becomes GFP added to the successor contract by modification of both losing and gaining contracts in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.6 Government Systems

3.6.1 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.6.2 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.6.3 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 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.6.4 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 5, 00-20-1, 00-20-2, and 00-20-3.

3.6.5 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.6.6 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.0 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. These services shall be performed at the Contractors/Subcontractor’s facilities and Contractor Field Service Representatives at various Government activities (CONUS/OCONUS) listed in Exhibits C-F.

4.1 Period and Place of Performance: The period of performance for this one year contract is 1 January 2018 – 31 December 2018.

4.2 Contract Data Requirements List (CDRL): The Contractor shall deliver all data/reports associated with all CDRLs with no more than one rejection of each deliverable. There shall be no more than three (3) total rejection(s) of deliverables per quarter. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. There shall be no more than five (5) late submission(s) of data/documents per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet a CDRL delivery requirement and shall negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government. The following table (4.1) identifies the data items and CDRLs for this effort;

TABLE 4.1

STATUS OF GOVERNMENT FURNISHED EQUIPMENT REPORT (GFE)

3.3

MANAGEMENT PLAN

4.3.1

CONTRACT WORK BREAKDOWN STRUCTURE (CWBS)

4.3.1

CONTRACTOR PERFORMANCE REPORT (CPR)

4.3.1

PERFORMANCE AND COST REPORT

4.3.1

COST DATA SUMMARY REPORT (DD FORM 1921)

4.3.2.1

SUSTAINMENT FUNCTIONAL COST HOUR REPORT (DD Form 1921-5) 4.3.2.1

CONFERENCE MINUTES

4.3.3.1, 4.3.3.2, 4.3.11, 4.4.4

CONFERENCE AGENDA

4.3.3.1, 4.3.3.2, 4.4.4

REQUEST FOR VARIANCE (RFV)

4.3.8.2

ENGINEERING CHANGE PROPOSAL (ECP)

4.3.8.3

CONTRACTOR CHANGE PROPOSAL (CCPs) 4.3.8.3

DATA ACCESSION LIST (DAL)

4.3.11.1, 4.3.11.2, 4.8

ACCEPTANCE TEST PLAN

4.3.9

TECHNICAL ORDERS/TECHNICAL ORDER UPDATES

4.3.10

SOFTWARE VERSION DESCRIPTION (SVD)

4.3.11

STATUS REPORT

4.3.12

SCIENTIFIC AND TECHNICAL REPORTS

4.3.12, 4.5.1, 4.6.3, 4.6.3.2, 4.6.3.4, 4.6.3.5, 4.6.3.7, 4.6.3.8

DEFICIENCY REPORT (DR)

4.3.12.3.1

TECHNICAL REPORT-STUDY/SERVICES

4.3.13

SOURCE DATA FOR FORECASTING DIMINISHING MANUFACTURING SOURCES & MATERIAL SHORTAGES (DMSMS) 4.3.14

SYSTEM SAFETY PROGRAM PLAN

4.3.16

SYSTEM SAFETY PROGRAM PROGRESS REPORT (SSPPR)

4.3.20.1

RELIABILITY & MAINTAINABILITY CLOSE-OUT REPORTS

4.3.21.2

QUALITY ASSURANCE PROGRAM PLAN

4.3.22.1

CONTRACTOR'S PROGRESS, STATUS and MANAGEMENT REPORT 4.4.3

CONSUMABLE PARTS BONDROOM/INVENTORY AND PARTS USAGE REPORT

4.4.10

STATUS REPORT

4.4.12, 4.6.1.1

TEST PLAN

4.5.1

CONTRACTOR'S PROGRESS, STATUS and MANAGEMENT REPORT 4.6.2.2

REQUIREMENT REPORT 10 USC 2466 (50/50)

4.6.2.8

ANALYTICAL CONDITION INSPECTION REPORT

4.6.3

ENVIRONMENTAL HEALTH & SAFETY PLAN

5.7.4.1

SERDs 4.6.2.10

PHYSICAL INVENTORIES REPORT

4.4.2

SOFTWARE MAINTENANCE TECHNICAL REPORT

4.3.11, 4.3.11.1, 4.3.11.2, 4.3.12.3.1

4.3 Product Support

4.3.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 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 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 CY17 Contract Work Breakdown Structure (CWBS) for tasks accomplished under this contract IAW Data Item Description.

(A002, DI-MGMT-80004A)

(A003, DI-MGMT-81334D/T)

The Contractor shall provide responsive focal points for:

a) Contractor Supported Weapon System (CSWS)/Contractor Inventory Control Point (CICP)

b) Software Integration Lab configuration control & maintain daily operation

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

d) Technical Order (TO) sustainment

e) Reliability and Maintainability (R&M) enhancements

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 2018 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/T)

4.3.2 Contractor Management

4.3.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-81992). IAW DODI 5000.02 AND DFARS 252.234-7003, Notice of Cost and Software Reporting System:

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

a) 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).

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

c) 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;

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.

II. 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.3.3 Meetings and Reviews

4.3.3.1 The Contractor shall schedule Biannual technical interchange meetings (MQ-1 and MQ-9 independent), Biannual program management reviews, EMR’s, CLS PMR’s, and support annual product improvement working groups for MQ-1 and MQ-9. 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/telecoms 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-81250B/T)

(A009, DI-ADMN-81249A)

4.3.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-81250B/T)

(A009, DI-ADMN-81249A)

4.3.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.3.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.3.4.2 Aircraft Maintenance Production/Compression Reporting: IAW AFMC Instruction (AFMCI) 21-118, the contractor shall notify Weapon System Program Manager (WSPM), 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.

4.3.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.3.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.3.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.3.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).

4.3.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.3.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.3.6 Engine Management Responsibilities

4.3.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.3.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.3.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 Poway depot and 214th Reconnaissance Group Arizona ANG, Sheppard AETC, 178th Reconnaissance Group Ohio ANG, and 132nd Attack Wing Iowa ANG, 111th Attack Wing Pennsylvania ANG, 188th Attack Wing ANG Fort Smith Arkansas, 110th Attack Wing ANG Battle Creek Michigan, 107th Attack Wing ANG Niagara New York, 118th Operations Group Tennessee Air National Guard. Tasks inclusive of this Det 3 specified requirement from AFI 21-101 are: Air Vehicle Distribution 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.3.8 Configuration Management (CM): The contractor shall conduct configuration management in accordance with the current approved GA-ASI Configuration Management Plan (CMP) ASI-00015E. 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.3.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.3.8.2 Request for Variance (RFV):

4.3.8.3 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 the AFLCMC/WII Engineering Change Proposal Standard Process.

(A012, DI-SESS-80639D/T)

(A013, DI-ADMN-81401B)

4.3.8.4 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.3.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 AFLCMC/WIILR for approval and signature prior to 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.3.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). 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 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 AFLCMC/WIILR and AFLCMC/WII-Det 3 shall be provided within 40 days of initial receipt. Routine changes approved by the TOMA, 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.

(A016, TM-86-01N/T)

4.3.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. The contractor shall continue support to the DET3 software manager with data and metrics as required. The Contractor shall prepare and deliver a monthly Summary Project Status to the Contracting Office Representative (COR) and the Procuring Contracting Officer (PCO) no later than the date specified in the CDRL A040. This report will be submitted in letter form and is intended to concisely capture all CLS software maintenance activities during the month and to address any new risks or concerns that have arisen within the current reporting period. (A008, DI-ADMN-81250A/T) (A017, DI-IPSC-81442A) (A040, DI-MGMT-80368A/T)

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