ead-release-7.1.pdf

EUROPEAN ORGANISATION FOR THE SAFETY OF AIR NAVIGATION

EUROCONTROL

EAD Service

Release 7 Extension 1

Content Information

EAD/DOC-GER66J

Version : 2.0 Issue Date : 2012/10/22 Status : Approved Deliverable No : No

Distribution EC : Yes

Release 7 Extension 1 Content Information

/35

Version: 2.0 Status: Approved EAD-DOC-GER66J-2.0c-0_R7E1_Content_Information.doc

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 Pegaso City Avda. de Aragón nº 402 Autovía A-2, Km. 14 28022, 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.


/35


Distribution Table

Name Company Department No. of copies

Hardcopy/ Softcopy

Mr Liegeois EUROCONTROL 1 SC

Mr Kummer EUROCONTROL 1 SC

Mr Scherzer FREQUENTIS 1 SC

Mr Berger 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


/35


Change History

Version Date Reason for Change Pages

Affected

0.1 2012-07-05 New document All

1.0 2012-08-28 Updates based on comments received from EUROCONTROL, released version

31-33

1.0 2012-08-28 Approved version --

2.0 2012-10-22 Update: CHM-954 removed 32

2.0 2012-10-23 Approved version --

Status Name Date Signature

Created/updated: R. Vorsmann 2012-10-22 Electronic

Reviewed: B. Kummer 2012-08-28 Electronic

Formally reviewed M. Segovia 2012-07-10 Electronic

Released: R. Vorsmann 2012-10-22 Electronic

Approved CCB: CCB 2012-10-22 REOI


/35


Contents

1 Introduction .......................................................................................................................................... 7

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

2 INO Data Provider ................................................................................................................................ 8

2.1 INO DP: Linking multiple RWY-s to single NOTAM (CHM-733)............................................................ 8 2.2 INO DP: Multilanguage NOTAM templates (CHM-784) ........................................................................ 9 2.3 INO DP: SNOWTAM validation enhancements (CHM-1346).............................................................. 10 2.4 INO DP: Add AFTN address to NOTAM Office (CHM-1396) .............................................................. 11

3 INO Data User ..................................................................................................................................... 12

3.1 INO DU: Route Manager – Route Proposal (CHM-183) ..................................................................... 12 3.2 BF: Improved Filtering (CHM-208) ...................................................................................................... 15 3.3 INO DU: Dynamic FPL and PIB activation (CHM-932) ....................................................................... 17 3.4 BF: Defining Filter tabs for incoming and outgoing messages (CHM-936) ......................................... 21 3.5 BF: “Add to FPL” enhancement (CHM-1103) ...................................................................................... 22 3.6 BF: Handling of DEP/ARR and RQP/RQS messages (CHM-1113) .................................................... 23 3.7 BF: Controlling message distribution (CHM-1136) .............................................................................. 24 3.8 INO DU: NOTAM Text (Item E) filter in PIB (CHM-1425) .................................................................... 25

4 SDO ..................................................................................................................................................... 27

4.1 SDO DP: Temporary backup of deleted slot content (CHM-549) ....................................................... 27 4.2 SDO DP: Adding Hyperlinks in SDO (CHM-692) ................................................................................ 28 4.3 SDO DP: SDO checking rule for arc radius (CHM-876) ...................................................................... 29

5 AIP ....................................................................................................................................................... 31

5.1 AIP: Obstacle Selection and Table Generation (CHM-667) ................................................................ 31 5.2 AIP: Location Indicators table - Predictable IDs with handler (CHM-790) ........................................... 31 5.3 AIP: Display of GEN 0.4 information in subsections (CHM-953) ........................................................ 32 5.4 AIP: Datalinks containing URLs from SDO to be used as hrefs in A-Links (CHM-955) ...................... 32 5.5 AIP: Option to choose to fetch files from local drive for preview HTML (CHM-1008) ......................... 32 5.6 AIP: Option to include date pairs on AIP cover page (CHM-1194) ..................................................... 33

6 Abbreviations and Definitions .......................................................................................................... 34

Contents of Figures

Figure 2-1 INO DP – RWY linking ...................................................................................................................... 8 Figure 2-2 INO DP – NOTAM Template ............................................................................................................. 9 Figure 2-3 INO DP – NOTAM Office Info ......................................................................................................... 11 Figure 3-4 INO DU – New FPL – Route Proposal ............................................................................................ 12 Figure 3-5 INO DU – Narrow Route PIB – Route Proposal .............................................................................. 13 Figure 3-6 INO DU – Route Proposal ............................................................................................................... 14 Figure 3-7 BF – FPL List................................................................................................................................... 15 Figure 3-8 BF – Incoming Messages ................................................................................................................ 16 Figure 3-9 BF – Outgoing Messages ................................................................................................................ 16 Figure 3-10 BF – Flight Plan, Distribution......................................................................................................... 17 Figure 3-11 BF – Flight Plan, Supplementary .................................................................................................. 18 Figure 3-12 BF – FPL List, Context Menu ........................................................................................................ 19


/35


Figure 3-13 BF – PIB List ................................................................................................................................. 19 Figure 3-14 INO DU – Narrow Route PIB......................................................................................................... 20 Figure 3-15 INO DU – Schedule Panel ............................................................................................................ 20 Figure 3-16 BF – FPL List, Add new filter tab................................................................................................... 21 Figure 3-17 BF – Add to FPL ............................................................................................................................ 22 Figure 3-18 Corporate Identity – ARR automatic Update Blacklist .................................................................. 23 Figure 3-19 BF – Connection Status ................................................................................................................ 24 Figure 3-20 BF – Connection to BF-Box lost .................................................................................................... 24 Figure 3-21 INO DU – PIB, Filter 2 ................................................................................................................... 25 Figure 3-22 INO DU – PIB output ..................................................................................................................... 25 Figure 4-23 SDO DP – Warning message ....................................................................................................... 27 Figure 4-24 SDO DP – Edit Private Slot ........................................................................................................... 28 Figure 4-25 SDO DP – Private Slot .................................................................................................................. 29


/35


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 7 Extension 1. 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 by dedicated users.

The structure of this document is as follows:

Chapter 1: Introduction

Chapter 2: INO Data Provider

Chapter 3: INO Data User

Chapter 4: SDO

Chapter 5: AIP

Note:

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

1.2 Changes excluded from the document

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

CHM-127 Common Services Single Data User Applet - Reduction of Download Size

CHM-1044 AIMSL AIMSL Publish/Subscribe Proof of Concept

CHM-1245 Common Services Web Home Briefing Framework - Part 1

CHM-1312 Common Services Upgrade to Joomla 1.7

CHM-1443 INO DU BF - improving memory with FPL caching

CHM-1457 INO DU Change interface implementation for CS interface to BF

CHM-1507 Graphical Tools GT query service implementation based on hibernate framework

Phase1

CHM-1521 INO DP Extend INODP NOF identification algorithm

CHM-1530 Graphical Tools GT query service implementation based on hibernate framework

Phase2

CHM-1571 SDO Create Geoborders spatial geomtery

Following R7E1 changes are excluded from this document due to their administrative (DOP specific) nature:

CHM-939 INO DP Additional reports needed based on service desk tickets

CHM-1619 INO DP NOTAM invalidation for grouped NOTAM

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


/35


2 INO Data Provider

The following INO Data Provider changes are deployed with Release 7 Extension 1:

Change Proposal CHM-733 INO DP: Linking multiple RWY-s to single NOTAM

Change Proposal CHM-784 INO DP: Multilanguage NOTAM templates

Change Proposal CHM-1346 INO DP: SNOWTAM validation enhancements

Change Proposal CHM-1396 INO DP: Add AFTN address to NOTAM Office

2.1 INO DP: Linking multiple RWY-s to single NOTAM (CHM-733)

NOTAM Linking of runways is extended with capability to link more than one runway at a time. Each row of the dialog window contains two fields to allow the entry of one or more runway direction of the particular runway.

Figure 2-1 INO DP – RWY linking

Decode text generation:

When more than one RWY is linked the text is decoded to Item E as follows: all linked runways listed + the condition text (code45) displayed only after the last item:

E) RWY 02/20

RWY 07L/25R CLOSED

Runway auto linkage is also supported by this extension. In case several RWYs are listed, all of them are linked automatically.

Impact on OUH: No

Impact on user: Enhanced RWY linking during NOTAM creation

Update of internal procedures to be considered: Yes

User workflow:

1. Create RWY NOTAM affecting more than one RWY

2. Link all affected RWY directions


/35


2.2 INO DP: Multilanguage NOTAM templates (CHM-784)

NOTAM Template creation is extended with capability to store multi language Templates. The INO DP users are able to view the different NOTAM text versions on the List of Template NOTAM screen using the Language tab pane (see below screenshot).

When Template is selected for NOTAM creation the multi language text versions are filled according to the template.

Figure 2-2 INO DP – NOTAM Template

Impact on OUH: Operational User Handbook Data Provider, new chapter to be introduced

Impact on user: Enhanced handling of NOTAM Templates


User workflow:

3. Create new multi language NOTAM

4. Save as Template

5. Go to List of Template NOTAM

6. Select the saved Template for display or use


/35


2.3 INO DP: SNOWTAM validation enhancements (CHM-1346)

SNOWTAM validation is enhanced with number of new rules and check that are based on requirements introduced with SNOWTAM Harmonisation Guidelines (EUROCONTROL, Edition 1.1, 24-09-2010) and experience that was gained during the past winter season. The checks will support the users in SNOWTAM creation and adhering to the ICAO SNOWTAM syntax.

1. The following current SNOWTAM validation rules shall be categorised as error:

a) Item C) RWY designator Item C) shall contain max 3 characters, of which the first two shall be numerical. Any other combination of characters shall raise an Error.

b) Item C) RWY designator Item C) RWY designator shall be in the range [01-18] only. Any other number shall raise an Error.

c) Item C) RWY designator Item C) 3rd character shall contain one of the following characters only: [L,C,R]. Any other character shall raise an Error.

d) Item F) Deposits Item F) shall contain 3 groups of characters, separated by a slash '/'. The groups shall contain either the text 'NIL', or a combination of the numbers [1-9]. "Any other characters shall raise an Error. Note: Several values for each 3rd is possible, e.g. 87/7/587"

e) Item G) Mean depth (mm) Item G) shall contain 3 groups of characters, separated by a slash '/'. The groups shall contain either the text 'XX', or a combination of the numbers [0-9]. Any other characters shall raise an Error.

f) Item H) Breaking Action the 3 groups shall contain a maximum of 2 digits. If 1 digit is published in each group, the numbers allowed are [1,2,3,4,5,9]. Any other characters shall raise an Error.

2. Adjustments of existing validation rules:

a) a) Item J - format [<hhh>"/"<dd>"L"] shall follow the principle max 3/max 2 digits, allowing also lower than maximum number of characters.

b) b) Item S - Item B) crosscheck deactivated

3. New checks to be introduced:

a) Item C) shall be checked for duplicates: if the same runway is reported more than once, like in the example below it shall be rejected with an error:

A) EDDF B) 11141400

C) 07L F) 5/5/5 G) 25/25/25 H) 87/87/87

C) 07L F) 5/5/5 G) 25/25/25 H) 87/87/87

C) 07L F) 5/5/5 G) 25/25/25 H) 87/87/87

Impact on OUH: No

Impact on user: Enhanced validation and SNOWTAM quality for all users of INO DP


User workflow:

1. Create new SNOWTAM

2. Save and distribute

3. Deviation from defined rules raises an error


/35


2.4 INO DP: Add AFTN address to NOTAM Office (CHM-1396)

A new entry is introduced under Basic Data Maintenance / NOTAM Office: AFTN Address. This entry is filled only by EAD staff for non-migrated NOFs. The entry is used only in case the normal NOF determination of an incoming message is not possible due to regular ambiguities from certain originators.

Figure 2-3 INO DP – NOTAM Office Info

Impact on OUH: No

Impact on user: No impact

Update of internal procedures to be considered: No

User workflow: Not applicable


/35


3 INO Data User

The following INO Data User changes are deployed with Release 7 Extension 1:

Change Proposal CHM-183 INO DU: Route Manager – Route Proposal

Change Proposal CHM-208 BF: Improved Filtering

Change Proposal CHM-932 INO DU: Dynamic FPL and PIB activation

Change Proposal CHM-936 BF: Defining Filter tabs for incoming and outgoing

messages

Change Proposal CHM-1103 BF: “Add to FPL” enhancement

Change Proposal CHM-1113 BF: Handling of DEP/ARR and RQP/RQS messages

Change Proposal CHM-1136 BF: Controlling message distribution

Change Proposal CHM-1425 INO DU: NOTAM Text (Item E) filter in PIB

3.1 INO DU: Route Manager – Route Proposal (CHM-183)

In order to support Flight Plan and PIB management, a Route Proposal mechanism is introduced in EAD. The proposal can be triggered both from Flight Plan and Narrow Route PIB screens. After the user fills the mandatory items, the system will propose several routes. User will be able to compare and edit different proposals and select one of them.

1. New FPL screen.

Following fields are mandatory and shall be filled in to be able to access Route Proposal dialog:

- Aircraft ID

- Flight Rules

- Departure aerodrome

- EOBT

- Cruising Speed

- Flight level

- Destination aerodrome

Figure 3-4 INO DU – New FPL – Route Proposal

2. Narrow Route PIB screen.

Following fields are mandatory and shall be filled in to be able to access Route Proposal dialog:

- Departure aerodrome

- Destination aerodrome

- Flight Rules

- Cruising Speed

- Flight level


/35


Figure 3-5 INO DU – Narrow Route PIB – Route Proposal

3. Route Proposal screen.

Proposal Scope section contains list of FIRs and Points that are either included or excluded (see below screenshot). In order to calculate possible routes:

The user must define FIRs that are included (“Include FIRs”). He can either add them manually or use the button “Detect FIRs” for retrieving all FIRs crossed by the direct line between ADEP and ADES.

The user can define FIRs that he wants to avoid (“Exclude FIRs”).

The user can add specific points that he wants to have included (“Include points”) or avoid (“Exclude Points”) in the route.

If the FPL form already includes a route, this route will be depicted in the Proposed routes section at the first position - label: "Current".

Proposed routes section contains the list of proposed shortest paths. The route has passed the SDO Check is listed as the first in the list. Other proposed paths routes are ordered by ascending EET.

User can select maximum 3 proposed (by holding Ctrl key) and compare them. All the routes selected for comparison are then listed in detailed form below, providing also total distance and EET for each.

User can then select the route that suits best and click “Apply” button. With this action the Route Proposal dialog closes and the route is copied back to FPL or Narrow Route PIB screen.


/35


In addition the updated EET is copied to FPL screen Field 16 in case it was used as starting point). The user is still able to change the EET manually. However, if modified EET is different from the calculated one more than 40%, the user will be informed with an error message.

Figure 3-6 INO DU – Route Proposal

Impact on OUH: Operational User Handbook Data User, Chapter 7.3.5

Impact on user: New functionality supporting Flight Plan and PIB operations


User workflow:

1. Open New FPL Screen

2. Fill in minimum fields (see above)

3. Click “Rte.Prop” button

4. Click “Detect FIRs” button

5. Select a Route

6. Click “Apply” button

1. Open Narrow Route PIB Screen

2. Go to “Route Proposal” tab


/35


3. Fill in all listed fields

4. Click “Propose” button

5. Click “Detect FIRs” button

6. Select a Route

7. Click “Apply” button

3.2 BF: Improved Filtering (CHM-208)

Search/filtering capabilities in Briefing Facility are enhanced as follows:

1. FPL List

a) New text field “Originator” – user can search/filter flight plans based on originator address

b) New checkboxes “IFPS” and “Non-IFPS” – user can search/filter flight plans originating either from IFPS, any other or both.

c) New checkboxes “Dynamic activation: FPL, PIB” – user can search/filter flight plans that have either FPL or PIB dynamic activation assigned (see CHM-932).

d) New checkbox “MIL” – user can search/filter only military flight plans.

e) New checkbox “Internet FPLs” – user can search/filter flight plans that have been submitted via configured webpage (organisation specific).

f) New text field “Free-text” – user can search/filter flight plans by using keyword search.

g) New checkboxes “Flight Rules: I, V, Y, Z” – user can search/filter flight plans based on flight rules.

In case the filtering items are not used/filled, the filter is not applied and all flight plans are listed.

Figure 3-7 BF – FPL List


/35


2. Incoming Messages

a) New checkboxes “ATFCM, IFPS, Non-IFPS” – user can search/filter incoming messages based on the type of originator.

b) New drop down item “Addressee” – user can search/filter incoming messages by selecting a single AFTN address used as addressee in the messages.

c) New checkboxes “All, Ambiguous, Information” – user can search/filter incoming messages based on category.

In case the filtering items are not used/filled, the filter is not applied and all incoming messages are listed.

Figure 3-8 BF – Incoming Messages

3. Outgoing Messages

a) New drop down item “Originator” – user can search/filter outgoing messages by selecting single AFTN address.

b) New checkboxes “ATFCM, IFPS, Non-IFPS” – user can search/filter the outgoing messages based on the type of the addressee.

c) New text boxes “ARCID, ADEP, ADES” – user can search/filter outgoing messages by filling these specific ATS Message items as filter criteria (e.g. all messages where departure aerodrome is EDDF).

d) New checkboxes “All, Not distributed” – user can search/filter outgoing messages by either showing all or only the ones that have not yet been distributed.

Figure 3-9 BF – Outgoing Messages

Impact on OUH: No

Impact on user: Enhanced filtering possibilities



/35


User workflow:

1. Access Data User

2. Go to Briefing/Flight Plan/My Flight Plans

3. Use the described filtering possibilities

3.3 INO DU: Dynamic FPL and PIB activation (CHM-932)

The following enhancements are introduced allowing better planning and service delivery for FPL/PIB users.

1. Dynamic FPL activation

A new checkbox “Distribute” is added to the FPL form, which allows the user to set time at which the FPL will be automatically distributed as a number of hours and minutes before EOBT. Previous checkbox "Distributed" is renamed to "Mark as distributed" to make its meaning clearer and to avoid confusion. When “Distribute” checkbox is used, the Send button is disabled.

Default value of FPL distribution is set for 22:00 hours before EOBT. The default value can be modified via Corporate Identity application.

Figure 3-10 BF – Flight Plan, Distribution

2. Dynamic PIB activation

A new checkbox “Generate and distribute PIB” is added to the Supplementary tab of the FPL form allowing user to easily set one-time distribution of PIB at certain time before EOBT.


/35


Default value of PIB distribution is set for 02:00 hours before EOBT. The default value can be modified via Corporate Identity application.

Figure 3-11 BF – Flight Plan, Supplementary

When the flight plan is saved or sent, a temporary Narrow Route PIB profile with one time schedule is created automatically. The temporary profile is deleted after the flight becomes inactive.

When the EOBT of the flight is changed (via FPL form or by CHG or DLA message); the time of distribution is automatically updated accordingly.

As Narrow Route PIB can only be generated if the route has passed SDO check, restrictions apply:

a) “Distribute PIB” checkbox in FPL form is enabled only after successful SDO check

b) When value of field 15 is changed and before generating and distributing a scheduled PIB profile, SDO check shall be executed. If it is not successful, the associated flight plan shall be marked with a red exclamation mark and moved to the Red queue (Important messages) in the flight plan list

The new items are also available as columns in FPL List together with an updated context menu (right mouse click) allowing the user create the PIB in HTML at any point in time (see below screenshot). If there has been a problem with PIB distribution, a red exclamation mark is displayed.


/35


Figure 3-12 BF – FPL List, Context Menu

3. PIB list

A new tab “PIBs” is added to the PIB profile form. It contains a list of already generated PIBs with a possibility of showing all PIBs or just PIBs which have been created based on the currently opened PIB profile.

Figure 3-13 BF – PIB List

4. PIB Profile

The new one-time distribution capability is also introduced at the PIB Screen, both on Distribution tab and Schedule Panel when defining the Recurrence Pattern.


/35


Figure 3-14 INO DU – Narrow Route PIB

Figure 3-15 INO DU – Schedule Panel


/35


Impact on OUH: No

Impact on user: Enhanced scheduling possibilities


User workflow:

1. Access Data User

2. Go to Briefing/Flight Plan/New FPL

3. Create a new FPL

4. Perform a successful “SDO Check” of the Route

5. Define automatic FPL distribution at certain time by filling in “Distribute xx:xx before EOBT”

6. Go to Supplementary Tab

7. Define automatic one-time PIB delivery at certain time by filling in “Generate and distribute PIB xx:xx before EOBT”

3.4 BF: Defining Filter tabs for incoming and outgoing messages (CHM-936)

This change introduces the capability to add a several "View (tabs)" at the Incoming and Outgoing messages, similar to "Multiple Flight plan list tabs".

In the "My Flight Plans" application, after clicking on "(+)" to add a new tab, the user is asked whether to add a new tab with FPL List filter, Incoming Messages filter or Outgoing Messages filter. The default option is based on the tab that is currently active.

The "Common tab" choice is available only for BF_SUPERVISOR role. Checking it will cause adding the new TAB for all users of the organization.

Figure 3-16 BF – FPL List, Add new filter tab


/35


Impact on OUH: No

Impact on user: Enhanced view capabilities


User workflow:

1. Access Data User

2. Go to Briefing/Flight Plan/My Flight Plans

3. Click on + sign to add a new tab

4. Select the type of data for the tab

5. Click “Accept”

3.5 BF: “Add to FPL” enhancement (CHM-1103)

Currently, "Add to FPL" only adds a selected message to an existing flight plan. This process is enhanced. Here are the steps describing the new workflow that is applicable only for ambiguous and not free text messages: DEP, DLA, CNL, CHG and ARR.

1. Select and ambiguous message (yellow) from the Incoming Message queue

2. Right click the message and use “Add to FPL”

3. Select the FPL that the message shall be associated with

4. The FPL opens, showing the associated messages on the right side

5. Right click the desired message and use “Apply” – with this the FPL is updated

6. Click “Save”

7. In case the content of the FPL was changed, the user is asked whether an update message shall be sent to the associated FF addresses. If the user agrees, update message will be sent.

Figure 3-17 BF – Add to FPL


/35


Impact on OUH: No

Impact on user: New procedure for associating ambiguous messages to FPL


User workflow: See above

3.6 BF: Handling of DEP/ARR and RQP/RQS messages (CHM-1113)

New properties are made available in Corporate Identity for Administrators of the organisation:

DEP/ARR Automatic Update Blacklist

RQP/RQS Automatic Update Blacklist.

These properties allow the organisation to define a list of AFTN addresses or AFTN address wildcards (two or more beginning characters) to be checked upon message reception. If a message of the defined type arrives from one of the specified addresses, the FPL List is not updated it goes automatically to ambiguous messages.

This supports the units where automatic handling of messages is not always beneficial and ARO operators need to be aware on certain incoming messages.

Figure 3-18 Corporate Identity – ARR automatic Update Blacklist


Impact on user: New general property for handling incoming messages in BF


User workflow:

1. Access Corporate Identity application

2. Define a blacklist entry either for ARR, DEP, RQP or RQS message

3. The entry is applicable for all the user within the organisation


/35


3.7 BF: Controlling message distribution (CHM-1136)

A new safety mechanism is introduced for messages transmission from BF to BF-BOX and out to AFTN. In case the message that is created does not reach the BF-Box (due to system failure or network problem), the distribution process is repeated several times. All messages waiting for distribution to AFTN are marked in the list of Outgoing Messages with a red exclamation mark and the entire row is marked red after certain time.

In case the connection is not re-established a Connection Status will show a yellow indicator: BF-Box connected, but there is a problem on the AFTN gateway.

Figure 3-19 BF – Connection Status

In case the connection problem to BF-Box and AFTN is temporary and the connection is restored, the messages will be distributed automatically and the colour on the list becomes white again.

In case the connection to BF-Box and AFTN is not solved, the user informed by an error message requesting the restart of both application and BF-Box.

Figure 3-20 BF – Connection to BF-Box lost


/35


Impact on OUH: No

Impact on user: Improved identification and control of connection loss and distribution of messages


User workflow: See above

3.8 INO DU: NOTAM Text (Item E) filter in PIB (CHM-1425)

The NOTAM filtering for PIB generation is enhanced allowing users to use keyword filtering. User is able to add keywords (e.g "strike") or strings of keywords (e.g. "bird strike") one by one on Filter 2 pane of all PIBs. The keywords will be presented in a scrollable list. User shall be able to select from two filtering options:

1. To Be Included, equivalent to "Any of the selected"

2. All Except, equivalent to "None of the selected"

The NOTAM Text filter is always applied in combination with one of the other selected filters on tab Filter 2 (see below screenshot). Only NOTAM matching all defined filters are provided in the PIB.

Figure 3-21 INO DU – PIB, Filter 2

Figure 3-22 INO DU – PIB output



/35


Impact on user: New filtering capability in PIBs


User workflow:

1. Access Data User

2. Go to any PIB screen

3. Define entries on tab “Filter”

4. Define keyword filter on tab “Filter 2”

5. Click generate or save the profile


/35


4 SDO

The following SDO changes are deployed with Release 7 Extension 1:

Change Proposal CHM-549 SDO DP: Temporary backup of deleted slot content

Change Proposal CHM-692 SDO DP: Adding Hyperlinks in SDO

Change Proposal CHM-876 SDO DP: SDO checking rule for arc radius

4.1 SDO DP: Temporary backup of deleted slot content (CHM-549)

A new mechanism is introduced for backing up the content storing it in IFS as AIXM file in case a private slot is deleted. This function is available in the following situations:

Upon manual deletion of a private slot (via HMI)

Upon automatic deletion of a public slot (when reaching its effective date)

In case of manual deletion, the user is always provided a message asking if the backup shall be performed or not.

Figure 4-23 SDO DP – Warning message

The completion of all backups is also announced with appropriate message in the SDO message window. The IFS subdirectory to which slot content backup files are saved is a configurable per organisation via Corporate Identity application.

Impact on OUH: Operational User Handbook Data Provider, new chapter to be introduced under 6.3

Impact on user: New functionality


User workflow:

1. Access SDO Data Provider application

2. Create a Private Slot

3. Make data updates and save them in the Private Slot

4. Delete the Private Slot

5. Message “Do you want to perform backup...” Select Yes.

6. Consult the message in SDO Message Screen for name and location of the backup file (AIXM)

7. Retrieve the AIXM file from IFS


/35


4.2 SDO DP: Adding Hyperlinks in SDO (CHM-692)

A new functionality is introduced allowing users to add hyperlinks in the “Reason for Change” field of private slot. The entry can be either a valid internet source (http://www.eurocontrol.int) or even a local/internal path (file:///X:/my/network/file.doc). It is the user’s responsibility to assure that the link provided is a valid one.

All hyperlinks shall be entered at the Private Slot edit screen by using square brackets e.g. [http://www.eurocontrol.int/].

Figure 4-24 SDO DP – Edit Private Slot

Hyperlinks are displayed as clickable links in the Private Slot screen and on Trace tab page of all the entities. The links are opened within the default browser on the workstation when clicking on them.

http://www.eurocontrol.int/


/35


Figure 4-25 SDO DP – Private Slot

Impact on OUH: No

Impact on user: Additional functionality


User workflow:

1. Access SDO Data Provider application

2. Create a Private Slot

3. Insert a hyperlink to the field “Reason for change” with square brackets [http://www.eurocontrol.int/]

4. Save the Private Slot

4.3 SDO DP: SDO checking rule for arc radius (CHM-876)

A new SDO checking rule on the entity AIRSPACE_VERTEX is introduced, in order to compare the entered value for the radius with the one calculated by the system:

"If CODE_TYPE='CWA' or 'CCA', then the radius of the arc given by VAL_RADIUS_ARC and UOM_RADIUS_ARC and the calculated radius shall not differ by more than 1%."

The rule raises an error on category B checking (Private Slot).


/35


Impact on OUH: No

Impact on user: New SDO rule raising an error, mismatching radius values are no longer allowed




/35


5 AIP

The following AIP changes are deployed with Release 7 Extension 1:

Change Proposal CHM-667 AIP: Obstacle Selection and Table Generation

Change Proposal CHM-790 AIP: Location Indicators table - Predictable IDs with

handler

Change Proposal CHM-953 AIP: Display of GEN 0.4 information in subsections

Change Proposal CHM-955 AIP: Datalinks containing URLs from SDO to be

used as hrefs in A-Links

Change Proposal CHM-1008 AIP: Option to choose to fetch files from local drive

for preview HTML

Change Proposal CHM-1194 AIP: Option to include date pairs on AIP cover page

5.1 AIP: Obstacle Selection and Table Generation (CHM-667)

This change introduces a new table style in FrameAPS that has the look of the new AD 2.10 table described in ICAO Doc 8126. The selection criteria however will remain the same:

"Approach/TKOF" areas and

"In Circling Area and at AD table"

This will take the place of the obstacles in area two and three table, and will be suitable for use in AIP sections AD 2.10, AD 3.10 and AD 4.10. The existing table also remains available.

Impact on OUH: No

Impact on user: Yes


User workflow:

1. Access FrameAPS

2. Go to “Insert AIP Table”

3. Use drop down menu to select new table design

5.2 AIP: Location Indicators table - Predictable IDs with handler (CHM-790)

The process for adding a new AD/HP to AIP is simplified/supported by the following enhancements:

1. The system automatically references new ADHP files to the GEN 2.4 via the REF attribute.

2. The IDs used to reference aerodromes to corresponding encode decode tables will be generated from the CODE_ID of the aerodrome and thus shall be predictable.

3. The system handles all format variants of GEN 2.4 table (i.e. Encode / Non-ICAO Encode / Decode etc) consistently.

4. The system handles the updating of the REF from GEN 2.4 in AD 4, AD 5 and AD 6 files consistently.


/35


Impact on OUH: No

Impact on user: Yes



5.3 AIP: Display of GEN 0.4 information in subsections (CHM-953)

A change is introduced allowing users to enhance the Gen 0.4 section for publishing of the AIP paper version. An updated EDD file is introduced which allows the GEN 0.4 (PDF) file to show the "List of changes" pages/dates in sections, including the section title, such as GEN 0, GEN 1, GEN 2, etc.

Impact on OUH: No

Impact on user: Yes



5.4 AIP: Datalinks containing URLs from SDO to be used as hrefs in A-Links (CHM-955)

A new option is introduced under advanced Options allowing the user to change an existing address datalink of type URL to a URL Datalink that automatically updates the HREF information during generation. This increases automation to eAIP output.

An additional function is introduced that allows the user to change the behaviour of an address datalink of type URL to automatically pick up the correct HREF information when the underlying data changes.

Impact on OUH: No

Impact on user: Yes



5.5 AIP: Option to choose to fetch files from local drive for preview HTML (CHM-1008)

When a “Preview HTML” action is currently performed, it fetches all of the files from the database. This enhancement provides a toggled on/off checkbox to allow the user to choose whether the system should get the files from the database or from the local work directory.

Files retrieved from the local drive will be faster than retrieval from the database increasing the user productivity.

Impact on OUH: No


/35


Impact on user: Yes



5.6 AIP: Option to include date pairs on AIP cover page (CHM-1194)

This change introduces a possibility to select whether the cover page of AIP AMDT shows only the dates of first page (front) or of both pages (front and back).

A Check Box is added to “Create Cover Page” dialogue where user can choose the preferred option.

Impact on OUH: No

Impact on user: Yes




/35


6 Abbreviations and Definitions

3D Three dimensional space

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

CFMU Central Flow Management Unit

CHP Chart Production

CIDIN Common ICAO Data Interchange Network

CM Configuration Management

COTS Commercial of the shelf

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

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

LRI Legal Recording Investigation

MHS Message Handling System

NOF NOTAM Office

NOTAM Notice to Airmen


/35


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

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

WFS Web Feature Service Interface Standard

XML Extensible Mark up Language

ead-release-7.1.pdf

Documents

approved version

sc release

sc mr kummer eurocontrol

sc mr kraft groupead

sc mr schaefer frequentis

sc mr berger frequentis

sc mr scherzer frequentis

content information