Atch-1_PWS_18Dec14.docx

Performance-based Work Statement Solicitation Number

FA8528-16-R-00104

for

MQ-1 (Predator) / MQ-9 (Reaper) Sensor Support and Services (CY16-18)

FX2399-16-00104

December 18, 2014

APPROVED BY:

Reproduction, disclosure, or dissemination of this document in whole or part, is prohibited except with permission of WR-ALC/GRCD (AFMC). Authority: AFR 205–1 and the MQ-1/MQ-9 Predator Security Classification/Declassification Guide.

Table of Contents

1.0 – Description of Services

2.0 – Services Summary

3.0 – Government Property and Services

Furnished Property (GFP)

4.0 – Technical Requirements

5.0 - General Information

6.0 - Appendices

1.0 Description of Services

1.1 Objective(s): This Performance-based Work Statement (PWS) describes the services required to provide depot level support and services for all Electro Optical/Infrared (EO/IR) sensor systems used on the MQ-1/MQ-9 Remotely Piloted Aircraft (RPA), i.e., the most notable archetype of this sensor suite is the Multi-Spectral Targeting System (MTS) pod comprised of two major hardware components, the turret unit (TU) and electronic unit (EU), in addition to software and peculiar support components. Additional supported sensor includes the Airborne Cueing and Exploitation System Hyper spectral (ACES HY). The Contractor shall be fully responsible to plan, manage, schedule, posture and deliver all Depot level material and expertise necessary to support all operational configurations, including the systems, sub-systems, and components, at Continental United States (CONUS) and Outside Continental United States (OCONUS) operational sites. These services include but are not limited to accurate and timely delivery of CDRLs, perform turret repair within turnaround time, ensure performance of on-site FSR personnel, ensure response time to Mission Impaired Capability Awaiting Parts (MICAPs), ensure reliability improvements, program management, data management, configuration management, technical manual maintenance, software maintenance, engineering support, flight operations support, , and depot maintenance for the hardware and firmware of the system. The following assumptions are to be used for planning purposes to evaluate the size of this effort:

· EO/IR (MQ-1 and MQ-9) level of support required for anticipated flight hours flown during the contract periods of performance; January through December.

Table 1.1 MQ-1/MQ-9 Level of Support Summary Historical and Latest Flying Hour Projections per Calendar Year (CY) - as of June 2014

· Depot repair workload mix (i.e. the proportion of Original Equipment Manufacturer [OEM], versus Government organic depot source of repair) shall be based on historical EO/IR system repair activity to the maximum extent possible.

This PWS covers depot sustainment actions associated with Department of Defense (DoD) Service Operation and Maintenance (3400) as well as any Modification or Procurement (3010) funds derived by this sustainment effort. Any activity associated with or as a result of production or development efforts must utilize funding from those efforts.

All data developed in support of the requirements of this PWS shall be maintained under this contract and shall be turned over to the Government as of the final period of performance.

1.1.1 Background:

1.1.1.1 Applicability: Raytheon manufactured sensors as installed on MQ-1 (Predator) and MQ-9 (Reaper) RPA.

1.1.1.2 System Description: The MQ-1 (Predator) and MQ-9 (Reaper) are multi-role RPA utilizing sophisticated high-resolution EO/IR sensors, and high resolution cameras to determine target locations and provide near real-time aerial surveillance.

1.2 Benefit to United States Air Force (USAF): The acquisition of these EO/IRhigh resolution sensors will benefit the USAF by providing long-range surveillance and high-altitude acquisition, tracking, and laser designation necessary for battlefield reconnaissance and combat.

2.0 Services Summary

2.1 Cycle Time Metric: Repair Turn-Around-Times (TAT) shall be based on the total number of calendar days from dock receipt date to ship complete date for sensor repairs completed in the quarterly period. This calculation shall be divided by the number of completed sensor repairs over that quarterly period. Contractor shall achieve an in-plant TAT average in CY 16 - 18 of 55 days from incoming to outgoing repair dock. Assets will be evaluated to exclude items that are Deficiency Report (DR) candidates, and those that have been cannibalized or pulled by the Government for other purposes. These TAT performance metrics are not applicable to the ACES HY sensors.

2.2 Quality Measures: The Contractor shall meet the following PWS measures to comply with the system level requirements. Measurements of these requirements shall be accomplished in accordance with the Services Summary, Table 2.1.

Table 2.1 Services Summary (SS)

Appendix 1, References and pg. 47-48 of the PWS.

There shall be no more than 5% late submissions of data documents per year of performance. On time delivery per CDRL and quality of the delivered item as identified by the data item descriptions (DID) shall be measured as such:

98% - 100% Exceptional 95% - 97% Good 90% - 94% Satisfactory 85% - 89% Marginal Below 85% Unsatisfactory

3.0 Government Property and 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. The Contractor shall manage GFE/ GFP which includes Contractor Acquired Government Property. The Contractor shall be responsible for modifying, repairing, and overhauling of equipment or components identified under this contract. The Contractor shall have access to an automated logistics supply support system to maintain an auditable account for all equipment/property and is subject to a Government authorized annual inventory. Upon termination of this contract, all GFE/GFP will remain at the Contractor’s facility until disposition is provided by the Government Procurement Contracting Officer (PCO). The Government will retain ownership of all Government provided material and equipment upon contract completion.

3.2 Government Property to be provided: Government Property has been supplied by the Government for the execution of this contract. This Government Property is listed under FA8620-06-G-4041 Orders 0003, 0004, 0007, 0009, 0011, 0013 and 0019 as well as under FA9620-11-G-4050 for Orders 0001 and 0004. The Government shall retain title to all Government provided material and equipment upon contract completion.

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 Return of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract/order. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All DoD Form 1423, CDRL, deliverables become the property of the Government upon receipt.

3.5 Maintenance of GFE/GFP: The Contractor shall maintain the GFE/GFP identified under this PWS. 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 Raytheon.

In the event property is received by the Contractor, or for GFE/GFP after receipt & 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.5.1 Records of Government equipment & property: The Contractor shall create and maintain records of all GFE/GFP accountable to the contract, including Government-Furnished & Contractor-Acquired Property. The Contractor shall deliver a report of all GFE/GFP annually. Property records shall enable a complete, current, auditable record of all transactions. A030, DI-MGMT-80269

3.6 Government System(s): The Government will provide Contractor personnel access to an automated logistics supply support system necessary to perform tasks and maintain an auditable account subject to a Government authorized annual inventory for all equipment/property under the contract/order. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account(s) will be closed.

4.0 Technical Requirements

4.1 Technical Management: The Contractor shall provide technical management and coordination of program contract requirements with the Government. The Contractor is responsible for managing the engineering process and is the focal point for engineering activities on this contract. The Contractor is also responsible for coordinating technical requirements of this PWS with the Government to ensure Government participation in design and procurement decisions during the duration of this effort. The Government will ensure close coordination with the using agencies.

4.2 Period and Place of Performance:

4.2.1 Contract/Order Period of Performance: The period of performance for the contract/order includes one base year from 1 Jan 2016 through 31 Dec 2016 and two one-year option years. Option I extends from 1 Jan 2017 through 31 Dec 2017 and Option II extends from 1 Jan 2018 through 31 Dec 2018.

4.2.2 Place of Performance: The Contractor shall provide materials and support services to include planning, activating, and operating in support of the Main Operating Bases (MOBs), Forward Operating Locations/Bases (FOLs/FOBs), and applicable Air National Guard locations. Services shall be provided at all Contractor locations, CONUS, OCONUS and Fleet Readiness Center-Southeast (FRCSE) Jacksonville.

4.3 Item Unique Identification (IUID)

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

The Contractor shall comply with all DoD and DFARS Instructions, regulations and directives concerning IUID/Request For Implementation Data (RFID) as appropriate without having to tear down units to satisfy the UID requirement. The Contractor shall confirm with the Government that company IUID implementation plans meet DoD requirements.

4.3.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.3.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 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.4 Packaging

4.4.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-129R, 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; Air Force Military Command Instructions (AFMCI) 24-201, specifically Paragraph 3.7, MIL-STD-2073-1E, Standard Practice for Military Packaging; and ASTM D3951, Standard Practice for Commercial 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); MIL-STD-129R, 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 . 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. The Contractor shall perform all Packaging, Handling, Shipping, & Transportation (PHS&T) tasks in accordance with Government approved requirements.

4.4.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) and MIL-STD-2073-1E, Standard Practice for Military Packaging.

4.4.3 The Contractor shall provide inspection of all shipping containers upon receipt. In accordance with MIL-STD-2073-1E, shipping containers received, which meet the requirements of the AFMC Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed, stored and protected for reutilization. Unserviceable containers shall be repaired or disposed of and replaced with new containers that meet the requirements of the AFMC Form 158 by the Contractor.

HAZARDOUS MATERIALS (When Applicable) Hazardous materials that require Performance Oriented Packaging (POP) shall be packaged and marked for all modes of transportation (UN container markings and hazardous commodities markings) in accordance with all of the following regulations: Air Force Manual (AFMAN) 24-204_IP, Preparing Hazardous Materials for Military Air Shipments, International Civil Aviation Organization (ICAO), International Maritime Dangerous Goods Code (IMDG, Annex 1), 29 CFR, Department of Transportation Final Rule, HM-181 of the Federal Register, of 49 CFR and shall be marked In Accordance With (IAW) MIL-STD-129R, DoD Standard Practice, Military Marking for Shipment and Storage. Material Safety Data Sheets (MSDS) are required for known hazardous items and applicable items shown in Federal Standard (FED-STD)-313, Tables I and II. The symbol used to certify compliance with United Nations Performance Oriented packaging (UN POP) requirements must be one which is properly registered with the US Department of Transportation. If there are no hazardous materials in this acquisition, this requirement is null and void.

4.4.4 All military and civilian agencies shipping, or arranging for the acquisition and shipment by Government Contractors, through the use of military-controlled transport or through military transshipment facilities shall follow DoD Regulation DoD 4500.9-R, Defense Transportation Regulation Part II. This establishes uniform procedures and documents for the generation, documentation, communication, and use of transportation information, thus providing the capability for control of shipments moving in the DTS. DoD 4500.9-R, Defense Transportation Regulation Part II has been implemented on a world-wide basis.

Contracting activities are responsible for (1) ensuring that the requirements of the DoD 4500.9-R, Defense Transportation Regulation Part II regulation are included in appropriate contracts for all applicable shipments and (2) enforcing these requirements with regard to shipments under their control. This includes requirements relating to documentation, marking, advance notification of shipment dates, and terminal clearances.

Contractual documents shall designate a contract administration office (see FAR 42.202(a)) as the contact point to which the Contractor will provide necessary information to:

(1) Effect DoD 4500.9-R, Defense Transportation Regulation Part II documentation and movement control, including air or water terminal shipment clearances; and

(2) Obtain data necessary for shipment marking and freight routing. Contractual documents shall specify that the Contractor shall not ship directly to a military air or water port terminal without authorization from the designated contract administration office (see FAR 47.305-6).

4.4.5 Palletization: The Contractor shall palletize loads for shipment in accordance with MIL-STD-147E, Department of Defense Standard Practice: Palletized Unit Loads.

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

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

4.6 Government-Industry Data Exchange Program (GIDEP): The Contractor shall participate in GIDEP in accordance with Air Force Joint Instruction (AFJI) 63-108, GIDEP, and GIDEP Operations Manual S0300-BT-PRO-010, Government-Industry Data Exchange Program.

4.7 Travel: Travel requests for Contractor personnel shall be submitted for approval to the PCO prior to costs being incurred and a minimum of five business days in advance of departure. Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46, Travel Costs.

All required and expected travel under this program shall be captured separately and comply with the Joint Travel Regulation (JTR). Synchronized Pre-Deployment and Operational Tracker or a Letter of Intent (LOI) travel request process is used to authorize and manage the transport and lodging of Contractor support personnel such as CFSRs. An LOI shall be submitted prior to all travel of three (3) working days or longer.

4.8 General Requirements: The following subsections outline the general and specific contract requirements, performance indicators and associated standards. The Contractor shall not deviate from the requirements of this PWS without the specific approval of the PCO.

4.8.1 Telecons: The Contractor shall participate in all task specific telecoms. Additionally, a weekly meet-me-call number shall be established to discuss the pertinent activities associated with the contract. The telecom should be restrained to an hour at a Government agreed upon time and format. Contractor participation shall include the program manager at a minimal. Subject matter experts shall be available to discuss specific areas of responsibility. The time limit and call frequency may be adjusted per Government and Contractor agreement based on Contractor’s performance and operational tempo.

4.8.2 Meetings and Reviews:

4.8.2.1 Program Management Reviews (PMR). The Contractor shall schedule semi-annual program reviews for MTS A/B Sensors, and support a continuous and collaborative set of activities that require integration of current logistics concepts into the preliminary planning necessary to evaluate various options for maintenance concepts and supply support to ensure a balanced life cycle strategy. Approximately six (6) information exchange meetings for MQ-1/9 are expected to occur annually as part of this contract effort with additional meetings added as required by Government. Every effort will be made to align these activities with program reviews and technical interchange meetings. (A001, DI-ADMN-81249A; A002, DI-ADMN-81250A; A018, DI-ADMN-81373/T.)

4.8.2.2 ACES-HY PMR. During the performance period for ACES HY, the Contractor shall meet with the PCO, and/or other Government personnel twice semi-annually at a mutually agreed upon time and location and twice quarterly via telecom or Video Tele-Conference (VTC) as appropriate.

The Contractor shall provide a written report and briefing which contains the following: (1) the status of work performed in the previous time period; (2) problems or constraints encountered while performing this effort; (3) suggested solutions to problems or constraints; (4) proposed initiatives or waivers requiring Government action; (5) status of open items from the previous meetings; and (6) title and date of reports delivered in the previous time period. The Contractor shall notify the PCO within 72 hours. The content of the report is subject to change at the Government’s discretion. The Contractor may also request a meeting with the PCO when he or she believes such a meeting is necessary. (A001, DI-ADMN-81249A, A002, DI-ADMN-81250A, A018, DI-ADMN-81373/T).

4.9 Performance and Financial Reporting:

4.9.1 Contract 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. Contractor reports shall be prepared in accordance with the instructions contained in the most recently approved versions of A023, DI-FNCL-81765B, A024, DI-FNCL-81831, and A003, DI-MGMT-81334D.

IAW Department of Defense Instructions (DODI) 5000.02 and DFARS 252.234-7003, Notice of Cost and Software Reporting System:

1) This solicitation includes

a. The Government-approved CSDR plan for the contract, DD Form 2794, and

b. The related Resource Distribution Table.

2) 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 the maximum extent possible, upon actual cost transactions and not cost allocations;

c. Demonstrate how the data from its accounting system will be mapped into the standard reporting categories required in the CSDR 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;

i. The Contractor CSDR plan will include level 3 or 4 of the contract work breakdown structure (WBS) and any 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 Sustainment Report DD Form 1921-4, with pricing proposal.

g. The Contractor will identify any subcontractors 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 subcontractor effort in this category and provide to the Government.

3) Post Contract Award: In the performance of this contract, the Contractor shall use:

a. A documented standard 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 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.

4) Post Award Conference (Teleconference): A post award conference will be held after contract award to include a discussion of the 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. The Defense Cost and Resource Center (DCARC) is responsible for administration of this requirement. The DCARC web site is located at http://dcarc.cape.osd.mil.

4.9.2 Monthly Program Status Report (MSR): The Contractor shall submit a status report that identifies contract obligations in terms of contract funds status, requirements metrics, technical progress, as well as any applicable logistics management efforts that effect contract objective. The costs section shall be reported at the WBS level. The Contractor shall list actual expenditures for all efforts, any differences in numbers from month to month and the reason for the differences. In the event programmatic issues warrant changes to either funding or contract type, modifications to the above stated reporting requirement may be requested. A026, DI-MGMT-80227.

4.9.3 CLS Funds Memorandum: The Contractor shall provide the status of CLS funds in accordance with the memo in section 5. (A004, DI-FNCL-80912; A031, DI-MGMT-81468/T).

4.9.4 Risk Management System: The Contractor shall establish and maintain a risk management system in accordance with International Organization for Standardization (ISO) 9001:2008 certified company Quality Management System procedures. The Contractor shall outline the major risks and proposed mitigation strategies for executing the project. The Contractor shall develop risk assessment and mitigation plans.

4.10 Government Property – Specific Requirements

4.10.1 Post contract award, ASC/WII and Robins AFLCMC/WIKBA Contracting Officers (COs) will officially transfer provided property.

4.10.2 Upon completion or termination of this contract all Government Property will remain at the Contractor’s facility until written disposition is provided by the Government PCO.

4.10.3 Inspection of Services Clause: FAR 52.246-3 through 52.246-6 gives the Government the right to inspect Contractor performance so long as it doesn’t cause undue delay to delivery of those services. DCMA – Dallas: Performs surveillance of maintenance and modification (MX/Mod) activities, administers contract performance for MX/Mod activities and negotiates Over & Above actions, if acting as the ACO, otherwise the PCO/ACO will be responsible. DMCA – Dallas will only be responsible for Raytheon McKinney in-plant activities.

4.10.4 This PWS includes all Contractor activities required for support of the EO/IR sensor, which unless otherwise noted includes all hardware, software, firmware, training, documentation and support segments. The Contractor shall provide materials and support services to include planning, activating, and operating in support of the MOBs, FOLs/FOBs, and applicable Air National Guard locations. This includes the procurement of all replenishment spares and consumables. The Contractor shall repair all Government furnished sensors and all Peculiar Support Equipment components. These repairable assets shall be repaired to the production standards by which they were manufactured and/or qualified; including tagging all spares and/or replacement parts with the required serviceability documentation and complying with maintenance and inspection requirements resulting from any special inspection programs.

4.11 Program Management: The Contractor shall identify and provide a program manager (PM) to be a responsive single focal point for management and direction of internal activities and interface with the Medium Altitude Unmanned Aerial System Division (MAUAS) and the PCO throughout the PoP. The PM shall be responsible for maintaining an adequate system for tracking the progress of this contract, managing it to completion, and maintaining workable interfaces and relationships with sub-Contractors including Fleet Readiness Center – Southeast (FRC-SE). Management activities include program control, customer liaison, supplier coordination, program status and metrics definition, implementation, measurement and reporting.

The Contractor shall plan, organize, control, integrate, execute and manage the sustainment program for all fielded sensor units – which includes MTS A, B, and ACES-HY. The Contractor shall initialize, update and reconcile sensor management data in Air Force data systems as required within this PWS and Government policy. The Contractor shall provide integration with the customer and subcontractors to ensure supportability throughout the contract period of performance. The Contractor shall ensure that schedules are maintained between all subcontractors and vendors to prevent logistics support incompatibilities and schedule impacts. The Contractor shall provide a management plan that describes the Contractor's organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs. (A026, DI-MGMT-80227, A005 DI-MGMT-80004A).

4.12 Sustaining Logistics: Involves efforts associated with managing areas that impact sustainment plans. Configuration management, maintenance data collection, technical data maintenance, software maintenance, and Diminishing Manufacturing Sources (DMS) are sections that fall into the area of sustaining logistics. The Contractor shall capture all pertinent sustaining logistics data consisting of integrating activities from intra-system & inter-system integration with other DOD customers & subcontractors. At a minimum this data will include impacts from scheduled system modifications, initial provisioning deliveries under Medium Altitude UAS Division contracts, depot standup & public-private partnerships. A close interaction with the Government is required for process success.

4.13 Configuration Management (CM): The Contractor shall conduct sensor configuration management in accordance with the approved Contractor’s CM Plan. Sustainment Engineering Change Requests (ECR), Engineering Changes (EC), Specification Change Notices, and Deviation and Waiver requests shall summarize the reasons for the change. Any price/schedule impacts and Engineering Change Proposals (ECP) shall be coordinated through the PCO as required. (A006, DI-CMAN-80858B/T; A009, DI-CMAN-80640C; A015, DI-CMAN-80639C).

4.13.1 The Contractor shall maintain EO/IR sensor Software Development Plans (SDPs) and Configuration Management Plans (CMPs), which may be combined. The Contractor shall manage the maintenance and development of the EO/IR sensor system and support equipment hardware per the CMP. (A016, DI-CMAN-81248A/T)

4.14 Material and Equipment Management: The Contractor shall provide depot supply support for all sensor configurations.

4.14.1 The Contractor shall maintain and operate a dedicated storage area for Government assets. The Contractor will utilize and have access to Contractor Automated Logistics Management Support System (CALMSS) where asset quantities and other supply support information shall be input and maintained throughout the period of this sustainment effort. The Government (item managers) shall demilitarize and process items through Defense Reutilization and Marketing Office (DRMO) upon approval from the Government.

4.14.2 The Contractor shall provide support for a physical inventory of all materials under the Contractor’s control, reconcile discrepancies, and submit all inventory adjustments to the Government on an annual basis with Government oversight. (A007, DI-MISC-81191A).

4.14.3 Government Inventory Control Point (ICP) to Robins AFLCMC/WIILR: The Contractor shall, manage and maintain a facility/warehouse to stock, store, and issue MTS A/B assets in support of Government Item Management of MTS A/B assets. The Contractor shall ensure all LRU/SRU transactions are processed in C-ALMSS and provide C-ALMSS data administration. Additionally any ACES-HY assets at Contractor facility shall follow the same procedures.

4.14.3.1 At the Contractors request/option, the C-ALMSS Bonded Stock Module can be made available to track stock issued to FSRs. Contractor shall ensure CFSRs usage of SBSS for the tracking and ordering of MTS A/B and ACES-HY assets in support of Supply Chain Management (SCM) processes to support the necessary interface between wholesale (C-ALMSS) and retail (SBSS) inventory/spares tracking systems. At ICP transfer date, the Contractor shall ensure that any field replacement SRUs are processed through base supply.

4.14.4 This program includes Contractor management of Government owned inventory to support the MQ-1/9 weapon system, support equipment including common weapon system spares support for MQ-1/9 weapon system, herein after known as inventory tasks to include procurement, storage, warehouse management, and issuing and receiving of all managed inventory. The Contractor shall also provide materiel support to weapons systems at other MQ-1/9 operating locations to include modification facilities or forward-deployed sites. The Contractor shall provide piece part support for end items in modification when necessary. Additionally, the Contractor shall provide limited services for the few spares transferred to MQ-1/9 custody from other programs. The Contractor shall receive and prepare for storage of all received equipment items and spare parts. The Contractor shall manage the transfer of the components to a repair facility. These components shall not be issued until they are certified by the Government.

4.14.4.1 Replenishment Spares: The Government will purchase replenishment spares as Supply Chain Management systems dictate to ensure adequate pipeline spares are available to support war fighter requirements. Upon a Request for Proposal (RFP) from the Government, the Contractor shall provide a proposal within 90 days in support of the assets and quantities provided in the RFP.

4.14.4.2 Beyond Economical Repairs (BER): When assets are deemed to be BER (Repair cost would be 75% of total acquisition cost), the Contractor shall notify the Government (AFLCMC/WIILR) for approval of this action and instructions for DEMIL.

4.15 Mission Impaired Capability Awaiting Parts (MICAP) Requirement: The Contractor shall ensure Line Replaceable Units (LRU)/Shop Replaceable Units (SRU) are available to support MICAP requests and are promptly processed for the carriers’ next scheduled pickup to requiring activity 95% of the time. Assets shall be shipped within 24 hours from receipt of notification. The Contractor shall notify the Government not more than 48 hours of any assets not shipped within the initial 24 hours from receipt of notification. 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. If items are not available, the Contractor shall provide an explanation to include a recommended plan of action with an agreed upon estimated date.

Non-MICAP Requirement: The contractor shall ensure Line Reparable Units (LRUs)/Shop Reparable Units (SRUs) are available to support all requests. Assets shall be shipped within 5 days from receipt of notification..

4.15.1 The Government shall monitor fill rates for wholesale and retail location stock requests and, in conjunction with government-provided surge information, proactively adjust repair capacity, spares inventory, and stock levels to ensure fill rates meet contractual timeframes as described in the Quality Assurance Surveillance Plan (QASP). Contractor shall deliver a plan of need to meet any additional capacity requirements which shall be implemented within 30 days of government’s approval of plan.

4.15.2 The Contractor shall provide all materiel management services for peculiar spares to meet requirements. The Contractor shall provide adequate level of support for all sensor configurations commensurate with the total number of requirements, flight hours and system reliability.

4.16 Spares: The Contractor shall provide support and materials for fabrication and/or procurement of replenishment spare parts and inform the Government of the methodology used. The Contractor shall provide an adequate level of support for the sensors, to include all configurations, commensurate with the total number of requirements, flight hours and system reliability.

4.16.1 Design Change Notices (DCN): The DCN shall be used to introduce new field level spares items into the system and to document configuration changes for items already in the system, to include new vendors. The Contractor will submit a DCN with applicable blocks annotated to the IM not later than 21 days after the design change is identified by the Contractor/Vendor. Configuration changes are defined as additions, deletions, or modification to the approved design, or any part/component thereof, during the performance of this contract. The Contractor shall not implement any design change that increases the cost or changes the form, fit or function without attaining prior approval from the Government via the DCN. The DCN shall also identify all the items that are now obsolete, the items requiring modification along with the effort to modify them, and any new items requiring procurement that are required by the design change.

4.17 Unique Identification (UID): The Contractor shall comply with all DoD and DFARS Instructions, regulations and directives concerning IUID/RFID as appropriate without having to tear down units to satisfy the UID requirement. The Contractor shall confirm with the Government that company IUID implementation plans meet DoD requirements.

4.18 Data Management (DM):

4.18.1 The Contractor shall execute a data assession list (DAL). The DAL shall contain a current list of all classified and unclassified technical, financial and management documents/data internally generated by the Contractor in compliance with the work effort described in this PWS. Both the DAL and the listed documents, which are unclassified, shall be electronically maintained and electronic access shall be made available to the Government at all times for the duration of the contract PoP. All data listed on the DAL shall be in Contractor format and content. The Contractor shall provide the capability to search the DAL data.