1. BOM Template SpecificationImages SISO-STD-003.1-DRAFT-V0.13

2. BOM Palette - x Choose what fits conceptual model A B X C Spec – Figure 1-1 Compositions identified as BOM Assemblies A,B,C and X

3. A B X C

4. BOM Elements Model Identification (Metadata) Conceptual Model Definition Pattern of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping Object Model Definition HLA Object Classes HLA Object Classes HLA Object Class Attributes HLA Interaction Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Data Types Notes Lexicon (definitions) 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. 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. Model Identification (Metadata) Model Identification (Metadata) Conceptual Model Definition Conceptual Model Definition Conceptual Model Definition Pattern of Interplay Pattern of Interplay Pattern of Interplay State Machine State Machine State Machine Entity Type Entity Type Entity Type Event Type Event Type Event Type Model Mapping Model Mapping Model Mapping Entity Type Mapping Entity Type Mapping Entity Type Mapping Event Type Mapping Event Type Mapping Event Type Mapping Object Model Definition Object Model Definition Object Model Definition HLA Object Classes HLA Object Classes HLA Object Classes HLA Object Classes HLA Object Classes HLA Object Classes HLA Object Class Attributes HLA Object Class Attributes HLA Object Class Attributes HLA Interaction Classes HLA Interaction Classes HLA Interaction Classes HLA Interaction Classes HLA Interaction Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Class Parameters HLA Interaction Class Parameters HLA Data Types HLA Data Types HLA Data Types Notes Notes Lexicon (definitions) Lexicon (definitions) BOM Elements

10. message event type source characteristic pattern action, target variation, or characteristic exception content characteristic action type or <<event type>> event trigger <<entity type>> sender <<entity type>> receiver event type source characteristic content characteristic trigger condition

11. message event type event type source source characteristic characteristic pattern action, pattern action, target target variation, or variation, or characteristic characteristic exception exception conceptual entity content content characteristic characteristic action type action type entity type entity type <<event type>> event <<event type>> event <<entity type>> sender <<entity type>> sender trigger trigger characteristic characteristic <<entity type>> receiver <<entity type>> receiver event type event type source source characteristic characteristic content content characteristic characteristic trigger trigger condition condition

12. An action can be potentially supported completely by another pattern of interplay old An action can be associated to an event

13. old

14. old BOM Element Relationship (Conceptual Model View) Event Type Description Entity Type Description Pattern Description State Machine

15. BOM Top-Level Schema View

16. BOM patternType

17. BOM eventsType

18. BOM stateMachine Type

19. BOMmodelDefinition segment

20. BOM notes Type

21. Guide for Base Object Model (BOM) Use and Implementation SISO-STD-003.0-DRAFT-V0.13

22. Figure 6-1 - Examples of Component Reuse

23. BOM Component Imp BOM Component Imp BOM Component Imp LEGEND Required Optional Potentially more thanone occurrence * * 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

24. * Federate View Implementation View (within each Federate) BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries LEGEND Conceptual Model View Required BOM a - State Machine BOM b - State Machine BOM c – State Machine BOM d - State Machine BOM x - State Machine Optional Potentially more thanone occurrence * 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)

25. Object Model View (class structures within multiple BOMs or a single SOM) Object Model View (class structures within multiple BOMs or a single SOM) Object Class y Object Class y Object Class y Object Class y Object Class z Object Class z Interaction Class r Interaction Class Q Interaction Class s Interaction Class R • Attribute 1 • Attirbute 2 • Attribute 3 • Attribute 1 • Attirbute 2 • Attribute 3 • Attribute 4 • Attirbute 5 • Attribute 6 • Attribute 4 • Attirbute 5 • Attribute 6 • Attribute 7 • Attirbute 8 • Attribute 9 • Attribute 7 • Attirbute 8 • Attribute 9 • Attribute 1 • Attirbute 2 • Attribute 3 • Attribute 1 • Attirbute 2 • Attribute 3 • Attribute 4 • Attirbute 5 • Attribute 6 • Attribute 4 • Attirbute 5 • Attribute 6 Implementation View (within each Federate) BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries LEGEND Required Optional Potentially more thanone occurrence * * 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

26. Implementation View (within each Federate) BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries LEGEND Required Optional Potentially more thanone occurrence * * 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 1 • Attirbute 2 • Attribute 3 • Attribute 4 • Attirbute 5 • Attribute 6 • 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 1 • Attirbute 2 • Attribute 3 • Attribute 4 • Attirbute 5 • Attribute 6 • Attribute 7 • Attirbute 8 • Attribute 9 • Attribute 1 • Attirbute 2 • Attribute 3 • Attribute 4 • Attirbute 5 • Attribute 6

27. Implementation View (capability within each Federate) BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries LEGEND Required Optional Potentially more thanone occurrence * * 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 1 • Attirbute 2 • Attribute 3 • Attribute 4 • Attirbute 5 • Attribute 6 • 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 E Event F Event G Event H Event A Event B Event C Event D 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 1 • Attirbute 2 • Attribute 3 • Attribute 4 • Attirbute 5 • Attribute 6 • Attribute 7 • Attirbute 8 • Attribute 9 • Attribute 1 • Attirbute 2 • Attribute 3 • Attribute 4 • Attirbute 5 • Attribute 6

28. Implementation View (within each Federate) BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries Object Model View (class structures within a single SOM or multiple BOMs)

29. BOM Component Imp BOM Component Imp BOM Component Imp LEGEND Required Optional Potentially more thanone occurrence * * 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)

30. Figure 6-4 – Application of BOMs for Providing Various Federation Level Support Federate(SOM) Sim / SystemA BOM 1 BOM 2 Federate A - or - Federate B Federation(FOM) BOM 3 BOMAssembly Representation Composition Federate X CompositeInterface - or - BOM n Model#1 Model#2 Aggregation BOMs(Coupling) Model#3 Model#n These BOMs represent the relationship of activities among conceptual entities (FOM level),

31. Federate(SOM) Sim / SystemA BOM 1 WeaponsEffect BOM 2 Federate A Detect / Jam Theater WarfareRepresentation - or - Federate B Federation(FOM) BOM 3 BOMAssembly RepairResupply Representation Composition Federate X CompositeInterface - or - BOM n Model#1 Model#2 RadioComms Aggregation BOMs(Coupling) Model#3 Model#n These BOMs represent the relationship of activities among conceptual entities (FOM level),

32. 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

33. 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 Event Action BOM n PatternAction ExitCondition NextState n n Sender Receiver Event Type Description Entity Type Description Event Entity n Role Characteristics Source n Target Characteristics Trigger Message Content

34. Perform Conceptual Analysis Plan, Integrate, and Test Federation Define Federation Objectives Analyze Data and Evaluate Results Develop Federation Design Federation Execute Federation and Prepare Outputs 5 1 3 4 6 7 2 Corrective Actions / Iterative Development Figure 7-1 – FEDEP Seven-Step Process

35. Figure 8‑1 - BOM Elements for Representing a Pattern of Interplay SOM BOM Assembly Xformation FOM n BOMs Aggregate Model

36. Model Identification(Key meta-data) ConceptualModel Name Description Type Use Limit Version Use History* Mod Date Keyword* Sec Class POC* Required Rel Rstctn* References Optional Purpose Other Supportsmultiple occurrences * App Dom Glyph Figure 8‑3 –BOM – Model Identification Table

37. Name Description Type Use Limit Version Use History* Mod Date Keyword* Sec Class POC* Rel Rstctn* References Purpose Other App Dom Glyph Model Identification(Key metadata) Required Optional Supportsmultiple occurrences * Figure 8‑3 –BOM – Model Identification Table

38. Pattern of Interplay Name * Actions (Activities) Sequence Name Source* Target* Event BOM Exceptions* Variations* Figure 8‑4 - BOM Template – Pattern Description

39. An action can be associated to an event An action can be potentially supported completely by another pattern of interplay Pattern n 1 Event Action 1 BOM(Another Pattern) n n Trigger Message Source Target Figure 8‑5 - BOM Template – Pattern Step Relationship

40. Figure 8-10 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 may react or respond to such an action. Figure 8‑7 – Event - Trigger Source Björn Löfstrand – Pitch AB

41. Send Event Receive Event and react to its contents Figure 8-11 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 reacts to the information contained in the directed message. • In the HLA, the federate responsible for modeling the receiving conceptual entity(s) may respond to the specific sent interaction or object attribute update. Figure 8‑6 – Event - Message Source Björn Löfstrand – Pitch AB

42. Figure 8-2 - FEDEP Steps 1 & 2

43. Figure 9‑1 - FEDEP Step 1 Figure 9‑2 - FEDEP Step 2

44. Federation Federation Scenario(s) Conceptual Federation (2.1) (2.1) Model (2.2) Requirements (2.3) Multiple Items: Multiple Items: Federate & • • FOM / BOM Assembly Federation (4.1) (4.1) Develop Federation Develop Federation Designs (3.2) • • FED/FDD (4.1) • • Scenario Instances 4.1 4.1 – – Develop FOM (Mega Develop FOM (Mega - - BOM) BOM) (4.2) 4.2 4.2 – – Establish Federation Establish Federation Federation • • Modified/New Agreements Agreements Development & 4.3 4.3 – – Implement Federate Designs Implement Federate Designs Federates (4.3) 4.4 4.4 – – Implement Federation Implement Federation Execution Plan • • Federation Infrastructure Infrastructure (3.3) Infrastructure (4.4) • • RTI Init Data (4.4) • • Supporting Databases (4.3) Federation Agreements (4.2) Figure 9‑6 - FEDEP Step 4 Figure 9‑5 - FEDEP Step 3

45. Federation Federation Federation Federation Scenario(s Scenario(s ) ) Conceptual Conceptual Federation Federation (2.1) (2.1) Model (2.2) Model (2.2) Requirements (2.3) Requirements (2.3) Multiple Items: Multiple Items: Federate & Federate & • • FOM / BOM Assembly FOM / BOM Assembly Federation Federation (4.1) (4.1) Develop Federation Develop Federation Designs (3.2) Designs (3.2) • • FED/FDD (4.1) FED/FDD (4.1) • • Scenario Instances Scenario Instances 4.1 4.1 – – Develop FOM (Mega Develop FOM (Mega - - BOM) BOM) (4.2) (4.2) 4.2 4.2 – – Establish Federation Establish Federation Federation Federation • • Modified/New Modified/New Agreements Agreements Development & Development & Federates (4.3) Federates (4.3) 4.3 4.3 – – Implement Federate Designs Implement Federate Designs 4.4 4.4 – – Implement Federation Implement Federation Execution Plan Execution Plan • • Federation Federation Infrastructure Infrastructure (3.3) (3.3) Infrastructure (4.4) Infrastructure (4.4) • • RTI Init Data (4.4) RTI Init Data (4.4) • • Supporting Supporting Databases (4.3) Databases (4.3) Federation Federation Agreements Agreements Figure 9‑6 - FEDEP Step 4 Figure 9‑5 - FEDEP Step 3

46. Figure 9‑10 - FEDEP Step 5

47. Perform Perform Plan, Plan, Define Define Analyze Analyze Develop Develop Design Design Execute Execute Conceptual Conceptual Integrate, Integrate, Federation Federation Data and Data and Federation Federation Federation Federation Federation Federation Objectives Objectives Analysis Analysis and Test and Test Evaluate Evaluate and and Federation Federation Results Results Prepare Prepare Outputs Outputs 5 5 1 1 3 3 4 4 6 6 7 7 2 2 Corrective Actions / Iterative Development Corrective Actions / Iterative Development F E D E P F E D E P F E D E P F E D E P Conceptual Conceptual Model Model Model Model Identifies Identifies Used to help Used to help • • • • Verify results • • purpose validate semantic composabilty composabilty Used to Used to • • locate locate Verify results • • BOM BOM candidate candidate BOM Mega - BOM Mega - BOM Assembly Figure 9‑4 - Conceptual Model Driven Development

48. 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) 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 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

49. Identify purpose / objective / intent • Focus on capturing Conceptual Model • Identify “pattern of simulation interplay” • E.g. Model capabilities of a JCAD Sensor Find candidate BOM • Use Conceptual Model metadata input for searching • Match metadata with available BOMs in repository 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 BOM CandidateFound Conceptual Model Object Model Insert BOM into library BOM found 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 FEDEPSteps 2 – 4 old

50. 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 Create BOM Assembly • Composition of BOMs based on their interface • Used to represent system interface (much like SOM) or a federation (much like FOM) 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 Insert BOM Assembly into library Generate FOM / SOM from BOM Assembly