SDA hopes to keep certain decision-making authorities as Congress weighs its future

TL;DR

Congress is considering provisions in the FY2027 NDAA (National Defense Authorization Act) that would dissolve the Space Development Agency (SDA) and transfer its authorities to the Space Force's portfolio acquisition executives. The SDA director has warned that losing SDA's unique hiring, classification, and contracting authorities could undermine the rapid-acquisition posture that enabled programs such as the Proliferated Warfighter Space Architecture (PWSA). If enacted, the reorganization could change contracting decision speed, points of contact, and the structure or use of existing contract vehicles supporting SDA efforts. Contractors working on PWSA and other SDA programs should treat this as a high-severity procurement and program risk event: expect shifts in who awards and manages work and the potential for realigned vehicle use and capture approaches. Immediate actions are inventorying affected contracts/vehicles, validating compliance posture, and preparing capture/proposal adjustments tied to potential Space Force acquisition authorities.

Key Points

• What happened: Congress is considering provisions in the FY2027 NDAA to dissolve the Space Development Agency (SDA) and transfer its authorities to the Space Force's portfolio acquisition executives, and the SDA director has raised concerns about losing authorities that enable rapid acquisition.
• Who is affected: NAICS 336414, 336415, 541330, 541512, 541513, 541715, 334220, 334511, 517410, 541370; agencies: DOD, Space Development Agency, Space Force, Space Systems Command; contract vehicles: IDIQ (Indefinite Delivery/Indefinite Quantity) contracts under SDA, Space Enterprise Consortium (SpEC), STRATFI, Rapid Resilient Command and Control (R2C2), Tranche contracts; market segments and compliance surfaces listed in segmentation.
• Timeline: Congress is considering provisions in the FY2027 NDAA; further timeline details TBD pending source review.
• What contractors should do NOW: inventory all SDA-related contracts and task orders; map each to listed contract vehicles; validate compliance posture against CMMC (Cybersecurity Maturity Model Certification), NIST 800-171 (NIST Special Publication 800-171), ITAR (International Traffic in Arms Regulations), DFARS (Defense Federal Acquisition Regulation Supplement) and other listed regimes; notify capture/proposal, contracts, program management, and security leads; update win strategies and bid/no-bid decisions assuming potential transfer of authorities to Space Force acquisition executives.

Who Is Affected

Contractors working in the Space and Defense market segments who support SDA programs are directly exposed. Explicitly named affected items from the segmentation include:

• NAICS codes: 336414, 336415, 541330, 541512, 541513, 541715, 334220, 334511, 517410, 541370.
• Agencies: DOD; Space Development Agency; Space Force; Space Systems Command.
• Contract vehicles: IDIQ contracts under SDA; Space Enterprise Consortium (SpEC); STRATFI; Rapid Resilient Command and Control (R2C2); Tranche contracts.
• Market segments: Space Systems; Defense; Satellite Communications; Space-based Sensors; Missile Warning/Tracking; Command and Control Systems; Proliferated LEO Constellation; Space Architecture; Rapid Acquisition.
• Compliance surfaces: CMMC; NIST 800-171; ITAR; DFARS; Export Control; Classified Information Handling.

Frequently Asked Questions

Q: Will the SDA be dissolved immediately?

A: Pending source review. The Summary states Congress is considering provisions in the FY2027 NDAA that would dissolve the SDA and transfer authorities; it does not indicate an enacted or immediate change.

Q: How will ongoing SDA contracts be affected operationally?

A: The Summary indicates potential impacts to decision-making speed, contract vehicles, and organizational points of contact. Specific operational effects (e.g., novation, task-order administration changes) are pending source review.

Q: What should capture and proposal teams prioritize this week?

A: Prioritize an SDA-focused contract inventory and vehicle mapping; run a compliance gap assessment against CMMC, NIST 800-171, ITAR, DFARS and classified-handling requirements; update bid/no-bid decisions and capture plans assuming acquisition authority could shift to Space Force portfolio acquisition executives. Engage internal contracts and security leads to prepare for potential changes in award authority and POC alignment.

Definitions

• Space Development Agency (SDA): The agency named in the Title and Summary under consideration for transfer/dissolution per FY2027 NDAA provisions.
• FY2027 NDAA: The fiscal year 2027 National Defense Authorization Act referenced as the legislative vehicle under which Congress is considering provisions affecting SDA.
• Space Force's portfolio acquisition executives: The acquisition authorities within the Space Force to whom SDA authorities would be transferred if provisions are enacted.
• Proliferated Warfighter Space Architecture (PWSA): An SDA program identified in the Summary as potentially impacted by the proposed reorganization.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Continuously monitors regulatory changes, contract vehicles, and policy shifts; immediate alerting on legislative language changes and public statements.
• Cabrillo Signals Match Engine — Rescores opportunity pipelines and reprioritizes opportunities tied to SDA, PWSA, and named contract vehicles when policy signals trigger change.
• Cabrillo Signals Intelligence Hub — Tracks affected agencies, NAICS codes, and contract vehicles. Saved searches and SAM.gov (System for Award Management) watchlists specific to SDA and listed vehicles will generate alerts when follow-on solicitations or administrative actions appear.
• Proposal Studio (Proposal OS) & Proposal Studio Workflow Tracker — Use Proposal OS to run rapid bid/no-bid assessments, instantiate updated compliance matrices (CMMC, NIST 800-171, ITAR, DFARS), and generate capture artifacts; use Workflow Tracker to manage the 9-gate capture process and maintain audit-ready routing and documentation.

Who to notify:

• Capture/BizDev leads — reposition pipelines and update win strategies.
• Program Managers & Contracts leads — assess vehicle-level impacts and prepare for potential novations or reassignments.
• Security/Compliance officers — validate classified-handling and export-control posture.
• Proposal managers — update bid/no-bid and proposal schedules.
• Executive sponsors — assess program-level risk and resourcing.

First 48-hour playbook:

• Hour 0–4: Trigger Cabrillo Signals War Room alert; run saved searches in Intelligence Hub for SDA, PWSA, and listed vehicles; notify Capture, Contracts, Security, PM, and Exec leads.
• Hour 4–12: Use Match Engine to rescore active opportunities; generate a ranked list of highest-risk/high-opportunity contracts; Proposal OS: run immediate bid/no-bid assessments for imminent actions.
• Hour 12–24: Contracts team compiles inventory of SDA-related IDIQs, task orders, and consortium agreements; Security runs rapid compliance checklist (CMMC, NIST 800-171, ITAR, DFARS).
• Hour 24–48: Update capture plans and Proposal Studio libraries; set Intelligence Hub saved searches to daily; schedule stakeholder decision brief and assign owners for follow-on tracking and outreach.