RPA Task Order 3 - PWS (26 WPN Nellis) - FINAL.pdf
PDF 271 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 3 under an Indefinite Delivery, Indefinite Quantity (IDIQ) contract.
The PWS outlines the unique requirements for providing Organizational-level (O-level) maintenance support for the Test Evaluation Squadron and United States Air Force Weapons School missions at Nellis AFB, NV. Key details include specific support requirements for MQ-9 Ground Control Station (GCS) cockpits in a secure Top Secret/Special Access environment, coordination with various units, software support, and Level of Effort for GCS, Avionics, and other areas. The PWS also specifies the Period of Performance and unique security clearance and access badge requirements. The related federal contract opportunity is a Draft Request for Proposal (DRFP) for the upcoming competitive requirement for RPA Maintenance support services, with a 5-year ordering period and an estimated award date of April 1, 2025.
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 – 3
Contract Number: FA4890-24-X-00XX
Date: 20 August 2024
REMOTELY PILOTED AIRCRAFT (RPA) Mx – Task Order 3 PWS
Date: 20 Aug 2024
Task Order 3 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 Unique Task Requirements
2.2 Unique Security Requirements
3.0 POINTS OF CONTACT
Table 1. Unique Requirements Level of Effort Table 2. Security Clearance & Access Badge Requirements
Task Order 3 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 O-Level maintenance in support of the Test Evaluation Squadron and United States Air Force Weapons School missions. These include support to MQ-9 Ground Control Station (GCS) cockpits in a secure environment up to and including Top Secret / Special Access.
1.2 Locations
Locations included in this PWS are as follows:
• 57th Wing, 26 Weapons (WPS) Schoolhouse, Nellis AFB, NV, Building 119
• 53rd Wing, 556 Test & Evaluation Squadron (TES), Operating Location Alpha, Nellis AFB, NV
1.3 References
References include:
• RPA IDIQ PWS
• IDIQ PWS Attachments 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; with four 12-month options.
2.0 UNIQUE REQUIREMENTS
2.1 Unique Task Requirements
2.1.1 The Contractor shall coordinate all local operational and maintenance requirements with the 26 WPS, 556 TES, and 432 MXG, as required.
2.1.2 Contractor shall utilize “redline” technical orders approved by ACC/A4I.
2.1.3 GCS Support
2.1.3.1 The Contractor shall provide Weapons School support 5 days per week for up to seven (7) MQ-9 ground control stations with a 20-hour daily flying window.
Test and Evaluation support includes four (4) days per week with an 8-hour flying window no earlier than 0800 and normally ends no later than 1800L.
2.1.3.2 The Contractor shall coordinate flying window management with the locally supported units, i.e., 26 WPS and 556 TES, and provide maintainers in support of early/late flying windows to meet mission requirements as necessary.
2.1.3.3 The Contractor shall provide weekend T&E support up to four (4) times per year; total number of days supported remains at four days per week when supporting weekend flying.
2.1.3.4 The Contractor shall be prepared to support six (6) Green Flag and Red Flag exercises when scheduled. Support will be required for a 24-7 flying window
Task Order 3 PWS Page | 4 over three (3) weeks (consecutive days) to include weekends and holidays.
2.1.3.5 The Contractor shall proactively communicate with the Government regarding exercise scheduling.
2.1.3.6 The Contractor shall provide GCS software support for both approved released software and test software as approved by 53 TEG.
2.1.4 The Contractor shall provide support per the Level of Effort (LOE) table below.
RPA Mx Site UTC CL / CT AC GCS
Nellis AFB, NV 0 N/A 0 7
Total 0 N/A 0 7
Table 1. Unique Requirements Level of Effort
NOTES:
• Currently at five (5) Cockpits planning growth up to seven (7) for exercise support.
• Up to 6 CL/CT, in coordination with 26 WPS/53 TES.
• Individual GCS configurations are determined by ACC through approved TCTOs, AF 1067s, or Modification Directives.
2.2 Unique Security Requirements
Security clearance level and access badges required are detailed in Table 2 below.
Location Security Clearance Level Required Access Badges Required
Nellis AFB TS/SCI & SAP Comon Access Card (CAC), SCIF Badge; White SAP Badge
Table 2. Security Clearance & Access Badge Requirements
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 Unique Task Requirements |
| 2.2 Unique Security Requirements |
| 3.0 POINTS OF CONTACT |
File details come from the government source that posted it. Updated .