OFFSETOFFSET

Army_Futures_Command

4 min read

United States Army Futures Command

INACTIVE. AFC was the Army command created in 2018 to fix Army modernization by pulling requirements generation out of TRADOC and putting it next to commercial technology in Austin. It ran the Cross_Functional_Teams and owned the six Army_Modernization_Priorities. The Army_Transformation_Initiative merged it back into TRADOC on October 1, 2025. Its successor is T2COM. This page exists because AFC-era program lineage, requirements documents, and org references are still live in contracts and budget justification books.

FieldValue
TypeArmy Command (ACOM), inactivated
HeadquartersAustin, Texas
EstablishedInitial operations July 1, 2018; formally activated August 24, 2018
InactivatedOctober 2, 2025 (merger effective October 1, 2025)
SuccessorT2COM
Subordinate toUS_Army / Headquarters, Department of the Army

Commanding Generals

CommanderTenure
John_M_Murray, GeneralAugust 24, 2018 to December 3, 2021
James_M_Richardson, Lieutenant General (acting)December 3, 2021 to October 4, 2022
James_E_Rainey, GeneralOctober 4, 2022 to October 2, 2025

Mission

AFC was chartered to shorten the distance between an operational problem and a fielded solution. Its specific fixes to the pre-2018 system:

  • Pull requirements out of the schoolhouse. Requirements development moved from TRADOC Capability Development Integration Directorates to AFC, on the theory that the institution that trains on legacy equipment should not be the institution defining its replacement.
  • Compress JCIDS timelines. Cross_Functional_Teams were given general officer leads reporting directly to the AFC commander, with authority to iterate requirements against prototypes rather than write a document and hand it off.
  • Locate outside the defense corridor. Austin was chosen deliberately to reach commercial software, autonomy, and hardware firms that did not orbit the Pentagon.
  • Own a science and technology enterprise. DEVCOM and the Army Research Laboratory moved under AFC.

Legacy Structure

  • Cross_Functional_Teams (eight at stand-up, later ten): the modernization delivery mechanism, each aligned to a priority area.
  • Futures and Concepts Center: concepts, force design, and the Capability Development Integration Directorates. Now Futures_and_Concepts_Command.
  • Combat Capabilities Development Command (DEVCOM): the Army’s S&T laboratories and engineering centers.
  • Army Applications Laboratory, Army Software Factory, and the Austin-based commercial outreach organizations.

Why it was merged away

The Army_Transformation_Initiative rationale, stated by Randy_George and Dan_Driscoll in May 2025, was that splitting requirements from doctrine and training produced capabilities the institutional Army could not absorb: a CFT could deliver a system without the tactics, formation design, or training base to employ it. Merging AFC back into TRADOC put “design, build, doctrine and training” under one headquarters. The merger also served the Secretary of War’s directed reduction in four-star billets, since it collapsed two four-star commands into one.

Critics of the merger, including members of Congress who wrote to the Army about it, argued that the 2018 separation existed precisely because TRADOC had been slow, and that reabsorbing AFC risked recreating the problem AFC was built to solve.

Why it matters

Requirements documents survive the org chart. Capability Development Documents, Abbreviated CDDs, and directed requirements written by AFC CFTs between 2018 and 2025 still govern programs of record. A vendor reading a program’s requirement baseline is often reading an AFC artifact, validated under an authority that no longer exists.

AFC-era vehicles are still in use. The Army Applications Laboratory, the xTech prize competitions, and the OTA consortia AFC stood up did not disappear with the command. Their institutional home moved to T2COM and ASAALT’s Pathway for Innovation and Technology (PIT).

The Austin thesis outlived the command. T2COM is headquartered in Austin. The commercial-outreach posture that justified AFC’s creation is now the posture of a much larger organization.

Program lineage matters for budget work. Program elements and procurement lines carrying AFC-era justification language are still funded. Reading a program element narrative that cites a CFT is a signal that the requirement predates the current portfolio structure and may be exposed to re-validation.

See Also

Graph View

Backlinks