1 Real-Time Platform Reference (RPR) Base Object Model (BOM) Composability Standard for Enabling...

1

Real-Time Platform Reference (RPR)Base Object Model (BOM)

Composability Standard for Enabling Interoperability

Tram Chase

[email protected]

Conceptual Federate

Federation

A

B

C

X

2

Fed

erat

e(S

OM

)

BOMAssembly

BOM 1

BOM 3

BOM n

CompositeInterface

Composition

Sim / System A

Representation Fed

erat

ion

(FO

M)Federate B

Federate X

Federate A

Agg

rega

tion

Model#1

Model#2

Model#3

Model#n

- or -

- or -Theate

r Warfa

re

Representa

tion

BOM 2

BOMs are designed for enabling model composability.

BOM Palette - x

Choose what fits conceptual model?

A

B

C

X

State MachinesPattern of Interplay

Events

User Requirements

Simulation Components

Simulation Systems• foms • federates

BOM – A piece part of a conceptual model, simulation object model, or federation object model, which can be used as a building block in the development and/or extension of a simulation or federation.

Weapons

Effect

Radio

Comm

s

Repair

Resupply

Detect /

Jam

Definition Concept Standards

Illustration

Key Concept - Using Base Object Models (BOMs) as Building Blocks

3

RPR BOM Initiative• To provide a set of applicable BOMs to community• Leverage RPR FOM 2.0 (& GRIM)

– Decompose into BOMs– Add Additional Metadata (including States from 1278)

• Encourage participation/input from – RPR FOM PDG– Other community members

• Identify and report on benefits (i.e., “ility” support)– Composability– Extensibility– Exchangeability– Manageability– Understandability

• Framework for supporting RPR V3 objective?– RPR BOM Assembly

RPR BOMS

Behavior Representations• Weapon Effects• Repair• Resupply• Collision• Transfer Control• Simulation Management• Radio Communications• Entity/Object Management• Minefield• Synthetic Environment

Object Representations• Entity Object Types• Env Object Types• Minefield Object Types• Signal Object Types

State MachinesPattern of Interplay

Events

Related Papers • 05S-SIW-088

“RPR-BOM Initiative: Providing a Set of Applicable BOMs to the M&S Community”

• 06S-SIW-115“From FOMs to BOMs and Back Again”

Release Dates • April 05

RPR BOM Set 1.0 released based on v0.10 draft spec

• Sept 05RPR BOM Set 1.0 released based on V0.12 draft spec

• July 06RPR BOM Set Version 1.0 (FINAL) released

4

Hierarchical View of the RPR BOMs…RPR FOM 2.0

Repair

Resupply

Entity Creation

Entity Reconst’n

Entity Removal

Action Request

Post Comment

Post Event

Behavior Rep

Object Rep EntityObjects

EnvObjects

MinefieldObjects

SignalObjects

Includes Model Mapping

Behavior Representations• Weapon Effects

• Repair

• Resupply

• Collision

• Transfer Control

• Simulation Management

• Radio Communications

• Entity/Object Management

• Minefield

• Synthetic Environment


• Repair

• Resupply

• Collision





• Minefield




Weapons Effect

Collision

Entity/Object Management

Minefield

Synthetic Env

SIMAN

Logistics

RadioComms

Transfer Control

5

RPR BOM Illustration #1

Derived from RPR FOM

State Machines

Pattern of Interplay

pattern actions

Weapons Effect

states

Federation Activities Federate Capability

6

RPR BOM Illustration #2

Could be the same Could be the same

REPAIR RESUPPLY

Ready

Requesting

Receiving

Ready

Ready

Offering

Ready

1

2

3

1

2

3

Ready

Request/Receive

Ready

Ready

RepairComplete

Offering

Ready

“The use of [the logistics] interaction classes involves a detailed understanding of the state transitions and timing between events.” - RPR FOM GRIM

Conceptual Entities• Requester / Consumer• Repairer• Supplier

Logistics Activities

• RepairComplete Interaction Class• RepairResponse Interaction Class• ServiceRequest Interaction Class

• ResupplyCancel Interaction Class• ResupplyOffer Interaction Class• ResupplyReceived Interaction Class• ServiceRequest Interaction Class

7

Model Identification (Metadata)

Notes

Lexicon (definitions)

Object Model Definition

HLA Object Classes

HLA Object Class Attributes

HLA Object Classes

HLA Interaction Classes

HLA Interaction Class Parameters


HLA Data Types

Conceptual Model

Pattern Of Interplay

State Machine

Entity Type

Event Type

Model Mapping

Entity Type Mapping

Event Type Mapping

The BOM Elements? An Inside Look

Not all these piecesare required for a BOM…

Essential metadata needed so thatthe BOM can be described, discovered and properly reused

Conceptual entitiesand the events whichoccur among thoseentities as well as thestates attainable bythose entities.

Mapping of conceptual entities and events to object model object and interaction classes.

Notes and definitionssupporting any of theabove mentionedelements

Object classes,interaction classes,and datatypes used to perform the behavior describedin the conceptualmodel.

An XML based standard for capturing

model metadata,

aspects of the conceptual model,

the class structures of an object model which are to be used by a system (and a federation) for representing the conceptual model aspects,

and the mapping that exists between that conceptual model and object model.

BOM template allows BOMs to be captured in a reusable way

8

Comparing FOMs to BOMsModel Identification (Metadata)

Notes


HLA Object Classes


HLA Object Classes




HLA Data Types

HLA Dimensions

HLA Time

HLA Tags

HLA Synchronizations

HLA Transportations

HLA Switches


Notes



HLA Object Classes


HLA Object Classes




HLA Data Types

Conceptual Model


State Machine

Entity Type

Event Type

Model Mapping

Entity Type Mapping

Event Type MappingFOM BOM

9

You Can Use BOMs in Multiple Ways!Model Identification (Metadata)


Conceptual Model Definition


State Machine

Entity Type

Event Type


Notes)



State Machine

Entity Type

Event Type



State Machine

Entity Type

Event Type

Lexicon (definitions)Lexicon (definitions)


Notes


Model Mapping

Entity Type Mapping

Event Type Mapping


Notes


Model Mapping

Entity Type Mapping

Event Type Mapping

Model Mapping

Entity Type Mapping

Event Type Mapping

Mappings


Notes



HLA Object Classes


HLA Object Classes




HLA Data Types


Notes



HLA Object Classes


HLA Object Classes




HLA Data Types


HLA Object Classes


HLA Object Classes




HLA Data Types

Conceptual (Behavioral)

Object (Class Structures)

10

This is what we did with the RPR BOMs…

Object (Class Structure) BOM

Behavior (Conceptual)BOM



Notes



HLA Object Classes


HLA Object Classes




HLA Data Types

Model Identification (Metadata)Model Identification (Metadata)

Model Mapping

Entity Type Mapping

Event Type Mapping

Conceptual Model


State Machine

Entity Type

Event Type

Notes


HLA Data Types

11

We also found a logical connection between the “patterns of interplay” being represented by the RPR FOM (going back to DIS PDU families) and the “HLA Interaction classes” that were defined. So we decided to keep the interaction classes with the conceptual model

This is what we did with the RPR BOMs…


• Repair

• Resupply

• Collision





• Minefield



• Repair

• Resupply

• Collision





• Minefield




We found the easy thing to do was pull out the HLA object classes into object groupings.

Remember this is just one way!!!

12

We could have put the Mappings in the Object-based BOMs. But we felt that the mappings were better served tethered to the Behavior (Conceptual) BOMs

This example also shows that both the interaction classes and object classes could have been isolated from the Behavioral (Conceptual) BOMs





State Machine

Entity Type

Event Type


Notes)



State Machine

Entity Type

Event Type



State Machine

Entity Type

Event Type


We could have done it this way…

Behavioral (Conceptual) BOMs


Notes



HLA Object Classes


HLA Object Classes




HLA Data Types

Model Mapping

Entity Type Mapping

Event Type Mapping


Notes



HLA Object Classes


HLA Object Classes




HLA Data Types


HLA Object Classes


HLA Object Classes




HLA Data Types

Model Mapping

Entity Type Mapping

Event Type Mapping

Model Mapping

Entity Type Mapping

Event Type Mapping

Object (Class Structure) BOMs

13

Or this way…





State Machine

Entity Type

Event Type


Notes)



State Machine

Entity Type

Event Type



State Machine

Entity Type

Event Type



Notes


Model Mapping

Entity Type Mapping

Event Type Mapping


Notes


Model Mapping

Entity Type Mapping

Event Type Mapping

Model Mapping

Entity Type Mapping

Event Type Mapping

Mappings


Notes



HLA Object Classes


HLA Object Classes




HLA Data Types


Notes



HLA Object Classes


HLA Object Classes




HLA Data Types


HLA Object Classes


HLA Object Classes




HLA Data Types

Behavioral (Conceptual)Object (Class Structures)

We could have also made independent mappings – thus making them their own BOMs.

There is no real wrong way to break a FOM up into BOMs.

14

BOM Assemblies


Notes



HLA Object Classes

HLA Attributes

HLA Object Classes

HLA Data Types

EntityObjects BOM

WeaponsFire BOM


Notes




HLA Parameters


HLA Data Types

Conceptual Model


State Machine

Entity Type

Event Type

Model Mapping

Entity Type Mapping

Event Type Mapping

Repair BOM


Notes




HLA Parameters


HLA Data Types

Conceptual Model


State Machine

Entity Type

Event Type

Model Mapping

Entity Type Mapping

Event Type Mapping


Conceptual Model


State Machine

Entity Type

Event Type

BOM Assembly

Notes


A composition of BOMs that can result in a Federation Object Model (FOM), Simulation Object Model (SOM), or pattern which encompasses a larger scope.

15

Exporting a FOM


Notes



HLA Object Classes


HLA Object Classes




HLA Data Types

Conceptual Model


State Machine

Entity Type

Event Type

Model Mapping

Entity Type Mapping

Event Type Mapping

XSLT/Method of

choice

BOM AssemblyModel Identification (Metadata)

Notes


HLA Object Classes


HLA Object Classes




HLA Data Types

HLA Dimensions

HLA Time

HLA Tags

HLA Synchronizations

HLA Transportations

HLA Switches

FOM

16

Object Representations

EntityObjects

SignalObjects

EnvironmentObjects

MinefieldObjects

Object Representations• Entity Object Types• Signal Object Types• Env Object Types• Minefield Object Types

Object Representations• Entity Object Types• Signal Object Types• Env Object Types• Minefield Object Types

Again, this is what we did with the RPR BOMs.

These are the HLA Object Classes from the original RPR FOM categorized into four sets.

17

BOM to FOM: Major Steps

• Create a BOM Assembly– Independent BOMs identified in

Pattern Description

• Atomize BOM-Assembly– Model Definition only carries one level

of object classes / interaction classes– Pattern Descriptions link BOMs

• Transform to FOM (HLA)– Recommend use of XSLT

Pattern

Action

n

BOM(Another Pattern)

1

BOM Assembly

SOM

FOM

BOMs

BOM Assembly

n

Aggregate Model

Xformation

18

Inside a RPR BOM

Weapons Effects

19

BOM Metadata Structure

Name

Type

Version

Modification Date

Security Classification

Release Restriction *

Purpose

Application Domain

Description

Use Limitation

Use History *

Keyword Taxonomy/Value *

POCs * Type Name Organization Telephone Email

References *

Other

Glyph Type Image Alternate Text Height Image

Model Identification Table

* Multiples Allowed



Object Classes


HLA Object Classes

Interaction Classes



HLA Data Types

Conceptual Model

Pattern Description

State Machine

Entity Type

Event Type

Model Mapping

Entity Type Mapping

Event Type Mapping

primary purpose of this metadata is to allow thediscovery and understanding of models &

components.

20Example – Model Identification

• This is the metadata• Leveraged elements from HLA OMT, Dublin Core, DDMS, VV&A RPG• Helps make components/piece-parts meaningful!

Category Information

Name WeaponsEffect

Type BOM

Version 1.0

Modification Date 2005-9-19

Security Classification Unclassified

Release RestrictionNot for release outside the I/ITSEC community

Purpose Warfighter Training, Testing

Application DomainRealtime Platform Testing/Training Simulation

Description This is an example BOM

Use Limitations None

Use History Initial release

Keyword

Taxonomy Military Warfare

Keyword Value Engagement

POC

POC Type Primary author

POC Name P. Gustavson

POC Organization SimVentions

POC Telephone 540 372-7727

Reference

Ref Type Glossary

Identification ISBN 12345678901

Reference

Ref Type Conceptual Model

Identification http://boms.info/

Other na

Glyph

Image

Alt WeaponEffectPicture1

Height 32

Width 32

http://boms.info/

21

21

Example – Pattern Description

• Composed of a collection of actions– Describe the activities which transpire

among the conceptual entities being modeled

– Each action supported by events or other BOMs

• Includes support for variations and exceptions

{OR}

1

*

1

*

Pattern

Action

«entity type»Sender

«entity type»Receiver

BOM

«event type»Event

Exception

Variation

0..1

*

1

*

0..1

*

Actions Seq Name Event BOM Sender Receiver

1 WeaponFireAction WeaponFire na FiringEntity TargetEntity

2 MunitionDetonationAction MunitionDetonation na FiringEntity TargetEntity

3 DamageStateUpdateAction DamageStateUpdate na TargetEntity FiringEntity

22

22Example – State Machine

“The use of interaction classes involves a detailed understanding of the state transitions and timing between events.” - RPR FOM GRIM

Name TargetStates

ObjectEntityClass TargetEntity

State

Name Ready

ExitAction WeaponFireAction

NextState UnderFire

Notes

State

Name UnderFire

ExitAction MunitionDetonationAction

NextState MunitionFlight

Notes

State

Name ImpactDenotation

ExitAction DamageStateUpdateAction

NextState Ready

Notes

Name ShooterStates

Conceptual Entities FiringEntity

State

Name Ready

ExitAction CommandToFire

NextState Fire

Notes

State

Name Fire

ExitAction WeaponFireAction

NextState MunitionFlight

Notes

State

Name MunitionFlight

ExitAction MunitionDetonationAction

NextState Ready

Notes

State Machine

States

1

*

Exit Condition

1

*

NextState

1 *

ExitAction

«entity type»Conceptual Entity

23

Example - Entities

Entity Type

Entity Characteristics

1

*

NOTE: FiringEntity and TargetEntity could be supported by the same EntityType

Unique id for entityID


Velocity for the entityVelocity

Physical position of the entity

LocationThing that is the intended target of a weapon fire

TargetEntity


LocationThing that fires a weapon at a target

FiringEntity

DescriptionCharacteristicsDescriptionName

Entity Type



Velocity for the entityVelocity


LocationThing that is the intended target of a weapon fire

TargetEntity


LocationThing that fires a weapon at a target

FiringEntity

DescriptionCharacteristicsDescriptionName

Entity Type

24

Example - Events

There are three types of characteristics that support an event: source, target and content. Source and Target specify the ”direction” of events. Content defines the information exchanged in the course of the event. There is also a trigger condition which indicates the condition under which this event could be invoked.

If the BOM developer specifies a target characteristic, the event type could be said to be a ”Message” and if there is no target but a trigger condition, it is a ”Trigger”.

Damaged = TRUETargetEntity_identiferDamageStateUpdate

TargetEntity_identiferFiringEntity_identiferMunitionDetonation

Munition_identiferTargetEntity_identiferFiringEntity_identiferWeaponFire

Trigger ConditionContent

CharacteristicTarget CharacteristicSource CharacteristicName

Damaged = TRUETargetEntity_identiferDamageStateUpdate

TargetEntity_identiferFiringEntity_identiferMunitionDetonation

Munition_identiferTargetEntity_identiferFiringEntity_identiferWeaponFire

Trigger ConditionContent

CharacteristicTarget CharacteristicSource CharacteristicName

25


HLA Object Classes


HLA Object Classes




HLA Data Types

Conceptual Model

Pattern Description

State Machine

Entity Type

Event Type

Model Mapping

Entity Type Mapping

Event Type Mapping

Model Mapping / Object Model Def


Platforms

EnviroObjects

MinefieldObjects

What things in my Training Environmentwill support

Weapons Effect?

WeaponsEffect

Entity Types Event Types

WeaponFire

Radios

Sensors

Munitions

Lifeforms Detonations

Collisions

Radio Signal

Repair

Resupply

Ack

EnviroObject

Transactions

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 (object classes / interaction classes).

represents the information necessary for execution and exchange.

26

Model Mappings

Entity Type Mapping Table

Entity Type HLA Object/Interaction Class Characteristics HLA Attributes/Parameters Condtn

FiringEntityHLAobjectClassRoot.BaseEntity.PhysicalEntity.Lifeform.Human

ID Human.EntityIdentifier NA

Location Human.Spatial.SpatialFP.WorldLocation NA

TargetEntityHLAobjectClassRoot.BaseEntity.PhysicalEntity.Platform

ID Platform.EntityIdentifier NA

Location Platform.Spatial.SpatialFP.WorldLocation NA

Velocity Platform.Spatial.SpatialFP.VelocityVector NA

Event Type Mapping Table

Event Type HLA Object/Interaction Class Characteristics HLA Attributes/Parameters Condition

WeaponFire

HLAinteractionRoot.WeaponFire

FiringEntity_Identifier .FiringObjectIdentifier NA

TargetEntity_Identifier .TargetObjectIdentifier NA

MunitionEntity_Identifier .MunitionObjectIdentifier NA

MunitionDetonation

HLAinteractionRoot.MunitionDetonation

FiringEntity_Identifier MunitionDetonation.FiringObjectIdentifier

NA

TargetEntity_Identifier MunitionDetonation.TargetObjectIdentifier

NA

DamageStateUpdate

HLAobjectClassRoot.BaseEntity.PhysicalEntity

Damage sustained from weapon fire

PhysicalEntity.DamageState

.DamageState != .previousDamageState

27

Object Model Def – Attributes Examples

Object Model Def - HLA Object Class Examples

PlatformPhysicalEntityBaseEntityHLAobjectRoot

HumanLifeform

HLA Object Classes

PlatformPhysicalEntityBaseEntityHLAobjectRoot

HumanLifeform

HLA Object Classes

OnChange

OnChange

OnChange

NA

NA

UpdateCond.

Conditional

Conditional

Conditional

Conditional

NA

UpdateType

StanceCodeEnum32

HatchStateEnum32

ForceIdentifierEnum8

SpatialStruct

NA

Datatype

StanceCode

HatchState

ForceIdentifier

Spatial

HLApriviledgeToDelete

Attribute

Lifeform

Platform

PhysicalEntity

BaseEntity

HLAobjectRoot

Object

ReceiveHLAreliableNAPSNo Transfer


ReceiveHLAreliableNANANA

OrderTransportationAvailableDimensionsP/S

Ownership



HLA Attributes

OnChange

OnChange

OnChange

NA

NA

UpdateCond.

Conditional

Conditional

Conditional

Conditional

NA

UpdateType

StanceCodeEnum32

HatchStateEnum32


SpatialStruct

NA

Datatype

StanceCode

HatchState

ForceIdentifier

Spatial

HLApriviledgeToDelete

Attribute

Lifeform

Platform

PhysicalEntity

BaseEntity

HLAobjectRoot

Object



ReceiveHLAreliableNANANA

OrderTransportationAvailableDimensionsP/S

Ownership



HLA Attributes

28

Object Model Def - HLA Interaction Class Examples

Object Model Def –Parameters Examples

:

HLA Parameters

StanceCodeEnum32

HatchStateEnum32


SpatialStruct

NA

Datatype

WarheadType

TargetObjectIdentifier

MunitionType

RateOfFire

MunitionObjectIdentifier

Parameter

WeaponFire

WeaponFire

MuntionDetonation

MunitionDetonation

MunitionDetonation

Interaction

:

HLA Parameters

StanceCodeEnum32

HatchStateEnum32


SpatialStruct

NA

Datatype

WarheadType

TargetObjectIdentifier

MunitionType

RateOfFire

MunitionObjectIdentifier

Parameter

WeaponFire

WeaponFire

MuntionDetonation

MunitionDetonation

MunitionDetonation

Interaction

MunitionDetonation

WeaponFireHLAinteractionRoot


MunitionDetonation

WeaponFireHLAinteractionRoot


29

HLA Object Class / Attribute Values

HLA Interaction Class / Parameter Values

Interaction Parameter DatatypeAvailable

DimensionsTransportation Order

AvailableValues

User definedUser defined

Static,Periodic,ConditionNA

NAHLAreliable,HLAbesteffortNA

Receive,Timestamp

,NA

Default Selection

- - NA NA NA NA

Filling in the BOM “Object Model Def” Information Available Choices / Default Values

AttributeDatatype

UpdateType

UpdateCondition

Ownership

P/S

AvailableDimensions

Transportation

Order

Available Values

User defined

User defined

Static,Periodic,Conditional,NA

rate value,on change,condition value,NA

D,A,N,DA,NA

P, S,PS,N,NA

NA

HLAreliable,HLAbesteffort,NA

Receive,Timestamp, NA

Default Selection

- - NA NA NA NA NA NA NA

30Filling in the Object ClassesA Graphical Illustration

NA

NA

NA

NA

NA

NA

NA

NA

For BOMs, you are allowed to use the “NA” value to tag many of the fields of the Object Class and Object Class Attributes

For an HLA FOM or SOM, however, you may need to specify these fields with something other than NA

31Filling in the Interaction ClassA Graphical Illustration

n/a

n/a

n/a

n/a

For BOMs, you are allowed to use the “NA” value to tag many of the fields of the Interaction Class and Object Class Parameters

For an HLA FOM or SOM, however, you may need to specify these fieds with something other than NA

32

Backup Slides

33

Why is Model Composability Desirable?

• Creating a simulation requires breaking the problem into parts that can be addressed separately

– To reduce the effects of interruption– To permit specialization– To facilitate computing alternative ways of

handling a given component– To maintain the software over time– To reduce risk by relying upon previously proven

components where possible• Understanding complex systems requires

decomposition. – No one can comprehend the whole’s details

• Testing systems is simplified if done module by module then at the system level

• Controlling M&S costs / economic incentives– Costs are correlated with the amount of new code

writing• Maintaining and modifying M&S

– Individual modules can be substantively modified or updated as software as necessary, without endangering the overall system.

“Modularity is necessary when dealing with complex systems, and some degree of composability is surely possible and desirable.” - Paul Davis (RAND)

34

BOM Support for MDA Objectives

• Define a model that specifies your system and its behavior without providing the details of how the computational infrastructure will support it– The role of abstractions

• Model should describe the system from several perspectives– Structure, collaboration,

activity, sequence, state– UML with executable

extensions

• Model should provide increased portability through abstraction

• Model should provide sufficient detail– Completely specify behavior with

action specification• Use of ASL, state charts,

sequence charts– Satisfy mission requirements

• Transform the system model to executable code with model compiler tools tailored for target environment– Possibly several build stages:

compile to lower level language, then object code, then binary

• Rebuild as needed from the system model– Requirements changes– Different or updated

environments

BOM

BOM

BOM

BOM

1 Real-Time Platform Reference (RPR) Base Object Model (BOM) Composability Standard for Enabling...

Documents

Transcript of 1 Real-Time Platform Reference (RPR) Base Object Model (BOM) Composability Standard for Enabling...