This presentation at ITEC 2011, explain how to cohabitate in a single architecture the DDS and HLA standards in order to provide real time distributed simulation in Net-Centric applications.
Developing Simulation & Training Solutions With Cots
How To Develop True Distributed Real Time Simulations
1. How to Develop True Distributed Real Time Simulations? Mixing IEEE HLA and OMG DDS standards ITEC 2011 Jose M. Lopez-Rodriguez NADS (Nextel Aerospace, Defense & Security)
2.
3.
4.
5. Towards massive distributed Simulation The Navy identified networked trainers as a key requirement in future training systems . Networking capability exists in many simulators, but frequently the capability is cumbersome to set up and difficult to use, particularly when participants are not collocated . In addition, the speed is not yet available to support the requirements for real time simulation across distributed networks . There are work-arounds, but they do not currently support full, real time simulations. The ability to easily and seamlessly link multiple training devices into the same training scenario will greatly enhance the quality and effectiveness of the training. […] Effective networking of simulators will require a common architecture and industry wide standards . Over the years, the High Level Architecture has provided the foundation for this standard, but going forward these standards will need to expand to accommodate new capabilities and new participants . The NASMP needs normalized, consistent architecture and a well articulated business case to justify the investment in the NASMP. (*) Extracted from NTSA market survey : Training 2015: Requirements - Trends - Forecasts for the Decade Ahead. Is HLA enough?
6.
7.
8.
9.
10.
11.
12.
13.
14. WEAPON1 WIU OTHER SENSORS IOS PERISC. SONAR2 CONSOLES SYSTEM1 ACOUSTICAL ENVIRONM NAV SENSORS SONAR1 WEAPON2 ACOUSTIC GENERATOR WEAPON3 SYSTEM 1 SEABED ENVIRONM EM ENVIRONM VOICE COMMS IMAGE GENERATOR RECORDER TACTICAL ENVIRONM SYSTEM 2 Migrating to an Open Distributed Simulation Architecture RT Simulation Middleware (HLA & DDS compliant)
15. WEAPON1 WIU OTHER SENSORS IOS PERISC. SONAR2 CONSOLES SYSTEM1 ACOUSTICAL ENVIRONM NAV SENSORS SONAR1 WEAPON2 ACOUSTIC GENERATOR WEAPON3 SYSTEM 1 SEABED ENVIRONM EM ENVIRONM VOICE COMMS IMAGE GENERATOR RECORDER TACTICAL ENVIRONM SYSTEM 2 Some advantages of an Open Simulation Architecture DDS DDS DDS DDS DDS DDS DDS DDS HLA HLA HLA HLA HLA HLA Concept of HLA Federation applied to the Internal Simulation Architecture. Make easy the System level Design. Rapid design and development based on Repositories and COTS. Less risky and more cost-effective integration and testing. Saving costs and speed up time to market up to 50% RT Simulation Middleware (NCWare)
16. The Simulator as an Asset in a Net-Centric Environments DDS Network HLA Network Federate 2 Federate 3 NCWare RTI HLA SIMULATOR 2 SIMULATOR N Simulation Module 1 Simulation Module 2 Federate 1 DDS HLA DDS DDS SIMULADOR 1 NCWare SIM NCWare Gateway SIMWARE C4I SYSTEM DDS DDS NCWare Information System 1 SQL ODBC Sensor APP DDS NCWare SENSOR C4I SYSTEM WS / SOAP Information System N Information System i NCWare C4I SYSTEM MIP DM MIP DM LEGACY DM HLA
17. We offer a complete portfolio of solutions in compliance to former paradigm… OMG DDS v.1.2 / OMG DDSI / RTPS v.2.1 HLA IEEE 1516
18.
19. Interoperating DDS and HLA systems HLA federate RTI HLA HLA Federation DDS Domain HLA federate NCWare RTI HLA SOM DDS model HLA federate RTI HLA HLA Domain Gateway NCWare Sim
21. Interoperability btw Simulation and C4I in the SP Army AMPS COAAAS SMCM (SP COP) SI-XML SP Army C4I System SI-XML BMS TALOS DDS DDS DDS DDS DDS NATO C2 systems Air System Link - 16 COAAAS ICC TDL-16 ICC TDL-16 TDL-16 TDL-16 ICC ICC NVG NVG NFFI NFFI MIP B3 MIP B2 MIP B3 MIP B2 NFFI Live (embedded) Sim DDS VirtualSimulators Constructive Simulators HLA DDS Gateway DDS HLA HLA
22. Interoperability Real systems & Simulators Blend QoS COTS Open Architecture DDS HLA Full lifecycle development tools Real-Time Automation High Level Design
23. For more information… Jose M Lopez-Rodriguez VP, Business Development Director http://www.nads.es [email_address]
Notes de l'éditeur
You can do this in two different ways: Using NCWare RTI. In this case you do not have to do any gateway, you only should be sure that there is a compatibility btw the SOM and the DDS data model. This approach is valid if the mapping btw the HLA model and the DDS topics is straightforward. Or you can develop a Gateway. Using NCWare Sim and its associated Modeller tool you can design a gw btw the HLA and DDS domains. This approach is more flexible than the first one because you can define transformations btw the data models in the Modeller. Then you do not need to have the same data model in the two domains. In both cases, the HLA federate source code should not be modified.