The Commission Implementing Regulation (EU) No 716/2014 requires the upgrade of existing AMAN to provide connection with cooperative En-Route Air Traffic Service Units (ATSU) to coordinate the actions to be taken by the cooperative ATSUs to make the correct time adjustment to flights under their control, in order to get the best and most efficient arriving flight sequence at the relevant airports based on AMAN arriving planning tool.
Categorisation
SERVICE_DEFINITION
- AERODROME_OPERATION
- CIVIL_AIRSPACE_USER
- COOPERATIVE_NETWORK_INFORMATION_EXCHANGE
- PUBLISH_SUBSCRIBE_PUSH
- SYNCHRONOUS_REQUEST_REPLY
Provider
EUROCAE
The European Organisation for Civil Aviation Equipment (EUROCAE) deals exclusively with aviation standardisation, for both airborne and ground systems and equipment. It was created in 1963 in Lucerne, Switzerland by a decision of the European Civil Aviation Conference as a European forum focusing on electronic equipment for air transport.
Restricted
Restricted
Cooperation between ATSUs and airports to improve the efficiency of arrival sequence.
Provide connection with cooperative En-Route Air Traffic Service Units (ATSU) to coordinate the actions to be taken by the cooperative ATSUs to make the correct time adjustment to flights under their control, in order to get the best and most efficient arriving flight sequence at the relevant airports based on AMAN arriving planning tool
Arrival Management Information_US
SESAR Identifier: IER-5.6.4-IERS-0032-0010 Issuer: Arrival Management Intended Addressess: Stakeholder ATSU Information Element: Arrival Management Information (IE-5.6.4-0032-0032)
Upstream Arrival Sequence information
A satellite airport which is a “nearby” airport having a departing flight to the concerned destination airport is informed of the arrival sequence of the destination airport.
Upstream ATSUs are informed of the sequencing of the arrival stream.
-
MAX_DELIVERY_TIME
The 'MAX_DELIVERY_TIME' is the maximum allowed difference between the time of reception of a message at the consuming interface and the time of publication from the providing interface. As this includes the time absorbed on the network layer, the provider has to offer an appropriate network performance and has to define a minimum network performance on the consuming side as a precondition. The MAX_DELIVERY_TIME shall be equal or lower than 10 seconds.
-
SERVICE_RESTART_TIME
Upon service restart the Arrival Sequence provider shall ensure that the service functionality is available within 'SERVICE_RESTART_TIME'. The ArrivialSequenceProvider shall provide a value for the SERVICE_RESTART_TIME parameter.
-
SUBSCRIPTION_TIME_TO_LIVE
Upon ArrivalSequenceConsumer unavailability the ArrivalSequenceProvider shall keep the subscription active within 'SUBSCRIPTION_TIME_TO_LIVE'. The ArrivialSequenceProvider shall provide a value for the "SUBSCRIPTION_TIME_TO_LIVE" parameter. This parameter is defined as the time within which the ArrivalSequenceProvider shall retain the subscription even if the ArrivalSequenceConsumer get disconnected.
-
MESSAGE_TTL
For each ArrivalSequenceConsumer, the ArrivalSequenceProvider shall retain a not yet consumed (or delivered) ArrivalSequence message for at least MESSAGE_TTL period of time. MESSAGE_TTL indicates the message 'time to leave', i.e. the amount of time a message yet to be consumed is retained by the provider if such message has not been consumed yet by the service consumer. The ArrivalSequenceProvider shall provide a value for the MESSAGE_TTL parameter. The MESSAGE_TTL represents the time a given ArrivalSequence message must be kept by the ArrivalSequenceProvider if not consumed or delivered to the ArrivalSequenceConsumer before discarding.
-
MAX_CONSUMER_NUMBER
The service provider shall define the MAX_CONSUMER_NUMBER parameter, which represents the maximum supported concurrent consumers of the service.
-
MIN_AVAILABILITY
The Arrivial SequenceProvider shall provide a value for MIN_AVAILABILITY parameter defined as the ratio between total time that the service is available and a given interval of time (e.g. 1 month, 1 year).
-
Common UTC time source
The systems providing or consuming the service shall be synchronised to a common UTC time-source.
-
Data qualityThe Quality of data provided by the service should be declared by the service provider
This can be achieved by verifying that the service formally fulfils the requirements of this standard and/or by validating or testing activities, which prove whether the expected behaviour and outcome of the service is achieved.
-
ATSUAir Traffic Service Unit
-
AMANArrival Management
-
SWIMSystem Wide Information Management
-
AIRMATM Information Reference Model
Arrival Sequence Service Information Definition
The order in which two or more Aircraft are planned to land taking into account ATM constraints
urn:aero:ses:eurocontrol:airm:1.0.0:LogicalModel:Subjects:AirTrafficOperations:TrafficSynchronization:ArrivalManagement:LandingSequence
Not applicable - Information Concept
-
General service behaviour
Please refer to ED-254 section 3.6.4
-
ArrivalSequenceInformationPublisherREST
REST Subscription Interface. This interface is one of the two implementation alternatives of the ArrivalSequenceInformationPublisher interface.
PROVIDER_SIDESYNCHRONOUS_REQUEST_RESPONSE-
subscribeToArrivalSequenceInformationgit
Create a new subscription resource
Messages-
subscribeToArrivalSequenceInformationIN
-
subscribeToArrivalSequenceInformationResponseOUT
-
-
unsubscribeToArrivalSequenceInformationgit
Remove a subscription from the portfolio.
Messages-
unsubscribeToArrivalSequenceInformationRequestIN
-
unsubscribeToArrivalSequenceInformationResponseOUT
-
-
communicateProblemgit
Report a problem.
Messages-
communicateProblemRequestIN
-
EndpointsRestricted
-
SWIM_TI_YP_1_1_WS_LIGHT
-
SWIM_TI_YP_1_1_IPV4_UNICAST
-
SWIM_TI_YP_1_1_WS_LIGHT1.1
-
-
ArrivalSequenceInformationPublisherSOAPWS SOAP Subscription Interface. This interface is one of the two implementation alternatives of the ArrivalSequenceInformationPublisher interface.PROVIDER_SIDESYNCHRONOUS_REQUEST_RESPONSE
-
subscribeToArrivalSequenceInformationCreate a new subscription resourcegitMessages
-
subscribeToArrivalSequenceInformationRequestIN
-
subscribeToArrivalSequenceInformationResponseOUT
-
-
unsubscribeToArrivalSequenceInformationRemove a subscription from the portfolio.gitMessages
-
unsubscribeToArrivalSequenceInformationRequestIN
-
unsubscribeToArrivalSequenceInformationResponseOUT
-
-
communicateProblemReport a problem.gitMessages
-
communicateProblemRequestIN
-
-
EUROCONTROL SWIM-TI Yellow Profile1.1
-
-
ArrivalSequenceInformationSubscriberPublication InterfaceCONSUMER_SIDEFIRE_AND_FORGET
-
publishArrivalSequenceOperation that allows the provider to publish an Arrival Sequence message to a subscribed consumer.gitMessages
-
arrivalSequenceOUT
-
-
communicateExceptionOperation that allows the provider to publish an Arrival Sequence message to a subscribed consumer.gitMessages
-
providerExceptionOUT
-
-
EUROCONTROL SWIM-TI Yellow Profile1.1
-
Arrival Sequence Service Performance Standard
SERVICE_STANDARD
Conformant
June 2018
Standardised SWIM service design for an AMAN Sequence Service. This standardised service design follows the specification documents for service descriptions as provided by EUROCONTROL. Together with them, it can be used as a basis to implement SWIM Service instances.
EUROCONTROL Specification for SWIM Service Description
EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION
Conformant
1.0
The Arrival Sequence Service is conformant with the SWIM Service Description Specification.
EUROCONTROL Specification for SWIM Information Definition
EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION
Conformant
1.0
The Arrival Sequence Service is conformant with the SWIM Information Definition Specification.
EUROCONTROL Specification for SWIM TI Yellow Profile
EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE
Conformant
1.1
The Arrival Sequence Service is conformant with the SWIM TI Yellow Profile Specification.