the european ais database (ead) - eurocontrol
TRANSCRIPT
1
The single source of aeronautical informationserving ATM and beyond
European AIS Database
EUROCONTROL
Network Managernominated by the European Commission
102003-2013
3
General Overview 5What is the European AIS database – EAD? 5
EAD – a unique concept 5
Benefits 6
Data Quality 6
Cost reduction 6
Availability and security 6
Data Coverage 6
Worldwide 6
ECAC 6
Accessing EAD 7
EAD Pro 7
MyEAD 7
EAD Basic 8
Download 8
AFTN 8
Supporting tools 8
Service Desk 8
Knowledge Base 8
SDO Input Guidance Manual - SIGMA 8
SDO Data Completeness Tool - SDC 8
EAD Training support and eLearning 8
Solutions 9SDO – Static Data Operations 9
SDO functions for Data Providers 9
SDO functions for Data Users 9
AIP and Chart Production Tools – AIP / CHT Production 10
AIP / CHT functions for Data Providers 10
PAMS – Published AIP Management System 10
PAMS functions for Data Providers 10
PAMS functions for Data Users 10
INO – International NOTAM Operations 11
INO functions for Data Providers 11
INO BF functions for ATS Reporting Offices 11
INO functions for Data Users 11
Becoming a client 12Trial Period 12
User registration 12
Data User Agreement 12
Connection Support 12
EAD Information Request Form 13
Table of contents
5
What is the European AIS database – EAD?
EAD, developed by EUROCONTROL on behalf of its Member
States, is a centralised reference database of quality-assured
aeronautical information. It includes a fully integrated state-of-
the-art Aeronautical Information Services (AIS) solution, for
the benefit of the ECAC (European Civil Aviation Conference)
Member States and all airspace users.
AIS units, acting as Data Providers, maintain the aeronau-
tical information under their responsibility directly into the
EAD. Airspace users, acting as Data Users, access the EAD to
retrieve, consult and download this aeronautical Information.
The rationale
The concept of the EAD was developed by EUROCONTROL
and its Member States following a study carried out in the
early 1990s which revealed that the AIS operational structure
at the time showed several limitations and drawbacks when
seen from a European perspective. In some cases, this included:
n incoherence of cross-border aeronautical information
n inconsistent quality of data throughout the ECAC area
n lack of interoperability between systems due to different
data models and exchange formats
n shortcomings in ensuring timely distribution of aeronau-
tical information updates to all stakeholders
n duplication of effort and investment and therefore costs
for all involved.
It was concluded that the cost effectiveness of AIS opera-
tions, the quality of aeronautical data and the accessibility
and availability of such data could be significantly improved
through automation and centralisation. This resulted in the
development of the EAD intended to facilitate European wide
maintenance and distribution of aeronautical information.
EUROCONTROL was entrusted with the development, estab-
lishment and operation of the EAD in July 1999. After the initial
development phase, the EAD entered provisional service in
July 2001 and began full operations in mid-2003. On 6 June
2013, the EAD celebrated ten years of successful operations.
Today, the EAD is made available through the Directorate
Network Management (DNM) of the EUROCONTROL Agency.
DNM provides air traffic flow management services over the
states of western and central Europe who are members of
ECAC. Within DNM, the Airspace/AIS Data Management Unit
(ADM) is responsible for the EUROCONTROL EAD service and
overall coherence of aeronautical information aspects within
DNM.
Non European States are showing growing interest, which
makes the scope of the EAD much wider than was originally
expected. At this point in time 15 organisations outside the
ECAC area are using the EAD; half of them are already providing
their Aeronautical data to EAD.
EAD – a unique concept
EAD is a single reference repository of aeronautical infor-
mation. It enables centralised management of digital
aeronautical information based on the AIXM model
(Aeronautical Information Exchange Model) developed by
EUROCONTROL. It enhances the quality of aeronautical data
by using international standards and rigorous data-checking
procedures, including in-depth validation and verification.
Two main types of clients use the EAD: Data Providers (DP)
and Data Users (DU). Additionally, the EAD Service Providers
ensure the required support to States on an operational,
technical and training level.
Data Providers use different EAD components for the crea-
tion, maintenance and storage of aeronautical information.
They retain full control of - and intellectual property rights
over - the data they input into the EAD. The concept of having
the Data Providers maintain their data in a common database
is unique in the aviation world. Available EAD solutions for
Data Providers are:
n Maintenance of static data - SDO
n Creation of NOTAM - INO
n Publication of aeronautical documents - PAMS
n AIP Production - AIP
n Chart Production - CHART.
EAD Service Provision is responsible for the processing
of worldwide NOTAM information as well as the Minimum
Static Data and AIP documents, for all those ECAC States not
migrated to the EAD, by using the SDO, INO and PAMS DP
solutions.
General Overview
6
Data Users consult and download aeronautical data or publi-
cations, and can generate reports from EAD. Available EAD
solutions for Data Users are:
n Generation of static data reports – SDO
n Pre-flight Information Bulletins (PIB) – INO
n Briefing Facility for ATS Reporting Office (ARO) – INO
n Consultation and download of aeronautical
publications – PAMS
Benefits
Data Quality
Data held in the EAD is assured against a variety of
standards and recommendations including ICAO,
OPADD, ESARRs, SDP, and the AICM/AIXM data models.
The system and operational procedures areupdated
in accordance with changes in applicable regulations.
In addition, regular data quality reviews and consistency checks
are conducted on data loaded by both the EAD and clients to
ensure consistency and improve procedures to minimise errors.
The EAD facilitates in resolving cross-border data conflicts
and guarantees the harmonisation of the available aero-
nautical information through well defined validation and
harmonisation rules.
Cost reduction
As a single point of reference the EAD provides a cost benefit
to both Data Users and Data Providers. The integration of the
different AIS components into the EAD has reduced the
workload throughout the AIS chain, including the cost and
effort of paper dissemination.
Centrally developed applications and common maintenance
have reduced implementation and maintenance costs to
clients, as well as increased compatibility between States.
In addition to this, the centralised processing of worldwide
NOTAM leads to added costs savings as well.
Availability and security
The service availability for the clients is covered by an SLA with
the provider, with an availability requirement of 99.975%. This
is supported by the 24h operational and technical Service Desk
enabling rapid dissemination of information on any issues
identified.
The EAD is using modern technologies, such as VPN or SSL,
for the timely and secure distribution of static and dynamic
data. As such, the EAD is a truly reliable source of aeronautical
information.
Data Coverage
Worldwide
n Original and processed NOTAM, SNOWTAM and ASHTAM
messages
n Minimum set of SDO required for NOTAM validation and
Pre-Flight Information Bulletin (PIB) generation encompassing
Aerodromes identification with associated Runways, Airspaces
(FIR, UIR, TMA, P-D-R), Routes, Navaids and Waypoints.
ECAC
n AIPs, AICs, Amendments, Supplements, and Charts
n Original and processed NOTAM, SNOWTAM and ASHTAM
n Full set of aeronautical information data published in AIP
including: Aerodrome information, procedures, obstacles;
enroute information, airspaces, routes, navaids and waypoints;
and general information, organization, authority and units.
Harmonisationand Consistency
DATA PROVIDERDirect data maintenance
DATA UsersPIB, NOTAM, AIP, Charts
NOTAM
SD
NOTAM
SD
NOTAM
SD
DATA
Quality
Central AIrepository
Since June 2003
EAD OperationsNon -migrated &
worldwide
7
General Overview
Accessing EAD
EAD Pro
EAD Pro is the software suite of specially-designed applications
to be installed on a PC. EAD Pro provides access to all EAD
Applications (SDO, INO, PAMS, BF) via a user-friendly, graphical
interface. It is the fully integrated, ready-to-run AIS solution,
which lets Data Providers manage aeronautical information
and retrieve the data. It provides also an easy access for Data
Users. Each EAD application is separately available on a soft-
ware license fee basis, including yearly maintenance providing
annual releases of the software, and is supplied by the EAD IT
Service Provider (ITP).
n ECIT – EAD Client Interface Terminal
EAD Pro software can be supplied pre-installed on a dedi-
cated PC by ITP, requiring no additional set-up work to be
done. Alternatively it can be installed by the client on any PC,
meeting the technical specifications, through the supplied
software installer.
n SSL – secure internet access
If the use of an ECIT is not required, the EAD Pro Data User ap-
plications can be made available by secure internet connec-
tion using Secure Socket Layer (SSL) technology.
MyEAD
MyEAD is the EAD system-to-system solution allowing client
applications, which require aeronautical information, to access
and/or exchange data seamlessly with the EAD. MyEAD
requires the client to carry out some software development,
based on schema supplied by EUROCONTROL, to access all
EAD functions. Any MyEAD connection will need to be tested
and validated prior to operational connection.
n ESI – EAD System Interface
ESI ensures the communication between an external client
system and the services provided by the EAD sub-systems.
The information exchanged via ESI is represented in XML.
For the development of an ESI connection, the Application
Programming Interface (API) and all other relevant technical
documentation will be supplied by EUROCONTROL.
n AIMSL – AIM Service Layer
With AIMSL, the EAD has started to provide interfaces to the
EAD sub-systems using open, standard technologies that
enable interoperability according to the Service-Oriented
Architecture principle, in particular Web Services. As such,
any possible dependencies on a bespoke API and dedicated
middleware are removed. Through AIMSL, the EAD will also
be able to act as an Aeronautical Information Management
System within the SESAR concept and exchange information
with other systems through SWIM.
EAD Basic
EAD Basic is an application providing a quick and easy access
to the EAD. Users who completed the on-line EAD Basic
registration, will be able to browse the database via the web.
EAD Basic provides, through a set of limited functions, the
possibility:
n to create basic Pre-Flight Information Bulletins (PIB),
n to generate standard aeronautical data reports, and,
n to browse Aeronautical Information Publication (AIP) and
chart publications.
As such, EAD Basic allows its users to get an idea of what
Aeronautical Information is made available through the EAD
prior to getting access through either EAD Pro or MyEAD.
EAD Basic can be accessed from:
http://www.ead.eurocontrol.int
Download
For clients who require defined batches of data, the EAD offers
the ability to download files from the EAD Internet File Server.
Downloads can be made at regular intervals, or by ad-hoc
requests through the EAD Service Desk from which the Client
will receive a notification that the file has been made available.
AFTN
If needed, NOTAM information contained in the EAD can also
be made available through a regular AFTN connection.
8
Supporting tools
Service Desk
The EAD Service Desk (SD) is the primary point of contact
between clients and the EAD providing 24h operational and
technical support for all clients, both Data Provider and Data
User. Through the online SD Interface, clients can report errors,
request downloads, ask questions and make suggestions.
Knowledge Base
The EAD Knowledge Base is a repository of EAD Documents
related to both the operational and technical aspects of the
system. Documents can either be searched for or can be
browsed by sub-system providing users a first-line informa-
tion source to anything EAD related, from the latest Release
content document to User Manuals and technical descriptions.
SDO Input Guidance Manual - SIGMA
SIGMA has been developed by the EAD to support Data
Providers uploading Static Data into the EAD. SIGMA includes
encoding rules of AICM/AIXM, as well as EAD SDO specific rules,
and contains AIP references where appropriate. The SIGMA
Forum is an online discussion tool monitored by the EAD
where users can ask questions and make use of the mutual
knowledge available.
SIGMA can be accessed from:
http://www.eurocontrol.int/sigma
SDO Data Completeness Tool - SDC
Through SDC, a process is set-up that facilitates the monitoring
of static data completeness by both States and EUROCONTROL.
This is done according to agreed Data Provider procedures
supporting the provision of all the required static data resulting
from the gap analysis that the SDC Tool provides.
The Static data completeness is covering all relevant AIP
information, and is going beyond the scope of ICAO Annex
15 requirements to address operational requirements as
addressed in various working groups.
EAD Training support and eLearning
Training is made available to all new clients of the EAD on each
of the subsystems and the use of the service desk. This can take
place in a variety of ways including: the EAD Training Centre
in Frankfurt, on site at the client’s premises, or by telephone.
In addition, introductory and continuing training is available
through the EAD e-learning facility. More information on the
available EAD eLearning modules can be found at:
http://www.eurocontrol.int/ians/public/standard_page/
training_catalogue.html
9
As a central repository of aeronautical information, the
EAD offers a number of seamlessly integrated sub-systems
to support the daily operations of any AIS unit. From the
maintenance of static data (SDO), to the creation (AIP/CHP)
and publication of AIP information (PAMS) and distribution
of NOTAM (INO), any AISP can use the different components
throughout the publication process of aeronautical informa-
tion.
At the same time, the different sub-systems allow any user of
aeronautical information to retrieve all information through
the respective functions – retrievel or query static data (SDO),
download AIP information (PAMS) or generate PIB and retrieve
NOTAM (INO). ATS Reporting office can also use the INO
Briefing Facility (BF) to manage and distribute their flight plans.
SDO – Static Data Operations
SDO is the central repository of validated static data
based on AICM/AIXM specifications. It is the heart of the EAD
and enables Data Providers to maintain the static data for their
area of responsibility and allows Data Users to retrieve static
data from all areas.
After data validation, the information is made available to the
different sub-systems to produce the AIP and Charts, to vali-
date the NOTAM information at creation or during processing,
and to perform the pre-validation of a flight-plan when using
the Briefing facility.
SDO allows the database to be queried through the generation
of pre-defined reports or the creation of user-defined reports. A
set of predefined filters can be incorporated in the report crea-
tion (e.g. validity period, sorting order, aeronautical region etc.).
The report can be generated in plain text or in XML format.
User defined reports allow the creation, deletion, modification,
retrieval, storage and execution of bespoke reports in the EAD;
while Pre-defined reports are created by EAD Staff to be used
by anyone having access to the database. SDO also provides
a graphical facility for the verification and visualisation of
complex static data changes before publication, while it can
also be used to build up queries and display the results in a
graphical manner, provided the static data has coordinates
(lat/long).
SDO functions for Data Providers
n Insertion, maintenance, withdrawal of data in AIXM format
n Graphical validation and verification
n Slot management for publication of data
n Upload facilities for data received from originators
n SIGMA and SDC Support
SDO functions for Data Users
n Generation of pre-defined report
n Creation of user-defined report
n Graphical reporting facility
n Data download in AIXM-XML, ARINC format
Solutions
StaticData
ECACAIP Library
DynamicData
AFTN, worldwideNOTAM reception
Worldwide AIP Subscription
TAM Processing
Worldwide MinimumStatic Data Set Update
AIP/Supp/AIC
TAM Creation
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
EAD Solutions and Workflow
eAIP Production& Charts
PAMS
NOTAMDistribution
BriefingFacility
SDO
INO
EADService
Military/Civil
ECACAIS
Office
10
AIP and Chart Production Tools – AIP/CHT Production
The AIP Production Tool is used to generate and maintain the
official national AIS documentation: AIP, AIRAC & non-AIRAC
AIP Amendments and Supplements, AICs and checklists for
Supplements and AICs. It provides facilities for: managing
the different versions of a document using the AIP manager,
modifying a document using the database by inserting a
database link inset in a paragraph or entering a table link inset
in a document, and generating document amendments in
PDF or XML format.
The Chart Production Tool is used to generate and maintain
aeronautical charts defined in an AIP. It provides facilities to:
set up a chart’s geographical reference, compose a chart with
elements from the database, synchronise a chart with annota-
tion from the database, update a chart for a new effective date,
maintain chart specifications and publish a chart.
The static data (Aerodrome, FIR, etc,) necessary for the creation
of both AIP documents and charts, is replicated from the SDO
database to the AIP and Chart database respectively.
AIP/CHT functions for Data Providers
n Creation and maintenance of aeronautical publications (eAIP,
AIP, AMDT, SUPP, CIRC)
n Creation and maintenance of aeronautical charts
n SDO data linkage
n Automatic generation of AIRAC or regular amendments and
charts
n Outputs: eAIP, PDF or HTML
PAMS – Published AIP Management System
PAMS is the library of ECAC States’ Aeronautical Information
Publications (AIPs), AIP Amendments, AIP Supplements and
Aeronautical Information Circulars (AICs) and Charts. It also
includes all AIP information from migrated States from outside
the ECAC region.
It enables Data Providers to store AIP, Amendments,
Supplements, AIC, and Charts, including meta-data such as
effective date and document heading in a document library.
The storage format to be used for the documents is either
PDF or XML format.
The automatic creation of NOTAM proposals, supported in
PAMS, is in accordance with the static data operational proce-
dures, when a newly created document is to be published.
PAMS enables Data Users to search aeronautical documents,
based on the meta-data filters associated with the documents
or the content of the documents itself.
PAMS functions for Data Providers
n Publication of documents and charts generated from EAD
AIP & CHT tools as well as from non-EAD tools
n Publication in PDF and XML/HTML format
n Pre-publication area
n Meta data setting per document
PAMS functions for Data Users
n Search, view, download, print aeronautical documents and
charts
n Advanced search selection criteria: AIP type and section,
effective date, meta data
n Iconography matching status of documents
11
Solutions
INO – International NOTAM Operations
As a worldwide database of original and processed messages
used in AIS and ATM, the INO sub-system provides consistent
and validated NOTAM, SNOWTAM and ASHTAM.
It enables the creation, maintenance and distribution of
NOTAM, SNOWTAM, and ASHTAM for NOTAM offices (NOF)
in accordance with ICAO Standards And Recommended
Practices (SARPS) and EUROCONTROL Operating Procedures
for AIS Dynamic Data (OPADD). It offers the possibility of
creating all different types of “TAM” messages as well as basic
data maintenance such as NOF Series, AFTN address lists and
distribution lists.
INO also supports the NOTAM management process by
providing increased quality and consistency through a single
repository, NOTAM-SDO linkage, NOTAM grouping, and
making available NOTAM templates and proposals. In addi-
tion NOTAM can be monitored by estimated NOTAM, NOTAM
history, and NOTAM proposals.
As such, it enables direct access to NOTAM, SNOWTAM,
ASHTAM for briefing purposes (PIB – Pre-flight Information
Bulletins). Additionally, monitoring of all incoming NOTAM
is possible. Briefings available include: aerodrome, area and
special area; based on airspace or centre point radius; route,
based on aerodrome of departure/destination and over-flown
FIRs; and narrow route, based on a pre-defined route, a flight
plan, or a route described by the operator.
For each PIB, the following features can also be requested:
a “full” or “update” PIB; immediate notification during a pre-
defined period of time after creation of the PIB; storage of
pre-defined routes based on flight plan or ad-hoc definition;
storage of frequently requested PIB in a profile; allowing the
user to re-use the definition of the PIB later on; schedule a
profile based on a date/time parameter.
For enhanced usability, pre-defined routes can be stored
based on flight plan or ad-hoc definition and store frequently
requested PIB in a profile, for later re-use.
The INO Briefing Facility (BF) for ATS Reporting
Offices (ARO) provides the ability to handle flight
plans and related information integrated in the INO
Data User application. Through this integration of the BF into
the existing INO DU application, the user can automatically
generate or schedule a PIB for a planned flight.
Through the BF, users are able to: create, validate and distribute
flight plans; manage repetitive flight plans; manage client
information and AFTN addresses; monitor the real traffic situ-
ation; identify the status of different flight plans; and manage
incoming and outgoing messages.
The Flight Plan (FPL) function enables users to: create new
FPL; manage routes; pre-validate the FPL against SDO data;
validate the FPL against the IFPUV; save a FPL in the FPL list;
send the FPL via AFTN; generate a PIB for a specific FPL; and
create AFTN addresses.
INO functions for Data Providers
n Creation and distribution of NOTAM, SNOWTAM, ASHTAM
n NOTAM SDO Linkage
n Grouping and Templates
n NOTAM history and proposals
n International, National and Military Series
n Meteo Support
n INO Contingency
INO BF functions for ATS Reporting Offices
n Creation, validation, distribution of Flight Plans
n Monitoring of real traffic situation
n Management of incoming and outgoing messages
n Management of client information and AFTN addresses
INO functions for Data Users
n Pre-flight Information Bulletin (PIB) inquiry: Aerodrome, Area,
Special area, Route, Narrow route
n PIB scheduling
n Profile and route management
n Graphical reporting
n TAM Subscription
12
Trial Period
The EADPro suite of software is made available to prospective
Data Users for a 3 month trial period.
User registration
To become an EAD Data User, please complete the Data
User registration form, which is available on the EAD general
website:
http://www.eurocontrol.int/network-operations/ead-service-
request-form
After receipt of the registration form a tailor-made offer will be
distributed, based on your specific requirements and needs.
This indicates the start of the connection activities.
Data User Agreement
Prior to connecting to the EAD a Data User Agreement must
be signed between the Data User (client) and EUROCONTROL.
This agreement will define the roles, responsibilities and the
obligations of both the client and EUROCONTROL, including
liability regarding data.
Connection Support
During the connection activities, the EAD Migration Manager
will assist the client until the finalisation of the migration
process.
Becoming a client
13
EAD Information Request Form
We are interested in the European AIS Database (EAD), please send us more information.
Our contact details:
Company: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unit/Dept.: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Name: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
First Name: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Position: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E-mail: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phone: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobile: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fax: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Street: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zip Code: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
City: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Country: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Nature of Business: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(I.e. airline, airport, commercial user, etc.)
We are interested in
q SDO - Static Data Operations
q INO - International Notam Operations
qPAMS - Published AIP Management System
qEAD Basic
qEAD Pro
qMyEAD
EAD Contact Point
Guido Haesevoets
EAD Customer & Migration Management
EUROCONTROL
Rue de la Fusée 96
B-1130 Brussels
Phone: +32 2 729 11 34
Fax: +32 2 729 90 29
E-mail: [email protected]
EAD general website: http://eurocontrol.int/ead
EAD Basic website: http://ead.eurocontrol.int
EUROCONTROL
© May 2013 – European Organisation for the Safety of Air Navigation (EUROCONTROL)
This document is published by EUROCONTROL for information purposes. It may be copied
in whole or in part, provided that EUROCONTROL is mentioned as the source and it is not used
for commercial purposes (i.e. for financial gain). The information in this document may not be
modified without prior written permission from EUROCONTROL.
www.eurocontrol.int