Battle Management Language (BML) is the unambiguous representation of all military Command and Control (C2) elements necessary to generate an executable plan of action – from actions to tasks, and from platforms to units. BML consists of three views: Doctrine, Representation, and Protocol. The Doctrine view describes the operational relevance of each C2 term, the Representation view enables the modeling of these C2 terms, and the Protocol view delivers an executable plan to the target system, which can be Command & Control systems, Simulation systems, or Robotic systems. The first prototype of BML was focused on the US Army ground operations, specifically the operations order (OPORD). However, none of the characteristics of BML cited above requires limiting BML to one service. Quite the opposite – from the beginning, other services and nations were part of the BML concepts. To support the United States Joint Forces Command (JFCOM), the BML team was tasked to prove the feasibility of multi-service operations within the common framework of BML. To this end, air operations were added to existing ground operations within BML using a common representation. An initial prototype was demonstrated at the Interservice/Industry Training, Simulation & Education Conference in December 2004 and is described in this paper. This paper summarizes the ongoing integration of air operations BML with ground operations BML and recommends how to approach future challenges that will occur when integrating other service or coalition requirements into a common methodological framework for BML.
[1]
Keywords
,
2006,
Vision Research.
[2]
Andreas Tolk,et al.
Coalition Battle Management Language
,
2004
.
[3]
Martin S. Kleiner,et al.
Communication mission-type orders to virtual commanders
,
1998,
1998 Winter Simulation Conference. Proceedings (Cat. No.98CH36274).
[4]
M. Hieb,et al.
Merging National Battle Management Language Initiatives for NATO Projects
,
2004
.
[5]
S. Carey,et al.
Standardizing Battle Management Language – Facilitating Coalition Interoperability
,
2002
.
[6]
Michael R. Hieb,et al.
Developing Battle Management Language into a Web Service
,
2004
.
[7]
Andreas Tolk,et al.
Taxonomies, Ontologies, and Battle Management Language - Recommendations for the Coalition BML Stud
,
2005
.
[8]
Andreas Tolk,et al.
Ideas for a Common Framework for Military M&S and C3I Systems
,
2003
.
[9]
Bo Sun,et al.
Web Services based on the C2IEDM - Data Mediation and Data Storage
,
2005
.
[10]
Andreas Tolk,et al.
Modeling and Simulation Integration with Network-Centric Command and Control Architectures
,
2003
.
[11]
Marnie R. Salisbury.
COMMAND AND CONTROL SIMULATION INTERFACE LANGUAGE (CCSIL): STATUS UPDATE
,
1995
.
[12]
Andreas Tolk,et al.
The Levels of Conceptual Interoperability Model
,
2003
.