1. 1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC morsek@saic.com Mr. Robert Lutz, JHU APL robert.lutz@jhuapl.edu

2. 2 XMSF Profile Overlay Purpose One of the key mechanisms for identifying content and structure requirements for XMSF profiles is to review how profiles will support a concept of operations for various simulation stakeholders –The existing HLA developers and users represent an important community of stakeholders. Overlays are an existing mechanism for relating the FEDEP to other (HLA federation development) processes –Identify FEDEP activities that may be supported through the application of XMSF profiles –Recommend additional tasks within these activities related to profiles

3. 3 Profile Definition XMSF profiles are formal technical specifications for application of interoperable web based technologies to enabling composable and reusable modeling and simulation, and facilitating enterprise integration. The objectives of XMSF profiles are to: –Provide unambiguous specification of the functionality of components, and interfaces among components of the framework –Ensure interoperability between existing and new web enabled technologies, both within M&S and in related domains –Provide the necessary metadata to facilitate composability and reuse of components across multiple M&S application domains –Facilitate development of new applications and services that are functionally interchangeable with existing applications and services –Enable development of new applications and services that readily extend functionality for continuous evolution of capabilities

4. 4 XMSF Profile SG Process Activity Diagram Develop definition and objectives Develop conops and roles and responsibilities Define XMSF- specific requirements Survey profiles from other domains Identify candidate exemplars Identify applicable documentation mechanisms structure Identify necessary interoperability information Draft standard Activities in blue are part of the standard refinement loop content

5. 5 FEDEP Overview Experts in specific disciplines have used FEDEP overlays as a means of defining how their lower–level processes operate within the broader end-to-end federation development process –VV&A –Testing –Fidelity management “Case study” overlays –Meant to convey how the FEDEP was implemented on a specific project Product overlays –Meant to convey how certain tools or tool classes can be used to automate FEDEP activities) The FEDEP is IEEE 1516.3- 2003

6. 6 Step 3 - Design Federation 3.1 - Select federates –The purpose of this activity is to determine the suitability of individual simulation systems to become members of the federation. This is normally driven by the perceived ability of potential federation members to represent objects, activities, and interactions in the federation conceptual model. –Profiles may be used to identify candidate federates. The profiles may be stored in registries where tools may support automated processes for identifying federates and evaluating their applicability to representing required entities/object and events. 3.2 - Prepare federation design –Once all federates have been identified, the next major activity is to prepare the federation design and allocate the responsibility to represent the entities and actions in the federation conceptual model to the federates. This activity will allow for an assessment of whether the set of selected federates provides the full set of required functionality. –Profiles may be used to assess what applicable functionality individual federates provide.

7. 7 Step 4 - Develop Federation 4.2 - Establish federation agreements –Although the FOM defines and documents the full set of data that is exchanged among federates to achieve federation objectives, there are other operating agreements that must be reached among federate developers and management (prior to implementation) that are not necessarily documented in the FOM. Such agreements are necessary to establish a fully consistent, interoperable, distributed simulation environment. –Agreements in existing profiles may be applicable, and therefore, readily reusable. –Also, agreements must be reached as to the databases and algorithms that must be common (or at least consistent) across the federation to guarantee valid interactions among all federation participants. –Review and evaluation of existing profiles may indicate requirements for new profiles.

8. 8 Step 4 - Develop Federation 4.3 – Implement federate designs –The purpose of this activity is to implement whatever modifications are necessary to the federates to ensure that they can represent assigned objects and associated behaviors as described in the federation conceptual model. –Federate modifications may include the addition of functionality that should be recorded in the federate’s profile. 4.4 - Implement federation infrastructure –The purpose of this activity is to implement, configure, and initialize the infrastructure necessary to support the federation and verify that it can support the execution and intercommunication of all federation components. … the initialization and configuration of the network elements, e.g., routers, bridges; and the installation and configuration of supporting software on all computer systems. –If existing profiles are used, ensure they are adhered to. If the need for new profiles has been identified, document the necessary information.

9. 9 Step 5 - Plan, integrate, and test federation 5.2 - Integrate federation –The purpose of this activity is to bring all of the federation participants into a unifying operating environment. This requires that all federate hardware and software assets are properly installed and interconnected in a configuration that can satisfy all FOM data interchange requirements and federation agreements. –Integrate existing systems/simulations via existing and/or new profiles.

10. 10 Step 7 - Analyze data and evaluate results 7.2 - Evaluate and feedback results –The purpose of this activity is to determine if federation objectives have been met and to archive reusable federation products. –Simulation/system developers update profiles as necessary. –… the derived results from the previous activity are evaluated to determine if all federation objectives have been met. –Simulation/system users provide feedback on usability of simulations/systems to simulation/ system developers.

11. 11 Overlay Summary The FEDEP process is outside the profile process, but the profiles are applied in 3.1, 3.2, 4.2, 4.4, and 5.2. Existing profiles and the profile standard may be affected by activities 4.3 and 7.2.

12. 12 Define Federation Objectives 1 Perform Conceptual Analysis 2 Design Federation 3 Develop Federation 4 Execute Federation and Prepare Outputs 6 Plan, Integrate, and Test Federation 5 Analyze Data and Evaluate Results 7 Updated profile standard Updated profiles Corrective Actions / Iterative Development Capability and functionality documentation Profiles of candidate federates Prior federation decisions Database design information Infrastructure design information Security requirements and capabilities Algorithms Time management capabilities Deficiencies in the profile standard Updates /extensions to existing profiles Web server and service requirements Profile Mapping to FEDEP

13. 13 Conclusions XMSF and HLA will complement each other in the web enabled M&S environment –This FEDEP overlay is an example of leveraging this relationship XMSF profiles must capture at least the following information: –Capability and functionality documentation –Database design information –Infrastructure design information –Security requirements and capabilities –Algorithms –Web server and service requirements –Time management capabilities

14. 14 Questions?