Improving the Systems Engineering of Live- Virtual-Constructive (LVC) Simulations This document has been cleared for public release (Distribution A) James E. Coolahan, Ph.D. Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD 20723-6099 240-228-5155 [email protected]NDIA Systems Engineering Conference San Diego, CA October 24-27, 2011 Gary W. Allen, Ph.D. Joint Training Integration and Evaluation Center 12000 Research Parkway, Suite 300 Orlando, FL 32826 407-208-5607 [email protected]
27
Embed
Improving the Systems Engineering of Live-Virtual ... · PDF fileLive- Virtual-Constructive (LVC) Simulations ... LVC Architecture Convergence ... •Utilization of social networking
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Improving the Systems Engineering of Live- Virtual-Constructive (LVC)
Simulations
This document has been cleared for public release (Distribution A)
Behavior (including organizational and individual)
Logistics
Event (testing, training, analysis, etc.) results
Prioritized continuing work as follows:
Priority 1: Manmade features and event results
Priority 2: Geospatial
Priority 3: Unit Order of Battle (UOB) and Plans / scenarios
Priority 4: Platform/weapons performance and behavior
Priority 5: Electronic Order of Battle (EOB)/network and logistics
12
13
3D Manmade Features
• Identified conforming format (X3D)
• Identified needed extensions
• Working with COI to implement and
integrate extensions within standard
• Publishing study results
0
2
4
6
8
10
12
14
Requirements
Haptics
Physics
Semantic Notes
Geospatial
CAD
Web
Mobile
Destruct
Compose
RW Pipeline
3D Advance
• Identified requirements based on previous
research/workshops
• Matched requirements to capabilities in the
formats previously identified
Event Logging
14
Federate
1
Federate
2 Logger
Interface
RTI
VV&A
AAR
Archive
Log
• Established set of design patterns from
existing log formats
• Identified weaknesses in existing formats
• Created draft format for HLA/DIS logging
• Working with community to identify any
missed use cases
• Incorporating additional community input
Improving the Use of Gateways and Bridges:
Gateway Challenges
Gateways provide the most widely used means of addressing
interoperability concerns in multi-architecture LVC environments
Despite the many documented success stories associated with
the use of gateways to facilitate LVC interoperability, there are
also some significant issues that impact technical, schedule, and
cost risk
Examples of known gateway issues include:
No central ―marketplace‖ of gateways
Gateways built for specific needs
Broad proliferation of gateways
Developer or integrator lock-in
15
Improving the Use of Gateways and Bridges:
Strategy Dimensions
Looking for the
―sweet spot‖
that addresses
the issues in a
timely fashion,
for reasonable
cost, enacts
positive change
that is long-
lasting, and has
a credible
business model
16
Educate
Enhance
Create
• Tutorials
• Classes
• Help Desk
• Machine-readable gateway
languages
• Architecture-neutral SDEM
representation
• Performance Benchmarks
• Fund existing & enhance
• Fund new
• New business models
Current
State
Educate
Enhance
Create
• Tutorials
• Classes
• Help Desk
• Machine-readable gateway
languages
• Architecture-neutral SDEM
representation
• Performance Benchmarks
• Fund existing & enhance
• Fund new
• New business models
Current
State
Selected the “Enhance” Strategy, along with
an element of the “Educate” Strategy
LVCAR-I Gateways Effort:
Completed Product Development Activities
Developed a Gateway Configuration Model that identifies an explicit set of gateway requirements, and discusses how the emerging gateway products and processes will address those requirements
Developed a Gateways Capability Description document, which formally delineates the various capabilities that individual gateways can offer to user programs, along with specific levels of implementation for each unique capability
Assessed the Architecture-Neutral Data Exchange Model (ANDEM), originally developed by the Joint Composable Object Model (JCOM) Program, to support Simulation Data Exchange Model (SDEM) mapping and/or translation in gateways
Developed a set of Gateway Performance Benchmarks (GPBs) to identify specific gateway performance measures, along with use cases that describe how and where these measures should be applied
17
LVCAR-I Gateways Effort:
FY11-Funded Product Development Activities
Development of a common Gateway Description Language (GDL), in a machine-readable format/syntax, for describing both user gateway requirements and the capabilities that individual gateways can offer
Supports user discovery of needed gateway capabilities
Development of a common SDEM Mapping Language (SML) to formalize format and syntax of mappings between different SDEMs
Reduces number of required mappings, and supports reuse of mapping data
Development of a repository for GDL-based gateway descriptions. Incorporate applicable search and requirements-to-capabilities matching algorithms
Development of tools for GDL and SML file creation/editing
Development of SML Translators for selected gateways
JBUS, GWB are likely choices
Socialization of draft GPBs with gateway developer organizations, incorporation of feedback, and preparation of formal specification
Development of a Gateways tutorial
18
LVC Architecture Convergence –
Perhaps a Bridge Too Far
19
HLA Federate
TENA Application
RTI BGCSI
Extensions
. Middle. ware
CSI
StandardAPI
DIS Simulation
DISPDUs
. GatewaytoDIS
CSI
Network
CTIA Simulation
Extensions
. Middle. ware
CSI
StandardAPI
An Envisioned Converged Architecture
LVC Architecture Convergence –
Perhaps a Bridge Too Far
20
Return on Investment (ROI) Estimate
Better ROI is provided through a slower, multi-year
development process that gradually builds confidence
in the new approach.
Investigating the Use of Service-Oriented
Architectures (SOAs) in LVC Simulations
Benefits of Employing SOA in LVC Distributed Simulations
Positive aspects to leveraging multiple contributors to the LVC simulation
Addresses a systemic need for agility in deployment and execution
Aids implementation through use of well-defined encapsulation
Designed for composability and reuse of distributed simulation components
Allows use of more business models, such as Software-as-a-Service (SaaS)
Barriers to Employing SOA in LVC Distributed Simulations
Uncooperative competing factions can stall governance agreements
Budget, time, and scope constraints on project
Actual or perceived lack of need for deployment and execution flexibility
Actual or perceived performance requirements
Existing LVC simulation infrastructure is extremely brittle, limiting upgrade
Difficulty in acceptance within M&S community
21
Applying SOAs in LVC Simulations:
SOA Pilot Effort (MITRE)
22
Investigating ―LVC Futures‖ – Five Scenario
Vignettes and Nine Technology Categories
23
“Sequoia Ring” Humanitarian Aid, Stability in response to natural disaster.
“Relay Exchange” Continued long-term COIN / Stability operation in fragile state.
“Urgent Extreme” Conventional small war to restore overthrown democracy.
“Cave Dive” Intervention into civil war that soon may spill over border into allied country.
“Electronic Egret” Cyber attack by near-peer nation against joint effort with allied nation.
Implementation
• Mobile computing and augmented reality
• Ubiquitous surveillance and automated
reasoning
• Event-model driven architectures
• Self-healing / self-managing systems
• M&S social graph
Socialization and adaptation
• Crowd-sourcing
• Mashup software and FIST (Fast,
Inexpensive, Simple, Tiny)
• Cloud encapsulation
• Everything is a game
The Way Ahead
Standards
The DMAO is expected to become an IEEE standard
The FEAT is expected to become a SISO standard
The FEAT tool to aid users in implementing the FEAT is expected to become a complete open-source product
Lessons learned in the exploration of alternative business models will be documented
Common data storage format advances will be solidified in several areas, including 3D data formats and event logging
Gateways
Users will have automated tools at their disposal to aid in discovering appropriate gateways for specific uses
Common components for SDEM translation will be completed
Building on the EMBR portal, an LVC asset reuse repository will be available to support LVC gateway discovery and reuse
24
Acknowledgments JHU/APL:
Bob Lutz
Randy Saunders
Katherine L. Morse
Bill Riggs
Ryan Brunton
David Drake
John Schloman
Jonathan Labin
Joseph Kovalchik
Shon Vick
Ronda Syring
Terri Morgan
Mike Kane
Ian Martins
Ric Roca
AEgis Technologies
• Dannie Cutts • Jake Borah
25
Trideum
• Kurt Lessmann
• John Rutledge
• Michael O’Connor
• Dennis Bergin
• Stacy Van Winkle
SimVentions
• Paul Gustavson
• Hart Rutherford
• Jonathan Belcher
• Bertram Chase
MITRE
• Frank Carr
• Anita Zabek
• Richard Crutchfield
• Bill Beebe
• Roy Scrudder
(ARL:UT)
• Mikel Petty (UAH)
• Wes Milks (LMCO)
• Bob Murray (Boeing)
• Ed Powell (SAIC)
Other Organizations with Representatives
at LVCAR-I Workshops (selected):
• DISA
• SPAWAR
• USJFCOM
• PEO STRI
• M&S CO
• NMSO
• AMSO
• UK MOD
• Army RDECOM
• IDA
• CNA
• MSIAC
• CAE USA
• Saab
• CACI
• Northrop Grumman
• Raytheon
References
―Live-Virtual-Constructive (LVC) Architecture Roadmap Implementation Workshop,‖ 2010 Spring SIW
―Live Virtual Constructive (LVC) Common Capabilities,‖ 2010 I/ITSEC
―Emerging Solutions for LVC Asset Reuse,‖ 2011 Spring SIW
―LVC Common Gateways and Bridges,‖ 2010 I/ITSEC
―Gateway Concepts for Enhanced LVC Interoperability,‖ 2011 Spring SIW
―LVCAR Enhancements for Selecting Gateways,‖ 2011 Spring SIW
―LVCAR Enhancements for Using Gateways,‖ 2011 Spring SIW