FAS | Military | DOD 101 | Systems | Land Warfare |||| Index | Search | Join FAS

Battle Command Vehicle [BCV]

The BCV is intended to be a Commander's vehicle capable of receiving digitized data from both the TOC (Command & Control Vehicles) and from combat vehicles. At the Brigade and below, the BCV is intended to be a combat vehicle: a Bradley in an Infantry battalion or an M1 tank in an Armor battalion. The BCV would have the same visual signature and survivability as these combat systems. The BCV concept allows the commander immediate data to execute the battle and will exploit the power of the information age as a combat multiplier.

The BCV is to be the maneuver commander's mobile forward tactical command post. The interior of the vehicle will be configured to host the digitized devices necessary to provide data to execute the battle. In the offense, the BCV will move primarily during the execution phases of tactical missions traveling cross country. At other times it will remain as part of the brigade/battalion main command post. In the defense, it will be positioned to act as an information node and battlefield coordination center. The BCV carries five soldiers: driver, vehicle commander, unit commander, an operations officer, and an intelligence officer. The commander and staff will focus on operating digital and voice nets in the vehicle while the driver and track commander the normal duties of their positions. The BCV is a command and control platform; it is not a fighting vehicle.

The following describes how the BCVs will be outfitted:
               AN/VRC 92                          PLGR
               VIICS                              EPLRS
               MSRT  *                      Flat Panel Display
               FH MUX                          Applique V2
               FDR                             Applique V3
              Tactical Multinet Gateway           MCS/P
              CHS II Processor System          RACAL Radio

                  (* All MSRTs are supplied by the unit)

The Battle Command vehicle, Brigade and below will provide the commander with digital command and control with maneuver units and situational awareness. The Meshnet intercom system will be integrated into each of the BCVs. The BCV will be capable of sending and receiving data to the maneuver force vehicles as well as linking to the Army Tactical Command and Control System (ATCCS). The Bradley based BCVs will be configured and integrated identically with the exception of radio nets. The Brigade's four radios will be division command, division intel, brigade command, and brigade intel.. The battalion's nets are brigade command, brigade intel, and battalion command and a spare. The M1 based BCV will have the same architecture but will be configured differently due to the layout of the vehicle.

The M1 BCV is no longer a fighting vehicle. The cannon assembly, breech, and barrel will be removed and a fixed, non-firing barrel will be installed. With this exception, the Bradley BCV and the M1 BCV will have the same physical characteristics and performance specifications as the maneuver M1s and Bradleys.

Currently, the Armor Center is maturing the requirements for the BCV. PM C2V will implement overall program management of the BCV program under the guidance of the Mounted Battlespace Battle Lab (MBBL) at the Armor Center. United Defense is currently "building" the prototype vehicles based on the Bradley Fighting Vehicle for use by the Brigade Commander and the Infantry Battalion Commander and the M1 for use by the Armor Battalion Commander. PEO- C3S is coordinating to have the GFE sent to UDLP.

The three BCVs are currently being modified at UDLP. The vehicles are to be delivered to Ft Hood NLT 20 May 96. One Bradley BCV will go to the Brigade Commander while the other Bradley will go to the commander of 1-22 IN. The M1 BCV will be used by the commander of 3-66 AR.

Sources and Resources

FAS | Military | DOD 101 | Systems | Land Warfare |||| Index | Search | Join FAS

Maintained by Robert Sherman
Originally created by John Pike
Updated Saturday, September 12, 1998 6:35:55 AM