Space Force Sunsets 1970s-Era Missile Warning Satellite Constellation

TL;DR

The Space Force has formally retired the 1970s-era Defense Support Program (DSP) missile warning satellite constellation after more than 50 years of service and is transitioning to next-generation architectures. The service is fielding Next-Gen OPIR satellites in GEO and plans proliferated constellations in MEO and LEO, shifting missile-warning architecture from a legacy single-constellation model to a multi-orbit approach. This creates near- and mid-term contracting opportunities across satellite development, launch services, ground systems, and associated command-and-control and ISR integrations. The Next-Gen OPIR Polar program faces proposed cancellation and remains subject to congressional debate, which injects program risk and potential re-scoping into the acquisition timeline. Contractors should position capture teams, validate compliance posture against listed regimes, and monitor solicitations and appropriation signals tied to follow-on sensors and ground infrastructure.

Key Points

• What happened: The Space Force decommissioned the Defense Support Program (DSP) missile warning satellite constellation and is moving to Next-Gen OPIR in GEO with proliferated MEO and LEO constellations.
• Who is affected: Defense, Space Systems, Satellite Communications, Missile Defense, Launch Services, Ground Systems, Command and Control, and ISR segments; NAICS 336414, 336415, 517410, 541330, 541370, 541512, 541715, 334220, 334511; agencies DOD, Space Force, Space Systems Command; contract vehicles STARS III, ASTRO, SOSSEC, GSA (General Services Administration) Schedule 70; compliance surfaces ITAR (International Traffic in Arms Regulations), CMMC (Cybersecurity Maturity Model Certification), NIST 800-171 (NIST Special Publication 800-171), NIST 800-53, DFARS (Defense Federal Acquisition Regulation Supplement) 252.204-7012, EAR.
• Timeline: Timeline TBD pending source review.
• What contractors should do NOW: validate and document export-control and cybersecurity posture against the listed compliance surfaces; map capabilities to multi-orbit sensor, space vehicle, launch, and ground-system requirements; open capture actions against STARS III / ASTRO / SOSSEC / GSA Schedule 70 where applicable; establish monitoring for new solicitations and appropriation language; and prepare compliant proposal artifacts for rapid response.

Who Is Affected

Specific NAICS codes, agencies, and contract vehicles pending source review.

(Note: Market and compliance segments explicitly implicated in the event are listed in Key Points above and derived from the segmentation provided.)

Frequently Asked Questions

Q: What was decommissioned?

A: The Defense Support Program (DSP) missile warning satellite constellation was decommissioned after over 50 years of operation, per the event summary.

Q: What contracting opportunities will follow this transition?

A: The summary identifies opportunities in satellite development, launch services, and ground systems as the Space Force builds out multi-orbit missile warning capability. Specific solicitations, scopes, and procurement timelines are Pending source review.

Q: Is Next-Gen OPIR Polar cancelled?

A: The summary states the proposed cancellation of the Next-Gen OPIR Polar program remains under congressional debate. Final program status and funding outcomes are Pending source review.

Definitions

• Defense Support Program (DSP): A 1970s-era missile warning satellite constellation referenced as retired in the summary.
• Next-Gen OPIR: Next-Generation Overhead Persistent Infrared missile-warning satellites referenced as being fielded in GEO and planned for proliferated constellations in MEO and LEO.
• GEO / MEO / LEO: Geostationary Earth Orbit, Medium Earth Orbit, and Low Earth Orbit — orbit regimes referenced in the summary as parts of the Space Force’s multi-orbit missile-warning architecture.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Continuously monitors regulatory changes, contract vehicles, and policy shifts that drive capture opportunities.
• Cabrillo Signals Match Engine — Automatically rescoring opportunity pipelines and supplier fit when multi-orbit missile-warning architecture changes shift program priorities.
• Cabrillo Signals Intelligence Hub — Tracks affected agencies, NAICS codes, and contract vehicles; saved searches will alert when related solicitations appear on SAM.gov (System for Award Management).
• Proposal Studio (Proposal OS) — Use to generate compliant proposal content, compliance matrices, and win themes tailored to space, satellite, and ground-systems solicitations.
• Proposal Studio Workflow Tracker — Run 9-gate capture management, automated compliance routing, and audit-ready documentation for rapid-response bids.

Who to notify: Capture Manager, BD Director, Proposal Manager, CTO/Systems Engineering Lead, Export Compliance Officer, and Cybersecurity/DFARS Compliance Owner.

First 48-hour response playbook:

• Hour 0–4: Convene capture stand-up (Capture Manager leads). Configure Cabrillo Signals War Room alerts and enable relevant saved searches in Cabrillo Signals Intelligence Hub for NAICS and vehicles listed in segmentation.
• Hour 4–12: Run portfolio rescore in Cabrillo Signals Match Engine to surface highest-fit opportunities and suppliers; notify BD Director and Proposal Manager with prioritized list.
• Hour 12–24: Initiate gap assessment in Proposal Studio (Proposal OS) for compliance matrices (ITAR, CMMC, NIST 800-171/800-53, DFARS 252.204-7012, EAR); route remediation tasks via Proposal Studio Workflow Tracker.
• Hour 24–48: Finalize capture plan and bid/no-bid decisions using Proposal Studio’s decision engine; allocate technical and pricing resources, and prepare initial compliant artifacts for rapid solicitation response.

Reference materials: Winning Federal Contracts Guide (/insights/winning-federal-contracts). For compliance and CRM handling of CUI (Controlled Unclassified Information), see CMMC Compliance Guide (/insights/cmmc-compliance-guide) and CUI-Safe CRM Guide (/insights/cui-safe-crm-guide).