• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Modeling And Simulation

Modeling And Simulation






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Modeling And Simulation Modeling And Simulation Presentation Transcript

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