Department of War | Autonomous warfare
AutoWarCom stands up October 1, 2027. The compute, comms, and data decisions start now.
What Federal System Integrators, Department of War program and contracting offices, and advanced projects teams need to know about the new four-star command—and how to architect, source, and stage the infrastructure that will run its unmanned systems.
On September 30, 2026, at Marine Corps Base Quantico, Secretary of War Pete Hegseth announced the creation of the Autonomous Warfare Command (AutoWarCom)—a new four-star combatant command endowed with service-like acquisition and force-development authorities to scale autonomous and robotic capabilities across the Joint Force. Pending congressional authorization, AutoWarCom is slated to achieve initial stand-up on October 1, 2027.
To bridge the gap over the next twelve months, former Defense Innovation Unit (DIU) director Owen West has been appointed chief executive officer of the Direct Reporting Portfolio Manager for Unmanned Systems (DRPM-UxS), with Navy SEAL Senior Chief Max Strasiser serving as chief operating officer. Together, DRPM-UxS is executing Project Agincourt—the transition effort laying the organizational, technical, and acquisition groundwork until the four-star command formally activates.
While airframes and attritable one-way attack drones will capture headlines, unmanned mass is only as effective as the infrastructure behind it. Every autonomous platform depends on high-density compute to train models and run edge inference, resilient communications links to receive tasking and report telemetry under electronic attack, and governed data pipelines that turn one sortie's sensor logs into the next mission's software update. This guide examines how AutoWarCom is structured, what each of those three infrastructure layers requires, the compliance mandates taking effect between late 2026 and 2027, and how program offices and integrators can procure deployment-ready hardware today.
Key takeaways
- AutoWarCom targets October 1, 2027. Until the command formally activates, DRPM-UxS runs Project Agincourt following its initial 30-day implementation plan delivered to the Chairman of the Joint Chiefs of Staff at the end of October 2026.
- Unprecedented funding scale is on the table. The FY2027 budget request for the Defense Autonomous Warfare Group (DAWG) reaches $54.6 billion—primarily through reconciliation—up from $226 million in FY2026.
- Airframes are expendable; edge infrastructure is not. While low-cost drones are procured as consumables, the ruggedized edge servers, MANET radios, ground control stations, and storage arrays that orchestrate them must survive the entire deployment.
- FIPS 140-3 is now mandatory for new CUI purchases. NIST moved all FIPS 140-2 certificates to its Historical List on September 21, 2026, meaning new procurements must specify FIPS 140-3 validated cryptographic modules.
- Three major 2027 gates converge alongside CMMC Phase 1 enforcement: While the Department of War suspended CMMC Phase 2 (third-party C3PAO mandates) on July 13, 2026 pending its CMMC Reform Task Force review, Phase 1 Level 2 self-assessments and NIST SP 800-171 Rev 2 remain mandatory ahead of DoW Target-Level Zero Trust (September 30, 2027), AutoWarCom stand-up (October 1, 2027), and the NDAA Section 5949 semiconductor ban (December 23, 2027).
Chapter 1
What the Autonomous Warfare Command is and how it got here
Pentagon leadership framed AutoWarCom's mandate as scaling "autonomous and robotic capabilities across the Joint Force in the fastest peacetime shift in modern military history." Secretary Hegseth distilled the strategic driver into a single sentence: "The pace of war is changing faster than the process to support it."
Rather than functioning solely as an advisory staff, AutoWarCom is designed to consolidate service-provided autonomous formations that support geographic combatant commands, establish joint interoperability requirements, and test emerging equipment and force designs in realistic operational environments. Its operating model intentionally "fuses operators with entrepreneurs in rapid adaptation cycles while distributing decisions and dollars closer to frontline units."
Capitol Hill is advancing enabling legislation on a parallel track. The Senate Armed Services Committee's FY2027 National Defense Authorization Act (NDAA) draft includes provisions authorizing a four-star Robotic and Autonomous Systems Combatant Command equipped with dedicated test-and-evaluation authorities and streamlined commercial marketplace purchasing power. However, legislative negotiations remain active, and defense analysts note that the Senate's initial language grants narrower unilateral acquisition authority than the Pentagon's September 2026 proposal.
Alongside AutoWarCom, Hegseth commissioned Project Meridian, a 120-day strategic study of future warfare led by Department of War Chief Technology Officer Emil Michael, with final recommendations due January 28, 2027. Explore how Paragon Micro's Public Sector division is postured for Project Meridian on our Advanced Projects page.
The policy trail behind the command
AutoWarCom represents the culmination of 15 months of aggressive acquisition directives, organizational restructurings, and large-lot procurement gauntlets. Each milestone directly reshapes what government buyers must demand from hardware and integration partners.
July 10, 2025
Unleashing U.S. Military Drone Dominance Memo: Mandates fielding low-cost tactical drones to every combat squad by the end of 2026 and transfers management of the Blue UAS cleared list to the Defense Contract Management Agency (DCMA) by January 1, 2026.
Impact on buyers: Shifts small UAS from boutique buys to high-volume unit equipping with faster component-level approval.
November 7, 2025
Warfighting Acquisition System (WAS) Overhaul: Requires at least two qualified sources for critical program content unless waived, enforces module-level competition with machine-readable interfaces, and establishes persistent test environments.
Impact on buyers: Modular Open Systems Approach (MOSA) interfaces and dual-sourced hardware baselines become enforceable contract terms.
Late 2025
Defense Autonomous Warfare Group (DAWG) Activation: DAWG stands up and absorbs the Pentagon's flagship Replicator initiative.
Impact on buyers: Consolidates joint autonomy standards and common control interfaces under a single portfolio structure.
January 9, 2026
Department of War Artificial Intelligence Strategy: Establishes seven pace-setting AI projects, strict data-sharing decrees, and accelerated Authorizations to Operate (ATO) with cross-service reciprocity.
Impact on buyers: Drives immediate demand for accredited GPU training clusters, edge inference servers, and machine-readable data catalogs.
February–March 2026
Drone Dominance Program Gauntlet I (Fort Benning): Allocates roughly $150 million for 30,000 one-way attack drones, issuing initial delivery orders across 11 winning vendors.
Impact on buyers: Validates competitive fly-off contracting for tens of thousands of attritable systems at once.
June 11, 2026
Senate FY2027 NDAA Markup: Senate Armed Services Committee formally introduces statutory language authorizing a four-star Robotic and Autonomous Systems Combatant Command.
Impact on buyers: Opens the formal legislative pathway for permanent command authorities.
August 2026
Drone Dominance Program Gauntlet II (Fort Carson): Doubles procurement scale with planned orders for 60,000 drones awarded to top-performing vendors.
Impact on buyers: Confirms sustained, multi-tranche volume production and stricter supply-chain origin rules.
September 30, 2026
AutoWarCom and Project Agincourt Unveiled: Secretary Hegseth announces the October 1, 2027 stand-up target at Quantico and empowers DRPM-UxS to lead the transition.
Impact on buyers: Establishes a unified operational customer for joint autonomous warfare.
October 1, 2027
AutoWarCom Target Stand-Up Date: Planned activation of the four-star command.
Impact on buyers: Compute, networking, and data architectures procured over the next 11 months will form the baseline AutoWarCom inherits on day one.
The funding landscape
$54.6B
FY2027 budget request for DAWG, up from $226 million in FY2026
Defense budget reporting indicates that $53.6 billion of the FY2027 DAWG request is structured through congressional reconciliation alongside $1 billion in the base defense budget. DAWG Director Lt. Gen. Steven Marks warned lawmakers that a funding lapse or continuing resolution "truly concerns me," noting that the industrial momentum built since DAWG's creation "will be waning" without predictable capital.
Because the bulk of this funding depends on reconciliation legislation, program offices and integrators should structure contracts to execute in modular, scalable phases as tranches of funding clear.
What changes for buyers and integrators
- Purchasing power moves closer to tactical formations: Because AutoWarCom's mandate pushes funding and testing decisions toward operational units, more procurements will originate from portfolio managers and brigade-to-corps commands operating on compressed delivery timelines.
- Consumable airframes require durable ground infrastructure: Attritable drones are designed to be expended in combat. By contrast, the ruggedized edge servers, tactical radios, ground control stations, and storage nodes that run them must endure months of field deployment across contested electromagnetic environments.
- Common control interfaces replace proprietary silos: Lt. Gen. Marks emphasized that formations must be trained on unified control architectures rather than juggling "six to eight" standalone vendor systems that each demand separate operator skills—the exact same integration lesson demonstrated by the U.S. Army's 2nd Cavalry Regiment during Project Flytrap in Europe.
Chapter 2
Compute from the training cluster to the tactical edge
Unmanned operations depend on three distinct tiers of compute infrastructure. Each tier involves different procurement offices, different environmental envelopes, and different operational failure modes.
Tier 1
Enterprise and training compute
Foundation models, target-recognition algorithms, and swarm behaviors are trained, stress-tested in synthetic environments, and retrained at the enterprise tier. The DoW AI Strategy commits "substantial resources" to department data centers, mandates access to frontier model releases within 30 days of commercial availability, and enforces reciprocal Authorizations to Operate.
Pace-setting initiatives such as Swarm Forge (testing AI-enabled combat tactics) and Ender's Foundry (large-scale AI simulation) require GPU-dense rack servers, high-throughput NVMe storage fabrics, and low-latency interconnects housed inside accredited facilities.
Tier 2
Forward edge nodes
Deployed inside tactical vehicles, command shelters, naval vessels, and austere forward operating sites, Tier 2 servers execute real-time inference on multi-sensor feeds, fuse tracks across dozens of unmanned assets, host local mission-planning and common operating picture software, and buffer mission logs when reachback links are jammed.
Every specification at this tier is governed by strict Size, Weight, Power, and Cooling (SWaP-C) limits alongside shock, vibration, thermal extremes, and airborne dust.
Tier 3
Onboard airframe compute
Processors mounted directly on attritable airframes must balance milliwatts against battery flight time. As field reporting on the Estonian Ghost Dragon reconnaissance drone in Ukraine demonstrated, effective onboard optical navigation can run on a lightweight 1-gigahertz Arm processor when paired with well-trained models.
While airframe processors are embedded by the drone OEM, the heavy lifting of model training, multi-sensor fusion, and mission orchestration happens on Tier 1 and Tier 2 infrastructure.
Tier 2 reference platform
Dell PowerEdge XR8000
A modular, sled-based server engineered specifically for high-vibration, thermally extreme forward edge deployments.
Chassis form factor
430 mm short-depth, up to 4 modular nodes
Thermal envelope
-20°C to 65°C in qualified configurations
GPU acceleration
Up to 3 NVIDIA L4 Tensor Core GPUs
Power options
100–240V AC or -48V DC tactical power
Hardware security
Silicon Root of Trust, TPM 2.0, Secure Boot, System Erase
Why rapid cryptographic sanitization matters: If a forward command post or mobile shelter risks being overrun, cached sensor imagery and fine-tuned model weights represent a high-value intelligence loss. Procurement specs should define how fast an edge server can execute cryptographic erase and how operators trigger it locally or remotely.
Pre-staged and validated before deployment
Inside a defense-grade Dell PowerEdge build
Paragon Micro, through its Public Sector Division, configures, burn-in tests, and stages tactical and enterprise servers inside its secure System Readiness Center. Hover over or tap each numbered marker below to inspect the pre-deployment checkpoints on a rack server.
- Locking security bezelA keyed front bezel prevents unauthorized drive removal during transit or inside shared tactical compounds. Specify locking bezels on all forward-deployed nodes.
- Pre-imaged drive baysStorage arrays are populated, loaded with golden-image mission configurations, and stress-tested prior to shipment so units do not waste field time building RAID volumes.
- Documented chain of custodyEvery serialized component is logged from intake to delivery and handled exclusively by vetted U.S. citizens inside access-controlled zones.
- Dell Technologies Federal Platinum PartnerParagon Micro holds Dell Technologies Federal Platinum Partner status. Explore our Dell Technologies Federal capabilities.
- Out-of-band management displayProvides immediate visibility into iDRAC/management IP status. Always verify that out-of-band management functions reliably over low-bandwidth tactical links before shipping.
- Hardened front console portsUSB and video ports enable direct crash-cart recovery when networks go dark. Define in your security baseline whether front ports remain active or locked down via BIOS policy.
Ruggedized operator endpoints
Ground control stations (GCS) and tactical operator laptops endure the same environmental punishment as forward servers. Platforms such as Dell's Pro Rugged series are engineered for this role. Contracting teams should specify high-nit direct-sunlight readability, glove-compatible touchscreens, hot-swappable dual batteries capable of sustaining a full operational shift, and FIPS 140-3 validated self-encrypting drives.
What to specify in compute RFPs
- Third-party environmental test evidence to MIL-STD-810H (shock, vibration, altitude, extreme temperature) and, where required by vehicle or aircraft integration, electromagnetic compatibility testing to MIL-STD-461G.
- Exact physical envelope constraints—operating temperature range, rack depth, weight, and power input (120/240V AC, -48V DC, or 28V tactical vehicle power).
- GPU architecture matched to the workload: low-SWaP inference accelerators (such as NVIDIA L4) at the tactical edge, paired with high-memory training GPUs in enterprise data centers.
- Hardware root of trust, cryptographically signed firmware, TPM 2.0, Secure Boot, and a verified rapid-sanitization procedure.
- Out-of-band management pre-configured to operate across degraded, high-latency links.
- Pre-staged mission spares and a lifecycle refresh schedule sized to the deployment, eliminating slow RMA turnarounds from forward theaters.
Paragon Micro's Public Sector division engineers, gold-images, and burn-in tests these architectures inside its 55,000+ square-foot, AS9120-certified System Readiness Center, delivering kitted, fully documented hardware ready for immediate field installation.
Chapter 3
Comms that hold up in contested spectrum
The electronic warfare reality
10,000
Drones Ukraine may lose per month, primarily to electronic warfare jamming, according to Royal United Services Institute estimates
Modern high-intensity conflict has proven that contested electromagnetic spectrum is the primary killer of unmanned systems.
To survive dense electronic warfare, forces in Ukraine have adopted two primary countermeasures: equipping strike drones with onboard optical terminal navigation to complete attacks after RF and GNSS links are severed, and flying first-person-view (FPV) drones tethered to unjammable spools of ultra-thin optical fiber stretching 20 kilometers or more.
While onboard autonomy reduces link dependence during the final seconds of a terminal engagement, the broader kill web—target cueing, airspace deconfliction, in-flight retasking, battle damage assessment, and multi-domain swarm coordination—still depends on resilient communications. Network architects must treat Denied, Degraded, Intermittent, and Limited (DDIL) spectrum as the everyday baseline rather than an emergency exception.
Architect the tactical network in four resilient layers
Layer 1
Unit-level MANET mesh
Mobile Ad Hoc Network (MANET) radios link dismounted operators, unmanned vehicles, and forward edge compute nodes within line of sight—automatically self-healing and rerouting packets when nodes move or drop.
Layer 2
Beyond-line-of-sight (BLOS)
Multi-orbit SATCOM terminals (LEO/MEO/GEO) and high-altitude relays provide resilient reachback from forward brigades to theater command posts and enterprise data centers.
Layer 3
Fixed sanctuary links
High-capacity fiber and wired tactical local area networks at main operating bases and staging hubs handle bulk telemetry ingestion and model distribution.
Layer 4
Edge store-and-forward
When active jamming forces formations into emission control (EMCON), forward edge servers cache telemetry locally and burst-sync prioritized deltas the moment a transport window opens.
Six engineering questions for any tactical radio or terminal
- Which frequency bands does the radio span, and how rapidly does it execute automated frequency hopping or spectrum evasion under active jamming?
- What Low Probability of Intercept / Low Probability of Detection (LPI/LPD) waveform features mask the operator's electromagnetic signature from enemy direction-finding?
- How many concurrent nodes can a single mesh subnet sustain before latency spikes, and what is the verified throughput at operational range?
- Does the hardware integrate natively with existing tactical waveforms, ATAK/Maven interfaces, and network management tools already fielded by the unit?
- Is the embedded cryptographic module validated under FIPS 140-3—or, for classified traffic, certified as an NSA Type 1 device or listed under an NSA Commercial Solutions for Classified (CSfC) capability package?
- What is the exact SWaP-C draw on the host vehicle electrical bus or soldier battery load?
Cryptographic mandate effective September 21, 2026
On September 21, 2026, NIST's Cryptographic Module Validation Program formally transitioned all FIPS 140-2 certificates to its Historical List. Federal and defense agencies were permitted to procure FIPS 140-2 modules for protecting Controlled Unclassified Information (CUI) only through that cutoff date.
Immediate contracting action: Specify FIPS 140-3 validated cryptographic modules across all new solicitations for radios, rugged laptops, edge servers, and encrypted drives, and audit lifecycle refresh schedules for legacy fleets.
For classified tactical links, the National Security Agency's Commercial Solutions for Classified (CSfC) program enables program offices to protect national security systems using layered, commercially available encryption products configured strictly in accordance with NSA capability packages and the CSfC Components List.
Enforce Section 889 supply-chain exclusions across sub-components
FAR 52.204-25 (implementing NDAA Section 889) strictly prohibits federal agencies from procuring or operating equipment that incorporates covered telecommunications or video surveillance components from Huawei, ZTE, Hytera, Hikvision, Dahua, or their affiliates as a substantial or essential element. In unmanned and C-UAS programs, this scrutiny must extend deep into optical gimbal cameras, cellular fallback modems, and RF sub-assemblies inside commercial radios.
Paragon Micro's Public Sector division has delivered handheld, manpack, and vehicular mesh radio systems, rugged SATCOM terminals, and tactical networking switches to defense customers. Because OEM authorization varies by contract vehicle and task order, engage our Department of War solutions team early when shaping your bill of materials.
Chapter 4
Data that makes each mission better than the last
Autonomous platforms gain combat advantage only when sensor logs, electronic warfare intercepts, and terminal engagement outcomes from today's sortie reach the engineers retraining models for tomorrow's launch. In practice, that feedback loop breaks at three choke points: at the tactical edge, where terabytes of raw video accumulate without a backhaul link; in transit, where narrowband tactical radios choke on unprioritized payloads; and at the enterprise, where proprietary vendor logs arrive in locked formats no other system can parse.
New Department of War data and open-architecture mandates
The January 2026 DoW AI Strategy enforces strict internal data decrees: component organizations must register datasets in a federated catalog within 30 days and submit written justification to the Under Secretary within 7 days if they deny a data-sharing request. Concurrently, the department is consolidating the Advana analytics environment into a centralized War Data Platform.
On the acquisition side, the Warfighting Acquisition System directive mandates module-level competition built on a Modular Open Systems Approach (MOSA), requiring documented, machine-readable interfaces so third-party integrators can swap sensors, algorithms, or UI layers without paying proprietary vendor lock-in fees. This policy directly reinforces DAWG's push for common control interfaces and the U.S. Army's adoption of the Integrated Sensor Architecture (ISA) during Project Flytrap.
Engineer the five-stage data loop before the first flight
- Collect
Full-motion video, telemetry, target detections, and EW spectral observations land on the forward edge server—automatically stamped with time, coordinates, platform ID, and security classification.
- Triage
Edge inference filters out empty transit video, retains high-value anomalies and engagement clips needed for the next sortie, and compresses archives.
- Move
Prioritized data deltas synchronize automatically to the enterprise War Data Platform whenever SATCOM or fixed sanctuary bandwidth becomes available.
- Label and retrain
Enterprise AI teams curate edge detections, retrain object-recognition and autonomy weights, and validate performance in synthetic simulation.
- Return
Cryptographically signed model updates push back to forward edge nodes and airframes with strict version control and one-click rollback capability.
Target-level Zero Trust arrives September 30, 2027
The Department of War's mandate to achieve target-level Zero Trust—spanning 91 distinct capability outcomes—falls on September 30, 2027, the exact day before AutoWarCom's target activation. Defense CIO leadership has explicitly noted that extending Zero Trust beyond enterprise IT into tactical weapon systems and operational technology represents a major engineering lift.
Forward edge servers and ground control stations procured today must support disconnected identity and access management (cached policy enforcement when cut off from cloud identity providers), FIPS 140-3 encryption at rest and in transit, and immutable audit logs that reconcile automatically when connectivity resumes.
Four data-rights questions to ask every autonomy vendor
- What exact schemas do your flight logs, video streams, and target detections use, and are the APIs documented in machine-readable formats compliant with MOSA and ISA?
- Does the government retain unlimited rights to raw mission telemetry, labeled training datasets, and fine-tuned model weights generated under the contract?
- How many gigabytes does a standard sortie generate, and how many days of disconnected operations can the forward edge storage array buffer before overwriting?
- How are over-the-air or local model updates cryptographically signed, verified prior to execution, and rolled back if a new build degrades flight performance?
Chapter 5
Supply chain and compliance rules for unmanned systems
Scaling unmanned systems to tens of thousands of units intersects with the strictest supply-chain and cybersecurity enforcement calendar in defense contracting history.
Drones and sub-tier components
FAR 52.240-1 and DCMA Blue UAS
FAR 52.240-1 prohibits contractors from delivering unmanned aircraft systems manufactured or assembled by American Security Drone Act (ASDA) covered foreign entities, and bars using federal funds to procure or operate them. Since December 22, 2025, the clause also prohibits operating covered UAS in the performance of any federal contract.
Under the July 2025 Drone Dominance directive, the Blue UAS cleared list transitioned to the Defense Contract Management Agency, while Phase II of the Drone Dominance Program explicitly bans Chinese-origin motors and batteries.
Semiconductors in servers and radios
NDAA Section 5949: December 23, 2027
Section 5949 of the FY2023 NDAA prohibits executive agencies from procuring electronic products or services that contain covered semiconductors designed or produced by SMIC, YMTC, or CXMT, taking effect on December 23, 2027.
The FAR Council's proposed rule (released February 17, 2026) requires prime contractors and suppliers to conduct a "reasonable inquiry," certify compliance, and flow the prohibition down across all tiers—including commercial off-the-shelf (COTS) hardware and purchases below the micro-purchase threshold.
Controlled Unclassified Information
CMMC Phase 1 & Phase 2 Suspension
On July 13, 2026, the Department of War suspended the November 10, 2026 rollout of CMMC Phase 2 (third-party C3PAO certification) while its CMMC Reform Task Force aligns the program with Acquisition Transformation System directives.
Crucially, CMMC Phase 1 remains in full force: CUI contracts still require Level 2 self-assessments, current SPRS scores, annual senior-official affirmations, and full compliance with NIST SP 800-171 Rev 2 and DFARS 252.204-7012—backed by select government-led assessments and False Claims Act enforcement.
Verified chain of custody and counterfeit mitigation
High-volume hardware surges inevitably attract gray-market brokers and counterfeit sub-components. Paragon Micro mitigates supply-chain risk by sourcing directly from authorized OEM channels, verifying component provenance, logging every serialized asset and BIOS/firmware step, enforcing Trade Agreements Act (TAA) compliance, and restricting physical handling inside our System Readiness Center to vetted U.S. citizens. In June 2026, Paragon Micro earned AS9120 certification—the aerospace and defense industry's premier quality-management standard for traceability, counterfeit prevention, and configuration control.
For sensitive and advanced projects
Classified and advanced defense programs require physically segmented integration bays, zone-based access control, and tamper-evident packaging backed by end-to-end custody manifests. Before awarding an integration order, ask your hardware partner to demonstrate where your nodes will be staged, who holds badge access to that zone, and what serialized documentation accompanies every pallet at delivery.
Chapter 6
How to buy it, readiness checklists, and common questions
Pre-competed contract vehicles available through Paragon Micro
U.S. Army & Federal
Army ITES-4H
Eligible buyersU.S. Army, Department of War, and all federal agencies
Ordering periodActive through 2035
ScopeServers, tactical & enterprise data center hardware, storage, rugged endpoints, networking, and lifecycle services
Missile Defense Agency
MDA SHIELD IDIQ
Contract numberHQ0859-26-D-E455
Ordering periodDecember 28, 2025 to December 28, 2035
ScopeIT infrastructure, rugged hardware, system integration, and lifecycle sustainment under a $151B shared ceiling
Governmentwide
NASA SEWP V
Contract numberNNG15SD91B
Ordering periodExtended by NASA through January 31, 2027
ScopeFull-spectrum commercial IT hardware, rugged compute, networking, and product-based integration services
Governmentwide
GSA MAS Products
Eligible buyersAll federal and defense agencies
Contract pathwayParticipating dealer and teaming arrangements via EC America (GS-35F-0511T) and TD SYNNEX (GS-35F-0563U)
Paragon Micro is a Dell Technologies Federal Platinum Partner alongside deep multi-OEM authorizations across compute, storage, tactical networking, and power. Contact our Public Sector division to align your exact bill of materials with the optimal contract vehicle.
Role-based readiness checklists
Checklist 01
For Federal System Integrators (FSIs)
- Satisfy dual-source mandates early: The Warfighting Acquisition System memo requires at least two qualified sources for critical content unless waived. Partner with a multi-OEM hardware integrator that can qualify, benchmark, and stage primary and alternate server/radio baselines simultaneously.
- Offload golden-image staging: Have edge nodes racked, cabled, BIOS-hardened, and loaded with your software stack before they hit your integration lab—complete with serialized configuration artifacts for your ATO package.
- Lock down supply-chain compliance: Use an AS9120-certified distribution partner so CMMC Phase 1 Level 2 self-assessment, NIST SP 800-171 Rev 2, TAA, FAR 52.240-1, and Section 5949 semiconductor inquiries have auditable answers.
Checklist 02
For Advanced Projects Teams
- Audit physical build security: Verify where staging occurs, confirm U.S.-citizen-only handling, and require physically segmented build cages isolated from commercial customer traffic.
- Demand end-to-end custody manifests: Require serialized chain-of-custody logs at every handoff and tamper-evident packaging for OCONUS or range transport.
- Burn-in test the complete kit: Validate thermal draw, out-of-band management, and power supplies under load prior to shipment so field operators never troubleshoot DOA hardware on range day.
Checklist 03
For DoW Program and Contracting Offices
- Define requirements around operational environment, SWaP-C envelope, and open interfaces—allowing qualified OEMs to compete at the module level.
- Mandate FIPS 140-3 validated cryptographic modules across all new CUI radios, servers, storage arrays, and operator laptops.
- Require documented, machine-readable data schemas (MOSA / ISA compliant) and explicitly establish government ownership of mission telemetry and trained models.
- Require MIL-STD-810H environmental and MIL-STD-461G EMI test documentation matched to the host vehicle, shelter, or vessel.
- Size forward NVMe storage capacity for the longest anticipated DDIL / EMCON disconnection window.
- Specify hardware root of trust and rapid cryptographic sanitization procedures on all forward-deployed nodes.
- Obtain written FAR 52.240-1 (ASDA), FAR 52.204-25 (Section 889), and TAA certifications, plus a Section 5949 semiconductor readiness attestation.
- Verify the supplier's active SPRS score, annual CMMC Phase 1 Level 2 self-assessment affirmation, and NIST SP 800-171 Rev 2 compliance while monitoring DoW CIO guidance on the CMMC Reform Task Force.
- Procure pre-configured mission spares and lifecycle sustainment upfront alongside initial fielding lots.
- Select a contract vehicle (such as ITES-4H or MDA SHIELD) whose ordering period spans your full multi-year program lifecycle.
Frequently asked questions
What is the Autonomous Warfare Command (AutoWarCom) and when does it stand up?
Announced on September 30, 2026 by Secretary of War Pete Hegseth at Marine Corps Base Quantico, the Autonomous Warfare Command (AutoWarCom) is a planned four-star combatant command with service-like authorities designed to scale autonomous and robotic capabilities across the Joint Force. Its target stand-up date is October 1, 2027, pending congressional authorization.
What is Project Agincourt and how does it relate to DRPM-UxS?
Project Agincourt is the transition effort that prepares the organizational, acquisition, and technical foundation for AutoWarCom ahead of its October 1, 2027 activation. It is executed by the Direct Reporting Portfolio Manager for Unmanned Systems (DRPM-UxS), led by CEO Owen West and COO Senior Chief Max Strasiser.
How much funding is requested for the Defense Autonomous Warfare Group (DAWG) in FY2027?
The FY2027 request for DAWG totals $54.6 billion—comprising $53.6 billion sought through congressional reconciliation and $1 billion in the base defense budget—up from $226 million in FY2026.
Why must new defense IT and tactical radio purchases specify FIPS 140-3 instead of FIPS 140-2?
On September 21, 2026, NIST's Cryptographic Module Validation Program moved all FIPS 140-2 certificates to its Historical List. Federal and defense agencies could accept FIPS 140-2 modules for protecting Controlled Unclassified Information (CUI) only through that date, making FIPS 140-3 validation mandatory for new procurements.
How do the CMMC Phase 2 suspension and NDAA Section 5949 affect unmanned systems infrastructure?
Although the Department of War suspended CMMC Phase 2 (third-party C3PAO mandates) on July 13, 2026 pending a CMMC Reform Task Force review, Phase 1 Level 2 self-assessments, active SPRS scores, annual senior-official affirmations, and full NIST SP 800-171 Rev 2 compliance remain mandatory for contracts involving CUI. Meanwhile, starting December 23, 2027, NDAA Section 5949 bars executive agencies from procuring electronic products containing covered semiconductors from SMIC, YMTC, or CXMT, reaching down to COTS servers, radios, and sub-tier components.
Which contract vehicles can DoW buyers use to procure edge compute and comms from Paragon Micro?
Paragon Micro's Public Sector division supports Department of War and federal buyers through Army ITES-4H (ordering through 2035), the $151B MDA SHIELD IDIQ (HQ0859-26-D-E455, ordering through December 2035), NASA SEWP V (NNG15SD91B), and GSA MAS teaming arrangements, backed by AS9120-certified staging inside the Paragon Micro System Readiness Center.
Timeline
Key dates through 2027
Late Oct 2026
Project Agincourt 30-day implementation plan delivered to the CJCS
DRPM-UxS transition milestone
Nov 10, 2026
Original CMMC Phase 2 date (suspended July 13, 2026; Phase 1 Level 2 self-assessments remain mandatory)
Awaiting CMMC Reform Task Force guidance
Jan 28, 2027
Project Meridian 120-day future warfare study due
Led by DoW CTO Emil Michael
Jan 31, 2027
Current NASA SEWP V ordering extension concludes
Contract NNG15SD91B
Sep 30, 2027
Department of War Target-Level Zero Trust deadline
Covers 91 capability outcomes
Oct 1, 2027
Autonomous Warfare Command (AutoWarCom) target stand-up
Pending congressional authorization
Dec 23, 2027
NDAA Section 5949 semiconductor prohibition takes effect
Bars SMIC, YMTC, and CXMT chips
Ultimately, AutoWarCom will be measured by how rapidly autonomous formations deploy and how reliably they fight inside contested electromagnetic environments. Achieving that readiness depends on ruggedized edge compute that survives forward deployment, multi-layered communications that hold up under jamming, and open data pipelines that turn every mission into a smarter model.
Paragon Micro · Public Sector Division
Equipping a program for autonomous operations?
Tell us what your mission requires. Paragon Micro's Public Sector division helps federal integrators and Department of War program offices specify, source, stage, and deliver ruggedized edge compute, tactical comms, and data infrastructure through ITES-4H, MDA SHIELD, NASA SEWP V, and GSA.
Talk to our Department of War solutions team
Explore the System Readiness Center Tactical and Rugged Equipment All Contract Vehicles
Related reading



