Invited Presentation C2/MS, Forum
46
Convergence of the Coalition Battle Management Language (C-BML) and the Military Scenario Definition Language (MSDL) Invited Presentation C2/MS, Forum Curtis Blais MOVES Institute Naval Postgraduate School [email protected] Kevin Gupton Applied Research Laboratories University of Texas at Austin [email protected] Kevin Heffner Pegasus Research & Technologies Montreal QC Canada [email protected]
description
Strategies for Alignment and Convergence of the Coalition Battle Management Language (C-BML) and the Military Scenario Definition Language (MSDL). Kevin Heffner Pegasus Research & Technologies Montreal QC Canada [email protected]. Invited Presentation C2/MS, Forum. Kevin Gupton - PowerPoint PPT Presentation
Transcript of Invited Presentation C2/MS, Forum
Strategies for Alignment and Convergence of the
Coalition Battle Management Language (C-BML)and the
Military Scenario Definition Language (MSDL)Invited Presentation
C2/MS, Forum
Curtis BlaisMOVES InstituteNaval Postgraduate [email protected]
Kevin GuptonApplied Research LaboratoriesUniversity of Texas at [email protected]
Kevin HeffnerPegasus Research & TechnologiesMontreal QC [email protected]
Previous Related Work
J. Abbott, C. Blais, K. Gupton, K.Heffner and L. Khimeche: Strategies for Application of the Coalition Battle Management Language (C-BML) with the Military Scenario Definition Language (MSDL), Spring 2012 SIW Invited Presentation
K. Heffner, Common Core Model for MSDL and C-BML Alignment, MSDL V2 Drafting Group Decision Analysis and Resolution Paper, June 2012
K. Gupton, K. Heffner, C. Blais, J. Abbott and C. Turnitsa, Management of C4I and M&S Standards with Modular OWL Ontologies, Spring 2011 SIW 11S-SIW-061
Presentation Outline
INTRODUCTIONWhat are C-BML and MSDL ?Why align C-BML and MSDL ?What needs to be aligned ?
CORE C-BML/MSDL MODELDefining a Core C-BML/MSDL ModelBuilding & Maintaining the Core C-BML/MSDL
ModelGenerating XML Schemas
CONCLUSIONS AND RECOMMENDATIONS
What are C-BML and MSDL ?
Define, schedule and exchange Orders according to 5W rules:
Exchange Reports on: Status and Location of friendly forces (CR POS) Enemy units discovered (CR OBS) Logistics
Who What WhenWhere
Advance To line L1QualifierAt Time T1Unit1
Why
Coalition Battle Management Language
Qualifier NameType NameName
What is C-BML ?
SISO-STD-011-2012-Draft
What are C-BML and MSDL ?
Entities{Organisation, Materiel,
Facility, Feature}
Event{Action, Task, Occurrence}
Location{Point, Line, Area,
Volume}
Place{Address,
Named location}
Time{Temporal point, Temporal region}
MSDL/C-BML Modeled Concepts
Symbology{Icons, Graphics, Overlay}
Materiel{Equipment,
Consumables}
Feature{Geographic,
Meteorological,Control Feature}
Organisation{Individual, Group,
Civil, Military }
Facility{Hospital, Runway,
Network, etc.}
MSDL/C-BML Modeled ConceptsWhat are C-BML and MSDL ?
Entities{Organisation, Materiel,
Facility, Feature}
Event{Action, Task, Occurrence}
Location{Point, Line, Area,
Volume}
Place{Address,
Named location}
Time{Temporal point, Temporal region}
Symbology{Icons, Graphics, Overlay}
Materiel{Equipment,
Consumables}
Feature{Geographic,
Meteorological,Control Feature}
Organisation{Individual, Group,
Civil, Military }
Facility{Hospital, Runway,
Network, etc.}Who
What
Where
When
Why
Why align C-BML and MSDL ?
“
C-BML
used to task
reports sent to
generates tasks in
Simulation
can generate
Typical MSDL/C-BML Information ExchangesHow are C-BML and MSDL used together ?
generates reports in
also can be used to initialize
C2 System
records snapshot as
used to initializeMSDL
SCENARIO INITIALIZATION
SCENARIO EXECUTION
References Initial
Tasking
References Initial TaskOrg, Materiel,
Unit Status/Position
“
C-BML
used to task
reports sent to
generates tasks in
Simulation
can generate
How are C-BML and MSDL used together ?
generates reports in
also can be used to initialize
C2 System
records snapshot as
used to initializeMSDL
SCENARIO INITIALIZATION
SCENARIO EXECUTION
References Initial
Tasking
References Initial TaskOrg, Materiel,
Unit Status/Position???
Typical MSDL/C-BML Information Exchanges
C-BML/MSDL Alignment Problem Statement
IFC-BML and MSDL stakeholders need for these standards to work “nicely” together,
THENthey need to have a common core aligned data model, andthey need to use a common physical format.
FURTHERMORE, IFC-BML maintains the requirement to use the MIP JC3IEDM as its underlying data model.
THENThe common core C-BML/MSDL data model should use the MIP- JC3IEDM or derived products as the initial and primary source.
What needs to be aligned ?
Alignment
1. Data Misalignment Example
MSDL: A unit has a mandatory symbol_ID, echelon defined as a symbol_modifier, and has relations to other units.
ORJC3IEDM/C-BML: A unit is a type of military organisation that is defined by properties such as echelon, category, service etc… and could have an extension for optional symbol information.
2. Physical Formats XML Schema Style Guide, Naming and Design Rules
Defining a MSDL/C-BML Common Core Model
Multi-lateral Interoperability Programme
MIP and NATO
• JC3IEDM has been ratified as STANAG 5525
• MIP specification is included in NATO C3 Technical Architecture
• Many national C2IS implement MIP specifications
1976 1980 1984 1988 1992 1996 2000 2004 2008 2012 2016 2020
NATO Long-Term Defense Plan (LTDP)
Army/Allied Tactical C2 Information System
(ATCCIS)
MIP replaces Battlefield Interoperability Program
(BIP)
ATTCIS and MIP merge to from Land C2 Information Exchange
Data Model (LC2IEDM)
LC2IEDM -> C2IEDM
C2IEDM -> JC3IEDM
JC3IEDM -> MIM
Concise History of MIP
Multi-lateral Interoperability Programme
MIP Information Model* http://mipcee-svn.lsec.dnd.ca/DEV/SVN/PIM/tags/Releases/MIM%201.0
• Many improvements from JC3IEDM150 Change proposals ~ 11,237 changesStructural Simplifications
E.g. Merged ObjectItem, ObjectType and ObjectItemStatus Improved comprehensibilityConsistent use of Metadata
Independent of Exchange Mechanisms Improved Modularity
• Tool Supported Automated ApproachMaintenance and Evolution of UML ModelManagement of Business RulesTransformation of Model to
Create other models Generate XSD Schemas
*See M.Gerz, N. Bau “A Platform-Independent Reference Data Model for a Future Interoperability Solution”, 17th ICCRTS, Fairfax VA USA June 2012
MSDL/C-BML Core Common Model
C-BML already uses something close to the MIM:Organisation, MSDL easily could use the same definitions
Same for Materiel, Equipment, Consumables
MIM Feature
Already aligned
MSDL Environment already uses MIM-MeteorologicalFeature
MSDL could use other Feature branches (e.g. ControlFeature)
RECOMMENDATION: MSDL should reference ControlFeatures and Units independent of the Tactical Graphics and Symbology. These can be added as extensions.
MSDL/C-BML Core Common Model
MSDL/C-BML Core Common Model
Proposed Approach for Building a MSDL/C-BML
Common Core Model
1. Start with MIM foundation classes2. Delete /Add / Modify as Required3. Use an automated, repeatable process4. Maintain a model, but generate schemas
MIP Information Model 1.0 (MIM-1.0)
MIP Transformation and Change Proposal Tools
MIP Change Proposal (CP) Processor
MSDL/C-BML Core Model Generation Procedure
MSDL/C-BML Core Model Generation Procedure MIP Change Proposal (CP) Processor
Input is MIM Enterprise Architect UML ModelChange Proposal is described as XML file Can add/remove/modify • Packages• Classes/Enumerations, • Attributes • Associations• Stereotypes• Tagged values
Tagged values can be used for model transformation• XSD Generation• OWL package generation• Custom
MIM model can evolve independently of C-BML/MSDL Model Can generate mapping classes between MIP products & C-BML/MSDLCan update C-BML & MSDL products upon MIP update, as required
Can remain independent of MIP types while re-using/modifying as few or many types, as required.
MIP CP Processor Functions
MIP CP Processor Functions (zoom)
AddTag function has been added to support C-BML/MSDL model transformation requirements
MIP Information Model 1.0 (MIM-1.0)
• Entire MIM is contained in one package.• C-BML utilizes a multi-package approach. • How to re-create MIM in a multi-packaged form ?
Example Model Generation“Repackaging the MIM”
MSDL/C-BML Core Model Generation Procedure
Problem - Current MIM contains:• one package for all classes, and• one package for all enumerations.
Solution - Create Change Proposal that:• defines a set of packages;• moves classes from root package to specified
packages
(See Backup Slides)
MIM 1.0 – Repackaging Change Proposal File
MIM 1.0 – Repackaged (Metadata Package)
This Change Proposal actually has been submitted for consideration during the next MIP meeting in September 2012.
The MIP-IPT-F Group is working with the SISO C-BML Phase 2 DG to support C-BML/MSDL Model Generation Requirements, including automated schema generation, as described in the following slides.
MSDL/C-BML Core Model Generation Procedure
Example XML Schema Generation“Generating Action.xsd”
MSDL/C-BML Core Model Generation Procedure
MIM 1.0 – UML -> XSD Transform Action Package
MIM 1.0 – UML -> XSD Transform Action Package (Cont’d)
MIM 1.0 – Action.xsd (auto-generated)
MSDL/C-BML Core Model Generation Procedure
C2IEDMJC3IEDM
MIM 1.0 MIM 1.1
MSDL/C-BML Core Model Description
V1.0
MSDL/C-BML Core Model Description
V1.1
MSDL/C-BML Core Model Description
V2.0
MIP CP TOOL
MIM 2.0
MSDL CBML Core Model
MSDL/C-BML Core Schemas
V1.0
UML Transform
MSDL/C-BML XSD Schema Naming and
Design Rules
C-BML/MSDLCore Model
V1.0
MSDL/C-BML Core Model Generation Procedure
C2IEDMJC3IEDM
MIM 1.0 MIM 1.1
MSDL/C-BML Core Model Description
V1.0
MSDL/C-BML Core Model Description
V1.1
MSDL/C-BML Core Model Description
V2.0
MIP CP TOOL
MIM 2.0
MSDL CBML Core Model
MSDL/C-BML Core Schemas
V1.1
UML Transform
MSDL/C-BML XSD Schema Naming and
Design Rules
C-BML/MSDLCore Model
V1.1
MSDL/C-BML Core Model Generation Procedure
C2IEDMJC3IEDM
MIM 1.0 MIM 1.1
MSDL/C-BML Core Model Description
V1.0
MSDL/C-BML Core Model Description
V1.1
MSDL/C-BML Core Model Description
V2.0
MIP CP TOOL
MIM 2.0
MSDL CBML Core Model
MSDL/C-BML Core Schemas
V2.0
UML Transform
MSDL/C-BML XSD Schema Naming and
Design Rules
C-BML/MSDLCore Model
V2.0
MSDL/C-BML Core Model Generation Procedure
C2IEDMJC3IEDM
MIM 1.0 MIM 1.1
MSDL/C-BML Core Model Description
V1.0
MSDL/C-BML Core Model Description
V1.1
MSDL/C-BML Core Model Description
V2.0
MIP CP TOOL
MIM 2.0
MSDL CBML Core Model
MSDL/C-BML Core Schemas
V2.0.1
UML Transform
MSDL/C-BML XSD Schema Naming and
Design Rules
C-BML/MSDLCore Model
V2.0.1
Conclusions and Recommendations
Conclusions
• We have worked out a first approach for unification of MSDL and C-BML data models
• Approach has been developed in collaboration with the MIP and includes an automated engineering process
• There are few technical obstacles but need to address SISO governance issues
Recommendations
• C-BML and MSDL PDGs need to work together to define an alignment and convergence strategy
• Options:– Merge current PDGs to create a combined PDG to develop the unified
data model and subsequent C-BML/MSDL SISO products– MSDL independently applies the C-BML Core Data Model– Create a Working Group (e.g., like DIS-ENUM) responsible for
providing a unified data model to the C-BML and MSDL PDGs– C-BML and MSDL PDGs form a Joint Team to develop the unified data
model; generate separate products from the unified model
*
Questions ?
Back-up slides
Requirements
MSDL Requirementsa. Scope
• Scenario Initialization of Sim• Initialization of C2• Scenario Snapshot• Multi-level with LAND-focus (currently)
b. Basic Elements• Scenario Description (e.g. ID, options)• Environment (e.g. Weather)• Symbology and Tactical Graphics• LOCATION• LOGISTICS (e.g. Equipment/Material)• ORGANISATION• INSTALLATIONS/FACILITIES• OVERLAYS
C-BML Content & Structure Requirements* a. Scope• Scenario Execution• Multi-level, Joint, Multi-national, • Multi-Domain (AIR, LAND, MARITIME)
b. Basic Elements (e.g. 5Ws, grammar)• Events / Actions / Tasks• Message Metadata• LOCATION• LOGISTICS (e.g. Equipment/Material)• ORGANISATION • INSTALLATIONS/FACILITIES• OVERLAYS / INFORMATION GROUPS
c. Expressions/Messages• Friendly/Enemy Situation• Friendly/Enemy COA• Status reports • Etc…
*C-BML also includes an IEM/Services Specification.
