fire commander 2 program functions level 3

To help dispel some of that fog and friction, this paper beseeches C2 practitioners, customers, and developers to return to the use of precise, doctrinally grounded terminology by offering a very simple definition of C2, by describing the relationship between battle management and C2, and by differentiating C2 from other warfighting functions. One source of this fog and friction is the common mischaracterization of C2 and its conflation with related functions. There is a lot of fog and friction, and that fog and friction can lead to redundant, duplicative, and sometimes unnecessary research, experimentation, and testing that comes at a high dollar cost and an even higher opportunity cost.

With all this upheaval, it is tough to keep track of who is doing what to modernize command and control. The Air Force is also deep in the throes of overhauling its tactical command and control platforms by divesting their legacy Joint Surveillance Target Attack Radar System (JSTARS) and replacing their Airborne Warning and Control System (AWACS) with the more modern E-7 Wedgetail, while at the same time advancing their Tactical Operations Center (TOC) family of systems concept. In turn, all the military services have programs nested under JADC2: for the Department of the Air Force, it is the Advanced Battle Management System (ABMS) for the Department of the Army, it is Project Convergence for the Department of the Navy, it is Project Overmatch. The Joint Staff is investing heavily in the Joint All Domain Command and Control (JADC2) program, which is designed to accelerate commanders’ decision cycles and close operational gaps. There’s never been a better time to be in the Command and Control (C2) business.

Fire commander 2 program functions level 3