5. Virtual Centre Concept - context
5
Geographical decoupling of:
• ATM Data Service Providers (ADSPs)
• Air Traffic Service Units (ATSUs)
In SESAR 1 and in the future:
decoupling through open and standardised
service interfaces
Service Oriented Architecture:
• Dataflows organised through Services
• Open and common service interfaces
• Standardised service interfaces as final
objective
6. Virtual Centre Concept - benefits
6
Virtual Centre Concept, a technical
enabler for:
•Optimized technical infrastructure costs to
provide ATM Data
•Dynamic airspace allocation allowing
optimisation of ATM operations:
Delegation of sectors during peak
hours
Closure of an ATSUs during night
•Contingency scenarios between European
ATSUs
7. Virtual Centre - context
7
OPEN AND STANDARD SERVICE
INTERFACES
SERVICE PROVIDER FOR VIRTUAL CENTRES
8. Virtual Centre - context
8
OPEN AND STANDARD SERVICE
INTERFACES
SPECIALISED SERVICE PROVIDERS BY SERVICE(S)
Inter Service Providers Services
9. Virtual Centre - context
9
OPEN AND STANDARD SERVICE
INTERFACES
Inter Service Providers Services
SPECIALISED SERVICE PROVIDERS BY SERVICE(S)
10. Virtual Centre - context
10
OPEN AND STANDARD SERVICE
INTERFACES
Inter Service Providers Services
SPECIALISED SERVICE PROVIDERS BY SERVICE(S)
Gateway
11. Virtual centre – context - SESAR 1 Scope
11
OPEN AND STANDARD SERVICE
INTERFACES
Necessary Dataflows
SPECIALISED SERVICE PROVIDERS BY SERVICE(S)
Gateway
Service interface design in SESAR1
SERVICE PROVIDER FOR VIRTUAL CENTRES
13. Main steps
17
Feasibility study for Virtual Centre Concept
Common service architecture
Common list of operations / service
Common logical payloads in messages
Proof of concept : Demonstrations !!!
15. 19
Virtual Centre Services for CWPs
The main objective of SESAR1 Virtual Centre is to define Services
needed by CWPs for normal operation
Operational Modelling described each of the capabilities
provided by an En-route/Approach ATS Node
Service Modelling described each of the Service
Interfaces for the CWP
SESAR Factsheet on operational modelling
methodology was adopted
SESAR Working Method Services AdoptedWhat is a
Service?
16. service modelling : covered scope
sd CHMI Management
CHMI
SUR
MONA
CONF
AMAN
SNET
AGDS
- ATC Clearances
- ATC Instruction
- Planning Inputs
- Sequence Advisory
Acceptance
TP&M
FPLD
C&T
SSRCM
ATCO
(from
Misc)
SUPP
CORR
LTCM
OPSUP
Surveillance Data
«flow»
Surveillance Weather
«flow»
Monitoring Aids
«flow»
TBS Related Alerts
«flow»
Conflict Data
«flow»
Manual Monitoring Aids Interaction
«flow»
Coordination&Transfer
Data
«flow»
Safety Nets Notifications
«flow»
Active Pattern and AFIs
«flow»
Arrival Flight Metering
«flow»
Arrival Sequence Data
«flow»
CTA Processing
«flow»
Coordination&Transfer
Data Inputs
«flow»
Departure Sequence Data
«flow»
CTA Processing
«flow»
Airspace Mgt Notifications
«flow»
Arrival Sequence Inputs
«flow»SFPL Change Request
«flow»
Manual Conflict
Interaction
«flow»
Mode A Code Mgt
«flow»
CTA Processing
«flow»
CTA Processing
«flow»
Trajectory Inputs
«flow»
Manual Correlation Mgt
«flow»
Sequence Advisories Acceptance
«flow»
CPDLC Uplink
Internal
«flow»
Flight Data
«flow»
Complexity Mgt Data
«flow»
Mode A Code Mgt
«flow»
Commands
«flow»
Track SFPL Correlation Data
«flow»
Arrival Constraint
«flow»
CPDLC
Downlink
Internal
«flow»
CM Downlink
Internal
«flow»
Air-Ground
Inconsistencies
«flow»
ADS-C Downlink
Internal
«flow»
Airspace Mgt
Notifications
«flow»
Trajectory Data
«flow»
Airspace & Sectorisation
«flow»
SURVSURV
SNETSNET
AMANAMANFlight
Data
Flight
Data
CORRCORR
C & TC & T
TRAJECTORYTRAJECTORY
CONFCONF
MONAMONA
AGDSAGDS
SSR CMSSR CM
LTCMLTCM
SUPPSUPP
OPSUPOPSUP
Primary Services
Secondary
Services
Not addressed CWP
90 % of the scope
covered
Note: Primary Services shall
be validated during the
Project Demonstration
Phase.
17. Service Identification - Project 10.1.7 TAD used to define Primary & Secondary
services
21
Virtual Centre Services for CWPs
Primary Services:
CWP
Flight Data
& Trajectory
Coordination
& TransferCorrelation
Surveillance
Surveillance
Data
SFPL Change
Request
Flight
Data
Manual
Correlation
Mgt
Correlation
Data
C & T
input
C & T
Data
Flight Data Management Service:
This Service supports the Controller
to input information in the system.
Flight Data Distribution
Service:
Distributes updates at
every modification of the
Flight Data.
Co-ordination & Transfer Service:
Manages Coordination and
Transfer operations.
.
Correlation Distribution Service:
Provides a pairing between a
System Flight Plan and a System
Track.
Correlation Management Service:
manually correlates/ de-correlates
a System Flight Plan to/from a
System Track.
Surveillance Data Distribution
Service:
Provides a representation of the
actual air traffic situation.
18. 22
Virtual Centre Services for CWPs
Surveillance
Data
Flight
Data
Manual
Correlation
Mgt
Correlation
Data
C & T
input
Secondary Services:
Conflict
Management
Safety
Nets
Monitoring
Aids
Arrival
Management
Conflict
Data
Manual Conflict
Interaction
Safety Net
Notification
Monitoring
Aids
Arrival
Arrival Data
Flight Data
& Trajectory
Correlation
Surveillance
Coordination
& Transfer
C & T
Data
CWP
SFPL Change
Request
19. Maturity of Services
The Maturity of two of the SET1 services:
– FlightDataManagementServices:
• CORE vs Extension - 68% / 32%
• Note: critical flight data such as Aircraft id, Aircraft type, flight plan status
has been agreed as CORE for the Flight Data Management Service
– CoordinationandTransferServices:
• CORE vs Extension - 30% /70%
• Note: Critical Co-ordination data such as Coordination Reference, Speed,
heading, SFL has been agreed as CORE for the C&T service
23
Lessons learned:
•Substantial activity to model all CWP / Service
Providers interactions
•Defined 90% of service interfaces for CWP
•50% of the service interfaces are common
across Industrial Partners
27. Demo #7: Set-up
31
NATS Remote
Position
NATS Remote
Position
skyguide Remote
Position
skyguide Remote
Position
Eurocontrol Remote
Position
Eurocontrol Remote
Position
VisualizerVisualizer
FRQ CWPsFRQ CWPs skyguide CWPsskyguide CWPs
30. Conclusion: Achievements
11 Partners have developed a common model for CWP services
All major service interfaces for CWPs have been designed
Service interfaces as a basis for Virtual Centre Concept are
integrated in SESAR framework
Service interfaces implemented in 5 Service Providers and
8 different CWPs
Successful demonstrations including multi-vendor collaboration
at several European sites
Virtual Centre Concept Event and communication to ATM
community
Feasibility of Virtual Centre Concept
positively assessed
36
3 last bullets removed to keep the focus on most important messages.
It used to be:
Increased availability of ATM services in one ATSU, improving the safety and security of ATM in Europe.
Harmonised functionalities for airspace users and seamless transitions between ATSUs.
Agile commissioning of new ATM functionalities throughout Europe.
Inter Service Provider are part of the S2020. Illustration with hierarchy of services e.g. surveillance used by TP, TP used by Conflict Management or MONA…
Slide removed. Motivation:
Gain time
Too much text
Most messages are given in slide 5.
Slide removed. Motivation:
Gain time
Too much text
Most messages are given in slides 5 or 14.
The Operational scope (En-Route and Approach) can be given orally.
Propose to be removed. Motivations:
Too much text
Too much detail (e.g. 10.1.7)
Most of it is part of slide 21
The slide is removed and is consolidated with the next one. The main messages would have already been given in the agenda.
Previous slide information puts at notes:
Use of SESAR framework
Deliver common and open Service interfaces for CWPs
Demonstrate
Technical feasibility of common services for CWPs
Multi-vendor platforms as a step towards Virtual Centre Services interoperability
Provide the basis for future R&I activities to develop Virtual Centre Concept
The services defined for CWP does not include failure modes.
A ‘Service’ is ‘The contractual provision of something (a non-physical object), by one party, for the use of one or more other parties.’
Input from SESAR 1 operational projects Use Cases; Due to time constraints and complexity of task, the operational activities were limited
Output from Service Modelling was a common set of service interface definitions across all partners
Primary Services – Set 1 Services – required for demonstrations
Secondary Services – Set 2 Services
Flight Data Distribution Service:
This Service distributes updates to CWPs at every modification of the Flight Data
Flight Data Management Service:
This Service supports the Controller to input information in the system:
Modify manually existing Flight Data.
Submit information about instructions/clearances given to the flight crew
Co-ordination & Transfer Service:
This service addresses:
the CWP manual interactions for managing Coordination and Transfer operations,
automatic coordination of standard conditions as well as for manual coordination of non-standard conditions.
Correlation Distribution Service
This Service provides a pairing between a System Flight Plan and a System Track. It allows a CWP to subscribe to updates of a single correlation status update and/or periodic updates of all correlation status.
Correlation Management Service
This Service provides to the controller the operations to manually correlate/de-correlate a System Flight Plan to/from a System Track.
Surveillance Data Distribution Service:
This service publishes surveillance data (System Tracks) to subscribed users for a defined volume of airspace and defined type of service, providing a representation of the actual air traffic situation
MTCD removed because thought to be part of the CONF FB
Flight Data Management – Updated as part of Secondary Services
CORE data – represents common data to be shared by all partners. Extension data represents specific data for partners.
4 demonstrations
All multi-vendors
All involving 2 or 3 different CWPs
One demonstrating Service provider independence 2 ADSPs
Demo #7 already run. Other demos are demonstrated similar operations
Boxes are representing CWPs from Frequentis and skyguide.
They are fed by two independent Service Providers Eurocontrol and NATS.
Logical model, physical model, implementation, collection of log files
Demo #7 scenario with increasing complexity: remote, switch, multiple ADSP.
Markus to introduce the movie and to depict the content
R&I will continue with the development of the Virtual Centre Concept:
Business Modelling for some Virtual Centre concepts
Cost effectiveness of Virtual Centre concept
Extension of the scope: Voice Communication, Tower, ATFCM
Technical thread: Verification of Virtual Centre concepts at V3 maturity level
Operational thread: Validation of Virtual Centre concepts at V2 maturity level.
Impact study on EATMA