1

Battle Management Language (BML) and the NPS MOVES Semantic Interoperability

Research Agenda

Curtis BlaisResearch Associate and PhD Candidate

MOVES InstituteNaval Postgraduate School

clblais@nps.edu

Outline

Motivation

Inspiration

Research Agenda

Summary

2

Motivation

• C4I and M&S systems do not work well together “out of the box”

• Interoperability -- Capability of a system to automatically provide services to and accept services from other systems to achieve a desired outcome (Draft DoD MSMP)

Information Sharing

“ An organization that does not promote the widespread sharing of information will not have well informed individuals and organizational entities. An organization that develops an approach to command and control that takes full advantage of the information available will be at a competitive advantage.”

Alberts & Hayes, Power to the Edge, CCRP

3

DoD Data Strategy• Global Information Grid• Net-Centric Data Strategy

• Ensuring data are visible, available, and usable when needed and where needed to accelerate decision-making

• “Tagging” of all data with metadata to enable discovery of data by users

• Posting of all data to shared spaced to provide access to all users

• Advancing the Department from defining interoperability through point-to-point interfaces to enabling “many-to-many” exchanges

C2 Ontology

Too large to be built all at onceWould take too longWould be too hard to gain widespread acceptance

Evolutionary development neededStart small (e.g., tracks)Show community how it is done (methodology)Demonstrate benefits (and limitations)Create mechanisms for extension

4

Inspiration

The Evolving WebWeb of

Knowledge

HTML/HTTP

Resource Description FrameworkExtensible Markup Language

Self-Describing Documents

Foundation of the Current Web

Proof, Logic andOntology Languages

Shared terminologyMachine-Machine Communication

1990

2000

2010

J. Hendler presentation, W3C , 2001

Explicit semantics through standard languages

5

Semantic Web“An extension of the current Web in which

information is given well-defined meaning, better enabling computers and people to work in

cooperation.”– Berners-Lee, et. al., 2001

• Transforming documents to information (data in context)• Enabling automated reasoning• Equally accessible to human and software agents

Semantic Web Stack

Source: I. Herman: “Introduction to the Semantic Web,” 12 November 2003.http://www.w3.org/2003/Talks/0624-BrusselsSW-IH/26.html

6

Research Agenda

7

RichSemantic

Track

Semantic Interoperability

Joint C3 InformationExchange

Data Model

TacticalAssessment

MarkupLanguage

USW-XML

MobilityCOP

C-BML

AutonomousVehicle Command

Language

ScenarioDescription

SMAL

AVCL/AUVW

FCSGIG

Plansand

Orders

BML

VIRT

Research Agenda

C2 Ontology-Concepts-Relationships-Rules/Constraints

JBML

MSDL

Key Capabilities Explored in this Research

• Representing Battlespace Information• Describing Scenarios• Reporting Information• Exchanging Plans and Orders• Supporting Decision-Makers

8

Representing Battlespace Information

• Joint Consultation, Command, and Control Information Exchange Data Model (JC3IEDM)

JC3IEDM

VERTICAL-DISTANCE

REFERENCE

GROUP-CHARACTERISTIC

COORDINATE-SYSTEM

AFFILIATION ADDRESS

ACTION

CONTEXT

OBJECT-ITEMOBJECT-TYPE LOCATION

REPORTING-DATA

RULE-OF-ENGAGEMENT

CAPABILITY

CANDIDATE-TARGET-LIST

Joint Consultation Command and Control Information Exchange Data Model (JC3IEDM) -- NATO STANAG 5525 (in ratification)

Automated C2 Interface Exchange Mechanism Supporting Liaison and Automation

A very rich representation of the COP enabling commanders work together

Country, system, Service, application, process, technology, vendor neutral Information Exchange Data Model

All commanders need these battlespace basics

Supports War Operations, Crisis Response Operations and Joint Ops

Multilateral Interoperability Programme

High-Level View

9

Describing Scenarios

• SAVAGE Modeling and Analysis Language (SMAL)• Military Scenario Definition Language (MSDL)

SAVAGE Modeling Analysis Language (SMAL)

• Strategy for identifying tactical, physical and simulation-oriented metadata for vehicles, terrain and entities in virtual environments

• Collects and organizes information necessary to create and populate a 3D virtual environment

• Equivalent XML and X3D representations for SMAL are defined

10

Military Scenario Definition Language (MSDL)

• Common language for describing initialization data for C2 and M&S systems

• Initial implementation for US Army OneSAF Objective System (OOS)

• Specification being developed under the Simulation Interoperability Standards Organization (SISO) for international standardization

• C-BML is the tasking language for initializing plans and orders in MSDL

Reporting Information

• Tactical Assessment Markup Language (TAML)• Rich Semantic Track (RST)• Joint Battle Management Language (JBML)

11

Tactical Assessment Markup Language (TAML)

• XML vocabulary for use in exchanging command and control, exercise assessment, operational analysis and simulation information among USW systems

• Schema definition registered in the DoD XML Metadata Registry and Clearinghouse

• Ontology developed in the Web Ontology Language (OWL) to demonstrate capabilities and limitations of the language and current automated reasoners in the context of a tactical problem

From Feasibility to Practice

• ENS Childers thesis demonstrated feasibility of application of Semantic Web standards• Tool-based demonstration (Protégé, SPARQL)• Single representation of contacts (TAML)• Single domain (USW)• Static ontology

• Unified Application (Rich Semantic Track)• Formalized abstraction of Track concept for general software

implementation• Mediation of multiple track representations across multiple

domains• Operator and problem-driven evolution of the ontology

12

Rich Semantic Track

• Basis for interoperability: Common Reference Model• Strong semantics for Beliefs• Basis for expression of user-specific information

requirements supporting VIRT principles• Driven by decision-maker pragmatics• Common semantics underlying multiple systems and

across multiple domains• Global Command and Control System, Maritime Domain

Awareness, Cooperative Engagement Capability, TAML, Joint Track Management, etc.

Rich Semantic TrackTrack

• Beliefs• Identity and Characteristics• Dynamic State at Time T• History of States (past “track”)• Predicted States (future “track”)

• Meta-Information (applicable to each element of belief)

• Evidence• Inferences• Error and Uncertainty Estimates• Temporal Qualifications• Spatial Qualifications

*Hayes-Roth. Towards a rich semanticmodel of Track: Essential Foundation forInformation Sharing. NPS Research Paper.Monterey, CA. February 25, 2005.

13

Exchanging Plans and Orders

• Joint Battle Management Language (JBML)• Coalition Battle Management Language (C-BML)• Autonomous Vehicle Command Language

(AVCL)*• Autonomous Unmanned Vehicle Workbench

(AUV WB)*

*see backup slides

Battle Management Language (BML)An unambiguous language used to command and control forces and equipment conducting military operations and to provide for situational awareness and a shared, common operational picture.*

C2 System

SimulationSystem

C2 System

RoboticSystem

BML tasking:Command and ControlForces and Equipment

BML reporting:Provide forSituational Awareness

*Carey, Kleiner, Hieb & Brown, “Standardizing Battle Management Language – A Vital Move Towards the Army Transformation,”

01F-SIW-067

14

Three Sides of BML Triangle

Terms and expressions

rooted indoctrine

Agreed-upon approach for describing concepts (missions, tasks, state)

C-BMLDoct

rine

RepresentationProtocol

Agreed-upon methodfor exchange of

BML expressions

Battle Management Language (BML)

Coalition Battle Management Language (C-BML)*

Three Sides of C-BML Triangle

XMLWeb Services Grid Services

...

Terms rooted ininternationalmulti-service,

multi-organizationaldoctrine,

such as AAP-6, …

Joint Consultation Command & Control Information Exchange Data Model (JC3IEDM)

C-BMLDoct

rine

Representation

Protocol

*SISO Product Development Group

15

Joint Battle Management Language (JBML)

Three Sides of JBML

XMLWeb Services

Terms rooted inUS joint

multi-servicedoctrine,

such as militarymessagingstandards

Agreed-upon approach for describing concepts (missions, tasks, state)

C-BMLDoct

rine

RepresentationProtocol

JBML Demonstration

Three Sides of JBML

JBML-DCS* XMLWeb Services

Ground OPORDERAir Tasking OrderNavy Tomahawk

plans and launch orders

Joint Consultation Command & Control Information Exchange Data Model (JC3IEDM)

C-BMLDoct

rine

Representation

Protocol

*Domain-Configured Service

16

Maritime Component

Introduction of Naval/Maritime plans and orders to BML capabilities

Initial mission selections• Air Tasking Order (ATO) – leverages work by Air

component (Gestalt) in JBML project• Tomahawk Mission Plans and Orders – capture content

of US Message Text Format (USMTF) Launch Sequence Plan and INDIGO messages

Maritime Component

Data Flow:• Generation of JBML-DCS XML representation of

USMTF TLAM messages using the JC3IEDM-enhanced Tactical Collaboration (JTC) program; content pushed to the JBML Web Service

• JBML-DCS XML converted JC3IEDM structures described by mapping spreadsheet and diagrams, implemented in JBML service architecture BBS layer

• JBML-DCS XML expressions pulled from the service by intermediate software and converted to JSAF orders

17

JC3IEDM-enhanced Tactical Collaboration (JTC)

• Naval Undersea Warfare Center open-source project• Prototype Naval planning tool• Provides capability to prepare Naval OPTASKS• Used in Trident Warrior 2006 for collaborative planning

and chat experimentation• JC3IEDM internal data model• Adding capability to plan Tomahawk strike missions using

JBML-DCS expressions for interaction with other systems through the JBML Web Service repository

• Similar to earlier introduction of CAPES on ground side for BML demonstrations

JC3IEDM -enhanced Tactical Collaboration (JTC)Leveraging Multinational Interoperability Standards

Multilateral Interoperability ProgrammeUndergoing ratification as STANAG 5525Multinational C2 Community of Interest

VERTICAL-DISTANCE

REFERENCE

GROUP-CHARACTERISTIC

COORDINATE-SYSTEM

AFFILIATION ADDRESS

ACTION

CONTEXT

OBJECT-ITEMOBJECT-TYPE LOCATION

REPORTING-DATA

RULE-OF-ENGAGEMENT

CAPABILITY

CANDIDATE-TARGET-LIST

VERTICAL-DISTANCE

REFERENCE

GROUP-CHARACTERISTIC

COORDINATE-SYSTEM

AFFILIATION ADDRESS

ACTION

CONTEXT

OBJECT-ITEMOBJECT-TYPE LOCATION

REPORTING-DATA

RULE-OF-ENGAGEMENT

CAPABILITY

CANDIDATE-TARGET-LIST

Joint Consultation Command and Control Information Exchange Data Model (JC3IEDM )

Speed of Command:• Enhanced distributed collaboration during planning using

JC3IEDM message templates• Rapid man-to-man and man-to-machine capability

Speed to Capability: • Interoperability: warfighter systems and services based

on information exchange standards• Leveraging NATO/Multinational standards. Adopt, don’t

reinvent - saves money and time and improves the resulting integrated capability

• JC3IEDM is the C2 core for the FORCEnet data strategy

18

Supporting Decision Makers

• Valued Information at the Right Time (VIRT)• Mobility Common Operational Picture (M-COP)*

*see backup slides

• Provides Valued Information at the Right Time

• Screens and marshals the “data storm”• Assists in the filtering of information to

provide guidance based on situational priorities

• Automatically adapts to the environment by inferring valued information

• Personalizes, using context, role, and state

What is VIRT Technology?

19

The Basic Ideas

• Synchronize groups by having them operate on semantically aligned and high-value information

• Determine what concepts operators’ missions depend on and make those standard

• Notice what beliefs underlie mission plans and Courses of Action (COAs)

• Automatically inform operators when changes in data affect their beliefs and planning rationales

Model-based Communication NetworkInstead of Stateless Networking, State-full

• Maintain shared state among collaborators• State = current values of models, e.g.

• The route plan, position, velocity of an aircraft• The current and future position and behavior of a unit• The hypothesized position, status and intention of a system

A shared world model is the goal• Collectively, what the collaborators believe• Distributed, replicated for efficiency• Autonomously updated, through dead-reckoning

Like a distributed blackboard of hypotheses• Re-conceptualize Common Operational Picture• Obviate “communication” of non-news• Emphasize “information,” especially valued information

20

BML provides the structural and semantic basis for description and interchange of critical information

promoting C2/M&S system interoperability.

ConclusionsSemantic Web development is offering promising language standards for adding meaning to data and increasing automated processing of information• Tools simplify the ontology building and testing process• Many potential applications in the military domain

Rich semantics can be added to simulation frameworks to enable experimentation and demonstration of potential benefits for Network-Centric Operations

Contacts

Curtis Blaisclblais@nps.edu

http://www.movesinstitute.org/~blais/MOVES Institute, Naval Postgraduate School

Monterey California 93943-5000 USA1.831.656.3215 voice1.831.656.7599 fax

21

Backups

Exchanging Plans and Orders

22

Autonomous Vehicle Command Language (AVCL)

• Battle Management Language (BML) is intended to be a standardized unambiguous language for expressing orders, commands, requests, and reports that can be understood and acted upon by live (real), constructive (simulated), and robotic (real or simulated) forces

• Specification of C-BML for robotic forces can be informed by current Autonomous Vehicle research- What are the key considerations for an AV command language?- What are the similarities and differences in current approaches?

AVCLA Rigorously Defined Common Data Model

• Vehicle-Independent• Subsumes Vehicle-Specific Data Format

and Content• Extensible Markup Language (XML)

Schema Governed

Scope of Application• Mission Specification (tasking)• Communications• Mission Results

Automated Conversions• Data Model to Vehicle-Specific Formats• Vehicle-Specific Formats to Data Model

Data Model

AAV 1

Support

AUV 2

ASV 2

AAV 2

AUV 1

ASV 1

23

AUV Workbench

• Open source, Java, XML, X3D graphics• Mission planning• Robot mission execution• Hydrodynamics response• Sonar modeling• 3D visualization• Compressed radio frequency (RF) and

acoustic communications

AUV Workbench windowsmission

commandsVisualization, mission planning

robot execution

6DOF response hydrodynamics

24

Supporting Decision-Makers

Mobility Common Operational Picture (MCOP)

•• The MThe M--COP is a subset of the COP consisting of COP is a subset of the COP consisting of relevant tactical movement and maneuver data and relevant tactical movement and maneuver data and information shared by more than one command. information shared by more than one command.

•• The MThe M--COP can be tailored for various users and will COP can be tailored for various users and will include data and information for mobility of individual include data and information for mobility of individual combatants, ground vehicles, and autonomous / combatants, ground vehicles, and autonomous / robotic vehicles.robotic vehicles.

•• Key categories of information: Terrain, Weather, Key categories of information: Terrain, Weather, Obstacles, Forces, Threat, Maneuver Analysis, Route Obstacles, Forces, Threat, Maneuver Analysis, Route PlanningPlanning

25

M-COP DemonstrationRoute Planning Service

Simulation

Visualization

KnowledgeManager

Command & ControlMenu

Reasoner

MCOPOntology

Route Finder

Knowledge-Based Route Planning in M-COP

Route FindingService

Terrain

Mission

FriendlyForces

EnemyForces

Maneuver ServicesMobility COP Ontology

SimulationSystem

BattleCommand

System

COP

Recon, Intel

Route Monitoring

Service

Based Upon

Based Upon

Unit location Recon, IntelWeb service request