1 / 20

Command and Control Roadmap

UNCLASSIFIED. . PURPOSE: To provide a overview of the Army's path forward to Unified Battle CommandOBJECTIVES: By the end of this presentation you will be able to: A. Understand the Army's definition of the Battle Command Essential Capabilities B. Understand the Army's intent in pursuing UBCC. Be aware of opportunities and challenges in achieving UBC.

jedidiah
Download Presentation

Command and Control Roadmap

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Command and Control Roadmap Session 3 20 August, 0930-1030

    2. PURPOSE: To provide a overview of the Army’s path forward to Unified Battle Command OBJECTIVES: By the end of this presentation you will be able to: A. Understand the Army’s definition of the Battle Command Essential Capabilities B. Understand the Army’s intent in pursuing UBC C. Be aware of opportunities and challenges in achieving UBC

    3. COL David Moore (PEO C3T PM BC) Battle Command Essential Capabilities UBC Overview UBC TOC Activities Mr. Eric Goodman (FCS PM BC) FCS Refresher UBC Platform Activities UBC System Engineering Tasks Mr. Michael Anthony (CERDEC C2D) UBC Organization and 120 Day Study S&T Investment in Meeting UBC Needs

    4. Genesis of the Current Effort The VCSA convened a series of four C4ISR Summits to holistically address problem areas in the programmatic execution for Army Battle Command The Army was creating three different forces – FCS – Maneuver Brigade Combat Teams – and everyone else Were not designing for interoperability and backwards compatibility Not all parts of the force would receive improved capability (non FCS or non Maneuver BCTs thus creating “haves” and “have-nots”) We were building duplication and hence not affordable Summit II proposed a concept – Unified Battle Command (UBC) as a solution to address the above problems UBC is a Strategy NOT a product or Program of Record (POR) Uses a System of Systems Approach Represents a federation of Battle Command Applications designed to deliver a suite of consistent Battle Command functions for the entire force Is a component of the overall Army LandWarNet / Battle Command Strategy Tasking from Summit III – Review the 7+1 Commander’s Needs Determine the essential Battle Command information and functions that must be digitally compatible between multiple versions and types of applications via the network

    5. The Critical Path to UBC A robust communications network interoperable across tiers (air, ground, & satellite) Connects leaders and soldiers to the network via multiple paths Extend the network to sensors and lower tactical elements Supports Major Combat Operations (MCO) and Stability Operations (SO) Expands or extends to meet commander’s priorities A suite of integrated Battle Command applications Tailorable to the mission of the Cdr and Functional Staff Display information on a common geospatial reference BC Data/information is stored and shared in common formats Using a common user interface – look and feel Collaboration (in multiple forms) from command posts to Leaders and Soldiers Rich Command Post Collaborative Environment at BDE – Battalion - Company Lesser collaboration environment Company-Platoon-Squad-Team-Soldier

    6. Cdr and Universal Needs to Achieve Essential BC Capabilities

    7. Unified Battle Command Vision (briefed to VCSA)

    8. UBC Long-term Schedule

    9. TOC Near-Term Challenges

    10. TOC Near-Term Pilot Efforts

    11. Mr. Eric Goodman (FCS PM BC) FCS Refresher UBC Platform Activities UBC System Engineering Tasks

    12. Army’s Future Combat System (Networked Battle Command) Common Operating Environment SOSCOE supports net-centric services for a variety of platforms Weapons (safety critical /real-time operations) Future Force Manned Systems (Vehicle) Infrastructure Services Unattended Systems Connectivity Networked Battle Command Infrastructure Services One Battle Command Application Role Based Functionality Situational Awareness & Collaboration Vehicle Systems / Weapon Platform Control Unmanned Systems Control Sensor Control & Data fusion System Status & Logistics Embedded Training

    13. FCS Battle Command (with Embedded Training / M&S)

    14. Notional SW Contribution to UBC Platform

    15. Notional Converged Platform SW Arch

    16. Mr. Michael Anthony (CERDEC C2D) UBC Organization and 120 Day Study S&T Investment in Meeting UBC Needs

    17. Objective: Develop a 2013 UBC Initial Operating Capability (IOC) with enough detail to inform the 2011-2015 Mini-POM and ARFORGEN Capability Set development 120 Day UBC Study Objective

    18. Develop and demonstrate multi-platform, cross community applications and software services to facilitate the unification of Battle Command S&T Investment

    19. Demonstrate feasibility of using “WMI” in non-FCS environment Develop approaches for JCR visualization built from FCS WMI components JCR Infrastructure dependencies & alternatives Examine SOSCOE Services that could/should be integrated in JCR/JBC-P Collaboration Universal Collaboration Bridge to interface different collaboration systems Participate in BC Net-centric Pilot Develop open framework for 3rd party collaboration developers COBRA Near-term: Prototyping

    20. COBRA Mid-Term: Products Multi-platform, cross-community applications and software services Collaboration Services Decision Support Software Products Planning Support Services Priority Information Requirements (PIR) Management Tools Collection / Sensor Management Tools Commercial/Joint Mapping Tool Kit (C/JMTK) Enhancements Unified net-centric data strategies Common architecture and framework across Intel/Ops/Geo communities

    21. Context has been set with the updated statement of the Commanders Needs UBC Represents a federation of Battle Command Applications designed to deliver a suite of consistent Battle Command functions for the entire force Challenges are management, system-of-system, and technical

More Related