RPA Task Order 7 - PWS (DP-80) - FINAL.pdf
PDF 253 KB Posted
- Solicitation number
- DRFP2-FA4890-24-R-0012
About this file
This document is a Performance Work Statement (PWS) for a Remotely Piloted Aircraft (RPA) Maintenance Support Task Order under an Indefinite Delivery, Indefinite Quantity (IDIQ) contract.
The PWS outlines the unique requirements for RPA organizational-level maintenance support, including maintenance actions, security, travel, and personnel requirements. Key details include providing 24/7 maintenance support for a single Unit Task Code consisting of a Main Operating Base and up to two contingency locations, conducting Satellite Communications Launch and Recovery operations, and maintaining a facility for battery charging. Unique security requirements include a SECRET clearance and restricted area badges. The Period of Performance is 1 Jul 2025 - 30 Jun 2026 with four 12-month option periods. The contract is expected to be awarded under NAICS code 488190 with a small business size standard of $35 million.
View the file
Other files
Show all 26
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Headquarters Air Combat Command (HQ ACC)
ACC AMIC PMAU
PERFORMANCE WORK STATEMENT
(PWS)
FOR
Remotely Piloted Aircraft (RPA)
Maintenance Support
Task Order – 7
Contract Number: FA4890-24-X-00XX
Date: 20 August 2024
REMOTELY PILOTED AIRCRAFT (RPA) Mx – Task Order 7 PWS
Date: 20 Aug 2024
Task Order 7 PWS Page | 2
TABLE OF CONTENTS
1.0 INTRODUCTION
1.1 Task Order Scope
1.2 Locations
1.3 References
1.4 Period of Performance (PoP)
2.0 UNIQUE REQUIREMENTS
2.1 Maintenance Requirements
2.2 Unique Security Requirements
2.3 Unique Travel and Transportation Requirements
2.4 Unique Personnel Requirements
3.0 POINTS OF CONTACT
Table 1. Unique Requirements Level of Effort Table 2. Security Clearance & Access Badge Requirements
Task Order 7 PWS Page | 3
1.0 INTRODUCTION
The Contractor shall provide qualified Organizational-level (O-level) maintenance IAW the Indefinite Delivery, Indefinite Quantity (IDIQ) Task Order performance work statement (PWS).
This PWS provides unique Remotely Piloted Aircraft (RPA) O-level support requirements as specified below. All other requirements are outlined in the IDIQ PWS.
1.1 Task Order Scope
Conduct MQ-9 Ground Control Station (GCS) cockpit and RPA O-Level maintenance for the primary operating location and forward contingency locations.
1.2 Locations
Locations included in this PWS are as follows:
• DP-80
• Forward Contingency Locations
1.3 References
References include:
• RPA IDIQ PWS
• IDIQ PWS Appendices A-L
• IDIQ Attachment 3 – Manpower, Labor Rates, and Pricing Tables
1.4 Period of Performance (PoP)
The PoP for the Base Year is twelve months: 1 Jul 2025 – 30 Jun 2026 followed by four 12-month options.
2.0 UNIQUE REQUIREMENTS
2.1 Maintenance Requirements
2.1.1 The Contractor shall accomplish planned sortie production and maintenance actions to ensure the Air Tasking Orders (ATO) for one (1) unit task code (UTC) consisting of one (1) main operating base (MOB) and up to two contingency locations.
2.1.2 The Contractor shall provide the ability to perform SATCOM Launch and Recovery (SLR) operations during sortie generation to include Commander Directed Lines (CDLs) as directed by the Combatant Commander or delegated authority.
2.1.3 The Contractor shall be prepared to support operations 24 hours per day, 7 days per week.
2.1.4 The Contractor shall follow DAFMAN 21-201 for Munitions loading/arm/de- arm, unless local procedures are more restrictive, then follow the local procedures.
2.1.5 The Contractor shall conduct Minimum Proficiency Requirement Load (MRPL) evaluations, to include initial monthly proficiency reviews, bi-monthly, semi-annual, and flightline evaluations when supporting OCONUS forward deployed MQ-9 munitions load operations.
2.1.6 The Contractor shall provide Maintenance Recovery Team (MRT) heavy maintenance support as coordinated with AMIC Program Management Office (PMO) and Site Commander for a period of up to 14 days.
Task Order 7 PWS Page | 4
2.1.7 The Contractor shall support as provided in the Level of Effort table below.
RPA Mx Site UTC CL / CT AC GCS
DP-80 2 8 16 4
Total 2 8 16 4
Table 1. Unique Requirements Level of Effort
2.1.8 The Contractor shall provide agile light maintenance aircraft support that is responsive and flexible, allowing for rapid directing, redirecting, and mission prioritization in coordination with the AMIC PMO and Site Commander for up to 14 days.
Assumptions:
• Expect up to 2 of the 8 combat lines will temporarily move along with 4 aircrafts.
• Expect the first combat line to be operational within 24 hours and the second within
72 hours.
2.1.9 The Contractor shall maintain a facility for battery charging adjacent to MQ-9 hangar.
NOTES:
• In accordance with SLR implementation, GCS support is expected to become obsolete.
• Two projected assigned MQ-9 hangars are on the ramp with MQ-9 parking area approximately
300’ away with adequate space to support 8 combat lines. Aircraft ramp parking and hangar space for additional aircraft may be physically separate from the projected 2 assigned hangars.
2.2 Unique Security Requirements
2.2.1 Security clearance level and access badges required are detailed in Table 2 below.
Location Security Clearance Level Required Access Badges Required
DP-80 SECRET Comon Access Card (CAC) & Restricted Area Badge
Table 2. Security Clearance & Access Badge Requirements
2.2.2 Visitor Group Security Agreement (VGSA). AFMAN 16-1406 does not require the contractor to sign a VGSA. Contractors who operate as an independent visitor group are subject to AFMAN 16-1404 and must identify an on-site security point of contact (POC) to the local Information Protection Office. Upon notification of the presence of the visitor group, the Information Protection office will contact the FSO and provide them with the local security policies when classified performance will occur to the contractor in writing (e.g., email, electronic media, or paper).
2.2.3 Long-Term VGSA. The contractor shall enter a long-term visitor group security agreement if contract performance is on base for 90 days or more. This agreement shall outline how the contractor integrates security requirements for contract operations with the Air Force to ensure effective and economical operation on the installation. The agreement shall address:
2.2.3.1 Security support provided by Air Force. Security support provided by the Air Force to the Contractor, including storage containers for classified information/material, use of base destruction facilities, classified reproduction facilities, use of base classified mail services, security badges, base visitor control, investigation of security incidents, Task Order 7 PWS Page | 5 base traffic regulations, the use of security forms, and conducting inspections required by DOD 5220.22-R and AFMAN 16-1406.
2.2.3.2 Security support requiring joint Air Force and Contractor coordination.
Includes packaging classified information, mailing and receiving classified materials, implementing emergency procedures for protection of classified information, security checks, and internal security controls for protection of classified material and high value pilferable property.
NOTE: On base, the long-term visitor group security agreement may take the place of a Standard Practice Procedure (SPP).
2.3 Unique Travel and Transportation Requirements
2.3.1 The Contractor shall travel via Commercial or MilAir travel from CONUS to expeditionary theater distribution centers (ETDC) and on to tasked location, or commercial travel from CONUS directly to host country as directed by COCOM.
2.3.2 The Contractor is responsible for providing vehicles to move personnel between duty location and billeting.
2.3.3 The Government is responsible for providing general-purpose flightline, MRT and special-purpose vehicles.
NOTE: The Contractor may also use the Government provided shuttle for moving people around the base.
2.4 Unique Personnel Requirements
2.4.1 The Contractor personnel shall be billeted on base.
2.4.2 The Contractor shall have access to the designated on-site dining facility and will utilize a ‘pay-as-you-go’ strategy.
3.0 POINTS OF CONTACT
• Anne Renn, PMAU Program Manager (PM), 757-764-9427, annette.renn@us.af.mil
• Carlos D. Thomas, PMAU Deputy PM, 757-528-3972, carlos.thomas.8@us.af.mil
• MSgt Kurtis Hoar, PMAU Maintenance SME, DSN: 757-225-9718, kurtis.hoar@us.af.mil
• S. Leeann Ori, PKC Contracting Officer, 757-255-4713, sherri.ori@us.af.mil
• Emma Elmore, PKCA, emma.elmore@us.af.mil
• Anthony Mills, DRQ/Contracting Officer Representative (COR) Lead, 702-468-2511, anthony.mills.7@us.af.mil
• Site COR(s), pending appointment prior to award mailto:carlos.thomas.8@us.af.mil mailto:emma.elmore@us.af.mil mailto:anthony.mills.7@us.af.mil
| 1.0 INTRODUCTION |
| 1.1 Task Order Scope |
| 1.2 Locations |
| 1.3 References |
| 1.4 Period of Performance (PoP) |
| 2.0 UNIQUE REQUIREMENTS |
| 2.1 Maintenance Requirements |
| 2.2 Unique Security Requirements |
| 2.3 Unique Travel and Transportation Requirements |
| 2.4 Unique Personnel Requirements |
| 3.0 POINTS OF CONTACT |
File details come from the government source that posted it. Updated .