Space Development Agency
Next-Generation Space Architecture
Request for Information
July 1, 2019
SDA requests information from industry related to satellite bus, payload, applique, and launch concepts that can contribute to an agile, responsive next-generation space architecture. SDA has developed a notional suite of capabilities, as depicted in Figure 1, to include multiple constellations (or “layers”) addressing the eight priorities listed above. Each layer provides an integral and integrated capability to the overall architecture.
The SDA’s notional architecture is predicated on the availability of a ubiquitous data and communications transport layer and assumes the use of small, mass-produced satellites (50-500 kg) and associated payload hardware and software. The SDA is considering the use of transport layer spacecraft as substrates for other layers, allowing for the integration of appropriate payloads based on each layer’s needs.
Seven layers are proposed:
- Space Transport Layer: Global, persistent, low-latency data and communications proliferated “mesh” network to provide 24×7 global communications.
- Tracking Layer: Indications, warning, targeting, and tracking of advanced missile threats.
- Custody Layer: 24×7, all-weather custody of all identified time-critical targets.
- Deterrence Layer: Space Situational Awareness (SSA) of, and rapid access to, the cislunar volume.
- Navigation Layer: Alternate Positioning, Navigation and Timing (PNT) for GPS-denied environments.
- Battle Management Layer: Distributed, artificial intelligence-enabled Battle Management Command, Control and Communications (BMC3), to include self-tasking, self-prioritization (for collection), on-board processing, and dissemination, supporting delivery of perishable space sensor-derived data products directly to tactical users.
- Support Layer: Mass-producible ground command and control capabilities, user terminals, and rapid-response launch services (small- to medium-class).
Proposed concepts should align to one or more of the layers described above. SDA prefers comprehensive solutions that include open architectures (e.g., buses that support multiple payloads and software appliques, and payloads/software capable of integration aboard multiple buses) and leverage commercial capabilities, existing or planned.