The file's text, extracted by GovTribe without its formatting.
GROUND SUPPORT PERFORMANCE WORK STATEMENT (PWS)
Space Systems Command (SSC) Innovation and Prototyping (SYD89) Prototype Ground Development and Sustainment Branch (SDG) Kirtland AFB, New Mexico
CHANGE LOG
| Version |
| Date |
| Summary of Changes |
| 1.0 |
| 16 December 2025 |
| Initial Draft |
| 2.0 |
| 4 March 2026 |
| Revised Draft |
TABLE OF CONTENTS
| 1. | PURPOSE | 4 |
| 2. | BACKGROUND | 4 |
| 3. | SCOPE | 4 |
| 4. | PERFORMANCE OBJECTIVES | 4 |
| 5. | CONTRACT TRANSITION | 5 |
| 6. | SUPPORT REQUIREMENTS | 5 |
| 1. | ABBREVIATIONS AND ACRONYMS | 13 |
1. PURPOSE
This Performance Work Statement (PWS) supplements the originating Hybrid Architecture and Development for Experimental Systems (HADES) Indefinite Delivery/Indefinite Quantity (IDIQ) PWS, encompassing the development, management and sustainment of all technical operational requirements necessary to ensure continuous mission execution on the Research, Development, Test, and Evaluation Support Complex (RSC). Unless explicitly stated otherwise in this document, all aspects of the original HADES IDIQ PWS are still valid and applicable. As supplemental, the contractor shall perform engineering, development, integration, and sustainment, and associated support services primarily at the RSC located at Kirtland Air Force Base (KAFB), New Mexico and may include occasional travel to contractor facilities for collaboration and integration testing.
2. BACKGROUND
The RSC requires secure, high-performance access extension and switching capabilities to support simultaneous multi-level missions. The organization’s goal is to accelerate mission design and ground integration, launch and on-orbit operations, ground system tests, and rapid fielding to provide reliable, low-cost access to space in support of the warfighter. Ground support maintains facility infrastructure, Information Technology (IT) systems, cybersecurity, physical security and integration activities critical to day-to-day mission execution.
3. SCOPE
The contractor shall provide day-to-day operational support, maintain full mission readiness and ensure the RSC environment remains capable of supporting multi-mission, multi-classification space operations. The scope includes sustaining existing RSC capabilities, developing and integrating new or evolving mission requirements, ensuring secure and reliable system performance, and delivering responsive support to all programs operating within or dependent upon the RSC. The requirement of support may fluctuate based on product development and budget requirements in response to awarded Task Orders. The contractor will be required to accomplish the tasks in this ancillary PWS and in the primary HADES IDIQ PWS.
4. PERFORMANCE OBJECTIVES
The PWS requirements from the originating HADES PWS which are applicable to this effort are identified via bullet lists below. In general, the following paragraphs apply only to the extent the work is directly applicable to the accomplishment of this effort. Further clarified specifications are identified for specific requirements where appropriate.
The following requirements are applicable to this effort in their entirety:
| · 1.3 |
| Access Department of the Air Force Computer Systems |
5. CONTRACT TRANSITION
The following transition requirements are applicable to this effort in entirety:
| · 2.1 |
| Contract Transition |
6. SUPPORT REQUIREMENTS
The following aspects of the HADES IDIQ Support Services section (2.2) are applicable to this effort:
· 2.2.1
Program Management
· 2.2.2.5
| · 2.2.3 |
| Information Management |
· 2.2.3.3
| · 2.2.4 |
| Security and Data Handling |
· 2.2.4.15
2.2.4.16 The contractor shall be responsible for maintaining complete accountability and accurate documentation for all unclassified and classified hardware in accordance with TSCO and GSSO policies.
2.2.4.17 The contractor shall also manage, maintain, control, procure, issue, inventory and safeguard all GFP. This includes reviewing equipment usage and material consumption to ensure full accountability of all GFP associated with this contract.
· 2.2.6.3
| · 2.2.7 |
| Training and Certification |
· 2.2.7.11
| · 2.2.8 |
| Configuration Management |
| · 2.2.9 |
| Procurement, Logistics and Lifecycle Management |
2.2.9.30 The Contractor shall develop technology refresh packages in accordance with their Life Cycle Sustainment plan and any applicable System Engineering plan and make these packages available to the government.
2.2.9.31 Perform maintenance on the Rendezvous and Proximity Video Distribution System (RVDS) as required. Effort includes, but is not limited to, the following actions:
· System administration of the RVDS SMP (Symmetric Multiprocessing) appliance (to include adding and removing sources from the SMP appliance, as requested)
· Debugging and repairing RVDS network connections
· Debugging and repairing touch panel connections or configurations
· Repairing RVDS networking connections to displays (monitors, televisions and projectors)
· Ensuring that RVDS equipment and interfaces are functioning as intended
· The contractor shall be expected to work with the manufacturer of the RVDS system to establish a relationship in which the manufacturer will provide reach-back technical support to both the Contractor and the Government
· Attend proprietary training for RVDS system as required
· Login to every computer (not workstation) once per month on the NIPR, SIPR, JWICS, SGN, and Mission networks that are connected via the RVDS system as part of monthly PMI’s. This action ensures that the computer resources are not removed from their respective networks due to in-activity during periods of low mission activity
2.2.9.32 Provide on-site hardware support, troubleshooting and maintenance during normal business days and hours (M–F, 8–5) and on-call support during non-business hours with a 3-hour threshold.
2.2.9.33 Contractor shall resolve the identified problems within 2 hours during business hours. Contractor shall resolve the identified problems within 3 hours during non-business hours.
2.2.9.34 Ensure any changes to the baseline for the purpose of restoring mission service are presented to and approved by the Government prior to implementation. If the change to the operational baseline is directed by the Government, the 3-hour limitation to fix will not count against the contractor.
| · 2.2.10 |
| Concept Development |
· 2.2.10.5
The following aspects of the HADES IDIQ Ground System Services section (2.3) are applicable in their entirety:
| · 2.3 |
| Ground Systems Services |
| · 2.3.1 |
| Ground System Engineering and Design |
| · 2.3.2 |
| Ground System Development |
| · 2.3.3 |
| Ground System Integration |
| · 2.3.4 |
| Ground System Sustainment |
· 2.3.4.9
| · 2.3.5 |
| Ground System Decommission, Disposal, and/or Transfer |
· 2.3.5.9
The following aspects of the HADES IDIQ Facility Services section (2.4) are applicable to this effort:
| · 2.4.1 |
| Power Distribution and Resiliency Support |
| · 2.4.2 |
| Heating, Ventilation and Air Conditioning Support |
| · 2.4.3 |
| Facility and Furniture Maintenance |
| · 2.4.4 |
| Network Infrastructure Support |
| · 2.4.5 |
| Space Optimization and Layout |
| · 2.5 |
| Software Support Services |
· 2.5.3.3
| · 2.6 |
| OTHER ACTIVITIES (COMSEC) |
2.6.2 Cybersecurity
| · 2.6.2 |
| OTHER ACTIVITIES (CYBERSECURITY) |
· 2.6.2.9
7. ABBREVIATIONS AND ACRONYMS
| ABBREVIATION/ACRONYM |
| MEANING |
| CONOPS |
| Concept of Operations |
| ERB |
| Engineering Review Board |
| GFP |
| Government Furnished Property |
| HADES |
| Hybrid Architecture and Development for Experimental Systems |
| IDIQ |
| Indefinite Delivery Indefinite Quantity |
| KAFB |
| Kirtland Air Force Base |
| MUS |
| Mission Unique Software scripts |
| OAT |
| Operational Assessment Test |
| PWS |
| Performance Work Statement |
| RSC |
| Research, Development, Test, and Evaluation Support Complex |
| RVDS |
| Rendezvous and Proximity Video Distribution System |
| SMP |
| Symmetric Multiprocessing |
| SSC |
| Space Systems Command |
| SYD89 |
| Innovation and Prototyping Delta |
image1.png image2.png