Why the JCO Left an Integration Problem
The Joint Counter-sUAS Office stood up in 2020 as a DoD-wide coordination body. The establishment memo itself describes a growing number of DoD C-sUAS organizations that "often are unconnected" to each other. The JCO's mandate was to synchronize requirements, avoid duplication, and accelerate delivery. It made measurable progress. In a January 2025 AUSA article, the JCO's director and chief strategist wrote that the JCO helped fund the Army's Forward Area Air Defense Command and Control system (FAAD C2) and was shepherding the integration of artificial intelligence into it to rapidly generate targeting options for commanders. Per the JIATF 401 Quick Reference Guide (p. 22), the Block 2C Coyote interceptor is fully integrated into FAAD C2, including airspace clearance and fratricide avoidance, and (p. 25) the vehicle-mounted L-MADIS is interoperable with FAAD C2.
The JCO's constraint was organizational: as a coordination office without program executive authority, it could synchronize but not enforce. Services retained their own programs of record, kept their acquisition funding, and pursued separate vendor relationships that could not always be made to interoperate. Consider a hypothetical example of integration debt: a radar from one vendor, a command-and-control platform from a second, and an effector from a third that must coordinate across different data formats, different networks, and different authorization workflows. For Group 1 and Group 2 drones, closing the detection-to-engagement loop in seconds is a real requirement. A workflow that depends on manually coordinating three systems that were not designed together is not a reliable way to meet it.
What JIATF 401 Changed—and What It Did Not
The August 27, 2025 memo signed by Secretary Hegseth specified three structural changes that distinguish JIATF 401 from the JCO.
Acquisition authority. The JIATF 401 director carries acquisition and procurement authority and may approve up to $50 million in funding per effort; the memo also directs the Under Secretary of Defense for Acquisition and Sustainment to designate an acquisition executive to support JIATF 401's rapid procurements and asks for an implementation plan covering a Joint Program Executive Office-like structure.
Centralized R&D funding. Department-wide C-sUAS research, development, test, and evaluation moves to JIATF 401. The memo excludes Military Service-specific and USSOCOM program-of-record development activities from that consolidation. It also directs the Comptroller to review and realign RDT&E, procurement, and operation and maintenance funding supporting joint C-sUAS to JIATF 401.
Direct reporting to the Deputy Secretary. The JCO reported through the Army chain. JIATF 401 reports to Deputy Secretary Stephen Feinberg. We read that as a signal of priority; beyond directing the Director to request liaisons from other federal departments and agencies, the memo does not describe interagency coordination mechanics.
The memo calls for a sunset review at 36 months, so the task force's structure will be re-justified by about August 2028. The Army Secretary was directed to deliver an implementation plan within 30 days of the memo.
Defence-industry.eu reported that a follow-on Department of War memorandum widened JIATF 401's role in fielding approvals: JIATF 401 coordinates counter-drone weapons safety reviews with the Unmanned Systems Direct Reporting Portfolio Manager, and any denial must carry a documented rationale submitted to JIATF 401. We have not reviewed the text of that memorandum, so treat these details as reported rather than confirmed.
What the memo did not change: existing service and USSOCOM programs of record are excluded from JIATF 401's authority, and the memo does not itself issue a directive for architectural consolidation of C2. FAAD C2, the fielded sensors, and the existing integration work stay under their current program owners. The memo gives the JIATF 401 Director authority to determine whether new Military Service-specific C-sUAS will be adopted, while excluding existing programs of record. Its leverage over C2 consolidation therefore runs through new starts and the systems it approves, not through the installed base.
The Domestic Shield Program: Structure and Access
JIATF 401's most visible 2026 action has been the Domestic Shield IDIQ program. JIATF 401 awarded AeroVironment a $500 million-ceiling IDIQ contract in early July 2026 (DVIDS, July 5, 2026), and CACI announced its SkyValor system as the first task order of a three-year $500 million IDIQ contract (July 30, 2026). On September 29, 2026, the Army announced ten more Domestic Shield base IDIQ awards: Allen Control Systems, Digital Force Technologies, DroneShield, Napatree, RADA, SRC and L3Harris WESCAM at $500 million each; Echodyne and PVP Advanced EO Systems at $250 million; and SmartShooter at $150 million. Those ten total $4.15 billion and do not include the earlier AeroVironment and CACI awards, so the known base ceilings across 12 awards come to at least $5.15 billion. Soldier Systems reported that DroneShield's award covers radio frequency sensing, electronic countermeasures, command-and-control, artificial intelligence and multi-sensor integration. Pulse2 covered the same ten awards.
Ceiling values are authorization, not obligation. Task orders—not IDIQ awards—determine actual spending and deployment. Domestic Shield allows JIATF 401 to issue task orders across multiple vendors for force protection, base defense, and homeland-defense requirements without running separate full-and-open competitions for each, though orders under multiple-award contracts remain subject to fair-opportunity rules among awardees.
The September 8, 2026 Quick Reference Guide is an 89-page unclassified document (Version 4). It catalogs systems commonly found in the services today across Groups 1-3 (the guide notes it is not all-inclusive), covering sensors, effectors, and two C2 platforms, FAAD C2 and Lattice C2, and totaling 37 listed system entries. It focuses on common terminology and TTPs, and states that all C2 platforms are intended to be interoperable with each other.
For program managers evaluating counter-UAS options for an installation or a deployed force structure, Domestic Shield may be the fastest path to Group 1-3 capability within JIATF 401's scope, in our assessment—assuming the requirement fits the IDIQ structure and JIATF 401 issues a task order for it. Using it does not require standing up a separate program of record; it does require engaging JIATF 401 directly to confirm scope alignment before assuming the contract vehicle will serve the requirement. The Army release also describes a JIATF-401 C-UAS Marketplace for identifying, evaluating and transitioning commercial capabilities, which is another route to ask about.
The C2 Integration Problem Is Not Solved by Organization
Procurement speed and organizational authority matter. They do not, by themselves, resolve the operational architecture problem.
FAAD C2 remains the integration layer for most of the installed base. Sensors feed detections in, the system generates engagement recommendations and manages authorization workflows, and effectors execute. The JCO made real progress integrating existing systems into this architecture: per the Quick Reference Guide, Coyote Block 2C is fully integrated and L-MADIS is interoperable, and AI-enabled improvements to the decision-support layer were underway at the time of the JCO's disestablishment. JIATF 401 inherits that work and that architecture.
That said, FAAD C2 is not the long-term endpoint. In October 2025, Breaking Defense reported that Anduril won an Army and Defense Innovation Unit competition for a modernized counter-UAS fire control system, and that the Army's counter-drone project lead said the winning solution would replace Northrop Grumman's FAAD C2. In November 2025, DefenseScoop reported that Anduril announced the Army had selected its Lattice platform as a next-generation fire control platform for the Integrated Battle Command System Maneuver (IBCS-M) program. Anduril says that in a seven-day trial at Yuma Proving Ground, Lattice integrated a previously undisclosed sensor and effector within hours and went four for four on live-fire intercepts; those results are the company's claims. Together, the two announcements point toward an Anduril/Lattice-based fire control layer replacing FAAD C2, although transition timing and scope have not been published. The practical implication for Domestic Shield vendors: FAAD C2 integration is the current operational requirement; Lattice/IBCS-M integration is the emerging one. In Spartan X's assessment, a program that only addresses FAAD C2 may need a second integration cycle within the contract period.
The new Domestic Shield contracts bring a different question: what C2 integration does each of these systems actually have, and what does a multi-vendor installation look like in practice? A detection layer from one vendor, a command-and-control platform of the kind listed in the Quick Reference Guide, and an effector from a third Domestic Shield awardee—do they all talk to FAAD C2? Do they interoperate with each other? Does the engagement authorization workflow flow through a single interface or require operators to manage separate displays?
Vendors have market incentives to claim interoperability and downplay integration work. The right due diligence is not to ask whether a system is compatible with FAAD C2, but to ask specifically whether it has completed FAAD C2 integration, what test events documented that integration, and what software work remains. A vendor that has Coyote-level FAAD C2 integration and one that has theoretical interoperability are not equivalent, and the difference surfaces in operational test rather than in the sales presentation.
Three integration questions are worth asking specifically for any Domestic Shield system:
- FAAD C2 status. Has integration been completed and tested, not just planned? What are the specific interface standards involved, and who maintains them?
- Airspace deconfliction. Does the engagement authorization workflow route through FAAD C2's airspace clearance process, or does the system operate outside that workflow? A faster engagement cycle that bypasses fratricide avoidance is not a net improvement.
- Decision-support latency under AI-enabled targeting. Group 1 threats can close engagement windows in seconds at low altitude. What is the system's end-to-end detection-to-recommendation latency? The AI integration work in FAAD C2 is specifically aimed at this problem; a system that bypasses that work in favor of a standalone AI layer needs to demonstrate equivalent or better performance, not just claim it.
JIATF 401's Quick Reference Guide describes systems but not integration depth. The detailed integration status for individual Domestic Shield awardees requires direct engagement with JIATF 401 and, where applicable, the relevant service program office.
Decision Points
If you are evaluating counter-UAS options under JIATF 401's current structure, four questions organize the decision:
- Is the requirement within Domestic Shield scope? Service programs of record and USSOCOM requirements stay under their current owners. Force protection and base defense against Groups 1-3 is the target scope for Domestic Shield task orders. Confirming scope alignment with JIATF 401 before building an acquisition strategy around Domestic Shield avoids the delay of discovering late that the vehicle does not cover the specific requirement.
- What is the vendor's FAAD C2 integration status, and what is their IBCS-M/Lattice roadmap? FAAD C2 is the current operational requirement; the Army has said the Anduril fire-control solution will replace FAAD C2. Ask both questions. A vendor with demonstrated FAAD C2 integration and no Lattice roadmap is carrying a second integration cycle inside the contract period.
- Does the system handle airspace deconfliction internally or rely on an operator-managed process? The answer shapes how the system can be employed and how much operator bandwidth it consumes during an engagement.
- What is the task order process from JIATF 401? IDIQ ceilings do not automatically translate to funded requirements. Understanding JIATF 401's task order initiation process, timelines, and coordination requirements is necessary planning work before a unit or installation needs capability in the field.
The establishment memo, the Quick Reference Guide, the Army award release, and the DVIDS news releases on individual Domestic Shield awards are all public and provide the factual baseline. The integration architecture questions above are what to bring into direct engagement with the task force.
Sources and further reading
- Secretary Hegseth, Establishment of Joint Interagency Task Force 401 (August 27, 2025): media.defense.gov
- JIATF 401 Counter-Small Unmanned Aircraft Systems Quick Reference Guide, Version 4 (published September 8, 2026): media.defense.gov
- JIATF-401 Awards $500 Million in Counter-UAS Contracts to Defend the Homeland (July 5, 2026): dvidshub.net
- DefenseScoop, "Hegseth orders Army secretary to create new joint interagency counter-drone task force" (August 28, 2025): defensescoop.com
- Army.mil, "JIATF-401 advances Domestic Shield with counter-UAS contract awards" (September 29, 2026): army.mil
- CACI SkyValor announcement (July 30, 2026): businesswire.com
- Soldier Systems, DroneShield awarded JIATF 401 Domestic Shield IDIQ contract (October 1, 2026): soldiersystems.net
- Defence-industry.eu, faster counter-drone approvals and the 30-day escalation rule: defence-industry.eu
- FAR 16.505, Ordering (fair opportunity): acquisition.gov
- Pulse2, "Army Awards Counter-UAS IDIQ Contracts With $4.15 Billion In Combined Ceilings": pulse2.com
- AUSA, "Countering Small Drones: Office Works Toward Joint Solutions to Growing Threat": ausa.org
- Breaking Defense, "Army picks Anduril for counter-drone fire control system" (October 16, 2025): breakingdefense.com
- DefenseScoop, "Army picks Anduril to provide next-gen fire control platform for IBCS-M program" (November 11, 2025): defensescoop.com
Spartan X works on the two pieces this analysis keeps returning to. BRIC is an edge AI platform built for denied, disconnected and low-bandwidth conditions, and Arbiter is a multi-model verification layer that keeps tamper-evident audit trails of how an AI output was produced. For a multi-vendor counter-UAS site, whether the C2 layer is FAAD C2 today or its successor, that combination addresses the questions above: whether inference holds up at the edge when links degrade, and whether an engagement recommendation can be reconstructed and checked after the fact.
