EAD Service Release 10 Content Information - Eurocontrol · EAD Service Release 10 Content Information EAD/DOC-GERJ9Z Version : ... (e.g. CHM-257), ... CHM-2582 SDD Upgrade the applications

EUROPEAN ORGANISATION FOR THE SAFETY OF AIR NAVIGATION

EUROCONTROL

EAD Service

Release 10

Content Information

EAD/DOC-GERJ9Z

Version : 2.0 Issue Date : 2015/12/11 Status : Approved Deliverable No : No

Distribution EC : Yes

Release 10

Content Information Page 2/68

Version: 2.0 Status: Approved

Document Information

Contact Person: Raul Vorsmann Department: GroupEAD Europe S.L.

Phone/Fax: +49 69 78072 890 E-mail: [email protected]

Document produced by:

GroupEAD Europe S.L. Heinz-Michael Kraft

Parque Empresarial San Fernando Avenida de Castilla 2 Edificio Francia - Escalera A - Piso 2 28830 San Fernando de Henares Madrid

Company or product names mentioned in this document may be trademarks or registered trademarks of their respective companies.

No part of the document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the written permission of EUROCONTROL.

Release 10



Distribution Table

Name Company Department No. of copies

Hardcopy/ Softcopy

Mr Matern EUROCONTROL 1 SC

Ms Neuschlova EUROCONTROL 1 SC

Mr Kummer EUROCONTROL 1 SC

Mr Robbins EUROCONTROL 1 SC

Mr Hughes EUROCONTROL 1 SC

Mr d’Humières FREQUENTIS 1 SC

Mr Wessely FREQUENTIS 1 SC

Mr Schaefer FREQUENTIS 1 SC

Mr Barrett MANAGED AIS 1 SC

Mr Smit NEDGRAPHICS 1 SC

Mr Kraft GROUPEAD 1 SC

Ms Segovia GROUPEAD 1 SC

Mr Langhammer GROUPEAD 1 SC

Ms Abajo GROUPEAD 1 SC

Mr Centeno GROUPEAD 1 SC

Release 10



Change History

Version Date Reason for Change Chapter / Section

Affected

0.1 2015-05-18 New document All

1.0 2015-06-26 Updates based on EUROCONTROL and FRQ review.

Released version.

1.2, 2, 2.3, 3.1, 4.2, 4.2, 4.4, 4.5,

5.4, 5.10, 6, 7, 8.5, 9, 9.1, 10, 10.9, 11, 11.2, 11.3, 11.5, 12, 12.1, 12.3, 13, 14, 15

1.0 2015-07-09 Approved version -

1.1 2015-12-01 New and updated changes included 1.2, 5.4, 6, 7, 10.6

2.0 2015-12-04 Released version 5.4

2.0 2015-12-11 Approved version -

Status Name Date Signature

Created/updated: R. Vorsmann 2015-12-01 Electronic

Reviewed: V. Karpenko 2015-12-01 Electronic

Formally reviewed M. Segovia 2015-12-02 Electronic

Released: R. Vorsmann 2015-12-04 Electronic

Approved CCB: CCB 2015-12-10 RKQ2

Release 10



Contents

1 Introduction .......................................................................................................................................... 8

1.1 Purpose and Scope ............................................................................................................................... 8 1.2 Changes excluded from the document .................................................................................................. 8

2 Static Data Operations (SDO) ........................................................................................................... 10

2.1 Upload and Download of SDO User Extensions (CHM-2414) ............................................................ 10 2.2 Category change for PR_RUM_45_DPN_DIST_1 (CHM-2503) ......................................................... 11 2.3 SDO/AIMSL Service Extension (CHM-2526) ...................................................................................... 11 2.4 Prevent update of records in SDO that have been updated in SDD (CHM-2533) .............................. 11 2.5 Changes from ICAO Amendment 38 to Annex 15 (CHM-2553) ......................................................... 12

3 Static and Dynamic Data (SDD) ........................................................................................................ 14

3.1 AIXM 5.1 input via AIMSL .................................................................................................................... 14 3.2 SDD-AIMSL services for AIXM 5.1 data (CHM-2521, 2522, 2523) ..................................................... 17 3.3 Business Rules validation component (CHM-2524) ............................................................................ 17 3.4 AIXM 5.1 to 4.5 mapping component (CHM-2525) ............................................................................. 17 3.5 Automated provision from AIXM 5.1 to AIXM 4.5 (CHM-2527) ........................................................... 18 3.6 Adaptation of the AIXM 4.5 to 5.1 slot replication/mapping functionality (CHM-2528) ....................... 18 3.7 Additional AIXM 5.1 features and attributes for SDD download (CHM-2529) ..................................... 18 3.8 SDD download available via AIMSL (CHM-2530) ............................................................................... 20 3.9 SDD reporting via WFM (CHM-2543) .................................................................................................. 20

4 INO Data Provider .............................................................................................................................. 22

4.1 Enhancement of polygon function (CHM-1634) .................................................................................. 22 4.2 Illegal character identification (CHM-2497) ......................................................................................... 24 4.3 NOTAM Proposal enhancements (CHM-2157, 2514) ......................................................................... 25 4.4 NOTAM Proposal via SSL (EAD Pro) (CHM-2506) ............................................................................. 28 4.5 NOTAM proposal via WFM (CHM-2540) ............................................................................................. 33 4.6 Implementation of OPADD 4.0 (CHM-2600) ....................................................................................... 36

5 INO Data User ..................................................................................................................................... 39

5.1 Enhancement of PIB Scheduling (CHM-1236) .................................................................................... 39 5.2 PIB query refactoring (CHM-2420) ...................................................................................................... 40 5.3 PIB scheduler refactoring (CHM-2421) ............................................................................................... 40 5.4 Common Address Book enhancements (CHM-2559) ......................................................................... 40 5.5 Webservices: route description for Narrow Route PIB (CHM-2598) ................................................... 42 5.6 BF-Box improvements (CHM-1608) .................................................................................................... 42 5.7 BF-Box configuration files (CHM-1937) ............................................................................................... 43 5.8 BF-Dynamic PIB Distribution Info with FPL Request (CHM-2544) ..................................................... 43 5.9 BF-“Un-map message” function (CHM-2551) ..................................................................................... 43 5.10 BF-"Clear status" enhancement (CHM-2552) ..................................................................................... 44 5.11 BF- Automatic PIB Creation after ACK-reception (CHM-2609) ........................................................... 45

6 AIP ....................................................................................................................................................... 47

6.1 AIXM 5.1 as data source for AIP (CHM-666) ...................................................................................... 47 6.2 Selecting AIP Sections AD 2, 3, 4, 5 and 6 for generation based on comparison (CHM-2469) ......... 47 6.3 Production tracking tools (CHM-2474) ................................................................................................ 47 6.4 Add/change text in table headings (CHM-2475) ................................................................................. 48 6.5 Annex 15 Amendment 38 changes to AD 2.19 (CHM-2607) .............................................................. 48 6.6 Annex 15 Amendment 38 changes to ENR 3.3 (CHM-2608) .............................................................. 48 6.7 Client side FrameMaker upgrade (CHM-2622) ................................................................................... 48 6.8 Annex 15 Amendment 37 changes to tables (CHM-2623) .................................................................. 49

Release 10



7 Chart Production ............................................................................................................................... 50

7.1 Conditional symbolisation on NDP attributes (CHM-903) ................................................................... 50 7.2 Match scale to footprint and vice versa (CHM-2636) .......................................................................... 50 7.3 Zoom capability for footprint picker (CHM-2655) ................................................................................. 50 7.4 AIXM 5.1 import from SDD - fix-type elements (CHM-2656) .............................................................. 50

8 Common Services ............................................................................................................................. 52

8.1 WFM: NOTAM proposal (CHM-2540) ................................................................................................. 52 8.2 WFM: slot information in forms (CHM-2541) ....................................................................................... 52 8.3 WFM: new input box (CHM-2542) ....................................................................................................... 54 8.4 WFM: SDD Data Reporting (CHM-2543) ............................................................................................ 54 8.5 CRC32 for data input and output (CHM-2589) .................................................................................... 54 8.6 New role "PROPOSAL" in UMS for INO DP (CHM-2672) ................................................................... 56

9 Service Desk ...................................................................................................................................... 57

9.1 Access rights in EAD Knowledge Base (CHM-973) ............................................................................ 57 9.2 Jira upgrade (Service Desk) (CHM-2601) ........................................................................................... 57 9.3 Atlassian Confluence upgrade (Knowledge Base) (CHM-2602) ......................................................... 57 9.4 Atlassian Crowd Upgrade (SSO) (CHM-2603) .................................................................................... 57

10 Basic Software ................................................................................................................................... 58

10.1 Client side Windows upgrade (CHM-2564) ......................................................................................... 58 10.2 Client side Internet Explorer upgrade (CHM-2565) ............................................................................. 58 10.3 Client side Firefox upgrade (CHM-2566) ............................................................................................. 58 10.4 Client side Java upgrade (CHM-2567) ................................................................................................ 59 10.5 Client side Acrobat Reader upgrade (CHM-2568) .............................................................................. 59 10.6 Client side FrameMaker upgrade (CHM-2622) ................................................................................... 59 10.7 Client side Charting upgrade to MicroStation SS3 (CHM-2657) ......................................................... 59 10.8 Client side Oracle upgrade (CHM-2658) ............................................................................................. 59 10.9 Change of antivirus tool from TrendMicro to McAfee (CHM-2659) ..................................................... 60 10.10 Enforce client SSL certificate for the use of EAD Pro via SSL (CHM-2666) ....................................... 60

11 ESI/AIMSL ........................................................................................................................................... 61

11.1 ESI: upgrade to Release 10 basic software (CHM-2577) ................................................................... 61 11.2 AIMSL: NOTAM proposal enhancements (CHM-2513) ...................................................................... 61 11.3 AIMSL: Expose SDO and SDD web services (CHM-2555) ................................................................. 61 11.4 CRC32 for data input and output (CHM-2588) .................................................................................... 62 11.5 AIMSL: Common Address Book REST Interface (CHM-2690) ........................................................... 62

12 Hardware/LAN .................................................................................................................................... 64

12.1 Strengthened cryptography by increased certificate key size (CHM-2515) ........................................ 64 12.2 Use of RADIUS service in EAD (CHM-2517) ...................................................................................... 64

13 PAMS .................................................................................................................................................. 65

14 Graphical Tools .................................................................................................................................. 66

15 Abbreviations and Definitions .......................................................................................................... 67

Release 10



Contents of Figures

Figure 2-1 SDO – Possible PBN values ........................................................................................................... 13 Figure 4-2 INO DP – Polygon, simple .............................................................................................................. 22 Figure 4-3 INO DP – Polygon, extended .......................................................................................................... 23 Figure 4-4 INO DP – Item E) editor .................................................................................................................. 24 Figure 4-5 INO DP – List of Unprocessed Proposals, Notes to NOF ............................................................... 25 Figure 4-6 INO DP – List of Unprocessed Proposals, Originator ..................................................................... 27 Figure 4-7 INO DP – List of Unprocessed Proposals, Languages ................................................................... 28 Figure 4-8 EAD Pro – INO Menu ...................................................................................................................... 29 Figure 4-9 EAD Pro – New proposal, simple .................................................................................................... 29 Figure 4-10 EAD Pro – New proposal, structured ............................................................................................ 30 Figure 4-11 EAD Pro – List of sent proposals .................................................................................................. 32 Figure 4-12 EAD Pro – List of processed proposals ........................................................................................ 32 Figure 4-13 EAD Pro – List of rejected proposals ............................................................................................ 33 Figure 4-14 WFM – NOTAM Proposal Process ............................................................................................... 34 Figure 4-15 WFM – NOTAM Proposal Form .................................................................................................... 35 Figure 4-16 OPADD – Table of default radius indicators ................................................................................. 37 Figure 5-17 Data User – Schedule Panel ......................................................................................................... 39 Figure 5-18 Data User – Interfaces .................................................................................................................. 41 Figure 5-19 Data User – Menu tree .................................................................................................................. 41 Figure 5-20 FPL – Un-map message ............................................................................................................... 44 Figure 5-21 FPL List – Clear status .................................................................................................................. 45 Figure 5-22 FPL – PIB distribution ................................................................................................................... 45 Figure 8-23 WFM – Assemble SDO Update .................................................................................................... 53 Figure 8-24 WFM – SDO Update Task ............................................................................................................ 53 Figure 8-25 WFM – Request of Data Origination ............................................................................................. 54 Figure 8-26 Trusted EAD Environment ............................................................................................................ 55 Figure 8-27 CRC overview ............................................................................................................................... 55

Release 10



1 Introduction

1.1 Purpose and Scope

The purpose of this document is to provide EAD Data Providers and Users the description of changes being implemented with EAD Release 10. The document represents a snapshot at the time the document is produced. For further details on the new functionalities, it is recommended to consult the different user manuals.

Every Change Proposal described in this document contains a unique key (e.g. CHM-257), which can be used in EAD Change Management Tool for obtaining more detailed description of the change. EAD Change Management Tool is available via URL: http://chm.ead-it.com for dedicated users.

The structure of this document is as follows:

Chapter 1: Introduction

Chapter 2: SDO

Chapter 3: SDD

Chapter 4: INO Data Provider

Chapter 5: INO Data User

Chapter 6: AIP

Chapter 7: Chart Production

Chapter 8: Common Services

Chapter 9: Service Desk

Chapter 10: Basic Software

Chapter 11: ESI/AIMSL

Chapter 12: MHS

Chapter 13: Hardware/Lan

Chapter 14: PAMS

Chapter 15: Graphical Tools

Note:

This document contains references to affected procedures in Operational User Handbook Data User (EAD-DOC-GEKEB9) and Operational User Handbook Data Provider (EAD-DOC-GEKB38). Both named documents will be updated for Release 10 to reflect the impact of the changes.

1.2 Changes excluded from the document

Following R10 changes are excluded from this document due to their technical nature:

CHM-2579 INO DP Upgrade the applications to the Basic Software of Release 10

CHM-2422 INO DU Refactor text wrapping for AFTN

CHM-2571 INO DU BF-Box upgrade to Red Hat Linux 5.11

CHM-2580 INO DU Upgrade the applications to the Basic Software of Release 10

CHM-1724 Common Services Integrate pluggable Data Source of DFS CRM System with Common

Address Book

CHM-2576 Common Services Upgrade the applications to the Basic Software of Release 10

http://chm.ead-it.com/

Release 10



CHM-2673 Common Services Common Address Book: Extension of CAB on B2B functionality

CHM-2569 Basic Software Server side upgrade from Linux 5.7 to Linux 5.11

CHM-2570 Basic Software Server side upgrade of database to Oracle 12

CHM-2575 AIMSL Upgrade AIMSL server side to the Basic Software of Release 10

CHM-2556 SDO SDO integration for ADQ Phase 2 changes

CHM-2583 SDO Upgrade the applications to the Basic Software of Release 10

CHM-2538 SDD Domain-model cleanup

CHM-2539 SDD O/R Mapping layer: switch to Hibernate

CHM-2582 SDD Upgrade the applications to the Basic Software of Release 10

CHM-2520 AIP Decoupling of the Datalink accessors (used in the AIP subsystem)

CHM-2616 - 2621 AIP Upgrade the applications to the Basic Software of Release 10

CHM-2674 / 75 / 96 AIP Upgrade the applications to the Basic Software of Release 10

CHM-2653 CHP MicroStation SS3 support (64-bit, x64)

CHM-2654 CHP Replacement of Oracle OO4O-based client connection

Following R10 changes are excluded from this document due to their administrative nature:

CHM-2531 Common Services WFM: DOP data entry forms SDD: mapped features from 5.1 to 4.5

CHM-2532 Common Services WFM: DOP data entry forms SDD: AIXM 4.5 (minimum static data set)

CHM-782 SDO Slot Management improvement

CHM-2534 SDO Notification to DOP of automatic slot transfer from SDO

CHM-2537 SDO FAA Loader updates

Release 10



2 Static Data Operations (SDO)

The following SDO changes are deployed with Release 10:

Change Proposal CHM-2414 Upload and Download of SDO User Extensions

Change Proposal CHM-2503 Category change for PR_RUM_45_DPN_DIST_1

Change Proposal CHM-2526 SDO/AIMSL service extension

Change Proposal CHM-2533 Prevent update of records in SDO that have been

updated in SDD

Change Proposal CHM-2553 Changes from ICAO Amendment 38 to Annex 15

2.1 Upload and Download of SDO User Extensions (CHM-2414)

The upload and download capability of SDO User Extensions (UE) is introduced in EAD.

In order to support the exchange of customer specific attributes, which are not part of the AIXM 4.5, an XML schema definition has been defined describing the exchange model for user extensions. This schema is used for both uploading and downloading user extension data in EAD.

Upload of User Extensions

Together with the AIXM 4.5 upload file for EAD an additional file shall be provided, having the same filename but an .uext extension. Upon upload the UE file is validated against the uext schema.

Upload of UE is possible also via ESI and the auto upload feature (IFS).

The auto-upload function ignores the provided uext files (is not upload alone), until the corresponding main upload file is provided in the IFS directory.

Download of User Extensions

In case user extensions are to be downloaded, the client shall indicate so in the standard EAD download request. EAD staff includes it respectively in the created parameter set (check mark). As a result an additional file with the extension ".uext" is created, one for each generated download file. It is created only if there exists any UE values for the content of the download file.

User extensions can have limited read permissions. The download of user extensions from EAD adheres to these permissions and UE data is not provided to download clients who do not have respective read permission. This is assured by the following workflow:

AIXM 4.5 download file is placed into specific IFS directory (e.g. /home/sdo/download1/)

The .uext files are put in the subdirectory under the main download (e.g. /home/sdo/download1/LP)

A separate .uext file is created per every recipient (”created for”) of the parameter set

A separate subdirectory is automatically created per every user that is the recipient of the parameter set (“created for”)

Respective .uext file is placed into the respective subdirectory of the user

EAD staff maintains the access rights of the subdirectories, making it available for the respective organisations

Impact on OUH: Operational User Handbook – Data User, chapter 6.4 and 13.1

Impact on user: Update of internal procedures to be considered: Yes

Release 10



2.2 Category change for PR_RUM_45_DPN_DIST_1 (CHM-2503)

The existing business rule in SDO (PR_RUM_45_DPN_DIST_1) is updated to be with both category B and C and provide a warning on both Private Slot and Public Slot level. This is instead of current category B only.

The rule reads: "If CODE_TYPE is of type ( 'ICAO' , 'COORD' , 'OTHER' ) then there should not exist any other designated point with CODE_TYPE of ( 'ICAO' , 'COORD' , 'OTHER' ) located within 1NM."

Impact on OUH: No

Impact on user: Update of internal procedures to be considered: No

2.3 SDO/AIMSL Service Extension (CHM-2526)

SDO/AIMSL is extended to expose services that are the equivalent of the following existing SDO-DP ESI functionalities:

SDO Update function for uploading AIXM 4.5 data

Slot Management functions that are necessary for manipulating private slots:

o Create, check, close, reopen, remove, modify, move.

Update of pending data by delete and re-upload, the interface functions are:

o CancelPendingData

o ModifyPendingData

Get administrative, pending, committed data (e.g list of Public Slots, content of private slot etc), the interface functions are:

o RequestPrivateSlotContent (already in AIMSL)

o RequestPrivateSlots (already in AIMSL)

o RequestPublicSlots (already in AIMSL)

o RequestPublicSlotCheckingReport

o RequestPublicSlotContents

Impact on OUH: No


2.4 Prevent update of records in SDO that have been updated in SDD (CHM-2533)

This change introduces necessary safeguards to prevent an update of the same entity of static data in different AIXM versions.

It shall not be possible to update in SDO the data records that have been backward mapped from AIXM 5.1 (SDD)

Organizations that transition and provide their static data in AIXM 5.1, shall not be able to update their data anymore in AIXM 4.5

The backward mapped data is identified and marked in SDO as 4.5*.

The safeguards are implemented on 3 different levels:

Release 10



1. Record

A feature (record) that has been changed in AIXM 5.1 (SDD) shall not be editable in AIXM 4.5 (SDO) anymore. This check is implemented as Level A check.

In the SDO application the Edit/Update button is disabled for those records and they include 4.5* in their version information.

2. Private Slot

Private Slots in SDO that contain backward mapped data from SDD are marked as 4.5*. Those slots are visible in Slot tree only for EAD staff.

3. Organisation

After an organisation has transitioned to SDD and provides static data in EAD in AIXM 5.1 format, all users within this organisation are no longer able to update static data in AIXM 4.5 (SDO).

In the SDO application the Edit/Update button is disabled for those users.

Impact on OUH: Operational User Handbook – Data Provider, chapter 6


2.5 Changes from ICAO Amendment 38 to Annex 15 (CHM-2553)

Based on ICAO Amendment 38 to Annex 15, the capability to enter Performance Based Navigation (PBN) specific data in SDO is introduced.

The capability to include PBN will be possible by introducing specific User Extensions. These specific User Extensions will not be placed in the UE tab page in SDO, but will have a separate tab page named “PBN”. It is made available for the following entities in SDO:

AHP Usage Condition (AUC)

Route segment (RSG)

STAR (SIA)

SID (SID)

IAP (IAP)

Procedure Leg PLG)

The user shall select the respective PBN value and pay utmost attention to the correctness and applicability of the value selected.

Release 10



Entity Label Possible values

AHP Usage Condition (AUC) Usage cond. RNP free text

Route segment (RSG) PBN Operations RNAV, RNP

Route segment (RSG) PBN Navigation SpecificationRNAV 10, RNAV 5, RNAV 2, RNAV 1, RNP 4, RNP 2, A-RNP, RNP

APCH, RNP AR APCH, RNP 0.3

STAR (SIA) PBN Operations RNAV, RNP

STAR (SIA) PBN Navigation SpecificationRNAV 10, RNAV 5, RNAV 2, RNAV 1, RNP 4, RNP 2, A-RNP, RNP


STAR (SIA) Procedure Leg sequence RNP 4, 2, 1, 0.3, 0.2, 0.1

SID (SID) PBN Operations RNAV, RNP

SID (SID) PBN Navigation SpecificationRNAV 10, RNAV 5, RNAV 2, RNAV 1, RNP 4, RNP 2, A-RNP, RNP


SID (SID) Procedure Leg sequence RNP 4, 2, 1, 0.3, 0.2, 0.1

IAP (IAP) PBN Operations RNAV, RNP

IAP (IAP) PBN Navigation SpecificationRNAV 10, RNAV 5, RNAV 2, RNAV 1, RNP 4, RNP 2, A-RNP, RNP


IAP (IAP) Procedure Leg sequence RNP 4, 2, 1, 0.3, 0.2, 0.1

Procedure leg (PLG), STAR Proc. Leg Phase/Type free text

Procedure leg (PLG), IAP Proc. Leg Phase/Type free text

Procedure leg (PLG), SID Proc. Leg Phase/Type free text

Procedure leg (PLG), HPE Proc. Leg Phase/Type free text

Figure 2-1 SDO – Possible PBN values

Impact on OUH: No


Release 10



3 Static and Dynamic Data (SDD)

The following SDD changes are deployed with Release 10:

Change Proposal CHM-2521, 2522, 2523 SDD-AIMSL services for AIXM 5.1 data

Change Proposal CHM-2524 Business Rules validation component

Change Proposal CHM-2525 AIXM 5.1 to 4.5 mapping component

Change Proposal CHM-2527 Automated provision from AIXM 5.1 to

AIXM 4.5

Change Proposal CHM-2528 Adaptation of the AIXM 4.5 to 5.1 slot

replication/mapping functionality

Change Proposal CHM-2529 Additional AIXM 5.1 features and attributes

for SDD download

Change Proposal CHM-2530 SDD download available via AIMSL

Change Proposal CHM-2543 SDD Reporting via WFM

3.1 AIXM 5.1 input via AIMSL

With Release 10, the AIXM 5.1 (SDD) input capability via AIMSL is introduced in EAD.

This capability impacts both data provision and usage of static data in EAD. All EAD Clients are requested to read carefully the provided information. Further details can be provided upon request.

Additional documentation on limitations accompanying the release deployment will be provided.

Basic Principles

Data in AIXM 4.5 format will be maintained in SDO.

Data in AIXM 5.1 format will be maintained in SDD.

Data in SDO is mapped and replicated to SDD: the process is named forward mapping.

Data loaded in SDD is mapped and replicated to SDO: the process is named backward mapping.

SDD will be the reference database for static data but both formats will coexist in EAD until further notice.

An ECIT interface is not yet implemented by EAD and only static data provider clients who implement the provided AIMSL interface can transition to SDD, providing and maintaining their data in AIXM 5.1.

The worldwide minimum dataset continues to be updated by DOP in SDO (AIXM 4.5).

Synchronisation

Necessary processes and services are put in place assuring continuous synchronisation between SDO and SDD, allowing the maintenance of static data in both formats in an efficient way.

SDD is populated with:

1. Native AIXM 5.1 data

2. Data replicated (forward mapped) from SDO (AIXM 4.5)

SDO is populated with:

1. Native AIXM 4.5 data

2. Data backward mapped from SDD (AXM 5.1)

Release 10



Data loaded in SDO, mapped from SDD, is called 4.5* data. Those data will not be again forward mapped to SDD.

The replication from SDO to SDD and the mapping from SDD to SDO are designed to keep both databases synchronized at the defined dataset level.

Data Maintenance in SDD

There is no slot concept in SDD. The slot concept of SDO is used for validation purposes in SDD. When an update is made to SDD via upload, the system will run the needed checks.

If all the checks are passed successfully, including the upload of the backward mapped data to SDO and related slot management.

The data is automatically and immediately “committed”. The concept of commit is then different to SDO because there is no manual commit of the data anymore.

If any of the checks fails, the upload file is rejected. This process is automated and not monitored by DOP service.

The status “Pending” does not exists in SDD. Data is in status “Pending” only while the system runs the relevant checks and internal processes, but data in status “Pending” cannot be manipulated or visualized.

The high level process for data maintenance in SDD is:

1. An AIXM 5.1 file is received in SDD via AIMSL.

2. Preparation phase: including file integrity check and schema validation.

3. Upload phase: including (AIXM 5.1) business rules check and mapping to SDO.

Forward mapping

All data maintained in 4.5 in SDO is forward mapped to 5.1 features in SDD, except the following ones:

Apron geometry

Obstacle for FATO direction

FATO direction STAR

FATO protection area

FATO protect area geometry

Runway protect area geometry

Special navigation system station

TLOF geometry

TLOF safe area geometry

The exceptions are due to little or no data available in SDO or due to significant differences between the models (e.g. procedure legs).

Backward mapping

The following 5.1 features are backward mapped from SDD to the corresponding 4.5 entities in SDO:

Airport Heliport

Airspace

Airspace Aggreg Comp

Airspace Border

Airspace Corridor

Airspace Derived Geometry

Authority For Airspace

Designated Point

DME

Release 10



Geoborder

MKR

NDB

Organisation Authority

Route

Route Segment

Runway

Runway Direction

TACAN

Unit

VOR

Data Download in AIXM 4.5

All data that is maintained in SDO is available for data download.

For data maintained in SDD, only backward mapped features are available for download (see above).

Data Download in AIXM 5.1

All data that is maintained in SDD is available for data download, except the following features (no data available or lower priority):

Unsupported Features Unsupported Objects

AerialRefuelling AerialRefuellingAnchor

AirportProtectionAreaMarking AerialRefuellingPoint

AirspaceBorderCrossing AerialRefuellingTrack

AltimeterSource AircraftStandContamination

ApronMarking AirportHeliportContamination

DeicingArea AltimeterSourceStatus

DeicingAreaMarking ApronContamination

DirectionFinder AuthorityForAerialRefuelling

FlightRestriction AuthorityForSpecialNavigationStation

FloatingDockSite AuthorityForSpecialNavigationSystem

GuidanceLineMarking DirectFlightClass

MarkingBuoy DirectFlightSegment

NonMovementArea FlightConditionCircumstance

PassengerLoadingBridge FlightConditionCombination

PilotControlledLighting FlightConditionElement

PrecisionApproachRadar FlightRestrictionLevel

PrimarySurveillanceRadar FlightRestrictionRoute

RadarSystem FlightRoutingElement

Road MarkingElement

RunwayBlastPad Meteorology

RunwayMarking RadarComponent

RunwayVisualRange Reflector

SDF Ridge

SeaplaneLandingArea RunwayContamination

SeaplaneRampSite RunwaySectionContamination

SecondarySurveillanceRadar SurfaceContaminationLayer

StandMarking SurveillanceGroundStation

TaxiHoldingPositionMarking TaxiwayContamination

Release 10



TaxiwayMarking TouchDownLiftOffContamination

TouchDownLiftOffMarking UnitAvailability

UnplannedHolding VerticalStructureLightingStatus

WorkArea WorkareaActivity

For data maintained in SDO, all forward mapped features are available for download except the ones listed as exception (see above).

SDD Reporting

See chapter 3.9 below.


Operational User Handbook – Data User, chapter 6


3.2 SDD-AIMSL services for AIXM 5.1 data (CHM-2521, 2522, 2523)

The following AIMSL services are implemented for managing the AIXM 5.1 data in SDD:

1. SDD input process,

Provides the infrastructure for the SDD input process, including the transport of relevant data between different components (business rules validation, backwards mapping, SDO slot management etc.) and the returning of progress notifications to the user.

2. SDD query service,

For returning the current perm data in SDD for the user using AIMSL, via WFS depending on the filtering criteria appplied.

3. SDD insert/update service,

For entering AIXM 5.1 data in SDD via AIMSL, returning either a success indication or failure condition.

Impact on OUH: No


3.3 Business Rules validation component (CHM-2524)

A Business Rules validation component is implemented in order to validate AIXM 5.1 data against defined business rules. This component is accessing AIXM 5.1 data in SDD through the SDD/AIMSL query interface.

Impact on OUH: No


3.4 AIXM 5.1 to 4.5 mapping component (CHM-2525)

An AIXM 5.1 to 4.5 mapping component is implemented in order to provide an AIXM 4.5 representation of the data provided in AIXM 5.1.

Release 10



Impact on OUH: No


3.5 Automated provision from AIXM 5.1 to AIXM 4.5 (CHM-2527)

An automated process is implemented for uploading and slot management of the validated AIXM 5.1 data to SDO after the successful business rule validation.

Impact on OUH: No


3.6 Adaptation of the AIXM 4.5 to 5.1 slot replication/mapping functionality (CHM-2528)

The already existing AIXM 4.5 to 5.1 slot replication / mapping functionality of SDD is modified due to newly introduced AIXM 5.1 capability.

The purpose of this technical change is to prevent the duplicate processing of data maintained and originating from AIXM 5.1 by the existing AIXM 4.5 to AIXM 5.1 slot replication functionality. In other words, backward mapped data must not be forward mapped.

Impact on OUH: No


3.7 Additional AIXM 5.1 features and attributes for SDD download (CHM-2529)

Additional features and objects in AIXM 5.1 are made available for SDD Data Download. The complete list of supported features is as follows:

AeronauticalGroundLight

AircraftGroundService

AircraftStand

AirportClearanceService

AirportHeliport

AirportHeliportCollocation

AirportHotSpot

AirportSuppliesService

Airspace

AirTrafficControlService

AirTrafficManagementService

AngleIndication

ApproachLightingSystem

Apron

ApronElement

Release 10



ApronLightSystem

ArrestingGear

ArrivalFeederLeg

ArrivalLeg

AuthorityForAirspace

Azimuth

ChangeOverPoint

CheckpointINS

CheckpointVOR

CirclingArea

DepartureLeg

DesignatedPoint

DistanceIndication

DME

Elevation

FinalLeg

FireFightingService

GeoBorder

Glidepath

GroundTrafficControlService

GuidanceLine

GuidanceLineLightSystem

HoldingAssessment

HoldingPattern

InformationService

InitialLeg

InstrumentApproachProcedure

IntermediateLeg

Localizer

MarkerBeacon

MissedApproachLeg

Navaid

NavigationArea

NavigationAreaRestriction

NDB

ObstacleArea

OrganisationAuthority

PassengerService

ProcedureDME

RadioCommunicationChannel

RadioFrequencyArea

Route

RouteDME

RouteSegment

RulesProcedures

Runway

RunwayCentrelinePoint

RunwayDirection

RunwayDirectionLightSystem

Release 10



RunwayElement

RunwayProtectArea

RunwayProtectAreaLightSystem

SafeAltitudeArea

SearchRescueService

SignificantPointInAirspace

SpecialDate

SpecialNavigationStation

SpecialNavigationSystem

StandardInstrumentArrival

StandardInstrumentDeparture

StandardLevelColumn

StandardLevelSector

StandardLevelTable

SurveyControlPoint

TACAN

TaxiHoldingPosition

TaxiHoldingPositionLightSystem

Taxiway

TaxiwayElement

TaxiwayLightSystem

TerminalArrivalArea

TouchDownLiftOff

TouchDownLiftOffLightSystem

TouchDownLiftOffSafeArea

Unit

VerticalStructure

VisualGlideSlopeIndicator

VOR

Impact on OUH: Operational User Handbook – Data User, chapter 6


3.8 SDD download available via AIMSL (CHM-2530)

This change exposes the AIXM 5.1 download files from SDD over the AIMSL. User can request AIMSL to be a method for file distribution when requesting AIXM 5.1 data download via EAD Service Desk.

Impact on OUH: Operational User Handbook – Data User, chapter 6.4.2


3.9 SDD reporting via WFM (CHM-2543)

Release 10



The SDD Reporting functionality (similar to SDO Reporting) is introduced, allowing the user to extract static data from SDD in form of reports. This functionality can be accessed via the Data User application by a user having one of the following SDO roles assigned in UMS:

DATA_USER

DATA_PROVIDER_USER

ADMINISTRATOR

A simple WFM based HMI is made available, allowing the user to:

Select an AIXM 5.1 feature-type

Select an effective date range to specify which timeslices shall be provided in the output

Select which AIXM 5.1 feature-properties and objects shall be visible in the output. Additionally the user is able to activate if notes and metadata shall be presented in the output.

The output is presented in HTML or XML formart. Spatial queries in SDD reporting are not yet supported.

Impact on OUH: Operational User Handbook – Data User, chapter 6


Release 10



4 INO Data Provider

The following INO Data Provider changes are deployed with Release 10:

Change Proposal CHM-1634 Enhancement of polygon function

Change Proposal CHM-2497 Illegal character identification

Change Proposal CHM-2157, 2514 NOTAM Proposal enhancements

Change Proposal CHM-2506, 2672 NOTAM Proposal via SSL (EAD Pro)

Change Proposal CHM-2540 NOTAM Proposal via WFM

Change Proposal CHM-2600 Implementation of OPADD 4.0

4.1 Enhancement of polygon function (CHM-1634)

The polygon linking function in INO DP is enhanced to allow user to build the polygon using either:

Coordinates

Navigation Aids (values from SDO)

Designated Points (values from SDO)

The navaids types that can be used for polygon are VOR, DME, TACAN, NDB, MKR.

The user is able to switch between the currently available simple and the newly introduced extended dialog.

Figure 4-2 INO DP – Polygon, simple

For including NAVAIDs or designated points on extended dialog, the user can either:

Enter it manually, in which case system validates it against SDO entries and provides coordinates

Use List of Values (LOV) for searching and picking an entry

In case the "Buffered" checkbox is checked, the retrieval/search is performed with a buffer of 5 NM around the Item A) location.

Release 10



Figure 4-3 INO DP – Polygon, extended

The upload capability on extended screen works the same way as currently on simple screen. User can paste and upload only a list of coordinates (without Navaid/Point information) separated either by linebreaks, commas (,), semicolons (;) or whitespace.

Item E) generation

The user can select if the Item E) text is generated based on the polygon. There are two options (checkboxes):

1. Copy to Item E

Only coordinates are copied to Item E). E.g.

AREA BOUNDED BY:

5054N00432E

5054N00442E

5054N00432E

2. Copy details to Item E

Coordinates and details of selected element (Type, ID, Name) are copied to Item E). E.g.

5054N00432E (BRUSSELS VOR/DME BUB)

5054N00433E

5054N00432E

Impact on OUH: No


Release 10



4.2 Illegal character identification (CHM-2497)

The identification of illegal characters during NOTAM creation that are copy/pasted to Item E) from other text editors (e.g. MS Word) is enhanced.

In case user tries to create a NOTAM with an illegal character in Item E), an error message is displayed: "Illegal character found in text. Please open the Item E) editor to identify it by the hash key (#)".

In such case the operator shall perform the following actions:

1. Open the Item E) editor (via Tools or by double clicking on Item E)

2. Mark "Display non-printable characters" checkbox and click “Refresh” next to it.

a. The non-printable characters are displayed (TAB etc)

b. The illegal (non-ITA2/ITA5) characters are displayed in the form of hash key (#)

3. Operator shall either replace or delete all hash keys (#) displayed

Figure 4-4 INO DP – Item E) editor

Impact on OUH: No


Release 10



4.3 NOTAM Proposal enhancements (CHM-2157, 2514)

Item R on NOTAM Proposal

NOTAM Proposal AFTN format in EAD is enhanced with a new dedicated Item R), to include information that is of administrative nature. This supports NOF operations and their information exchange with originators. Using this field in NOTAM Proposals sent to NOF via AFTN is optional. Example:

(NOTAMN PROPOSAL EBBR A

Q) EBBU/QOBCE/IV/M/AE/000/005/5054N00429E005

A) EBBR B) 1312121212 C) 1312232323

E) THIS OBSTACLE IS IN THE MIDDLE OF NOWHERE.

R) ORIGIN: UNIT 2, USER: BILL BENTLEY)

The information from this new field is not parsed to any real NOTAM Items. It is stored in NOTAM history (similar to operator comments) during NOTAM creation. Additionally the content of Item R) is stored together with the NOTAM proposal and displayed on the new Originator tab pane in the Notes to NOF section, see below.

Figure 4-5 INO DP – List of Unprocessed Proposals, Notes to NOF

Release 10



NOTAM proposal originator information

In addition, the following additional information can be provided together with NOTAM Proposal using different delivery methods and be stored in EAD:

Operator

Accountable Source

Organisation

Notes to NOF

For details, how the information can be provided and how it is stored in EAD, please see the below table:

Proposal List NOTAM history

Originator Operator Accountable Source Organisation Notes to NOF Operator remark

AFTNAFTN originator

address- - - Item R) Item R)

ESIESI user (e.g.:

ed_ESI)- -

Organisation Name

of ESI UMS user

(e.g.: "DFS

DEUTSCHE

FLUGSICHERUNG")

- -

AIMSLAIMSL user (e.g.:

ed_AIMSL)

<Operator>

element

<AccountableSourc

e> element

Organisation Name

of AIMSL UMS user

(e.g.: "DFS

DEUTSCHE

FLUGSICHERUNG")

<NotesToNOF>

<Operator>

<AccountableSource

>

<NotesToNOF>

AIMSL/WFMAIMSL user (e.g.:

ed_DESI)

Non-mandatory

input field on WFM

screen: "Operator"

Non-mandatory

input field on WFM

screen:

"Accountable

Source"

Organisation Name

of AIMSL UMS user

(e.g.: "DFS

DEUTSCHE

FLUGSICHERUNG")

<NotesToNOF>

<Operator>

<AccountableSource

>

<NotesToNOF>

ECIT/HTTPSUMS user (e.g:

INO_g1_SNyarady)

Firs t Name, Last

Name of UMS user

(e.g.: "Szabolcs

Nyarady")

Non-mandatory

input field on

NOTAM proposal

screen:

"Accountable

Source"

Organisation Name

of UMS user

(e.g.: "Group EAD")

Non-mandatory

input field on

NOTAM proposal

screen: "Notes to

NOF"

Accountable Source

Operator

Notes to NOF

Originator tab pane in INOChannel

The originator information provided are displayed for the NOF Operator on the “Originator” tab of the NOTAM Proposal.

Release 10



Figure 4-6 INO DP – List of Unprocessed Proposals, Originator

AIMSL exposure

The following INO operations are newly exposed via AIMSL:

Get NOTAM Proposal Status

Update NOTAM Proposal

Reject NOTAM Proposal

Get System Status

In addition, the already exposed “Submit NOTAM Proposal” operation via AIMSL is extended with:

Multi-language handling

Inclusion and interpretation of Notes to NOF

The new optional "AccountableSource" element as defined in Originator information

Multi-language handling

The NOTAM proposal XML schema is extended by providing the multi-language element the same way as the NOTAM schema. This will allow to submit multi-language NOTAM Proposal to EAD via AIMSL. The provided Item E) language versions are taken to NOTAM upon usage of the proposal.

For supporting this capability, a new tab named “Languages” is introduced in INO DP where different language versions are visible for NOF operator.

Release 10



Figure 4-7 INO DP – List of Unprocessed Proposals, Languages

Impact on OUH: Operational User Handbook – Data Provider, chapter 9.4.4, 9.5, 17


4.4 NOTAM Proposal via SSL (EAD Pro) (CHM-2506)

A new capability is introduced in EAD allowing clients to submit NOTAM Proposals directly from Data User application started via SSL (EAD Pro).

This function is available only for users that have a newly created “PROPOSAL” role assigned for INO DP in EAD User Management System, allowing them to open INO DP screen via SSL (EAD Pro login at www.ead.eurocontrol.int). The user role must be assigned by migrated Data Provider CSO, automatically restricting proposal submission capability to the NOF of that Data Provider.

For the following INO DP user roles the access to INO DP via SSL is granted by the EAD Service Desk during contingency periods only:

DATA PROVIDER

COORDINATOR

ADMINISTRATOR

TAM_PROVIDER

Release 10



Figure 4-8 EAD Pro – INO Menu

The proposal user accessing EAD via SSL is able to use the following functions:

1. Create NOTAM Proposals via a new screen

2. View Sent/Unprocessed NOTAM Proposals

3. Edit and Reject not yet processed NOTAM Proposals

4. View Processed and Rejected NOTAM Proposals

Create NOTAM Proposal

The user can use either a simple or structure mode for entering a NOTAM Proposal. The user can toggle between the modes. The default mode for the organisation is configurable in the Corporate Identity application.

Figure 4-9 EAD Pro – New proposal, simple

The simple mode allows user to enter most of the proposal in free text form or copy/paste from external source.

Mandatory items in simple mode:

Type - prefilled with N, user can change to R or C)

NOF - prefilled, not changeable

Optional items in simple mode:

Release 10



Series of new proposal - input is validated against existing values for the NOF in question, LOV can be used

Series of referenced NOTAM - input is validated against existing values in INO DP

Number of referenced NOTAM - input is validated against existing values in INO DP

Year of referenced NOTAM - input is validated against existing values in INO DP

Text – free text, input not validated

Notes to NOF – free text, input not validated

Accountable Source – free text, input not validated

Figure 4-10 EAD Pro – New proposal, structured

The structured mode allows user to enter the proposal field by field.

Mandatory items in structured mode:

Type - prefilled with N, user can change to R or C)

NOF - prefilled, not changeable

Optional items in structured mode:

Series of new proposal - input is validated against existing values for the NOF in question, LOV can be used

Series of referenced NOTAM - input is validated against existing values in INO DP

Number of referenced NOTAM - input is validated against existing values in INO DP

Year of referenced NOTAM - input is validated against existing values in INO DP

Text – free text, input not validated

Notes to NOF – free text, input not validated

Accountable Source – free text, input not validated

Additionally for the remaining items a basic syntax validation is provided:

Release 10



QFIR: 4 uppercase characters

QCode23 and Code45: 2 uppercase characters

Traffic: max. 2 uppercase characters

Purpose: max. 3 uppercase characters

Scope: max. 2 uppercase characters

Lower and Upper: 3 digits

Coordinates: 4 digits + N|S + 5 digits + E|W

Radius: 3 digits

Item A): 4 uppercase characters (the screen provides the possibility to enter up to 7 Item A) values - each 4 uppercase characters)

Item B): YYMMDDhhmm or WIE

Item C): YYMMDDhhmm or PERM

EST: EST or empty

View Sent/Unprocessed NOTAM Proposals

The proposal user is able to see the list of sent proposals that are not yet processed by the NOF. The list contains only proposals belonging to the organisation that the user is part of. In case the proposal is being processed it is indicated by the red letter L next to the proposal.

From this screen, the proposal user is able to:

Create new proposal based on already existing one

Edit not yet processed proposal

Reject not yet processed proposal

Edit and Reject not yet processed NOTAM Proposals

The proposal user can edit an already sent proposal in case it is not yet undergoing processing by NOF. When the processing is ongoing, the red letter L is indicated and edit is not possible.

During the editing by proposal user, the NOF operator is informed with red letter L that proposal is blocked and not yet available for processing.

The proposal user can also reject an already sent proposal in case it is not yet undergoing processing by NOF. When the processing is ongoing, the red letter L is indicated and reject is not possible. When rejecting, the proposal user asked to select a reason for selection (same as NOF user). After which the proposal is removed from the List of sent proposals

During the rejecting by proposal user, the NOF operator is informed with red letter L that proposal is blocked and not yet available for processing.

Release 10



Figure 4-11 EAD Pro – List of sent proposals

View Processed and Rejected NOTAM Proposals

The proposal user has also access to List of Processed and List of Rejected Proposal (by clicking on queue counter), limited to proposals belonging to its organisation only. This allows the user to see and check the end result of the proposal submitted. On both those list proposal user has only read rights. The new based button is available for creating a new proposal based on any of the ones listed.

Figure 4-12 EAD Pro – List of processed proposals

Release 10



Figure 4-13 EAD Pro – List of rejected proposals

Impact on OUH: Operational User Handbook – Data Provider, chapter 9.5


4.5 NOTAM proposal via WFM (CHM-2540)

A new capability is introduced in EAD allowing clients to send NOTAM Proposals directly from WFM tool to INO Data Provider.

Two new roles are introduced in WFM in order to be able to use this capability: proposal and proposalReviewer and organisations created in the WFM tool can be assigned to a NOTAM Office. A service ticket shall be created for requesting this capability and configuration before starting to use it.

A new process is introduced in WFM for NOTAM Proposal origination:

Release 10



Figure 4-14 WFM – NOTAM Proposal Process

Release 10



A dedicated form is provided to the WFM users starting the NOTAM Proposal Process:

Figure 4-15 WFM – NOTAM Proposal Form

Enter NOTAM Proposal Data

The user shall fill the following fields during “Enter NOTAM Proposal” step of the process.

Mandatory items:

Organisation – filled automatically, not changeable

NOF – filled automatically based on the NOF-Organisation assignment in the WFM tool

Type - selectable from a drop down list (N/R/C)

Optional items:

Series - empty or a capital letter A-Z

Ref Series - empty or a capital letter A-Z

Ref Number – empty or 4 digits

Ref Year – empty or 2 digits

Release 10



Text - text area (limited to max. 4000 characters)

Accountable Source - contact details of the NOTAM proposal originator in free text form, when needed

Notes to NOF - notes for the NOF operator receiving the NOTAM Proposal in free text form, when needed

Review NOTAM Proposal Data

To be filled by a person during “Review NOTAM Proposal” step of the process.

NOTAM Proposal Response

Filled by the system (response from INO DP on the submitted proposal) and can be seen during “Verify/Review response” step of the process.

One of the following NOTAM Proposal Statuses will be shown:

Queued

In Progress

Distributed, including the Full Distributed NOTAM object

Rejected, including the Reject Reason

Error, including Error Code and Error Message

Impact on OUH: Operational User Handbook – Data Provider, chapter 2.9 and 9.5


4.6 Implementation of OPADD 4.0 (CHM-2600)

The following enhancements and changes are introduced in INO DP due to publication of EUROCONTROL Guidelines, Operating Procedures for AIS Dynamic Data (OPADD), edition 4.0.

Ref OPADD chapter 2.3.5.3, Qualifier FIR

A new validation is introduced for supra-national NOTAM creation and processing, checking that the nationality letters in Q-FIR correspond to the nationality letters of the first FIR in Item A).

In case this rule is violated an error is provided, forcing the user to update the NOTAM.

Ref OPADD chapter 2.3.13.6, Qualifier Radius

A possibility to define a radius range for certain NOTAM subjects is introduced based on the below table from OPADD. Those values are managed by EAD staff within NOTAM Selection Criteria (NCS) of EAD. While the range is introduced newly, the possibility of providing default value still remains.

During NOTAM creation and processing it is validated that the radius value in NOTAM is within the range defined in NCS.

In case this rule is violated a warning is provided, asking the user to consider and update of the NOTAM.

Release 10



Figure 4-16 OPADD – Table of default radius indicators

Ref OPADD chapter 2.3.17.3, Item C)

The existing NOTAM validation rule No 1531 is updated. In case 'EST' is used in Item C, no dates and date periods with or without the month are allowed in Item D). Still allowed is DAILY with time specification, 'Day of Week' or 'Day of Week Period' with time specification, and combinations of them.

Examples of allowed entries:

MON WED FRI 1000-1300 1500-1700

DAILY 1000-1200 1400-1600

DAILY 0900-1100, MON-WED FRI 1000-1300

Examples of not allowed entries (in combination with EST in Item C):

DAILY 1700-1900 EXC 01-03

DAILY 1700-1900, 05-08 1000-1200


Ref OPADD chapter 2.3.19.3, Item D)

Release 10



Terms HJ, HN, AND are no longer permitted to be used in Item D) of the NOTAM. A blank shall be used instead of AND, or in case of separating complete schedules a comma should be used.


Ref OPADD chapter 2.5.3.2, Checklist format - Item E)

During the checklist creation in EAD, if there are no valid NOTAM a standard entry is provided to Item E) consisting of current year and term NIL. E.g.

CHECKLIST

YEAR=2015 NIL

Impact on OUH: No


Release 10



5 INO Data User

The following INO Data User changes are deployed with Release 10:

Change Proposal CHM-1236 Enhancement of PIB Scheduling

Change Proposal CHM-2420 PIB query refactoring

Change Proposal CHM-2421 PIB scheduler refactoring

Change Proposal CHM-2559 Common Address Book enhancements

Change Proposal CHM-2598 Webservices: route description for Narrow Route

PIB

Change Proposal CHM-1608 BF-Box improvements

Change Proposal CHM-1937 BF-Box configuration files

Change Proposal CHM-2544 BF-Dynamic PIB Distribution Info with FPL Request

Change Proposal CHM-2551 BF-“Un-map message” function

Change Proposal CHM-2552 BF-"Clear status" enhancement

Change Proposal CHM-2609 BF- Automatic PIB Creation after ACK-reception

5.1 Enhancement of PIB Scheduling (CHM-1236)

PIB scheduling is enhanced with new recurrence patterns that allow monitoring of active NOTAM in form of PIB several days in advance.

In the Schedule panel dialog for daily/weekly/monthly recurrence patterns the user can define:

"PIB Validity Start" value in future either in hours or days.

"PIB Validity End" value in future either in hours or days.

Hour values can be between 1-999, day values can be between 1-99.

Figure 5-17 Data User – Schedule Panel

Release 10



Impact on OUH: No


5.2 PIB query refactoring (CHM-2420)

The production of Full and Update PIBs is optimized on the server side for increased performance and capacity for the EAD users. Several technical optimization measures are implemented.

There is no change on user functionality.

Impact on OUH: No


5.3 PIB scheduler refactoring (CHM-2421)

The PIB scheduling process on the server side is new replaced with independent and transactional-safe scheduler module that will provide increased stability for scheduled PIBs and improve code base maintenance. There is no change on user functionality.

Impact on OUH: No


5.4 Common Address Book enhancements (CHM-2559)

The address book management in EAD remains with default (R9) configuration also after the R10. The change described here is available and can be activated for clients with their own database. A service ticket shall be raised for triggering the migration and configuration accordingly.

Common Address Book management in EAD is updated with the following principles:

The Client External Address Book database will be the master storage point for INODU client information.

EAD Common Address Book reads all data from the client’s directory.

Organization is responsible for maintaining their own client records. Client’s directory shall also be used for storing INODU clients, including notification settings and contact information needed for notifications.

Release 10



Figure 5-18 Data User – Interfaces

The client management application in the Data User GUI is removed and therefore, the Client/Address Management menu item in INO DU application is renamed to “Address Management”.

Defined business rules for ARCID, E-mail and phone number must be applied by organisations managing their own data.

Figure 5-19 Data User – Menu tree

Automated Client Association

A client record can contain a specified ARCID attribute. When an incoming flight plan from IFPS is stored in the Data User 'FPL list', client records are checked to see if their ARCID attribute information matches the flight plan Aircraft ID information. If a match is made, the client's information, such as e-mail addresses, phone numbers, and notification settings is copied into the flight plan. However if more than one match is

Release 10



found, then NO information is copied into the flight plan and no client is notified (by the INODU Briefing Facility notification mechanism for flight plans). The contact information stored in the flight plan is used by the INODU system for sending FPL notifications or distributing a PIB based on the flight plan.

Each organization is able to configure the automated mapping of client contacts to incoming FPLs via respective CI properties in Corporate Identity application. When the CI property 'Automated client data mapping to FPL' is set to 'TRUE' (the default value), client data is automatically mapped to an FPL based on its ARCID information. When the property is set to 'FALSE', no client mapping is done for incoming FPLs of concerned organization.

Also when the property is set to 'False' there no client data are stored in the INO DU system for the back-up purposes.

Back-up

INO DU remains independent of the Client’s Address Book data sources. When client data are received from the Client’s Address Book, the INO DU stores them in a local client database - separately from the flight plans. Information stored in this local client database is not directly connected with any flight plan, but can be used as a data source if the connection to the Common Address Book interface is not available.

Impact on OUH: Operational User Handbook – Data User, chapter 7.1.4

Operational User Handbook – Data Provider, chapter 9.4.10


Users shall be trained using LDAP instead of INO DU Client Management application.

5.5 Webservices: route description for Narrow Route PIB (CHM-2598)

The already existing capability of entering a flight route (without the full FPL) as the basic for Narrow Route PIB creation is made available also via AIMSL. Example of NarrowRoutePIBRequest:

<com:NarrowRouteGeoFilter>

<com:RouteDescription>LKPR DCT LKKV</com:RouteDescription>

<com:RouteWidth>10</com:RouteWidth>

<com:RouteRadiusAD>1</com:RouteRadiusAD>

<com:FIRList>

<com1:FIR>

<com1:ICAO>LKAA</com1:ICAO>

</com1:FIR>

</com:FIRList>

</com:NarrowRouteGeoFilter>

Impact on OUH: No


5.6 BF-Box improvements (CHM-1608)

The following improvements are made to the BF-Box:

The communication part of BF-BOX software, which takes care about concurrent messages processing, is refactored reducing internal dependencies

Release 10



The BF-Box database is improved by adding several indexes to increase the performance of the database's main operations.

The existing AFTN Simulator (used for testing and development) is enhanced to support FMTP.

The existing AFTN Simulator is enhanced with capability to send automatically “ACK” or “REJ” message for the last received "FPL", "CHG", " DLA" or "CNL" message.

Impact on OUH: No


5.7 BF-Box configuration files (CHM-1937)

The server interface for a BF-Box is enhanced allowing reception of configuration files, which are stored in IFS with a date/time stamp in the filename and with the BF-BOX version number.

Additionally the received configuration parameters are stored in in a new DU database table, to be used for investigation or statistical purposes only.

This allows EAD ITP to track BF-Box restart behaviour and reduces the maintenance costs in general.

Impact on OUH: No


5.8 BF-Dynamic PIB Distribution Info with FPL Request (CHM-2544)

The existing capability of dynamic PIB distribution based on FPL (send PIB immediately when FPL is accepted by IFPS, or at defined time before EOBT after acceptance by IFPS) is made available also via AIMSL.

Impact on OUH: No


5.9 BF-“Un-map message” function (CHM-2551)

A new function is introduced for handling messages related to Flight Plan. In case a message has been accidentally assigned to the wrong flight plan, it can be un-assigned using the new “Un-map message” command. This command is available in the flight plan screen by right clicking on the "message" context menu.

Release 10



Figure 5-20 FPL – Un-map message

Impact on OUH: No


5.10 BF-"Clear status" enhancement (CHM-2552)

The existing “Clear status” function for flight plans FPL List is enhanced as follows: when there is only a single reason for clearing the status, the "Clear status" menu label now contains also the reason. The possible options are:

Clear status Long ACK

Clear status Response Timeout

Clear status REJ message

Clear status Slot message

Clear status ALR

Clear status SS Priority message

In case there are multiple reasons, the pop-up dialog requesting the user to make a selection remains without change.

Release 10



Figure 5-21 FPL List – Clear status

Impact on OUH: No


5.11 BF- Automatic PIB Creation after ACK-reception (CHM-2609)

PIB distribution capabilities for a FPL (available in supplementary tab) are enhanced as follows:

User can schedule an automatic delivery of Full PIB to an e-mail either:

Immediately;

Certain time before EOBT

The PIB is automatically delivered only in the following cases:

For IFR FPL subject to IFPS: after reception of ACK message

For IFR FPL not subject to IFPS: after FPL has been distributed

For VFR FPL: after FPL has been distributed

In case of REJ reception, PIB is not distributed.

Figure 5-22 FPL – PIB distribution

Release 10



In addition, the option “Immediately” can be controlled to be by default ticked or not, using a new parameter in Corporate Identity application.

Impact on OUH: No


Release 10



6 AIP

The following AIP changes are deployed with Release 10:

Change Proposal CHM-666 AIXM 5.1 as data source for AIP

Change Proposal CHM-2469 Selecting AIP Sections AD 2, 3, 4, 5 and 6 for

generation based on comparison

Change Proposal CHM-2474 Production tracking tools

Change Proposal CHM-2475 Add/change text in table headings

Change Proposal CHM-2607 Annex 15 Amendment 38 changes to AD 2.19

Change Proposal CHM-2608 Annex 15 Amendment 38 changes to ENR 3.3

Change Proposal CHM-2622 Client side FrameMaker upgrade

Change Proposal CHM-2623 Annex 15 Amendment 37 changes to tables

6.1 AIXM 5.1 as data source for AIP (CHM-666)

With introduction of AIXM 5.1 input in EAD, the AIP tools will be able to use the AIXM 5.1 information provided with the data accessors that make up the eAIP content.

User can select the source via the dropdown list in APS > APS Preferences > Advanced Options... AIXM Version (Tab).

Impact on OUH: No


6.2 Selecting AIP Sections AD 2, 3, 4, 5 and 6 for generation based on comparison (CHM-2469)

This change introduces higher level of automation for Sections AD 2, 3, 4, 5 and 6 during the AIP generation process. It will be possible to select the advanced AD section generation option when generating the eAIP that preselects the above named sections for generation based on data comparison.

Impact on OUH: No


6.3 Production tracking tools (CHM-2474)

This change will allow the AIP editor to view the readiness of all files in a document set based on the check-in remark and a possible status flag. This allows the AIP editor easily to know when a file is ready for generation or has been checked.

The user will be able to:

Assign status to Files during Check in.

Assign status to ranges of files without Check-in.

Define up to 10 Status definitions with Colours.

Clear File status during Generate and Issue.

Release 10



Impact on OUH: No


6.4 Add/change text in table headings (CHM-2475)

This change introduces a capability to add and edit headings in the FrameAPS tables, including insertion of default table headings.

This facilitates the need to have a dual language eAIP, but have the tabular data in dual language tables in the English eAIP only with references from the associated sections in the other language.

Impact on OUH: No


6.5 Annex 15 Amendment 38 changes to AD 2.19 (CHM-2607)

This change introduces upgrade of table designs in AIP section AD 2.19 based on requirements introduced with ICAO Annex 15 Amendment 38.

It includes detailed description of radio navigation and landing aids associated with the instrument approach and the terminal area procedures at the aerodrome.

Impact on OUH: No


6.6 Annex 15 Amendment 38 changes to ENR 3.3 (CHM-2608)

This change introduces upgrade of table designs in AIP section ENR 3.3 based on requirements introduced with ICAO Annex 15 Amendment 38.

It includes detailed description of PBN (RNAV and RNP) routes in the ENR 3.3 Area Navigation Route tables: magnetic bearing to the nearest degree, geodesic distance to the nearest tenth of a kilometre or tenth of a nautical mile between defined end-points and distance between each successive designated significant point.

Impact on OUH: No


6.7 Client side FrameMaker upgrade (CHM-2622)

See chapter 10.6.

Impact on OUH: No


Release 10



6.8 Annex 15 Amendment 37 changes to tables (CHM-2623)

This change introduces general upgrade of table designs in AIP sections ENR 2.8, ENR 3.3, ENR 4.4, AD 2 and AD 3 based on requirements introduced with ICAO Annex 15 Amendment 37.

Impact on OUH: No


Release 10



7 Chart Production

The following Chart Production changes are deployed with Release 10:

Change Proposal CHM-903 Conditional symbolisation on NDP attributes

Change Proposal CHM-2636 Match scale to footprint and vice versa

Change Proposal CHM-2655 Zoom capability for footprint picker

Change Proposal CHM-2656 AIXM 5.1 import from SDD - fix-type elements

7.1 Conditional symbolisation on NDP attributes (CHM-903)

In order to introduce more automation and reduce clean-up work when working with charts, it will be possible to specify rules on NDP attributes to use a specific symbol, label and/or symbology (level, color, style weight) on NDP attribute values. These rules will overrule the standard smartGlobe default symbolisation. This will make it easier to examine and modify the reasoning behind the selection of specific elements.

Impact on OUH: No


7.2 Match scale to footprint and vice versa (CHM-2636)

This change introduces a capability to match a footprint to a scale, automatically picking the smallest scale covering the chart frame from the scale menu, or calculate a custom scale if the custom scale is available for the chart type.

And also other way around: when the user has selected a specific scale and footprint, he/she can enlarge or reduce the footprint automatically to exactly fit the chart frame into the footprint.

Impact on OUH: No


7.3 Zoom capability for footprint picker (CHM-2655)

This change introduces a capability to not only pan but also zoom in the footprint picker maps. This is a better alternative when creating detailed maps for multiple regions as footprint picking on large scale charts is not accurate enough.

Impact on OUH: No


7.4 AIXM 5.1 import from SDD - fix-type elements (CHM-2656)

This change is a first step in the migration towards data import from SDD instead of SDO. This is a technical change and there are no changes to user interface. It will be possible to place fix-type elements as stored in SDD (AIXM 5.1). The data from SDD to Charting is retrieved from the WFS interface.

Release 10



Impact on OUH: No


Release 10



8 Common Services

The following Common Services changes are deployed with Release 10:

Change Proposal CHM-2540 WFM: NOTAM proposal

Change Proposal CHM-2541 WFM: slot information in forms

Change Proposal CHM-2542 WFM: new input box

Change Proposal CHM-2543 WFM: SDD Data Reporting

Change Proposal CHM-2589 CRC32 for data input and output

Change Proposal CHM-2672 New role "PROPOSAL" in UMS for INO DP

8.1 WFM: NOTAM proposal (CHM-2540)

See chapter 4.5 for more details on this change.

8.2 WFM: slot information in forms (CHM-2541)

SDO Update form in WFM tool is changed to allow the selection of a public slot and the private slots from a list (retrieved from SDO) so that the user does not need to enter it manually. The manual entry or overwriting the selected entry from list is still possible.

Public Slot

User can enter an effective date, after which all Public Slots in SDO with that effective date and private slots closing date in future are available for selection. When user selects one of the available Public Slot, all the additional information for this is slot is filled in automatically (public slot name, private slot closing date, commit date, publication date).

Release 10



Figure 8-23 WFM – Assemble SDO Update

Private Slot

After selecting a Public Slot, all private Slots which are assigned to the organisation of the user are available for selection. This can be done via “Update Tasks”. After selecting a private slot the "Reason for change" is filled automatically.

Figure 8-24 WFM – SDO Update Task

Impact on OUH: No


Release 10



8.3 WFM: new input box (CHM-2542)

Request of Data Origination form in WFM tool is enhanced with possibility to select an AIRAC-date from a drop down list. This field is not mandatory and earliest date than can be selected is at least 81 days in the future.

Figure 8-25 WFM – Request of Data Origination

Impact on OUH: No


8.4 WFM: SDD Data Reporting (CHM-2543)


8.5 CRC32 for data input and output (CHM-2589)

Based on data protection requirements as laid down in the European Commission Regulation (EU) 73/2010, storage and retrieval facilities for CRC32Q values will be implemented in EAD.

The implementation is applied to the boundaries of EAD (AIMSL, IFS, CRC GUI). Within the trusted environment of EAD no CRC calculation needs to be done.

Release 10



Figure 8-26 Trusted EAD Environment

Figure 8-27 CRC overview

A new server side CRC API (see above image) is introduced which:

Is capable to calculate the CRC32Q values for provided information (e.g. files, AIMSL messages)

Stores CRC32Q values for provided key/identifier

Retrieves CRC32Q values for provided key/identifier

In addition, a CRC GUI is introduced that is accessible via the EAD Explorer and EAD Pro. The following roles and capabilities are available for the CRC GUI:

Release 10



DATA_USER: can retrieve key/CRC32Q value pairs

DATA_PROVIDER: can retrieve and in addition store key/CRC32Q value pairs, where the CRC32Q value is either manually entered or automatically calculated based on an uploaded file that is discarded afterwards

ADMINISTRATOR (EAD Staff): can retrieve, store and in addition let the CRC application automatically calculate the CRC value for a provided file that is discarded afterwards.

The Client Security Officer can manage the CRC roles (DATA_USER, DATA_PROVIDER, ADMINISTRATOR) for users of his/her organisation. By default, no user has CRC role.

New file operation function “ShowKey” is made available in IFS allowing user to retrieve the key of a file directly in the IFS.

Client AIMSL operations are impacted as follows:

1. CRC checksum can be stored by the client and the associated transaction identifier (key value) can be added to the AIMSL request header.

2. AIMSL will automatically store a CRC checksum for response messages and provide the associated transaction identifier (key value) to the client in the AIMSL response header.

Client ECIT operations impacted as follows:

1. Data Providers uploading data to SDO and PAMS can use CRC HMI provided by EAD to store a CRC Checksum for the file being uploaded.

2. Data Providers receiving data downloads from EAD can use CRC HMI provided by EAD to identify and retrieve the CRC Checksum for the file being downloaded.


Impact on user: See above description. Update of internal procedures to be considered: Yes

8.6 New role "PROPOSAL" in UMS for INO DP (CHM-2672)


Release 10



9 Service Desk

The following Service Desk changes are deployed with Release 10:

Change Proposal CHM-973 Access rights in EAD Knowledge Base

Change Proposal CHM-2601 Jira upgrade (Service Desk)

Change Proposal CHM-2602 Atlassian Confluence upgrade (Knowledge Base)

Change Proposal CHM-2603 Atlassian Crowd Upgrade (SSO)

9.1 Access rights in EAD Knowledge Base (CHM-973)

A dedicated space will be created in EAD Knowledge Base with restricted access (only ITP, DOP, EUROCONTROL and Client organisation NATS). This space will be used by UK NOTAM Office for storing their internal working instructions.

Impact on OUH: No


9.2 Jira upgrade (Service Desk) (CHM-2601)

Jira (the underlying COTS product used for EAD Service Desk application) is upgraded to version 6.4.

Impact on OUH: No


9.3 Atlassian Confluence upgrade (Knowledge Base) (CHM-2602)

Atlassian Confluence (the underlying COTS product used for Knowledge Base application) is upgraded to version 5.7.

Impact on OUH: No


9.4 Atlassian Crowd Upgrade (SSO) (CHM-2603)

Atlassian Crowd (the underlying COTS product used for EAD Service Desk and Knowledge Base Single-Sign-On) is upgraded to version 2.8.

Impact on OUH: No


Release 10



10 Basic Software

The following Basic Software changes are deployed with Release 10:

Change Proposal CHM-2564 Client side Windows upgrade

Change Proposal CHM-2565 Client side Internet Explorer upgrade

Change Proposal CHM-2566 Client side Firefox upgrade

Change Proposal CHM-2567 Client side Java upgrade

Change Proposal CHM-2568 Client side Acrobat Reader upgrade

Change Proposal CHM-2622 Client side FrameMaker upgrade

Change Proposal CHM-2657 Client side Charting upgrade to MicroStation SS3

Change Proposal CHM-2658 Client side Oracle upgrade

Change Proposal CHM-2659 Change of antivirus tool from TrendMicro to McAfee

Change Proposal CHM-2666 Enforce client SSL certificate for the use of EAD Pro

via SSL

10.1 Client side Windows upgrade (CHM-2564)

The operating system on client workstations for EAD is upgraded to Windows 8.1 Professional 64bit. Detailed information is provided directly to all client Managers for necessary preparation before

release deployment.

Impact on OUH: No

Impact on user: The operating system on all client workstations (ECIT and EAD Pro) has to be upgraded to Windows 8.1.

Update of internal procedures to be considered: No

10.2 Client side Internet Explorer upgrade (CHM-2565)

The Internet Explorer on client workstations for EAD is upgraded to version 11 and becomes a secondary supported browser.

Impact on OUH: No

Impact on user: IE on all client workstations (ECIT and EAD Pro) has to be upgraded to version 11.


10.3 Client side Firefox upgrade (CHM-2566)

The Mozilla Firefox on client workstations for EAD is upgraded to version 31 and becomes a primary supported browser.

Impact on OUH: No

Impact on user: Firefox on all client workstations (ECIT and EAD Pro) has to be upgraded to version 31.

Release 10




10.4 Client side Java upgrade (CHM-2567)

The Java version on client workstations for EAD is upgraded to Java 1.8.0_25.

Both browsers in Windows 8.1 (IE 11 and Firefox 31) support only 32bit Java as embedded helper application (jre-8u25-windows-i586.exe).

Impact on OUH: No

Impact on user: Java on all client workstations (ECIT and EAD Pro) has to be upgraded to version 1.8.0_25.


10.5 Client side Acrobat Reader upgrade (CHM-2568)

The Acrobat Reader on client workstations for EAD is upgraded to version 11.0.06.

Impact on OUH: No

Impact on user: Adobe Reader on all client workstations (ECIT and EAD Pro) has to be upgraded to version 11.0.06.


10.6 Client side FrameMaker upgrade (CHM-2622)

The FrameMaker on client workstations for EAD (chart production) is upgraded to version 12.

Impact on OUH: No

Impact on user: FrameMaker on all client workstations (ECIT and EAD Pro) that are used for AIP production has to be upgraded to version 12.


10.7 Client side Charting upgrade to MicroStation SS3 (CHM-2657)

The Microstation on client workstations for EAD (chart production) is upgraded to MicroStation SS3 (08.11.09.459).

Impact on OUH: No

Impact on user: MicroStation on all client workstations (ECIT and EAD Pro) that are used for chart production has to be upgraded to MicroStation SS3 (08.11.09.459).


10.8 Client side Oracle upgrade (CHM-2658)

The Oracle client on client workstations for EAD is upgraded to version 12.1.0.2.

Release 10



Impact on OUH: No

Impact on user: Oracle client on all client workstations (ECIT and EAD Pro) has to be upgraded to version 12.1.0.2.


10.9 Change of antivirus tool from TrendMicro to McAfee (CHM-2659)

The antivirus tool on client workstation for EAD is changed from TrendMicro to McAfee 8.8 Patch 4.

Impact on OUH: No

Impact on user: Antivirus tool on all client workstations (ECIT and EAD Pro) has to be replaced with McAfee 8.8 Patch 4.


10.10 Enforce client SSL certificate for the use of EAD Pro via SSL (CHM-2666)

Gradually more features of EAD are made available via EAD Pro via SSL. In order to ensure complete protection of access, it will be protected with a client authentication based on SSL certificates.

Using EAD Pro after from Release 10 onwards requires a certificate to be installed. Client Managers, please be aware and be ready to install the certificate immediately after release deployment. Detailed

information is provided directly to all client Managers for necessary preparation before release deployment.

Impact on OUH: Operational User Handbook – Data Provider, chapter 3.2

Operational User Handbook – Data User, chapter 3.2, 7.12

Impact on user: Certificate installation required on client workstation in order to access EAD Pro via SSL.

Update of internal procedures to be considered: Yes

Release 10



11 ESI/AIMSL

The following ESI/AIMSL changes are deployed with Release 10:

Change Proposal CHM-2577 ESI: upgrade to Release 10 basic software

Change Proposal CHM-2513 AIMSL: NOTAM proposal enhancements

Change Proposal CHM-2555 AIMSL: Expose SDO and SDD web services

Change Proposal CHM-2588 AIMSL: CRC32 for data input and output

Change Proposal CHM-2690 AIMSL: Common Address Book REST Interface

11.1 ESI: upgrade to Release 10 basic software (CHM-2577)

The ESI client API shall be upgraded and be compatible with:

Upgrade to Java Runtime Environment 8 update 25 (32 bit)

Upgrade to Windows 8.1 Professional 64bit

Impact on OUH: No


11.2 AIMSL: NOTAM proposal enhancements (CHM-2513)

The following INO operations is added to those currently exposed via AIMSL:

Submit NOTAM Proposal

The following additional INO operations are newly exposed via AIMSL:

Get NOTAM Proposal Status

Update NOTAM Proposal

Delete NOTAM Proposal

Get System Status

For more details on NOTAM Proposal enhancements please see chapter 4.

Impact on OUH: No


11.3 AIMSL: Expose SDO and SDD web services (CHM-2555)

The following new/changed SDO and SDD services are exposed via AIMSL:

SDO/AIMSL service extension

The SDO/AIMSL is extended to expose services that are the equivalent of the following existing SDO-DP ESI functionality: SDO Update function for uploading AIXM 4.5 data to a private slot, Slot Management functions for private slot create, check, close, reopen and remove.

Release 10



SDO integration for ADQ Phase 2 changes

The SDO web services are extended to support the following additional requests:

SDD uses the private slot checks of SDO for ensuring AIXM 5.1 data can be backward mapped. For this reason a functionality is needed, which allows to retrieve the status of the backward mapped slot, without the need to loop through all private slots of a public slot. It is also necessary for retrieving the status, in case the default AIMSL response is lost for a technical reason (e.g. hardware failure of the system).

WFM needs all public slots which private slot closing date is not reached. Therefore the existing function RequestPublicSlots is enhanced. A possibility is added to filter slots which private slot closing date is not reached.

SDD download

SDD exposes the download functionality via AIMSL. It will be possible to receive download files from a web service exposed by AIMSL, as well as the IFS.

Insert/update service for AIXM 5.1 data

SDD exposes an insert/update service for AIXM 5.1 data using AIMSL.

Query service for viewing AIXM 5.1 data

SDD exposes a query service using AIMSL which returns a summary of the currently perm data in SDD for the user. The query via SDD-AIMSL shall be implemented via WFS.

Impact on OUH: No


11.4 CRC32 for data input and output (CHM-2588)

See chapter 8 for more details on this change.

11.5 AIMSL: Common Address Book REST Interface (CHM-2690)

The following new service is made available via AIMSL: REST interface of the Common Address Book, for searching client data in searchable Data Sources in order to support B2B communication.

The search result can be filtered on organisational level so that the displayed result is reduced to match the filter.

The following information is available in the Common Address Book Result List and Details View (configurable in Corporate Identity application):

ARCID

SelfManaged

Name

PostalAddress

AFTNAddress

SITAAddress

PhoneNumber

FaxNumber

MobilePhoneNumber

EmailAddress1

Release 10



EmailAddress

NotificationSettings:

o NotificationACK

o NotificationFAM

o NotificationFPL

o NotificationMAN

o NotificationREJ

o NotificationSLOT

o NotificationTEXT

o NotificationProposalStatus

o NotificationPIB

Impact on OUH: No


Release 10



12 Hardware/LAN

The following Hardware/LAN changes are deployed with Release 10:

Change Proposal CHM-2515 Strengthened cryptography by increased

certificate key size

Change Proposal CHM-2517 Use of RADIUS service in EAD

12.1 Strengthened cryptography by increased certificate key size (CHM-2515)

In order to enhance the EAD IT security levels, EAD will transition from the currently used 1024 key size in the VPN and ESI certificates to certificates featuring a 2048 key size.

This will be accompanied by switching to a shared PKI service, which will generate certificates in a publicly trusted chain.

Impact on OUH: No


12.2 Use of RADIUS service in EAD (CHM-2517)

RADIUS stands for Remote Authentication Dial in User Service (RADIUS) and describes a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for users that connect and use a network service.

A new RADIUS server of EAD will serve as interconnection link between the EAD database containing the single source for the EAD user base (UMS) and the VPN infrastructure as well as the web portal.

The radius services enables EAD to use the Online Certificate Status Protocol (OCSP) for the advanced certificate revocation handling.

Impact on OUH: No


Release 10



13 PAMS

No PAMS changes concerning operations are deployed with Release 10.

Release 10



14 Graphical Tools

No Graphical Tools changes concerning operations are deployed with Release 10.

Release 10



15 Abbreviations and Definitions

AFTN Aeronautical Fixed Telecommunication Network

AIC Aeronautical Information Circular

AIMSL AIM Service Layer

AIP Aeronautical Information Publication

AIRAC Aeronautical Information Regulation and Control

AIS Aeronautical Information Services

AIXM Aeronautical Information Exchange Model

ANSP Air Navigation Service Provider

AoR Area of Responsibility

APP Application Server

BF Briefing Facility

CHP Chart Production

CIDIN Common ICAO Data Interchange Network

CM Configuration Management

COTS Commercial of the shelf

CRC Cyclic Redundancy Check

CSO Client Security Officer

DOP-C Data Operation Centre

DTD Document Type Definition

EAD European AIS Database

EC EUROCONTROL

ECAC European Civil Aviation Conference

ECIT (EAD PRO) EAD Client Interface terminal

EDD Element Definition Document

ESI (My EAD) EAD System Interface

FAM Flight Activation Monitoring

FIR Flight Information Region

FTM Free Text Message

GUI Graphical User Interface

ICAO International Civil Aviation Organisation

INO International NOTAM Operation

IT Information Technology

LAN Local Area Network

LOV List of Values

LRI Legal Recording Investigation

MHS Message Handling System

NOF NOTAM Office

NOTAM Notice to Airmen

Release 10



NOTAMC Cancellation of a NOTAM

NOTAMR Replacement of a NOTAM

OPADD Operational Procedures for AIS Dynamic Data

OUH Operational User Handbook

PAMS Published AIP Management System

PIB Pre-Flight Information Bulletin

RWY Runway

SDO Static Data Operation

SDD Static and Dynamic Data

SLS Service Level Specification

SSO Single Sign On

SUP (AIP-SUP) Supplement

SW (Computer) Software

TAM Collective term for: NOTAM, SNOWTAM, BIRDTAM, ASHTAM

TCP/IP Transmission Control Protocol / Internet Protocol

TOC Table of Contents

UE User Extension

UMA User Management Agent

URL Uniform Resource Locator

VPN Virtual Private Network

WAN Wide Area Network

WFM Work Flow Management

WFS Web Feature Service Interface Standard

XML Extensible Mark up Language

Documents

EAD Service Release 10 Content Information - Eurocontrol · EAD Service Release 10 Content Information EAD/DOC-GERJ9Z Version : ... (e.g. CHM-257), ... CHM-2582 SDD Upgrade the applications