(U) Section L Attach D Ground Control PWS 20260820.pdf

UNCLASSIFIED

i

UNCLASSIFIED

HYBRID ARCHITECTURE AND DEVELOPMENT FOR

EXPERIMENTAL SYSTEMS (HADES) SERVICES

GROUND CONTROL

PERFORMANCE WORK STATEMENT (PWS)

FA8809-26-R-B002

SPACE SYSTEMS COMMAND (SSC)

SYSTEMS DELTA 89 (SYD89)

INNOVATION AND PROTOTYPING DELTA (SD)

INNOVATION AND PROTOTYPING DIVISION GROUND (SDG)

KIRTLAND AFB, NM

24 JULY 2026

Distribution Statement A. Approved for public release. Distribution is unlimited.

Destruction Notice: For unclassified, limited documents, destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

ii

REVISION HISTORY

Revision Date Version Description

1 1/15/2026 1.0 Initial Ground Control PWS

2 1/28/2026 2.0 Initial PWS published to SAM.gov

3 3/10/2026 3.0 Aerospace revision, Ground Control PWS

4 4/20/2026 3.1 Aerospace revision, 5 7/24/2026 3.8 Aerospace revision, GOV input iii

UNCLASSIFIED

Innovation and Prototyping Division Ground

SSC/SYD89/SDG

Kirtland AFB, NM

7/24/2026

(U) Hybrid Architecture and Development for Experimental Systems

(HADES) Services

Ground Control

Performance Work Statement (PWS)

(U) Contents

(U) Contents .................................................................................................................................................................iii

1. (U) PURPOSE AND OBJECTIVES

1.1 (U) Purpose

2. (U) OBJECTIVE

3. (U) BACKGROUND

4. (U) PERFORMANCE REQUIREMENTS

4.1 (U) Contractor Meeting Participation

4.1.1 (U) Ground Control Program Coordination

4.1.2 (U) Technical and Operations Review

4.1.3 (U) Mission Partner Coordination

5. (U) INHERITED AVAILABILITY REQUIREMENTS

5.1 (U) Ground Control Mission Enabling Role

6. (U) SCOPE

6.1 (U) HADES IDIQ Requirements

7. (U) ACCESS TO DEPARTMENT OF THE AIR FORCE COMPUTER SYSTEMS

7.1 (U) HADES IDIQ Requirements

8. (U) BASIC SERVICES

8.1 (U) HADES IDIQ Requirements

5.0 – Basic Services

5.1 – Contract Transition

5.2 – Support Services

5.2.1 – Program Management Ground Control Specific Requirements:

5.2.2 – Cost Management

5.2.3 – Information Management Ground Control Specific Requirements

5.2.4 – Information Management Ground Control Specific Requirements Ground Control Specific Requirements ............................................................ Error! Bookmark not defined.

Ground Control Specific Requirements Ground Control Specific Requirements ............................................................ Error! Bookmark not defined.

Ground Control Specific Requirements Ground Control Specific Requirements

9. (U) GROUND SYSTEM SERVICES

9.1 (U) HADES IDIQ Requirements

5.3 – Ground System Services iv

UNCLASSIFIED

Ground Control Specific Requirements ............................................................ Error! Bookmark not defined.

Ground Control Specific Requirements Ground Control Specific Requirements

10. (U) SUPPORTING INFRASTRUCTURE

10.1 (U) HADES IDIQ Requirements Ground Control Specific Requirements

11. (U) SOFTWARE SUPPORT SERVICES

11.1 (U) HADES IDIQ Requirements

12. (U) OTHER ACTIVITIES

12.1 (U) HADES IDIQ Requirements Ground Control Specific Requirements ............................................................ Error! Bookmark not defined.

Ground Control Specific Requirements

13. (U) SPECIAL STUDIES AND RECOMMENDATIONS

13.1 (U) HADES IDIQ Requirements Ground Control Specific Requirements

14. (U) HARDWARE PACKAGING AND SHIPPING. ....................................... Error! Bookmark not defined.

14.1 (U) Ground Control Specific Requirements ........................................ Error! Bookmark not defined.

Tables

Table 1. (U) Ground Control PWS Meeting Participation

UNCLASSIFIED

Copy no. ____ of ____ copies

Innovation and Prototyping Division Ground

SSC/SYD89/SDG

Kirtland AFB, NM

7/24/2026

(U) Hybrid Architecture and Development for Experimental Systems

(HADES) Services

Ground Control

Performance Work Statement (PWS)

1. (U) PURPOSE AND OBJECTIVES.

1.1 (U) Purpose

This Performance Work Statement (PWS) expands upon foundational requirements established under the Hybrid

Architecture and Development for Experimental Systems (HADES) Indefinite Delivery/Indefinite Quantity (IDIQ) contract. This task order supports Space Systems Command's (SSC) Innovation and Prototyping Division Ground

(SDG) by ensuring sustainment, development, and operational readiness of Ground Control systems.

Ground Control is an integrated suite of systems, processes, and capabilities that facilitate communication between ground-based operations centers and on-orbit space vehicles. This infrastructure enables command uplink, telemetry downlink, mission scheduling, and real-time status monitoring through distributed antenna service providers.

RSC CUE & Comm (Common User Equipment and Communications) is an IL4 hybrid cloud environment that provides simultaneous multi-level mission support through access to government and commercial antenna networks while hosting black-side tools, applications, and workloads.

Ground System Enterprise (GSE) integrates multiple antenna service providers and communication systems. The primary service is the Satellite Control Network (SCN), supported by the MIDAS Automated Resource Scheduler

(MARS) Advanced Scheduling Tool (AST) for mission scheduling and coordination, and the Distributed

Communication Controller (DCC) for ground station interface management. The GSE architecture accommodates additional Government and Commercial antenna service providers.

Remote Agile Ground Equipment (RAGE) is a locally developed capability enabling Mission Test and Validation

Campaigns throughout the satellite development lifecycle, including connectivity to test facilities, integration with test equipment (RF racks, SCN test vans, or equivalent systems), and technical troubleshooting to ensure mission readiness.

Activities will primarily be conducted at the Research, Development, Test, and Evaluation (RDT&E) facility at

Kirtland Air Force Base, New Mexico, with travel to contractor facilities and mission partner locations as required.

The contractor operates as a mission partner, collaborating with Prototype Operations I (POPS-I) personnel, space vehicle contractors, antenna service providers, and external mission partners to maintain operationally ready systems aligned with rapid-fielding objectives supporting the warfighter and national defense priorities.

2. (U) OBJECTIVE.

The contractor shall provide comprehensive systems engineering, development, integration, testing, and operational support for Ground Control systems, ensuring mission readiness, technical performance, and alignment with program requirements.

Specifically, the contractor shall:

1. Provide systems engineering, development, integration, and sustainment of CUE & Comm and antenna service integration systems within the GSE architecture.

2. Deliver systems engineering, development, integration, and sustainment of test support infrastructure for space vehicle factory and launch-based testing activities.

3. Support ongoing mission integration and technical activities across all Ground Control systems, ensuring seamless functionality, interoperability, and interface compliance.

4. Maintain lifecycle sustainment support for current missions through end-of-life and for new missions as established.

5. Conduct planning, requirements analysis, procurement, development, installation, integration, testing, and operational readiness activities.

6. Antenna Service Integration Support:

o Configure and sustain MARS and DCC systems for SCN operations.

o Integrate and configure Government and Commercial antenna service providers.

o Establish, configure, and troubleshoot data transport systems and network connectivity.

o Configure antenna broker applications and local tool interfaces.

o Perform remote and on-site sustainment of patches and software upgrades.

o Maintain and upgrade supporting infrastructure.

7. Test Support Infrastructure Operations:

o Deploy, configure, and sustain RAGE and associated test equipment.

o Conduct site surveys and technical assessments at space vehicle contractor facilities and launch sites.

o Establish and teardown temporary communication circuits and test equipment interfaces.

o Troubleshoot test data streams and communication system issues.

o Provide on-site support and coordination with space vehicle contractors, launch base personnel, and communication service providers.

The contractor shall collaborate with SSC/SYD89/SDG Government personnel, POPS-I contract personnel, space vehicle contractors, antenna service providers, communication service providers, and external mission partners. All

Ground Control systems shall meet readiness, technical, performance, and security requirements outlined in this

PWS.

This task order incorporates applicable requirements from the HADES IDIQ PWS, ensuring alignment with established mission objectives and technical management processes.

3. (U) BACKGROUND.

The RSC CUE& Comm system supports simultaneous multi-level missions by providing access to various government and commercial antenna networks and hosting black-side tools, applications, and workloads. To continue to meet mission partners’ emerging requirements, SDG sustains and develops hybrid on-premises and cloud-based ground systems. 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. The Ground Control section maintains both on-premises and cloud information technology (IT) systems and performs cybersecurity compliance and integration activities that are critical to day-to-day mission execution.

4. (U) PERFORMANCE REQUIREMENTS.

This section establishes the performance requirements for Ground Control operations and support activities. These requirements build upon the foundational requirements established in the HADES IDIQ PWS and include mission-specific requirements tailored to Ground Control systems, infrastructure, and capabilities.

The contractor shall meet both the applicable HADES baseline requirements and the Ground Control-specific requirements identified in this section.

4.1 (U) Contractor Meeting Participation

The contractor shall participate in the meetings identified in Table 1, as a minimum:

UNCLASSIFIED

Table 1. (U) Ground Control PWS Meeting Participation

Meeting Title Duration (hours) Frequency

Ground Control Program Coordination 1.0 Weekly

Technical and Operations Review 1.0 Weekly

Mission Partner Coordination TBD As Required

The Government Task Order lead may adjust meeting frequencies, durations, formats, or combine meetings as appropriate based on mission needs, operational tempo, or program priorities. Additional meetings including technical working groups, integration sessions, and ad hoc coordination meetings may be required by the

Government based on mission needs, test campaign activities, or program priorities.

4.1.1 (U) Ground Control Program Coordination

The Ground Control Program Coordination meeting provides a forum for regular coordination between the contractor Task Order Manager and the Government Task Order lead. This meeting addresses program-level issues, administrative matters, schedule coordination, and action item tracking and provides a forum for rapid resolution of issues that do not require detailed technical discussion.

Topics include, but are not limited to:

• Contractor staffing and personnel matters

• Schedule updates and milestone tracking

• Action item status and resolution

• Administrative and contractual issues

• Budget and cost performance updates

• Quality control and performance issues

• Upcoming activities and resource planning

• Coordination with other RSC activities

4.1.2 (U) Technical and Operations Review

The Technical and Operations Review meeting addresses the technical and operational aspects of Ground Control systems and capabilities. This meeting covers all three Ground Control functional areas: CUE&COMM, antenna service integration, and test support operations. Relevant technical subject matter experts may be included as needed based on agenda topics

• System availability and performance metrics

• Incident reports and problem resolution status

• Maintenance activities and scheduled downtime coordination

• Hardware and software sustainment activities

• System failures and corrective actions

• Response and resolution time performance

• Development activities including software enhancements and cloud architecture solutions

• Integration activities for new capabilities or antenna service providers

• Configuration management and baseline changes

• Cybersecurity status and compliance

• Technical risks and mitigation activities

• Continuous improvement initiatives

4.1.3 (U) Mission Partner Coordination

The Mission Partner Coordination meeting provides a forum for coordination with external organizations and stakeholders involved in Ground Control activities. These meetings are scheduled as required based on active test

UNCLASSIFIED

campaigns, antenna service integration activities, or other mission needs. Participants may include space vehicle contractors, antenna service providers, communication service providers, launch base personnel, POPS-I contractors, and other mission partners as appropriate.

• Test campaign planning and execution

• Space vehicle factory testing coordination

• Launch site testing and support activities

• Antenna service integration and interface coordination

• Temporary communication circuit establishment

• Site survey planning and results

• RAGE deployment coordination

• Test equipment interface requirements

• Schedule coordination for distributed operations

• Technical interface definitions and requirements

• Issue resolution requiring multi-organizational coordination

The duration, frequency, and specific participants for Mission Partner Coordination meetings will be determined by the Government Task Order lead based on the nature and scope of the coordination required. These meetings may range from brief coordination calls to extended working sessions depending on mission needs.

5. (U) INHERITED AVAILABILITY REQUIREMENTS.

5.1 (U) Ground Control Mission Enabling Role

Ground Control provides common infrastructure on the critical path that enable satellite operations within the RSC.

Availability requirements reflect the criticality of infrastructure while acknowledging that Ground Control infrastructure often supports multiple simultaneous missions with varying criticality levels, and as such Ground

Control inherits the availability requirements of hosted missions.

6. (U) SCOPE.

The scope of this acquisition is to provide comprehensive IT and operational support for the hybrid-cloud ground control environment. This includes, but is not limited to, the management of on-premises hardware and software, private cloud resources, and the integration and orchestration of all components. The objective is to ensure a secure, reliable, and scalable ground control system that can adapt to evolving mission requirements.

6.1 (U) HADES IDIQ Requirements

The following services/actions are derived from the specific sections found within the HADES IDIQ Basic PWS as annotated by the numbering below.

▪ 3.0 – Scope

☒ 3.1 ☒ 3.2 ☒ 3.3 ☒ 3.4 ☒ 3.5 ☒ 3.6

7. (U) ACCESS TO DEPARTMENT OF THE AIR FORCE COMPUTER SYSTEMS.

7.1 (U) HADES IDIQ Requirements

The following requirements from the HADES IDIQ PWS are applicable to this effort and are derived from the specific sections annotated by the numbering below:

▪ 4.0 – Access to Department of the Air Force Computer Systems

☒ 4.1

8. (U) BASIC SERVICES.

8.1 (U) HADES IDIQ Requirements

The following requirements from the HADES IDIQ PWS are applicable to this effort and are derived from the specific sections annotated by the numbering below:

UNCLASSIFIED

5.0 – Basic Services

5.1 – Contract Transition

☒ 5.1.1 ☒ 5.1.2

5.2 – Support Services

5.2.1 – Program Management

☒ 5.2.1 ☒ 5.2.2 ☒ 5.2.1.3 ☒ 5.2.1.4 ☒ 5.2.1.5 ☒ 5.2.1.6 ☒ 5.2.1.7

☒ 5.2.1.8 ☒ 5.2.1.9 ☒ 5.2.1.10 ☒ 5.2.1.11 ☒ 5.2.1.12

Ground Control Specific Requirements:

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.2.1.13 The contractor shall provide qualified personnel whose experience, education, certifications, and training are relevant to their assigned roles. Personnel holding certifications shall maintain them in active status. Critical positions, including but not limited to the Task Order

Manager and Lead Systems Engineer, shall possess one or more industry-recognized certifications and/or demonstrate equivalent expertise through prior relevant experience.

5.2.1.14 The contractor shall ensure at least 50% of all technical staff supporting Ground Control systems have relevant associate-level certifications in a domain relevant to their job duties.

5.2.1.15 The contractor shall submit proof of certifications for proposed personnel, as required.

5.2.2 – Cost Management

☒ 5.2.2.1 ☒ 5.2.2.2 ☒ 5.2.2.3 ☒ 5.2.2.4 ☒ 5.2.2.5

5.2.3 – Information Management

☒ 5.2.3.1 ☒ 5.2.3.2 ☒ 5.2.3.3 ☒ 5.2.3.4

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.2.3.4 The contractor shall work with the Government and the Configuration Management teams to provide and track documentation for all new or updated hardware or software supporting

Ground Control systems.

5.2.3.5 The contractor shall ensure their Configuration Management databases and all related tracking information are readily available on Government-directed systems. The contractor may be required to provide data or access to databases as required by the Government.

5.2.4 – Security and Data Handling Management

☒ 5.2.4.1 ☒ 5.2.4.2 ☒ 5.2.4.3 ☒ 5.2.4.4 ☒ 5.2.4.5 ☒ 5.2.4.6 ☒ 5.2.4.7

☒ 5.2.4.8 ☒ 5.2.4.9 ☒ 5.2.4.10 ☒ 5.2.4.11 ☒ 5.2.4.12 ☒ 5.2.4.13 ☒ 5.2.4.14

☒ 5.2.4.15

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.2.4.16 The contractor shall provide management, supervision, labor, and personnel necessary to perform security escort services for uncleared and unauthorized individuals within the RSC and other designated controlled or restricted areas as required by Ground Control operations.

5.2.4.17 The contractor shall comply with DoDD 8140 certification requirements for personnel who will conduct work in cyberspace work roles supporting Ground Control systems.

UNCLASSIFIED

5.2.5 – Quality Control

☒ 5.2.5.1 ☒ 5.2.5.2 ☒ 5.2.5.3 ☒ 5.2.5.4 ☒ 5.2.5.5 ☒ 5.2.5.6

5.2.6 – Risk Management

☒ 5.2.6.1 ☒ 5.2.6.2 ☒ 5.2.6.3

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.2.6.4 The contractor shall be responsible for risk identification and mitigation associated with supporting Ground Control operations and systems.

5.2.7 – Certification and Training

☒ 5.2.7.1 ☒ 5.2.7.2 ☒ 5.2.7.3 ☒ 5.2.7.4 ☒ 5.2.7.5 ☒ 5.2.7.6 ☒ 5.2.7.7

☒ 5.2.7.8 ☒ 5.2.7.9 ☒ 5.2.7.10 ☒ 5.2.7.11

5.2.8 – Configuration Management

☒ 5.2.8.1 ☒ 5.2.8.2 ☒ 5.2.8.3 ☒ 5.2.8.4 ☒ 5.2.8.5 ☒ 5.2.8.6 ☒ 5.2.8.7

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.2.8.8 The contractor shall be responsible for configuration of any Mission-Unique Software

(MUS) scripts supporting Ground Control operations.

5.2.8.9 The contractor shall be responsible for creating, updating, or modifying MUS scripts as required for Ground Control missions.

5.2.8.10 The contractor shall be responsible for reviewing all scripts, licenses, MUS, hardware, adjacent systems, control items, and consider mission partners when assessing impact of changes to Ground Control systems.

5.2.9 – Procurement, Logistics and Lifecycle Management

☒ 5.2.9.1 ☒ 5.2.9.2 ☒ 5.2.9.3 ☒ 5.2.9.4 ☒ 5.2.9.5 ☒ 5.2.9.6

☒ 5.2.9.7 ☒ 5.2.9.8 ☒ 5.2.9.9 ☒ 5.2.9.10 ☒ 5.2.9.11 ☒ 5.2.9.12

☒ 5.2.9.13 ☒ 5.2.9.14 ☒ 5.2.9.15 ☒ 5.2.9.16 ☒ 5.2.9.17 ☒ 5.2.9.18

☒ 5.2.9.19 ☒ 5.2.9.20 ☒ 5.2.9.21 ☒ 5.2.9.22 ☒ 5.2.9.23 ☒ 5.2.9.24

☒ 5.2.9.25 ☒ 5.2.9.26 ☒ 5.2.9.27 ☒ 5.2.9.28 ☒ 5.2.9.29 ☒ 5.2.9.30

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.2.9.31 The contractor shall receive, inventory, and track all hardware materials in accordance with the HADES IDIQ PWS. The contractor shall manage the inventory of Government

Furnished Property (GFP) supporting Ground Control systems, including spares.

5.2.9.32 Ground Control system solutions must integrate with existing RDSMO architectures, networks, and interfaces.

5.2.9.33 All work must remain within the scope, funding, and authorities defined by the

Government.

5.2.9.34 The contractor must adhere to Government-approved processes for requirements development, change control, and risk management.

5.2.9.35 The contractor shall provide on-site hardware support, troubleshooting, and maintenance during normal business days and hours (Monday–Friday, 0800–1700 MST) and on-call support during non-business hours with a three-hour response threshold.

UNCLASSIFIED

5.2.9.36 The contractor shall resolve identified problems within two hours during business hours.

The contractor shall resolve identified problems within three hours during non-business hours.

5.2.9.37 The contractor shall 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 time limit to fix will not count against the contractor.

5.2.9.38 The contractor shall perform hardware sustainment, to include but not limited to, maintenance, hardware monitoring, detailed troubleshooting, fault detection, isolation, and removing and replacing failed components to restore system operations and maintain system availability.

5.2.9.39 The contractor shall de-conflict any scheduled system downtime with the Government to avoid affecting training and real-time contacts.

5.2.9.40 The contractor shall perform system rollbacks (if needed) within two hours during business hours and three hours during non-business hours.

5.2.9.41 The contractor shall finalize system documentation to reflect changes. Updates to system documentation must be incorporated into the baseline within three business days of system changes.

5.2.10 – Concept Development

☒ 5.2.10.1 ☒ 5.2.10.2 ☒ 5.2.10.3 ☒ 5.2.10.4 ☒ 5.2.10.5

9. (U) GROUND SYSTEM SERVICES.

9.1 (U) HADES IDIQ Requirements

The following requirements from the HADES IDIQ PWS are applicable to this effort and are derived from the specific sections annotated by the numbering below:

5.3 – Ground System Services

5.3.1 – Ground System Engineering and Design

☒ 5.3.1.1 ☒ 5.3.1.2 ☒ 5.3.1.3 ☒ 5.3.1.4 ☒ 5.3.1.5 ☒ 5.3.1.6 ☒ 5.3.1.7

☐ 5.3.1.8 ☒ 5.3.1.9 ☒ 5.3.1.10

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.3.1.11 The contractor shall provide software development to enhance the capabilities of the RSC CUE & COMM Ground Control system. This includes developing new applications and modernizing legacy systems to improve operational efficiency, functionality, and maintainability.

5.3.1.12 The contractor shall ensure all software code and scripts developed for

Ground Control systems is maintained in Government-approved version control repositories with appropriate documentation, branching strategies, and access controls.

5.3.2 – Ground System Development

☒ 5.3.2.1 ☒ 5.3.2.2 ☒ 5.3.2.3 ☒ 5.3.2.4 ☒ 5.3.2.5 ☒ 5.3.2.6

☒ 5.3.2.7 ☒ 5.3.2.8

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

UNCLASSIFIED

5.3.2.9 The contractor shall develop and propose cloud architecture solutions in accordance with industry best practices for emerging mission requirements specified by the Government.

Solutions shall leverage Government cloud environments and integrate with existing

Ground Control infrastructure.

5.3.3 – Ground System Integration

☒ 5.3.3.1 ☒ 5.3.3.2 ☒ 5.3.3.3 ☒ 5.3.3.4 ☒ 5.3.3.5 ☒ 5.3.3.6

☒ 5.3.3.7 ☒ 5.3.3.8 ☒ 5.3.3.9 ☒ 5.3.3.10 ☒ 5.3.3.11 ☒ 5.3.3.12

☒ 5.3.3.13 ☒ 5.3.3.14

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.3.3.15 The contractor shall provide software integration services to enhance the capabilities of the

RSC CUE & COMM Ground Control system. This includes integrating third-party software and populating or modifying configuration files to support mission requirements.

5.3.4 – Ground System Sustainment

☒ 5.3.4.1 ☒ 5.3.4.2 ☒ 5.3.4.3 ☒ 5.3.4.4 ☒ 5.3.4.5 ☒ 5.3.4.6

☒ 5.3.4.7 ☒ 5.3.4.8 ☒ 5.3.4.9

5.3.5 – Ground System Decommission, Disposal, and/or Transfer

☒ 5.3.5.1 ☒ 5.3.5.2 ☒ 5.3.5.3 ☒ 5.3.5.4 ☒ 5.3.5.5 ☒ 5.3.5.6

☒ 5.3.5.7 ☒ 5.3.5.8 ☒ 5.3.5.9

10. (U) SUPPORTING INFRASTRUCTURE.

10.1 (U) HADES IDIQ Requirements

The following requirements from the HADES IDIQ PWS are applicable to this effort and are derived from the specific sections annotated by the numbering below:

5.4 – Facility Services

5.4.1 – Power Distribution and Resiliency Support

☒ 5.4.1.1 ☒ 5.4.1.2 ☒ 5.4.1.3 ☒ 5.4.1.4 ☒ 5.4.1.5 ☒ 5.4.1.6

5.4.2 – Heating, Ventilation and Air Conditioning Support

☒ 5.4.2.1 ☒ 5.4.2.2 ☒ 5.4.2.3 ☒ 5.4.2.4 ☒ 5.4.2.5 ☒ 5.4.2.6

5.4.3 – Facility and Furniture Maintenance

☒ 5.4.3.1 ☒ 5.4.3.2 ☒ 5.4.3.3 ☒ 5.4.3.4 ☒ 5.4.3.5 ☒ 5.4.3.6

5.4.4 – Network Infrastructure Support

☒ 5.4.4.1 ☒ 5.4.4.2 ☒ 5.4.4.3 ☒ 5.4.4.4 ☒ 5.4.4.5 ☒ 5.4.4.6

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.4.4.7 The contractor shall manage the hybrid cloud environment, including the Government Cloud

(GovCloud) and on-premises infrastructure supporting Ground Control systems. This includes resource provisioning, cost management, and performance optimization.

5.4.4.8 The contractor shall manage and maintain all network connectivity between the on-premises

RSC CUE & COMM and the cloud environments. This includes, but is not limited to, Virtual Private Networks (VPNs) and other secure connections.

UNCLASSIFIED

5.4.4.9 The contractor shall implement and maintain a comprehensive cybersecurity program for

RSC CUE & COMM Ground Control in accordance with DoD and Space Force Defensive

Cyber Operations policy and directives.

5.4.4.10 The contractor shall manage firewalls, intrusion detection/prevention systems (IDS/IPS) such as Amazon GuardDuty to ensure compliance with all relevant security regulations and authorization requirements.

5.4.4.11 The contractor shall manage and protect all data generated and processed by Ground Control systems. This includes data backup, disaster recovery, and ensuring data integrity and availability across the hybrid environment.

5.4.4.12 The contractor shall create contingency plans for Government approval to ensure that in the event of natural disaster or other crisis event, Ground Control system data remains intact and accessible.

5.4.5 – Space Optimization Layout

☒ 5.4.5.1 ☒ 5.4.5.2 ☒ 5.4.5.3 ☒ 5.4.5.4 ☒ 5.4.5.5 ☒ 5.4.5.6

11. (U) SOFTWARE SUPPORT SERVICES.

11.1 (U) HADES IDIQ Requirements

The following requirements from the HADES IDIQ PWS are applicable to this effort and are derived from the specific sections annotated by the numbering below:

5.5 – Software Support Services

5.5.1 – Software Setup

☒ 5.5.1.1 ☒ 5.5.1.2 ☒ 5.5.1.3 ☒ 5.5.1.4

5.5.2 – Software Development

☒ 5.5.2.1 ☒ 5.5.2.2 ☒ 5.5.2.3 ☒ 5.5.2.4 ☒ 5.5.2.5 ☒ 5.5.2.6

☒ 5.5.2.7 ☒ 5.5.2.8

5.5.3 – Software Configuration

☒ 5.5.3.1 ☒ 5.5.3.2 ☒ 5.5.3.3

12. (U) OTHER ACTIVITIES.

This section establishes specialized security and cybersecurity requirements for Ground Control operations, including Communications Security (COMSEC), cybersecurity authorization support (ATO/ATC/IATT), and

Defensive Cybersecurity Operations (DCO).

12.1 (U) HADES IDIQ Requirements

The following requirements from the HADES IDIQ PWS are applicable to this effort and are derived from the specific sections annotated by the numbering below:

5.6 – Other Activities

5.6.1 –Communication Security (COMSEC) and Cryptographic Support

☒ 5.6.1.1 ☒ 5.6.1.2 ☒ 5.6.1.3 ☒ 5.6.1.4 ☒ 5.6.1.5 ☒ 5.6.1.6

☒ 5.6.1.7 ☒ 5.6.1.8 ☒ 5.6.1.9 ☒ 5.6.1.10 ☒ 5.6.1.11 ☒ 5.6.1.12

☒ 5.6.1.13

5.6.2 – Cybersecurity

☒ 5.6.2.1 ☒ 5.6.2.2 ☒ 5.6.2.3 ☒ 5.6.2.4 ☒ 5.6.2.5 ☒ 5.6.2.6

☒ 5.6.2.7 ☒ 5.6.2.8 ☒ 5.6.2.9

5.6.3 – Defensive Cybersecurity Operations (DCO)

☒ 5.6.3.1 ☒ 5.6.3.2 ☒ 5.6.3.3 ☒ 5.6.3.4

UNCLASSIFIED

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.6.3.5 The contractor shall implement and maintain DCO capabilities for Ground Control systems including, but not limited to, continuous monitoring, threat detection, vulnerability scanning, and incident response in accordance with DoD and Space Force

DCO policies.

13. (U) SPECIAL STUDIES AND RECOMMENDATIONS.

The contractor shall conduct special studies and analyses to support continuous improvement of Ground Control systems and capabilities. These studies provide the Government with independent assessments of current system performance, identification of improvement opportunities, and development of alternative courses of action to enhance operational effectiveness, reduce costs, or address emerging requirements.

13.1 (U) HADES IDIQ Requirements

The following requirements from the HADES IDIQ PWS are applicable to this effort:

5.7 – Special Studies and Recommendations

☒ 5.7.1 ☒ 5.7.2 ☒ 5.7.3 ☒ 5.7.4 ☒ 5.7.5

Ground Control Specific Requirements

The following mission-specific requirements supplement the HADES IDIQ baseline requirements and continue the HADES numbering sequence to maintain traceability.

5.7.6 Upon Government request, the contractor shall conduct special studies on Ground Control system capabilities, architecture, performance, and infrastructure. Studies shall assess current state, identify deficiencies or improvement opportunities, and provide no fewer than three

Courses of Action (COAs) for system improvements, enhancements, or architectural changes.

Each COA shall include technical feasibility assessment, risk analysis, benefits analysis, implementation approach, milestone schedule, and Rough Order of Magnitude (ROM) cost estimate to enable Government decision-making.

APPENDIX A – (U) ABBREVIATIONS AND ACRONYMS.

AST – Advanced Scheduling Tool

ATC – Authorization to Connect

ATO – Authorization to Operate

CCB – Change Control Board

COA – Course of Action

COMSEC – Communications Security

CONOPS – Concept of Operations

CUE & Comm – Common User Equipment and Communications

DCC – Distributed Communication Controller

DCO – Defensive Cybersecurity Operations

DoD – Department of Defense

DoDD – Department of Defense Directive

ERB – Engineering Review Board

ESD – Electronic Scheduling and Dissemination

FTE – Full Time Equivalent

GFP – Government Furnished Property

GSE – Ground System Enterprise

HADES – Hybrid Architecture and Development for Experimental Systems

HVAC – Heating, Ventilation and Air Conditioning

IA – Information Assurance

IATT – Interim Authority to Test

IDIQ – Indefinite Delivery Indefinite Quantity

IDS/IPS – Intrusion Detection/Prevention Systems

IL4 – Impact Level 4

IT – Information Technology

KAFB – Kirtland Air Force Base

MARS – MIDA Automated Resource Scheduler

MST – Mountain Standard Time

MUS – Mission Unique Software

OAT – Operational Assessment Test

POPS-I – Prototype Operations I

PWS – Performance Work Statement

RAGE – Remote Agile Ground Equipment

RDT&E – Research, Development, Test, and Evaluation

RF – Radio Frequency

RMA – Return Merchandise Authorization

ROM – Rough Order of Magnitude

RSC – Research, Development, Test, and Evaluation Support Complex

RVDS – Rendezvous and Proximity Video Distribution System

SCN – Satellite Control Network

SD – Innovation and Prototyping Delta

SDG – Innovation and Prototyping Division Ground

SMP – Symmetric Multiprocessing

SSC – Space Systems Command

SV – Space Vehicle

SYD89 – Systems Delta 89

TO – Task Order

VPN – Virtual Private Network

This Page is Intentionally Left Blank