Nogesi project represents a milestone for proposed LSA architecture. Know the challenges and solutions for this project and how it has been a real proof of concept for SISO LSA.
4. Nogesi Challenges
•
•
•
•
•
Integration of legacy systems
and COTS
Interoperability between
simulated and operational
systems
Development and maintenance
of Simulation assets using MDA
(Model Driven Architecture)
Deployment of simulation assets
as services into an HLA
federation
HLA full interoperability
including ownership transfer
2013 Fall SIW
5. Nogesi needs of integration
•
Integration of legacy systems, HLA and DIS-based COTS
HLA
VBS2
FAC of INDRA
DIS
VRForces
2013 Fall SIW
6. WHAT IS DIFFERENT IN NOGESI SOLUTION
• Traditional approach
• Implement a simulation engineering methodology, like FEDEP
/ DSEEP
• For the deployment
• Wrapper or middleware that provides an abstraction of
different simulation protocols like HLA, DIS or TENA
• Gateways and bridges between the different types of
simulators
• Advanced simulation services like execution, ownership or time
management are unavailable
2013 Fall SIW
7. The architecture as THE key point
• Main innovations in NOGESI are not in the development process but
in the simulation technical architecture.
• NOGESI is based on LSA, a pure distributed data-centric architecture
2013 Fall SIW
8. ARCHITECTURE OF THE SOLUTION
• Use of DDS in conjunction with HLA and DIS standards
• NOGESI follows LSA architectural proposal
2013 Fall SIW
10. Nogesi as LSA milestone
NOGESI project has been the test bed and proof of concept of
LSA architecture
2013 Fall SIW
NOGESI
11. LSA Layers Overview
Simulators; new and existing (included legacy)
Current simulation architectures; HLA, DIS, TENA
Arch specific APIs
Gateways
HLA Services
Simulators
HLA
DDS
DIS
DDS
Simulation Services
TENA
DDS
Common interface
Data-centric Middleware: OMG DDSI
Open Wire protocol
2013 Fall SIW
New Services
DDS simulators
12. LSA-Nogesi overlapping: COTS and legacy
Simulators; new and existing (included legacy)
Current simulation architectures; HLA, DIS, TENA
ArchFAC of INDRA
specific APIs
DIS data-bridge
Simulators
HLA
DDS
VBS2
Gateways
DIS
DDS
VRForces
HLA Services
HLA data-bridge
Simulation Services
TENA
DDS
Common interface
Data-centric Middleware: OMG DDSI
Open Wire protocol
2013 Fall SIW
New Services
DDS simulators
13. LSA-Nogesi overlapping: HLA over DDS
Simulators; new and existing (included legacy)
Current simulation architectures; HLA, DIS, TENA
Arch specific APIs
FAC of INDRA
Gateways
VBS2
Simulators
HLA
DDS
DIS
DDS
TENA
DDS
HLA over DDS
VRForces
HLA Services
Simulation Services
Common interface
Data-centric Middleware: OMG DDSI
Open Wire protocol
2013 Fall SIW
New Services
DDS simulators
14. LSA-Nogesi overlapping: DDS simulators and services
Simulators; new and existing (included legacy)
Current simulation architectures; HLA, DIS, TENA
Arch specific APIs
Gateways
HLA Services
Simulators
HLA
DDS
DIS
DDS
Simulation Services
TENA
DDS
Common interface
Data-centric Middleware: OMG DDSI
Open Wire protocol
2013 Fall SIW
New Services
DDS simulators
16. On the Core: eHost for Simulation management
Configuration file
- <config>
<EJEC nid="2" id="3" name="EJEC" HlaFed="Aislado"
HlaSom="Som.xml" SchedFrec="25" HTime="5" GTime="3"
TTime="0" UTime="3" NotIni="no" NotFin="no" NotCierre="no"
Critico="si" NotGrab="si" />
- <EHOST4 nid="2" id="4" name="MOTOR1" SchedSecuencial="si"
NotIni="si" NotFin="si" NotCierre="no" Critico="si" NotGrab="si">
<Mod0 nid="2" id="16" name="Modulo_ModCIRCLE"
type="Modulo_ModCIRCLE" SchedFrec="50" SchedOrden="0"
SchedPrio="1" SchedOffset="0" NotIni="no" NotDisc="no"
NotEstab="no" NotFin="si" NotCierre="no" Critico="si" NotGrab="si"
/>
</EHOST4>
</config>
- <!--
eHost
Simulation
engine
Scheduler
ACS
Simulation
engine
Scheduler: Is an advanced scheduler for controlling the real time clock and the
state machine. It coordinates and balances many Simulation Engines that are in
different nodes.
Simulation Engines: Are the simulation engines, manage the Simulation modules
in each simulation node.
2013 Fall SIW
17. Control of NOGESI: ACS
ACS—Application to Control SimWare simulations, is a GUI that allows to
manage SimWare state machine and simulation assets’ parameters during
execution
2013 Fall SIW
20. Key point 1: Reusability
• Nogesi allows to reuse simulation models and services
These models can be deployed in any scenario
Models can be changed by editing a file
• Nogesi can incorporate already existing simulators and
legacy simulators
• Any COTS using HLA or DIS can be incorporated
2013 Fall SIW
21. Key point 2: Extensibility
• Nogesi can be extended to include new COTS not tested or
included on the original project
• Already tested with STAGE 6.1.1 and 6.2 and Vega Prime
2013 Fall SIW
22. Key point 3: Cost savings
• Nogesi allow a clear saving in costs by:
Reusing previous existing models
Leaving existing HLA and DIS
federations “as is”
Incorporating already purchased
COTS
Adding legacy elements/simulators
Connecting different HLA vendors
Allowing new COTS not tested before
2013 Fall SIW
23. NOGESI as a simulation
black-box
2013 Fall SIW
24. Nogesi as a simulation black box
• Can be deployed anywhere
• Can connect to any HLA or DIS compatible COTS
• Can be fully distributed
NOGESI
ANY COTS
2013 Fall SIW
27. Next Challenges
• Extension of Nogesi has new challenges
Wan interconnection using DDS: Qos file and Qos patterns
Compensation of network latencies
Network requirements and limitations: dedicated network
vs general network
Security requirements: What security is really needed?
2013 Fall SIW
29. Please address any questions about this presentation to:
José Ramón Martínez Salio
Technical Presales Director
jrmartinez@nads.es
@NADS_news
/NEXTELADS
jrmses
Nextel Aerospace