Base Object Model BOM Architecture PDG Effort XMSF Fit

1
Base Object Model (BOM)Architecture PDG Effort
XMSF Fit

• Paul Gustavson
• SimVentions
• pgustavson_at_simventions.com
• 540.372.7727

2
XMSF Focusing on the integration dilemma?

• Background
• Architecture
• PDG
• XMSF

• Dealing with the reality of mixed IT environments
  
• Preserving existing investments
• Integration strategies
• The impact on quality performance

3
XMSF Focusing on the integration dilemma!

• Background
• Architecture
• PDG
• XMSF

• Dealing with the reality of mixed IT environments
  
• Preserving existing investments
• Integration strategies
• The impact on quality performance

4
What Are BOMs?

• Background
• Architecture
• PDG
• XMSF

• A reusable package of information representing an
  pattern of simulation interplay
• Used as a building block in the development and
  extension of a simulation and/or interoperable
  environments.

• Patterns Components for composable simulation
  interoperability environments
• Enables syntactic / semantic interoperability
• Promotes reusability
• Open community development effort
• Grass roots movement
• Started in 1998 within SISO
• Focus towards a standard
• Utilizes XML and XML-based standards
• To Define Interface
• To Capture Meta-data
• To promote adaptability

• HLA compatibility
• Can be leveraged by web services
• Collaborative Development
• BOM Repositories
• Meta-data matching
• Execution
• Dynamic Distribution
• Persistent Data
• Supports other initiatives
• Virtual hands-on learning
• C4ISR MS interoperability
• XMSF composable, reusable model components
• Leverage DoDAF / Conceptual model (meta-data)
• Prototyping

5
How Did We Get Here?

• Background
• Architecture
• PDG
• XMSF

2004
1998
2002
2000
2003
2001
1996
2010
1999
SISO-STD-003.1-2003 BOM Spec Vol 1 Interface BOM
Rapidly composableand scalable MS
ReferenceFOM Study Group
BOM Study Group
FEDEP PDG
CMSE
RPR FOM
BOM PN
BOM Methodology Strawman
BOMPDG / DG
SRML
FOMpiece parts (FEDEP, OMT)
HLA1516
6
Existing HLA Architecture

• Background
• Architecture
• PDG
• XMSF

Federation Layer
Federate A
Federate B
Federate C
Federate D
Federate E
Federate Z
Interface Layer
FOM
HLAObjectModels
FOM based,meta-datachallenged
Communication Layer
RTI
Optional
Required
7
BOM Architecture

• Background
• Architecture
• PDG
• XMSF

Federation Layer
Federate A
Federate B
Federate C
Federate D
Federate E
Federate Z
Encapsulation Layer
HLAObjectModels
Federate Code
ECAP BOM a
ECAP BOM b
ECAP BOM c
ECAP BOM d
ECAP BOM x
Interface Layer
IF BOMs
IF BOM 1
IF BOM 2
IF BOM 3
IF BOM n
Classa
Classb
Classx
Classa
Classc
Classx
Classb
Classc
Classx
Classa
Classb
Classd
ECAP BOMs
Mega BOM
Meta-dataRich
Communication Layer
RTI
Optional
Required
8
BOM Architecture

• Background
• Architecture
• PDG
• XMSF

Federation Layer
Federate A
Federate B
Federate C
Federate D
Federate E
Federate Z
Encapsulation Layer
Federate Code
ECAP BOM a
ECAP BOM b
ECAP BOM c
ECAP BOM d
ECAP BOM x
Interface Layer
IF BOM 1
IF BOM 2
IF BOM 3
IF BOM n
Classa
Classb
Classx
Classa
Classc
Classx
Classb
Classc
Classx
Classa
Classb
Classd
Mega BOM
Meta-dataRich
Composability The capability to select and
assemble components in various combinations into
complete, validated simulation environments to
satisfy specific user requirements across a
variety of application domains, levels of
resolution, and time scales Dr. Mikel Petty
Communication Layer
RTI
Optional
Required
9
BOM Architecture

• Background
• Architecture
• PDG
• XMSF

Federation Layer
Federate A
Federate B
Federate C
Federate D
Federate E
Federate Z
Encapsulation Layer
Federate Code
ECAP BOM a
ECAP BOM b
ECAP BOM c
ECAP BOM d
ECAP BOM x
ComponentRepository
ECAP BOM X
Interface Layer
ECAP BOM d
IF BOM 1
IF BOM 2
IF BOM 3
IF BOM n
ECAP BOM c
Classa
Classb
Classx
Classa
Classc
Classx
Classb
Classc
Classx
Classa
Classb
Classd
ECAP BOM c
ECAP BOM a
Mega BOM
Meta-dataRich
Composability The capability to select and
assemble components in various combinations into
complete, validated simulation environments to
satisfy specific user requirements across a
variety of application domains, levels of
resolution, and time scales Dr. Mikel Petty
Communication Layer
RTI
Optional
Required
10
BOM Architecture

• Background
• Architecture
• PDG
• XMSF

Federation Layer
Federate A
Federate B
Federate C
Federate D
Federate E
Federate Z
Encapsulation Layer
HLAObjectModels
Federate Code
ECAP BOM a
ECAP BOM b
ECAP BOM c
ECAP BOM d
ECAP BOM x
Interface Layer
IF BOMs
IF BOM 1
IF BOM 2
IF BOM 3
IF BOM n
Classa
Classb
Classx
Classa
Classc
Classx
Classb
Classc
Classx
Classa
Classb
Classd
ECAP BOMs
Mega BOM
Meta-dataRich
Communication Layer
RTI
Optional
Required
11
Application ofInterface BOMs

• Background
• Architecture
• PDG
• XMSF

Sim / System A
Federate
InterfaceBOM 1
Federate A
Federate B
- or -
InterfaceBOM 2
Federation
Mega-BOM
Representation
Composition
Federate X
InterfaceAssembly
- or -
InterfaceBOM n
Model1
Model2
Aggregation
Interface BOMs(Coupling)
Model3
Modeln
12
Pattern IF BOM Mapping
IF BOM / Mega-BOM Elements
Pattern Description
Model Definition
Model Identification
Object Models(1516.2)
Name
Description
Activity
Type
Use Limitation
Events
Version
Use History
Mod Date
Keywords
Security Class
POCs
Rel Restriction
References
Purpose
Others
App Domain
Glyph
Not needed for Mega-BOM
13

• Background
• Architecture
• PDG
• XMSF

ECAP BOM Elements
Behavior Model
other
Model Description
Visual Model
VV Markup
Digital Rights
Level of Fidelity

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

Required
Optional
14
FEDEP

• Background
• Architecture
• PDG
• XMSF

15

• Identify purpose / objective / intent
• Focus on capturing Conceptual Model
• Recommend Use Case identifying aspect of
  simulation interplay
• E.g. Model capabilities of a JCAD Sensor

FEDEPStep 1
ConceptualModel
FEDEPStep 2
16
Development Process

• Background
• Architecture
• PDG
• XMSF

Activities
Pattern
Step 1
Objective / Desired Capability
Step 2
IF BOM
Step n
Classa
Classb
Classx
17
Creating BOM Components

• Background
• Architecture
• PDG
• XMSF

• Identify Patterns
• Represent them as IF BOMs
• Identify Classes within IF BOMs
• Codify Classes as Component Models ECAP BOMs
• PIMs (using SRML)
• PSMs (DLL, DSO, .NET assembly, ActiveX)
• Assemble into Packages (maps to 2)
• for deployment
• Potential elements of an Encapsulated BOM
• Behavioral (SRML)
• Security / Licensing
• Verification and Validation (VV)
• Level of Fidelity
• Visual Representation
• Other Meta-Data

IF BOM 1
Classa
Classb
Classx
Pattern
Manifestation
EPB 1
ECAPBOM a
ECAPBOM b
ECAPBOM x
Component Package
Implementations representing a pattern of
simulation interplay can be either contained
within an Encapsulated Package BOM (consisting of
components) or external within the simulation.
18
Race Pattern Example
19
Race Example
IF BOM Classes
ECAP BOM Classes
Relationshipof Actors
Models
20
Soap Box Derby Mega-BOM
Environment ECAP BOM
Car ECAP BOM
Track ECAP BOM
Race Manager ECAP BOM
Race IF BOM
21

• Background
• Architecture
• PDG
• XMSF

22
SISO Relationship

• Background
• Architecture
• PDG
• XMSF

SISO
C4I X3D SOAP HTTP BEEP
XMSFStudy Group
DRM Study Group(proposed)
SAPD Forum
SMS Forum
DSPTForum
BOMPDG
VVAForum
ConceptualModel
LogisticsForum
Link16PDG
23

• Background
• Architecture
• PDG
• XMSF

24
BOM Alignment with XMSF

• Background
• Architecture
• PDG
• XMSF

Extensible Modeling Simulation Framework (XMSF)

• Pattern Profile Enabler
• IF BOM / Mega-BOM support XMSF Profile definition
  objectives
• Provide unambiguous specification of the
  functionality of components, and interfaces among
  components of the framework
• Provide the necessary metadata to facilitate
  composability and reuse of components across
  multiple MS application domains
• Component Profile Enabler
• ECAP BOM applied to support XMSF push for web
  enabled simulation
• Provides behavior modeling for a pattern within a
  distributable payload

• Web-based Technologies
• Web services

• Standards
• Process
• Practices

• Web-based Technologies
• Web services

• Web-based Technologies
• Web services

MS tailored
Profiles
New Generation Internet-distributed applications
Next Generation Internet-distributed applications
Next Generation Internet-distributed applications
emerge
develop
interoperate
25
Issues and Shortcomings