What the first formations established
The Army's March 2025 account identifies three initial TiC brigades: 2nd Brigade Combat Team, 101st Airborne Division; 3rd Brigade Combat Team, 10th Mountain Division; and 2nd Brigade Combat Team, 25th Infantry Division. The approach placed technology with operational formations so soldiers could help determine how equipment and organizations should change. The 2nd Brigade of the 101st was the first selected. Army account.
That account also records an organizational observation worth retaining. Sergeant Major of the Army Michael Weimer reported that the 2nd Brigade had the division's highest retention and connected its demanding, purposeful work with positive morale. This is an attributed leadership observation, not a controlled study proving that increased tempo improves retention everywhere. Its practical implication is still useful: how soldiers participate in change matters alongside the equipment they receive.
TiC's contribution is a closer connection between the people using a capability and the people shaping its next version. That connection can expose training demands, support problems and differences between an intended workflow and the work a formation actually performs. It complements laboratory testing and engineering analysis rather than replacing them.
Combined Resolve made the integration work visible
Public records from Combined Resolve 25-2 at Hohenfels in May 2025 document several examples involving the 3rd Infantry Division. A May 17 caption shows 5-7 Cavalry soldiers operating a Skydio X10E4TT. Separate records show EnforceAir 2 counter-UAS training on May 6 and use of the Beast+ electronic warfare system on May 7.
Those records establish presence and use in an exercise. They do not, on their own, establish effectiveness against every relevant threat or prove which subsequent requirement changed because of a particular result. That distinction should carry into a supplier's account of its own participation.
The useful follow-up is specific: what configuration was evaluated, who operated it, what support was available, and which findings apply to the proposed delivery? A successful event with extensive vendor assistance can justify further work while leaving an important question about what the receiving unit can sustain on its own.
TiC 2.0 expands the organizational question
In a February 18, 2025 interview, Army Chief Technology Officer Alex Miller described the next iteration's emphasis on autonomy, including the objective of moving beyond a one-operator-to-one-system relationship. The reporting identifies a broader footprint including the 25th and 101st divisions, the 2nd Cavalry Regiment, 1st Brigade of the 3rd Infantry Division, and additional National Guard, aviation and logistics formations. These were the Army's stated plans and objectives at that point, not proof that every formation had already achieved the intended arrangement. Firsthand interview reporting.
For acquisition planning, the central issue is the burden placed on the organization. An individual system may demonstrate an impressive function while still requiring substantial specialist support, training or maintenance. A broader deployment must account for those obligations as well as the equipment itself.
The 101st's Multifunctional Reconnaissance Company illustrates the organizational experimentation. Its commander described a developing formation and capabilities during a public Army roundtable. Treating that experimental organization as a permanently settled structure would miss the point: TiC is also examining how people, responsibilities and technologies fit together.
Suppliers should therefore explain the personnel and support assumptions behind a demonstration. A claim about reduced operator burden is more useful when it includes the work transferred to maintainers, trainers or external support personnel. Moving the work elsewhere does not necessarily eliminate it.
PIT provides a transition path, not an automatic order
The Army's Pathway for Innovation and Technology is intended to connect promising technology with acquisition and fielding. In a May 19, 2026 explanation, the Army Acquisition Executive described a 12-to-18-month planned transition of mature, commercial-first capabilities to Portfolio Acquisition Executives. That is a program approach and target, not a guaranteed clock starting with any supplier's successful demonstration. Army acquisition explanation.
The published FY2026 priorities span autonomous counter-UAS, open command-and-control architectures, AI-enabled decision support and scalable electronic warfare. The Army also identifies autonomous breaching, terrain shaping and launched effects under All Arms Maneuver, and autonomous refueling, rearming and medical triage under Adaptive Sustainment. These dated priorities describe the scope of the effort; they do not constitute an award or universal product requirement. Army acquisition executive’s FY2026 priorities.
A transition discussion should connect four things:
- The supported need: What problem did the formation identify, and does the proposed increment address it?
- The evidence: Which results support the claim, with what configuration and limitations?
- The receiving organization: Who will own integration, training, maintenance and subsequent changes?
- The acquisition commitment: What funding, agreement and acceptance conditions actually exist?
These questions keep an accelerated pathway from being mistaken for an exemption from delivery planning. They also give a supplier a stronger basis for deciding what work to fund before a contract is available.
xTechOverwatch shows the opportunity and its limits
The official November 14, 2025 account reports that xTechOverwatch brought 40 selected teams to the Bush Combat Development Center in Bryan, Texas, on October 27–29. Twenty teams were chosen for continued work with TiC formations, with engagement planned from January 2026 through July 2027. Those are reported competition outcomes and a planned engagement period. Official competition account.
The funding description also needs precision. The program advertised $1 million in cash prizes and opportunities to submit Direct to Phase II SBIR proposals of up to $2 million each, with $40 million in potential follow-on awards. The opportunity to propose for follow-on work is not evidence that the entire amount was already awarded or spent. Army SBIR announcement.
Sustained formation engagement can help participants understand the customer and build a useful performance record. It does not establish that every later competition is closed to outsiders or that one cohort's experience determines every PIT decision. Contractors should pursue the relevant published opportunity and distinguish access to experimentation from a procurement commitment.
The wider innovation effort provides additional context. In July 2026, the Army reported more than 1,800 Catalyst submissions, 26 Pathfinder projects and 36 academic and small-business partners. The same account described field testing across several commands and BISON, the Buildable Innovation Shop for Operational Needs, supporting exercises and being fielded across commands including CENTCOM and Special Forces. That is an ongoing fielding description, not confirmation of completed adoption everywhere. Army innovation account.
BISON's manufacturing and repair role highlights a practical acquisition point: a useful product can depend on an equally useful support arrangement. The receiving organization needs to know how that arrangement will be delivered, staffed and maintained.
Electronic warfare adds integration responsibilities
May 2025 reporting, based on an Army spokesperson's explanation, described planned TLS-EAB prototype configurations for divisions, corps and Multi-Domain Task Forces, with choices tailored to echelon and theater. It supports a picture of evolving equipment and organizational needs. It does not establish that higher-echelon EW support has become obsolete or that every formation requires the same structure. Army spokesperson's account.
For suppliers, the relevant acquisition question is whether the proposed capability can be integrated and supported within its intended environment. Exercise findings can contribute important evidence, but they should remain connected to the tested configuration and conditions. Laboratory work, simulation, safety assessment and other applicable assurance processes retain their roles.
The support discussion should identify external dependencies and the responsibilities of each party. A product may rely on a vendor for particular updates or repairs; that dependence needs to be visible in the delivery plan. It is not sound to assume that every external support requirement automatically disqualifies a technology, or that a successful exercise makes the dependency disappear.
Build a transition case the customer can inspect
For a contractor, the most useful next step is to prepare a short transition record alongside the technical description. It should connect the product's demonstrated value to the work still required for delivery. This is a practical recommendation, not an assertion that the Army mandates a single document format.
- State the claim at the demonstrated scope. Identify the configuration, users and conditions behind it. Separate measured findings from expectations about broader deployment.
- Preserve the unresolved findings. A limitation that affects integration or support belongs in the transition discussion, with an owner and a proposed way to resolve it.
- Account for the whole support burden. Include training, maintenance, update responsibilities and any vendor presence assumed during evaluation.
- Show what changes at the next increment. A new configuration or receiving formation may require renewed evidence. Earlier results are valuable when their applicability remains clear.
- Separate interest from commitment. Record the actual agreement, funded work and decision still pending. Customer enthusiasm is valuable; it is not an appropriation or contract.
This approach also improves the decision to defer or narrow a transition. A capability may be useful but require more integration work than the proposed schedule allows. A smaller increment can be sensible when it delivers a supported benefit and preserves a credible route forward. Conversely, continuing demonstrations without resolving a known support problem can consume time without improving readiness for acquisition.
TiC gives the Army and industry a stronger opportunity to learn together. The supplier's contribution is to turn that learning into a clear, supportable proposition: what works, what remains uncertain, and what the customer would need to take the next step.
Spartan X's engineering, AI assurance and program experience are relevant at that transition, where technical promise must be matched with integration evidence, realistic support and a delivery plan the receiving organization can use.
Sources and further reading
- Army: Transforming in Contact alters Army in unexpected ways
- Army acquisition executive: Pathway for Innovation and Technology
- Army: establishing PIT and its priorities
- DVIDS: xTechOverwatch competition outcomes
- Army SBIR: xTechOverwatch prize and follow-on opportunity
- Army: Catalyst, Pathfinder and Accelerating FORCE
- DefenseScoop: February 2025 interview on TiC 2.0
- DefenseScoop: May 2025 Army explanation of EW prototypes
