110 likes | 125 Views
C ENTRE D'ETUDES DE LA NAVIGATION AERIENNE. Common Modular Simulator (CMS) : a PHARE system integration environment. by J-R. Velten, CMS Project Leader CENA - ESV velten@cena.dgac.fr. 1. Principles for setting up the CMS project. The CMS objectives :
E N D
CENTRE D'ETUDES DE LA NAVIGATIONAERIENNE Common Modular Simulator (CMS) : a PHARE system integration environment by J-R. Velten, CMS Project Leader CENA - ESV velten@cena.dgac.fr 1
Principles for setting up the CMS project • The CMS objectives : • Provide a simulation and experimentation environment for new ATM concepts, in such a way that software components could be identified, produced by individual participants as required and exchanged between them. • Improve the flexibility and adaptability of real-time simulators used for experimentation. • Permit closer collaboration between member establishments and cross fertilisation of research ideas through the exchange of software components.
Principles for setting up the CMS project • The CMS Approach : • Define a common open/modular architecture based on an active client/server model • Decompose an ATM system into a set of loosely coupled clients and servers • Specify a common data model and a set of commonly agreed Application Programming Interfaces (APIs) • Adapt existing components to these APIs • Develop New components according to this foundation
History of applying standards in PHARE • The CMS project missions : • Define a Common Simulation Environment • A set of commonly agreed APIs • An open/modular architecture, the use of which is encouraged • A set of Components, which can be used to improve existing simulators • Prototype this common environment (PARADISE) • Provide related support to other PHARE projects
History of applying standards in PHARE • PHASE 1 : Requirements • Agree on the ATM system decomposition • Identify the main CMS products : PARADISE, PREPCOT, LORAS, ASCOT • Collect the user requirements on the common data model and the standard APIs • The PHARE demonstrations : An incremental definition of the PHARE APIs • PD/1 : The technical integration • PD/2 : The functional integration • PD/3 : The operationnal integration
How are other European projects applying standards • GAAS : a DG 12 sponsored APAS action to define a Generic ATM architecture • PATIO : a DG7 sponsored 4th FP project to develop an integration platform for advance tools integration • Da Vinci : a DG7 sponsored 4th FP project on future Airport traffic management system • AVENUE : a DG7 sponsored 4th FP project to develop a common ATM validation platform
Major lessons learnt • Standard APIs need to be functionally validated • APIs semantic to be carefully defined • Need for a common Data Preparation • APIs to be delivered with Test data set • System configuration problems : OS, compilers, ... • proper APIs Configuration management is essential
Is a worldwide standard feasible ? • PHARE has demonstrated the technical feasibility • Official Standard or De facto Standard ? • OMG is interested by the European experience
CENTRE D'ETUDES DE LA NAVIGATIONAERIENNE Common Modular Simulator (CMS) : a PHARE system integration environment by J-R. Velten, CMS Project Leader CENA - ESV velten@cena.dgac.fr next 1