(U) 04. Jaguar_PWS_v4.0_20260901.pdf

UNCLASSIFIED

HYBRID ARCHITECTURE AND DEVELOPMENT FOR

EXPERIMENTAL SYSTEMS (HADES) SERVICES

JAGUAR

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 1/15/2026 1.0 Initial Jaguar PWS

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

3 2/10/2026 3.0 Aerospace revision, Jaguar PWS

4 4/20/2026 3.1 Aerospace revision, Jaguar PWS

5 7/24/2026 3.8 Aerospace revision, Jaguar PWS w/Gov Input -

Done

Innovation and Prototyping Division Ground

SSC/SYD89/SDG

Kirtland AFB, NM

7/24/2026

(U) Hybrid Architecture and Development for Experimental Systems

(HADES) Services

Jaguar

Performance Work Statement (PWS)

(U) Contents

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

1. (U) PURPOSE AND OBJECTIVES

1.1 (U) Purpose

1.2 (U) Objective

2. (U) BACKGROUND AND ASSUMPTIONS

2.1 (U) Background

2.2 (U) Assumptions

2.3 (U) Personal Security Requirements

2.4 (U) Facilities and Equipment Access

2.5 (U) Contractor Oversight and Management

2.6 (U) Government Oversight and Direction

2.7 (U) Travel Requirements

3. (U) PERFORMANCE REQUIREMENTS

3.1 (U) Base Effort and Options

3.2 (U) System Sustainment Responsibilities

3.3 (U) Hardware Support for Compunetix Systems

3.4 (U) Installation Support for Compunetix Systems

3.5 (U) Compunetix Support and Compunetix Depot Support

3.6 (U) Procurement of Hardware and Software

3.7 (U) Customer Support Activities

3.8 (U) Hardware Storage and Accountability

3.9 (U) Compunetix Equipment Accountability

3.10 (U) POC Hardware Sustainment and Refresh

3.11 (U) On-Site Support Requirements and Activities

3.12 (U) On-Call Support Requirements and Activities

3.13 (U) Contractor Meeting Participation

4. (U) SYSTEM AVAILABILITY REQUIREMENTS

4.1 (U) System Availability Standards

4.2 (U) System Availability Further Defined

4.3 (U) Response Time to System Failures

4.4 (U) Reporting Requirements

5. (U) SCOPE

5.1 (U) HADES IDIQ Requirements

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

5.2 (U) HADES IDIQ Requirements

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

6. (U) BASIC SERVICES

6.1 (U) HADES IDIQ Requirements

▪ 5.0 – Basic Services

▪ 5.1 – Contract Transition

▪ 5.2 – Support Services

▪ 5.2.1 – Program Management

▪ 5.2.2 – Cost Management

▪ 5.2.3 – Information Management

▪ 5.2.4 – Security and Data Handling

▪ 5.2.5 – Quality Control

▪ 5.2.6 – Risk Management

▪ 5.2.7 – Certification and Training

▪ 5.2.8 – Configuration Management

▪ 5.2.9 – Procurement, Logistics and Lifecycle Management

▪ 5.2.10 – Concept Development

7. (U) GROUND SYSTEM SERVICES

7.1 (U) HADES IDIQ Requirements

▪ 5.3 – Ground System Services

▪ 5.3.1 – Ground System Engineering and Design

▪ 5.3.2 – Ground System Development

▪ 5.3.3 – Ground System Integration

▪ 5.3.4 – Ground System Sustainment

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

8. (U) GROUND TERMINAL SUPPORT SERVICES

8.1 (U) Remote Support Requirements

8.2 (U) In-Person (On-Site) Support Requirements

8.3 (U) Oversight and Level of Effort

9. (U) OPERATIONAL SUPPORT

9.1 (U) Comprehensive System Support

9.2 (U) Ground System Sustainment

9.3 (U) Procedure Development for System Recovery

9.4 (U) Mission Capability Assurance

9.5 (U) Mission Operations Coordination

9.6 (U) Mission Database Management

9.7 (U) Compunetix, LLVD, File Share, and VPOAT Support

9.8 (U) Spares and Repair Inventory Management

10. (U) SUPPORTING INFRASTRUCTURE

10.1 (U) HADES IDIQ Requirements

▪ 5.4 – Facility Services

▪ 5.4.1 – Power Distribution and Resiliency Support

▪ 5.4.2 – Heating, Ventilation and Air Conditioning Support

▪ 5.4.3 – Facility and Furniture Maintenance

▪ 5.4.4 – Network Infrastructure Support

▪ 5.4.5 – Space Optimization Layout

11. (U) SOFTWARE SUPPORT SERVICES

11.1 (U) HADES IDIQ Requirements

▪ 5.5 – Software Support Services

▪ 5.5.1 – Software Setup

▪ 5.5.2 – Software Development

▪ 5.5.3 – Software Configuration

12. (U) OTHER ACTIVITIES

12.1 (U) HADES IDIQ Requirements

▪ 5.6 – Other Activities

▪ 5.6.1 –Communication Security (COMSEC) and Cryptographic Support

▪ 5.6.2 – Cybersecurity

▪ 5.6.3 – Defensive Cybersecurity Operations (DCO)

12.2 (U) Special Studies and Recommendations

12.3 (U) HADES IDIQ Requirements

▪ 5.7 – Special Studies and Recommendations

12.4 (U) Hardware Packaging and Shipping

APPENDIX A – (U) ABBREVIATIONS AND ACRONYMS

Tables

Table 1. (U) Jaguar PWS Meeting Participation

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

Jaguar

Performance Work Statement (PWS)

1. (U) PURPOSE AND OBJECTIVES.

1.1 (U) Purpose

The purpose of this Performance Work Statement (PWS) is to expand upon the foundational requirements established under the Hybrid Architecture and Development for Experimental Systems (HADES) Indefinite

Delivery/Indefinite Quantity (IDIQ) contract. This supplemental effort supports the Prototype Ground Development and Sustainment Branch (SDG) by ensuring the sustainment, stability, and advancement of critical satellite ground systems and Satellite Operations Centers (SOCs).

This effort is undertaken to maintain operational readiness, enable system stability, and provide engineering, development, and integration support for prototype and operational satellite ground systems. Activities will primarily be conducted at the Research, Development, Test, and Evaluation (RDT&E) support facility (RSC) aboard

Kirtland Air Force Base, New Mexico. Additionally, occasional travel to contractor facilities, mission partner locations, or other Government-designated sites may be required for collaboration, integration testing, procurement activities, or technical coordination.

Through collaboration with key stakeholders and adherence to the principles outlined in the original HADES IDIQ contract, this initiative ensures the continued reliability and operational success of mission-critical infrastructure.

This effort directly supports the organization’s mission to deliver innovative, cost-effective, and effective space-based capabilities aligned with national defense objectives.

1.2 (U) Objective

The objective of this PWS is to ensure the effective support, sustainment, and development of the Jaguar mission through the delivery of high-quality services and technical expertise. The contractor will provide comprehensive engineering, development, testing, and operational support for the Jaguar ground systems, ensuring mission readiness and alignment with program requirements. The contractor’s efforts will directly contribute to the sustained operational success of the Jaguar mission, supporting its goals of reliable, secure, and cost-effective satellite operations.

Specifically, the contractor shall:

1. Provide continued engineering, development, and sustainment of the Satellite Operations Center

(SOC) ground system.

2. Deliver continued engineering, development, and sustainment of the Payload Operations Center

(POC) ground system.

3. Support ongoing program test and integration activities, ensuring seamless functionality across systems.

4. Maintain continued sustainment support for external customers as required.

5. Conduct planning, procurement, development, installation, testing, and operational readiness activities for

Jaguar ground systems.

6. Execute the development and sustainment of dedicated Ground Terminals (GTs), including but not limited to Remote troubleshooting of ground terminal issues, remote application of patches and software upgrades, and maintenance and upgrades to supporting infrastructure.

The contractor will collaborate closely with stakeholders, including SSC/SYD89/SD Government personnel, the

Jaguar Program Management Office, Prototype Operations I (POPS-I) contract personnel, the Space Vehicle contractor (SV Ctr), and other future and external partners. The contractor shall ensure that the SOC and POC ground systems meet readiness requirements and satisfy all specifications outlined in this PWS.

This task order incorporates applicable requirements from the originating HADES PWS, ensuring alignment with previously established mission objectives. The contractor is responsible for meeting all clarified and specified requirements directly related to the successful execution of this effort.

2. (U) BACKGROUND AND ASSUMPTIONS.

This section provides essential context for the project or effort outlined in the Performance Work Statement (PWS).

2.1 (U) Background

The RSC serves as a multi-mission support facility that plays a critical role in enabling and sustaining the execution of high-priority space operations. As part of its mission, the RSC requires a secure, high-performance operational system to support the demands of its critical missions. These systems are foundational to maintaining the operational readiness and effectiveness of the organization’s mission portfolio.

The organization’s overarching goal is to accelerate key phases of mission operations, including mission design, ground system integration, launch and on-orbit operations, ground system testing, and the rapid deployment of fielded capabilities. These efforts are essential to ensuring reliable, low-cost access to space and directly support the warfighter’s needs. Ground support activities at the RSC encompass the maintenance of critical infrastructure, systems, information technology (IT) networks, cybersecurity measures, and integration processes, all of which are vital to the successful completion of daily mission activities.

Within this operational framework, the Jaguar mission represents a key program supported by the RSC. At present, the Jaguar mission is managed by the Jaguar Program Management Office; however, this management structure may change in the future to accommodate evolving mission requirements or organizational realignments. The contractor under this task order will assume responsibility for sustaining and maintaining the Jaguar ground system and its associated infrastructure, which are located at the SOC and the POC. The successful execution of this TO will ensure that the Jaguar mission continues to operate seamlessly within the RSC’s broader operational environment.

The Government TO lead will provide the contractor with direction, guidance, and oversight throughout the period of performance, ensuring alignment with mission objectives and compliance with all applicable standards and requirements.

2.2 (U) Assumptions

2.3 (U) Personal Security Requirements

All personnel supporting the Jaguar mission and requiring access to the POC must hold a Top Secret clearance with

Sensitive Compartmented Information (SCI) eligibility. The contractor must ensure that SCI clearance is obtained for applicable personnel within 120 days of their hiring date. Exceptions to this requirement for support personnel in non-critical roles, such as logistics, finance, or scheduling, will be reviewed and approved on a case-by-case basis through coordination between the Government and the contractor. The contractor assumes full financial responsibility for obtaining all required security clearances and SCI eligibility for their personnel.

2.4 (U) Facilities and Equipment Access

The Jaguar mission operates within the RSC and occupies Payload Test Centers 2, 3, and 4, collectively referred to as the POC. The POC houses all mission-critical equipment necessary for the Jaguar mission, to include The POC houses the Black Ground Configuration Controller (GCC), Red GCC, and GUTS and EC2K MMSOC Merged

Architecture (GEMMA). Contractor personnel will be required to work onsite as needed to fulfill mission objectives and ensure uninterrupted operational support for the Jaguar ground system and infrastructure.

2.5 (U) Contractor Oversight and Management

To ensure the effective execution of this PWS, the contractor will appoint a dedicated Task Order Manager. This individual will serve as the primary interface with the Government team, facilitating communication, coordination, and the successful completion of all assigned tasks and deliverables.

2.6 (U) Government Oversight and Direction

Throughout the period of performance, the Government Task Order (TO) lead will provide oversight and guidance to the contractor. This includes providing clarifications, approving key deliverables, and addressing any changes to the scope of work or operational priorities

2.7 (U) Travel Requirements

The personnel may be required to travel to meet mission objectives (CONUS and OCONUS). Travel is estimated to be less than five days per quarter. All travel arrangements and associated requirements will be coordinated with the

Government to ensure alignment with mission needs and cost-effectiveness.

3. (U) PERFORMANCE REQUIREMENTS.

3.1 (U) Base Effort and Options

The base effort and options include engineering, development, and sustainment of the Payload Operations Center

(POC) and Satellite Operations Center (SOC) ground systems. These tasks include, but are not limited to:

• Management, sustainment and development of the GCC

• Management and sustainment of GEMMA

• Architecture supporting spacecraft bus and payload TT&C (MUS software).

o Limited to HW infrastructure, front end processors, crypto devices, network equipment, high speed guard (HSG), and any other peripheral equipment necessary to conduct satellite bus

Telemetry, Tracking, and Commanding (TT&C) operations o May require government delivery of TT&C SW and/or MUS.

• Sustainment of hardware and software supporting vehicle operations.

• Management and sustainment of the Compunetix phone system.

• Limited support for the Alternate Ground Terminal (AGT) and dedicated Ground Terminals (GTs).

3.2 (U) System Sustainment Responsibilities

The contractor shall support the following for all assets accepted by the Government for sustainment:

• Perform continual Information System Security Engineer (ISSE) work.

• Conduct single point of failure analysis.

• Drive automation efforts to improve operational efficiency.

• Execute continuous improvement efforts for all supported systems.

3.3 (U) Hardware Support for Compunetix Systems

The contractor shall provide hardware support for Compunetix system integration.

3.4 (U) Installation Support for Compunetix Systems

The contractor shall create installation instructions for Compunetix systems to support required functionality. The contractor is not expected to provide infrastructure support, materials, or personnel for installations at locations outside the POC.

3.5 (U) Compunetix Support and Compunetix Depot Support

The contractor shall provide depot support for the Compunetix phone system during normal business hours at the

POC (0800–1600 MST).contractor shall provide hardware support for Compunetix system integration.

3.6 (U) Procurement of Hardware and Software

The contractor shall procure all Jaguar hardware and software in accordance with a Government-approved Bill of

Materials (BOM), subject to approval by the Government Mission Manager.

3.7 (U) Customer Support Activities

The contractor shall provide on-location and over-the-phone support for external customers as required for all hardware, network, and software within the POC.

3.8 (U) Hardware Storage and Accountability

The contractor shall:

• Manage the storage and accountability of hardware components for the Jaguar mission on Kirtland Air

Force Base (RSC and MRF).

• Assist appropriate Government representatives with shipping components to other CONUS or OCONUS locations as directed.

3.9 (U) Compunetix Equipment Accountability

The contractor shall manage the accountability of Compunetix equipment under its responsibility. For equipment shipped to geographically separated locations, documentation shall be maintained using a signed DD Form 1149.

3.10 (U) POC Hardware Sustainment and Refresh

The contractor shall:

• Sustain hardware and infrastructure for PTC 2, 3, and 4.

• Perform technical refreshes as needed.

• Procure hardware, software, and peripherals necessary to meet all security standards, Authorization to

Operate (ATO) requirements, and Sensitive Compartmented Information Facility (SCIF) requirements.

• Provide escorts and coordinate with the Government to ensure escort requirements do not delay scheduled work.

3.11 (U) On-Site Support Requirements and Activities

At contract award, the contractor shall provide on-site support as follows:

• System Administrators shall be on-site 16 hours per day, 5 days per week (16x5).

• All other functions shall be supported on-site during core business hours, 8 hours per day, 5 days per week

(8x5).

3.12 (U) On-Call Support Requirements and Activities

The contractor shall provide 24x7 on-call support with a 2-hour response time.

3.13 (U) Contractor Meeting Participation

The contractor shall participate in the following meetings, as a minimum:

Table 1. (U) Jaguar PWS Meeting Participation

Meeting Title Duration (hours) Frequency

Contractor/Government Tag-up 1.0 Weekly

Operations and Sustainment Tag-up 1.0 Weekly

Integrated Product Team (IPT) Tag-up 1.5 Weekly

Program Office Update 1.5 Weekly

External Customer Update 1.5 Weekly

4. (U) SYSTEM AVAILABILITY REQUIREMENTS.

4.1 (U) System Availability Standards

1. The Payload Operations Center (POC) ground systems shall maintain an availability of at least 99% within any sliding 30-day period.

2. The Satellite Operations Center (SOC) ground systems shall maintain an availability of at least 95% within any sliding 30-day period.

3. Downtime required for Jaguar-specific Preventive Maintenance Inspections (PMIs), installations, and other

Government-approved events shall not count against the system availability requirements.

4.2 (U) System Availability Further Defined

System availability is defined as follows:

1. Unscheduled Downtime: Any unscheduled downtime or other downtime that did not have pre-coordinated

Government approval will count against the 99% POC availability requirement and the 95% SOC availability requirement.

2. SOC Availability Metrics: Availability metrics for the SOC ground system shall include all required and scheduled Space Communications Network (SCN) and dedicated antenna contacts.

3. POC Availability Metrics: Availability metrics for the POC ground systems shall include all required and scheduled payload operations.

4.3 (U) Response Time to System Failures

The contractor shall respond to any system failure within 2 hours of notification.

4.4 (U) Reporting Requirements

The contractor shall provide the following system availability reports:

1. Weekly System Availability Reports: These reports shall include calculated system availability metrics for the preceding week, with and without PMI downtime.

2. Monthly System Availability Reports: These reports shall include calculated system availability metrics for the preceding month, with and without PMI downtime.

5. (U) SCOPE.

5.1 (U) HADES IDIQ Requirements

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

▪ 3.0 – Scope

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

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

5.2 (U) HADES IDIQ Requirements

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

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

☒ 4.1

6. (U) BASIC SERVICES.

6.1 (U) HADES IDIQ Requirements

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

▪ 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.1 ☒ 5.2.1.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

▪ 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

▪ 5.2.4 – Security and Data Handling

☒ 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

▪ 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

▪ 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

▪ 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

▪ 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

7. (U) GROUND SYSTEM SERVICES.

7.1 (U) HADES IDIQ Requirements

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

▪ 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

▪ 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

▪ 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

▪ 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

8. (U) GROUND TERMINAL SUPPORT SERVICES

This section outlines the contractor's responsibilities for providing remote and, when necessary, in-person support for Ground Terminals (GTs) and Alternate Ground Terminals (AGTs). The contractor shall ensure effective troubleshooting, maintenance, and configuration management to sustain the operational readiness of all supported systems.

8.1 (U) Remote Support Requirements

The contractor shall provide remote support from Kirtland Air Force Base (AFB) to assist with troubleshooting and the maintenance of all OCONUS GTs and AGTs. This support shall include, but is not limited to, the following tasks:

1. Provide government-approved logs and screenshots as needed for system diagnostics and troubleshooting.

2. Implement government-approved configuration changes to address system requirements or resolve issues.

3. Install government-approved software and apply patch updates to ensure systems remain secure and operational.

4. Perform government-approved account management tasks and network maintenance to ensure system integrity and availability.

5. Provide necessary inputs and products to the government for configuration management or procurement consideration.

6. Deliver remote preventive and corrective maintenance to address potential or existing system issues.

8.2 (U) In-Person (On-Site) Support Requirements

The contractor shall provide in-person support on a case-by-case basis for special circumstances. In such instances, the Government Task Order (TO) lead will coordinate and approve the requirements for in-person support.

8.3 (U) Oversight and Level of Effort

The contractor’s level of effort for GT and AGT support shall be monitored and scrutinized by the Government TO lead to ensure it aligns with the objectives of this PWS and remains consistent with mission priorities.

9. (U) OPERATIONAL SUPPORT

This section outlines the contractor's responsibilities for providing remote and, when necessary, in-person support for Ground Terminals (GTs) and Alternate Ground Terminals (AGTs). The contractor shall ensure effective troubleshooting, maintenance, and configuration management to sustain the operational readiness of all supported systems.

9.1 (U) Comprehensive System Support

The contractor shall provide Hardware, Software, System Administration, Network Engineering, and COMSEC support to ensure the continued operational functionality of the Jaguar systems.

• All hardware and software purchases must receive prior approval from the Government before procurement.

• Contractor personnel across all functional groups may be required to provide off-hours support on a case-by-case basis, as determined by the Government.

9.2 (U) Ground System Sustainment

The contractor shall maintain and sustain the SOC and POC ground systems and associated subsystems required to support the Jaguar mission.

• This includes sustainment support for mission-unique hardware and software specific to Jaguar operations.

9.3 (U) Procedure Development for System Recovery

The contractor shall develop procedures to assist in recovering from:

• Ground system maintenance activities.

• System anomalies.

• Pre- and post-high-tempo operational events.

9.4 (U) Mission Capability Assurance

The contractor shall ensure all Jaguar SOC and POC ground system infrastructure is mission-capable and ready to support operational crews in the preparation and execution of development, testing, verification, validation, and operational events.

9.5 (U) Mission Operations Coordination

The contractor shall coordinate with operations teams to execute all required pre- and post-activities for development, testing, verification, validation, and high-tempo operational events. This coordination ensures all operational requirements are met in a timely and effective manner.

9.6 (U) Mission Database Management

The contractor shall verify and ensure that all mission databases are in an optimal state, redundant and synchronized to maintain data redundancy.

The contractor shall develop and update procedures to enable seamless transitions between operational domains with minimal downtime.

The contractor shall ensure procedures account for any updates or changes to the Cross Domain Solution

(CDS) required for successful domain switching.

9.7 (U) Compunetix, LLVD, File Share, and VPOAT Support

The contractor shall provide over-the-phone support during core business hours for the following systems:

1. Compunetix phone system

2. Long Line Video Distribution (LLVD)

3. File Share systems

4. Virtual Private Operations Access Terminal (VPOAT)

If the issue cannot be resolved over the phone, the contractor shall:

1. Arrange for the equipment to be shipped back for inspection or repair using on-hand spares.

2. Consult with Compunetix or other software support teams when required to resolve issues beyond contractor capabilities.

9.8 (U) Spares and Repair Inventory Management

The contractor shall maintain a complete inventory of spares and repair equipment for the Compunetix system. This includes conducting regular audits of the inventory to ensure accuracy and readiness for operational needs.

10. (U) SUPPORTING INFRASTRUCTURE.

10.1 (U) HADES IDIQ Requirements

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

▪ 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

▪ 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:

▪ 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 outlines additional requirements applicable to this effort. These activities supplement the primary responsibilities and ensure comprehensive operational and sustainment support for the Jaguar mission.

12.1 (U) HADES IDIQ Requirements

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

▪ 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

12.2 (U) Special Studies and Recommendations

The contractor shall conduct special studies and analyses to support continuous improvement of Jaguar 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.

12.2.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

▪ Jaguar 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 Jaguar 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.

12.3 (U) Hardware Packaging and Shipping

The contractor shall package, and ship hardware as required to support sustainment activities for the SOC, POC, Compunetix systems, and GT systems. The contractor’s responsibilities include:

1. Managing shipments for return merchandise authorizations (RMAs) with vendors.

2. Shipping and receiving spare depot parts to support sustainment activities.

3. Transferring OCONUS shipments to a government-designated party. The contractor shall not directly ship hardware to OCONUS locations without Government direction.

All shipping and receiving activities must align with Government-approved processes and timelines to ensure minimal disruption to sustainment operations.

APPENDIX A – (U) ABBREVIATIONS AND ACRONYMS.

AFB – Air Force Base

AGT – Alternate Ground Terminal

ATO – Authorization to Operate

BOM – Bill of Materials

CCB – Change Control Board

CDS – Cross Domain Solution

COMSEC – Communications Security

CONOPS – Concept of Operations

CONUS – Continental United States

Ctr – Contractor

DCO – Defensive Cybersecurity Operations

DD – Department of Defense (Form)

DoD – Department of Defense

DoDD – Department of Defense Directive

ERB – Engineering Review Board

FTE – Full Time Equivalent

GCC – Ground Configuration Controller

GEMMA – GUTS and EC2K MMSOC Merged Architecture

GFP – Government Furnished Property

GT – Ground Terminal

HADES – Hybrid Architecture and Development for Experimental Systems

HSG – High Speed Guard

HVAC – Heating, Ventilation and Air Conditioning

IA – Information Assurance

IDIQ – Indefinite Delivery Indefinite Quantity

IPT – Integrated Product Team

ISSE – Information System Security Engineer

IT – Information Technology

KAFB – Kirtland Air Force Base

LLVD – Long Line Video Distribution

MRF – Mission Readiness Facility

MST – Mountain Standard Time

MUS – Mission Unique Software

OAT – Operational Assessment Test

OCONUS – Outside Continental United States

PMI – Preventive Maintenance Inspection

POC – Payload Operations Center

POPS-I – Prototype Operations I

PTC – Payload Test Center

PWS – Performance Work Statement

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

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 – Space Communications Network

SCI – Sensitive Compartmented Information

SCIF – Sensitive Compartmented Information Facility

SD – Innovation and Prototyping Delta

SDG – Innovation and Prototyping Division Ground

SMP – Symmetric Multiprocessing

SOC – Satellite Operations Center

SSC – Space Systems Command

SV – Space Vehicle

SYD89 – Systems Delta 89

TO – Task Order

TT&C – Telemetry, Tracking, and Commanding

VPOAT – Virtual Private Operations Access Terminal

This Page is Intentionally Left Blank