Project Manager Battle Command
Encyclopedia
Project Manager Battle Command (or PM BC) develops, deploys and sustains integrated Battle Command software capabilities to the Army and Joint forces. PM BC supports the Warfighter by ensuring units are efficiently fielded, effectively trained and professionally supported. Successful implementation requires a disciplined and responsive development process that focuses on both near-term deliveries to current software baselines and longer-term development that sets conditions for enhanced Warfighter effectiveness. PM BC focuses its efforts on providing rapid delivery of capability to the field through software development, which allows constant interaction with the users to help maintain operational relevancy. These interactions have been vital to help identify and provide solutions to current challenges.

Mission


Provides Integrated Battle Command Capabilities, training and support to the Joint Land Component Warfighter. Project Manager Battle Command's (PM BC's) products enable Warfighters to plan and execute and synchronize tactical and operational warfighting functions to include maneuver, fires, sustainment, airspace management, and air defense. PM Battle Command also procures a common hardware computing baseline used by a broad range of Army products.

Colonel David M. Moore

Program Manager Battle Command




COL David Moore assumed command as the Project Manager, Battle Command in August 2007. PM Battle Command develops and sustains Army and Joint software command and control capabilities from tactical to strategic levels. The scope of PM Battle Command includes the life cycle management of software products that include Command Post of the Future (CPOF), Advanced Field Artillery Tactical Data System (AFATDS), Global Command and Control System – Army (GCCS-A), Battle Command Sustainment and Support System (BCS3), and a common software effort.




PM BC also serves as the Army’s Component Program Management Office for Joint Command and Control as well as manages the Army’s Common Hardware Systems procurement effort. COL Moore’s previous acquisition assignments have focused on warfighting solutions for combat vehicle, soldier equipment, and software command and control systems for the joint force and coalition partners.




PM Battle Command Family

PM BC provides many operationally relevant capabilities to the Warfighter. PM BC's product offices are Tactical Battle Command (TBC), Fire Support Command and Control (FSC2), Sustainment Command and Control (C2), Strategic Battle Command (SBC), Common Software (CS), Common Hardware Systems (CHS) and the Single Interface to the Field (SIF).



  • Tactical Battle Command (TBC) provides maneuver capabilities through products including Command Post of the Future (CPOF), Battle Command Common Services (BCCS), and Joint Convergence/Multilateral Interoperability Programme (MIP).


  • Fire Support Command and Control (FSC2) provides lethal and non-lethal fires through products including Advanced Field Artillery Tactical Data System (AFATDS), Joint Automated Deep Operations Coordination System (JADOCS), Pocket-Sized Forward Entry Device (PFED), Lightweight Forward Entry Device (LFED), CENTAUR (Lightweight Technical Fire Direction System) and Gun Display Unit- Replacement (GDU-R).


  • Sustainment Command and Control (C2) provides users with sustainment capabilities through products including Battle Command Sustainment and Support System (BCS3) and BCS3-Node Management (BCS3-NM).


  • Strategic Battle Command (SBC) provides operational and strategic tools through products including Global Command and Control System-Army, the Defense Readiness Reporting System-Army and Joint Command and Control.


  • Common Software (CS) eliminates redundancy in software development by ABCS systems through design and development of common, multiple user products. CHS provides state-of-the-art, interoperable, compatible, deployable, and survivable hardware and commercial-off-the-shelf software.


  • Single Interface to the Field (SIF) provides a synchronized baseline for the DoD and Army through a single access point on the SIF Portal where Warfighters and forward support have 24/7/365 support.

Major Initiatives

The Battle Command Collapse Strategy



Project Manager Battle Command (PM BC) launched the development of the Battle Command Collapse strategy during fall 2009. Its strategic intent is to shift from a Battle Command family of distinct applications with unique data storing and sharing mechanisms and collapse the fires, maneuver, sustainment, air defense and airspace management product lines towards a consolidated Battle Command product line. Through the BC Collapse strategy, PM BC intends to provide Warfighters with high-quality capabilities that enhance performance through technology while simultaneously reducing system complexity.




The Battle Command Collapse Strategy is composed of three primary efforts:

  • Battle Command Workstation: Future collaborative capabilities will be developed and deployed into a common Battle Command Workstation. The Battle Command Workstation will provide the foundation to be able to substantially increase the Maneuver Commander and staffs' ability to collaborate across a broad range of operations through development application.
  • Battle Command Web: The Battle Command Web BC Web thin client is standardized operating environment that provides visualization, collaboration and planning capabilities to the Warfighter. It allows for exposure of tactical data to include air space management, logistics, fires and enemy and friendly data. BC Web is expected to reduce the hardware footprint to increase sustainability and better efficiency for the Army
  • Information Infrastructure: PM BC is taking a unified approach to data handling and infrastructure procurement by consolidating the "back office" infrastructure consistent with Army Global Network Enterprise Construct (GNEC) strategy. PM BC expects this approach to reduce Army infrastructure cost and tactical server burden.

External links

The source of this article is wikipedia, the free encyclopedia.  The text of this article is licensed under the GFDL.
 
x
OK