Battle command
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
[edit]- FM 100.5[further explanation needed]
BC 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-30[further explanation needed]
BC 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
[edit]BC is also known by the following terms:
Battle management
[edit]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.[nb 1][6]
Processes
[edit]Business processes associated with command and control[7] of military forces are detailed in various publications of the United States Department of Defense.[2][8]
System of systems
[edit]Modern BC software and hardware exhibit all of the traits and qualities of an SoS.[9] 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.[10][11][12] 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
[edit]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
[edit]Battle command on the move (BCOTM)
[edit]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.[13][14]
Airborne battle command
[edit]Example airborne systems that contribute to BC:
See also
[edit]- 505th Command and Control Wing
- Battle management language
- C4ISTAR
- Command and control (military)
- Command and Control Research Program
- Command and control warfare
- Command center
- Command ship
- Common operational picture
- Future Combat Systems manned ground vehicles
- Global Command and Control System
- Global Information Grid
- Joint Force Air Component Headquarters
- Joint Interoperability of Tactical Command and Control Systems
- Local operational picture
- NATO Communications and Information Systems Agency
- NATO Consultation, Command and Control Agency
- NORAD
- Program Executive Office Command Control and Communications Tactical
- Project Manager Battle Command
- Project Manager Force XXI Battle Command Brigade and Below
- Staff (military)
- Worldwide Military Command and Control System
- Mobile Modular Command and Control (M2C2) program
Notes
[edit]- ^ 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.
References
[edit]- ^ a b "United States Army Functional Concept for Battle Command - 2015-2024" (PDF). 1.0. 30 April 2007. TRADOC Pamphlet 525-3-3. Archived from the original (PDF) on 2007-06-14.
- ^ a b Headquarters, Department of the Army (14 June 2001). FM 3–0, Operations. Washington, DC: GPO. OCLC 50597897.
— Part A: Begin – Chapter 4 (PDF). Archived from the original (PDF) on 14 July 2007. Retrieved 19 August 2013.
— Part B: Chapter 5 – Chapter 9 (PDF). Archived from the original (PDF) on 14 July 2007. Retrieved 19 August 2013.
— Part C: Chapter 10 – End (PDF). Archived from the original (PDF) on 14 July 2007. Retrieved 19 August 2013. - ^ "Studies in Battle Command", United States Army Command and General Staff College, 17 April 2006 [1]
- ^ "Operations", FM 100–5, Headquarters Department of the Army, June 1993 [2] Archived September 26, 2006, at the Wayback Machine
- ^ "The Infantry Brigade", FM 7-30, Headquarters Department of the Army, 3 October 1995 [3]
- ^ "DoD Dictionary of Military and Associated Terms", Joint Publication 1-02, DoD, 17 March 2009 "Archived copy" (PDF). Archived from the original (PDF) on 2009-11-08. Retrieved 2007-10-01.
{{cite web}}: CS1 maint: archived copy as title (link) - ^ Builder, Carl H., Bankes, Steven C., Nordin, Richard, "Command Concepts — A Theory Derived from the Practice of Command and Control", RAND, ISBN 0-8330-2450-7, 1999 [4]
- ^ "Joint Operations", Joint Publication 3-0, Joint Chiefs of Staff, DoD, 13 February 2008 [5] Archived 2008-12-02 at the Wayback Machine
- ^ 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 "Archived copy" (PDF). Archived from the original (PDF) on 2011-07-19. Retrieved 2009-07-20.
{{cite web}}: CS1 maint: archived copy as title (link) - ^ Collins, Marie, Pete, Dugan, "Army Battle Command System Overview", MITRE, 13 March 2002 [6]
- ^ Meilich, Abe, "Capturing the Army Battle Command System (ABCS) Architecture Using the C4ISR Architecture Framework", Lockheed Martin, 8 May 2002 [7]
- ^ Moore, David, "Command and Control Roadmap", AFCEA, Project Manager Battle Command, 20 August 2008 "Archived copy". Archived from the original on 2011-09-19. Retrieved 2009-07-21.
{{cite web}}: CS1 maint: archived copy as title (link) - ^ Young, Rodney, Morley Rebecca, "Battle Command On The Move", CERDEC, 4 November 2005, [8]
- ^ Odierno, Raymond T., Erickson, Edward J., "The Battle of Taji and Battle Command on the Move", Military Review, July–August 2003 [9]