A Geospatial Battle Management Language GeoBML

1
A Geospatial Battle Management Language (GeoBML)
September 14, 2006 Presentation to the Coalition
Battle Management Language Product Development
Group
Dr. Michael Hieb
Center for C4I George Mason University
Fairfax, Virginia
2
A Geospatial Battle Management Language (GeoBML)
for Terrain Reasoning
Presented to the 11th International Command and
Control Research and Technology Symposium Paper
I-110
Dr. Michael Hieb Dr. Mark Pullen Martin Kleiner
Michael Powers
Center for C4I George Mason University
Topographic Engineering Center US Army Engineer
Research and Development Center Alexandria,
Virginia
Fairfax, Virginia
Michael.W.Powers_at_erdc.usace.army.mil
mhieb_at_gmu.edu
3
geoBML Development Team
George Mason University Michael Hieb, Research
Associate Professor Martin Kleiner,
Research Associate ACS Inc. John Roberts,
Project Manager Adam Ritchie, Senior Computer
Scientist Tech Projects LLC Eric Nielsen,
Subject Matter Expert
Viecore FSD Michael Fennell, Program
Manager Michael Altenau, Principle Information
Engineer ERDC-TEC Ken Braswell,
Subject Matter Expert ERDC-GSL Burhman Gates,
Electrical Engineer Paul Richmond, Mechanical
Engineer
4
Outline

• Why a geoBML?
• Geo-Centric
• Future-Force Centric
• Net-Centric
• geoBML
• Architectural Framework
• Representational Consistency Battle Management
  Language
• Computational
• Semantic
• Enabling Terrain Reasoning with geoBML
• Battlespace Terrain Reasoning and Awareness
• An example

5
Automation and Force Structure

• Network-Centric Vision
• Information Superiority..C2 Agility
• Elimination of Stovepipes
• Horizontal Integration
• Smaller Force Structure
• Design for a highly automated force
• Geo-information Concept
• Shared, common information structures.unambiguou
  s meaning
• Reinforced the need for explicit representation
  and a BML

6
Current View of geo Information

• Beliefs and Assumptions
• Possesses a ubiquitous quality across C2
• Use is often very similar
• Stable, sufficient representations is a goal
• Deserves the same rigor of explicit, quality,
  consistency of representation applied to other
  battlefield information
• Foundation for shared, common awareness
• 3a.Terrain and weather are fundamental
  enabler/constraint to
• Combatant and non-combatant behavior
• Force, system, sensor and soldier performance
• 3b.Military operations and behaviors are not
  random
• Basis for relationships among battlespace
  entities and actors/actions
• Organizing the Battlespace in space, time and
  tactical intent
• Value F(x) of geo information Knowledge gt
  Information gt Data
• Hierarchy of Abstraction
• Get out of the data ASAPtoo many reasons to
  count

Enabling the Commander, Warrior and C2
systems through embeddable geospatial information
7
Battle Command Centric(Geospatial Information,
Technology)
Battle Command Mission Execution
Embedded Sustainment
WMI Services
Situation Understanding
Planning Preparation
Presentation Services
Intelligent Services
Battle State Assessor
Readiness Monitor
Airspace Planner
COA Planner
Incoming Order Processor
Action Requester
Administrative Services
Platform Soldier Mission Readiness System
Role Manager
Presentation Tailor
Assessor Services
Weather Service
Plan Assessor
Ground Space Planner
Sustainment Info Services
Task Organization
Policy Editor
Agent Authorizer
Presentation Builder
Objective Planner
Fires Effects Planner
Order, Report Authorizer
Notification
Object Refinement
Fusion Process Refinement
Human Resource Services Planner
Maintenance Planner
Tactical Planning
Intelligent Operator Monitor
Presentation Manager
Command Services
Situation Refinement
Comms Network Planner
Supply Distribution Planner
Battlespace Object Priority Manager
Sensor Planner
Manned Ground Vehicle Remote Operation
Unmanned Payloads Control
Threat Monitor Service
Threat Refinement
Collaborator
WMI Primitives
Maneuver Assessor
Security Planner
Force Health Protection Planner
UAV Control
BSO Understanding Services
Sustainment Planning Services
Translation Interface Text-Voice, etc)
Visualizer
Survivability Planner
Air Defense Planner
Unattended Munitions Control
WMI Element Services
UGV Control
SU Toolset
SU Presentation
Resource Planning
Human Resource Services Manager
Maintenance Manager
UGS Control
Task Integration Network Editor
SU Tool Services
Report Generator
Terrain Analyzer
AAR Services
Supply Manager
Common Vehicle Control
I/O Services
Planning Analysis Services
Rear Area Security Manager
Distribution Manager
Airspace Control
Ground Space Control
Rehearsal Services
Simulation
PPS Support Services
Force Health Protection Manager
Fires Effects Control
Sustainment Control Services
Tactical Control
SoS COE
Interactive / Computational Info Services
Geo-based Decision Tools
GeoBML and JC3IEDM
8
Architectural Framework(Terrain and Weather)
Battle Command/Mission Execution
Planning and Preparation
Situation Understanding
C4ISR Sensor Fusion
C2 Training / Modeling and Simulation
Net Centric Enterprise Services
Commercial Joint Mapping Toolkit
Enterprise GIS Architecture
Exploitation Technology
Decision Tools
Decision Tools
Analytic Technologies
Photogrammetry And Spectral Technology
Mission Context
Situational Context
Geographic Context
Tactical Context
Representation
Representation
Information
Knowledge
Format/Encoding
Format/Encoding
Format/Encoding
Format/Encoding
Format / Encoding
Models
Models
Models
Models
Actionable Information
Bandwidth
9
BTRA Technology Framework
Warfighter Pay-off Decision Tools Battlespac
e Environment Actionable Information Tactical
Extensions to Core Science Competencies Core
Science Engineering Competencies
Dynamically Responsive Geo-Tactical Chessboard
Vehicle and Class Speeds
Digital- Interactive Maneuver Graphs Task-to-Miss
ion Relationship Nets
Regional Sensor P(d) (IR)
Vehicle-Terrain Interaction
Spatial Objects Representation Multi-
Relational Geometries
State of the Ground Atmosphere
Transfer Sensor Physics
Mobility and Maneuver Sciences
Geospatial and Carto Sciences
Physical / Atmospheric Sciences
10
Representation Consistency (Potential of a
Battle Management Language)
Formal Language with Syntax and Semantics
XML Web Services/ Grid Services
Doctrine
Protocols
BML
Representation
Command Control Information Exchange Data Model
(C2IEDM)
11
Semantic Consistency geospatial Battle
Management Language (geoBML)

• geoBML is an Unambiguous Language
• Defined by the role of actionable
• geo-information in the C2
• Provides Unificationacross
• Doctrine and terms
• Explicit vocabulary and grammar
• Specific context mapped to operations, missions
  and tasks
• Explicit Representation (2 tiers)
• Consistent extension to the C2IEDM
• Standard framework and exchange model
• Computational structure
• Both necessary and sufficient for
• shared, common understanding
• Protocols
• Explicit structure for transmission / sharing

XML Web Services Grid Services
Terrain, Weather and Military Eng Terms
Doctrine
geoBML
Protocols
Representation
Geo-Environmental Extension to Command Control
Information Exchange Data Model (C2IEDM /
JC3IEDM)) Explicit Computational
Representation For Actionable Geospatial
Information
12
Integrating Terrain and C2 Information through BML
C2IEDM
Spatial Object
Spatial Object
Spatial Object
Spatial Object
GIS
13
Current Spatial Objects for geoBML
Tier 2 products (Mission Context)/Tier 3
products (Planned) Avenues of approach Assembly
Areas Engagement Areas Tier 2 Routes Battle
Positions Attack positions Axis of
Advance Indirect Fire Firing Position Assault
Positions Attack by Fire Positions Drop
Zones Helicopter Landing Zones
Tier 1 Products (Terrain/Military
Context) Natural Obstacles Concealment Fields
of Fire Cross Country Movement Maneuver
Network Mobility Corridors Chokepoints
14
Choke Points in a Mobility Corridor
Minimum Spanning Distance
15
Selected Engagement Areas
Top 5 with highest visibility
16
Demonstration Architecture
Web Service Interface
Commanders Support Environment
geoBML C2IEDM
Tasks Graphics Units
OTB
Route Planner
Battlespace Terrain Reasoning Analysis System
BML GUI
17
Overall AO
18
AO W/ Obstacles Overlay
19
AO W/ Obstacles and Maneuver Network
20
BDE Planning

• Fields of Fire
• Mobility
• Axis of Advance
• Avenue of Approach
• Boundaries

21
PL PINE
PL ASPEN
41
PL ELM
AA BELTON
1-4 CAV
PL SPRUCE (LOA)
X
42
218
PL OAK
43
TF 1-118
TF 2-263
TF 1-118
TF 2-263
MORT
OBJ JAB
31
TF 2-263
TF 2-263
TF 4-118
TF 4-118
218
MORT
X
1
PL ASPEN
32
MORT
33
PL OAK
PL ELM
PL SPRUCE (LOA)
RAG
Appendix 2 (Bde PHASE 1 (Attack) Sketch) to ANNEX
C (Operations)
22
(No Transcript)
23
CSE
24
OneSAF Testbed
25
Summary

• Network-Centric Operations require change in
  paradigm for Terrain Reasoning
• Digital Maps are not enough
• C2 information needs to inform terrain reasoning
  in a dynamic and highly networked environment
• BML is a formalization of C2 Information
• Spatial Objects added to BML to form geoBML will
  enable reasoning to adapt to both changed
  missions and a variety of terrain and
  environmental data
• geoBML allows Commanders to access the right
  environmental information to accomplish their
  intent

Carry the right battlespace knowledge you
carry the day
26
(No Transcript)
27
Computational Consistency Spatial Objects and
Relational Objects
Geo-Complex

• Spatial Objects
• Hierarchical Representation
• ESRI Geo-database
• Geometric Networks
• Rationale and Objectives
• Common, stable spatial geometry, ID and
  attribution
• Base input for all engines
• Temporal tags (persistence)
• Relational Objects
• Physical or Effects-based
• Rationale and Objectives
• 1st Principle effects on military behavioral
  relationships
• Graph provide structure capable of dynamic
  attribution

Cover
Spatial Objects
28
Evolving a geoBML

• Assumptions
• Cohesive Formations occur to execute a tactical
  task or mission creating a situation
• Grouping of objects. So there are subordinate
  forces (children) forces comprising the Force
  (target)
• Cohesive Formation and tasks argue that there are
  operational relationships required for the task
  (e.g. fire complimenting angles and range fans)
• Possible that there is parent to the target
  force
• (F ())

Table of Organization and Equipment (TOE)
Physical Account of the Force Vehicle Type and
Count of units Spacing Weapons Relationships

• Syntax and Semantics
• Understand the elements and qualities of the
• force being evaluated
• Possible Tasks, Activities and Missions
• C2IEDM
• 2. FMs
• TOE, Physical Conditions and Behaviors
• Universal Joint Task List (UJTL)
• Language of Command
• BOS/BFAs
• Tactical Tasks and Missions

29
Evolving a geoBML

• What Dynamics Impact the Representation
• Weather
• Other Battlefield information
• Persistence of Operational Value

Table of Organization and Equipment (TOE)
Physical Account of the Force Vehicle Type and
Count of units Spacing Weapons Relationships

• Computation Constraints
• Data and Information Dependencies
• Product Generation
• Time Sensitivity
• Computational Time Allowed
• 1 Time, Intervals or at Run Time
• Sensitivity to locally held data