Application of BOMs for Supporting Aggregation

1
Application of BOMs for SupportingAggregation

• Paul Gustavson
• Tram Chase
• SimVentions

Mike Haddad PEOSTRI
2
Topics

• Problems with Large Scale Simulations
• What are BOMs?
• Aggregation Approach using BOMs(04S-SIW-024)
• Multi-Resolution Modeling Approach using
  BOMs(04S-SIW-052)

These are all issues / solutions focused on the
concept of composability
3
Background

• Large-scale simulations exercises
• High entity loads
• High degree of resolution needed
• Undue strain on Federation.
• Resolution scaling and aggregation
• Concern for water down effect
• Lack of techniques
• No common infrastructure

Aggregation - the coupling of multiple
entities/models into a single inclusive group
4
Aggregation Goals

• Develop aggregation mechanism
• capable of managing load balancing
• Minimal impact on
• performance or
• execution analysis and assessment.
• Cost effective
• Capable of support agg/deagg before or during
  execution
• Support large scale simulations
• Helps to reduce independent high resolution
  models to more efficient, lower resolution models
• Varying Models must be able to interact
• New Need Adaptability among diverse models

• reduce amount of traffic

• preserve simulation validity

NEEDS

• support different states of aggregation

• accessible to different federates

• To achieve these needs
• Separate Representation from Model (Interface
  vs- Implementation)
• Couple Representations
• Provide capability via a Web Service

5
But - What are BOMs?
6
Composability View
Model Composability
System Composability
FEDEP
an idea that has been useful in one practical
context and will probably be useful in
others. - Martin Fowler
Conceptual Models
Reusable Components
Plug Play Systems

• the capability to select and assemble simulation
  components in various combinations into
  simulation systems to satisfy specific user
  requirements. - Dr. M. Petty

Base ObjectModels
Patterns
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
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

8
Two Different Facets of BOMs

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

9
BOM Example
Arrival Trigger
Greeting Message
Seating Message
Food Order Request Message
Food Order Response Message
Waiting (reading paper)
Food Served Trigger
Eating
Finished Eating Trigger
Check delivered trigger
Payment Message
Leaving
Customer left Trigger
Clearing
10
Logistics RPR BOMs
Could be the same
Could be the same
Ready
Ready
Ready
Ready
Request/Receive
Requesting
Offering
Offering
RepairComplete
Receiving
Ready
Ready
Ready
Ready
The use of the logistics interaction classes
involves a detailed understanding of the state
transitions and timing between events. - RPR
FOM GRIM
11
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
12
Aggregation Approach using BOMs
13
Types of BOM Aggregations

• Pattern Aggregations
• Interface Groupings
• Non-exercise specific (class based)
• Examples
• Car(Engine / Wheels / Suspension / Braking
  System / Frame)
• Ship(Weapon System / Radar / CIC)
• Equipment Pack(Ammo / Weapon / Grenade / Water /
  First Aid Kit / MRE)
• First Aid Kit(Gauze / Wrap / Ointment / Knife /
  Aspirin / Blood Clot (kitty litter))
• Human Anatomy(Heart / Liver / Kidney / Digestion
  system, Epidermis, etc)

• Instance Aggregations
• Entity Groupings
• Exercise specific (object driven)
• Examples
• Battalion (Collection of Individual Soldiers)
• Air Squadron
• Battle group
• Weather (Storm Cells / Wind / Temperature /
  Atmospheric Pressure/ Bathymetry)
• Close Air Support(Forward Air Controller /
  Aircraft / Target / Target Locater / Designator)
• Crowds

Composite Pattern
Flyweight Pattern
14
BOM Pattern Aggregation

• Pattern Aggregations
• Interface Groupings
• Non-exercise specific (class based)
• Examples
• Car(Engine / Wheels / Suspension / Braking
  System / Frame)
• Ship(Weapon System / Radar / CIC)
• Equipment Pack(Ammo / Weapon / Grenade / Water /
  First Aid Kit / MRE)
• First Aid Kit(Gauze / Wrap / Ointment / Knife /
  Aspirin / Blood Clot (kitty litter))
• Human Anatomy(Heart / Liver / Kidney / Digestion
  system, Epidermis, etc)

Federate
Sim / System A
InterfaceBOM 1
Federate A
Federate B
- or -
InterfaceBOM 2
Federation
Mega-BOM
Federate X
Representation
Composition
InterfaceAssembly
- or -
InterfaceBOM n
Model1
Model2
Aggregation
Interface BOMs(Coupling)
Model3
Modeln
Composite Pattern
15
BOM Pattern Aggregation

• Pattern Aggregations
• Interface Groupings
• Non-exercise specific (class based)
• Examples
• Car(Engine / Wheels / Suspension / Braking
  System / Frame)
• Ship(Weapon System / Radar / CIC)
• Equipment Pack(Ammo / Weapon / Grenade / Water /
  First Aid Kit / MRE)
• First Aid Kit(Gauze / Wrap / Ointment / Knife /
  Aspirin / Blood Clot (kitty litter))
• Human Anatomy(Heart / Liver / Kidney / Digestion
  system, Epidermis, etc)

Processing Space

• Composite Pattern
• used to form a collection of objects.

Aggregate State
InterfaceBOM 1
InterfaceBOM 2
Model1
Model2
Mega-BOM
Composite Representation
Federate
Model3
Modeln
Composition
InterfaceAssembly
InterfaceBOM n
Interface BOMs(Coupling)
Composite Pattern
EBI a
EBI b
EBI x
16
BOM Pattern Aggregation

• Pattern Aggregations
• Interface Groupings
• Non-exercise specific (class based)
• Examples
• Car(Engine / Wheels / Suspension / Braking
  System / Frame)
• Ship(Weapon System / Radar / CIC)
• Equipment Pack(Ammo / Weapon / Grenade / Water /
  First Aid Kit / MRE)
• First Aid Kit(Gauze / Wrap / Ointment / Knife /
  Aspirin / Blood Clot (kitty litter))
• Human Anatomy(Heart / Liver / Kidney / Digestion
  system, Epidermis, etc)

Processing Space
De-aggregate State
InterfaceBOM 1
Model1
InterfaceBOM 2
Model2
Federate
Independent Representation
Model3
Modeln
InterfaceBOM n
Interface BOMs
Composite Pattern
17
Aggregate to megaBOM
Model Identification BOM A
Name
Description
Type
Version
Mod Date
Security Class
Rel Restriction
Purpose
App Domain
18
BOM Flyweight Aggregation

• Flyweight Pattern
• used to help manage large numbers of class
  instances (i.e. entities) within a simulation.
• Identify common attributes of the classes
  representing the entities within a simulation
• Define a common class
• any differences in attributes among the various
  classes can be maintained as extrinsic data
  passed in as arguments (using mechanisms such as
  HLA Interactions).

• Instance Aggregations
• Entity Groupings
• Exercise specific (object driven)
• Examples
• Battalion (Collection of Individual Soldiers)
• Air Squadron
• Battle group
• Weather (Storm Cells / Wind / Temperature /
  Atmospheric Pressure/ Bathymetry)
• Close Air Support(Forward Air Controller /
  Aircraft / Target / Target Locater / Designator)
• Crowds

19
BOM Aggregation Framework (BAF)

• BAF represented as a defined set of web-services
• available both at design-time among model
  developers and
• at run-time with the constructive simulations
  that are at play over a network.
• Web Service Rationale
• web-services provide the logical automation
  mechanism for supporting
• BOM to Mega-BOM aggregation (and de-aggregation),
  
• load balancing,
• behavior preservation, and
• delivery of model-to-model transformations for
  supporting adaptability.
• allows a myriad of federates developed for
  different platforms and languages to access and
  utilize the service independent of the platform
  or language the BAF is hosted or written under.

aggregate()
BAF
deaggregate()
otherservices

• Actual implementation of BAF set of services
  called
• BASS BOM Aggregation Support Service
• Execution Monitoring support
• Auto-triggering
• Multi-Resolution Model dialing
• Transfer Control
• Connection to Resource Libraries
• Model-to-Model Transformations

20
BAF -Principal Web Service Methods
A3-206
21
BAF Web Service Prototype
22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
Determining Whenand How to Aggregate

• Triggers / Criteria
• Proximity to a specific obstacle, entity or
  feature in the synthetic battlespace
• A change in the level of interest or significance
  regarding the specific domain a model supports
  or
• An increase (or decrease) in the physical entity
  load by the system and/or over the entire
  federation.

27
Findings and Results

• application of BOMs provides a solid approach to
• reflect detailed information that is relevant,
• while preserving the simulation modeling validity
  at the federate level.
• BOMs can be used for supporting two useful types
  of aggregation
• Pattern Aggregation
• Instance Aggregation
• ECAP BOMs can be applied and scaled to the
  resolution needed. (see paper 052)

28
Recommendations

• Need more community BOMs
• Encourage potential users to consider this
  approach for supporting aggregation
• Provide comment on BAF specification
• Use BASS or roll your own BAF implementation
• Explore tool integration
• Provide feedback to community
• Let us come back to SMS in the future to report
  on status

29
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

30
Multi-resolution Modeling Approach using BOMs

• 04S-SIW-052

31
Addendum Slides
32
Related Papers

• Adelantado, Siron, "Multiresolution Modeling and
  Simulation of an Air-Ground Combat Application,
  01S-SIW-012
• Beeker, Battlespace Federation An HLA
  Experiment in Disaggregation, 00S-SIW-083
• Briddle, A Proposed Scheme for Implementing
  Aggregation and Disaggregation in HLA,
  00F-SIW-074
• Franceschini, Gerber, Schriker, Adkins, Use of
  the Eagle/OneSAF Testbed to Support Large Scale
  Exercises, 11TH-CGF-070
• Generazio, Young, The Aggregation/Disaggregation
  Problem In Vertical Integration of Dissimilar
  Combat Simulations, 9 February 1995, 12-95-050
• Gustavson, Lutz, Morse, Reichenthal, Applying
  Design Patterns for Enabling Simulation
  Interoperability, 04S-SIW-111
• Davis P., Aggregation, Disaggregation, and the
  31 Rule in Ground Combat, RAND,
  MR-638-AF/A/OSD, 1995
• Reichenthal, Gustavson, de la Cruz, Case Study
  Prototyping a Mega-BOM with SRML for
  Next-Generation Combat Support, 03S-SIW-143
• Seiger, Holm, Bergsten, Aggregation/Disaggregatio
  n Modeling in HLA-based Multi Resolution
  Simulations, 00F-SIW-037

33
States of Aggregation / Deaggregation
A3-206 - Research
Franceschini, Gerber, Schriker, Adkins, Use of
the Eagle/OneSAF Testbed to Support Large Scale
Exercises, 11TH-CGF-070
34
Requirements forSupporting Aggregation

• Reduce Amount of Traffic (load balancing)
• Separate Representation from Model
• Couple Representations (composite pattern)
• Preserve Simulation Validity
• Support Different States of Aggregation
• Pattern Aggregation
• Instance Aggregation
• Accessibility To Disparate Federates
• Web Service

• Allows clean separation between the interface
  (and coupling of interfaces) and the actual
  models used to support the behavior identified in
  an interface,
• Aggregation can occur creating necessary
  groupings without the need to scale the behavior
  models of those entities that have been
  assimilated into an aggregate.
• At the federate level, those behavior models can
  continue to be applied generating full fidelity
  within the federate responsible for the
  associated entity or entities.
• Only the message information being shared among
  federates within a federation has been altered
• an aggregate message reflects information
  regarding multiple entities (or sub-entities if
  it is a pattern aggregation).

35
ProcessDefine - Discover - Design - Develop
Activities
Pattern
Step 1
Objective / Desired Capability
Step 2
Step n
BOM-basedFOM
megaBOM
FederationAgreement
EBI a
EBI b
EBI x
ECAP BOM a
ECAPBOM b
Resource Lib
FederateCapability
ECAPBOM x
36
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