1. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM-SUIT Final User Forum

2. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM-SUIT Benefits for ANSPs

3. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM and Business Trajectory During the planning phase the SBT could be changed taking into account the ANSP declared capacity During the execution phase (see scenario 1): –the RBT will be authorised by ANSP –the RBT will be updated by AOC/aircraft following co-ordination with the ANSP (currently simulated via constraints) –the ANSP will analyse the Predicted Trajectory in order to discover potential unexpected problems (e.g. temporary segregated areas)

4. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Impact on ATCOs Main changes compared to some of today’s working practices include the following: –In managed airspace separation, responsibility may be delegated from Air Traffic Controller to the Flight Crew in accordance with pre-defined rules (ATM-4 Level emulation – Target Scenario). –Departure and Arrival queues will be generated by queuing systems and will be optimised by Air Traffic Controllers and/or Flight Crew (e.g. AMAN sequencing, Scenarios 9.x / 1.x).

5. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Coordination and Transfer All air traffic services units and ATM partners have access to the applicable trajectories of each flight; –Flights are able to cross boundaries at any point rather than being restricted to predefined transfer points. Decision-making aids are able to operate with trajectories and prediction horizons that are not constrained by unit boundaries and data availability; –This enables more flexible transfer of control and results in minimum or no disruption to the trajectory when crossing boundaries. It is envisaged that no message based co-ordination will be required in this environment; –change proposals are applied directly on the shared RBT; –coordination acceptance can be assumed on the basis that the proposal (or counter-proposal) is known to be conflict free.

6. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Surveillance Surveillance data availability provides common situational awareness across the ATM network as well as supporting a range of collaborative processes (Scenarios 6.x). The system provides Surveillance information to the interested stakeholders through SWIM and displays them on a frontend (GIS HMI); –Surveillance information of sectors outside one’s surveillance coverage can be used to improve surrounding traffic information coverage. It is possible to configure rich and flexible filters (e.g. geographical area, FL bands, ModeS, Aircraft Operator etc) when subscribing to surveillance data.

7. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome From Design to Implementation Information from different sectors or Geographical Areas can be showed on a single screen (see SWIMs IOP activities with FAA)

8. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM-SUIT Prototype Air France Feedback Giuseppe Pillirone, Air France Ion Berechet, Air France Consulting

9. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Advantages for Aircraft Operators Seamless operational control of the aircraft with collaboration capabilities with the flight crew and ANSPs across SWIM domains Transparent access to aircraft Flight Object regardless of SWIM domain Shared surveillance provides the ability to track aircraft situation Allows operator to maintain flown trajectory closer to Reference Business Trajectory Symmetrical –Would apply to a US airline aircraft operating in Europe AID domain: Smoother access to the most up-to-date EAD information will allow to produce more optimized "flight plans"

10. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome IT-specific aspects Facilitates "Enterprise Architecture" approach –The Data Domains of the SwimBox define standardized "business objects" that contribute in EA / SOA approaches undertaken internally –Those very good data models can be adopted internally as well Lessons learnt: –Introducing "external" components in a company's IT operations needs special attention (e.g. network-level security, interdependece with internal frameworks and platforms, existing IT-ops tooling, …) –We would recommend to work on these aspects in further Sesar activities. Sharing deployment practices between SWIM partners having similar environments, can speed up deployment. Airlines will follow with attention the works on air-ground link, for its potential usage for non-ATC purposes (e.g. onboard internet access)

11. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM: Accelerating A-CDM Nathan Day Rockshore-NATS Business Development Director

12. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Airport CDM & the “legacy anchor” A large proportion of the technology effort needed to implement Airport CDM comes from integration to legacy systems. The A-CDM Platform (shadow mode) at LHR is integrated to: Electronic strip system Airport schedule system Arrival Manager AFTN (CFMU) A-SMGCS All these interfaces deal with flight information in a different way. They provide implementations with a “legacy anchor”.

13. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM & A-CDM The flow of Flight Objects across a common network removes the need for multiple, bespoke technical interfaces. This frees up valuable resources (time and money) to focus on what really matters: people & procedures. The simplification of the technical landscape and the focus on people and procedures de-risks implementations. Individual implementations have: A greater probability of success A shorter implementation timescale

14. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome The bigger picture: network benefits If individual A-CDM implementations are successful, the march toward network level benefits speeds up. EUROCONTROL ‘magic number’ is 42 airports 42 airports give an estimated reduction of delay between 18-23%* * EUROCONTROL EXPERIMENTAL CENTRE Airport CDM Network Impact Assessment EEC Note No. 10-009

15. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM benefits Paolo Sordi SEA Milan Airports Airport Processes Development and Supervision Manager

16. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM-less ATFCM (CFMU) Airline (FDP) MXP AIRPORT Airport AODB receives information after several steps

17. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM-ness SWIM-SUIT MXP AIRPORT Airport AODB collaborates with Partners

18. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Remarks POSITIVE FACTS Airport information system receives real-time updates from all the Contributors and feeds in real time Partners with its own information set; Actors involved in SWIM-SUIT collaborate during the whole “flight-life-cicle”; All Actors have real time augmented situation awareness; The Swim environment reduces the number of system interfaces needed.

19. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Remarks TO BE IMPLEMENTED SWIM SUIT is a sort of CUTE (Common User Terminal Equipment) enabling Actors DCS/OCS/DB to be accessed from a common system but there is the strong need to overcome differences in “language” among operators (that are one of the causes of the communication’s problems efficiently solved by SWIM- SUIT) and define an “Air Transport World Common Language” combining ICAO and IATA terminology.

20. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Remarks QUESTION FOR THE AUDIENCE WHERE IS E.A.S.A.? DO YOU THINK THAT SHOULD HAVE BEEN INVOLVED IN SWIM-SUIT?

21. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome CFMU and SWIM Andy Simpson EUROCONTROL CFMU/ENGD

22. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 15/04/2010 CFMU Architecture Today Authentication Single Sign-On Authorisation Confidentiality Overload Protection User Access Segregation Firewalls, DMZ Service Level Objectives SLA differentiation Service Monitoring Service Measuring Service Reporting User model Access Request Processes User provisioning Central repository Farm Node architecture Site contingency NOP Portal Website Dynamic Content User Tailored Content

23. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Towards SWIM Service Layer Identity Management High Availability Scalability Infrastructure Service Level Management Integration Layer B2B Services NOP Portal Access Management Transaction Logging & Replay Consumes and integrates services from the SWIM network Offers services to the SWIM network Integrated picture to end user

24. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome CFMU Lessons Learned - Towards SWIM AIM: high quality operational data is a key SWIM enabler. SWIMSUIT needed data from CFMU’s ENV and EAD systems. The CFMU ADR system (ENV + EAD) will likely be key to the success of SWIM. Standardisation: Component interface standardisation enables interoperability e.g. standard security, messaging, caching components address flexibility and multi sourcing concerns. Content: Standard exchange business models enable communication via a common vocabulary. Our experience with a SOA/SOAP/REST deployment suggests a business agnostic middleware layer may reduce systems update versioning issues. - Principle of separation of concerns Distributed Data Store: We suggest that the reliability of this approach is validated under adverse conditions, as we believe this is challenging. Access & Identity Management: Deployment and operation can be slow and costly in distributed environments c.f. inside the enterprise..

25. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM in China ATMB

26. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome The Future Air Traffic Management System of China 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

27. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM Research Team Members include: –General ATMB –7 Regional ATMBs –Technical Center of ATMB –3 Companies –1 Institution –1 University 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

28. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome Implementation Plan 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

29. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome User’s Benefits in China SWIM B E C D A Enhance safety Increase airspace capacity and efficiency Improve Collaborative Decision Making Reduce cost and emission Promote quality of service 24-25 June 2010 SWIM-SUIT Final User Forum, Rome

30. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome ATC Airlines Airports Passengers User’s Benefits in China Access to accurate flight information anytime, anywhere Optimize travel routes Reduce the waiting time Increase the right to know of the operation of flights Help approach tower controllers plan flights taking off and landing sequence in advance to reduce airport congestion Help flight controllers realize air traffic flow management, reduce side effects caused by the delay Improve flight regularity Participate in making decisions for flights taking off and landing Enhance the predictability of the flight operation of Airlines Reduce delays, reduce costs Better allocation of airport resources Provide better services to customers Optimize allocation of parking bays Increase throughput of passengers 24-25 June 2010SWIM-SUIT Final User Forum, Rome

31. 24-25 June 2010 SWIM-SUIT Final User Forum, Rome SWIM-SUIT Final User Forum