1 Common Modular Simulator (CMS) : a PHARE system integration environment by J-R. Velten, CMS Project Leader CENA - ESV C ENTRE D'ETUDES DE LA NAVIGATION AERIENNE

2 Principles for setting up the CMS project l The CMS objectives : l 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. l Improve the flexibility and adaptability of real-time simulators used for experimentation. l Permit closer collaboration between member establishments and cross fertilisation of research ideas through the exchange of software components.

3 Principles for setting up the CMS project l The CMS Approach : l Define a common open/modular architecture based on an active client/server model l Decompose an ATM system into a set of loosely coupled clients and servers l Specify a common data model and a set of commonly agreed Application Programming Interfaces (APIs) l Adapt existing components to these APIs l Develop New components according to this foundation

4 Principles for setting up the CMS project

5

6 History of applying standards in PHARE l The CMS project missions : l Define a Common Simulation Environment l A set of commonly agreed APIs l An open/modular architecture, the use of which is encouraged l A set of Components, which can be used to improve existing simulators l Prototype this common environment (PARADISE) l Provide related support to other PHARE projects

7 History of applying standards in PHARE l PHASE 1 : Requirements l Agree on the ATM system decomposition l Identify the main CMS products : PARADISE, PREPCOT, LORAS, ASCOT l Collect the user requirements on the common data model and the standard APIs l The PHARE demonstrations : An incremental definition of the PHARE APIs l PD/1 : The technical integration l PD/2 : The functional integration l PD/3 : The operationnal integration

8 How are other European projects applying standards l GAAS : a DG 12 sponsored APAS action to define a Generic ATM architecture l PATIO : a DG7 sponsored 4 th FP project to develop an integration platform for advance tools integration l Da Vinci : a DG7 sponsored 4 th FP project on future Airport traffic management system l AVENUE : a DG7 sponsored 4 th FP project to develop a common ATM validation platform

9 Major lessons learnt l Standard APIs need to be functionally validated l APIs semantic to be carefully defined l Need for a common Data Preparation l APIs to be delivered with Test data set l System configuration problems : OS, compilers,... l proper APIs Configuration management is essential

10 Is a worldwide standard feasible ? l PHARE has demonstrated the technical feasibility l Official Standard or De facto Standard ? l OMG is interested by the European experience

1 Common Modular Simulator (CMS) : a PHARE system integration environment by J-R. Velten, CMS Project Leader CENA - ESV next next next C ENTRE D'ETUDES DE LA NAVIGATION AERIENNE