RPA PWS

FA4890-10-R-0009

PERFORMANCE WORK STATEMENT

FOR

REMOTELY PILOTED AIRCRAFT (RPA) MAINTENANCE SUPPORT

CONUS and OCONUS Locations

Revised – Amendment 0001

Revised – Amendment 0002

Revised – Amendment 0004

TABLE OF CONTENTS

SECTION A

DESCRIPTION OF SERVICES

1.0 SCOPE OF WORK

1.1 Scope

2.0 PROGRAM MANAGEMENT

2.1 General Requirements

2.2 Uniforms

2.3 Drug Testing

2.4 Hours of Operation

2.5 Personnel Qualifications and Training

2.6 Listing of Employees

2.7 Contract Management

2.8 Financial Management

2.9 Records Maintenance and Reporting

2.10 Aircraft Reporting

2.11 RPA System Reporting

2.12 Mission Essential Contractor Services

2.13 Incident Notification

2.14 Deployment Reporting

2.15 Meetings

2.16 Metrics

2.17 Information Management

2.18 Quality Management System (QMS)

2.19 Performance Evaluation

2.20 Visitor Support

2.21 Host Nation Requirements

2.22 Deployments

2.23 Reports

3.0 OPERATIONS AND MAINTENANCE

3.1 Operations & Maintenance Support

3.2 Equipment Maintenance

3.3 Aircraft

3.4 Aircraft Impoundment

3.5 Aircraft Positioning

3.6 Additional Maintenance Requirements

3.7 Certifications

3.8 Depot and Contract Field Team (CFT)

3.9 Response Time

3.10 Ground Control Station (GCS)

3.11 TFT, FSST, and SETSS

3.12 Reachback Facilities

3.13 Circuit Support

3.14 Information Assurance Certification

3.15 Maintenance Documentation

3.16 Plans, Scheduling, and Documentation

3.17 Maintenance Management Analysis

3.18 Combat Air Patrol (CAP)

3.19 Divert Aircraft

3.20 CAP and Sortie Requirements

3.21 Logistics Management

3.22 Property Control/Administration

3.23 Item Unique Item Identification

3.24 Transportation

3.25 AVGAS POL/Fuel

3.26 Aerospace Ground Equipment (AGE)

3.27 Aircraft Armament Systems

3.28 Munitions

4.0 MISSION SUPPORT

4.1 Facility Management

4.2 Communications Security (COMSEC)

4.3 Environmental, Safety, and Health Program

4.4 Security

SECTION B

SERVICES SUMMARY

1.0 SERVICES SUMMARY

1.0 Service Summary Narrative

1.1 Purpose

1.2 Components

1.3 Quality Assurance Surveillance Plan (QASP)

1.4 Right to Surveil

1.5 Services Summary Tables

2.0 Measurement, Analysis, and Improvement (MA&I)

2.1 Quality Assurance

SECTION C

GOVERNMENT FURNISHED PROPERTY AND SERVICES

1.0 GENERAL INFORMATION

2.0 GOVERNMENT FURNISHED PROPERTY

2.1 Facilities

2.2 PMEL

2.3 T.O.s, Publications, Forms, and Equipment Manuals

2.4 Vehicles

2.5 Petroleum, Oil, and Lubricant (POL)

2.6 Tools and Equipment

3.0 PROGRAMS

3.1 Wing-Level Maintenance Functions

3.2 Weapons Certifications

3.3 Environmental

3.4 Security

3.5 Morale, Welfare, and Recreation (MWR)

4.0 OPERATIONS

4.1 OCONUS Deployment Preparation Assistance

4.2 Deployment Medical and Health Services

4.3 Mobility and Deployment Support

4.4 Back Shop Support

4.5 Host Base Maintenance Operations Squadron Functions

4.6 Crash Recovery

5.0 CIVIL ENGINEERING

5.1 Utilities

5.2 Refuse Collection

5.3 Pest, Insect, and Rodent Control

5.4 Real Property Maintenance

5.5 Roads & Grounds: Ramp/Runway Sweeper Services

5.6 Bioenvironmental Engineering

6.0 COMMUNICATIONS

6.1 Installation Distribution

6.2 Telephone Services

6.3 Electronic Mail Service /Local Area Network Connectivity

6.4 Land Mobile Radios (LMR)

6.5 Automated Data Processing

7.0 MEDICAL

8.0 TRAINING

9.0 MEALS AND LODGING

10.0 APO/FPO

11.0 CAC/ID CARD

12.0 COMMISSARY

13.0 EXCESS BAGGAGE

14.0 MILITARY BANKING

15.0 MILITARY ISSUED EQUIPMENT

16.0 MILITARY AIRLIFT

SECTION D

GENERAL INFORMATION

1.0 Transition Aircraft

2.0 Backorder Parts

3.0 Government Furnished Property

4.0 GFE Reporting/Documentation

5.0 Existing Conditions

6.0 Training

7.0 Transition/Phase In Plan

8.0 Phase-Out Plan

APPENDICES

Appendix A Definitions, Abbreviations, and Acronyms

Appendix B Contract Data Requirements List

Appendix C AFI 21-101, 21-201, 21-200 Compliance Matrix

Appendix D Publications, Forms, and Websites

Appendix E Government Furnished Property

Appendix F Quality Management System

Appendix G Incentive Fee Plan

Appendix H RPA Service Summary

Appendix I Special Requirements for Deployment Support

Appendix J Contractor Identified Key Personnel-Qualifications

Appendix K C4ISR Demarcation Points

Appendix L PWS Addendum/Proposal Incorporation

Appendix M Certifications, Training, and Qualifications

Appendix N Operational Requirements

Appendix O PWS Matrix

SECTION A

DESCRIPTION OF SERVICES

1.0 Scope of Work

1.1 Scope: The primary objective of this contract is to provide a high level of organizational-level (O-level) maintenance support for MQ-1and MQ-9 Remotely Piloted Aircraft (RPA) and systems to sustain the combat and training capability at tasked locations worldwide, wherever required. The contractor shall provide operations support as required by this Performance Work

Statement (PWS). The contract objective shall be fulfilled by providing qualified management and supervisory personnel at the contractor’s and customer’s facilities, qualified organizational maintenance personnel at Continental United States (CONUS) and Outside Continental United

States (OCONUS) locations, and a level of support for these personnel that shall allow them to accomplish the primary objective. Support shall include aircraft maintenance management, Aerospace Ground Equipment (AGE) and Ground Support Equipment (GSE) maintenance, supply support, Command, Control, Communications, Computer, Intelligence, Surveillance, and

Reconnaissance (C4ISR) Systems O&M support, Quality Control, and ancillary support programs.

1.1.1 Comply with the responsibilities and aircraft maintenance management philosophy and policy outlined in this PWS.

1.1.2 Throughout this PWS, certain paragraphs stipulate tasks and functions which shall be accomplished in accordance with (IAW) Air Force Instruction (AFI) 21-101 and as supplemented by Air Combat Command (ACC).

1.1.3 The contractor is encouraged and expected to generate innovative approaches to efficiently and effectively accomplish contract tasks, functions, and requirements in a quality manner, at appropriate costs, and in a way which fosters pride and ownership in work performed.

1.1.4 Accomplish planned sortie production and all maintenance actions as necessary to support the flying schedule and Air Tasking Orders (ATO). All maintenance shall be performed IAW applicable technical orders (T.O.s), publications, and local directives listed in Appendices C and D.

1.2 Performance Work Statement Pricing Methodology. Unless otherwise stated in this

PWS, all work and purchases are part of the Firm Fixed Price portion of the contract.

2.0 Program Management

2.1 General Requirements: Provide program management oversight for all work performed under this contract.

2.1.1 Program Management Office (PMO): Provide, staff, and equip an off-base

PMO.

2.1.2 On-Site Management: Provide an on-site management and oversight function at all locations that serve as a single interface between the government and contractor.

During normal duty hours, the individual shall be available to meet with the government within one hour of notification, and aggressively pursue timely responsiveness to government requests. Exercise management and operational control for this contract and be responsible for contract performance IAW this PWS.

2.2 Uniforms: Contractors working on site at all government locations shall wear a standard uniform shirt identifying them with this program, unless otherwise directed by the government program office to meet local security requirements.

2.3 Drug Testing: Employees shall be subject to substance abuse testing at the direction of the government following any Class A, B, or C mishap, or at any other time the government deems necessary. Drug testing shall normally be conducted at military testing facilities, however, the

Contracting Officer (CO) may direct testing be conducted at a commercial testing facility.

Commercial testing facilities shall meet the requirements of Department of Defense Instruction

(DoDI) 1010.16, Paragraph E1.11.

2.4 Hours of Operation: Operating hours established by the contractor shall be consistent with meeting the flying schedule or ATO as tasked by the MAJCOM sponsoring each location.

Schedule duty hours around the flying schedule, including working mid-shifts, night shifts, and weekends. Weekend maintenance shall be required to support weekly flying schedule and to support scheduled surges, deployments, and exercises. Flying and maintenance schedule deviations shall be governed and recorded by the requirements in ACCI 21-165. The contractor shall have a plan to shelter aircraft / equipment in emergency situations such as extreme weather during normal duty and non-duty hours in government provided facilities.

2.5 Personnel Qualifications and Training: Select and employ qualified personnel in sufficient numbers to manage, supervise, and perform all tasks required by this PWS. Contractor personnel shall be properly trained, qualified, and certified when applicable. See Appendix I for specific deployment requirements.

2.6 Listing of Employees: Submit a report identifying all personnel working on-site at government facilities IAW Paragraph 2.23.1. The list shall be validated and signed by the contractor’s Facility Security Officer (FSO).

2.7 Contract Management: The contractor is responsible for all program administration required to fulfill contract requirements. Provide all data, information, reports, and proposals including Contract Data Requirements List (CDRL) deliverables or contract requirements, to the government in electronic format compatible with Microsoft Office software, unless otherwise directed by the Government. Develop and maintain a non-proprietary set of procedures, policies, and supplements that provide guidance and establish procedures for this contract.

2.8 Financial Management: Provide backup information to include a detailed breakdown of costs that provides a clear/verifiable accounting trail for each cost reimbursable CLIN. Travel expenses shall be broken down by traveler’s name and cost areas such as airline tickets, taxi, mileage, per diem, visas, and passports, incurred by each individual. The contractor shall provide the supporting documentation to the government program office five business days before submitting the invoice into Wide Area Work Flow (WAWF) for review and validation.

After concurrence from the government, the contractor may submit the invoice into WAWF.

The CLIN total needs to match and be traceable directly back to the WAWF invoice. The contractor shall provide a Cost Performance Report IAW Paragraph 2.23.2.

2.9 Records Maintenance and Reporting: Maintain records, reports, publication files, and control maintenance administrative procedures. All contractor-generated records, documents, databases, other electronic media, and associated papers shall become government property and will remain in place upon contract termination or completion. Records, documents, databases, other electronic media, and associated papers shall be available for government review at all times.

2.9.1 Maintain records resulting from processes in this document IAW AFMAN 33-363, Management of Records, and dispose of them IAW AFI 33-364, Records Disposition –

Procedures and Responsibilities and AF Records Disposition Schedule located at https://www.my.af.mil/gcss-af61a/afrims/afrims/rims.cfm. Contact supporting records managers as required. If requested by the Government, the Contractor shall provide the original record or a reproducible copy within 5 duty days of receipt of the request.

2.10 Aircraft Reporting: Monitor and report all aircraft gain/loss actions IAW AFI 16-402 with the Wing Aerospace Vehicle Distribution Office (AVDO).

2.11 RPA System Reporting: Report RPA system status IAW Paragraph 2.23.3.

2.12 Mission Essential Contractor Services: All contractor services are considered mission essential IAW DFARs 252.237-7023 and 252.237-7024. Provide a Contingency Plan for all sites

IAW Appendix I and Paragraph 2.23.4.

2.13 Incident Notification: Report mishap and security incidents, damage to government property, and other significant incidents IAW local procedures and IAW CDRL A0006.

2.14 Deployment Reporting: At deployed locations, report reportable incidents as defined by and IAW DoDD 2311.01E.

2.15 Meetings:

2.15.1 Program Management Meetings: Attend up to 4 program management meetings in Contract Year 1, and up to 2 meetings in each subsequent Contract Year at the government program office, or as directed by the government. Attend Award Fee

Review Boards (AFRB) as desired IAW Appendix G. Limit attendance to 3 people at all meetings and AFRBs without prior coordination with Government Program Office.

https://www.my.af.mil/gcss-af61a/afrims/afrims/rims.cfm

2.15.2 Customer Meetings: Attend meetings and briefings as required by the government. Provide information and be prepared to discuss contractor activities and their impact upon operations/logistics at any requested meeting/briefing. Provide information in support of meetings and briefings in the format requested by the government.

2.15.3 Type and Frequency: The following meetings and briefings are the minimum requirements the contractor is expected to attend, be prepared for, and participate in during the course of this contract at each installation.

Type Frequency

Maintenance or Operations Group Stand-Up Daily

Wing Stand-Up Daily

Maintenance Group Production Meeting Daily

Unit Scheduling Meeting Weekly

Maintenance Group Scheduling Meeting Weekly

Operations Group Scheduling Meeting Weekly

Health of Fleet Meeting Monthly

Intermediate Repair Enhancement Program Monthly

Time Compliance Technical Order Meetings (TCTO) As Required

Wing Weapons Manager Monthly

Munitions Scheduling Meeting Weekly

Data Integrity Team Weekly

Maintenance Standardization and Evaluation Program Monthly

2.16 Metrics: Develop, maintain, and analyze metrics for assigned RPA requirements, and continually explore opportunities for process improvements. Provide government access to the metrics and steps taken to exploit opportunities.

2.17 Information Management:

2.17.1 Master Reference Library: Establish and maintain a master library containing copies of, or electronic access to, all contractor-prepared or acquired T.O.s, publications, manuals, and other information. Establish and implement a method of controlling master library items. Establish and maintain a current list of all items in the master library. AF publications are located at (http://www.e-publishing.af.mil).

2.17.2 Records Custodian: Designate a primary and alternate records custodian representative at each site. Integrate documents into the USAF file plan program.

2.17.3 Technical Publications Function: Establish and maintain a Technical Order

Distribution Account (TODA) function under the host base Technical Order Distribution

Office (TODO). Maintain technical publications sufficient to support deployments.

http://www.e-publishing.af.mil/

2.18 Quality Management System (QMS): Utilize knowledge/experience gained through current ISO 9001, AS9100, AS9110, or AS9120 registration to develop, document, implement, maintain, and continuously improve a comprehensive higher-level Quality Management System that assures compliance with the most current version of American National Standards Institute

(ANSI)/International Organization for Standards (ISO)/American Society for Quality (ASQ)

9001 (currently 9001:2008) and all requirements of this PWS and Appendix F.

2.19 Performance Evaluation: Contractor performance outputs are subject to surveillance by a government Contracting Officer’s Representative (COR) to ensure compliance with this

PWS. At a minimum, the contractor shall:

2.19.1 Access: Allow CORs access to work areas and data, provide support, and not interfere with the CORs, state, federal, and other designated personnel in the performance of their official duties. Permit the CO or authorized representative access to all records, data, and facilities used in the performance of the contracted services. Provide access as soon as possible, but not to exceed one workday of the request. Notify the Government

Program Office immediately when outside agencies request access.

2.19.2 Non-conformances: Take immediate remedial and corrective actions for all non-conformances identified during government surveillance.

2.19.3 Corrective Action Request (CAR): Upon receipt of a CAR, complete applicable sections of the CAR (or automated equivalent) and return it to the CO within time constraints issued by the CO. At a minimum, provide corrective and preventive action plans that address why the performance threshold was not met, how performance will be returned to acceptable levels, and how recurrence of the cause will be prevented in the future.

2.19.4 Performance Evaluation Meetings, Conferences, and Workshops: Meet with the

CO, COR, and other Government personnel, on a periodic basis or as deemed necessary. The contractor may request a meeting with the CO when they believe such a meeting is necessary. The government may require meeting with the contractor to discuss compliance, performance improvement, quality strategic planning, teamwork, and training opportunities. The purpose of these meetings is to foster proactive continuous improvement by analyzing past performance problems as well as exceptional performance levels. These meetings shall review the contractor’s QMS efforts and the government’s Quality Assurance function focusing on improved performance through teamwork. Explore and implement DoD and industry best practices and quality tools/methods.

2.20 Visitor Support: Support visits by dignitaries, inspection teams, depot teams and other groups as directed by the Government.

2.21 Reachback Site Host Nation Requirements: Meet all host nation personnel, labor, and travel requirements at Reachback Facilities. Coordinate Technical Expert Status Accreditation

(TESA) applications or similar country-specific requirements with ACC AMIC/PSC prior to hiring employees. TESA procedures and information can be found at the DoD Contractor

Personnel Office (DOCPER) website referenced in Appendix D. The host country has sole approval authority for all TESA applications.

2.22 Deployments: Support deployed locations to meet mission requirements based on Combat

Air Patrols (CAP) requirements, number of aircraft assigned, assigned equipment, and site unique requirements. Operations at deployed locations shall provide 24 hours/7 day coverage.

Submit personnel Letters of Authorization (e.g., contractor TDY order equivalent) through the

Synchronized Personnel Operational Tracking (SPOT) system to ACC AMIC for processing not earlier than 14 days prior to scheduled travel dates. All personnel shall complete chemical warfare training prior to deployment, if applicable. All contractor personnel shall be on site to perform task order requirements NLT 45 days after the Government Contracting Officer issues a deployment task order. Deployments shall be based on minimum average 120 day rotations.

See Appendix I for deployment specific requirements and Appendix D for references to the requirements listed below.

a. Comply with all host and enroute country entry, exit, and work permit requirements.

These requirements are cost reimbursable exclusive of fee.

b. Comply with Unified Combatant Command (CENTCOM, AFRICOM, PACOM, etc.)

contractor deployment requirements.

c. Comply with Joint Theater Support Contracting Command guidance found on

CENTCOM’s website (http://www2.centcom.mil/sites/contracts/Pages/Default.aspx).

d. Comply with all local business registration requirements.

e. Use the lowest total cost air travel route between CONUS locations and the applicable

Joint Reception Center (JRC), or deployed location for personnel not required to process through a JRC. Travel to support deployments is cost reimbursable exclusive of fee.

2.22.1 Comply with Turkish Government requirements for deployed contractor personnel.

Contact the Turkish Embassy or Consulate to determine specific requirements. Turkish travel and work requirements are subject to change without notice and the U.S. Government is not responsible for any changes or decisions made by the Turkish Government. Keep

Government Program Office apprised of status of paperwork for personnel deploying to

Turkey.

2.22.1.1 Work visas, work permits, and residency permits are normally required for contractor personnel deployed to Turkey. These requirements are cost reimbursable exclusive of fee.

2.22.1.2 The contractor may attempt to utilize Technical Representative status for emergency or short-notice situations after coordination with the Government Program

Office. Final approval for personnel entering and working in Turkey remains with the

Turkish Government.

2.22.2 Provide a list of contractor personnel who travel via military or government-provided contractor airlift IAW Para. 2.23.8. Do not pay invoices received from Air Mobility

Command for contractor travel on military or government-provided contractor airlift directly.

http://www2.centcom.mil/sites/contracts/Pages/Default.aspx

Forward any invoices received from the Government directly to the Government Program

Office for payment.

2.23 Reports: All reports, unless otherwise directed, shall be in an electronic editable format compatible with Microsoft Office and delivered via NIPRNET electronic mail system. All reports in this paragraph are part of the firm fixed-price portion of the contract.

2.23.1 Personnel Report: Personnel Manning Report

Reference: PWS Paragraph 2.6

Receiving Office ACC AMIC/PMAU

Proprietary information - further dissemination only as directed by ACC AMIC/PMAU or higher DoD authority.

Distribution authorized to U.S. Government agencies and their contractors. Other requests for this document shall be referred to ACC AMIC/PMAU.

Submit first report the first Wednesday after start of contract full performance, then update and resubmit weekly each Wednesday. Provide to local security manager as required. Information shall be current as of the date of submittal.

Note: Include full name, job title, last four of social security number, permanently assigned location, deployed location, and deployment start and end dates. Report shall be organized by location.

2.23.2 Cost Performance Report (CPR): Financial

Reference: PWS Paragraph 2.8

Receiving Office ACC AMIC/PMAU

Proprietary information - further dissemination only as directed by ACC AMIC/PMAU or higher DoD authority.

All data shall reflect the same time period as the invoice submitted to WAWF. Submittal shall be no later than the 25th calendar day of each month.

Note: Document financial information to reflect current and previous fiscal year (FY) contract cost data, projected funding requirements, and specific expenditures.

Report shall contain the following:

- Contract identification data

- Funding authorized to date

- Cumulative billings

- Actual cumulative costs to date

- Actual costs incurred since last reporting period

- Estimated costs through end of contract year

- Detailed listing of all costs for cost reimbursable CLINS by category to include supplies, equipment purchases, and travel

- Contract Line Item Number (CLIN), description, cost

2.23.3 Status Report: RPA Status Report

Reference: PWS Paragraph 2.11, 3.10

Receiving Office: ACC AMIC/PMA, AMIC/PSC, ACC/A8Q; other organizations as directed by ACC/PMAU, and as required to fulfill requirements at forward deployed locations.

Submit report up to 2 times per day broken down by site and include:

- Aircraft/GCS tail number

- Aircraft configuration to include air handler serial number

- Status

- Breaks

- Daily sortie data to include number of CAPs, number of total sorties, number of commander-directed sorties, and flying hours

- MQ-1: Time to next 720- and 1080-hour inspections, and propeller change

- MQ-9: Time to next 2000- and 4000hour engine inspections, and propeller change

- Spare engine availability by site

- Any MICAP parts on order, estimated delivery date, and document number

- TCTO information to include tail number and status

Distribution authorized to U.S. Government agencies and their contractors. Other requests for this document shall be referred to ACC AMIC/PMAU.

Submit first report at start of contract full performance and updated daily thereafter.

Unless otherwise stated in this paragraph, CONUS sites shall submit the report via

NIPRNET. Deployed sites, reachback sites, and Whiteman AFB shall submit the report via SIPRNET.

2.23.4 Management Plan: Contingency Plan

Reference: PWS Paragraph 2.12

Receiving Office: ACC AMIC/PMA

Proprietary information, further dissemination only as directed by ACC AMIC/PMAU or higher DoD authority.

Provide a contingency plan that provides reasonable assurance of maintaining operations at all site locations in the event of contingency or crisis conditions. Specifically address maintaining operations in the event of a labor strike. Include contractor's strategy to retain, and rotate site personnel as required to meet mission requirements in these conditions. Submit plan within 7 days of contract full performance start date, with revisions submitted as required.

The document will be accepted/rejected by the government within 30 working days after receipt. Contractor shall revise and resubmit the document within 5 working days after receipt unless otherwise directed by the CO.

2.23.5 Command Status Report: C4ISR Daily Maintenance Report

Reference: PWS Paragraph 3.11-3.13

Receiving Office: ACC AMIC/PMA & PSC; 432 ACMS

Report equipment system/circuit outages, maintenance and status. As a minimum, provide the following information for all outages, scheduled and unscheduled maintenance: System/Equipment/Circuit ID/nomenclature, outage/maintenance narrative, Discrepancy, Estimated Time of Return to Operation (ETRO), maintenance start/stop date and times, corrective actions, status changes, date/time of outage/status change, Item(s) ordered (include part number), IMDS Job Control Number (JCN), Supply

Document number and Supply status. List all visitors to the site.

Submit first report the day contract full performance begins and then submitted each day thereafter NLT (No Later Than) 1900Z. Report shall be sent via SIPRNET.

2.23.6 Command Weekly Report: C4ISR Weekly Summary Report

Reference: PWS Paragraph 3.10-3.13

Receiving Office: ACC AMIC/PMA, DRQ, & PSC; 432 ACMS

FOUO - further dissemination only as directed by ACC AMIC/PMAU or higher DoD authority.

Report shall contain the following:

Significant Events/O&M/Visits for the week

Projected Significant Events/O&M/Visits up to 30 days out

Priority Facility/System Projects Status and Timelines

C4ISR (include GCS) Weekly Or (%) and Monthly Or (%), calculated IAW Appendix H

C4ISR (include GCS) Weekly and Monthly Or (%) by equipment identification number

Active, non-mission capable unscheduled and approved hours

C4ISR previous month’s Or by the fifth day of new reporting month by system

Submit report every Monday, NLT 1900Z.

Send report via NIPRNET.

2.23.7 Technical Report - Study/Services: System Circuit Information Guide

Reference: PWS Paragraph 3.11-3.13

Receiving Office: ACC AMIC/PMA & PSC; 432 ACMS

Establish, maintain and update system circuit information guide for each Communication facility. Update and submit guide NLT 20 calendar days after any change. Guide shall include: system diagrams, circuit routing maps, circuit troubleshooting information, circuit restoral information and priority, circuit loss contingency plan, contact information, encryption settings, and associated C4I systems configurations to include circuit type specific profiles, timing configuration and sources. Include all Satellite terminal BaseBand information: All circuit configurations clearly indicating which values are in use (includes circuit type specific profiles and timing configuration and sources). Identify satellite link controllers, local and distant end user and points of contact for each individual distribution authorized to U.S. Government agencies and their contractors. Other requests for this document shall be referred to ACC AMIC/PMAU.

Submit first report 90 days after contract full performance start date and then submit as mission needs dictate, after any change to document or as directed by the Contracting

Officer.

2.23.8 Contractor Travel on Military Aircraft Report

Reference: PWS Paragraph 2.22.2

Receiving Office ACC AMIC/PMAU

Submit first report 30 days after contract full performance start date and monthly thereafter.

Include traveler’s name, dates of travel, flight number, origin, and destination.

2.23.9 Weekly Aircraft Statistics

Reference: PWS Para. 3.17

Submit first report the first Monday NLT 1200 EST/EDT after contract full performance start date and weekly thereafter.

Include Mission Capable Rate, Total Non-Mission Capable Rate for Maintenance, Total

Non-Mission Capable Rate for Supply, and high drivers for contractor- and military-supported aircraft in a format provided by the Government Program Office.

2.23.10 Monthly RPA Statistics Report

Submit first report NLT the 20 th calendar day of each month beginning the month after contract full performance start date.

Include site-by-site statistics for number of flying hours, total sorties, and all service summary metrics. Include a summary of all commander-directed sorties by site and date.

Report shall also include a summary of the entire contractor effort on a calendar month basis and a running total for the current fiscal year.

2.23.11 Monthly Logistics Indicators Report, RCS: ACC-LGP (M) 9302

Receiving Office: As directed by ACC AMIC/PMAU

Submit as directed by ACC AMIC/PMAU.

Format IAW ACCI 21-118 or other MAJCOM equivalent directives.

2.23.12 Monthly Vehicle Report

Reference: PWS Para. 3.24

Receiving Office: ACC AMIC/PLGT

Submit NLT the 10 calendar day of each month.

Include vehicle registration number, date and duration of maintenance, reason for maintenance, cost of maintenance. Include a complete inventory broken down by site of all government furnished vehicles to include registration number and type vehicle.

Contractor format is acceptable.

3.0 Operations and Maintenance (O&M)

3.1 O&M Support: Perform only organizational-level maintenance. Perform all maintenance, repairs, or modifications IAW applicable publications listed in Appendices C and D, and authorized depot-level directives. Provide organizational-level maintenance support for government-directed test plans, including verification and validation of procedures as required.

Perform validation and verification for organizational-level TCTOs as required. Contractor personnel performing O&M activities within classified areas shall comply with all government security directives and requirements.

3.1.1 Deployment Support: Provide planning support for new deployed sites and existing deployed sites to be redeployed. Provide deployment, bed down, tear down, and redeployment support for aircraft, equipment, and contractor personnel.

3.2 Equipment Maintenance: Provide personnel, expertise, and services necessary to troubleshoot, maintain and repair all aircraft, C4ISR, and support equipment. Accomplish maintenance IAW applicable publications listed in Appendices C and D.

3.3 Aircraft: Perform organizational-level maintenance tasks, including but not limited to, servicing, pre-, thru-, and post-flight inspections, launch and recovery activities, weapons loading and unloading, munitions build-up, scheduled periodic inspections, post-maintenance checks and verification, troubleshooting, scheduled and unscheduled maintenance, and configuration control to the level described in the applicable T.O.s. Implement approved organizational-level modifications or upgrades to aircraft systems.

3.3.1 Crash Recovery: Support crash recovery operations as directed by on-scene commander. Perform crash recovery duties on-base as required at CONUS and

OCONUS locations. Contractor shall not perform crash recovery services off-base at

CONUS or OCONUS locations without prior written approval from the government program manager or contracting officer.

3.3.2 Composite Repair: Perform O-level composite repair IAW applicable T.O.s and authorized depot-level directives.

3.3.3 Nondestructive Inspection (NDI): Perform nondestructive inspections as required

IAW applicable T.O.s and authorized depot-level directives.

3.3.4 Emergency Services Training: Provide up to 3 hours of MQ-1/MQ-9 familiarization training per calendar quarter to Government emergency services personnel (Fire Dept, etc.) at each deployed site.

3.4 Aircraft Impoundment: Comply with aircraft impoundment procedures IAW AFI 21-101 and local procedures.

3.5 Aircraft Positioning: Position and remove aircraft for special purpose use as directed by the government. Comply with all safety and munitions directives as applicable for all special use and static display aircraft.

3.6 Additional Maintenance Requirements: Comply with additional O-level maintenance requirements and programs IAW AFI 21-101 and Appendices C & D.

3.7 Certifications: Special Certification Roster (SCR). Develop, maintain and present an SCR program to identify those contractor employees trained and certified to complete critical tasks.

Keep the certification lists of authorized personnel to a minimum consistent with requirements and immediately notify the COR and government program office of any changes. All certification documentation will be maintained in an electronic data file and be available for review at government request. Ensure the SCR is reviewed quarterly by appropriate work center supervisors to verify that all entries are current and accurate, and prerequisites including applicable training, testing, evaluation, or other requirements for task certification have been completed. The contractor’s SCR shall be reviewed and signed by the Contractor Program

Manager (no delegation is authorized). The Contractor Site Lead will ensure the Government

CORs have a current copy of the SCR. At a minimum the SCR tracked items shall include:

* All Systems Red-X (no egress/welding/munitions)

* Red-X Down Grade (Shall be used only when specifically authorized by the applicable Maintenance Group Commander)

* Red-X By Specialty

* Clear Red-X When Lost Tool/Item Cannot Be Found

* Exceptional Release (ER)

* Impoundment Authority

* All Systems In Process Inspection (IPI) (no egress, welding, munitions)

* In-Process Inspection By Specialty

* Mission Impaired Capability Awaiting Parts (MICAP) Approval

* CANN Authority

* Tow Team Supervisor

* Could Not Duplicate (CND)

* Installed Engine Run Certifier

* Installed Engine Run

* Not Reparable This Station (NRTS) and Serviceability Tag

* Weight and Balance Certified/Clear Red X

* Test, Measurement, & Diagnostic Equipment (TMDE) Calibration Limitation Approval

* Weapons Supervisory Postload Inspection

3.8 Depot and Contracted Field Teams (CFT): Support depot and contracted field teams as required for depot-level TCTO modifications/aircraft maintenance.

3.9 Response Time: Maintain a maximum two minute response time for all GCS outages for assigned Remote Split Operations (RSO) and an immediate response time for all Reachback site outages.

3.10 Ground Control Station (GCS): Provide organizational-level O&M support for all assigned GCSs, subsystems, ancillary equipment and Ground Data Terminals (GDT). Perform all pre-, thru-, and post-flight inspections, launch and recovery activities scheduled and unscheduled maintenance IAW applicable T.O.s in Appendix D. Operate and maintain GDT systems, including units located on government communications towers. Provide technical solutions to integrate government requests and TCTOs. Operate and maintain all C4ISR systems and infrastructure interfacing or supporting GCS operations within established demarcation points listed in Appendix K. Document all daily maintenance activity IAW Paragraph 2.23.3.

System shall meet or exceed published Operational Readiness Rates (OR) IAW Appendix H.

3.11 Tactical Field Terminal (TFT)/Fixed Site SATCOM Terminal (FSST)/SATCOM

Earth Terminal Sub-System (SETSS): Provide organizational level O&M support for all assigned mobile and fixed satellite earth terminals, subsystems, ancillary equipment and supporting C4ISR systems within established demarcation points listed in Appendix K.

Maintain and relocate mobile satellite earth terminals and transportation platforms, components, and assemblies. Maintain, troubleshoot, and repair all earth terminal systems and equipment

IAW applicable publications, directives, guidance and T.O.s listed in Appendix D. Provide solutions to integrate government requests and TCTOs to upgrade satellite earth terminals, subsystems, ancillary equipment and supporting C4ISR systems. Provide immediate (within 15 minutes) notification to designated Operation Centers/Cells any hardware failures and any unscheduled maintenance activities, all lost link condition occurring for one or more missions due to Reachback equipment, all power failures at the site, heavy local weather that may affect satellite system transmit/receive signal strength, maintenance actions/activities that require moving GCSs between threads/satellite, and all other issues that can have immediate impact on on-going missions. Document all daily maintenance activities for these systems IAW Paragraph

2.23.5. Document all weekly maintenance activity IAW Paragraph 2.23.6. Establish and maintain a System Circuit Information Guide for all OCONUS Reachback/communication facilities IAW Paragraph 2.23.7. Systems shall meet or exceed published OR IAW Appendix H.

Perform validation and verification for organizational-level TCTOs as required.

3.12 Reachback Facilities: The Reachback facilities provide critical connectivity using satellite and networking resources as described in paragraphs 3.11 and 3.13. Provide all personnel, supervision, and other services necessary to support, operate, maintain, configure, and repair

C4ISR systems, equipment, and circuits supporting RPA missions at OCONUS facilities within established demarcation points listed in Appendix K. Establish, obtain, and maintain spares for equipment and systems as approved by the government. Reachback sites require 24/7/365 on-site coverage. Operational direction shall be accepted for satellite earth terminal configurations only from approved designated Operation Centers/Cells. Maintain, troubleshoot, and repair all circuits/ equipment IAW applicable COTS publications, directives, T.O.s, OIs, and COTS service manuals. Perform operational checks to verify all equipment is serviceable and able to support mission requirements. Develop and accomplish preventative maintenance routines for commercial C4ISR systems IAW applicable commercial manuals and manufacturer’s guidance.

PMIs on Single Point of Failure equipment or system shall be approved only by designated

Operation Centers/Cells using the Reachback site for command and control of aircraft. Accept operational direction from the 432 nd

Network Operations Center (NOC) or ACC AMIC/PMA for the FSST and SETSS. Accept operational direction from Global Hawk Operations Cells and forward operating locations or ACC AMIC/PMA for the TFT.

3.12.1 MQ-1/MQ-9 Reachback Operations: Report the following events to the 432d

Network Operations Center (NOC) via secure telephone (use number provided by 432d

Aircraft Communications Maintenance Squadron (ACMS)) within 15 minutes of

Reachback Site awareness of an unscheduled occurrence. Events initiated by notification from the 432 ACMS do not require an initial report from the Reachback Site. Report conclusion of an event within 30 minutes via SIPR email to 432 NOC and AMIC (use email addresses provided by 432 ACMS and AMIC).

o Hardware failures and/or unscheduled maintenance activities that affect missions.

o All lost link conditions due to equipment at the Reachback Site.

o All power failures affecting site operations to include transferring site to or from backup generator power.

o Local weather causing significant disruption to satellite system transmit/receive signal strength. 432d Wing Operations Center (WOC) Weather personnel will assist with assessing weather severity and duration to the Reachback Site and all

GCSs.

o Signal anomalies/interference that impact communications links. Also report all suspected or observed Electromagnetic Interference (EMI) incidents IAW AFI

10-707 Spectrum Interference Resolution Program.

o Other issues within the control of the Reachback Site personnel that have immediate impact to on-going MQ-1/MQ-9 missions.

3.12.1.1 Coordinate and obtain approval from the 432 NOC prior to making temporary or permanent configuration changes on all mission equipment that affect ongoing missions (other than the object of troubleshooting). Additionally, coordinate and obtain approval from the 432 NOC prior to performing maintenance activities that impact ongoing missions. Depending on the mission impact, some maintenance activities (i.e.

Authorized Service Interruptions (ASIs) ) may require up to 30 days prior notification/approval. Report conclusion of changes within 30 minutes via SIPR email

(use email addresses provided by 432 ACMS and AMIC).

3.12.1.2 Reachback Site personnel shall contact the 86th Airlift Wing (AW) Command

Post, for possible initiation of checklist F5 immediately after isolating any of the following events that are within the control of the 86 AW.

o Loss of power.

o Loss of C2 data communication (primary or redundant paths) within Ramstein

Tech Control area of responsibility.

o Emergency or mission-critical CE item (i.e. roof leak near equipment, flooding).

o Other infrastructure issues that may affect Reachback Site operations.

3.12.1.3 432 NOC will provide the following to the Reachback Site via email or telephone communication: Communications Posture (COMSPOT), Communications

Critical Incident (CCI), and NOC daily reports that include ASI schedules.

3.12.1.4 Coordinate any required changes with the 432 NOC prior to moving ground control stations to a new thread/satellite terminal.

3.12.2 Maintain daily documentation of all maintenance activities performed on C4ISR systems and circuits IAW Paragraph 2.23.5. Document all weekly maintenance activity

IAW Paragraph 2.23.6. Systems shall meet or exceed published OR IAW Appendix H.

3.12.3 Support emerging technologies, to upgrade/increase Reachback capabilities, infrastructure, and mission at government direction. O-level support shall include planning assistance, configuration changes, cable fabrications, testing, coordination, COMSEC, operational verification assistance, and implementation of approved modifications as directed by designated Operation Centers/Cells and ACC

AMIC/PMA/PSC.

3.12.4 Relocation: The contractor shall support the relocation of Reachback Site operations from currently occupied facilities to new facilities located on the current installation as directed by the government. The contractor shall assist the government in developing a relocation plan to include reutilization, disposition, and decommissioning of the equipment located in the previously occupied facility as approved by the government.

3.12.5 Technical Interchange: Participate in technical interchange meetings as directed by government personnel/representatives for the purpose of discussing technology/services managed by the contractor under this PWS.

3.12.6 Emergency Generators and UPS: The contractor shall accomplish periodic checks and first responder actions to back-up generator and UPS equipment. All Reachback personnel shall be able to perform emergency generator start-up actions as required in response to commercial power outages.

3.13 Circuit Support: Monitor, troubleshoot, configure, repair, and modify all communications systems/equipment and Reachback circuitry supporting satellite earth terminal operations within established demarcation points listed in Appendix K. Install and maintain fiber optic cable jumpers to support equipment connectivity requirements. Work with outside entities to include

DISA and local host base circuit actions personnel to install new circuit connectivity as site growth requires with coordination and approval by approved and designated Operations

Centers/Cells. Maintain a circuit history folder consisting of Request for Service (RFS), Telecommunications Service Request (TSR), Telecommunications Service Order (TSO), and change TSO paperwork. Notify the appropriate government entity when new circuits require new equipment purchases to support installation including routers, switches, and fiber or electrical cables. Coordinate with ACC AMIC/PMA & PSC; 432 ACMS if network equipment, including routers, switches, fiber, or electrical cabling is in need of replacement or spares on hand fall below 10% of operational levels. Document and report all barriers to completing new circuit installation in the C4ISR Daily Maintenance Report, Paragraph 2.23.5. Operate and maintain all Remote Split Operations (RSO), including the Asynchronous Transfer Mode

(ATM)/Internet Protocol (IP) network systems and circuits and cryptographic equipment.

Document all daily maintenance activities for these systems IAW Paragraph 2.23.5. Document all weekly maintenance activity IAW Paragraph 2.23.6. Establish and maintain a System Circuit

Information Guide for all OCONUS Reachback/communications facilities IAW Paragraph

2.23.7. Systems shall meet or exceed published OR IAW Appendix H.

3.13.1 Coordinate and assist all troubleshooting efforts. Work with other entities or organizations as required to resolve circuit outages and modifications at lines of demarcation IAW Appendix K. The contractor shall immediately report external connection problems and all configuration changes to designated Operation

Centers/Cells, and ACC AMIC/PMA/PSC. Restore all circuit and system outages affecting OCONUS RPA missions. Response time to TS circuit outages shall be immediate.

3.13.2 ATM-to-IP migration: Assist in engineering changes and implementations of technology changeovers such as ATM equipment to IP; this may include hardware such as switches, routers, edge devices, and encryption equipment. Aid the government in creating and implementing a Reachback migration plan from ATM to IP which minimizes or eliminates mission down time. Coordinate and implement any circuit or technology changes with approved designated Operations Centers/Cells. Document equipment technology changes in comprehensive network diagrams using the Microsoft

Visio software application. These diagrams must accurately reflect both the layer 1 network and subnet address for all ports and interfaces.

3.14 Information Assurance (IA) Certification for Reachback Personnel: Personnel performing IA functions that establish policies or implement security measures or those performing technical support for networks at Reachback sites shall be IA certified at Technical

Level II IAW DoD 8570.01-M and Appendix M. Certifications and required Continuous

Education or Sustainment Training shall be maintained through the life of the contract.

3.15 Maintenance Documentation: Make all required entries into IMDS, RPA, and Equipment

Forms. Provide representative and participate on the Data Integrity Team. Maintenance actions shall be documented IAW AFI 21-101 and T.O. 00-20-1.

3.15.1 Debrief: Perform mission debrief function following each sortie IAW AFI

21-101 and local directives using software and communications tools provided by government specifically for debrief function.

3.16 Plans, Scheduling, and Documentation: Perform Aircraft Maintenance Unit (AMU)-level plans, scheduling, and documentation functions IAW applicable directives and publications listed in Appendices C and D. Accomplish applicable Time Compliance Technical Order

(TCTO), one-time inspections, modifications, and other special maintenance items as directed by the government.

3.17 Maintenance Management Analysis: Track, report, and analyze maintenance activities

IAW AFI 21-101 for supported units. Provide input to host unit military Maintenance Analysis personnel for Monthly Logistics Indicators Report, RCS: ACC-LGP (M) 9302 IAW ACCI 21-

118 when contractor supports host wing Maintenance Analysis military analysts. Track and report metrics to the Government Program Office IAW PWS Paragraphs 2.23.9 and 2.23.10

Provide Monthly Logistics Indicators Report, RCS: ACC-LGP (M) 9302 as required by ACCI

21-118 and, or equivalent product for other MAJCOMs, IAW PWS Para 2.23.11 for supported units when contractor provides sole Maintenance Analysis support. Provide additional data and reports to the government program office as requested. Coordinate activities with military analysis personnel as required to provide required Wing-level products. All analysis support shall be located at Creech AFB, NV unless otherwise directed by the Contracting Officer.

3.18 Combat Air Patrol (CAP): The total effort (personnel, aircraft, equipment, etc.) required to generate and sustain a combat capable aircraft on station (over target or area to be surveilled), 24 hours a day, continuously as dictated by mission requirements. The government reserves the right to schedule a CAP as two separate operational sorties (e.g., Contractor launches one aircraft, recovers it 8 hours later, then launches second aircraft on different mission. Second sortie is considered part of the original CAP). Contractor shall launch additional aircraft as required to support a CAP when original aircraft is unable to support mission requirements (e.g., maintenance abort, fuel/munitions, etc.).

3.18.1 Stand-Alone CAP: The first CAP at a given deployed location (Core maintenance/support package). The government shall assign up to 4 MQ-1 or MQ-9

RPAs as applicable, up to 2 GCSs, and up to 2 GDTs per stand-alone CAP.

3.18.2 Collocated CAP: All additional CAPs at a given deployed location after the stand-alone CAP. The government shall assign up to 4 MQ-1 or MQ-9 RPAs as applicable for each collocated CAP. Two GCSs & 2 GDTs may be assigned for every 6 total CAPs at a deployed location.

3.18.3 Commander Directed Sorties: Contractor shall support up to 2 sorties per day (in addition to the number of CAPs on contract) at the local commander’s direction. The number of commander directed sorties shall be limited to a maximum of 20 sorties in a

30 day rolling window at each deployed site. Any sortie performed under this section shall be deemed…