Why the JCO Left an Integration Problem
The Joint Counter-sUAS Office stood up in 2020 as a DoD-wide coordination body after years of service-by-service counter-UAS acquisition produced dozens of incompatible systems with no shared command-and-control framework. The JCO's mandate was to synchronize requirements, avoid duplication, and accelerate delivery. It made measurable progress: fielded systems like Coyote were integrated into the Army's Forward Area Air Defense Command and Control system, the JCO funded FAAD C2 development directly, and the office was advancing AI-enabled decision support within FAAD C2 to reduce time-to-engagement-recommendation for commanders. L-MADIS, the Marine Corps' vehicle-mounted non-kinetic counter-UAS system, was made interoperable with FAAD C2 during this period. [AUSA, "Countering Small Drones: Office Works Toward Joint Solutions to Growing Threat"]
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. The pattern that emerged in exercises was integration debt made visible—scenarios where a radar from one vendor, a command-and-control platform from a second, and an effector from a third had to 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. [SecDef memo, Establishment of Joint Interagency Task Force 401, August 27, 2025: media.defense.gov]
Acquisition authority. The JIATF 401 director carries acquisition and procurement authority and can approve individual development efforts up to $50 million without a separate program executive layer. That shortens the path from requirement to contract for systems the task force prioritizes.
Centralized R&D funding. Department-wide C-sUAS research, development, test, and evaluation moves to JIATF 401. Services retain their programs of record, and USSOCOM retains its own portfolio; exploratory development and technology demonstration outside those established programs now has a single owner. The intent is to reduce the parallel-experimentation pattern that allowed competing architectures to proliferate.
Direct reporting to the Deputy Secretary. The JCO reported through the Army chain. JIATF 401 reports to Deputy Secretary Stephen Feinberg. In practice, this signals priority and gives the task force a faster path to interagency decisions when coordination with DHS, the FAA, or state and local authorities is required.
The memo carries a 36-month sunset review, signaling that JIATF 401 is a time-limited delivery mechanism rather than a permanent architecture. The Army Secretary was directed to deliver an implementation plan within 30 days of the memo.
What the memo did not change: service programs of record, USSOCOM programs, and the underlying C2 architecture remain where they were. JIATF 401 acquired authority over new starts and department-wide R&D; it did not absorb the existing installed base or issue a directive for architectural consolidation. FAAD C2, the fielded sensors, and the existing integration work stay under their current program owners. JIATF 401's ability to drive C2 consolidation depends on how it uses its acquisition authority on new vehicles and whether services align new programs to JIATF 401 rather than pursuing independent service-specific contracts.
The Domestic Shield Program: Structure and Access
JIATF 401's most visible 2026 action has been the Domestic Shield IDIQ program. By late September, the task force had awarded $500 million ceiling IDIQ contracts to AeroVironment (announced approximately July 1 [DVIDS news story 569395, July 5, 2026]), CACI for its SkyValor system (approximately July 30), Digital Force Technologies for its SeraphimOS-powered family of systems (September 29), and DroneShield for RF sensing, electronic countermeasures, and multi-sensor integration (September 30). Army-attributed reporting described 10 Domestic Shield IDIQ awards with a combined reported ceiling of approximately $4.15 billion. [Pulse2, "Army Awards Counter-UAS IDIQ Contracts With $4.15 Billion In Combined Ceilings"]
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.
The September 8, 2026 Quick Reference Guide—a 89-page unclassified document (Version 4, cleared August 27, 2026, published on media.defense.gov)—catalogs the systems under JIATF 401's awareness across Groups 1-3. It covers sensors, effectors, and two C2 platforms, totaling 37 listed entries, and is designed to help planners and tactical operators translate doctrine into repeatable TTPs with consistent terminology across military and interagency teams. [JIATF 401 Counter-Small Unmanned Aircraft Systems Quick Reference Guide, Version 4, media.defense.gov, September 8, 2026]
For program managers evaluating counter-UAS options for an installation or a deployed force structure, Domestic Shield is currently the fastest path to Group 1-3 capability within JIATF 401's scope—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 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: Coyote is fully integrated, L-MADIS is interoperable, and AI-enabled improvements to the decision-support layer were underway at the time of the JCO's dissolution. JIATF 401 inherits that work and that architecture.
That said, FAAD C2 is not the long-term endpoint. In October 2025, the Army announced that Anduril won the Forward Counter Unmanned Aircraft Systems Command and Control System (FCUAS C2) competition — explicitly billed as the FAAD C2 successor — run jointly with the Defense Innovation Unit. [Breaking Defense, "Army picks Anduril for counter-drone fire control system," October 2025] The following month, the Army selected Anduril's Lattice platform as the fire control software for the Integrated Battle Command System Manoeuvre (IBCS-M) program, following a seven-day live-fire demonstration at Yuma Proving Grounds in which Lattice integrated a previously undisclosed sensor and effector within hours and completed four successful intercepts. [DefenseScoop, "army-ibcs-maneuver-anduril-lattice-counter-uas," November 11, 2025] The two announcements in rapid succession establish Lattice as the Army's planned counter-UAS fire control architecture going forward. The practical implication for Domestic Shield vendors: FAAD C2 integration is the current operational requirement; Lattice/IBCS-M integration is the emerging one. 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 from 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; Lattice is the Army's declared successor. 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, 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 (cleared August 27, 2026; 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
- 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 2025): breakingdefense.com
- DefenseScoop, "Army's IBCS-M maneuver program selects Anduril Lattice for counter-UAS" (November 11, 2025): defensescoop.com
Spartan X's work at the intersection of edge AI inference and command-and-control architecture—specifically building decision-support systems that function under degraded communications and produce auditable targeting recommendations—is directly relevant to the integration challenge JIATF 401 is working through. The combination of BRIC's edge compute and C3 architecture with Arbiter's AI verification approach maps to exactly what the FAAD C2 AI enhancement work requires: fast, reliable inference at the kill chain edge with a verification layer that can document how an engagement recommendation was generated.
