European ATM Service Description for
the Airport Flight Information
Publication Service
Document information
Project Title
Information Service Modelling Deliverables
Project Number
08.03.10
Project Manager
NORACON
Deliverable Name
European ATM Service Description for the Airport Flight Information
Publication Service
Deliverable ID
D62
Edition
00.00.04
Template Version
00.01.00
Task contributors
EUROCONTROL
Abstract
This document describes the SESAR service “Airport Flight Information Publication” as
part of the work for ISRM iteration 1.2. It is the result of the “Service Design” step of
the B.4.3 Working Method on Services. The Service Design has been performed in the
context of Service Activity FT10 entailing Airport Collaborative Decision Making
services.
The AirportFlightInformationPublication service supports the Airport CDM concept and
its implementation by providing the A-CDM partners with Common Situation Awareness
about flights at a CDM airport.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
Authoring & Approval
Prepared By - Authors of the document.
Name & Company
Position & Title
Date
Carlos Fornas Fernández / EUROCONTROL
WP8 Contributor
22/10/2014
Walter Van Hamme / EUROCONTROL
Service Activity Leader
22/10/2014
Name & Company
Position & Title
Date
Oliver Krüger / DFS
8.3.10 Contributor
03/11/2014
Bjørn Solberg / NORACON
8.3.10 Contributor
10/11/2014
Svein Johnsen / NATMIG
8.3.10 Contributor
12/11/2014
Frank Follert / SEAC
8.3.10 Contributor
12/11/2014
Reviewed By - Reviewers internal to the project.
Reviewed By - Other SESAR projects, Airspace Users, staff association, military, Industrial Support, other organisations.
Name & Company
Position & Title
Date
Name / Company
Position / Title
DD/MM/YYYY
Approved for submission to the SJU By - Representatives of the company involved in the project.
Name & Company
Position & Title
Date
Name / Company
Position / Title
DD/MM/YYYY
Rejected By - Representatives of the company involved in the project.
Name & Company
Position & Title
Date
Name / Company
<Position / Title>
DD/MM/YYYY
Rational for rejection
None.
Document History
Edition
Date
Status
00.00.01
22/10/2014
Draft
00.00.02
27/10/2014
Draft
00.00.03
30/10/2014
Draft
00.00.04
21/11/2014
Draft
Author
Carlos Fornas
Fernández
Carlos Fornas
Fernández
Carlos Fornas
Fernández
Carlos Fornas
Fernández
Justification
Initial Draft
For Team Review
For Project Review
For Approval
Intellectual Property Rights (foreground)
This deliverable consists of SJU foreground.
2 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
Table of Contents
EXECUTIVE SUMMARY ........................................................................................................................ 6
1
INTRODUCTION ............................................................................................................................. 7
1.1 PURPOSE OF THE DOCUMENT ........................................................................................................ 7
1.2 INTENDED READERSHIP ................................................................................................................. 7
1.3 INPUTS FROM OTHER PROJECTS .................................................................................................... 7
1.4 GLOSSARY OF TERMS ................................................................................................................... 7
1.5 ACRONYMS AND TERMINOLOGY..................................................................................................... 7
1.5.1 Acronyms ............................................................................................................................. 7
1.5.2 Terminology ......................................................................................................................... 9
1.6 INTRODUCTION TO THE A-CDM SERVICES ................................... ERROR! BOOKMARK NOT DEFINED.
1.6.1 Joint Service Activity ............................................................ Error! Bookmark not defined.
1.6.2 Overview of the A-CDM services......................................... Error! Bookmark not defined.
1.6.3 Beyond Service Design ....................................................... Error! Bookmark not defined.
2
SERVICE IDENTIFICATION ......................................................................................................... 11
3
OPERATIONAL AND BUSINESS CONTEXT .............................................................................. 12
3.1
3.2
3.3
4
SERVICE OPERATIONAL NODE INTERACTION ................................................................................ 12
SUPPORTED OPERATIONAL ACTIVITIES ........................................................................................ 13
INFORMATION EXCHANGE REQUIREMENTS ................................................................................... 12
SERVICE OVERVIEW ................................................................................................................... 15
4.1
4.2
4.3
5
SERVICE POLICIES (TAXONOMY) ................................................................................................. 15
SERVICE ATTRIBUTES (QOS) ...................................................................................................... 17
SERVICE FUNCTIONS AND CAPABILITIES ...................................................................................... 17
SERVICE INTERFACE SPECIFICATIONS .................................................................................. 19
5.1 PROVIDEDAIRPORTFLIGHTINFORMATIONPUBLICATION SERVICE INTERFACE DEFINITION ................ 19
5.1.1 subscribeFlightAlert Service Interface Operation .............................................................. 19
5.1.2 subscribeInboundFlight Service Interface Operation .......... Error! Bookmark not defined.
5.1.3 subscribeOutboundFlight Service Interface Operation ....... Error! Bookmark not defined.
5.1.4 unsubscribeFlightAlert Service Interface Operation ............ Error! Bookmark not defined.
5.1.5 unsubscribeInboundFlight Service Interface Operation ...... Error! Bookmark not defined.
5.1.6 unsubscribeOutboundFlight Service Interface Operation ... Error! Bookmark not defined.
5.1.7 Common Service Interface Parameter Definitions .............. Error! Bookmark not defined.
5.2 REQUIREDAIRPORTFLIGHTINFORMATIONPUBLICATION SERVICE INTERFACE DEFINITION ........ ERROR!
BOOKMARK NOT DEFINED.
5.2.1 pushFlightAlert ..................................................................... Error! Bookmark not defined.
5.2.2 pushInboundFlight ............................................................... Error! Bookmark not defined.
5.2.3 pushOutboundFlight ............................................................ Error! Bookmark not defined.
6
SERVICE DYNAMIC BEHAVIOUR ............................................................................................... 21
7
SERVICE PROVISIONING ............................................................................................................ 22
8
VALIDATION AND VERIFICATION .............................................................................................. 23
8.1
8.2
9
VERIFICATION............................................................................................................................. 23
VALIDATION ................................................................................................................................ 23
REFERENCES ................................................................... ERROR! BOOKMARK NOT DEFINED.
APPENDIX A
DEFINED.
SERVICE PAYLOAD TRACING TO AIRM CLDM ........... ERROR! BOOKMARK NOT
A.1
COMMON PAYLOAD ELEMENTS ................................. ERROR! BOOKMARK NOT DEFINED.
A.2
SERVICE-SPECIFIC PAYLOAD ELEMENTS ................ ERROR! BOOKMARK NOT DEFINED.
3 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
4 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
List of tables
Table 1 Summary table of the A-CDM services ...................................... Error! Bookmark not defined.
Table 2 A-CDMServiceResponseStatus element CLDM tracing ............ Error! Bookmark not defined.
Table 3 FlightID element CLDM tracing .................................................. Error! Bookmark not defined.
Table 4 GUFI element CLDM tracing ...................................................... Error! Bookmark not defined.
Table 5 IATAFlightIdentification element CLDM tracing ......................... Error! Bookmark not defined.
Table 6 ICAOFlightIdentification element CLDM tracing ........................ Error! Bookmark not defined.
Table 7 IFPLIdentification element CLDM tracing .................................. Error! Bookmark not defined.
Table 8 OffBlockReady element CLDM tracing ...................................... Error! Bookmark not defined.
Table 9 StartUpApproval element CLDM tracing .................................... Error! Bookmark not defined.
Table 10 TakeOff element CLDM tracing ............................................... Error! Bookmark not defined.
Table 11 TimeWindow element CLDM tracing ....................................... Error! Bookmark not defined.
Table 12 A-CDMServiceSubscription element CLDM tracing ................ Error! Bookmark not defined.
Table 13 Aerodrome element CLDM tracing .......................................... Error! Bookmark not defined.
Table 14 Aircraft element CLDM tracing ................................................. Error! Bookmark not defined.
Table 15 AircraftStand element CLDM tracing ....................................... Error! Bookmark not defined.
Table 16 Airline element CLDM tracing .................................................. Error! Bookmark not defined.
Table 17 AirportTransitView element CLDM tracing ............................... Error! Bookmark not defined.
Table 18 Alert element CLDM tracing ..................................................... Error! Bookmark not defined.
Table 19 Boarding element CLDM tracing .............................................. Error! Bookmark not defined.
Table 20 Deicing element CLDM tracing ................................................ Error! Bookmark not defined.
Table 21 Flight element CLDM tracing ................................................... Error! Bookmark not defined.
Table 22 FlightAlertSubscriptionRequest element CLDM tracing .......... Error! Bookmark not defined.
Table 23 FlightAlertSubscriptionResponse element CLDM tracing ........ Error! Bookmark not defined.
Table 24 FlightAlertUnsubscriptionRequest element CLDM tracing....... Error! Bookmark not defined.
Table 25 FlightAlertUnsubscriptionResponse element CLDM tracing .... Error! Bookmark not defined.
Table 26 FlightAlerts element CLDM tracing .......................................... Error! Bookmark not defined.
Table 27 Gate element CLDM tracing .................................................... Error! Bookmark not defined.
Table 28 GroundHandling element CLDM tracing .................................. Error! Bookmark not defined.
Table 29 InBlock element CLDM tracing ................................................ Error! Bookmark not defined.
Table 30 InboundFlight element CLDM tracing ...................................... Error! Bookmark not defined.
Table 31 InboundFlightSubscriptionRequest element CLDM tracing ..... Error! Bookmark not defined.
Table 32 InboundFlightSubscriptionResponse element CLDM tracing .. Error! Bookmark not defined.
Table 33 InboundFlightUnsubscriptionRequest element CLDM tracing . Error! Bookmark not defined.
Table 34 InboundFlightUnsubscriptionResponse element CLDM tracing .............Error! Bookmark not
defined.
Table 35 Landing element CLDM tracing ............................................... Error! Bookmark not defined.
Table 36 OffBlock element CLDM tracing ............................................... Error! Bookmark not defined.
Table 37 OutboundFlight element CLDM tracing.................................... Error! Bookmark not defined.
Table 38 OutboundFlightSubscriptionRequest element CLDM tracing .. Error! Bookmark not defined.
Table 39 OutboundFlightSubscriptionResponse element CLDM tracingError! Bookmark not defined.
Table 40 OutboundFlightUnsubscriptionRequest element CLDM tracing .............Error! Bookmark not
defined.
Table 41 OutboundFlightUnsubscriptionResponse element CLDM tracing ..........Error! Bookmark not
defined.
Table 42 RunwayDirection element CLDM tracing ................................. Error! Bookmark not defined.
Table 43 StandardInstrumentDeparture element CLDM tracing ............ Error! Bookmark not defined.
Table 44 TaxiOut element CLDM tracing ................................................ Error! Bookmark not defined.
List of figures
Figure 1 NOV-2 node interaction of Airport CDM Services .................... Error! Bookmark not defined.
Figure 2 NSOV-1 A-CDM Service taxonomy .......................................... Error! Bookmark not defined.
Figure 3 NSV-12 service provision of Airport CDM Services .................. Error! Bookmark not defined.
Figure 4 Airport CDM Information Sharing Concept Element ................. Error! Bookmark not defined.
Figure 5 NOV-2 AirportFlightInformationPublication node interaction of service ................................. 12
5 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
Figure 6 NSOV-4 ServiceToOpetationalActivitiesMapping ................................................................... 14
Figure 7 NAV IER Airport Flight Information Publication service requirement traceability ................... 13
Figure 8 NSOV-1 ISRM Service taxonomy 2 ........................................................................................ 15
Figure 9 NSOV-1 Airport Flight Information Publication service attributes ........................................... 17
Figure 10 NSOV-2 Airport Flight Information Publication service interface definitions......................... 18
Figure 11 NSOV-2 AirportFlightInformationPublication service interface definitions............................ 19
Figure 12 NSOV-2 AirportFlightInformationPublication service interface parameter definition
FlightAlertSubscriptionRequest ....................................................... Error! Bookmark not defined.
Figure 13 NSOV-2 AirportFlightInformationPublication service interface parameter definition
FlightAlertSubscriptionResponse ..................................................... Error! Bookmark not defined.
Figure 14 NSOV-2 AirportFlightInformationPublication service interface parameter definition
InboundFlightSubscriptionRequest .................................................. Error! Bookmark not defined.
Figure 15 NSOV-2 AirportFlightInformationPublication service interface parameter definition
InboundFlightSubscriptionResponse ............................................... Error! Bookmark not defined.
Figure 16 NSOV-2 AirportFlightInformationPublication service interface parameter definition
OutboundFlightSubscriptionRequest ............................................... Error! Bookmark not defined.
Figure 17 NSOV-2 AirportFlightInformationPublication service interface parameter definition
OutboundFlightSubscriptionResponse ............................................ Error! Bookmark not defined.
Figure 18 NSOV-2 AirportFlightInformationPublication service interface parameter definition
FlightAlertUnsubscriptionRequest ................................................... Error! Bookmark not defined.
Figure 19 NSOV-2 AirportFlightInformationPublication service interface parameter definition
FlightAlertUnsubscriptionResponse ................................................. Error! Bookmark not defined.
Figure 20 NSOV-2 AirportFlightInformationPublication service interface parameter definition
InboundFlightUnsubscriptionRequest .............................................. Error! Bookmark not defined.
Figure 21 NSOV-2 AirportFlightInformationPublication service interface parameter definition
InboundFlightUnsubscriptionResponse ........................................... Error! Bookmark not defined.
Figure 22 NSOV-2 AirportFlightInformationPublication service interface parameter definition
OutboundFlightUnsubscriptionRequest ........................................... Error! Bookmark not defined.
Figure 23 NSOV-2 AirportFlightInformationPublication service interface parameter definition
OutboundFlightUnsubscriptionResponse ........................................ Error! Bookmark not defined.
Figure 24 NSOV-2 AirportCDM Serices service interface parameter Flight ID .....Error! Bookmark not
defined.
Figure 25 NSOV-2 AirportCDMServices service interface parameter A-CDMServiceResponseStatus
......................................................................................................... Error! Bookmark not defined.
Figure 26 NSOV-2 AirportCDMServices service interface parameter A-CDMServiceSubscriptionError!
Bookmark not defined.
Figure 27 NSOV-2 AirportFlightInformationPublication service interface parameter definition
FlightAlerts ....................................................................................... Error! Bookmark not defined.
Figure 28 NSOV-2 AirportFlightInformationPublication service interface parameter definition
InboundFlight ................................................................................... Error! Bookmark not defined.
Figure 29 NSOV-2 AirportFlightInformationPublication service interface parameter definition
OutboundFlight ................................................................................ Error! Bookmark not defined.
Figure 30 NSOV-5c AirportFlightInformationPublication service event-trace description FlightAlerts . 21
Figure 31 NSOV-5c AirportFlightInformationPublication service event-trace description InboundFlights
......................................................................................................... Error! Bookmark not defined.
Figure 32 NSOV-5c AirportFlightInformationPublication service event-trace description
OutboundFlights ............................................................................... Error! Bookmark not defined.
Figure 33 NSV-12 AirportFlightInformationPublication service provision ............................................. 22
6 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
Executive summary
This document describes the SESAR service “XXXX” as part of the work for ISRM iteration
1.3. It is the result of the “Service Design” step of the B.4.3 Working Method on Services.
The Service Design has been performed in the context of SVAXXX/FTXX entailing
ServiceTaxonomyLevel(n-1)_Name.
The XXXX service supports the XXXX
SID_General_Goal_Of_IdetifiedService.
concept
and
its
implementation
by
SVAXXX/FTXX was based on OFA_OSED_OR_SOURCE_DOCUMENT. The activity has
happened in the frame of OFAXXX (OPS_WP and SYS_WP). Any joint collaboration should
come here.
The design complies with the ISRM Foundation and the service is published as part of ISRM
1.3. The service hereby presented is intended to be prototyped and validated in the VX
validation exercise EXEXXXXXXXXXX.
7 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
1 Introduction
1.1 Purpose of the document
The purpose of this Service Design Document (SDD) is to provide a complete logical
description of the XXXX service, its operational context, its basic architectural features, its
dynamical aspects, its operations and the data provided. All these aspects are presented as
model views according to the ISRM UML EATMA Profile, which organize knowledge about a
service into views inspired to the NAF Framework.
This SDD services as a complement to a model based description and supports the
configuration management process by providing well-defined baselines.
The logical service model presented in this SDD is part of the current ISRM 1.3 release, and
provides a blueprint which service developers must follow in order to create SWIMCompliant implementations of the service.
The service presented will be part of the Service Portfolio. The Service portfolio presents all
services that are available or is planned to become available at a high level.
1.2 Intended readership
This service description is intended to be read by Enterprise Architects, Service Architects,
Information Architects, System Engineers and Developers in pursuing architecting, design
and development activities.
It must be read by members of P08.01.03, P08.03.10, SYS_PROJECT, SWIM-TI_PROJECT
and B04.03.
1.3 Inputs from other projects
IF any:
Operational requirements are derived from OPS_PROJECT(s).
ELSE:
None. Operational requirements are derived from SOURCE_DOC.
1.4 Glossary of terms
IF any  Manual List
ELSE:
No terms beyond the ones accepted by SESAR have been identified yet.
1.5 Acronyms and Terminology
1.5.1 Acronyms
Term
Definition
8 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
Term
Definition
ADD
Architecture Description Document
ATM
Air Traffic Management
CC
Capability Configuration
EATMA
European Air Traffic Management Architecture
E-ATMS
European Air Traffic Management System
FAA
Federal Aviation Administration
IER
Information Exchange Requirement
ISRM
Information Services Reference Model
NAF
NATO Architecture Framework
NSOV
NAF Service Oriented View
NOV
NAF Operational View
NSV
NAF System View
OSED
Operational Service and Environment Definition
QoS
Quality of Service
SDD
Service Description Document
SESAR
Single European Sky ATM Research Programme
SESAR Programme
The programme which defines the Research and Development activities
and Projects for the SJU.
SJU
SESAR Joint Undertaking (Agency of the European Commission)
SJU Work Programme
The programme which addresses all activities of the SESAR Joint
Undertaking Agency.
SoaML
Service Oriented Architecture Modelling Language
SWIM
System Wide Information Management
UML
Unified Modelling Language
V&V
Validation and Verification
WSDL
Web Services Definition Language
XSD
XML Schema Definition
COMPLETE_MANUAL
LY
COMPLETE_MANUALLY
9 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
1.5.2 Terminology
Term
Definition
Source
Capability
The collective ability to deliver a specified type of effect or a
specified course of action. Within the context of the SESAR
Programme a capability is therefore the ability to support the
delivery of a specific operational concept to an agreed level of
performance.
Common working
meeting between
B41 EA study and
B43 T5
Capability
Configuration
A combination of organisational aspects (with their B43 ADD
competencies) and equipment that combine to provide a
capability. A Capability Configuration represents a
recognisable set of resources (technical systems, human
roles, and physical assets) derived from a generic stakeholder
organisation.
Note: Capability Configuration is a term used in NAF. The
equivalent SoaML stereotype to be used is Participant. Also
see note in Node term definition.
Node
A logical entity that performs Operational Activities specified
independently of any physical realisation e.g. a stakeholder
type providing and/or consuming operational information
within a network of others.
Common working
meeting between
B41 EA study and
B43 T5
Note: Node is a term used in NAF. The equivalent SoaML
stereotype to be used is Participant. Be aware that the original
intention of SoaML is that Participants are physical items and
not logical constructs. Service architects must indicate
whether the Participant is a logical (Node) or a physical
(Capability Configuration) construct.
Service
The contractual provision of something (a non-physical B43 T5 study
object), by one, for the use of one or more others. Services
involve interactions between providers and consumers, which
may be performed in a digital form (data exchanges) or
through voice communication or written processes and
procedures.
Service attribute
A Service Attribute defines a property of a service. Examples: B43 T5 study
Response time, Frequency of invocation, Message Exchange
Pattern.
Service contract
A service contract represents an agreement between the B43 T5 study
stakeholders involved for how a service is to be provided and
consumed.
Service function
A Service function describes what functionality is needed to B43 T5 study
provide or consume a service; it is the trigger for or is
triggered by the Service interactions. A Service function can
be automated to different extents depending on the context
e.g. a Service function supporting a complex activity may
need more automation than a Service function for a simple
activity.
Note: The equivalent SoaML stereotype is Capability, in WP8
Foundation documentation referred to as Service Capability.
10 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
Term
Definition
Source
Service
interaction
A Service interaction is a description of an information B43 T5 study
exchange between ATM stakeholders’ systems which can
potentially be automated; phone calls / voice exchanges are
considered as non-automated service interactions.
In considering automated interactions, a service interaction is
described by several modelling artefacts depicting the static
and dynamic behaviour of a service. This includes service
operations, data messages model and interaction behaviour.
Service interface
The mechanism by which a service communicates.
B43 T5 study
Service providers and consumers need to implement service
interfaces to be able to collaborate. A service interface
includes service operations that enable access to the
functionality of the services identified, as well as the data used
in the service interaction.
11 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
2 Service identification
The purpose of this chapter is to provide a unique identification of the service and describe
where the service is in terms of the engineering lifecycle.
Name
ID
SERVICE_NAME_(SPARED_BY_CAMELCASE)
«Service»_ELEMENT.GUID
Version
XX
Keywords
MANUAL EXTRACTION FROM SID
Architect(s)
MANUAL INPUT
Lifecycle
status
Date
Link
Identified
XX/XX/XXXX
SID_REFERENCE
Allocated
XX/XX/XXXX
SERVICE_ALLOCATION_REPORT_REFERENCE
Designed
XX/XX/XXXX
ISRM 1.3 Delivery Report
EXTRANET_LINK
Validated
Date when validated.
Filled by WP3
Link to protocol documenting the decision
IOC
Date
for
Initial
Operational Capability
Link to technical enabler hosting the service in the ATM master plan
FOC
Date
for
Full
Operational Capability
Link to technical enabler hosting the service in the ATM master plan
12 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
3 Operational and Business context
EXCREPT FROM SID
3.1 Service Operational Node Interaction
The following diagram describes the operational nodes interaction through the XXXX
Service:
NSV 12 NOV-2 AirportFlightPublication node interaction of serv ice
AirportCollaborativeDecisionMakingService
«Node»
AirportCDMOperations
«NodeProvidesServiceInterface»
«Service»
AirportFlightInformationPublication
«Node»
A-CDMPartner
«NodeRequiresServiceInterface»
Figure 1 NOV-2 AirportFlightInformationPublication node interaction of service
This service aims to enable interaction between the NODE_NAME_1, NODE_NAME_2, and
NODE_NAME_N.
3.2 Information Exchange Requirements
The following diagram describes the information exchange requirements satisfied by this
service:
13 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
NAV IER NAV IER AirportFlightInformationPublication serv ice requirements traceability
Provide to A-CDM partners Common Situational
Awareness concerning Outbound Flight
tags
megaid =
ref = A-CDM Implementation Manual
refType = Information exchange requirement
Text =
Provide to A-CDM partners Flight Alerts
AirportCollaborativeDecisionMakingService
«Service»
AirportFlightInformationPublication
«Satisfy»
tags
megaid =
ref = A-CDM Implementation Manual
refType = Information exchange requirement
Text =
Provide to A-CDM partners Common Situational
Awareness concerning Inbound Flights
tags
megaid =
ref = A-CDM Implementation Manual
refType = Information exchange requirement
Text =
Figure 2 NAV IER Airport Flight Information Publication service requirement traceability
The XXXX service is defined to satisfy COUNT_IER_ELEMENTS IERs:

To IER_1.NAME(No_Capital_Letter).

To IER_2.NAME(No_Capital_Letter).

To IER_N.NAME(No_Capital_Letter). EXTRA INFO CAN BE ADDED MANUALLY.
3.3 Other Requirements
3.3.1 Non-Functional Requirements
EXCREPT FROM OSED OR SPR OR INTEROP. MANUAL TEXT IF REQUIRED.
3.3.2 Relevant Industrial Standards
MANUAL TEXT
3.3.3 Supported Operational Activities
The following diagram describes the operational activities supported by this service:
14 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
NSOV-4 NSOV-4 Serv iceToOperationalActiv itiesMapping
AirportCollaborativeDecisionMakingService
«Service»
AirportFlightInformationPublication
«ServiceSupportsActivity»
A-CDM Flight Alerts
«OperationalActiv ity»
Take Correctiv e Action
«ServiceSupportsActivity»
«ServiceSupportsActivity»
Inbound Flights
«OperationalActiv ity»
Notify InboundFlightData
Outbound Flights
«OperationalActiv ity»
Notify ASAT
«OperationalActiv ity»
Check FPL discrepancy
(EOBT Tolerance Check)
«OperationalActiv ity»
Notify ASRT
«OperationalActiv ity»
Generate Alert
«OperationalActiv ity»
Notify TOBT/TTOT
«OperationalActiv ity»
Generate Alert (TOBT not
confirmed)
«OperationalActiv ity»
Notify TSAT
Figure 3 NSOV-4 ServiceToOpetationalActivitiesMapping
The XXXX service aims to support many operational activities in the framework of
SERVICE_TAXONOMY_LEVEL(N-1).NAME.
15 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
4 Service overview
XXXX service is «Service»_ELEMENT.NOTES. part of a series of services that help automate
the A-CDM process at a CDM Airport. This service concerns the publication of flight information to all
A-CDM Partners that need it.
In particular, this service provides publication under subscription of inbound flights, landing in the
airport; outbound flights, taking off from the airport; and their system generated alerts, here called
Flight Alerts.
IF PUB/SUB:
Note that technical details of the service, such the subscription identifier, are out of the
scope of this document. This document sticks to the pure logical definition of the service and
it is up to the service implementation to decide technical solutions.
4.1 Service Policies (Taxonomy)
The following diagram describes the relevant part of the ISRM Service Taxonomy and the
positioning of this service within it:
class NSOV-1 ISRM Serv ice taxonomy 2
«ServiceGeneralisation»
«Service»
AirportOperationsManagementService
«Service»
IsrmService
{root}
«ServiceAttribute»
+ providedAccessControl :AccessControl
+ providedAuthenticity :Authentication
+ providedAvailabilityInPercent :Integer
+ providedContext :ISRMcontext
+ providedContextQualification :Qualification
+ providedFlightCondition :Integer
+ providedIntegrity :Integrity
+ providedMaximumMessageReception :Integer
+ providedMaximumMessageSize :Integer
+ providedMaximumReceptionPerTimeUnit :TimeUnit
+ providedMessageSizeUnit :MessageSizeUnit
+ providedProcessingThroughput :Integer
+ providedProcessingThroughputTimeUnit :TimeUnit
+ providedProvisionCapacity :Integer
+ providedProvisionPeriod :TimeUnit
+ providedRecoverabilityTime :Integer
+ providedRecoverabilityTimeUnit :TimeUnit
+ providedReportingCondition :ReportingCondition
+ providedResponseTime :Integer
+ providedResponseTimeUnit :TimeUnit
+ providedSafety :Safety
+ requiredAccessControl :AccessControl
+ requiredAuthenticity :Authentication
+ requiredAvailabilityInPercent :Integer
+ requiredConfidentiality :Confidentiality
+ requiredContext :ISRMcontext
+ requiredContextQualification :Qualification
+ requiredFlightCondition :Integer
+ requiredIntegrity :Integrity
+ requiredMaximumMessageReception :Integer
+ requiredMaximumMessageSize :Integer
+ requiredMaximumReceptionPerTimeUnit :TimeUnit
+ requiredMessageSizeUnit :MessageSizeUnit
+ requiredProcessingThroughput :Integer
+ requiredProcessingThroughputTimeUnit :TimeUnit
+ requiredProvisionCapacity :Integer
+ requiredProvisionPeriod :TimeUnit
+ requiredRecoverabilityTime :Integer
+ requiredRecoverabilityTimeUnit :TimeUnit
+ requiredReportingCondition :ReportingCondition
+ requiredResponseTime :Integer
+ requiredResponseTimeUnit :TimeUnit
+ requiredSafety :Safety
«ServiceGeneralisation»
«Service»
AirportCollaborativeDecisionMakingService
«ServiceGeneralisation»
«ServiceGeneralisation»
«Service»
AirportFlightInformationPublication
«Service»
PartnerValueSetting
«ServiceGeneralisation»
«ServiceGeneralisation»
«ServiceGeneralisation»
«Service»
TargetOffBlockTimeSetting
«Service»
PreDepartureSequenceSetting
«Service»
CalculatedResultDelivery
«ServiceGeneralisation»
«Service»
CalculatedPreDepartureSequenceDelivery
Figure 4 NSOV-1 ISRM Service taxonomy 2
The
XXXX
service
is
one
if
the
SERVICE_TAXONOMY_LEVEL(N1).NAME(WITHOUT_SPACES), which itself is part of SERVICE_TAXONOMY_LEVEL(N2).NAME(WITHOUT_SPACES).
16 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
Within ISRM, all defined services are specialisations of the abstract ISRM Service.
17 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
4.2 Service Levels (NfRs)
The following diagram describes the non-functional requirements expressed as Service
Attributes. Additional information on the Quality of Service may appear in plain text notes.
NSOV-1 SL NSOV-1 AirportFlightInformationPublication serv ice lev el
Name:
Author:
Version:
Created:
Updated:
NSOV-1 AirportFlightInformationPublication service level
08.03.06 Walter Van Hamme
1.0
3/13/2014 12:00:00 AM
11/19/2014 3:30:43 PM
«ServiceLevel»
airportFlightInformationPublication :
AirportFlightInformationPublication
requiredConfidentiality = Configurable
requiredAvailabilityInPercent = Configurable
requiredProcessingThroughput => 10000
requiredProcessingThroughputTimeUnit = Day
Time behav iour:
latency of input or change
from sending partner systems
to the ACISP and publication
from ACISP to receiving
partners systems shall not
exceed more than 10 seconds.
Performance:
depends on the consumers
ATC tends to have stricter
requirements. In general it is
the second range.
Modifiability:
easy extension of further
attributes.
Detail of configurable service attributes.
requiredConfidentiality:
ability to restrict access to flights and certain data fields the consumer is authorised to see
(e.g. role and profile based).
requiredAv ailabilityInPercent:
depends on the customer.
Figure 5 NSOV-1 Airport Flight Information Publication service attributes
4.3 Service Functions and Capabilities
The following diagram describes the functions and capabilities provided by this service:
18 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
NSOV-2 NSOV-2 AirportFlightInformationPublication serv ice interface definition
«RequiredServiceInterfaceDefinition»
«ServiceInterfaceDefinition»
Prov idedAirportFlightInformationPublication
«ProvidedServiceInterfaceDefinition»
«ServiceInterfaceOperation»
+ subscribeFlightAlert(FlightAlertSubscriptionRequest) :FlightAlertSubscriptionResponse
+ subscribeInboundFlight(InboundFlightSubscriptionRequest) :InboundFlightSubscriptionResponse
+ subscribeOutboundFlight(OutboundFlightSubscriptionRequest) :OutboundFlightSubscriptionResponse
+ unsubscribeFlightAlert(FlightAlertUnsubscriptionRequest) :FlightAlertUnsubscriptionResponse
+ unsubscribeInboundFlight(InboundFlightUnsubscriptionRequest) :InboundFlightUnsubscriptionResponse
+ unsubscribeOutboundFlight(OutboundFlightUnsubscriptionRequest) :OutboundFlightUnsubscriptionResponse
AirportCollaborativeDecisionMakingService
«Service»
AirportFlightInformationPublication
AirportFlightInformationPublication
consumer
«ServiceInterface»
AirportFlightInformationPublicationInterface
«ServiceInterfaceDefinition»
RequiredAirportFlightInformationPublication
«ProvidedServiceInterfaceDefinition»
«ServiceInterfaceOperation»
+ pushFlightAlert(FlightAlerts) :void
+ pushInboundFlight(InboundFlight) :void
+ pushOutboundFlight(OutboundFlight) :void
«RequiredServiceInterfaceDefinition»
Figure 6 NSOV-2 Airport Flight Information Publication service interface definitions
The XXX service is composed of COUNT_«ServiceInterfaceDefinition»_ELEMENT interface
definitions
with,
in
total,
COUNT(COUNT_«ServiceInterfaceDefinition»_«ServiceInterfaceOperation»_ELEMENT)
operations:
«ServiceInterfaceOperation»_ELEMENT_1.NAME,
«ServiceInterfaceOperation»_ELEMENT_2.NAME,
and
«ServiceInterfaceOperation»_ELEMENT_N.NAME.
The service interface definition and its operations and parameters payload are further
explained in Section 5.
19 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
5 Service interface specifications
The XXXX service is based on 1) COUNT_«ServiceInterfaceDefinition»_ELEMENT
interfaces together implementing MEP_LIBRARY_TYPE interaction 2(IF ONLY ONE)
implementing MEP_LIBRARY_TYPE :

«ServiceInterfaceDefinition»_ELEMENT_1.NAME
contains
the
«ServiceInterfaceDefinition»_ELEMENT_1.NOTES(MUST_INCLUDE_SIMPLE_MEP
_MENTION). subscription and unsubscription operations and is instantiated by the
service provider and used by the service consumer to access the service interface
definition operations. This interface implements Synchronous Request/Response
MEP in order to enable un/subscriptions

«ServiceInterfaceDefinition»_ELEMENT_N.NAME
contains
the
«ServiceInterfaceDefinition»_ELEMENT_N.NOTES(MUST_INCLUDE_SIMPLE_ME
P_MENTION).
The following diagram describes the service interface definitions of this service:
NSOV-2 NSOV-2 AirportFlightInformationPublication serv ice interface definition
«RequiredServiceInterfaceDefinition»
«ServiceInterfaceDefinition»
Prov idedAirportFlightInformationPublication
«ProvidedServiceInterfaceDefinition»
«ServiceInterfaceOperation»
+ subscribeFlightAlert(FlightAlertSubscriptionRequest) :FlightAlertSubscriptionResponse
+ subscribeInboundFlight(InboundFlightSubscriptionRequest) :InboundFlightSubscriptionResponse
+ subscribeOutboundFlight(OutboundFlightSubscriptionRequest) :OutboundFlightSubscriptionResponse
+ unsubscribeFlightAlert(FlightAlertUnsubscriptionRequest) :FlightAlertUnsubscriptionResponse
+ unsubscribeInboundFlight(InboundFlightUnsubscriptionRequest) :InboundFlightUnsubscriptionResponse
+ unsubscribeOutboundFlight(OutboundFlightUnsubscriptionRequest) :OutboundFlightUnsubscriptionResponse
AirportCollaborativeDecisionMakingService
«Service»
AirportFlightInformationPublication
AirportFlightInformationPublication
consumer
«ServiceInterface»
AirportFlightInformationPublicationInterface
«ServiceInterfaceDefinition»
RequiredAirportFlightInformationPublication
«ProvidedServiceInterfaceDefinition»
«ServiceInterfaceOperation»
+ pushFlightAlert(FlightAlerts) :void
+ pushInboundFlight(InboundFlight) :void
+ pushOutboundFlight(OutboundFlight) :void
«RequiredServiceInterfaceDefinition»
Figure 7 NSOV-2 AirportFlightInformationPublication service interface definitions
The Service Interface Definitions and their payload tracing are described in the subsections
below. The tracing of the Service Payload to AIRM CLDM appears in Error! Reference
source not found..
5.1 «ServiceInterfaceDefinition»_ELEMENT_N.NAME
Interface Definition
Service
The «ServiceInterfaceDefinition»_ELEMENT_N.NAME interface provides means to:

«ServiceInterfaceOperation»_ELEMENT_N.NAME
allows
to
«ServiceInterfaceOperation»_ELEMENT_N.NOTES(WITHOUT_CAPITAL_LETTER).
A graphical representation of this interface is given in PREVIOUS_FIGURE_REFERENCE.
5.1.1 «ServiceInterfaceOperation»_ELEMENT_N.NAME
Interface Operation
Service
The «ServiceInterfaceOperation»_ELEMENT_N.NAME Service Interface Operation
«ServiceInterfaceOperation»_ELEMENT_N.NOTES(WITHOUT_CAPITAL_LETTER).
receives subscription requests for flight alert publications filtered to the specification of the
request. The operation returns a confirmation of the validity of such subscription request
20 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
taking into account local business rules in accordance with the provision of the Service Level
Agreement ratified by all the A-CDM partners within the airport.
The operation requires COUNT(«ServiceInterfaceOperation»_ELEMENT_N.INPUT) input
parameter:
«ServiceInterfaceOperation»_ELEMENT_N.INPUT.NAME
message.
IF
COUNT(«ServiceInterfaceOperation»_ELEMENT_N.OUTPUT)>0 THEN After the operation
is
processed,
the
service
provides
COUNT(«ServiceInterfaceOperation»_ELEMENT_N.OUTPUT)
output
parameter:
«ServiceInterfaceOperation»_ELEMENT_N.OUTPUT.NAME. ELSE ; and does not return
any message as output parameter. The service interface parameters are further explained in
sections below.
21 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
6 Service dynamic behaviour
This section describes the behaviour of the interactions between the Service Consumer and
each Service Interface of the XXXX service.
6.1 Service Interface «ServiceInterface»_ELEMENT_N.NAME
The XXXX service supports mainly COUNT(«Service»_ELEMENT.MEP_LIBRARY) MEP:
«Service»_ELEMENT.MEP_LIBRARY.NAME. IF COMPLEX MEP THEN However, in order
to provide this complex MEP, «Service»_ELEMENT.MEP_LIBRARY.NOTES. it provides
Synchronous Request/Response MEP for subscription and unsubscription operations and
Fire«actor,Servic...
& Forget for publication operations (asynchronous by definition).
The following diagram describes the interaction between the service consumer and the
service EXTRA CLARIFICATION CAN BE ADDED IF MORE THAN ONE NSOV-5c:
NSOV-5c NSOV-5c AirportFlightInformationPublication serv ice ev ent-trace description FlightAlerts
«Service»
AirportFlightInformationPublication
AirportFlightInformationPublication
consumer
AirportFlightInformationPublicationInterface
subscribeFlightAlert(FlightAlertSubscriptionRequest) :FlightAlertSubscriptionResponse
loop Repetetiv e publication
pushFlightAlert(FlightAlerts)
opt Unsubscribe
unsubscribeFlightAlert(FlightAlertUnsubscriptionRequest) :FlightAlertUnsubscriptionResponse
Figure 8 NSOV-5c AirportFlightInformationPublication service event-trace description
FlightAlerts
22 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
7 Service provisioning IF EXISTS (NSV-12)
The following diagram describes the service provision of the XXXX service:
NSV 12 NSV-12 AirportFlightInformationPublication serv ice prov ision
Name:
Author:
Version:
Created:
Updated:
NSV-12 AirportFlightInformationPublication service provision
cffernan
1.0
10/24/2014 12:00:00 AM
11/21/2014 10:28:05 AM
«System»
AirportCollaborativeDecisionMakingService
«System»
ACISP
«Service»
AirportFlightInformationPublication
A-CDM Partner System
«ProvidedService»
«RequiredService»
Figure 9 NSV-12 AirportFlightInformationPublication service provision
The XXX service is naturally provided by the «System»_ELEMENT(WHERE
«ProvidedService».SOURCE).NAME and consumed by the «System»_ELEMENT(WHERE
«RequiredService».SOURCE).NAME.
23 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
8 Validation and Verification
8.1 Verification
Note the verification report:
LINK TO EXTRANET VERIFICATION REPORT
8.1.1 Verification Results
Service Name:
Service XXX
Date of
DDMMYY
Verification:
Service Version:
Version of
Phase:
Verification
-
Owner of Service:
Rules used:
Name of Verifier:
Manual
Overall Comments:
Passes:
Failures:
Warnings:
ID
Path
Author
Modified
Type
Rule
Result
Comment
Res
pons
e
8.2 Validation
The service hereby presented is intended to be prototyped and validated in the Validation
Exercise VPXXX, planned to be executed in Manual_Input_FROM(SCG_ROADMAP).
24 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.
Project Number 8.3.10
Edition 00.00.04
D62 - European ATM Service Description for the Airport Flight Information Publication Service
END OF DOCUMENT-
25 of 25
©SESAR JOINT UNDERTAKING, 2011. Created by member(s) for the SESAR Joint Undertaking within the frame of the
SESAR Programme co-financed by the EU and EUROCONTROL. Reprint with approval of publisher and the source properly
acknowledged.