UNCLASSIFIED

HYBRID ARCHITECTURE AND DEVELOPMENT FOR

EXPERIMENTAL SYSTEMS (HADES) SERVICES

FUTURE GROUND SYSTEM DEVELOPMENT

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.

Revision History

Revision Date Version Description

1 7/21/2026 1.0 Initial Draft PWS

2 7/31/2026 2.0 Revised Draft PWS, updated IDIQ numbers

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 Support

Performance Work Statement (PWS)

(U) Contents

(U) Contents

1 OBJECTIVE

2 BACKGROUND

3 TASKS

3.1 Architecture Design and Requirements Development

3.2 System Development and Integration

3.3 Cybersecurity Implementation

3.4 Test and Evaluation

3.5 Documentation and Training

4 Deliverables 5 Technical Needs

5.1 Architecture

5.2 Availability

5.3 Multi-Mission Command and Control

5.4 Data Distribution

5.5 Cybersecurity

1 OBJECTIVE.

This Performance Work Statement is not intended to be awarded but give the Offeror the opportunity to describe how they would design the future ground system for the RSC that will provide a single, flexible, multi-mission, multi-classification system for flying Research and Development satellites.

This Performance Work Statement (PWS) supplements the originating Hybrid Architecture and Development for Experimental Systems (HADES) Indefinite Delivery/Indefinite Quantity (IDIQ) PWS, specifically expanding on the Space Systems Command (SSC), Systems Delta 89 (SYD89), Innovation and Prototyping Delta (SD), Prototype Ground Development and Sustainment Branch's (SDG) requirements for system sustainment and maintaining system stability.

The HADES contract is a procurement for prototype and operational satellite ground systems, satellite operations centers (SOCs), and support services. 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 satellite ground system and satellite operations center engineering, development, integration, and sustainment, and associated support services primarily at the Research, Development, Test, and Evaluation (RDT&E) Support Complex (RSC) located at Kirtland, Air Force Base in New Mexico.

Research, Development, Test, and Evaluation facility and may include occasional travel to contractor facilities for collaboration and integration testing.

2 BACKGROUND.

The purpose of this Task Order (TO) is to develop a new future ground system for the RSC. The goal of this system is to implement a single, flexible multi-mission, multi-classification ground system baseline.

The Contractor shall design, develop, integrate, test, and deploy a future-focused functional ground system for the RSC that supports efficient mission onboarding, multi-mission operations, multi-classification, and mission transition capabilities. The architecture shall be operational for missions beginning in 2028 and beyond, with design and development commencing in the second half of FY27.

This effort encompasses infrastructure, platform, common services, and integration frameworks necessary to support space-based prototype missions.

The applicable IDIQ PWS elements are all those elements that pertain to the design, development, integration and sustainment of the RSC ground system (IDIQ PWS 5.3.1 – 5.3.3, 5.5). The scope is limited to prototyping and R&D mission support and does not include enterprise operational systems, data exploitation/processing, or RF chain components (architecture interfaces at antenna network boundaries).

The Contractor shall be responsible for cybersecurity compliance for the ground system to include materials, and travel in support of the ground systems.

3 TASKS.

3.1 Architecture Design and Requirements Development

The Contractor shall:

• Refine and finalize the functional ground system architecture based on the Government-provided Future Functional Ground Architecture reference design and System Concept Document (SYSCON), incorporating feedback from meetings with government stakeholders.

• Develop detailed system requirements derived from the functional architecture and government-provided system requirements addressing infrastructure, platform, system services, mission-unique software integration, and operator interfaces.

• Create comprehensive Architecture artifacts to support architecture documentation and decision-making.

• Define interface specifications for all architectural layers including:

• Platform to Infrastructure interfaces

• Applications and Services to Platform interfaces

• Common Services interfaces

• Mission-Unique Software integration points

• External system interfaces (CUE & Comm, data distribution, remote operations)

• Develop use cases and operational scenarios covering mission onboarding, multi-mission operations, distributed operations, data distribution, mission transition, and system maintenance.

• Augment government-executed trade studies as part of design trade-offs

• Support government milestone reviews through development of review slides and required documentation.

• Define a minimum-viable product and evolutionary roadmap to meet the services included here as well as potential future needs (as proposed by Offeror)

3.2 System Development and Integration

3.2.1 Infrastructure and Platform Implementation

The Contractor shall:

• Deploy selected infrastructure solution with compute, network, and storage resources

• Implement platform services including deployment services, application hosting, DNS, and automated resource management

• Establish security services including Identity and Access Management (IdAM), encryption, monitoring, and audit logging

• Configure multi-level security architecture with appropriate enclaves and cross-domain solutions

3.2.2 Common Services Development

The Contractor shall:

• Develop or integrate Telemetry, Tracking & Command (TT&C) services

• Develop or integrate Flight Dynamics services (GMAT, STK, FreeFlyer, or equivalent)

• Develop or integrate Mission Management services

• Develop or integrate Trending and analysis services

• Develop or integrate Ground System Monitor & Control services

• Develop or integrate Antenna Interface and scheduling services

• Develop or integrate Data Services for distribution and archival

• Develop Multi-Mission Operating Status aggregation service

• Implement standardized interfaces for all common services per approved specifications

3.2.3 Integration Framework Implementation

The Contractor shall:

• Implement standard/non-proprietary data exchange services (message bus, API gateway, or approved alternative)

• Implement configuration management services

• Establish external connections framework for CUE & Comm, data distribution (Unified Data Library, Warp Core, etc), and remote operations

3.2.4 System Modes and Environments

The Contractor shall:

• Establish segregated Development, Integration & Test, Training, and Operations environments

• Implement environment promotion and deployment services between environments

• Configure resource isolation and security controls between environments and missions

• Establish segregated ground system prototyping area allowing for service and/or technology prototyping for potential deployments to system

3.3 Cybersecurity Implementation

The Contractor shall:

• Develop and implement cybersecurity controls consistent with applicable USSF security policies.

• Prepare Authority to Operate (ATO) documentation package including System Security Plan (SSP), security control implementation details, and risk assessment.

• Establish repeatable Security Impact Assessment (SIA) process for mission onboarding to existing system

ATO.

• Implement continuous monitoring, vulnerability scanning, and security patch management processes.

• Support Government through ATO assessment and accreditation process.

3.4 Test and Evaluation

The Contractor shall:

• Develop comprehensive test plans covering unit, integration, system, security, performance, and user acceptance testing.

• Conduct Factory Acceptance Testing (FAT) demonstrating all system capabilities and requirements.

• Support Government Site Acceptance Testing (SAT) at the RSC facility.

• Conduct end-to-end mission integration testing using representative mission profiles.

• Perform load testing validating multi-mission concurrent operations.

• Develop regression test suite for ongoing validation of system changes.

3.5 Documentation and Training

The Contractor shall:

• Develop comprehensive system documentation including:

o System architecture documentation o Interface Control Documents (ICDs) for all system interfaces o System Administration Guide o Mission Onboarding Guide o Operations Procedures o Configuration Management Plan o Cybersecurity documentation

• Develop and deliver training for:

o System administrators o Mission integration personnel o Operators o Cybersecurity personnel

• Conduct training sessions for Government personnel prior to system acceptance.

4 Deliverables The Contractor shall provide all artifacts pertinent to the design and development of the future ground system:

• Architecture Refinements / Views

• System Requirements Document

• Interface Control Documents – internal and external

• System Design Document

• System Administration Guide

• Mission Onboarding Guide

• Configuration Management Plan

• Test Reports (FAT, SAT, Integration)

• Milestone Review Materials

5 Technical Needs These technical needs are not intended to be a comprehensive requirements list but a basic reference for the Offeror to describe their approach and basic design concepts for a future single ground system for the RSC.

5.1 Architecture

• The system shall provide a mission-area agnostic architecture capable of supporting missions ranging from science and technology experiments to sensor missions to tactics, techniques and procedures (TTP) prototype missions.

• The system shall support mission types including multiple experiments on common satellite buses, sensor missions, and prototype missions with potential transition to operations.

• The system shall implement a loosely-coupled, layered architecture including Infrastructure, Platform, System Services, Common Mission Services, and Mission-Unique Software layers.

• The system shall allow missions to integrate at the appropriate architectural layer (Infrastructure, Platform, Services, or Application) based on mission-specific needs and existing capabilities.

• The system shall provide standardized, non-proprietary interfaces between each architectural layer to enable flexible mission integration.

5.2 Availability

• System Availability: The system shall provide a system operational availability of 97.5% for real-time satellite contact functions.

5.3 Multi-Mission Command and Control

• The system shall support concurrent command and control (C2) operations for multiple missions at varying stages of their operational lifecycle.

• The system shall provide standardized interfaces that enable common services to support multiple missions simultaneously without cross-contamination of data or commands.

• If necessary for security reasons, the system shall support tenant isolation with mission-specific security domains managed by Identity and Access Management (IdAM) services.

• The system shall enable resource health and tracking for each mission.

• The system shall detect and send alarms for resource contention issues.

• The system shall enable the reassignment and/or release of resources at the conclusion of a mission.

5.4 Data Distribution

• The system shall provide data distribution capabilities to deliver mission data products to authorized consumers both internal and external to the RSC.

• The system shall provide cross-domain solution integration points to enable secure data transfer across security boundaries when data needs to be distributed at a lower classification level than the operational enclave.

• The system shall provide audit logging and data accountability throughout the distribution chain.

5.5 Cybersecurity

• The system shall be accreditable by applicable Authorizing Officials (AOs) to operate.

• The system shall enable support to a repeatable Security Impact Assessment process to the existing

Authorization to Operation as part of mission onboarding.

• The system shall enable efficient security patching and post-patching functional assessments.

• The system shall provide regular security scanning.

• The system shall enable defensive cyber operations.