Army runs 'Right to Integrate' sprint
- Secretary of the Army Dan Driscoll and 10 defense firms launched “Right to Integrate” on May 5, with the first sprint set for Fort Carson. - The Army’s demand is blunt: expose APIs and technical documentation or miss the ecosystem, with Fort Carson bringing engineers, soldiers, and live systems together. - It matters because the Army is shifting from bespoke integrations toward an open-architecture model shaped by Ukraine’s faster battlefield networking.
The Army is trying to fix one of its oldest digital problems — too many weapons, sensors, and software tools that work fine alone but not together. That sounds boring until you translate it into battlefield terms: slower decisions, extra contractors in the loop, and soldiers bouncing between disconnected screens. The new move is called “Right to Integrate,” or R2I, and it’s not a memo-writing exercise. Secretary of the Army Dan Driscoll and a group of major defense companies announced on May 5 that they’re starting a series of hackathon-style sprints, with the first one headed to Fort Carson, Colorado. ### What is the Army actually doing? Basically, it is forcing a live integration test. Instead of buying one more polished standalone system, the Army wants companies and soldiers in the same room trying to make existing gear and software exchange data, coordinate, and operate as part of one larger stack. The announced participants include Anduril, Boeing, General Dynamics, L3Harris, Leidos, Lockheed Martin, Northrop Grumman, Palantir, Perennial Autonomy, and RTX. (army.mil) ### Why is this a problem now? Because the Army’s procurement habits built silos on purpose, even if nobody called them that. Different programs bought “exquisite” systems optimized for their own mission, vendor, and budget line. The result was a force full of platforms that often needed manual, custom integration work — extra time, extra money, and field engineers stitching things together in ways that often broke. (army.mil) ### What makes R2I different? The catch is that this is not just a plea for better cooperation. Army CTO Alex Miller put a hard condition on participation: vendors need to expose their interfaces and documentation. In plain English, if a company keeps its software plumbing closed, the Army is signaling that the company may get locked out of the future ecosystem. That is a bigger shift than the word “hackathon” makes it sound. (army.mil) ### Why does Fort Carson matter? Fort Carson is where this stops being theory. DefenseScoop said the first event is planned there in the coming weeks, and other coverage says companies are expected to bring equipment, engineers, and technical support so Army teams can test current and future systems together. That matters because interoperability problems usually hide in the messy details — data formats, permissions, timing, radios, edge devices — not in PowerPoint. (defensescoop.com) ### Is this only about big primes? Not quite. The headline names are the giant contractors, but the ecosystem is already widening. Picogrid said on May 12 that the Army invited it to join the Fort Carson sprint too, which suggests the event is not limited to the original May 5 list. That fits the whole point of vendor-neutral interoperability — the Army wants more plug-and-play options, not just a cleaner version of the old prime-contractor club. (defensescoop.com) ### Why does Ukraine keep coming up? Because Ukraine turned open architecture from a nice idea into a combat lesson. The Army keeps pointing to Ukraine’s use of modular open systems and exposed APIs to connect drones, sensors, and firing platforms faster. That example gives Army leaders political cover to push industry harder — not as an abstract software reform, but as a wartime necessity. (financialcontent.com) ### So what’s the real stakes here? This is really a fight over control. For years, defense vendors gained leverage by owning closed systems and the expensive integration work around them. R2I tries to move that leverage back toward the Army by making interoperability a requirement, not an add-on. If it works, the service can swap in new autonomy, AI, sensing, or cyber tools faster. If it fails, it gets another layer of middleware and another decade of swivel-chair warfare. (army.mil) ### Bottom line The Army is treating integration as a weapon now, not an IT cleanup project. Fort Carson is the first real test of whether the service can make defense companies open up — and whether “open architecture” finally becomes procurement reality instead of conference language. (army.mil)
