SWIM-SUIT
Final User Forum
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
SWIM-SUIT Benefits
for ANSPs
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)
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).
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.
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.
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
From Design to Implementation
ATSU 1
ATSU 2
ATSU 3
A/C
ATSU 2
ATSU 1
ATSU 3
Stakeholders
24-25 June 2010
Information from
different sectors or
Geographical Areas can
be showed on a single
screen (see SWIMs IOP
activities with FAA)
SWIM
SWIM-SUIT Final User Forum, Rome
SWIM-SUIT Prototype
Air France Feedback
Giuseppe Pillirone, Air France
Ion Berechet, Air France Consulting
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"
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)
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
SWIM: Accelerating A-CDM
Nathan Day
Rockshore-NATS
Business Development Director
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”.
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
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
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
SWIM benefits
Paolo Sordi
SEA Milan Airports
Airport Processes Development and Supervision Manager
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
SWIM-less
Airline
ATFCM
(CFMU)
(FDP)
Airport AODB receives information after several steps
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
MXP
AIRPORT
SWIM-ness
SWIM-SUIT
Airport AODB
collaborates with
Partners
24-25 June 2010
MXP
AIRPORT
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.
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 SWIMSUIT) and define an “Air Transport World Common
Language” combining ICAO and IATA terminology.
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?
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
CFMU and SWIM
Andy Simpson
EUROCONTROL
CFMU/ENGD
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
CFMU Architecture Today
Military
Web Browser
NOD
Service Level Objectives
SLA differentiation
External tools
Service Monitoring
Service Measuring
Service Reporting
Policy
CHMI
Access Management
OTP
Server
Other
Proxy Server
Authentication
server
Server
REST Web
Services
NOP Portal
SOAP Web
Services
B2B Service – External Model
CFMU Integrated Services - Internal Model
Flight Planning
Services
AS
Services
Flow Mng
Services
Other
Services
Integration Layer
Business
Layer
User model
Access Request Processes
RPL
User provisioning
Central repository
IFPS
RCT
ANg1
ETFMS
IFPUV
AN3
SAFA
DWH
FTPS
Predict
ERS
AN3D
AFTN
15/04/2010
24-25 June 2010
ENV
SITA Network
SWIM-SUIT Final User Forum, Rome
CIR
SIMEX
Service Level Management
Transaction Logging &
Replay
NOP Portal Website
Dynamic Content
User Tailored Content
Identity Management
Authentication
Consumer
SingleApps
Sign-On
Authorisation
Confidentiality
Overload Protection
Service Layer
User Access
Segregation
Firewalls, DMZ
ANSP
High Availability, Scalability
Infrastructure
AO
Actors
Env Val
systems
Farm
Remedy
Node architecture
Site contingency
Centra
Towards SWIM
Access
Management
Service
Layer
Identity
Management
NOP
Portal
Transaction
Logging & Replay
B2B
Services
Integration Layer
Integrated picture to end user
Positioni
ng
Conflict
Mng
Flight
Planning
Cap
Balanc.
24-25 June 2010
High Availability
Scalability
Infrastructure
Offers services to the
SWIM network
<wsdl:binding name ="submitSoapBinding "
type="impl:IFPUV">
<wsdlsoap:binding style ="rpc"
transport ="http://schemas .xmlsoap.org/
soap/http"/>
<wsdl:operation name ="submit">
<wsdlsoap :operation soapAction =""/>
<wsdl:input name ="submitRequest ">
< wsdlsoap:body
encodingStyle
="http://
Flight
Weather
Guidance
schemas.xmlsoap .org/soap/encoding/"
Dep.
Mng
namespace
="http://cfmu" use="encoded"/>
</wsdl:input>
Arr.Mng
<wsdl:output
name ="submitResponse ">
< wsdlsoap:body
SWIM Network
encodingStyle ="http://
Surveilla
schemas.xmlsoap
.org/soap/encoding/"
nce
namespace ="http://cfmu" use="encoded"/>
</wsdl:output >
Network
Perf
Mng
</wsdl:operation
>
Airspace
Dem &
Scenario </wsdl:binding>
Mng
Consumes and integrates
services from the
SWIM network
...
Service Level
Management
Mng
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..
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
SWIM in China
ATMB
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
The Future Air Traffic
Management System of China
24-25 June 2010
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
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
24-25 June 2010
SWIM-SUIT Final User Forum, Rome
SWIM-SUIT Final User Forum, Rome
Implementation Plan
……
2010 - 2013
Short-term
…
2011
2012
Short-term
2010
2013 - 2017
Middle-term
2013
2014
2015
2016
2017 - 2025
Long-term
2017
2018
2019
Middle-term
1.Prototype design: based
1.Requirement Analysis:
on ATM information platform,
Data exchange among
the validation of SWIM
different users
simulation prototype
2.Standards: Consistency
2.Demonstration program:
of data, SOA, message
North Regional ATMB to ATMB,
service, data transmission
Evaluates the reliability, safety
and SWIM plan
and robust of service, message,
3.Policies: Consistency of
security and interface
service policies, strategies
3.Key technologies:
4.Key technologies: Flight
Security architecture,
info (plan, radar, ADS-B),
the structure of flight object service management,
, data exchange technologies Wx, AIM, TFM
4.Policies: improve service
5.Prototype research:
policies
Research on the transition
from current informationlization
5.Coordination: airlines,
Airports, None-CAAC users
construction programs
24-25 June 2010
24-25 June 2010
2020
2021
Long-term
2022
……
2023
2024
2025
2025
1.Seamless integration: Ground-ground and
ground-air data exchange and sharing, system
Integration
2.Upgrading and Deployment: Infrastructure
upgrading, from western to eastern China, from
low density to high density airports
3.Infrustructure running: Online operation,
providing services for CNATS users
SWIM-SUIT Final User Forum, Rome
SWIM-SUIT Final User Forum, Rome
User’s Benefits in China
Increase
airspace capacity
and efficiency
B
Enhance
safety
A
SWIM
Promote quality
of service
24-25 June 2010
24-25 June 2010
E
Improve
C
Collaborative
Decision Making
D Reduce cost
and emission
SWIM-SUIT Final User Forum, Rome
SWIM-SUIT Final User Forum, Rome
User’s Benefits in China
Passengers
ATC
Airlines
Airports
24-25 June
2010June 2010
24-25
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
SWIM-SUIT Final User Forum, RomeSWIM-SUIT Final User Forum, Rome
SWIM-SUIT
Final User Forum
24-25 June 2010
SWIM-SUIT Final User Forum, Rome