27
2004 ICCRTS, 14-16 September 2004, Copenhagen Extensible Battle Management Language (XBML) A Methodology for Web Enabling Command and Control for Network Centric Warfare J. Mark Pullen, D.Sc. George Mason University [email protected] William P. Sudnikovich Atlantic Consulting Services, Inc. [email protected] Andreas Tolk, Ph.D. VMASC - Old Dominion University [email protected] Michael R. Hieb, Ph.D. Alion Science & Technology [email protected]

Extensible Battle Management Language (XBML) A Methodology for Web

  • Upload
    others

  • View
    2

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Extensible Battle Management Language (XBML)

A Methodology for Web Enabling Command and Control for Network Centric Warfare

J. Mark Pullen, D.Sc.George Mason University

[email protected]

William P. SudnikovichAtlantic Consulting Services, Inc.

[email protected]

Andreas Tolk, Ph.D.VMASC - Old Dominion University

[email protected]

Michael R. Hieb, Ph.D.Alion Science & [email protected]

Page 2: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

What Is Battle Management Language (BML)?

• BML is the 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.

A Military-Specific Domain Ontology

Page 3: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Current Situation

• What we use today for “BML” is a loosely knit “language” tailored to interpersonal communication.

• Its vocabulary is found in Doctrinal Manuals, 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 DoD is implementing. • It will not support the integration of advanced modeling and

simulation with “digitized” command and control.

Page 4: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Principles of BML

BML must be unambiguous

BML must not constrain the expression of a commander’s intent

BML must use standardized C4I data and message representations

BML must allow forces to communicate information pertaining to their mission, their status and their environment

Page 5: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

BML Scope

C4I C4I

Simulation

Robotic Forces

BMLOrder

Page 6: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

BML Concept

MessagesData/Object

Models

XML/Data

Replication

C4IData Model

Doctrine

FM-1-02Other FMsARTEPs

BML

Page 7: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

BML Views

BMLDoctr

ine

Representation

Protocols

Page 8: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Course of Action Analysis ExampleGraphics convert to BML

Division attacks on order in zone to seize OBJ SLAM.Division Mission

Form of maneuver: PenetrationMain effort: BLUE-MECH-BDE2,

on order BLUE-ARMOR-BDE1Supporting effort: BLUE-MECH-BDE1

BLUE-ARMOR-BN1Deep: NoneReserve: BLUE-AVN-BDE1Security: BLUE-CAV-SQN1Tactical Combat Force: BLUE-MECH-TM1

Division Concept of Operations

Tasks to Subordinates

•Protect (Division Rear Area)•DSA•On order•Tactical Combat Force•BLUE-MECH-TM1

•Protect (Division left flank)•Zone (PL AMBER to PL BLUE)

•On order•Screen•BLUE-CAV-SQN1

•Support (B-A-BDE1)•Zone•On order•Follow and Support (B-A-BDE1)

•BLUE-ARMOR-BN1•Reserve•AA EAGLE•On order•Occupy•BLUE-AVN-BDE

•Seize (OBJ SLAM)•Zone•On order•Follows and Assumes (B-M-BDE2)

•BLUE-ARMOR-BDE1•Penetrate (MRR2)•Zone•On order•Attacks•BLUE-MECH-BDE2•Fix (MRR1)•Zone•On order•Attacks•BLUE-MECH-BDE1

•Why•Where•When•What•Who

Page 9: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

BML

XML/Data

Replication

ServiceData Model

Service Doctrine

BML

XML/Data

Replication

JointData Model Joint Doctrine

BML

XML/Data

Replication

NATO Doctrine

Ser

vice

Join

tIn

tern

atio

nal

CoalitionData Model

BML Scalability

Page 10: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

US Army BML Proof of PrincipleBML GUI

CAPES OTB

C4ISIXML – BML

Parser

BML acts as the common denominator

Multi-Source DatabaseAugmented with BML

Page 11: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Paragraph 1: Enemy Most Probable CoAWho What WhyWhereWhen

Page 12: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Extensible Modeling and Simulation Framework

• What is XMSF?– The Extensible Modeling and Simulation Framework (XMSF) is

defined as a set of Web-based technologies and services, applied within an extensible framework, that enables a new generation ofmodeling & simulation (M&S) applications to emerge, develop and interoperate.

• XMSF Precepts– Web-based technologies can provide an extensible modeling and

simulation architecture, to support a new generation of interoperable applications

– Simulation support is needed for operational warfighting capabilities– XML-based architecture can provide a bridge between emerging

rehearsal/reality/replay requirements and open/commercial Web standards

– Web = best tech strategy + best business case

Page 13: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

What Is XBML?

• XBML is BML provided as Web services

• XBML is being developed as an integral part of the Extensible Modeling and Simulation Framework

Page 14: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Applying XMSF Principles to BML

• BML must utilize Web Standards for Message Transmission • SOAP • XML

• BML must use a standard “vocabulary”• the Command and Control Information Exchange Data Model

(C2IEDM)

• This results in:

• Distributed, Flexible Interfaces

• Common Syntax and Semantics between Services, and Coalition Partners

• Unambiguous terms needed for Simulation Execution

Page 15: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

CAPESMSDB

OTB XMLParserC4ISI

SOAP

SOAP

SOAP

SOAP

BML GUISOAP

JDBC Interface

SOAP

UDP

ODBC ODBC

MSDBData

MSDBUpdates

Data forOTB

XML document

XBML Testbed Distributed Interfaces

Page 16: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Why use the C2IEDM for XBML?

• Developed by NATO data modeling experts (ATCCIS Permanent Working Group)

• Based on the Information Exchange Requirements on the Battlefield

• Unambiguous Representation of Information

• Extensible Data Model

• NATO Standard ADatP-32

• Used by the NATO Data Administration Group

• Core Data Model for various C4I Systems

• Reference Data Model for various Simulation Systems

• Data Model for Multilateral Interoperability Program (MIP)

Page 17: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

ACTION-TASK WHAT

ACTION-TASK-id (FK)

ACTION-TASK -minimum-durationACTION-TASK -maximum-durationACTION-TASK -estimated-durationACTION-TASK -planned-start-dateACTION-TASK -planned-end-dateACTION-TASK -planned-start-timeACTION-TASK -planned-end-time

WHEN

LOCATION WHERELOCATION-id

LOCATION -category-code

ACTION WHATACTION-id

ACTION-category-codeACTION-name

ACTION-OBJECTIVE

WHY

ACTION-id (FK)ACTION-OBJECTIVE-index

ACTION-OBJECTIVE-category-code

UNIT-TYPE

UNIT-TYPE-id (FK)

UNIT-TYPE -category-codeUNIT-TYPE -mobility-codeUNIT-TYPE -service-codeUNIT-TYPE -size-code

(echelon)

ACTION-category-code

ACTION-TASKACTION-EVENT

ORGANISATION-TYPEORGANISATION-TYPE-id

ORGANISATION-TYPE -category-code

ORGANISATION-TYPE-CATEGORY-CODE

UNIT-TYPEPOST-TYPE

ORGANISATION-id (FK)ACTION-id (FK)ORGANISATION-ACTION-ASSOCIATION-index

ORGANISATION-ACTION-ASSOCIATION -category-codeORGANISATION-ACTION-ASSOCIATION -effective-dateORGANISATION-ACTION-ASSOCIATION -effective-timeORGANISATION-ACTION-ASSOCIATION -intent-text

ORGANISATION-ACTION-ASSOCIATION

ORGANISATION WHO

ORGANISATION -category-codeORGANISATION -nickname-nameORGANISATION -type-id (FK)

ORGANISATION-id (FK)

ORGANIZATION-POINT

FACILITY-LOCATION

FEATURE-LOCATION

PERSON-POINT

MATERIAL-POINT

5 Ws in C2IEDM

Page 18: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

BML

5Wsin

C2IEDM

Nation XGround

CoalitionJoint

Nation YGround

Nation XAir

Agency ZDisaster Relief

Nation YMaritime

Joint BML Implementation Concept:Extend the C2IEDM

Page 19: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

CoalitionPlanningSystem

CoalitionC4I

System

GroundSimulation

Air Simulation

http transport

XML FormatC2IEDM Semantics5 Ws Representation

XBML Coalition Concept

XBML

Page 20: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

BML as a Domain Ontology

Upper Level Ontology

C2IEDM as an Underlying Data Model

BML as a Domain Ontology

Page 21: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

BML Developments

• Simulation Interoperability Standards Organization (SISO) Coalition BML Initiative

– United Kingdom– France– Germany– Strong Interest from other nations

• Other Services– Currently developing Air Tasking Order in BML– Working with JFCOM to demonstrate BML in large scale

exercise

Page 22: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Conclusions

• BML can provide a true common language among humans, machines, Services and national militaries– Will enable command and control interoperability within

Joint and coalition environments

• The concept of simulation applications implemented as Web services will support future network centric operational concepts

• We have demonstrated the capability of distributed, remote operation of web-enabled components

Page 23: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Backups

Page 24: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

The Problem

• Current and emerging simulations do not have the capability of directly interacting with C4I systems.

– They require the development of unique interfaces (“black boxes”) for each pairing of a simulation and a C4I system

– They require significant non-training audience intervention in order to support digital battle staff training and they will continue to do so until a standardized Battle Management Language is developed for communicating between these systems.

– The most difficult aspect of this problem is in communicating mission type orders from the command nodes to the supporting simulations. Generically this is known as the “Free Text Problem.”

Page 25: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

BML as an Enabler for Network Centric Operations

Network CentricKnow precisely, in real-time, location of all friendly and enemy forces

Robotics Integrated into ForceAmplify capability of manned elementsMulti-functional (RSTA, armed, sustainment)

Increased Reliance on Extended Range Engagement

Organic plus strategic and tactical supportLong range ISR and precision fires

Capable of Air-Mobile OperationsCommercial and minimum DoD strategic and tactical lift

Direct Fire Function

Infantry Carrier + C2 Function

Indirect Fire Function

Sensor Function

Organic &Inorganic

RSTA

Networked Command,Control &Comms

Page 26: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Extending the BML Vocabulary to Air Operations

• Begin with Air C2DIF (Command and Control Data Interchange Format)– Developed by Gestalt – AF/ESC Sponsorship (1998)– Vetted in over 120 Exercises/Events/Demonstrations/Tests

• Includes the Following Categories – Air Battle Plan

• Air Tasking Order (ATO)• Airspace Control Order (ACO)• Special Instructions (SPINS)• Mission Feedback • Friendly Order of Battle (FRoB)• Scenario Data (UOB)

– Mission Representation• Includes More Detailed Mission Planning Aspects of ATO Directed

Missions• Supports the “Decrease of the Controller Footprint Goal”

Page 27: Extensible Battle Management Language (XBML) A Methodology for Web

2004 ICCRTS, 14-16 September 2004, Copenhagen

Army, Joint and NATODoctrine Hierarchies