Force XXI Battle Command Brigade and Below

Force XXI Battle Command Brigade and Below
Name	Force XXI Battle Command Brigade and Below
Caption	FBCB2 display in a tactical operations vehicle
Developer	United States Army Research Laboratory; General Dynamics Land Systems; BAE Systems
Introduced	1990s
Status	In service
Platforms	M1 Abrams, M2 Bradley, M993 HMMWV, Stryker

Force XXI Battle Command Brigade and Below

Force XXI Battle Command Brigade and Below is a tactical digital command-and-control system fielded by the United States Army to support situational awareness, blue force tracking, and mission command at the brigade and below echelons. It integrates satellite navigation, datalinks, and mapping to improve decision-making for commanders, staff officers, and vehicle crews during operations such as those in Operation Iraqi Freedom, Operation Enduring Freedom (2001–present), and multinational exercises with NATO partners. The program linked research from the Army Research Laboratory, procurement by Program Executive Office Command, Control and Communications-Tactical, and industry implementation by firms including General Dynamics Land Systems and BAE Systems.

Overview

Force XXI Battle Command Brigade and Below was designed to provide near-real-time position reporting, messaging, and digital map overlays to formations from platoon to brigade. The system combined inputs from Global Positioning System receivers, radio networks like SINCGARS, and satellite terminals to present common operational pictures to commanders, joint staff elements, and coalition partners such as United Kingdom and Australian Defence Force units. It contributed to doctrinal shifts codified by Field Manual 3-0 and interoperability initiatives under Joint Chiefs of Staff guidance.

History and Development

Origins trace to experiments during the post-Cold War restructuring of the United States Army and the Force XXI modernization effort articulated by the Department of the Army and Army Chief of Staff. Early prototypes evolved from programs associated with Battle Command XXI demonstrations and trials at installations including Fort Hood and Fort Irwin. Contracts were awarded through competitive solicitations involving Science Applications International Corporation and other defense contractors. Fielding accelerated following lessons observed in the Gulf War (1990–1991) and requirements generated by combatant commands during the Balkans conflicts and later in Iraq War (2003–2011).

System Architecture and Components

The architecture integrated hardware, middleware, and applications running on ruggedized displays and embedded vehicle systems. Core components included the Blue Force Tracking client, mapping packages based on Vector Product Format datasets, and communications interfaces for networks such as Joint Tactical Radio System testbeds and legacy radios. Servers and gateways provided message routing and security services aligned with National Security Agency guidance and Defense Information Systems Agency standards. User devices were installed on platforms like the M1 Abrams and Stryker, and were supported by logistic nodes at brigades and corps levels.

Capabilities and Features

Capabilities encompassed position reporting, two-way text messaging, tasking and synchronization overlays, and integrated geospatial graphics for route planning and obstacle marking. Features supported coalition interoperability with translation layers compliant with Multilateral Interoperability Programme profiles and enabled collaboration with air assets coordinated through Air Operations Center procedures. The system supported tactical decision aids influenced by Mission Command doctrine and data sharing consistent with Net-centric principles promoted by defense acquisition reforms.

Deployment and Operational Use

Widespread deployment occurred across brigade combat teams during rotations to Kuwait and Iraq, where commanders used the system for convoy management, patrol coordination, and integration with unmanned aerial vehicles reconnaissance feeds. Units adapted the toolset during complex urban operations in cities such as Baghdad and Fallujah, and for stability tasks in Afghanistan. Integration with logistics and medical evacuation chains interfaced with Combat Lifesaver procedures and sustainment nodes under United States Army Materiel Command oversight.

Training, Support, and Maintenance

Training programs were run at centers including Fort Leavenworth and unit training centers, leveraging doctrine from Combined Arms Center curricula and simulations at the National Training Center. Field support and maintenance were provided by Program Executive Office elements and Original Equipment Manufacturer teams from General Dynamics and BAE Systems, with sustainment contracting managed through Defense Logistics Agency mechanisms. Lessons learned informed updates deployed via capability set releases and software refresh cycles overseen by acquisition offices.

Criticisms and Limitations

Critiques addressed bandwidth constraints on contested networks, cybersecurity vulnerabilities highlighted by cybersecurity incidents in operational environments, and the challenge of interoperability with rapidly evolving coalition systems. Analysts compared system performance against emerging architectures promoted by Defense Advanced Research Projects Agency prototypes and raised concerns about dependence on Global Positioning System signals in GPS-denied environments. Logistics and lifecycle costs were examined in studies by oversight bodies including Government Accountability Office.

Category:United States Army equipment Category:Command and control systems