Battle Command System (FBCB2)

Battle Command System (FBCB2)
Name	Force XXI Battle Command Brigade and Below (FBCB2)
Developer	United States Army Tactical Command, Control and Communications (TAC), United States Army Training and Doctrine Command contractors
Released	1990s
Platform	Vehicular computers, ruggedized laptops, handhelds, satellite terminals
Status	In operational use

Battle Command System (FBCB2)

FBCB2 is a tactical Battlefield command-and-control system fielded to enhance situational awareness for United States Army and allied units. It provides a digital common operating picture linking brigade and lower elements, integrating position reports, orders, and sustainment data across maneuver, fires, intelligence, and logistics nodes. Developed during the late Cold War and refined through operations in Operation Desert Storm, Iraq War, and Operation Enduring Freedom, FBCB2 influenced subsequent programs such as Blue Force Tracking and networked architectures used by NATO partners.

Overview

FBCB2 delivers a map-based display showing friend and foe icons, maneuver graphics, and logistical overlays to commanders from brigade to squad. The system fuses inputs from GPS receivers, terrestrial radios, and satellite communications including Defense Satellite Communications System relays to create a shared picture for platforms such as M1 Abrams, Bradley Fighting Vehicle, Stryker, and HMMWV. Software development followed standards influenced by Joint Tactical Radio System concepts and contributed to doctrine promulgated by TRADOC and combatant commands like United States Central Command.

History and Development

Concepts leading to FBCB2 originated in experiments by United States Army Forces Command and research at U.S. Army Research Laboratory during the late 1980s. Early prototypes were trialed during exercises such as REFORGER and refined after lessons from Operation Just Cause and Gulf War (1990–1991). Acquisition involved industry partners including General Dynamics, Raytheon, and smaller contractors who produced rugged hardware and mapping clients. Fielding accelerated in the 1990s with the Army’s digitization initiatives and was iteratively updated after feedback from units deployed to Bosnia and Herzegovina, Kosovo, and later to Iraq and Afghanistan.

System Architecture and Components

The architecture comprises vehicle-mounted battle command units, dismounted handsets, server nodes, and network gateways. Core components include map clients, messaging brokers, position reporting modules, and database engines that manage icons, graphics, and messages. Communications nodes implement wide-area links via UHF satcom and line-of-sight radios like the AN/VRC-92 family, while terrestrial mesh and point-to-point links support short-range exchanges. Interfacing with sensors employs standards from Defense Information Systems Agency and interoperability layers aligned with North Atlantic Treaty Organization data formats adopted by partner militaries.

Capabilities and Features

FBCB2 provides real-time blue force tracking, text and graphical messaging, ground- and air-asset coordination overlays, and digital logistics status. It supports geospatial products such as overlays of urban terrain, choke points, and route corridors relevant to units like 101st Airborne Division and 3rd Infantry Division. Commanders use cursor-on-target style graphics for close air support coordination with units of United States Air Force and artillery coordination with United States Army Field Artillery. The system also records track histories for after-action review used by organizations such as Combined Arms Center and unit training commands.

Operational Use and Doctrine

Doctrine for employment arose from operational testing and was codified in manuals and tactical publications used by brigade combat team staffs. FBCB2 supported mission command principles as exercised in combined operations alongside United Kingdom Armed Forces, Canadian Army, and other coalition partners. Units employed FBCB2 for route planning, supply convoys protection, and coordination of maneuver during urban operations in cities such as Fallujah and Kandahar. Training institutions integrated the system into simulations run at centers like National Training Center and Joint Readiness Training Center to refine command procedures and decision cycles.

Interoperability and Integration

Designed to exchange data with allied battle management systems, FBCB2 implemented gateways to NATO protocols and proprietary interfaces for platforms including Stryker Combat Vehicle systems and aviation assets like AH-64 Apache. Integration efforts connected the system to logistics information systems and intelligence feeds from organizations such as National Geospatial-Intelligence Agency and Defense Intelligence Agency. Coalition interoperability initiatives drove adoption of common symbology and messaging standards to enable combined operations with forces from Australia, Germany, France, and other partner nations.

Limitations and Criticism

Critics cited bandwidth constraints, reliance on GPS, and vulnerability to electronic attack as operational limitations during high-intensity conflicts. Early iterations faced usability issues leading to cognitive overload for crews in heavy fighting reported by units such as 1st Infantry Division. Data overload and network congestion required doctrinal workarounds adopted by commanders at III Corps and other formations. Privacy and operational security concerns were raised when positional data reached unintended audiences during coalition operations, prompting policy changes and technical mitigations across programs of record.

Category:Military equipment of the United States Category:Command and control systems