The Application of BOMs for Enabling MultiResolution Modeling

1
The Application of BOMs for EnablingMulti-Resolu
tion Modeling

• Tram Chase
• Paul Gustavson
• SimVentions, Inc.

Latika Eifert U.S. Army RDECOM
2
Introduction

• 1000s of entities
• To be realistic requires high resolution
• High resolution requires considerable resources

3
Whats the need?
An easy way to dynamically change the resolution
of models as the simulation conditions and
federates needs vary.
4
What is Multi-Resolution Modeling?

• Multi-Resolution Modeling is the practice of
  representing the synthetic world with models of
  varying levels of resolution. This can be done by
  creating multiple modules for the same model that
  can be exchanged depending upon the needs of the
  study or training.
• -Roger D. Smith
• 2001 Game Developers Conference

5
Requirements forSupporting MRMs

• Models must operate at many levels of resolution
• Supports a variety of models (terrain,
  environment, physics, 3D)
• Interfaces/interoperates with current
  architecture/frameworks
• Support for real-time data links (live and
  constructive entities)
• Reduction of run-time computational load.
• Improved federate/federation performance
• Minimal impact on assessment
• Minimal attribution loss

• Allows clean separation between the interface
  (and coupling of interfaces) and the actual
  models used to support the behavior identified in
  an interface,
• Multi-resolution models can support any one
  interface
• At the federate level, those behavior models can
  continue to be applied generating full resolution
  within the federate responsible for the
  associated entity or entities.
• Systems can choose from an assortment of BOM
  implementations that best represents their needs
  and system capabilities, even though the
  interface that is applied and used by all players
  may be equivalent.

6
What are BOMs?

• A reusable package of information representing or
  supporting a pattern of interplay
• Used as a building block for composable
  simulation environments.

Pattern of interplay - reflects a set of
activities related to one or more conceptual
entities used for accomplishing a common
objective, capability, or purpose
7
What are BOMs?

• A reusable package of information representing or
  supporting a pattern of interplay
• Used as a building block for composable
  simulation environments.
• Accomplished by capturing Pattern Components
  representing the relationship of activities among
  conceptual entities (FOM level), and
• Defining Behavior Components that model the
  needed behavior required of a conceptual entity
  to support patterns (Federate level)

8
Example Pattern of Interplay

• Common (subconscious) representation of real
  world activities
• Often modeled and represented by federates and
  federations
• Examples
• DIS 1278
• Weapons Fire
• Logistics Support
• Simulation Management
• Emission Regeneration
• Radio Comms
• Danzig Approach for representing threats

9
Example Pattern of Interplay

• Common (subconscious) representation of real
  world activities
• Often modeled and represented by federates and
  federations
• Examples
• DIS 1278
• Weapons Fire
• Logistics Support
• Simulation Management
• Emission Regeneration
• Radio Comms
• Danzig Approach for representing threats

10
ProcessDefine - Discover - Design - Develop
11
Applying BOMs

• BOM candidate was a simple race.
• Consists of a race manager, a competitor, a
  track, and the environment.
• The roles of each participant were defined and
  laid out in a UML sequence diagram

12
Interface to Implementation
Name
Name
Name RaceBOMl
Type
Type
Type IFBOM
Version
Version
Version 1.0
Mod Date
Mod Date
Mod Date 2004-03-05
Security Class
Security Class
Security Class
Release Restriction
Release Restriction
Release Restriction
Purpose
Purpose
Purpose
Model Identification
Model Identification
Model Identification
Behavior Description
Application Domain
Application Domain
Application Domain
IF BOMs Supported
Description
Description
Description
(Key BOM meta
-
data)
(Key BOM meta
-
data)
(Key BOM metadata)
State(s) (Transitions)
Use Limitation
Use Limitation
Use Limitation
Name
Use History
Use History
Use History
Entry Action(s)
ECAP BOM
Input Action(s)
Keywords
Keywords
Keywords
IF BOM
ECAP BOM IMPLEMENTATION
Output Action(s)
POCs
POCs
POCs
Exit Action(s)
References
References
References
Others
Others
Others
Behavior Description
Glyph
Glyph
Glyph
IF BOMs Supported
Pattern Description
Pattern Description
Pattern Description
State(s) (Transitions)
Steps
Steps
Steps
Name
Entry Action(s)
Input Action(s)
Object
Object
Objects
Objects
Output Action(s)
Models
Models
Exit Action(s)
Interactions
Interactions
(1516.2)
(1516.2)
Model Definition
Model Definition
Data Types
Data Types
Behavior Description
Notes
(Representing Model
Notes
(Representing Model
IF BOMs Supported
Definition of a BOM)
Definition of a BOM)
State(s) (Transitions)
Triggers
Triggers
Name
Events
Events
Entry Action(s)
Message
Message
Input Action(s)
Output Action(s)
Exit Action(s)
13
Building BOMs
14
Race BOM
IFBOM Classes
ECAP BOM Classes
Various Degrees of Resolution
15
ECAP BOM MRMs

• A properly constructed IF BOM allows compatible
  ECAP BOMs to be swapped in and out during
  simulation runtime. It follows that these models
  could vary in resolution, providing for dynamic
  upgrading/downgrading based on the needs of a
  simulation.

16
Race Demo
MR Federate Demo
17
BOM Mapping to the HLA
Federate View (Federate Capability)
EBI
EBI
EBI
EBI
HLAObjectModels
SOM
Interface View (Federation Agreement)
IF BOMs
ECAP BOMs
(FOM /- )
MetadataRich
FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve)
DLC
Required
Communication View
Optional
RTI
18
EBIs and ECAP BOM Interfaces
EncapsulationSub-View
Federate Code/Libraries

• ECAP BOM Implementations Types
• XML-based (SRML)
• Source Code (C, C, Java, Delphi, )
• Binary (DLL, DSO, .NET Assembly, Java Bean, COM,
  )
• Platform Specific (OneSAF Component)

EBI
EBI
EBI
EBI
Reverse engineer-able - useful for describing
federate capability
Provides framework for defining components
ECAP BOM a
ECAP BOM b
ECAP BOM c
ECAP BOM d
ECAP BOM x
Interfaces
Assembly of ECAP BOMs used to formulate SOM
SOM

• ECAP BOMs provide a way to define whats needed
  to model a conceptual entity
• ECAP BOMs provide a way for federates
• to describe their model capabilities (object
  class attributes, methods, event handlers,
  states)
• Identify what IF BOMs (i.e. defined patterns of
  interplay) they support
• Much like how web services can be described
  using WSDL
• Federates could be described by their set of ECAP
  BOMs
• SOMs are either
• Not necessary, or
• Easily generated by coupling the ECAP BOMs and
  dropping the behavioral description elements

19
Findings and Results

• BOMs allow for separation between interface and
  implementation
• This allows EBIs to be built, applied and scaled
  to the resolution needed.
• BOMs enable dynamic composability of
  multi-resolution models
• Effort provided feedback to BOM Product
  Development Group

Can be applied in various MS domains, e.g.,
Manufacturing, Medical, DoD, Training
20
Recommendations

• Encourage BOM PDG to continue effort ECAP BOM
  standard
• Broaden ECAP development and use
• Establish sandbox of available ECAP BOMs and EBIs
• Further exploration of SRML for EBIs
• Adoption of BOMs in the Manufacturing PDG

21
Questions?

• Links
• BOMs www.boms.info
• SRML www.w3c.org
• Events
• BOM PDG Meeting Thursday 800-1200
• Contact Info
• Tram Chase
• SimVentions, Inc.
• tchase_at_simventions.com

22
Addendum Slides
23
What do we mean by Patterns?
Each pattern describes a problem which occurs
over and over again in our environment, and then
describes the core of the solution to that
problem, in such a way that you can use this
solution a million times over, without ever doing
it the same way twice. - Christopher Alexander
04S-SIW-111Applying Design Patterns for Enabling
Simulation InteroperabilityPaul Gustavson
(SimVentions)Dr. Katherine Morse (SAIC)Bob Lutz
(JHU/APL) Steve Reichenthal (Boeing)
an abstraction of the occurrences of events that
happen over time amongst specific actors to
support a common, repeatable operation.
24
BOM Metadata
Essential for Reusability
The pattern of interplay is described as a
sequence of steps. Each step can be associated
with an event or another BOM.
Interface BOM
25
BOM Metadata
Essential for Reusability
The pattern of interplay is supported by one or
more conceptual entity. The behavior for a
conceptual entity can be described as a set of
states linked to the events of a pattern or
another BOM.
Encapsulated BOM
26
BOM Model Definition
Object
Object
Objects
Objects
Models
Models
Interactions
Interactions
(1516.2)
(1516.2)
Model Definition
Model Definition
Data Types
Data Types
Notes
Notes
(Representing Model
(Representing Model
Definition of a BOM)
Definition of a BOM)
Triggers
Events
Message
HLA 1516 OMT
Events