Modeling And Simulation


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Modeling And Simulation

  1. 1. Modeling and Simulation Reuse Analysis From IEEE 1517 to SOA May 23-24, 2006 Doug Clark, DMSO/GARD Associates, LLC John James, MITRE Larry Pizette, MITRE Approved for Public Release; Distribution Unlimited Case Number: 06-0641 ©2006 The MITRE Corporation. All rights reserved.
  2. 2. Agenda <ul><li>Background </li></ul><ul><li>Reuse Vision </li></ul><ul><li>M&S Domain </li></ul><ul><li>Why SOA? </li></ul><ul><li>Governance </li></ul><ul><li>Business Case </li></ul><ul><li>SOA and Middleware </li></ul><ul><li>Use of Open Source and Reusable Infrastructure </li></ul><ul><li>Reuse of Data/Models </li></ul><ul><li>SOA Adoption Challenge </li></ul>
  3. 3. Background <ul><li>Objective </li></ul><ul><ul><li>Determine methods of reuse for the M&S community ranging from IEEE 1517 to Service Oriented Architecture </li></ul></ul><ul><ul><li>M&S reuse to include as example: </li></ul></ul><ul><ul><ul><li>Simulations: training, testing and analysis </li></ul></ul></ul><ul><ul><ul><li>Scenarios </li></ul></ul></ul><ul><ul><ul><li>Physics based models </li></ul></ul></ul><ul><ul><ul><li>Data </li></ul></ul></ul><ul><li>Anticipated benefits: accomplish more with the same resources </li></ul><ul><ul><li>Reduced cost: development and sustainment </li></ul></ul><ul><ul><li>Reduced time to respond to new and/or changing simulation requirements </li></ul></ul>
  4. 4. M&S Reuse Vision <ul><li>Move towards a future of Service Oriented Architecture </li></ul><ul><ul><li>IEEE 1517 policy (top down strategy) </li></ul></ul><ul><ul><li>Programs delivering SOA reuse solutions (bottom up strategy) </li></ul></ul><ul><li>Extend the working definition of reuse in IEEE 1517 to include SOA </li></ul><ul><ul><li>Suggest DMSO policy that SOA is the preferred form of reuse for all M&S programs </li></ul></ul><ul><ul><li>Participate in IEEE 1517 discussion when the standard is reopened for review </li></ul></ul>
  5. 5. Is this the M&S Path to SOA?
  6. 6. M&S Domain <ul><li>Distributed computing </li></ul><ul><ul><li>Location distributed </li></ul></ul><ul><ul><li>Organization distributed </li></ul></ul><ul><li>Time considerations vary by need </li></ul><ul><ul><li>Real time or non-real time-synchronized </li></ul></ul><ul><li>Wide variety of needs and uses </li></ul><ul><ul><li>Multi-million dollar exercises (training, etc) </li></ul></ul><ul><ul><li>Physics based models and simulations </li></ul></ul><ul><ul><li>Human-in-the-loop </li></ul></ul><ul><li>Significant past and on-going investment in M&S </li></ul><ul><li>Security implications </li></ul>
  7. 7. Parallels Between Simulation Federations and SOA
  8. 8. Why SOA for M&S? (1 of 2) <ul><li>SOA provides industry standard service-to-service communication </li></ul><ul><li>SOA provides platform/operating system independence </li></ul><ul><li>Many commercial standard SOA development environments </li></ul><ul><li>Integration through SOA is straight forward </li></ul><ul><ul><li>SOAP/XML interface to High Level Architecture (HLA) less effort than to use HLA API </li></ul></ul><ul><ul><li>Many commercial tools to help with SOAP/ XML </li></ul></ul><ul><ul><li>System engineering important regardless of SOA or HLA </li></ul></ul><ul><ul><li>Commercial marketplace, producers and suppliers, rapidly embracing and incorporating SOA concepts </li></ul></ul>The future of M&S middleware should include SOA
  9. 9. Why SOA for M&S? (2 of 2) <ul><li>Organizational agility/orchestration </li></ul><ul><ul><li>Recompose tactics and procedures without extensive redesign of systems/simulations </li></ul></ul><ul><ul><li>Reduced time to compose simulation to support the war fighter needs </li></ul></ul><ul><ul><li>Reduced long term cost </li></ul></ul><ul><li>Training and exercise needs </li></ul><ul><ul><li>Closer integration of M&S simulations with real systems which are using SOA </li></ul></ul>Long term cost savings and ability to deliver M&S services sooner to the war fighter with less effort
  10. 10. SOA Use of Discovery with M&S <ul><li>Within organization is promising </li></ul><ul><ul><li>No external Service Level Agreement (SLA) with some cost sharing </li></ul></ul><ul><ul><li>Useful for finding backup instances </li></ul></ul><ul><ul><li>Useful for implementing load sharing </li></ul></ul><ul><li>External organizations are less promising </li></ul><ul><ul><li>Much more difficult for federated simulations </li></ul></ul><ul><ul><li>For M&S, need to know more than just WSDL </li></ul></ul><ul><ul><ul><li>Documentation </li></ul></ul></ul><ul><ul><ul><ul><li>Design and semantics </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Simulation algorithms </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Granularity </li></ul></ul></ul></ul><ul><ul><ul><li>SLA </li></ul></ul></ul><ul><ul><ul><li>Cost sharing </li></ul></ul></ul><ul><ul><ul><li>Lack of trust </li></ul></ul></ul>Adhoc discovery not likely for M&S, but planned intra-organization discovery beneficial
  11. 11. Disadvantages of SOA <ul><li>Performance is an issue </li></ul><ul><ul><li>XML is verbose </li></ul></ul><ul><ul><li>Possible problems with latency, increased computation requirements, and communication overhead </li></ul></ul><ul><ul><li>No inherent priority mechanisms for SOA messages </li></ul></ul><ul><ul><li>10,000s of entities simultaneously messaging impacts performance </li></ul></ul><ul><li>Large investment in federates using legacy middleware </li></ul><ul><li>SOA infrastructure of services (e.g., time) not established </li></ul>Existing investment in current middleware solutions and limited funding for new solutions will likely slow the adoption of SOA
  12. 12. Governance Issues (systinet) <ul><li>Federates (i.e., services) combine together to deliver simulation functionality </li></ul><ul><ul><li>Many independent federates that can each impact the simulation </li></ul></ul><ul><ul><li>What happens when a service is changed? </li></ul></ul><ul><ul><li>How is it validated and verified (V&V)? </li></ul></ul><ul><li>Federation needs to gain trust with supplier </li></ul><ul><ul><li>No trust = no reuse </li></ul></ul><ul><li>Requires </li></ul><ul><ul><li>Policies, lifecycle processes and metadata (more than simple “card catalog metadata”) </li></ul></ul><ul><ul><li>Tools, standards and metrics </li></ul></ul><ul><ul><li>Explicit and accepted governance structure </li></ul></ul><ul><ul><li>Without governance infrastructure, reuse difficult </li></ul></ul>
  13. 13. Types of Metadata <ul><li>Describes individual resources (datasets, simulations, services …) </li></ul><ul><li>Example: Modeling and Simulation Resource Repository catalog entries </li></ul><ul><li>Necessary for the discovery of resources </li></ul><ul><li>Resides in COI Metadata Catalogs </li></ul><ul><li>Based on the DoD Discovery Metadata Specification (DDMS) </li></ul><ul><li>Focus of the M&S COI Metadata Focus Group </li></ul><ul><li>Describes the semantics and syntax for types of resources </li></ul><ul><li>Examples: XML schemas, data models, etc. </li></ul><ul><li>Necessary for the understanding of resources </li></ul><ul><li>Resides in the DoD Metadata Registry </li></ul><ul><li>Typically defined in XML, but not limited </li></ul><ul><li>Necessary to facilitate the work of the M&S COI Mediation Focus Group </li></ul>Metadata Resource Metadata Structure Metadata
  14. 14. Multiple Levels of V&V Required <ul><li>Testing of each component </li></ul><ul><ul><li>Does this node (database, consumer console, service provider) perform its function properly (as expected and according to specifications)? </li></ul></ul><ul><li>Testing services and transport components working together as different subnets </li></ul><ul><ul><li>Do this/these services work in an integrated and consistent fashion on the network as expected? </li></ul></ul><ul><li>Testing each system’s use of the network </li></ul><ul><ul><li>Does this network architecture have bottlenecks and what is the maximum throughput it can handle? </li></ul></ul><ul><ul><li>What is the network performance? </li></ul></ul><ul><li>Testing the end-to-end suite of systems over the network </li></ul>Reference: Flournoy, Doug; Lee, Elizabeth; Mikula, Rob; “ Testing Net-Centric Systems of Systems: Applying Lessons Learned from Distributed Simulation ”, NDIA Systems Engineering Conference, October 26, 2005.
  15. 15. <ul><li>Challenge quantifying investment from a business perspective </li></ul><ul><ul><li>Capacity/infrastructure planning </li></ul></ul><ul><ul><li>Investment </li></ul></ul><ul><ul><ul><li>Who pays </li></ul></ul></ul><ul><ul><ul><li>Incentive to invest </li></ul></ul></ul><ul><ul><li>How are simulation usage costs recovered </li></ul></ul><ul><ul><li>Current DoD business model of contractor based simulations </li></ul></ul><ul><ul><li>Value of organizational agility </li></ul></ul><ul><li>Savings </li></ul><ul><ul><li>Integration costs </li></ul></ul><ul><ul><ul><li>Reduced costs to set up exercises </li></ul></ul></ul><ul><ul><li>Opportunities for increased backup and capacity </li></ul></ul><ul><ul><li>Solving tomorrow’s unforeseen problems </li></ul></ul>M&S SOA Business Case Factors
  16. 16. Financial Criteria for M&S SOA (Notional)
  17. 17. SOA and Middleware <ul><li>Migrate towards standardized SOA for federated simulations </li></ul><ul><ul><li>Interfacing with an existing proprietary HLA Run Time Infrastructure (RTI) </li></ul></ul><ul><ul><li>Current impediment to reuse: different HLA-RTIs are not compatible </li></ul></ul><ul><ul><li>Advantageous to standardize protocol “on the wire” </li></ul></ul><ul><ul><ul><li>Use SOA on the wire </li></ul></ul></ul><ul><ul><ul><li>Solves compatibility problem of RTI </li></ul></ul></ul><ul><ul><ul><li>Adaptors could communicate with legacy RTI </li></ul></ul></ul><ul><ul><li>Potential problems </li></ul></ul><ul><ul><ul><li>Performance more challenging than with legacy middleware </li></ul></ul></ul><ul><ul><ul><li>Distributed time management difficult </li></ul></ul></ul>
  18. 18. Current/Proposed SOA Architectures for Federated Simulations
  19. 19. Use of Open Source and Reusable Infrastructure <ul><li>Without data rights, cost/benefit of reuse won’t be fully realized </li></ul><ul><li>Gov’t funded, non-proprietary simulations should be open source </li></ul><ul><ul><li>Example: reusable simulation (gaming) infrastructure </li></ul></ul><ul><ul><ul><li>Visual simulations quickly available at low cost </li></ul></ul></ul><ul><ul><ul><li>Only differentiating content needs to be acquired </li></ul></ul></ul>Full benefit of reuse won’t be possible without data rights
  20. 20. Use Discovery to Find Models <ul><li>Discovery of existing physics models and simulations through multiple layers of metadata </li></ul><ul><li>Open source physics based models </li></ul><ul><ul><li>Potentially available as services </li></ul></ul><ul><li>Potentially easier repository submission process </li></ul><ul><li>Exemplar in NASA data reuse </li></ul>
  21. 21. Reuse of Data <ul><li>Discover reuse data through SOA metadata </li></ul><ul><ul><li>Reuse of data from simulations </li></ul></ul><ul><ul><li>Reuse of real world data for modeling and simulations </li></ul></ul><ul><ul><ul><li>Establish repositories of exercise data for M&S community </li></ul></ul></ul><ul><li>Issues </li></ul><ul><ul><li>Need to know (classification) </li></ul></ul><ul><ul><li>Authoritative and accredited data </li></ul></ul><ul><ul><li>Business model </li></ul></ul><ul><ul><ul><li>Who pays? </li></ul></ul></ul><ul><ul><ul><li>How’s cost recovered? </li></ul></ul></ul>Data is exceptionally valuable for reuse, but business model is not clear
  22. 22. SOA Adoption Challenge <ul><li>Significant business model inertia to overcome </li></ul><ul><ul><li>Lack of incentive for reuse </li></ul></ul><ul><li>Lack of data rights may prevent realizing full reuse </li></ul><ul><li>Complex organization structures </li></ul><ul><ul><li>Relying on bottoms up adoption of SOA </li></ul></ul><ul><ul><li>Limited funding for change </li></ul></ul><ul><ul><li>Each program does their own funding of M&S </li></ul></ul><ul><li>SOA </li></ul><ul><ul><li>New technology to M&S COI </li></ul></ul><ul><ul><li>Global Information Grid evolving </li></ul></ul>The challenge is the business model, but there are significant commercial and DoD forces pushing the M&S community towards SOA adoption
  23. 23. Next Steps <ul><li>Obtain feedback from SOA community </li></ul><ul><li>Continue research and development of SOA ideas </li></ul><ul><li>Continue evolution/analysis of ideas presented in slides </li></ul><ul><ul><li>Correlate with ongoing DoD community M&S gap analysis </li></ul></ul><ul><ul><li>Provide recommendations </li></ul></ul><ul><li>Continue research </li></ul><ul><ul><li>Commercial industry </li></ul></ul><ul><ul><li>Tools vendors </li></ul></ul><ul><ul><li>DoD community </li></ul></ul><ul><li>Get feedback from open source community </li></ul>