1 / 46

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). Kevin Heffner Pegasus Research & Technologies Montreal QC Canada k.heffner@pegasim.com. Invited Presentation C2/MS, Forum. Kevin Gupton

paniz
Télécharger la présentation

Invited Presentation C2/MS, Forum

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 k.heffner@pegasim.com Invited Presentation C2/MS, Forum Kevin Gupton Applied Research Laboratories University of Texas at Austin kgupton@arlut.utexas.edu Curtis Blais MOVES Institute Naval Postgraduate School clblais@nps.edu

  2. 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

  3. Presentation Outline • INTRODUCTION • What are C-BML and MSDL ? • Why align C-BML and MSDL ? • What needs to be aligned ? • CORE C-BML/MSDL MODEL • Defining a Core C-BML/MSDL Model • Building & Maintaining the Core C-BML/MSDL Model • Generating XML Schemas • CONCLUSIONS AND RECOMMENDATIONS

  4. What are C-BML and MSDL ?

  5. What is MSDL ? SISO-STD-007-2008 http://goo.gl/cEtiU

  6. Coalition Battle Management Language What is C-BML ? • 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 Where When Why Qualifier Name Name Name Qualifier Type Unit1 Advance To line L1 At Time T1 SISO-STD-011-2012-Draft

  7. What are C-BML and MSDL ? MSDL/C-BML Modeled Concepts Entities {Organisation, Materiel, Facility, Feature} Organisation {Individual, Group, Civil, Military } Facility {Hospital, Runway, Network, etc.} Feature {Geographic, Meteorological, Control Feature} Materiel {Equipment, Consumables} Event {Action, Task, Occurrence} Place {Address, Named location} Location {Point, Line, Area, Volume} Symbology {Icons, Graphics, Overlay} Time {Temporal point, Temporal region}

  8. What are C-BML and MSDL ? MSDL/C-BML Modeled Concepts Entities {Organisation, Materiel, Facility, Feature} Organisation {Individual, Group, Civil, Military } Facility {Hospital, Runway, Network, etc.} Who Feature {Geographic, Meteorological, Control Feature} Materiel {Equipment, Consumables} Event {Action, Task, Occurrence} What Why Where Place {Address, Named location} Location {Point, Line, Area, Volume} When Symbology {Icons, Graphics, Overlay} Time {Temporal point, Temporal region}

  9. Why align C-BML and MSDL ?

  10. How are C-BML and MSDL used together ? Typical MSDL/C-BML Information Exchanges SCENARIO EXECUTION reports sent to generates reports in C2 System Simulation C-BML used to task generates tasks in References Initial TaskOrg, Materiel, Unit Status/Position References Initial Tasking “ can generate used to initialize MSDL also can be used to initialize records snapshot as SCENARIO INITIALIZATION

  11. How are C-BML and MSDL used together ? Typical MSDL/C-BML Information Exchanges SCENARIO EXECUTION reports sent to generates reports in C2 System Simulation C-BML used to task generates tasks in ??? References Initial TaskOrg, Materiel, Unit Status/Position References Initial Tasking “ can generate used to initialize MSDL also can be used to initialize records snapshot as SCENARIO INITIALIZATION

  12. C-BML/MSDL Alignment Problem Statement • IF • C-BML and MSDL stakeholders need for these standards to work “nicely” together, • THEN • they need to have a common core aligned data model, and • they need to use a common physical format. • FURTHERMORE, IF • C-BML maintains the requirement to use the MIP JC3IEDM as its underlying data model. • THEN • The common core C-BML/MSDL data model should use the MIP- JC3IEDM or derived products as the initial and primary source.

  13. What needs to be aligned ?

  14. Alignment • Data Misalignment Example • MSDL: A unit has a mandatory symbol_ID, echelon defined as a symbol_modifier, and has relations to other units. OR • JC3IEDM/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. • Physical Formats • XML Schema Style Guide, Naming and Design Rules

  15. Defining a MSDL/C-BML Common Core Model

  16. Multi-lateral Interoperability Programme • Concise History of MIP • JC3IEDM -> MIM • Army/Allied Tactical C2 Information System (ATCCIS) • MIP replaces Battlefield Interoperability Program (BIP) • LC2IEDM -> C2IEDM 1976 1980 1984 1988 1992 1996 2000 2004 2008 2012 2016 2020 • ATTCIS and MIP merge to from Land C2 Information Exchange Data Model (LC2IEDM) • C2IEDM -> JC3IEDM • NATO Long-Term Defense Plan (LTDP) • 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

  17. Multi-lateral Interoperability Programme • MIP Information Model* • http://mipcee-svn.lsec.dnd.ca/DEV/SVN/PIM/tags/Releases/MIM%201.0 • Many improvements from JC3IEDM • 150 Change proposals ~ 11,237 changes • Structural Simplifications • E.g. Merged ObjectItem, ObjectType and ObjectItemStatus • Improved comprehensibility • Consistent use of Metadata • Independent of Exchange Mechanisms • Improved Modularity • Tool Supported Automated Approach • Maintenance and Evolution of UML Model • Management of Business Rules • Transformation 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

  18. 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

  19. MSDL/C-BML Core Common Model 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.

  20. MSDL/C-BML Core Common Model

  21. Proposed Approach for Building a MSDL/C-BML Common Core Model • Start with MIM foundation classes • Delete /Add / Modify as Required • Use an automated, repeatable process • Maintain a model, but generate schemas

  22. MIP Information Model 1.0 (MIM-1.0)

  23. MIP Transformation and Change Proposal Tools

  24. MSDL/C-BML Core Model Generation Procedure • MIP Change Proposal (CP) Processor

  25. MSDL/C-BML Core Model Generation Procedure • MIP Change Proposal (CP) Processor • Input is MIM Enterprise Architect UML Model • Change 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/MSDL • Can 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.

  26. MIP CP Processor Functions

  27. MIP CP Processor Functions (zoom) AddTag function has been added to support C-BML/MSDL model transformation requirements

  28. 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 ?

  29. MSDL/C-BML Core Model Generation Procedure Example Model Generation“Repackaging the MIM” (See Backup Slides) 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

  30. MIM 1.0 – Repackaging Change Proposal File

  31. MIM 1.0 – Repackaged (Metadata Package)

  32. MSDL/C-BML Core Model Generation Procedure 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.

  33. MSDL/C-BML Core Model Generation Procedure Example XML Schema Generation“Generating Action.xsd”

  34. MIM 1.0 – UML -> XSD Transform Action Package

  35. MIM 1.0 – UML -> XSD Transform Action Package (Cont’d)

  36. MIM 1.0 – Action.xsd (auto-generated)

  37. MSDL/C-BML Core Model Generation Procedure C2IEDM MSDL/C-BML XSD Schema Naming and Design Rules JC3IEDM MIM 2.0 MIM 1.1 MIM 1.0 MSDL CBML Core Model MIP CP TOOL UML Transform MSDL/C-BML Core Schemas V1.0 MSDL/C-BML Core Model Description V1.0 MSDL/C-BML Core Model Description V1.1 MSDL/C-BML Core Model Description V2.0 C-BML/MSDL Core Model V1.0

  38. MSDL/C-BML Core Model Generation Procedure C2IEDM MSDL/C-BML XSD Schema Naming and Design Rules JC3IEDM MIM 2.0 MIM 1.1 MIM 1.0 MSDL CBML Core Model MIP CP TOOL UML Transform MSDL/C-BML Core Schemas V1.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 C-BML/MSDL Core Model V1.1

  39. MSDL/C-BML Core Model Generation Procedure C2IEDM MSDL/C-BML XSD Schema Naming and Design Rules JC3IEDM MIM 2.0 MIM 1.1 MIM 1.0 MSDL CBML Core Model MIP CP TOOL UML Transform MSDL/C-BML Core Schemas V2.0 MSDL/C-BML Core Model Description V1.0 MSDL/C-BML Core Model Description V1.1 MSDL/C-BML Core Model Description V2.0 C-BML/MSDL Core Model V2.0

  40. MSDL/C-BML Core Model Generation Procedure C2IEDM MSDL/C-BML XSD Schema Naming and Design Rules JC3IEDM MIM 2.0 MIM 1.1 MIM 1.0 MSDL CBML Core Model MIP CP TOOL UML Transform MSDL/C-BML Core Schemas V2.0.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 C-BML/MSDL Core Model V2.0.1

  41. Conclusions and Recommendations

  42. 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

  43. 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 *

  44. Questions ?

  45. Back-up slides

  46. Requirements • C-BML Content & Structure Requirements* • Scope • Scenario Execution • Multi-level, Joint, Multi-national, • Multi-Domain (AIR, LAND, MARITIME) • Basic Elements (e.g. 5Ws, grammar) • Events / Actions / Tasks • Message Metadata • LOCATION • LOGISTICS (e.g. Equipment/Material) • ORGANISATION • INSTALLATIONS/FACILITIES • OVERLAYS / INFORMATION GROUPS • Expressions/Messages • Friendly/Enemy Situation • Friendly/Enemy COA • Status reports • Etc… • MSDL Requirements • Scope • Scenario Initialization of Sim • Initialization of C2 • Scenario Snapshot • Multi-level with LAND-focus (currently) • 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 also includes an IEM/Services Specification.

More Related