BOM Template Specification Images

1
BOM Template SpecificationImages

• SISO-STD-003.1-DRAFT-V0.13

2
Compositions identified as BOM Assemblies A,B,C
and X
3
(No Transcript)
4
BOM Elements
structured, encoded data that describe
characteristics of information-bearing entities
to aid in the identification, discovery,
assessment, and management of the described
entities
static descriptions of items resident in the real
world described in terms of conceptual entities
and conceptual events. information on how such
items relate or interact with each other in the
real world in terms of patterns of interplay and
state machines.
maps the relationship between the elements in the
Conceptual Model space and the interface
description elements described in the HLA Object
Model Space
required simulated capabilities defined in the
context of an interface description. represents
the information necessary for execution and
exchange. described in terms of structural
and/or object-based classes defining capabilities
of a simulation application. use of the HLA
OMT provides a familiar construct for the
simulation software designer, but does not
restrict the use of a BOM to HLA specific
implementations.
BOM template allows BOMs to be captured in a
reusable way
5
BOM Elements

• a component-based standard describing reusable
  piece parts of a simulation or simulation space.
• BOMs can be used to document one or more of the
  following piece part elements
• Conceptual Model Definition
• Patterns of interplay
• State machines
• Entities
• Events
• Object Model Definition (Interface)
• Object classes / attributes
• Interaction classes / parameters
• Mapping between Conceptual Model and Object Model
• Used as a building block in the development and
  extension of a simulation and/or a federation of
  simulations.
• Provides developers and users a modular approach
• for defining and adding new capabilities to a
  federate or federation,
• for quickly composing object models such as HLA
  FOMs and SOMs through BOM Assemblies.

6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
Example Conceptual Model

• Pattern Description
• State Machine
• Entity Types
• Event Types

13
An action can be potentially supported completely
by another pattern of interplay
old
An action can be associated to an event
14
old
15
BOM Element Relationship (Conceptual Model View)
old
Event Type Description
Entity Type Description
Pattern Description
State Machine
16
BOM Top-Level Schema View
17
BOM patternType
18
BOM eventsType
19
BOM stateMachine Type
20
BOMmodelDefinition segment
21
BOM notes Type
22
Guide for Base Object Model (BOM) Use and
Implementation

• SISO-STD-003.0-DRAFT-V0.13

23
Figure 6-1 - Examples of Component Reuse
24

Federate View
Implementation View (within each Federate)
Federate Code / Libraries
Conceptual / Interface View
BOM a - State Machine
BOM b - State Machine
BOM c State Machine
BOM d - State Machine
BOM x - State Machine
SOM
ReuseLibrary
Federation View
Conceptual / Interface View
HLAObjectModels(FOMs)
BOM 1 - Pattern
BOM 2 - Pattern
BOM 3 - Pattern
BOM n - Pattern
Classa
Classb
Classx
Classa
Classc
Classx
Classb
Classc
Classx
Classa
Classb
Classd
MoreOMT
BOMs
BOM Assembly (Composite)
MetadataRich
FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve)
Communication View
RTI
25
(No Transcript)
26

Federate View
Conceptual Model View
BOM a - State Machine
BOM b - State Machine
BOM c State Machine
BOM d - State Machine
BOM x - State Machine
ReuseLibrary
Federation View
Conceptual Model View
HLAObjectModels(FOMs)
BOM 1 - Pattern
BOM 2 - Pattern
BOM 3 - Pattern
BOM n - Pattern
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
BOMs
BOM Assembly (Composite)
MetadataRich
27

Federate View
Conceptual Model View
BOM a - State Machine
BOM b - State Machine
BOM c State Machine
BOM d - State Machine
BOM x - State Machine
Object Model View (class structures defined
within multiple BOMs or a single SOM)
Object Class y
Object Class y
Object Class z
Interaction Class Q
Interaction Class R

• Attribute 4
• Attirbute 5
• Attribute 6

• Attribute 1
• Attirbute 2
• Attribute 3

• Attribute 7
• Attirbute 8
• Attribute 9

• Attribute 1
• Attirbute 2
• Attribute 3

• Attribute 4
• Attirbute 5
• Attribute 6

ReuseLibrary
Federation View
Conceptual Model View
HLAObjectModels(FOMs)
BOM 1 - Pattern
BOM 2 - Pattern
BOM 3 - Pattern
BOM n - Pattern
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
BOMs
BOM Assembly (Composite)
MetadataRich
Object Model View (class structures defined
within multiple BOMs or a single SOM)
Object Class y
Object Class y
Object Class z
Interaction Class Q
Interaction Class R

• Attribute 4
• Attirbute 5
• Attribute 6

• Attribute 1
• Attirbute 2
• Attribute 3

• Attribute 7
• Attirbute 8
• Attribute 9

• Attribute 1
• Attirbute 2
• Attribute 3

• Attribute 4
• Attirbute 5
• Attribute 6

28

Federate View
Conceptual Model View
State Machine a
State Machine b
State Machine c
State Machine d
State Machine x
Entity a1
Entity a2
Entity b1
Entity b2
Entity c1
Entity c2
Entity d
Entity x1
Entityx2
Object Model View (class structures supported
with each Federate to represent conceptual
elements)
Object Class y
Object Class y
Object Class z
Interaction Class Q
Interaction Class R

• Attribute 4
• Attirbute 5
• Attribute 6

• Attribute 1
• Attirbute 2
• Attribute 3

• Attribute 7
• Attirbute 8
• Attribute 9

• Attribute 1
• Attirbute 2
• Attribute 3

• Attribute 4
• Attirbute 5
• Attribute 6

ReuseLibrary
HLAObjectModels(FOMs)
Federation View
Conceptual Model View
Pattern of Interplay 1
Pattern of Interplay 2
Pattern of Interplay 3
Pattern of Interplay 4
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
BOMs
Event G
Event H
Event E
Event F
Event C
Event D
Event A
Event B
MetadataRich
Object Model View (class structures describing
context for information exchange among Federation)
Object Class y
Object Class y
Object Class z
Interaction Class Q
Interaction Class R

• Attribute 4
• Attirbute 5
• Attribute 6

• Attribute 1
• Attirbute 2
• Attribute 3

• Attribute 7
• Attirbute 8
• Attribute 9

• Attribute 1
• Attirbute 2
• Attribute 3

• Attribute 4
• Attirbute 5
• Attribute 6

29
Object Model View (class structures within a
single SOM or multiple BOMs)
30

Federate View
Implementation View (within each Federate)
Federate Code / Libraries
Object Model View
BOM a Object Class / Attribute
BOM a Object Class / Attribute
BOM a Object Class / Attribute
BOM a Object Class / Attribute
Conceptual Model View
BOM a - State Machine
BOM b - State Machine
BOM c State Machine
BOM d - State Machine
BOM x - State Machine
SOM
ReuseLibrary
Federation View
Conceptual Model View
HLAObjectModels(FOMs)
BOM 1 - Pattern
BOM 2 - Pattern
BOM 3 - Pattern
BOM n - Pattern
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
MoreHLA OMTelements
BOMs
BOM Assembly (Composite)
MetadataRich
FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve)
31
Figure 6-4 Application of BOMs for Providing
Various Federation Level Support
Federate(SOM)
Sim / System A
BOM 1
BOM 2
Federate A
Federate B
- or -
Federation(FOM)
BOM 3
BOMAssembly
Representation
Composition
Federate X
CompositeInterface
- or -
BOM n
Model1
Model2
Aggregation
BOMs(Coupling)
Model3
Modeln
These BOMs represent the relationship of
activities among conceptual entities (FOM level),
32
Federate(SOM)
Sim / System A
BOM 1
WeaponsEffect
BOM 2
Federate A
Theater WarfareRepresentation
Detect / Jam
Federate B
- or -
Federation(FOM)
BOM 3
BOMAssembly
RepairResupply
Representation
Composition
Federate X
CompositeInterface
- or -
BOM n
Model1
Model2
RadioComms
Aggregation
BOMs(Coupling)
Model3
Modeln
These BOMs represent the relationship of
activities among conceptual entities (FOM level),
33
Figure 6-5 - Application of BOMs for Providing
Federate Level Support
BOM 1
BOM 1
CODE
BOM 2State Machines, Entities, Events ----Object
Classes,Attributes,Interaction
Classes,Parameters
Sim / System
FunctionalCapabilityRun-timeExecution
FunctionalExposureState MachineEntity
TypesHLA Object Classes
BCI
BCI
BCI
BCI
BOM nState Machines, Entities, Events ----Object
Classes,Attributes,Interaction
Classes,Parameters
Federate ImplementationView
BCI BOM Component Implementation
Federate - Conceptual / interface view
34
BOM Element Relationship (Conceptual Model View)
Pattern Description
State Machine
An action can be potentially supported completely
by another pattern of interplay
n
An action can be associated to an event
State Machine
Entity
Pattern
n
States
n
1
1
Action
Event
BOM
n
ExitCondition
PatternAction
NextState
n
n
Sender
Receiver
Entity Type Description
Event Type Description
Event
Entity
n
Role
Characteristics
Source
n
Target
Characteristics
Trigger
Message Content
35
Figure 7-1 FEDEP Seven-Step Process
36
Figure 8-1 - BOM Elements for Representing a
Pattern of Interplay
BOM Element -gt Model Identification Conceptual Model Model Mapping Object Model Definition
Individual BOM(Conceptual Model Def)behavior representation(pattern, state machine, events) Required Required Optional Optional
Individual BOM(Object Model Definition) object repesentation (object classes, interaction classes) Required Optional Optional Required
BOM Assembly(representing composite of other BOMs) Required Required(Pattern of Interplay) Optional Optional
SOM
BOM Assembly
FOM
Xformation
n
BOMs
Aggregate Model
37
Figure 8-3 BOM Model Identification Table
38
Model Identification(Key metadata)
Required
Optional
Supportsmultiple occurrences

Figure 8-3 BOM Model Identification Table
39
Figure 8-4 - BOM Template Pattern Description
40
Figure 8-5 - BOM Template Pattern Step
Relationship
41
Messages
Directed events

• The conceptual entity identified as the sender of
  the action within the pattern of interplay
  directs (sends) a message event to the conceptual
  entity(s) identified as the receiver.
• In the HLA, the message occurs between federates
  using either an object class attribute update or
  a sent interaction.

• The conceptual entity(s) identified as the
  receiver then react to the information contained
  in the directed message.
• In the HLA, the federate responsible for modeling
  the receiving conceptual entity(s) will respond
  to the specific sent interaction or object
  attribute update.

Figure 8-6 Event - Message
Source Björn Löfstrand Pitch AB
42
Triggers
Undirected Events
Publish Event
Subscribe Event

• The conceptual entity identified as the sender of
  the action within the pattern of interplay
  publishes information as an event for other
  conceptual entities to react to, but does not
  know the target conceptual entities.
• In the HLA, the event is generated using either
  an object class attribute update or a sent
  interaction.

• A response (reaction) may occur by one or more
  subscribing conceptual entities that have
  interest in such observable events.
• In the HLA, the occurrence of the undirected
  event is of interest to a federate, which might
  react or respond to such an action.

Figure 8-7 Event - Trigger
Source Björn Löfstrand Pitch AB
43
Figure 8-2 - FEDEP Steps 1 2
44
Figure 9-1 - FEDEP Step 1
Figure 9-2 - FEDEP Step 2
45
Figure 9-6 - FEDEP Step 4
Figure 9-5 - FEDEP Step 3
46
Figure 9-6 - FEDEP Step 4
Figure 9-5 - FEDEP Step 3
47
Figure 9-10 - FEDEP Step 5
48
Figure 9-4 - Conceptual Model Driven Development
49

• Identify purpose / objective / intent
• Focus on capturing conceptual model
• Identify pattern of simulation interplay
• E.g. Model capabilities of a JCAD Sensor

Conceptual Analysis
BOM DevelopmentLibrary

• Find candidate BOMs
• Use purpose, keywords, and conceptual model as
  searching criteria
• Match metadata with available BOMs in repository

Search library
results

• Create BOM piece parts
• Define patterns of interplay, state machines,
  entities, events such as triggers messages
  (Conceptual Model)
• Define class structures (Object Model Definition)
• Define model mappings
• Use BOM DIF (based on an extension of HLA OMT)

Design
BOM candidatefound
FEDEPSteps2 4
BOM not found
Conceptual Model
Object Model
Insert BOM into library
BOM found

• Integrate BOM within federate
• Use BOM Object Model Definition piece parts
• Ensure federate supports conceptual behavior of
  BOM
• Develop or use existing BOM Component
  Implementation (BCI) if needed

Development

• Create BOM Assembly
• Composition of BOMs that support functional
  inputs / anticipated outputs
• Used to represent system interface (much like
  SOM) or a federation (much like FOM)

Insert BOMs / BOM Assembly into library
Fetch model
FOM/SOM/BOMReuse Library
Generate FOM / SOM from BOM Assembly
results
Insert FOM / SOM into library
Federation Integration
50
FEDEPSteps 2 4
old
51
FEDEPStep 1

• Identify purpose / objective / intent
• Focus on capturing Conceptual Model
• Identify pattern of simulation interplay
• E.g. Model capabilities of a JCAD Sensor

ConceptualModel
FEDEPStep 2
FEDEPStep 3

• Find candidate BOM
• Use Conceptual Model metadata input for searching
• Match metadata with available BOMs in OMRC
  (future capability)

BOM ReuseLibrary
Search library
results

• Create BOM Interface
• Identify functional inputs / anticipated outputs
• Identify potential Events such as Triggers and
  Messages
• Use BOM DIF (based on an extension of HLA OMT)
• Note represents interface not an
  implementation

BOM not found
BOM CandidateFound
old
Insert BOM into library
BOM found

• Integrate BOM within federate
• XML Parsable BOM Interface
• BOM Component Implementation (BCI) if needed

BOM Assembly
FEDEPStep 4

• Create BOM Assembly
• Composition of BOMs based on their interface
• Used to represent system interface (much like
  SOM) or a federation (much like FOM)

Insert BOM Assembly into library
Generate FOM / SOM from BOM Assembly
52

• Identify purpose / objective / intent
• Focus on capturing Conceptual Model
• Identify pattern of simulation interplay
• E.g. Model capabilities of a JCAD Sensor

FEDEPStep 1
ConceptualModel

• Find candidate BOM
• Use Conceptual Model metadata input for searching
• Match metadata with available BOMs in OMRC
  (future capability)

BOM ReuseLibrary
Search library
results

• Create BOM
• Identify functional inputs / anticipated outputs
• Identify potential Events such as Triggers and
  Messages
• Use BOM DIF (based on an extension of HLA OMT)
• Note represents interface not an
  implementation

BOM not found
FEDEPStep 2 Step 5
BOM CandidateFound
Insert BOM into library
BOM found
old

• Integrate BOM within federate
• XML Parsable BOM Interface
• BOM Component Implementation (BCI) if needed

BOM Assembly

• Create BOM Assembly
• Composition of BOMs based on their interface
• Used to represent system interface (much like
  SOM) or a federation (much like FOM)

Insert BOM Assembly into library
Generate FOM / SOM from BOM Assembly
53
BOM History
Protocol Oriented
Object-Based Oriented
Component/Service Oriented
2004
1998
2002
2000
2003
2001
1996
2010
1999
2006

1990
HLA1516 Evolve
HLA1516
DIS
HLA
FEDEP1516
Rapidly composableand scalable MS
C M S E
FOMpiece parts (FEDEP, OMT)
BOM Methodology Strawman
ReferenceFOM Study Group
BOM Study Group
BOMPDG
RPR FOM
SRML
Schemas
DTD

• Tools
• Components
• Libraries

XSLT
SOAP
WSDL
54
Figure 9-7 - Base Object Model in FEDEP
55
Figure 9-8 Skeleton Design Process
56
Figure 9-9 BOM Assembly Pattern Action to BOM
Relationship
57
ReuseLibrary
Composition A
Composition B
ReuseLibraries
BOM 1
HLAObjectModels(FOMs)
BOM 2
BOM 1
BOM 2
BOM 4
BOM 3
BOM 3
BOMs
BOM 17
BOM 11
BOM 4
. . .
BOM 23
BOM 19
MetadataRich
BOM N
Figure 10-1- Leveraging a BOM Resource Reuse
Library
58
Miscellaneous Images
59
BOM Palette
-
x
Simulation Components
User Requirements

• Simulation Systems
• federation interactivities(i.e., foms)
• federate capabilities

Compositions identified as BOM Assemblies A,B,C
and X
Figure 6-2 - Creating BOM Compositions
60
State Machine
State Machine
n
States
n
NextState
PatternAction
ExitCondition
61
BOM Element Validity Matrix
BOM Element -gt Model Identification ModelDefinition BehaviorDescription Pattern BehaviorDescription State Machine BehaviorDescription - Events
IndividualBOM (representing pattern, state machine, and/or object/interaction class) Required Required Optional Optional Optional
BOM Assembly(representing composite of other BOMs) Required Optional Required Optional Optional
62
Application of BOM Elements
BOM Element Federation Level Support Federate Level Support
Model Identification Required Use Required Use
Behavior Description / Pattern Intended Use(Required for BOM Assembly) Optional Use
Behavior Description / Events Intended Use Optional Use
Behavior Description / State Machine Optional Use Intended Use
Model Definition(object class/ interaction class / attributes / parameters / datatypes) Intended Use(Not Require for BOM Assembly) Intended Use
63
RPR BOMs
64
What BOMs Provide? Model Composability
BOMs are designed for enabling composability,
providing extensibility, facilitating
interoperability, improving manageability, and
encouraging understandibility.
65
BOM Illustration
Detect /Jamming Activity
Jammer(Originator)
Radar
Threat / Target
Emits
Reflects
Detect
Threat Detected in Range (Msg)
Jam
Federation Activities
Federate Capability
66
BOM Illustration 2
Weapons Effect
Derived from RPR FOM
Federation Activities
Federate Capability
67
What BOMs Provide? Model Composability
Interface (Profile)
WeaponsEffect
BOM 1
Federate A
Operation FreedomTraining FOM
Homeland DefenseTraining FOM
Theater WarfareRepresentation
Collision
Detect / Jam
CAPSupport
Federate B
BOM 2
BOMAssembly
Representation
Composition
Federate X
RadioComms
Logistics
BOM n
CompositeInterface
FederationforJoint Training
Conceptual Model View
Object Model View
BOMs
68
(No Transcript)
69
What is Composability?
The ability to rapidly select and assemble
components to construct meaningful simulation
systems to satisfy specific user requirements.
Composability includes the framework, body of
knowledge, tools, techniques, and standards
necessary to enable effective integration,
interoperability, and reuse. - (DoD MS
Master Plan)
MS COMPONENTS - Reusable building blocks which
have a known set of inputs and provide expected
output behavior, but the implementation details
may be hidden. Such components are useful for
constructing simulations and/or providing
functionality for simulation systems. COI MS
Metadata Focus Group