Battle command explained

Battle command (BC) is the discipline of visualizing, describing, directing, and leading forces in operations against a hostile, thinking, and adaptive enemy. Battle command applies leadership to translate decision into actions, by synchronizing forces and warfighting functions in time, space, and purpose, to accomplish missions.[1] [2] [3] Battle command refers both to processes triggered by commanders and executed by soldiers and to the system of systems (SoS) that directly enables those processes.[1]

Alternate definition

FM 100.5BC is defined as the art of battle decision-making, leading, and motivating soldiers and their organizations into action to accomplish missions. BC includes visualizing the current state and future state, formulating concepts of operations to get from one to the other, and doing so at least cost. Assigning missions, prioritizing and allocating resources, selecting the critical time and place to act, and knowing how and when to make adjustments during the fight are also included.[4]
FM 7-30BC is the art and science of battlefield decision making and leading soldiers and units to successfully accomplish the mission. The BC basic elements are decision making, leading, and controlling. The BC System of Systems at brigade level enables commanders to lead, prioritize, and allocate assets required to employ and sustain combat power. The brigade commander must see further, process information faster and strike more precisely and quicker. If information is the medium of the BC process, the BC system must provide the commander with timely and accurate information on which to base the commander's decision.[5]

Synonyms

BC is also known by the following terms:

Battle management

Battle management (BM) is the management of activities within the operational environment based on the commands, direction, and guidance given by appropriate authority. BM is considered to be a subset of BC.[6] [7]

Processes

Business processes associated with command and control[8] of military forces are detailed in various publications of the United States Department of Defense.[2] [9]

System of systems

Modern BC software and hardware exhibit all of the traits and qualities of an SoS.[10] A BC SoS can be decomposed into systems such as maneuvers, logistics, fires and effects, air support, intelligence, surveillance, reconnaissance (alternatively recognizance) (these three sometimes grouped as ISR, or by adding target acquisition, ISTAR), terrain, and weather.[11] [12] [13] Among the many inputs of these systems is a plethora of sensors which undergo sensor fusion and are compiled into a common operational picture/local operational picture that enable commanders to achieve situational awareness (SA)/situational understanding (SU). SA/SU is paramount for commanders to command and control modern military forces.

Military acquisition in the United States

The Department of the Army organization primarily responsible for the acquisition of the BC SoS is the PM BC, a subordinate organization within the PEO C3T.

Types

Battle command on the move (BCOTM)

One of the problems with BC SoS is that a commander has little communication while in the battlefield. Command and control planning occurs at a command post (CP) or tactical operations center (TOC). Once a battle begins, a commander leaves the CP/TOC and moves forward to stay engaged. A commander has limited communication possibilities while in the battlefield, making it difficult to follow and control all events as they happen. Battle command on the move (BCOTM) is a capability that provides commanders all of the information resident in their CP/TOC and the required communications necessary to command and control on the move, or at a short halt, from any vantage point on the battlefield.[14] [15]

Airborne battle command

Example airborne systems that contribute to BC:

See also

Notes

  1. Web site: United States Army Functional Concept for Battle Command - 2015-2024. TRADOC Pamphlet 525-3-3. 1.0. 30 April 2007 . dead . https://web.archive.org/web/20070614100805/http://www.tradoc.army.mil/tpubs/pams/p525-3-3.pdf . 2007-06-14 .
  2. Book: United States Department of the Army#Headquarters, Department of the Army

    . Headquarters, Department of the Army . United States Department of the Army#Headquarters, Department of the Army . . 14 June 2001 . Washington, DC . . 50597897.
    — Book: Part A: Begin – Chapter 4 . https://web.archive.org/web/20070714135134/http://www.dtic.mil/doctrine/jel/service_pubs/fm3_0a.pdf . 14 July 2007 . dead . 19 August 2013 .
    — Book: Part B: Chapter 5 – Chapter 9 . https://web.archive.org/web/20070714135134/http://www.dtic.mil/doctrine/jel/service_pubs/fm3_0b.pdf . 14 July 2007 . dead . 19 August 2013 .
    — Book: Part C: Chapter 10 – End . https://web.archive.org/web/20070714135134/http://www.dtic.mil/doctrine/jel/service_pubs/fm3_0c.pdf . 14 July 2007 . dead . 19 August 2013 .

  3. "Studies in Battle Command", United States Army Command and General Staff College, 17 April 2006 http://www.au.af.mil/au/awc/awcgate/army/csi-battles.htm
  4. [List of United States Army Field Manuals#FM 100-5|"Operations", FM 100–5]
  5. "The Infantry Brigade", FM 7-30, Headquarters Department of the Army, 3 October 1995 http://www.globalsecurity.org/military/library/policy/army/fm/7-30/index.html
  6. In some contexts (e.g. BMC3 and C2BM), BM appears to be distinct from command and control. In other contexts (e.g. Battle management command), BM appears to be a subset of command and control.
  7. "DoD Dictionary of Military and Associated Terms", Joint Publication 1-02, DoD, 17 March 2009 Web site: Archived copy . 2007-10-01 . dead . https://web.archive.org/web/20091108082044/http://www.dtic.mil/doctrine/jel/new_pubs/jp1_02.pdf . 2009-11-08 .
  8. Builder, Carl H., Bankes, Steven C., Nordin, Richard, "Command Concepts — A Theory Derived from the Practice of Command and Control", RAND,, 1999 http://www.rand.org/pubs/monograph_reports/2006/MR775.pdf
  9. "Joint Operations", Joint Publication 3-0, Joint Chiefs of Staff, DoD, 13 February 2008 http://www.dtic.mil/doctrine/jel/new_pubs/jp3_0.pdf
  10. Boardman, John, DiMario, Michael, Sauser, Brian, Verma, Dinesh, "System of Systems Characteristics and Interoperability in Joint Command and Control", Defense Acquisition University, 25–26 July 2006 Web site: Archived copy . 2009-07-20 . dead . https://web.archive.org/web/20110719123741/http://www.sosece.org/pdfs/2ndConference/Presentations/SoSECE%20Howell%20Day%20One/DiMario.pdf . 2011-07-19 .
  11. Collins, Marie, Pete, Dugan, "Army Battle Command System Overview", MITRE, 13 March 2002 http://www.slideworld.com/slideshows.aspx/Army-Battle-Command-System-Overview-ppt-794255
  12. Meilich, Abe, "Capturing the Army Battle Command System (ABCS) Architecture Using the C4ISR Architecture Framework", Lockheed Martin, 8 May 2002 http://www.ngtservices.com/Documents/ArmyBattleCommandArchitectureFramework.pdf
  13. Moore, David, "Command and Control Roadmap", AFCEA, Project Manager Battle Command, 20 August 2008 Web site: Archived copy . 2009-07-21 . dead . https://web.archive.org/web/20110919232004/http://www.afcea.org/events/pastevents/documents/Track7Session3.ppt . 2011-09-19 .
  14. Young, Rodney, Morley Rebecca, "Battle Command On The Move", CERDEC, 4 November 2005, https://web.archive.org/web/20110604202148/http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA432738&Location=U2&doc=GetTRDoc.pdf
  15. [Raymond T. Odierno|Odierno, Raymond T.]

External links

This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "Battle command".

Except where otherwise indicated, Everything.Explained.Today is © Copyright 2009-2024, A B Cryer, All Rights Reserved. Cookie policy.