An Application Extension for the Military Scenario Definition Language

1
An Application Extension for theMilitary
Scenario Definition Language

• Saikou Diallo, Dr Andreas Tolk,
• Virginia Modeling Analysis Simulation Center
• Old Dominion University
• Norfolk, Virginia, USA
• Sdiallo,Kdupi,atolk_at_odu.edu
• Wayne Civinskas
• Lockheed Martin Simulation, Training
  SupportAdvanced Simulation Centers (ASC)164
  Middlesex TurnpikeBurlington, Massachusetts
  01803wayne.j.civinskas_at_lmco.com

2
Outline

• Introduction
• Motivation
• Decoupling MSDL from MSDE
• Mapping MSDL to BML and C2IEDM
• CultureSim Extensions

3
Introduction

• Scenario Generation
• Simulation Dependant
• Time consuming and costly
• Error prone and not portable
• Military Scenario Definition Language
• Simulation independent
• Portable scenarios
• Brings consistency to scenario generation process

4
Motivation

• How can I extend MSDL?
• Can I Use MSDL without MSDE?

5
MSDL and CultureSim

• Cultural features
• Urban Warfare
• Buildings
• Cars
• Bikes
• Crowds
• Individuals
• Groups
• Crowds
• Can I use MSDL to initialize these elements?
• Investigate MSDL
• Decouple MSDL from MSDE

6
Decoupling MSDL from MSDE

• MSDL
• Task Organization
• Plans
• Equipments
• Tactical Overlays
• Installations
• Tactical Graphics
• Terrain
• MSDE
• Military Scenario Definition Environment
• Tightly coupled with MSDL
• Contains Enumerations referenced in MSDL

7
MDSL AS IT STANDS

• Current Format
• Well Defined XML schemas
• Main schema referencing enumeration schemas
• All enumerations are not included in the schema
• Assumptions
• MSDL users have access to MSDE
• MSDL users will know how to read the schemas
• MSDL users have access to standard documents

8
Decoupling Algorithm
ADD Primary Keys Foreign Keys Unique
Keys Relational Fields
MSDL Database
MSDL.XSD
9
Mapping to BML and C2IEDM

• Common Ontology
• 5 W from C-BML
• Identify them in MSDL
• Common Reference Model
• C2IEDM as the CRM
• Map to C2IEDM
• SOA and Web Services
• Use Atomic Services
• Use Mediation Services

10
WHO, WHAT, WHERE, WHEN, WHY
11
RESULTS

• Generate MSDL from C2IEDM or BML
• Read and Display MSDL XML
• Write to C2IEDM and BML from MSDL
• Another Proof of Concept for the Architecture
• Shows link between C-BML and MSDL

12
EXTENDING MSDL

• CultureSim Initialization
• There is no agreement in the community
• Initialization is simulation dependant
• There is a core information need
• It is currently under investigation

• MSDL Extensions
• Basic Definitions
• Stochastic Behavior
• Agents, groups, crowds
• MSDL PDG
• Scope of MSDL
• Core MSDL
• Extension Validation

13
The Crowd Example

• Knowledge It represents the relationship between
  the entity and the virtual environment. This
  includes potential obstacles to avoid, expected
  motion and action, and collective knowledge.
•   Beliefs They represent the internal status of
  the entity (happy, sad etc) as well as possible
  behaviors. The group behaviors identified so far
  is Flocking, Following, Goal Changing,
  Attraction, Repulsion, Split, Space adaptability
  and Safe Wandering.
•     Intention This represents the objectives of
  the crowd and it can be influenced by individual
  elements in the crowd.

14
Intension Vs Extension

• Intension
• Intension refers to the set of all possible
  things that a word could represent. Extending
  MSDL by intension means that the model should
  list all of the types that could ever exist.
• Extension
• Extension refers to the set of all the actual
  things that a word could represent. Extending by
  extension means including all of the actual types
  necessary to describe civilian entities.

• For MSDL
• Need to stabilize the mode
• Intension must be agreed upon
• Extension are done in a vertical fashion
• The CultureSim Extensions are needed but the jury
  is still out as to whether MSDL is the adequate
  choice
• Tools based approach depending on focus and
  intent is satisfactory for now
• Symbology extension in the works

15
QUESTIONS???