OMG and Air Traffic Management Systems CARDAMOM: a new generation of OMG standard Middleware

1. OMG and Air Traffic Management SystemsCARDAMOM: a new generation of OMG standard Middleware OMG, 2003 November Presentation by Robert C. Brown Director Business Innovation AMS

2. Architectural Issues of ATM Systems • ATM systems deployed have different architectural features, although operationally very similar in performance and function • The future of Air Traffic calls for increases in capacity (x3 by 2020), efficiency (lower cost to those who fly, punctuality for the passenger), safety (x9 by 2020) • The airspace structures follow National Boundaries, resulted in fragmentation and inefficiencies • Interoperability is increasingly recognised as supporting future needs, including a shift in operating paradigm to reach the predicted needs • Work is underway at EU level to promulgate the Single European Sky Regulation that moves along the lines of meeting the future need of European Skies

3. OMG Standards are a solution • R&D projects by the EU such as Avenue and Gate to Gate, initiatives by EUROCONTROL such as OATA, initiatives by EUROCAE in WG 59 and 61 have identified CORBA middleware as the Distributed ATM Services socket into which ATM components may be plugged • Communication Services (Fixed and Mobile) provide for a seamless end to end transmission of Services

4. IoP aspects related to ATM • Interoperability is a functional attribute of a complex, articulated safety critical system • The Performance Review Committee of Eurocontrol has successfully tackled the issue of delays; flow management needs to be functionally tied into Flight Data Processing, into Arrival and Departure Management, into the Flight Management System and into the Air Operations Centre-IoP! • Interoperability granularity of the complex ATM system: FMS relates to FDP through data link. Interoperability in this instance branches out into a wide spectrum of communication systems and services

5. The ATM Challenge • The ATM Systems architect is posed with a challenge that goes beyond the technological, as the systems implemented according to such architecture will condition the modus operandi of Stakeholders, • ATM Systems Manufacturing Industries in Europe (among which are AMS and THALES ATM) intend to adopt an open architecture that hosts present legacy applications, incorporating innovative applications as they become progressively available, • The Companies are also working on a new generation of Middleware based on independent company approaches to an evolution of CORBA3, • Planned to become a Common Language for ATM domain modelling, including process and tools and to save 80% of the cost that would have to be sustained to reuse large distributed system components.

6. The ATM Business Case • By adopting the MDE approach, fully compliant with the OMG/MDA standard, the intrinsic complexity of the future ATM system will be reduced, improving the transparency between Operational Requirements and ATM system specifications through model weaving and transformation to expedite the industrial process that leads to the Development phase. • The Architectures we are working on will have these requirements in their baseline. Their complexity will be greater than anything deployed to date. Their level of automation will contribute to optimised use of the airspace, supporting 4D Trajectories from Gate to Gate, Free Flight, ASAS, all weather curved precision approaches, CDM • Investments will not be substantially different than present practices due to the reuse of applications and to the MDE approach. • Reluctance of Controllers to adopt the new ATM systems will be mitigated by such initial re-use.

7. CARDAMOM • AMS and THALES Companies have started the joint development of a new generation of Middleware for their large-scale software intensive, real time and fault tolerant distributed systems with Corba3 • In order to ensure large-scale dissemination and usage of this MIDDLEWARE, it has been agreed to distribute CARDAMOM through Open Source Scheme (OSS) • The eFDP/fi, currently under development by Thales and AMS for France and Italy, is based on CARDAMOM

8. Core Foundation Build Configuration and Plugging Open Container Code Generation XML Server Tools CCM Deployment Trace Pluggable Services COTS and/or OSS Life Cycle Naming Property Recording Fault Tolerance Event Persistence Load Balancing System Management DDS DCPS DDS DLRL Time & Clock Transaction CARDAMOM - Services

9. Common Development Organization DEVELOPMENT REFERENCE ENTERPRISE EDITION COMMUNITY EDITION Services & Solutions Provider OSS Consortium Commercial User Non Commercial User Cardamom - Proposed Organization • CARDAMOM has to satisfy conflicting constraints • Wide dissemination and marketing vs Controlled evolution • Open Source vs Industrial support • CARDAMOM solves the issue through a structured management as shown in the following

10. Cardamom - Start Up Roadmap • Interim releases, starting from V0, targeted as Open Source • 2004-Q1 : Finalisation of proper organisation, licensing condition, packaging and distribution for Community Version • 2004-Q3 : Finalisation of proper organisation, licensing condition, packaging and distribution for Enterprise Version