Decision Support for Geo- Enabled Battle Command Eric Nielsen U.S. - PDF document

2/4/09 Decision Support for Geo- Enabled Battle Command Eric Nielsen U.S. Army Topographic Engineering Center 4 February 2009 Definitions • Command and Control – “The exercise of authority and direction…over assigned and attached forces in the accomplishment of a mission” (FM 1-02) • Mission – “The task, together with the purpose, that clearly indicates the action to be taken and the reason therefore” (FM 1-02) • Task – “A clearly defined and measurable action, activity, or event…” (FM 7-15) • The 5 W’s 1

2/4/09 Geo-Centric View of C2 Beliefs and Assumptions • Ubiquitous across C2 • Terrain and weather are fundamental enablers/constraints to force, system, sensor and soldier performance • Military operations and behaviors are not random • Warfighting Value: Knowledge > Information > Data • Deserves the same rigor of “explicit, quality, consistency of representation” applied to other battlefield information Tasks – Engineered Knowledge x x x 856+ 3537 3921 41 723 989 48 373 285 28 284 821 HHC E MI SPT 430 487 Tasks for every different HHC unit type & echelon 41 106 HQ HQ 115 108 108 190 MGS 102 51 64 SNIPER 32 SNIPER 2

2/4/09 Task-To-Terrain - GeoBML Tactical Spatial Objects Tac$cal Spa$al Objects (TSOs) provide the specific set of geospa$al informa$on necessary to support the decision maker • Tier 1 - foundation products • Pre-computed for large Areas of Analysis • Answer OAKOC questions Tiered TSO Structure • Tier 2 - mission or task specific Tier 3 • Based on Tier 1 Product(s) • Cover smaller Areas of Analysis Tier 2 Tier 1 • Consider additional factors of METT-TC • Tier 3 – represent Command Decision fine coarse • Informed by Tier 2 Product mission specific general / reusable • Generally have an associated Graphic more dynamic primarily static Control Measure (GCM) Information data 3

2/4/09 Terrain Reasoning Informs Tac$cs and Opera$ons Observa(on & Concealment Cover & Maneuver Fields of Fire Concealment Network Network and complex data informs the development of more tac$cally focused and AA mission specific terrain products DOG Co & Bn CCP Chokepoints Mobility II Corridors Avenues of Approach An Example - 2/3 SBCT 2d Bn Commander wants to aKack to defeat enemy forces in OBJ O2. He assigns OBJ D1, E1 and F1 to companies D, E and F respec$vely. He wants F company to aKack by fire enemy on OBJ F1 so he requests BTRA to ini$ate the ABF engine. OBJ O2 OBJ E1 OBJ F1 OBJ D1 4

2/4/09 2/3 SBCT ABF TSO Request Example of TSO use (Attack by Fire) • Engine calculates potential positions for ABF • Considers Objective F1 – LOS (Elevation/curvature) – Target/Observer Height • Sample points within Objective m area (OBJ F1) 0 0 5 1 ~ ~1000m • Relatively flat terrain provides limited LOS • Concealment values evaluated, but not heavily weighted • Areas with no value as ABF show as clear ABF Engine result 5

2/4/09 Example of TSO use – Planning for F/2/3 • Engine calculates potential positions for A ttack B y F ire (ABF) Objective F1 • Considers – LOS (elevation/curvature) – Target/Observer height • Sample points within objective m 0 area (OBJ F1) 0 5 1 ~ ~1000m • Relatively flat terrain provides limited LOS • Concealment values evaluated, but not heavily weighted • Areas with no value as ABF displayed as clear ABF Engine result Tier 2 to Tier 3 – Graphic Control Measure ABF Graphic Control Measure • Examine ABF Engine result • Eliminate inappropriate locations/areas – User decision based on actionable information • C2 application to designate actual position • Consider approach/ingress 6

2/4/09 CCP TSO generation Casualty Collection Point for F/2/3 Initial CCP Location 900 m • Initial placement at ABF – 900 m circle for CCP analysis • Consult Complex for – – Concealment – Reverse slope TSO Enabled Reasoning Movement Planner generates route • F Company route from Assembly Area to ABF position – Use Maneuver Network – Most concealed route – Avoid roads in urban areas 7

2/4/09 TSO Enabled Reasoning Route informs decision • Concealment for CCP paramount – to include ingress/egress This is good, but… • March order • Tradeoff: Change location Require additional functionality to dramatically – Simplicity – easier to increase speed and quality of command and control. implement from march – Security – concealment is equal to original position • Multiple, related TSOs = Better, terrain informed decisions Geospatially Aware Battlefield Object (GABO) • Robust data structure for geospatial reasoning with military objects – – Location – Time – Parentage/Order of Battle/Task Organization – Capabilities of units/weapons – Interaction(s) with control measures, organizations, and forces • Under development – Initial capability 4 th Qtr, FY09 • Integrate BML tasks to govern behavior of objects • Implement JC3IEDM compatibility 8

2/4/09 BTRA Battle Engine (BBE) • Fast COA development based on – Abstracted battlespace – Friendly/Enemy order of battle – Dupuy-derived combat model – Genetic algorithm • Delivers abstract COAs, requires: – BML to generate comprehensive task (what) – GeoBML for precise location (where) – GABO to manage & display interactions (who/when) GABO-BML C2 Use Case Route re-generated. Do Task will not be completed in time you want to: required. Do you want to: Re-generate Re-generate Accept Change Task Ignore Route Route Route -Minefield reported – intersects route - Styker Co. ordered to attack to seize - C2 app determines additional OBJ - Styker Company Continues to OBJ movement cost - Alerts user of route/time constraint - C2 App generates route 9

2/4/09 Use Case – Task Change (add) Task will not be completed in time Change Task - Do you want to change: Attack required. Do you want to: Defend Move Re-generate Time to complete Task Organization Change Task Add Task Ignore Route Breach Withdraw Delay Occupy AA Symbol updated when unit completes -Minefield reported – intersects route User Adds “Breach Minefield” task - C2 app determines additional Breach task movement cost Recalculate time cost to OBJ - Alerts user of route/time constraint Stryker Company Continues to OBJ Use Case – Task Org change (add) Define Command Relationship: Change Task - Do you want to change: Route re-generated. Do you want to: Re-generate Accept Time to complete Attach Task Organization OPCON Add Task TACON Route Route - Engineer Platoon symbol disappears -Minefield reported – intersects route -User queries for units with mine plows once co-located with the Company it’s - C2 app determines additional -Application identifies nearest unit, attached to generates route movement cost - Alerts user of route/time constraint - Minefield breached, Stryker Company continues to OBJ 10

2/4/09 BML-GABO-BBE • Order-to-task BML • Task-to-terrain • Terrain-to-Abstract COAs GeoBML BBE GABO • Abstract-to-Refined COAs – Context-specific TSOs – 5 W’s BML • COA-to-Order • Order-to-Subordinates Result: Very rapid analysis, development and dissemination of plans and orders that exhaustively consider the full range of METT-T*. * Civil Considerations – not yet implemented Decision Support for Geo- Enabled Battle Command Questions? Eric Nielsen U.S. Army Topographic Engineering Center 4 February 2009 11