Space Domain Awareness

Space domain awareness (SDA) enables mission owners to detect and characterize objects, behaviors, environmental conditions, and anomalous events that may affect their space systems. When correlated with other intelligence and mission data, SDA can also support assessment of possible threats and attribution. SDA encompasses the tracking and cataloging of space objects, prediction of future object positions, monitoring of the space environment and space weather, and characterization of the capabilities and behaviors of on-orbit objects. SDA data must provide the accuracy, timeliness, coverage, and characterization needed for the mission’s defined decisions. Publicly available data may support general awareness but may be insufficient for time-sensitive conjunction, proximity, or threat assessment; appropriate government, commercial, partner, or owner-operator data should be obtained where required. SDA is generated by a diverse sensor architecture spanning terrestrial optical, infrared, and radar systems and space-based sensors including inspector satellites capable of close-approach observation. The SDA landscape is increasingly populated by national space agencies, military programs, allied partners, commercial providers, and amateur tracking communities, making the space environment progressively more transparent and creating opportunities for mission owners to leverage diverse data sources to build a more complete operational picture.

Sources

  • CCSDS 502.0-B-3 — Orbit Data Messages
  • CCSDS 503.0-B-2 — Tracking Data Message
  • CCSDS 508.0-B-1 — Conjunction Data Message
ID: CM0077
Tier: II
Onboard SV CM 
Created: 2023/04/22
Last Modified: 2026/08/06

Pre-Operations Government

Acquisition strategies for space missions should address SDA access as a mission support requirement, specifying the minimum timeliness, accuracy, and coverage needed to support the mission's defensive decision-making processes, and identifying the combination of government-operated, allied, and commercial SDA sources that will satisfy those requirements across the mission's operational orbital regime. Requirements should address the integration of SDA data into the mission's operations center, including data ingestion, correlation, and display capabilities that enable operators to assess conjunction risks, anomalous proximity approaches, and potential attack indicators within operationally meaningful response timelines. Contract language should require that SDA integration architecture be documented as a mission design deliverable, covering the data sources, update frequencies, data handling protections, and operator interface requirements for SDA products used to support mission defense. Evaluation criteria should assess offerors' proposed SDA architecture, their demonstrated access to or relationships with SDA data providers for the mission's orbital regime, and their experience integrating SDA into operational space mission defense processes. Verification should include demonstration that SDA data is being received, processed, and presented to operators within the timelines required to support defined defensive decision scenarios.

Pre-Operations Developer/Supplier

Commercial mission operators should identify SDA data sources relevant to their operational orbital regime during the mission design phase, establishing data sharing agreements with government SDA programs, commercial SSA (space situational awareness) providers, and relevant sharing communities before launch so that SDA coverage is available from the beginning of operations rather than arranged reactively following an anomaly. SDA data integration into mission operations systems should be designed to support the specific defensive use cases relevant to the mission, including conjunction assessment, anomalous approach detection, rendezvous and proximity operation (RPO) monitoring, and post-anomaly forensic analysis, with data latency, update frequency, and positional accuracy requirements defined for each use case. Missions must obtain SDA data and analysis services that meet their defined conjunction, proximity, and defensive decision requirements. These capabilities may be provided through government, commercial, partner, or mission-owned sources. Public catalog data must not be relied upon for operational decisions when its accuracy, covariance, update rate, or coverage is insufficient for the intended use. SDA data handling must account for the sensitivity of precise orbital element data, which can reveal information about spacecraft capabilities, maneuvering capacity, and operational patterns that mission owners may not want adversaries to access; data sharing agreements should include appropriate handling restrictions. Operations center software should correlate relevant SDA data from available sources while preserving source provenance, uncertainty, update time, and conflicting observations. Multi-source fusion may improve coverage or confidence, but the resulting assessment must not be assumed more accurate than the best individual source without validation.