1. BOM Template Specification Images SISO-STD-003.1-DRAFT-V0.13

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

3. A B C X

4. structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment, and management of the described entities BOM Elements 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. 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 Interaction Classes HLA Data Types Conceptual Model Definition Pattern of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping 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. BOM template allows BOMs to be captured in a reusable way maps the relationship between the elements in the Conceptual Model space and the interface description elements described in the HLA Object Model Space

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. 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 Interaction Classes HLA Data Types Conceptual Model Definition Pattern of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping 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 Interaction Classes HLA Data Types Object Model Definition HLA Object Classes HLA Object Class Attributes HLA Object Classes HLA Interaction Classes HLA Interaction Class Parameters HLA Interaction Classes HLA Data Types Conceptual Model Definition Pattern of Interplay State Machine Entity Type Event Type Conceptual Model Definition Pattern of Interplay State Machine Entity Type Event Type Model Mapping Entity Type Mapping Event Type Mapping Model Mapping Entity Type Mapping Event Type Mapping

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

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

12. Example – Conceptual Model Pattern Description State Machine Entity Types Event Types

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

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

16. BOM Top- Level Schema View

17. BOM patternType

18. BOM eventsType

19. BOM stateMachine Type

20. BOM modelDefinition 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. BOMs Metadata Rich HLA Object Models (FOMs) Federate View Communication View Class a Class b Class x Class a Class c Class x Class b Class c Class x Class a Class b Class d BOM Assembly (Composite) More OMT Implementation View (within each Federate) BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State MachineBOM x - State Machine BOM Component Imp Reuse Library * Required Optional * LEGEND Potentially more than one occurrence SOM Conceptual / Interface View Federate Code / Libraries Conceptual / Interface View FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve) RTI BOM 1 - PatternBOM 2 - PatternBOM 3 - PatternBOM n - Pattern Federation View

25. BOMs Metadata Rich HLA Object Models (FOMs) Federate View Entity a Entity b Entity x Entity a Entity c Entity x Entity b Entity c Entity x Entity a Entity b Entity d BOM Assembly (Composite) More HLA OMT elements Implementation View (within each Federate) BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State MachineBOM x - State Machine BOM Component Imp Reuse Library * Required Optional * LEGEND Potentially more than one occurrence SOM Conceptual Model View Federate Code / Libraries Conceptual Model View FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve) BOM 1 - PatternBOM 2 - PatternBOM 3 - PatternBOM n - Pattern Federation View

26. BOMs Metadata Rich HLA Object Models (FOMs) Federate View Entity a Entity b Entity x Entity a Entity c Entity x Entity b Entity c Entity x Entity a Entity b Entity d BOM Assembly (Composite) BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State MachineBOM x - State Machine Reuse Library * Required Optional * LEGEND Potentially more than one occurrence Conceptual Model View BOM 1 - PatternBOM 2 - PatternBOM 3 - PatternBOM n - Pattern Federation View Object Model View (class structures within multiple BOMs or a single SOM) Object Class y Attribute 4 Attirbute 5 Attribute 6 Object Class y Attribute 1 Attirbute 2 Attribute 3 Object Class z Attribute 7 Attirbute 8 Attribute 9 Interaction Class r Attribute 1 Attirbute 2 Attribute 3 Interaction Class s Attribute 4 Attirbute 5 Attribute 6 Object Model View (class structures within multiple BOMs or a single SOM) Object Class y Attribute 4 Attirbute 5 Attribute 6 Object Class y Attribute 1 Attirbute 2 Attribute 3 Object Class z Attribute 7 Attirbute 8 Attribute 9 Interaction Class Q Attribute 1 Attirbute 2 Attribute 3 Interaction Class R Attribute 4 Attirbute 5 Attribute 6 Implementation View (within each Federate) BOM Component Imp Federate Code / Libraries

27. BOMs Metadata Rich HLA Object Models (FOMs) Federate View Entity a Entity b Entity x Entity a Entity c Entity x Entity b Entity c Entity x Entity a Entity b Entity d BOM Assembly (Composite) BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State MachineBOM x - State Machine Reuse Library * Required Optional * LEGEND Potentially more than one occurrence Conceptual Model View BOM 1 - PatternBOM 2 - PatternBOM 3 - PatternBOM n - Pattern Federation View Object Model View (class structures defined within multiple BOMs or a single SOM) Object Class y Attribute 4 Attirbute 5 Attribute 6 Object Class y Attribute 1 Attirbute 2 Attribute 3 Object Class z Attribute 7 Attirbute 8 Attribute 9 Interaction Class Q Attribute 1 Attirbute 2 Attribute 3 Interaction Class R Attribute 4 Attirbute 5 Attribute 6 Implementation View (within each Federate) BOM Component Imp Federate Code / Libraries Object Model View (class structures defined within multiple BOMs or a single SOM) Object Class y Attribute 4 Attirbute 5 Attribute 6 Object Class y Attribute 1 Attirbute 2 Attribute 3 Object Class z Attribute 7 Attirbute 8 Attribute 9 Interaction Class Q Attribute 1 Attirbute 2 Attribute 3 Interaction Class R Attribute 4 Attirbute 5 Attribute 6

28. BOMs Metadata Rich HLA Object Models (FOMs) Federate View Entity a Entity b Entity x Entity a Entity c Entity x Entity b Entity c Entity x Entity a Entity b Entity d State Machine aState Machine bState Machine cState Machine dState Machine x Reuse Library * Required Optional * LEGEND Potentially more than one occurrence Conceptual Model View Pattern of Interplay 1Pattern of Interplay 2Pattern of Interplay 3Pattern of Interplay 4 Federation View Object Model View (class structures supported with each Federate to represent conceptual elements) Object Class y Attribute 4 Attirbute 5 Attribute 6 Object Class y Attribute 1 Attirbute 2 Attribute 3 Object Class z Attribute 7 Attirbute 8 Attribute 9 Interaction Class Q Attribute 1 Attirbute 2 Attribute 3 Interaction Class R Attribute 4 Attirbute 5 Attribute 6 Implementation View (capability within each Federate) BOM Component Imp Federate Code / Libraries Object Model View (class structures describing context for information exchange among Federation) Object Class y Attribute 4 Attirbute 5 Attribute 6 Object Class y Attribute 1 Attirbute 2 Attribute 3 Object Class z Attribute 7 Attirbute 8 Attribute 9 Interaction Class Q Attribute 1 Attirbute 2 Attribute 3 Interaction Class R Attribute 4 Attirbute 5 Attribute 6 Entity a1Entity a2Entity b1Entity b2Entity c1Entity c2Entity dEntity x1Entityx2 Event GEvent HEvent EEvent F Event CEvent DEvent AEvent B

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

30. BOMs Metadata Rich HLA Object Models (FOMs) Federate View Entity a Entity b Entity x Entity a Entity c Entity x Entity b Entity c Entity x Entity a Entity b Entity d BOM Assembly (Composite) More HLA OMT elements Implementation View (within each Federate) BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State MachineBOM x - State Machine BOM Component Imp Reuse Library * Required Optional * LEGEND Potentially more than one occurrence SOM Conceptual Model View Federate Code / Libraries Conceptual Model View FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve) BOM 1 - PatternBOM 2 - PatternBOM 3 - PatternBOM n - Pattern Federation View Object Model View BOM a – Object Class / Attribute

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

32. Federate (SOM) BOMs (Coupling) BOM Assembly BOM 1 BOM 3 BOM n Composite Interface Composition Sim / System A Representation Federation (FOM) Federate B Federate X Federate A Aggregation Model #1 Model #2 Model #3 Model #n - or - These BOMs represent the relationship of activities among conceptual entities (FOM level), Weapons Effect Radio Comms Theater Warfare Representation BOM 2 Repair Resupply Detect / Jam

33. Federate - Conceptual / interface view BOM 1 Sim / System Functional Exposure State Machine Entity Types HLA Object Classes BCI = BOM Component Implementation CODECODE BCI Federate – Implementation View BOM 2 State Machines, Entities, Events ---- Object Classes, Attributes, Interaction Classes, Parameters BOM n State Machines, Entities, Events ---- Object Classes, Attributes, Interaction Classes, Parameters Functional Capability Run-time Execution Figure 6-5 - Application of BOMs for Providing Federate Level Support BOM 1

34. BOM Element Relationship (Conceptual Model View) Pattern ActionEvent n 1 BOM 1 SenderReceiver nn An action can be associated to an event State Machine States n Exit Condition Pattern Action n Next State State Machine Pattern Description An action can be potentially supported completely by another pattern of interplay Entity Characteristics Entity Type Description n Event Type Description Event Source Target Trigger Message Content Entity n Characteristics n Role

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

36. BOM Element -> Model Identification Conceptual Model Model Mapping Object Model Definition Individual BOM (Conceptual Model Def) behavior representation (pattern, state machine, events) Required Optional Individual BOM (Object Model Definition) object repesentation (object classes, interaction classes) RequiredOptional Required BOM Assembly (representing composite of other BOMs) Required Required (Pattern of Interplay) Optional SOM FOM BOMs BOM Assembly n Aggregate Model Xformation Figure 8 ‑ 1 - BOM Elements for Representing a Pattern of Interplay

37. Model Identification (Key meta-data) Type Name Version Mod Date Description Use Limit Use History * Keyword * Sec Class POC * Rel Rstctn * References PurposeOther App DomGlyph Conceptual Model Required Optional * Supports multiple occurrences Figure 8 ‑ 3 –BOM – Model Identification Table

38. Model Identification (Key metadata) Type Name Version Mod Date Description Use Limit Use History * Keyword * Sec Class POC * Rel Rstctn * References PurposeOther App DomGlyph Required Optional * Supports multiple occurrences Figure 8 ‑ 3 –BOM – Model Identification Table

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

40. Pattern ActionEvent TriggerMessage n 1 BOM (Another Pattern) 1 SourceTarget nn An action can be associated to an event An action can be potentially supported completely by another pattern of interplay Figure 8 ‑ 5 - BOM Template – Pattern Step Relationship

41. Triggers 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. Publish EventSubscribe Event Undirected Events Source Björn Löfstrand – Pitch AB Figure 8 ‑ 7 – Event - Trigger Figure 8-10

42. Messages 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. Send EventReceive Event and react to its contents Directed events Source Björn Löfstrand – Pitch AB Figure 8 ‑ 6 – Event - Message Figure 8-11

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

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

45. Figure 9 ‑ 5 - FEDEP Step 3 Figure 9 ‑ 6 - FEDEP Step 4

46. Figure 9 ‑ 5 - FEDEP Step 3 Figure 9 ‑ 6 - FEDEP Step 4

47. Figure 9 ‑ 10 - FEDEP Step 5

48. Figure 9 ‑ 4 - Conceptual Model Driven Development

49. Find candidate BOMs Use purpose, keywords, and conceptual model as searching criteria Match metadata with available BOMs in repository Find candidate BOMs Use purpose, keywords, and conceptual model as searching criteria Match metadata with available BOMs in repository FEDEP Steps 2 – 4 BOM candidate found 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) 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) 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 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 BOM not found BOM found Identify purpose / objective / intent Focus on capturing conceptual model Identify “pattern of simulation interplay” E.g. Model capabilities of a JCAD Sensor Identify purpose / objective / intent Focus on capturing conceptual model Identify “pattern of simulation interplay” E.g. Model capabilities of a JCAD Sensor Search library results Insert BOM into library Insert BOMs / BOM Assembly into library 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) 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 FOM / SOM into library BOM Development Library Federation Integration results Fetch model Generate FOM / SOM from BOM Assembly FOM/SOM/BOM Reuse Library Conceptual Analysis Design Development Conceptual ModelObject Model

50. FEDEP Steps 2 – 4 Find candidate BOM Use Conceptual Model metadata input for searching Match metadata with available BOMs in repository BOM Candidate Found 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” Integrate BOM within federate XML Parsable BOM Interface BOM Component Implementation (BCI) – if needed BOM not found BOM found BOM Assembly Identify purpose / objective / intent Focus on capturing Conceptual Model Identify “pattern of simulation interplay” E.g. Model capabilities of a JCAD Sensor Conceptual Model BOM Reuse Library Search library results Insert BOM into library Insert BOM Assembly into library Create BOM Assembly Composition of BOMs based on their interface Used to represent system interface (much like SOM) or a federation (much like FOM) Generate FOM / SOM from BOM Assembly Object Model old

51. Find candidate BOM Use Conceptual Model metadata input for searching Match metadata with available BOMs in OMRC (future capability) Find candidate BOM Use Conceptual Model metadata input for searching Match metadata with available BOMs in OMRC (future capability) BOM Candidate Found 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” 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” Integrate BOM within federate XML Parsable BOM Interface BOM Component Implementation (BCI) – if needed Integrate BOM within federate XML Parsable BOM Interface BOM Component Implementation (BCI) – if needed BOM not found BOM found FEDEP Step 3 FEDEP Step 4 BOM Assembly Identify purpose / objective / intent Focus on capturing Conceptual Model Identify “pattern of simulation interplay” E.g. Model capabilities of a JCAD Sensor Identify purpose / objective / intent Focus on capturing Conceptual Model Identify “pattern of simulation interplay” E.g. Model capabilities of a JCAD Sensor FEDEP Step 2 FEDEP Step 1 Conceptual Model BOM Reuse Library Search library results Insert BOM into library Insert BOM Assembly into library Create BOM Assembly Composition of BOMs based on their interface Used to represent system interface (much like SOM) or a federation (much like FOM) Create BOM Assembly Composition of BOMs based on their interface Used to represent system interface (much like SOM) or a federation (much like FOM) Generate FOM / SOM from BOM Assembly old

52. Find candidate BOM Use Conceptual Model metadata input for searching Match metadata with available BOMs in OMRC (future capability) BOM Candidate Found 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” Integrate BOM within federate XML Parsable BOM Interface BOM Component Implementation (BCI) – if needed BOM not found BOM found BOM Assembly Identify purpose / objective / intent Focus on capturing Conceptual Model Identify “pattern of simulation interplay” E.g. Model capabilities of a JCAD Sensor FEDEP Step 2 – Step 5 FEDEP Step 1 Conceptual Model BOM Reuse Library Search library results Insert BOM into library Insert BOM Assembly into library Create BOM Assembly Composition of BOMs based on their interface Used to represent system interface (much like SOM) or a federation (much like FOM) Generate FOM / SOM from BOM Assembly old

53. 1998200220002003 Reference FOM Study Group BOM Methodology Strawman SRML Rapidly composable and scalable M&S 2001 BOM Study Group 1996 RPR FOM 20101999 HLA 1516 FOM “piece parts” (FEDEP, OMT) BOM PDG 2004 BOM History SISO-STD-003.1-2003 BOM Spec Vol 1 Interface BOM BOM Spec Guidance Doc 2006… Tools Components Libraries HLA 1516 Evolve DIS HLA 1990 FEDEP 1516 C M S E Protocol Oriented WSDL Schemas XSLT DTD SOAP Object-Based OrientedComponent/Service Oriented

54. Figure 9 ‑ 7 - Base Object Model in FEDEP Develop Federation 4.1–Develop FOM (Mega-BOM) 4.2–Establish Federation Agreements 4.3–Implement Federate Designs 4.4–Implement Federation Infrastructure Design Federation 3.1–Select Federates 3.2–Prepare Federation Design 3.3–Prepare Plan Conceptual Model Develop Federation 4.1– Develop FOM 4.2–Establish Federation Agreements 4.3–Implement Federate Designs 4.4–Implement Federation Infrastructure Design Federation 3.1–Select Federates 3.2–Prepare Federation Design 3.3–Prepare Plan Conceptual Model BOM Assembly

55. Figure 9 ‑ 8 – Skeleton Design Process

56. Pattern Action n BOM (Another Pattern) 1 Figure 9 ‑ 9 – BOM Assembly – Pattern Action to BOM Relationship

57. BOMs Metadata Rich HLA Object Models (FOMs) Reuse Libraries Composition A BOM 2 BOM 4 BOM 17 Reuse Library BOM 1 BOM 2 BOM 3 Composition B BOM 1 BOM 3 BOM 11 BOM 4 BOM N BOM 23... BOM 19 Figure 10 ‑ 1- Leveraging a BOM Resource Reuse Library

58. Miscellaneous Images

59. User Requirements A B C X BOM Palette - x Choose what fits conceptual model? Simulation Components 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 States n Exit Condition Pattern Action n Next State

61. BOM Element Validity Matrix BOM Element -> Model Identification Model Definition Behavior Description – Pattern Behavior Description – State Machine Behavior Description - Events Individual BOM (representing pattern, state machine, and/or object/interaction class) Required Optional BOM Assembly (representing composite of other BOMs) RequiredOptionalRequiredOptional

62. Application of BOM Elements BOM Element Federation Level Support Federate Level Support Model Identification Required Use Behavior Description / Pattern Intended Use (Required for BOM Assembly) Optional Use Behavior Description / Events Intended UseOptional Use Behavior Description / State Machine Optional UseIntended Use Model Definition (object class/ interaction class / attributes / parameters / datatypes) Intended Use (Not Require for BOM Assembly) Intended Use

63. RPR BOMs RPR FOM 2.0 Repair Resupply Entity Creation Entity Reconst’n Entity Removal Action Request Post Comment Post Event Behavior Rep Object RepEntityObjects EnvObjects MinefieldObjects SignalObjects Weapons Effect Collision E ntity S t U pdate Minefield Synthetic Env SIMAN Logistics RadioComms Includes Model Mapping

64. BOMs Base Object Models LocateComposeCreate Federation Implementations Interfaces Activity Relationship Conceptual Entities Behavioral States Events System Composability Plug & Play Systems Model Composability Reusable Piece Parts What BOMs Provide? – Model Composability 6 5 43 1 Perform Conceptual Analysis 2 Analyze Data and Evaluate Results 7 Define Federation Objectives Design Federation Develop Federation Plan, Integrate, and Test Federation Execute Federation & Prepare Outputs FEDEP BOMs are designed for enabling composability, providing extensibility, facilitating interoperability, improving manageability, and encouraging understandibility.

65. BOM Illustration Jammer (Originator) Radar Threat Detected in Range (Msg) Threat / Target Emits Reflects Detect Jam Detection Jamming Pattern of Interplay State Machine Detect /Jamming Activity Federation ActivitiesFederate Capability

66. BOM Illustration #2 Derived from RPR FOM State Machines Pattern of Interplay pattern actions Weapons Effect states Federation ActivitiesFederate Capability

67. What BOMs Provide? – Model Composability Interface (Profile) BOMs BOM 1 BOM 2 BOM n Conceptual Model View Object Model View Weapons Effect Detect / Jam Radio Comms BOM z Sup plier BOM b BOM a Platform Human BOM c BOM d Radar Munition Logistics CAP Support Collision BOM Assembly Composite Interface Composition Representation Federate B Federate X Federate A Theater Warfare Representation Federation for Joint Training Homeland Defense Training FOM Operation Freedom Training FOM

68. BOM Composition BOM Assembly “Application and Use” Composability View BOM

69. What is Composability? Barriers “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 M&S Master Plan) M&S 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 M&S Metadata Focus Group