Future Battle Command: Geospatially-Enabled ESRI Federal User Conference 21 February, 2008 John J. Day Director, Defense Business Development ESRI, Inc. 1
Outline Geospatially-enabled Battle Command What is the Challenge? Why Is It Desirable? How Is It Feasible? Meeting Key Challenges What Does This Mean For Operations? Demonstration: Soldier As A Sensor Where Is It In Operation? What Are the Implications? 2
What is the Challenge? Exploit the power of GIS technology to substantially increase the effectiveness quality, timeliness, and efficiency of military operations by Geo-enabling mainstream, general purpose, integrated information management applications to better support distributed operations under demanding conditions C2 Services GIS Services M&S Services exploiting, and ultimately, supplanting, ancillary, special purpose, discrete information management systems. C2 Geo M&S 3 ESRI 2008
Geospatially-enabled Battle Command: Military Decision Making Process (MDMP) Observe, Orient, Decide, Act (OODA) Loop Adaptive Planning Integrated with Execution COA Development IPB Wargame Prediction & Planning Mission Analysis Commander Envisions and Decides FRAGO WngO Strike OPORD Execution 4
Why Is It Desirable? Quality, Timeliness, Information Integration Analysis/Workflow Visualization More than maps and imagery a foundation for mission planning and execution Common Operating Picture and Efficiency 5
!.!. Army Applications Integrated Information Products Tier 1 impact of terrain and weather on military operations independent of mission OCOKA Obstacles, Cover and Concealment, Observation, Key terrain Maneuver Networks Weather impacts on mobility and sensor performance Tier 2 - for performing well defined military tasks or actions consistent with a mission or objective Routes / Axis of Advance Battle, Attack, Assault and Attack by Fire and Indirect Fire Positions Assembly and Engagement Areas Tier 3 - for performing well defined military tasks or actions based upon known or predicted situation Products selected as part of the OPLAN and OPORD Off- and On-Road Connected Graph Observation & Fields of Fire 2525B Symbology Directional Concealment Direct Fire Positions Route Assessment Axis of Advance Attack By Fire Positions Control Graphics Information and graphics courtesy of U.S. Army Topographic Engineering Center 6
How Is It Feasible? Core infrastructure advance Advent of web services and the SOA Development of enterprise GIS product platform Rich, smart clients Flexible and powerful data management Computational flexibility client, server, embedded Capture and use of tradecraft Strong support for interoperability 7
Enabling Infrastructure Technology Developments in Faster Processing Multi-core, Blades Increased Bandwidth Larger Storage Web Services Standards Mobile Technologies Real Time Networks accommodate GIS demands Desktop Laptop PDA Servers Web Services Phone Scalable Networked Hardware Unique imagery and mapping content, and a variety of data models/formats Very large, distributed databases Legacy systems built around computing and integration constraints... and support integration in mainstream applications 8
Advent of Web Services and the SOA Delivering Agility: Rapid development and legacy integration, lower costs, collaboration, interoperability 2-D Viewers 3-D D Viewers Rich Internet Client Presentation Integration Platform App Catalog Globe Map & Chart Image- Process Geo- Process Open Web Tracking & RSS Serving/ Publishing Map of the business expressed in technology CIO Magazine Data Authoring and by decoupling information, business logic, and presentation enabling flexible management of data and applications in accordance with infrastructure constraints, especially bandwidth. 9
Advancing GIS Technology Integrated Platform... On the Desktop, Server, or Embedded Desktop Web Mobile Open APIs OGC KML SOAP SQL Google Earth AutoCAD Interoperable CAD KML BAE LEICA Image Integration GIS Services Metadata ISO 19139 Ionic SOAP, XML, SQL MapInfo SAP GeoMedia Any DBMS ArcGIS Server OGC Standards WMS/WFS/GML GDB ArcGIS Server ArcIMS ArcSDE Image Server Tracking Server ArcGIS Engine Distributed data management Headquarters Field Region Local... enabling Enterprise GIS 10
Commercial Joint Mapping ToolKit (CJMTK) Standard COTS Software Tools/Architecture for C2 Applications Mapping, Charting, Geodesy, and Imagery (MCG&I) functionality for NCES/NCW - all DoD C2I systems Standard Visualization Platform for imagery and geospatial data Desktop & Server software licensed by NGA through 2014 Approved Programs: C2PC DCGS Future Combat Systems GALE AF JET CCIC2S JMPS JSTARS GCCS- TBMCS and hundreds more Sponsor: National Geospatial-Intelligence Agency Contractors: Northrop Grumman, ESRI, Analytical Graphics, Inc., Leica Geosystems 11
Power of Geospatial Tradecraft Moving from Terrain Analysis to Behavioral Modeling SWORD Brigade Simulation module Courses of action Dynamic operational indicators and Capturing Knowledge for Validation, Sensitivity Analysis, Training, and Sharing 12
Challenge: Coping with Available Bandwidth Combining GIS and Web Services technology Analysis compressing TB of data into MB of actionable terrain information Web Services sending only the pixels needed Off-network transactions only using the network for high-priority information Layering Data a mechanism for prioritization Separating Data, Business Logic & Presentation Application Independence from Data Source Products all or nothing, when you get it CD-ROM of CIB: 650MB CD-ROM of VMAP: 650MB File of NITF is 4GB Services what you need, when you need it Cache the 10MB of 5m resolution pixels that matter for the next 24 hours Access the 40kB service of 1m resolution pixels that matter now 13
CJMTK Geospatial Appliance Standard Data/Architecture Solution for C2 Applications Application Ready Data 2D and 3D Standard NGA Products General Worldwide Coverage Data NGA Geonames Preconfigured Content and Applications Map Documents Layer Files Map Services Versatile Access File sharing for legacy Geodatabase Web Services (WMS, KML, SOAP) Data Administration Map Database, Cache Updates Replication Tools Administration Tools Ruggedized Server (1 TB) Rack Mounted Server (7 TB) GCCS GoogleEarth FalconView C2PC Data Updates DCGS NGA-Arnold DGINet for analysis and decision support 14
What Does This Mean For Operations? How does this relate to the Orders process? 15
Essence of Order Resides in the 5Ws The 5 Ws WHO: which unit is to accomplish the task. - Normally identified by a Unit_ID. - When Unit_ID is in doubt, could be identified by location. - Could be identified by ROLE (Main Effort, Security Force, etc.) WHAT: the task to be accomplished. - Could be either an operation or ARTEP task. - Selection maybe dependent on how much the higher commander wants to limit his subordinate. The more specific the task the less it conforms to mission type. HOW: In mission type orders, how to do a task is left up to the subordinate. The general how for the order itself is found in the context of the Commander s Intent and the Concept of Operations. WHEN: the timing of the task. - Control type (AT a certain time, NLT a certain time, EVENT_PLUS_T (D+1, H+2, etc.) - Parameters: (DTG, Event, Time, Unit_ID, etc..) WHERE: the location for accomplishing the task - Lat/Long, UTM, MGRS, etc. - Terrain_Feature_ID Graphic_Control_Measure_ID WHY: the reason for accomplishing the task. - Purpose term. (Attrit, Defeat, Destroy, Contain, Clear, etc..) - Parameters: (dependent on the term but required for clarification: Destroy what? Enemy Force, Terrain Feature) 16
COTS C2 System Framework SitaWare MIP Compliant C2 based on ArcGIS Natively based on MIP standards MIP Block 2 compliance (C2IEDM) MIP Block 3 according to MIP test/implementation plan (JC3IEDM) Best-in-class interoperability Messages: ADatP-3, USTMF, OTH GOLD, J- series Replication: MIP DEM Services: xml/web services, IBM SOA/ESB connectivity ESRI GIS Latest ArcGIS products through strategic collaboration with ESRI Possible to integrate any ArcGIS based components with little effort. Core functionality Situation picture Plan & orders Logistics/holdings ORBAT/task organization MilStd2525/APP6 or tailored symbology. 80% of what all C2 systems require in an open architecture where partners can tailor and extend the solution. 17
Defining C2 for the US Army Future Combat System How will it Communicate Orders? Network Centric Explicit understanding of orders and operations in a distributed environment Know precisely, in real-time, location of all friendly and enemy forces Robotics Integrated into Force Amplify capability of manned elements Multi-functional (scouting, armed, sustainment) Increased Reliance on Extended Range Engagement Organic plus strategic and tactical support Long range ISR and precision fires Capable of Air-Mobile Operations Commercial and minimum DoD strategic and tactical lift Indirect Fire Function Direct Fire Function Networked Command, Control & Comms Organic & Inorganic RSTA Infantry Carrier + C2 Function Sensor Function 18
The Solution - Battle Management Language (BML)? BML - an unambiguous language to: Transmit Digital Orders to Joint and Combined Forces using an unambiguous, machine and human readable language Command and control live and simulated forces conducting military operations Provide for situational awareness and a shared, common operational picture Reduce workstation controllers, unique interfaces, and interpreters Reduce time and cost to accomplish training / operations Only having to input units / graphics once into system since they are stored and are accessible through a common database OPORD production / issue Facilitates auto-fill of large portions of units OPORD based on data from higher headquarters OPORD Improve Service, Joint, Coalition interoperability Better integration of simulations into C2 systems Shared Semantics between C2 and M&S via a Common Tasking Description 19
BML Scope BML is being developed as a standard representation of digitized C2 information for executable plans, orders, requests and reports C2 Systems C2 Systems Simulation Systems for military units, for simulated forces, and for future robotic forces. Robotic Forces 20
BML Representations Tasks to Subordinates Graphics convert to BML Division Mission Division attacks on order in zone to seize OBJ SLAM. Division Concept of Operations Form of maneuver: Penetration Main effort: BLUE-MECH-BDE2, on order BLUE-ARMOR-BDE1 Supporting effort: BLUE-MECH-BDE1 BLUE-ARMOR-BN1 Deep: None Reserve: BLUE-AVN-BDE1 Security: BLUE-CAV-SQN1 Tactical Combat Force: BLUE-MECH-TM1 Who What When Where Why BLUE-MECH-BDE1 Attacks On order Zone Fix (MRR1) BLUE-MECH-BDE2 Attacks On order Zone Penetrate (MRR2) BLUE-ARMOR-BDE1 Follows and Assumes (B-M-BDE2) On order Zone Seize (OBJ SLAM) BLUE-AVN-BDE Occupy On order AA EAGLE Reserve BLUE-ARMOR-BN1 Follow and Support (B-A-BDE1) On order Zone Support (B-A-BDE1) BLUE-CAV-SQN1 Screen On order Zone (PL AMBER to PL BLUE) Protect (Division left flank) BLUE-MECH-TM1 Tactical Combat Force On order DSA Protect (Division Rear Area) 21
BML The need for a Grammar 5 Ws is an intuitive organizing principle. 5 Ws and relationships can be expressed But, Why a 5 W Representation is not a Grammar in the existing formalism of the C2IEDM. 5 Ws are not necessary nor sufficient. 5 Ws are not detailed enough to specify tasks for execution. 5 Ws do not have a formal, verifiable syntax. 22
BML The need for a Grammar Tasks are not explicitly represented in the C2IEDM. Tasks are listed and verbally defined in the C2IEDM table: action-task-category-code. Tasks have no grammar within the C2IEDM. Example: advance is a C2IEDM action-task. While advance has meaning, it has no explicit relationships within the C2IEDM. Thus, any interpretation of advance must be through Human interpretation. 23
Why An Improved Formal BML is needed Our current US Army BML is a loosely knit language tailored to interpersonal communication. Its vocabulary is found in FM 1-02, but it lacks clearly delineated rules governing its use (semantics and syntax). It is riddled with ambiguity and overlapping definitions. As such, it is incapable of transitioning to the full range of automation that the Army is implementing. It will not support the integration of advanced modeling and simulation with digitized command and control. 24
JC3IEDM Spatial Component What if we add the GIS spatial component? JC3IEDM tables + Geodatabase Tables Access the spatial component in JC3IEDM Maintain the same tables in JC3IEDM + = Point, Polyline, Polygon 25
geobml geobml is an extension of BML into the domain of actionable geospatial information. geobml is not a geo-spatial database. geobml provides a semantic and syntactic bridge between the Warfighter s decision making, Situational Awareness (SA) needs, and the terrain experts realm. 26
BML Way Ahead Horizontal Interoperability (Military and Commercial Investment) C2 Services Layer BML M&S Services Layer JC3IEDM GeoBML GIS Services Layer GeoBML MIPDEM Geospatial HLA/DIS GML 27
Challenge: Integrating C2, Geo, and M&S BML a standard representation of digitized C2 information and geobml, for actionable geospatial information US Systems A Common Operational Picture Coalition Systems Web Services Other Business Logic C2 Business Logics Embedded Simulation Web Services HLA / DIS MIP Services Layer C/JMTK HLA / DIS BML GML MIPDEM COTS / NGA / CJMTK geobml MIP / COTS / DoD JC3IEDM Operational DBs Geodatabase 28
Modeling and Simulation/Wargaming Train As We Fight MÄK GIStoSIM Simulation data in ArcGIS Displays Simulator Network Simulator allows ArcGIS-based applications to interoperate with HLA, DIS or TENA exercises & visualize data in real-time incorporates HLA, DIS, or TENA data into ArcGIS based C4I systems 29
Demonstration: Soldier as Sensor A loosely coupled Service Architecture GIS Workstation Mobile Clients Browser Presentation Tier Service Architecture Server Map & Chart Services Geo Analysis Services Geodata Replication Services Image Data Services Workflow Services Serving/ Publishing Tier BGD GDB DIV GDB BGD GDB Desktop Authoring Tier to collect, integrate, and share information across echelons 30
Demonstration: Soldier as Sensor Technical Workflow Service / Theater / Joint / Agency GIS Workstation XX Infantry Division X Brigade Combat Team I RSTA Platoon Browser GIS Workstation Browser Connected & Disconnected Operations Mobile Clients Services Architecture Reusable Web Services Synchronization Division Synchronization Brigade Synchronization Patrol Common Operating Picture ArcGIS Server 31
Demonstration: Soldier as Sensor Operational Workflow Common Operating Picture Plans Situational Awareness Manage Operations XX 1 DIV TOC XML Patrol Order Transmit Patrol Order X 2 SBCT TOC Operational Drivers Intel Current Ops Base Data 6 Division Sends Updates Down Brigade Pushes Changes Up X Situational Awareness 5 SBCT TOC Conduct Patrol Debrief Value Added Analysis QC/QA Data Updates X SBCT TOC Situational Awareness Mission Management Detailed Mission Planning Conduct Operations Connected / Disconnected Reporting I 4 Situational Awareness RSTA Dynamic Platoon Re-tasking 3 Conduct Patrol Digital Mission Profile 32
33
Demonstration: Soldier as Sensor Implications for deployed forces of Service-enabling GIS support Knowledge base Data, maps, simple applications limited, pre-packaged, static Data, maps, complex applications rich, flexible, customizable, dynamic Operations planning & execution Rigid, iterative (OODA loop), connected or unsynchronized Adaptive in near real time, connected or disconnected, synchronized Situational awareness Limited, restricted scope, stove-piped, inconsistent, obsolescent Broad-based, flexible scope, integrated, consistent, and current Multiple COPs One consistent COP 34
Operations: Airborne Web Services (AWS) Sponsor: 753 rd Electronic Systems Group, Hanscom AFB Contractors: MITRE, ProLogic and SAIC 35
Operations: Joint Geospatial Enterprise Services (JGES) Sponsor: U.S. Army Engineering Research and Development Center, Topographic Engineering Center Contractors: ESRI, George Mason University, Viecore FSD, Northrop Grumman 36
Operations: Search and Rescue Optimal Planning System (SAROPS) Software Support Agent: U.S. Coast Guard Command and Control Engineering Center, Portsmouth, VA. Contractors: Northrop Grumman, Applied Science Associates, Metron, Allied Technologies Group 37
Implications: Geospatially Enabled Battle Command improving Military Decision Making Where are my Strike Assets? J3 Where is the Enemy? J2 SH**PG 10% 56 SH**PG 12% 3 What is their Status? B SH**PG 54% 28 How could the Enemy Move? J4 s F22 10 min M105 A Terrain Analysis What are my Options? M&S Mission Planning What is my Optimum Mission Plan? Adaptive planning, realistic wargaming, rapid and flexible execution 38
Conclusions Battle Command systems need to be geospatially enabled to meet the future force needs Enterprise GIS technology provides the integrating platform for C2 capabilities BML provides the semantic consistency required to integrate C2 and M&S capabilities This Geo-Enabled Battle Command environment will provide: Adaptive planning and flexible mission operations execution Better communication between mission planners and operations staff Wargaming of future options through direct use of modeling and simulation capabilities in warfighting systems Immediate consideration in the planning process of options emerging from a simulation Rehearsal capabilities within operational systems A current operational picture for planners and operations staffs An improved military decision making process 39