The presentation to Externals of the NM23.0 Release via - - PowerPoint PPT Presentation

nm.releases@eurocontrol.int

The presentation to Externals of the NM23.0 Release via video-conference took place on the 18th of February 2019. Unfortunately during the presentation we experienced some issues with the audio feature; the audio quality of the recording may therefore be lower than expected for some Functional Blocks. Please find below:

• The recording: https://youtu.be/mZdpERqRD7o
• The link toward the NM23.0 Release Notes:

https://www.eurocontrol.int/publication/network-manager-release-notes-planned-implementation- 2019-2020

• The slides used during the Presentation (below in this pdf)
• This document is available on the public website (as a pdf) at:

https://www.eurocontrol.int/library?f%5B0%5D=activity%3A774

EUROCONTROL – Network Manager Directorate 18/02/2019

v1.2 Classification TLP : White (Public)

Presentation of NM23.0 to Externals

nm.releases@eurocontrol.int 3

Welcome to the Presentation of NM23.0 to Externals

Agenda

1- Introduction and interface set-up 2- NM23.0 Release presentation: 2.1- Important notifications related to NM23.0 OPT (operational testing) session 2.2- FBs (Functional Blocks) presentation 3- Way forward toward NM23.0 migration

nm.releases@eurocontrol.int 4

1- Introduction: Recording

Presentation is recorded; recording (audio and slides) will be available

• n the Eurocontrol public website in a few days:

https://www.eurocontrol.int/library?f%5B0%5D=activity%3A774 (This URL available in §1 of the NM Release Notes: https://www.eurocontrol.int/publication/network-manager-release-notes- planned-implementation-2019-2020)

nm.releases@eurocontrol.int

1- Introduction

5

• Goals of the presentation:
• Present the new features of the Release NM23.0.
• Operational Project Managers will present their Functional Block.
• Enable you to assess the impacts on your procedures or systems.
• Ask questions (today after each FB presentation, or by eMail at

nm.releases@eurocontrol.int).

• Why doing the presentation now?

⇒ SHOM2 Gate (Software Hand-Over Meeting) is passed. ⇒ System testing and Operational Acceptance testing are still on- going, so Release content may slightly change until the Release migration.

nm.releases@eurocontrol.int 8

2- NM23.0 Presentation

nm.releases@eurocontrol.int

2.1- The NM Release Notes

9

• The NM Release Notes contains the latest information on Releases:
• OPT (Operational Testing) Session information, OPT guide, etc.
• Webex presentation information (including slides and recording)
• Release migration plan per system and services
• Releases important notifications
• Release content in a structured format
• Release Notes are available at:

https://www.eurocontrol.int/publication/n etwork-manager-release-notes-planned- implementation-2019-2020 To receive information on the Release (including NM Release Notes updates, OPT information, presentations, etc.): subscribe to the mailing (cf. §1 of the NM Release Notes)

nm.releases@eurocontrol.int

2.1- NM23.0: The OPT (Operational Testing) (Release Notes §4.1.3)

10

NM23.0 will be available for testing with the OPT (operational testing) session!

• NM23.0 OPT session will start on the 28th of February and end on the 28th of March.
• With the NM23.0 OPT you are able to:
• Test NM23.0 on your systems with your procedures.
• Download and test the new NM23.0 CHMI.
• Test the new NM23.0 NOP Portal.
• Test some new FBs (operational scenario provided in the OPT guide).
• B2B: NM23.0 will be available on PREOPS (as from 01/04/2019-14:00 UTC)
• All you need is to already have access to NM systems. No registration required

(unless you want to exchange FPL messages with OPT platform).

⇒ Questions: nm.opt@eurocontrol.int

nm.releases@eurocontrol.int

2.1- NM23.0: Important notifications (Release Notes §2.2)

11

• Browsers recommended in NM23.0:
• n-CONECT HMI does not work with Internet Explorer; for this HMI, we

recommend Chrome or FireFox.

• For other NM services:
• Internet Explorer 11
• Edge
• FireFox
• Chrome

The NM web-based HMIs will have been fully tested on Internet Explorer 11, Edge and FireFox. For these recommended browser brands, NM undertakes to investigate and attempt to resolve problems that can be reproduced on the latest stable version of that brand. (Anything else is on a “best efforts” basis.)

• The recommended operating system is Windows 10.

Issues reported on CHMI using Windows 7 will be fixed on a best effort basis.

• NM B2B: Decommission of NM B2B NM21.0 webservice.

nm.releases@eurocontrol.int

Any questions?

12

nm.releases@eurocontrol.int

2.2- NM23.0 FBs and CRs presentation

13

Only new features impacting operations and Externals are presented

FB FB Title Performance Work Programme FB973 Performance Work Programme ATFCM evolutions FB1001 ATFCM Domain improvements CR_043914 TACT activation versus Expecting FSA & AOWIR services FB917 DCB Measure proposal via B2B e-HelpDesk FB1019 e-HelpDesk improvements Airspace Data evolutions FB971 NM airspace data model evolution FB1000 Airspace Data Domain improvements FB943 Airspace Flight Planning evolutions FB999 Flight Planning Domain improvements FB972 ASM - Advanced FUA process improvement FB977 Rerouting Evolutions FB1012 FF-ICE filing Function - file eFPL Airport Programme FB975 Airport Programme FB992 DPI Improvements Other evolutions FB958 Correction and tuning of the external data processing FB980 Predictability: Yo-Yo flight plans identification NM23.5 CR_040712 NM plans to allow Aerodromes with no ICAO or IATA identifier into CACD

FB973: Performance Work Programme

v1.2

Change to delay computation

nm.releases@eurocontrol.int

1- Background – Why

• Short background of the FB:
• Why was it developed? There is a need to compute the ATFM delay based on

real operational parameters and milestones.

• What was the business need? To produce a consistent an correct ATFM delay

dashboard.

• What was the problem it intends to solve? Unrealistic computation of ATFM delay

in specific circumstances.

• What are the benefits? Correct ATFM delay computation and tracking of related

targets.

• What are the possible next steps? Continue the work on ATFM delay and

perform the required system changes.

15 FB973: Performance Work Programme

nm.releases@eurocontrol.int

2- Impact of the FB

• Stakeholder(s) impacted :
• Flow Manager (FMP)
• Post-ops analyst
• CDM-Airport
• Air Navigation Service Provider (ANSP)
• Other (specify)

16

FB xxx

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Yes Data structure Yes User Interface Yes Procedures Training Yes B2B Yes Other

FB973: Performance Work Programme

nm.releases@eurocontrol.int

2- Impact of the FB

• TTOT change in the DPI-s messages
• aircraft operator update of the TOBT - 57% of the cases
• TSAT updates - 14%
• insufficient data (missing TOBT/TSAT data) - 29%
• There is a need to adjust the model to compute the ATFM delay associated

to DPI-S re-computations.

• This requires a change in the reporting and operational systems

19 FB973: Performance Work Programme

nm.releases@eurocontrol.int

3- New features

• NM will adapt the ATFM delay calculation to use the latest OBT (i.e. TOBT)
• f 3.9% saving of en-route ATFM delays and 1.7% of airport ATFM delays.
• NM will go further and use the TOBT information in DPIs messages in the

ATFM delay calculation wherever appropriate.

• The ATFM computation will consider the last TOBT available in the CDM

message information (including DPI-S)

• ATFM delay will be: CTOT(from NM) - (TOBT + last received 'AO' taxi time)

20 FB973: Performance Work Programme

nm.releases@eurocontrol.int

4- Summary

• TTOT change in the DPI-s messages
• NM will adapt the ATFM delay calculation to use the latest OBT
• NM will go further and use the TOBT information in DPIs messages

in the ATFM delay calculation wherever appropriate.

• Changes targeted at 2019 release programme
• PRB should note the changes for RP3 preparation

21 FB973: Performance Work Programme

nm.releases@eurocontrol.int

Questions

Any questions?

22 FB973: Performance Work Programme

FB1001: ATFCM Domain improvements

v1.1

Presentation of NM23.0

FAM reduction to 20 minutes

nm.releases@eurocontrol.int

1- Impact of the FB

• Stakeholders impacted:
• Flow Manager (FMP)
• Airspace User (Civil)
• AO or CFSP
• Non-CDM Airport
• CDM-Airport
• Air Navigation Service Provider (ANSP)

24

FB 1001

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Yes Data structure User Interface Procedures Yes Training Yes B2B Other

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB1001: ATFCM Domain improvements

nm.releases@eurocontrol.int

1- Impact of the FB

2nd step of the reduction of the FAM parameter from 25 to 20 minutes CR_044350: FAM parameter reduction External impact mainly on FMP, AO/CFSP and Airports/TWRs in terms of:

• Procedures;
• Client systems.

25 FB1001: ATFCM Domain improvements

nm.releases@eurocontrol.int

2- New features

• FAM is applied on all flights, whether regulated or not, that are:
• departing from
• landing in
• crossing

an area where CPRs are received by the NM and FAM is activated.

• 25 minute FAM parameter is reduced to 20 minutes – applies on flights
• departing from, landing in or crossing (with less than 3 hour flying time to) areas where CPRs are

received by the NM and FAM activated.

• No change - 120 min FAM parameter – applies on flights
• departing from non-FAM-enabled areas but with a destination in or crossing a FAM enabled area with

more than 3 hours flying time to the FAM enabled area;

26 FB1001: ATFCM Domain improvements

nm.releases@eurocontrol.int

• FAM applicability

27

1.

X

2.

X

= FAM enabled CPR-covered areas

3.

X

FAM parameter: 20 minutes FAM parameter 20 minutes for EET less than 3 hours FAM parameter 120 minutes for EET more than 3 hours FAM parameter 20 minutes for EET less than 3 hours FAM parameter 120 minutes for EET more than 3 hours

2- New features

FB1001: ATFCM Domain improvements

nm.releases@eurocontrol.int

3- Background

Reduction of FAM parameter from 25 to 20 minutes

• After consultation and approval of ODSG/41 the 30 min FAM parameter will

be gradually reduced to 15 min by 5 min step every NM Release;

• NM22.5: first step of reduction from 30 min to 25 min;
• NM23.0: second step of reduction from 25 min to 20 min;
• Objective
• improve network predictability and reinforce IFPS compliance (checking updated

EOBT);

• In addition, according to ICAO Doc 7030 any changes to the EOBT of more than

15 minutes for any IFR flight within the IFPZ shall be communicated to the IFPS which further supports the FAM parameter adaptation.

• Follow-up/Results of the change will be presented at the next ODSG &

AOG meetings;

• Further information is available at:

http://www.eurocontrol.int/articles/enhanced-tactical-flow-management- system-etfms

• Or contact: nmfamreduction@eurocontrol.int

28 FB1001: ATFCM Domain improvements

nm.releases@eurocontrol.int

Questions

Any questions?

29 FB1001: ATFCM Domain improvements

CR_043914: TACT activation versus Expecting FSA & AOWIR services

v1.1

Presentation of NM23.0

nm.releases@eurocontrol.int

1 - Background

TACT Activation and FSA Expected

32

A flight is TACT Activated if:

• the clock reaches ETOT/CTOT
• At the reception of T-DPI-s/A-DPI for non-regulated flights or a

compliant T-DPI-s/A-DPI for a regulated flight. Once the flight is TACT Activated, a flight is flagged either:

• with no FSA expected
• with FSA expected

A flight is flagged as TACT Activated with FSA expected if departs from a aerodrome where departure FSA are received

• These aerodromes are set in ENV as part of an Aerodrome Set

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int 33

1 - Background

TACT Activation and FSA Expected

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int

1 – Background (Limitation 1)

Flights departing from the A-CDM aerodromes are not flagged as TACT Activated with FSA Expected

34 CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int

1 – Background (Limitation 1)

TACT Activated flights departing from an A-CDM aerodrome are not subject to AOWIR function

35 CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int 39

2 – Functional Improvements

The NM plans to remove the early TACT activation by T-DPI-s in order to:

• Solve the deficiencies on the expecting FSA mechanism for A-

CDM departures reported by Flow Management Units.

• Support DCB activities by improve the count details and the flights

lists information (see impact).

• Overcome the Aircraft Operators What-It rerouting (AOWIR)

limitations reported by Aircraft Operators.

• Simplify the current complexity of the flight status structure

experienced by the ATM community.

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int

3- Impact of the change

42

Service affected Flight Planning Flow Aeronautical Information /AS data Reporting Other Internal computation Yes Data structure User Interface Yes Procedures Yes Training Yes B2B Yes Other

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int 43

3- Impact of the change

• ETFMS Flight Data (EFD) users processing flight data

containing a CTFM profile shall consider that there is not anymore an association with FLTSTATE TA (TACT Activated).

• B2B flight data users processing CTFM data shall

consider that there is not anymore an association with Flight Type TACT_ACTIVATED.

• Flight Update Messages (FUM) users processing data

and considering the FLTSTATE TA (TACT Activated) shall evaluate the proposed change.

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int 44

• CHMI/NOP users shall note

that the TACT Activated status as a result of processing a T- DPI-s will not appear or update to ‘t’ the column ‘Type of Flight Data’.

• The flight will remain as Filed

‘I’. This is also applicable to the flight details display.

3- Impact of the change

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int 45

• CHMI/NOP users shall note

that, depending on the FSA_Category of the departure aerodrome, the traffic count details presented for each count interval:

• Will exclusively consider as

‘TACT activated with FSA expected’ flights for which the clock has reached the ETOT or a valid TTOT from A-DPI has been processed.

• Similar criteria as above for the

case ‘TACT activated with no FSA expected’.

3- Impact of the change

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int 46

• All users shall note that there are no changes in the way CASA

gives CTOT improvements

3- Impact of the change

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int 47

4- Communication Plan

• The communication process started in spring 2018.
• The NM communication plan included different stakeholders

(Airspace Users, Flow Management Units, and Airports) and FUM/EFD/B2B users

• The NM communication plan was discussed in
• Consultation groups (AOG, ODSG, DPI-WG)
• For more details on the functional block
• NM 23.0 Release Notes

CR_043914: TACT activation versus Expecting FSA & AOWIR services

nm.releases@eurocontrol.int

Questions

Any questions?

48 CR_043914: TACT activation versus Expecting FSA & AOWIR services

FB1019: NM Helpdesk Improvements FB917: CTM Coordination evolutions

DCB Measure proposal via B2B

v1.1

Presentation of NM23.0

nm.releases@eurocontrol.int

• To solve urgent particular operational

problems beyond the use of ATFM message exchange:

• Assisting stakeholders on specific flight

actions

• Providing information concerning ATFCM

measures.

• Available via:
• electronic means (NOP Portal e-Helpdesk)
• electronic requests with priority over

phone calls.

• phone when no internet access (mainly

business aviation).

50

1- NM Helpdesk Service

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

nm.releases@eurocontrol.int

2- Background – Why

51

NM - FB1019 S18 Experience

• Capacity shortfalls
• Exponential increase of requests
• Jeopardize the Network service

S19 Strategy

• Enhance Network support
• Automation
• Integration
• Request classification

CTM - FB917 S18 Experience

• MUAC Customer Initiative to help their

customer improve operation

• When possible flight

exclusion/improvement to NMOC by email S19 Strategy

• MUAC Continuation Customer initiative
• Introduce flight request to NMOC via

B2B

Less workload / phone communication (NMOC and other stakeholders)

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

nm.releases@eurocontrol.int

3- Impact of the FBs

52

FB1019/FB 917

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Data structure Yes User Interface Yes Procedures Yes Training Yes B2B Yes Other

FB1019 Impacted Stakeholders

• FMP / TWR / AO
• NMOC
• Post Ops

FB917 Impacted Stakeholders

• FMP
• NMOC
• Post Ops

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

nm.releases@eurocontrol.int FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

NM Systems HelpDesk (NOP/Phone)

Flight Exclusion Request Slot Improvement Request

Slot extension request

Slot Swap request ….

B2B

I introduce the request from the e-helpdesk into the ETFMS

I receive the request on system, I analyse and accept/reject the request

I identify my need and send my request to NMOC directly from my working system

I identify my need on my working system

Flight Exclusion Request

Local System Local System B2B Manual

NM System

Regulation Creation Request

Manual

AO/TWR/FMP FMP

NMOC Staff NMOC Staff

NMOC staff analyze the results and introduce the answer to the request in the e-helpDesk/Phone

B2B B2C

Slot Improvement Request

nm.releases@eurocontrol.int

Integrated Coordination / Rationalization Objectives (CTM + E-Helpdesk)

54

4- FB917/FB1019 Overall view

USER

AUTOMATION Comments!

URGENCY INTERFACE

FB917 Digitalised proposal FB917 FMP FB1019 + FMP +TWR FB1019 Avoid duplicates. FB1019 Order in queue Originator CTOT FB1019 NOP FB917 Avoid duplicates. FB917 Ongoing.

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

nm.releases@eurocontrol.int

FMP systems NM systems

4- CTM - FB917 New features

55

EXCLUDE

FMP EDYY

IMPROVE

NMOC REVIEW PROCESS

B2B B2B

PROPOSED ACKNOWLEDGED ACCEPTED/ REJECTED

NMOC

AFR1234 EXCL REG_A18 RYR4567 IMPR REG_B18

FB917 Features:

• EXCLUDE flight from

regulation(s) B2B proposal

• IMPROVE flight in

regulation B2B proposal

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

nm.releases@eurocontrol.int

4- E-Helpdesk FB1019 New features

• Access for TWR and FMP (CR_045011)
• To relax the telephone line - overall faster response
• FMP/TWR will be able to make following requests:
• Request for slot extension
• Request for slot improvement
• Requests exclusion from regulation

56 FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

nm.releases@eurocontrol.int

4- FB1019 New features

• Classification of FMP/TWR/AO requests (CR_045012)
• New queue management, to focus on critical requests.
• Criterias for sorting requests:

1. Originator of the request (CDM > Adv. TWR > Std. TWR > FMP > AO) 2. Type of the request (Extensions > Exclusions > Improvements > Other)

57 FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

nm.releases@eurocontrol.int

4- FB1019 New features

• Automatic processing of requests
• For requests before EOBT-2h (SIT1) (CR_045015)
• Requests for Slot Improvement and Slot Extension that arrive before

the Slot allocation time (SIT1 = EOBT-2h) will be automatically processed by the NM system.

• For duplicate requests (CR_045014)
• In order to focus the workload on the critical requests and increase the

customer satisfaction, NMOC will strengthen the mechanism for identification of duplicate requests.

• Based on average delay (CR_044319)
• During the high workload periods, NMOC staff will have the possibility to

automatically process the requests which are below the Local Average Delay

58 FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

nm.releases@eurocontrol.int

1) Fill in Helpdesk Survey for your TWR/FMP 2) Ensure internet connection / web browser compatibility 3) Request secure Network Manager NOP Portal access

5- Steps to deploy in operations

4) Ensure your request comes as soon as possible if you wish to participate in OPT (from 28th February) and are a NEW USER. 5) If you are ALREADY USING the NOP PORTAL your access will be temporarily upgraded for OPT. 6) Follow ATFCM manual updates and testing sessions 7) Train your staff using external training and Youtube material a. For using the E-Helpdesk in OPS, fill in the request form http://www.eurocontrol.int/network-operations/access-service-request-form Select Type ANSP and Sub-type TWR or FMP In III. PURPOSE OF REQUEST, write “E-Helpdesk use” and specify clearly if you are ALREADY USING the NOP PORTAL or are a NEW USER. i. If you are already using the NOP PORTAL (with token) your access rights will be updated ii. If you are NEW USER (without token) your access will be created More details http://www.eurocontrol.int/network-operations/nm-operational-services-and-products http://w.eurocontrol.int/network-operations/nm-operational-services-and-products-fees

B2C (NOP)

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 59

nm.releases@eurocontrol.int

B2B

1) Fill in Helpdesk Survey for your FMP 2) Get insight on B2B use cases and documentation 3) Standard B2B validation process a) Implement locally in my ATFCM tool b) Perform a PRE OPS validation (technical and business) c) Get Certificate for OPS deployment 4) Update local procedures 5) Train your staff using external training and Youtube material

5- Steps to deploy in operations

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 60

nm.releases@eurocontrol.int

5- Steps to deploy in operations

Deployment Information NOP Portal Network Operations Handbook

• Survey
• NOP access
• Functional Changes
• Best Practices
• + more info.

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 61

nm.releases@eurocontrol.int

TELEPHONE

• It is strongly recommended to reduce to the minimum the use of

the telephone coordination.

• The telephone coordination shall not be used to request

improvements, exclusions from regulations or extensions requests before COBT-20 (exceptional reasons permit TWR to contact afterwards).

INTERFACE

• It is strongly recommended to use the electronic coordination

means (B2B/NOP) to transmit the necessary requests. This has a beneficial effect on the treatment of most urgent requests.

• FMP using electronic desk shall choose between B2B or B2C

interface and never use the two channels simultaneously.

PROCEDURES

• Review the ATFCM manuals to understand when and where

you are entitled to request helpdesk assistance.

• Remember that helpdesk requests have limited possibilities

subject to Network capacity constraints.

TRAINING

Train your operational staff with the new features and remind the procedures and operational best practices.

6- How to use the service and best practices

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 62

NM 23.0 Deployment support

Milestones for the HelpDesk deployment

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 63 nm.releases@eurocontrol.int

nm.releases@eurocontrol.int

For further information on the upcoming improvements or any other question related to the Helpdesk Service:

nm.releases@eurocontrol.int e-helpdesk@eurocontrol.int

More Information?

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 64

nm.releases@eurocontrol.int

Any questions?

66 FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B

FB971: NM Airspace model evolution

v1.2

Presentation of NM23.0

nm.releases@eurocontrol.int

Impact of the FB

• Stakeholder(s) impacted:
• Airspace User (Civil)
• AO or CFSP
• Air Navigation Service Provider (ANSP)

68

FB 971

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Yes Data structure Yes User Interface Yes Procedures Training Yes B2B Yes Yes IFPUV Access

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB971: NM airspace data model evolution

nm.releases@eurocontrol.int

• Background
• FB971 constitutes the forth wave of CACD data model adaptations to allow

seamless Annex 15 data download from the EAD

• Several changes mainly related to the Aerodrome domain have been already

rolled out in scope of NM21.5, 22.0 and 22.5 (FBs 862, 893, 957)

• The intention is to gradually continue rolling out changes in this and subsequent

NM releases

• Objectives
• Internal NM model alignment to AIXM 5.1
• Improve data quality by reducing manual manipulations to the published data
• Part of the NM Strategic Objective No. 2 implementation
• Summary
• Two CRs impact externals (explained below)

FB971: NM Airspace model evolution

69 FB971: NM airspace data model evolution

nm.releases@eurocontrol.int

• Background
• In NM22.0 an Aerodrome operations attribute (IFR/VFR/BOTH) was introduced

at an aerodrome level. It has an associated time schedule

• Corresponding AD Flight Rule restrictions are generated for NM client systems

and external users to prevent IFR flights when AD operates only VFR

• Content
• Timesheets for AD operations, often refer to sunrises (SR) and/or sunsets (SS),

sometimes with additional time shift, e.g. from SR-30 minutes to SS+30 minutes

• To enable AD download from the EAD, CACD will support such timesheets
• CACD will calculate SR/SS times for each AD location
• Impact on clients
• Impact on the clients who use AD flight rules in Airspace B2B
• No impact on the clients who use AD Flight Rule restrictions
• CHMI users

will see them

CR_043842 & CR_045206: Timesheets to allow sunsets and sunrises

70 FB971: NM airspace data model evolution

nm.releases@eurocontrol.int

Questions

Any questions?

71 FB971: NM airspace data model evolution

FB1000: Airspace Data Domain Improvements

v1.2

Presentation of NM23.0

Evaluate FPL against AIRACs earlier

nm.releases@eurocontrol.int

Impact of the FB

• Stakeholder(s) impacted:
• Airspace User (Civil)
• AO or CFSP
• Air Navigation Service Provider (ANSP)

73

FB 1000

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Data structure User Interface Procedures Training B2B Yes IFPUV Access Yes

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB1000: Airspace Data Domain improvements

nm.releases@eurocontrol.int

New features

AO’s & CFSP’s & ANSP’s have today IFPUV access 5 days before the AIRAC switch, meaning they can start validating Flight Plans against the new NM Airspace Data. AIXM NM Airspace data sets available via B2B As from NM 23.0 release: In addition of today’s IFPUV usage:

• Flight plan validation via NOP Portal/B2B at ± 15 days before AIRAC

switch ;

• Flight plan validation via NOP Portal/B2B at n_days before AIRAC

becomes effective;

• No new token required

74 FB1000: Airspace Data Domain improvements

nm.releases@eurocontrol.int

New features

75 FB1000: Airspace Data Domain improvements

nm.releases@eurocontrol.int

New features

Access to the NM Airspace data for ENV Query and MAP

• AO’s & CFSPs & ANSPs will have early access to the NM Airspace Data for

next AIRAC and Ad-Hoc AIRAC’s* via CHMI

* Ad Hoc AIRAC: 1) ± 35 days before AIRAC becomes effective (two AIRAC’s in advance) 2) n_days before AIRAC becomes effective (Pre- validation projects)

76 FB1000: Airspace Data Domain improvements

nm.releases@eurocontrol.int

New features

77

• Access to the NM Airspace data for ENV Query and MAP

FB1000: Airspace Data Domain improvements

nm.releases@eurocontrol.int

New features

NM Airspace data available ± 15 days before AIRAC switch is still subject to NM Airspace data changes (Internal NM validation process, Late publication, …); NM Airspace data available for Ad-Hoc AIRAC(s) will be incomplete in NM system. Only required pre validation NM Airspace Data will be available; The availability of access to the NM Validation / Pre-validation systems depends on the availability of both systems; NM Operational validation / Pre-validation exercise has priority 1

• n the usages of the validation / Pre-validation NM systems.

78 FB1000: Airspace Data Domain improvements

nm.releases@eurocontrol.int

Questions

Any questions?

79 FB1000: Airspace Data Domain improvements

FB943: n-CONECT - Airspace

v1.1

Presentation of NM23.0

New CIREN (CHMI for ENV Coordinators)

nm.releases@eurocontrol.int

1- Impact of the FB

• Stakeholder(s) impacted:
• Air Navigation Service Provider (ANSP)
• Other: ENVCOOR

81

FB 943

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Data structure User Interface Yes Replaces CIREN Procedures Training B2B Other

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB943: n-CONECT - Airspace

nm.releases@eurocontrol.int

1- Impact of the FB

The FB943 replaces CIREN (CHMI for ENV Coordinators) It provides the same functionality however with improved usability, ergonomy and a better map There is no need for local installation anymore however the use requires PENS or internet Existing tokens for the login will be used FMPs and AOs will continue to use the existing CHMI (CIFLO, CITO, CIAO) AMC will continue to use CIAM FMPs and AO will upgrade at later releases At the ANSPs, if the local documenation contained pictures, these pictures shall be updated

New n-CONECT CIREN and current CIREN will be both available

82 FB943: n-CONECT - Airspace

nm.releases@eurocontrol.int

2- New features

The new application will run from a web browser (Chrome preferred) No local installation required, therefore less maintenance required. Improved Map Better organised more logical User Interface which will probably increase productivity Better use of multiple screens and maps. It provides the possibility to save user queries, name certain maps, and there new way to handle the map dossier New feature: contains Sunset, Sunrise values Is is possible to display elaboration and production braches of airspace data

83 FB943: n-CONECT - Airspace

nm.releases@eurocontrol.int

Screenshots

84 FB943: n-CONECT - Airspace

nm.releases@eurocontrol.int

Map screenshot with vertical view, level ban and azimuth filter, and with a timeline

85 FB943: n-CONECT - Airspace

nm.releases@eurocontrol.int

3- Background

The application was developed as part of n-CONECT programme which aimed to merge all existing NM interfaces It replies to the business need of providing effective services to all stakeholder at a reduced cost Benefits are increased usability and less maintenace, later stage integrated CDM workflow with the stakeholders. It can run literally from everywhere, so the application is portable Possible next steps are:

• Inclusion of a workflow (similar to RAD)
• Comparaison between elaboration and production data
• Better ENV dossier, CACD forms

86 FB943: n-CONECT - Airspace

nm.releases@eurocontrol.int

Questions

Any questions?

87 FB943: n-CONECT - Airspace

FB999: Flight Planning Improvements

v2.1

Presentation of NM23.0

nm.releases@eurocontrol.int

1- Impact of the FB

• Stakeholder(s) impacted:
• Airspace User (Civil)
• Airspace User (Military)
• AO or CFSP
• Non-CDM Airport
• CDM-Airport
• ARO
• Air Navigation Service Provider (ANSP)

89

FB 999

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Yes Data structure User Interface Procedures Yes Training Yes B2B Yes Other

FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

1- Impact of the FB

CR_044325 - Prevent multiple flight planning Flight Plan Originators (AFTN/SITA/NOP/B2B) should be aware of the new error that will be returned if they file two flights that overlap with the same aircraft registration. CR_044418 - Remove the special overlap association logic for Type of Flight ‘X’ Flight Plan Originators who submit flight plans with Type of Flight ‘X’ should not expect the specific flight association rule that used to be applied in IFPS. CR_044506 - Reduce output of IFP/IFPSROUTEMOD in FPLs ANSPs that receive FPLs that contain the IFP/IFPSROUTEMOD indicator should understand the new rules for the inclusion in IFPS. CR_043145 - Improve logic for associating RQP to multiple FPLs ANSPs that receive FPLs that contain the IFP/IFPSROUTEMOD indicator should understand the new rules for the inclusion in IFPS.

90 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_044325 - Prevent multiple flight planning
• NM has received reports that some AUs file multiple flight plans (with

different ARCIDs) in an attempt to get a CTOT close to EOBT.

• To prevent this, it has been decided to implement a mechanism in IFPS

to prevent multiple flight plan submissions.

• Note: FB977 REROUTING EVOLUTIONS:
• AUs (Airspace Users) have the possibility to assess the CTOT prior

filing of the FPL (NOP Protected IFPUV Validate/Try).

91 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_044325 - Prevent multiple flight planning
• With this change, IFPS will reject any FPL that is submitted that

matches a valid FPL with same

• REG
• ADEP
• ADES
• And overlapping flying period between the two FPLs.
• New error: EFPM321: FPL WITH SAME REG MARKINGS AND

OVERLAPPING FLYING PERIOD EXISTS:WOO86P EDDF1550 EBBR0035 DOF/181225.

92 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_044325 - Prevent multiple flight planning

93

VALID FPL IN IFPS (FPL-WOO86-IS

• A333/H-SDE1E2E3FGHIJ4J5RWXYZ/LB1D1
• EDDF1550
• N0470F180 SOBRA Y180 BITBU Y181 GOPAS

N852 LNO

• EBBR0035 EHAM
• PBN/A1B1C1D1L1O1S1S2 NAV/T1T2 RNP2

DAT/1PDC REG/WOOPS) NEW SUBMISSION MATCHING REG, ADEP, ADES, and time

• verlap, with a valid FPL in IFPS

(FPL-WOO86P-IS

• A333/H-SDE1E2E3FGHIJ4J5RWXYZ/LB1D1
• EDDF1520
• N0470F180 SOBRA5P SOBRA Y180 BITBU

Y181 GOPAS N852 LNO

• EBBR0035 EHAM
• PBN/A1B1C1D1L1O1S1S2 NAV/T1T2 RNP2 DAT/1PDC

REG/WOOPS) EFPM321: FPL WITH SAME REG MARKINGS AND OVERLAPPING FLYING PERIOD EXISTS:WOO86 EDDF1550 EBBR0035 DOF/181225

FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_044418 - Remove the special overlap association logic for

Type of Flight ‘X’

• For historical reasons, Type of Flight ‘X’ (mostly training flights) have

had a specific flight (overlap) association logic in IFPS.

• With NM 23.0 we will remove this specific treatment and Type of Flight

‘X’ will be treated the same way as other flight types (Scheduled flights ‘S’, non-scheduled ‘N’, General aviation ‘G’ or Military flights ‘M’).

94 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_044418 - Remove the special overlap association logic for

Type of Flight ‘X’

95

VALID FPL IN IFPS (FPL-WOOPS-IG

• DA42/L-SDGHY/S
• EBAW1230
• N0140F060 NIK L179 COA
• EBOS0030 EBAW
• 0)

NEW SUBMISSION: Old IFPS behaviour; second FPL = ACK. (FPL-WOOPS-IX

• DA42/L-SDGHY/S
• EBOS1245
• N0140F060 COA L179 NIK
• EBAW0030 EBOS
• 0)

NEW SUBMISSION: IFPS behaviour with NM 23.0: second FPL = REJ. (FPL-WOOPS-IX

• DA42/L-SDGHY/S
• EBOS1245
• N0140F060 COA L179 NIK
• EBAW0030 EBOS
• 0)

EFPM217: FPL WITH SAME ARCID AND OVERLAPPING FLYING PERIOD EXISTS:WOOPS EBAW1230 EBOS0030 DOF/190225

FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_044506 - Reduce output of IFP/IFPSROUTEMOD in FPLs
• Currently, the presence of IFP/IFPSROUTEMOD in a FPL output is the

result of:

• A manual insertion by an IFPS staff or
• An automatic insertion by IFPS
• Automatic insertion reasons:
• Speed changed from knots to Mach at oceanic entry point
• DCT replaced by co-located ATS route designator
• SID/STAR designator inserted for AD that require SID/STAR in FPL
• IFPS elegant output feature (removing duplicate ATS route designators)
• Etc…

96 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_044506 - Reduce output of IFP/IFPSROUTEMOD in FPLs
• Large number of flagged FPLs is causing some issues:
• AOs have to identify what has been modified.
• ANSP: at least one ANSP introduced a warning to their controllers when

IFPSROUTEMOD was present.

• In NM 23.0, automatic insertion of the IFP indicator IFPSROUTEMOD

will be disabled.

97 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_044506 - Reduce output of IFP/IFPSROUTEMOD in FPLs
• Only occurrences will be by manual insertion by an IFPS staff (when

IFPSRA is present in the FPL or after phone coordination).

• Presence of the indicator means that the trajectory has been laterally

and/or vertically modified between first and last en-route point.

• AOs and ANSPs should understand the new rules for the insertion of the

IFP indicator: IFPSROUTEMOD.

98 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_043145 – Improve logic for associating RQP to multiple

FPLs

• It is recommended to send RQP with the EOBT and the DOF:
• (RQP-ABC123-EBBR-LFML-0)
• (RQP-ABC123-EBBR1200-LFML-DOF/190225)
• This is used to associate the RQP to the correct FPL (when multiple

FPLs with same ARCID, ADEP, ADES exist) .

• Currently when a RQP matches multiple FPLs, it is passed for manual

processing.

• The new logic will avoid the manual processing and improve the quality
• f the replies to RQP messages.

99 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_043145 – Improve logic for associating RQP to multiple

FPLs

• Upon reception of an RQP matching multiples FPLs:
• It will only associate to those FPLs valid in IFPS than have an EOBT up

to 6 hours in the future when compared to the IFPS system time.

• If all matching FPLs have an EOBT later than 6 hours when compared

to the IFPS system time, then the RQP shall associate to all of them.

100 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_043145 – Improve logic for associating RQP to multiple

FPLs

• FPL: ABC123 EBBR1100 LFML DOF/190225
• FPL: ABC123 EBBR1700 LFML DOF/190225
• @1145: (RQP-ABC123-EBBR-LFML-0)
• Any valid FPL with EOBT up to 1745 (1145+0600) → 2 FPLs matching
• In response to the RQP, IFPS sends automatically both FPLs.

101 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_043145 – Improve logic for associating RQP to multiple

FPLs

• FPL: ABC123 EBBR1100 LFML DOF/190225
• FPL: ABC123 EBBR1800 LFML DOF/190225
• @1145: (RQP-ABC123-EBBR-LFML-0)
• Any valid FPL with EOBT up to 1745 (1145+0600) → 1 FPL matching
• In response to the RQP, IFPS sends automatically the FPL with

EOBT1100.

102 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

2- New features

• CR_043145 – Improve logic for associating RQP to multiple

FPLs

• FPL: ABC123 EBBR1800 LFML DOF/190225
• FPL: ABC123 EBBR1800 LFML DOF/190226
• @1145: (RQP-ABC123-EBBR-LFML-0)
• Any valid FPL with EOBT up to 1745 (1145+0600) → 0 FPL matching

before 1745, but 2 matching later than 1745, then:

• In response to the RQP, IFPS sends automatically both FPLs, the one
• f today and the one for tomorrow.

103 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

3- Background – Why

• Short background of the FB:
• Change IFPS behavior as requested by the EUROCONTROL NM Stakeholders.

104 FB999: Flight Planning Domain improvements

nm.releases@eurocontrol.int

4- Questions

Any questions?

105 FB999: Flight Planning Domain improvements

FB972 – ASM Advanced FUA process improvements

v2.0

Presentation of NM23.0

nm.releases@eurocontrol.int

1- Impact of the FB

• Stakeholders impacted:
• Airspace Manager (AMC)

107

FB 972

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Yes Data structure User Interface Procedures Training B2B Other

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

1- Impact of the FB

• way of working
• Systems

108

CR_ID Title

CR_036912 CDR expansion to consider RELATED/CROSSING/OFFLOAD routes vertical limits CR_042633 Complex FUA Restrictions CR_042424 Restriction Grouping CR_041209 FUA KPIs Updated Reports

Impact of the FB on externals:

Current procedures NO Way of working NO Systems YES CHMI; CIAM; CACD;

FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

CR_036912 CDR expansion to consider RELATED/CROSSING/OFFLOAD routes vertical limits Background User Requirement New Features

Currently, automatic closure

• f

the routes affected by an RSA allocation

• nly closes the affected routes within

the vertical limit of the allocation. In certain situations routes above and/or below the allocated range should also be closed to guarantee the flights’ safety The User shall be able to trigger RELATED/CROSSING/OFFLOAD routes through CDR expansion as they are specified, not limiting the update to the vertical limits of the allocated RSA. The CDR Route can be closed or

• pened for the complete vertical limits
• f

the Route CDR definition, independent of the vertical limits of the RSA allocation.

2- New features

109 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

2- New features

110

• If the request is "expand above", the expansion will be until the upper limit of the Route CDR definition but taking the

lower limit of the RSA allocation into account.

• If the request is "expand below", the expansion will be until the lower limit of the Route CDR definition but taking the

upper limit of the RSA allocation into account.

FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

CR_042633 Complex FUA Restrictions Background User Requirement New Features

FUA restrictions are often complex and in order to effectively define the required constraint several sub- restrictions are needed.

• The NM ENV system shall support

the maintenance and validation of Complex FUA Restrictions by combining them in a "FUA" Restriction Group.

• The NM ENV and CIAM systems

shall guarantee that all FUA Restrictions belonging to a FUA Restriction Group are activated / de-activated together.

• If the FUA Restriction Group is

activated, it will automatically activate all FUA Restrictions belonging to the group.

• If any FUA Restriction belonging to

the group is activated, it will automatically activate all FUA Restrictions belonging to the group including the FUA Restriction Group itself.

2- New features

111 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

2- New features

112 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

CR_042424 Restriction Grouping Background User Requirement New Features

• The fine tuning of the selection of

traffic to be validated by FUA Restrictions requires a combination

• f multiple restrictions.
• Prerequisite for CR_042633

(Complex FUA Restrictions) The NM ENV system shall support Restriction Groups that allow to combine Restrictions with some common properties and common behavior. AMCs will have the possibility to ask for the creation of a restrictions group to manage these restrictions in a coherent way (e.g. activate / deactivate).

2- New features

113 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

CR_041209 FUA KPIs Updated Reports Background User Requirement New Features

The existing dashboard are complex and difficult for users to find the correct information. A global overview is missing on the FUA KPIs. Improve and update the NMIR FUA KPIs outcome to reflect the users requirements and to update the calculation algorithm.

• New report templates
• Improved map visualisation
• Introduction of a performance

monitoring dashboard with different layers of analysis

• Updated reports based on the ASM

Handbook updates and users feedback

• Updated calculation algorithm for

countries with both, FRA and route network

2- New features

114 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

2- New features

115 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

2- New features

116 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

2- New features

117 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

2- New features

118 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

3- Background – Why

• Short background of the FB:
• The objective is to provide more flexible solutions to manage airspace structure

data via AUP/UUP.

• Several member States requested more flexibility and new capabilities in order to

better apply the AFUA process.

• The required improvements are pre-requisite for the finalisation of deliverables

described in the AFUA NSP, including some deliverables related to PCP awarded projects.

119 FB972: ASM - Advanced FUA process improvement

nm.releases@eurocontrol.int

4- Questions

Any questions?

120 FB972: ASM - Advanced FUA process improvement

FB977: Rerouting evolutions

v1.2

Presentation of NM23.0

nm.releases@eurocontrol.int

1- Background

122

• Why this FB is being developed?
• To support users of NM rerouting services
• What is the main business objective?
• Improve the rerouting services provided by NM
• FB is done in coordination with AOG taskforce group
• Requirements came from external stakeholders
• What was the problem it intends to solve?
• Improve the information associated to the alternatives
• Enhance the options available on the rerouting tools
• Improve the operational usability and user experience on:
• CHMI/NOP AOWIR
• CHMI/NOP IFPUV

FB977: Rerouting Evolutions

nm.releases@eurocontrol.int

2- Impact of the FB

• Stakeholder(s) impacted:
• Airspace User (Civil)
• AO or CFSP

123

FB 977

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Data structure User Interface Yes Yes AOWIR/IFPV is changed Procedures Training Yes Youtube videos as additional training B2B Other

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB977: Rerouting Evolutions

nm.releases@eurocontrol.int

2- Impact of the FB

• Impact of the FB on externals (what will the FB change in their way of working?) - possibly per Stakeholder
• Impact on Airline Operators
• This change will offer simplified and centralised user interface to AOs.
• IFPUV and AOWIR are enhanced and merged into one single HMI – “Advanced Flight

Management”

• New information available: CTOT and Last Validity Off Block Time

124 FB977: Rerouting Evolutions

nm.releases@eurocontrol.int

• Accessing new features of the AOWIR/IFPUV
• Current functionalities will remain unchanged
• All new functionalities will be integrated in the “Advanced flight management”

interface

3- New features

125 FB977: Rerouting Evolutions

nm.releases@eurocontrol.int

1. CR_044707 Permit identification of the flow impact (CTOT) before filing the flight plan (IFPUV)

• Problem Statement: Today IFPUV (NOP&CHMI) does not return the provisional CTOT or the

potential flow suspension status for a flight plan in preparation. Airspace users have today to file the flight plan to identify the flow impact for a flight.

• Value: Reduce AO effort to file and update flight plans and reduce delays in the network.

Reduce the number of flight plan changes. Allow flight plan operators to work more efficiently.

3- New features

Could be CTOT/ETOT

126 FB977: Rerouting Evolutions

nm.releases@eurocontrol.int

2. CR_044706 Avoid measure function in AOWIR in IFPUV propose routes

• Problem Statement: In IFPUV propose routes (NOP) and AOWIR (CHMI&NOP) the user

needs to be able to interpret, decode and input the locations to avoid the measures.

• Value: Reduce airspace users effort to file and/or update flight plans to reduce delays in the
• network. Reduce the number of flight plan changes

3- New features

127 FB977: Rerouting Evolutions

nm.releases@eurocontrol.int

3. CR_043722 : Give last validity for route proposals in IFPS and IFPUV

• Problem Statement: When a FPL has been filed, AOs *shall* be able to find in the CHMI

NOP & B2B (route proposals), the Last Validity value (LV column) which shows the maximum time to which the OBT of the flight which may be shifted without triggering IFPS

• errors. Today this feature is not available in IFPS/IFPUV and AOWIR context.
• Value: This information is aimed at improving AOs awareness and hence their own
• perations by anticipating the necessary actions on flights that might be delayed (DLA).

3- New features

128 FB977: Rerouting Evolutions

nm.releases@eurocontrol.int

3. CR_044708 AOWIR overload is no longer an error

• Problem Statement: Currently, when the AO What-if (AOWIR) proposes routes that go

through an overloaded area, they are flagged with an error that does not permit to Apply the rerouting from AOWIR.

• Value: Reduce the workload of current process by allowing the rerouting to be applied from

AOWIR tool.

3- New features

Overload is a warning, NOT an error.

129 FB977: Rerouting Evolutions

NM 23.0 Deployment support

CONSULTATION PROCESS – F2F & WebEx

FB977: Rerouting Evolutions 130 nm.releases@eurocontrol.int

nm.releases@eurocontrol.int

For further information on the upcoming improvements or any

• ther question related to the Rerouting service:

NM_rerouting_service@eurocontrol.int

Training material will be uploaded to the YouTube channel: NM Flight Management Zone:

https://www.youtube.com/channel/UCSBhxXXAITbhov9QyuEwH6A

131 FB977: Rerouting Evolutions

nm.releases@eurocontrol.int

4- Questions

Any questions?

132 FB977: Rerouting Evolutions

FB1012: FF-ICE filing Function - file eFPL

v1.1

Presentation of NM23.0

nm.releases@eurocontrol.int

Impact of the FB

• Stakeholder(s) impacted:
• AO or CFSP

134

FB 1012

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Data structure Yes User Interface Procedures Yes Training Yes B2B Yes Other

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

Topics

• Implementation planning – high level overview
• Implementation Considerations
• Supported services
• Data items for eFPL filing
• NM Evaluation and Feedback (NM reply)

135 FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

NM FF-ICE Implementation Plan – High level

• FF-ICE/1 phase 1
• Filing service - RL21-RL24
• eFPL filing by AU/CFSPs to NM
• FF-ICE/1 phase 2
• eFPL distribution – RL23-RL24
• Planning service – RL24-RL25
• FF-ICE/1 phase 3
• Planning service with ATC reply to NM – RL24-RL25

136 FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

FF-ICE/1 Phase 1 (NM23) – Supported Services

• Initial FF-ICE Trial Service
• Flight Plan Validation
• Initial FF-ICE Filing Service
• Flight Plan Creation
• Flight Plan Update
• Flight Plan Cancellation
• Initial FF-ICE Flight Data Request Service
• Flight Retrieval
• to obtain all data available about that flight
• Filing Status
• to obtain the status of their own flight(s) i.e. when MAN was received as reply

to eFPL file

Services over current NM B2B

137 FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

eFPL content

• ICAO FPL data (Current FPL content)
• GUFI (Globally Unique Flight Identifier)
• Filed Trajectory (Optional)
• Route/Trajectory Specific Aircraft Performance (Optional)

138 FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

‘eFPL file’ Data Items (NM23.0)

• ICAO FPL data
• GUFI
• Mandatory in eFPL file, eFPL Update,
• Optional for Trial Service
• either Route/Trajectory (Filed)
• Trajectory Point Properties: Top_Of_Climb, Top_Of_Descent,

TCP_Altitude, Airport_Reference_Location

• Full IFR flights only - no change of Flight Rules
• ADEP, ADES reference location used as Initial/End Prediction Point
• r Route (Item15c FPL) as free text
• Route/Trajectory Specific Aircraft Performance
• Using FIXM 4.1
• + European Extension for typical European operations (e.g. RVR,

IFPLID, etc.)

• AUs Flight Plan Version (waiting for FIXM 4.2 availability)

139 FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

NM Evaluation & Feedback – NM ‘reply’

140

‘eFPL file’

• The NM ‘reply’ will indicate if the flight plan is Valid, Queued or

Rejected (ACK, MAN, REJ) - Error indication in case of REJ

• AGREED Route/Trajectory
• Constraints feedback (PTRs only)
• Trajectory Point Property CONSTRAINT_POINT only
• Route (Item15c FPL) as free text
• IFPLID
• GUFI

‘Trial Service Request’

• NM ‘reply’ can indicate ‘Valid’ – no errors returned, or ‘Invalid’ – errors

are returned

• AGREED or NEGOTIATING Route/Trajectory
• Constraints feedback (PTRs only)
• Trajectory Point Property CONSTRAINT_POINT only
• GUFI (if included in the request)

FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

Remarks for the Other services

• Flight Plan Update
• expected to be provided as a full eFPL
• GUFI
• IFPLID
• Flight Plan Cancellation, Flight Retrieval & Filing Status
• no GUFI
• IFPLID

141 FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

Implementation considerations

• ICAO approach to FF-ICE
• no Big Bang approach as for 2012 FPL
• benefit driven implementation
• NM will translate eFPL(s) and distribute as FPL (ICAO/ADEXP)
• Time of implementation and pace of integration of new data by

ANSP to be determined by each stakeholder

142 FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

• NM
• NOP/B2B Reference Manual

https://ost.eurocontrol.int/sites/B2BWS/default.aspx

• Flight Services, FIXM Validation Rules for NM B2B, etc.
• NM Release Notes for NM23.0
• Network Operations Handbook
• FPFDE Implementation Guidance Vol. 1 – FF-ICE/1 – pre-departure
• FIXM CCB (www.fixm.aero)
• FIXM Implementation Guidance
• ICAO (https://portal.icao.int/icao-net/Pages/default.aspx)
• PANS-ATM (Doc 4444)
• FF-ICE Manual (Doc 9965)
• Vol. 1 – FF-ICE Concept
• Vol. 2 (New) – Implementation Guidance

Documentation

143 FB1012: FF-ICE filing Function - file eFPL

nm.releases@eurocontrol.int

Questions

Any questions?

144 FB1012: FF-ICE filing Function - file eFPL

FB975: Airport Programme

v1.1

Presentation of NM23.0

A-CDM improvements

nm.releases@eurocontrol.int

1- Impact of the FB

• Stakeholder(s) impacted:
• CDM-Airport
• Advanced ATC TWR Airport

146

FB 975

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Internal computation Yes Data structure Yes User Interface Procedures Training B2B

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB975: Airport Programme

nm.releases@eurocontrol.int

1- New features CR_044117

CR_044117 - Improve syntax checking of DPI messages

• The syntax checking of DPI messages provided via AFTN will be changed as follows:
• The SID field will be mandatory in an A-DPI
• The fields ARCTYP, REG, TAXITIME and DEPSTATUS will be forbidden in a C-DPI
• The value TOTUNKNOWN will be forbidden in the reason-field of the C-DPI.

147 FB975: Airport Programme

nm.releases@eurocontrol.int

2- Background – Why CR_044117

CR_044117 Improve syntax checking of DPI messages

• The syntax of DPI messages evolved based on acquired experience and new CDM

requirements

• To align the syntax of DPI, independent of the provision means (AFTN / B2B)
• The only remaining difference will be that the reason-field in the C-DPI is

mandatory in B2B

148 FB975: Airport Programme

nm.releases@eurocontrol.int

3- Impact of CR_044117

CR_044117 - Improve syntax checking of DPI messages

• Concerned A-CDM and Advanced ATC TWR airports have already adapted their

system(s) in order to comply with the modified syntax changes or will do so by the migration date of NM23.0

• DPI messages that do not comply with the modified syntax will be rejected

149 FB975: Airport Programme

nm.releases@eurocontrol.int

1- New features CR_044326

CR_044326 - Correct TTOT acceptance around filing time for regulated flights

• A T-DPI-t with a TTOT in the past (earlier than filing time – 10min) will no longer be

rejected

150 FB975: Airport Programme

nm.releases@eurocontrol.int

2- Background – Why CR_044326

CR_044326 - Correct TTOT acceptance around filing time for regulated flights

• In NM22.5, the T-DPI-t message with TTOT more than 10 min in the past is

rejected

• For a regulated flight with a long ATFM delay, such a TTOT is justified as

TTOT = TOBT + Taxi Time

• Some airports decided to apply an adjustment to the clock as a temporary

solution until the NM systems are updated

• This results in incorrect ATFM delay calculation and an increased risk of CTOT

recalculation

151 FB975: Airport Programme

nm.releases@eurocontrol.int

3- Impact of CR_044326

CR_044326 - Correct TTOT acceptance around filing time for regulated flights

• A-CDM airports applying an adjustment to the clock to the TTOT value in the T-DPI-t

are recommended to update their system so that TTOT is always based on the TOBT

152 FB975: Airport Programme

nm.releases@eurocontrol.int

Questions

Any questions?

153 FB975: Airport Programme

FB992: DPI Improvements

v1.2

Presentation of NM23.0

nm.releases@eurocontrol.int

Impact of the FB

• Stakeholder(s) impacted:
• Flow Manager (FMP)
• CDM-Airport
• Advanced ATC TWR Airport
• TWR

155

FB 992

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Internal computation Yes Data structure Yes User Interface Yes Procedures Yes Training Yes B2B Yes

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB992: DPI Improvements

nm.releases@eurocontrol.int

New features

• The following three features are delivered in FB992:
• Tower Update A-DPI (CR_039924)
• Issue next available CTOT (CR_043612)
• C-DPI with reason “UNDOADPI” (CR_041042)

156 FB992: DPI Improvements

nm.releases@eurocontrol.int

1- New features introduced by CR_039924

Tower Update A-DPI

• A-DPI with value “TWRUPDATE” in a separate depstatus-field
• Special processing by ETFMS
• Only for regulated flights; if provided for a non-regulated flight, message treated

like a classic A-DPI

• Only for when the flight is under control of TWR/ATC and TOBT/TSAT

update is no longer feasible Three different Use Cases

• 1. Request a 10 min CTOT extension
• 2. Request a next available CTOT
• 3. Request de-suspension of a flight that was suspended by the airport

(Advanced ATC TWR) via C-DPI

157 FB992: DPI Improvements

nm.releases@eurocontrol.int

1- New features introduced by CR_039924

Tower Update A-DPI Use case 1 → Request a 10 min CTOT extension

• Manually triggered by TWR controller in case of an operational/technical problem

while taxiing

• A 10 min CTOT extension will be granted automatically (SRM with new CTOT =

CTOT + 10) if all the below conditions are met:

1. The flight has off-blocked (classic A-DPI received) (if not → request rejected) 2. No CTOT extension has been granted before (if not → request rejected) 3. The STW is standard, [-5;+10] (if not and if TTOT outside extended STW → send next available CTOT, see Use Case 2) 4. Limit of 3/hour CTOT extensions, automatically granted, has not been reached (if not → request rejected) 5. CTOT + 10 < TTOT <=CTOT + 20 (if TTOT>CTOT+20 → explicit request to send next available CTOT, see Use Case 2) 6. The flight trajectory updated with the new TTOT and/or SID is not violating restricted airspace (if not → request rejected) 7. A 10 min CTOT extension does not push the flight inside a zero-rate, insufficient RVR or XCD regulation period (if not → send next available CTOT, see Use Case 2) 8. The request is made before the end of STW (if not → send next available CTOT, see Use Case 2)

158 FB992: DPI Improvements

nm.releases@eurocontrol.int

1- New features introduced by CR_039924

Tower Update A-DPI Use case 2 → Request a next available CTOT

• Tower Update A-DPI will be treated as a request for a new CTOT when:
• A. The CTOT extension could not be granted (see Use Case 1; if Condition 3, 7 or

8 on previous slide are not met)

• B. TWR has already identified that a 10min CTOT extension will not be sufficient

(Condition 5 on previous slide, TTOT > CTOT + 20)

• In case B, TTOT is the earliest time when the flight will be ready
• Processed like a T-DPI-s with TTOT after end of STW
• An automatic network impact assessment will be triggered which may lead

to, e.g. a new CTOT, SLC or an FLS

159 FB992: DPI Improvements

nm.releases@eurocontrol.int

1- New features introduced by CR_039924

Tower Update A-DPI Use case 3 → Request de-suspension of a flight that was suspended by Advanced ATC TWR airports via C-DPI

• Flight is taxiing and is suspended by a C-DPI
• A classic A-DPI is rejected in this case
• Tower Update A-DPI → triggers an automatic network impact assessment

that may result in SAM, DES, FLS

• Highly recommended for Advanced ATC TWR airports

160 FB992: DPI Improvements

nm.releases@eurocontrol.int

2- Background – Why CR_039924

Tower Update A-DPI

• Request from A-CDM airports via the DPI WG:
• To automate the request for CTOT extensions
• To provide next available CTOT when the CTOT extension cannot be granted
• To request flight de-suspension via Tower Update A-DPI
• The message exchange replaces the need for phone coordination for

individual flights, reduces workload for TWR and flow controllers

• Automatically processed by ETFMS with no manual intervention by flow

controller

• The TWR remains in control of when to receive a new CTOT
• Ensures provision of a more fitting CTOT based on the local situation
• Only option for Advanced ATC TWR airports to request flight de-suspension

following C-DPI (other than EOBT update; classic A-DPI is rejected)

161 FB992: DPI Improvements

nm.releases@eurocontrol.int

3- Impact of CR_039924

Tower Update A-DPI

Impact on A-CDM / Advanced ATC TWR airports

• Only those A-CDM / Advanced ATC TWR airports that wish to make use of the Tower Update A-DPI

will be impacted

• Following coordination with the NM A-CDM team, they will have to update their system(s):
• To send the depstatus value “TWRUPDATE” in A-DPI
• To display to TWR controller the replies from ETFMS
• The A-DPI may contain two depstatus-fields, one for the value “TWRUPDATE” and the other for

“DEICING” Impact on TWR

• The Tower Update A-DPI will partially replace the phone call to NMOC
• Procedures for the TWR need to be established to describe:
• The situations when a Tower Update A-DPI message can be triggered (manually)
• The required action that needs to be taken depending on the reply from ETFMS to the Tower

Update A-DPI request

• TWR has to be ready to deal with a new CTOT after the off-block event

Impact on FMPs

• A CTOT extension that creates an over-delivery in the regulation period may be granted
• The impact is mitigated by restricting the requests made by the same airport at max 3/hour

162 FB992: DPI Improvements

nm.releases@eurocontrol.int

4- New features introduced by CR_043612

Issue next available CTOT

• New button in the NID window for use of flow controller on request from

TWR (during phone coordination for individual flight)

• Allows Flow controller to manually trigger a CTOT recalculation
• The new CTOT is shown to the flow controller, who will consult with TWR

before confirming it (issue SRM)

• [Updated after presentation] The action "Operator CTOT Recalculation" is

visible in the flight history via B2B and B2C

163 FB992: DPI Improvements

nm.releases@eurocontrol.int

5- Background – Why CR_043612

Issue next available CTOT Problem statement

• TWR calls NMOC for CTOT extension (after the flight has off-blocked)
• Flow controller concludes that CTOT extension cannot be granted (after

network impact assessment) and currently asks TWR to apply the return to stand procedure

• Request from A-CDM airports via the DPI WG:
• To provide next available CTOT when the CTOT extension cannot be granted

Benefits

• The TWR remains in control of when to receive a new CTOT
• Increased adherence to the ATFM slot
• TWR may not need to apply the return to stand procedure

164 FB992: DPI Improvements

nm.releases@eurocontrol.int

6- Impact of CR_043612

Issue next available CTOT Impact on TWR

• Only for TWR at A-CDM or Advanced ATC TWR airports
• TWR has to be ready to deal with a new CTOT in case the CTOT extension of 10min

cannot be granted, possibly with a long delay

• Procedures for the TWR need to be established to describe:
• The situations when a request for a new CTOT should be made
• The required action that needs to be taken after new CTOT received
• Refer also to CTOT Extension Management procedure of the ATFCM Operations Manual

165 FB992: DPI Improvements

nm.releases@eurocontrol.int

7- New features introduced by CR_041042

C-DPI with reason UNDOADPI

• Possibility for TWR to request de-activation of a flight via C-DPI with reason

“UNDOADPI”

• This message will be automatically processed in the same way as a manual de-

activation

• Unlike for all other values for the C-DPI reason, the flight will not be suspended when

the reason UNDOADPI is provided

166 FB992: DPI Improvements

nm.releases@eurocontrol.int

8- Background – Why CR_041042

C-DPI with reason UNDOADPI Problem statement

• Flight is erroneously activated by wrong A-DPI (triggered by wrong AOBT

input)

• TWR calls NMOC for manual de-activation
• Request from A-CDM / Advanced ATC TWR airports to automate request

Benefits

• Reduction of workload
• Following de-activation, DLA/CHG messages are accepted again
• Especially useful for Advanced ATC TWR airports that cannot provide

another type of DPI after such A-DPI

167 FB992: DPI Improvements

nm.releases@eurocontrol.int

9- Impact of CR_041042

C-DPI with reason UNDOADPI

Impact on A-CDM / Advanced ATC TWR airports

• Only those A-CDM / Advanced ATC TWR airports that wish to request flight de-

activation via message will be impacted

• They will need to update their system(s) to send:
• The C-DPI reason value “UNDOADPI” if provided via AFTN
• The C-DPI reason value “UNDO_ADPI” if provided via B2B Web Services

Impact on TWR

• Replaces phone coordination with NMOC to request manual flight de-activation
• Manually triggered by TWR
• Procedures for the TWR need to be established to describe:
• The situations when a request for a flight de-activation should be made via C-DPI with

reason “UNDOADPI”

168 FB992: DPI Improvements

nm.releases@eurocontrol.int

Questions

Any questions?

169 FB992: DPI Improvements

FB958: Correction and tuning of external data processing

v1.0

Presentation of NM23.0

Changes in EFDs content

nm.releases@eurocontrol.int

1- Impact of the FB

• Stakeholder(s) impacted:
• Air Navigation Service Provider (ANSP)
• AO – clients of the service EFD

171

FB 958

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Data Distribution EFD Internal computation Data structure see the next slide User Interface Procedures Training B2B Other

• Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.

FB958: Correction and tuning of the external data processing

nm.releases@eurocontrol.int

1- Impact of the FB

172

There is NOT a new feature brought by this FB for externals compare to today. The ADEXP standard already covers the format of the PTID : 2{ALPHANUM}5. The change consists that this format will appear in the EFDs.

FB958: Correction and tuning of the external data processing

nm.releases@eurocontrol.int

2- New features

• Examples:
• Terminal Points:
• BL011 (part of the SID description in LEBL)
• MD001 (part of the STAR description in LEMD)

173 FB958: Correction and tuning of the external data processing

nm.releases@eurocontrol.int

2- New features

• Helicopter Points:
• LS100 (part of the route KY251)
• LS103 etc

174 FB958: Correction and tuning of the external data processing

nm.releases@eurocontrol.int

3- Background – Why

• Short background of the FB:
• Why was it developed?
• One of the objectives of this FB is:
• To align systems: CACD - ETFMS - EFD/B2B Publish/Subscribe by using and
• utputting the same terminal/helicopter points as presented in the CACD.
• What was the business need? And what was the problem it intends to solve?
• This alignment will be reflected in the data distribution (EFD/B2B Publish/Subscribe).
• What are the benefits?
• With the NM22.0 release the terminal/helicopter points were made visible to the

systems after being implemented into CACD and output in the B2B Publish/Subscribe. This CR requests to present these terminal/helicopter points in EFDs exactly as they are in the CACD (not to be transformed in the GEO points).

175 FB958: Correction and tuning of the external data processing

nm.releases@eurocontrol.int

Questions

Any questions?

176 FB958: Correction and tuning of the external data processing

FB980: Predictability: Yo-Yo flight plans identification

v1.1

Presentation of NM23.0

nm.releases@eurocontrol.int

1- Background – Why

• Yo-Yo drafting group (YYDG), mandated by ODSG to investigate options for reduction of

received flight plans containing Yo-Yo profile.

• Highlighting such flight plans and sharing information:
• to reduce number of filed Yo-Yo flight plans
• to increase awareness of FMPs and AOs when such flight plans are submitted.
• All flight plans where change of cruising flight level is done in a way that flight will have to

initially descend and after that climb in the cruising phase for certain amount of feet are considered to be Yo-Yo flight plans.

• YYDG participants will explore and define further steps for this FB.

178 FB980: Predictability: Yo-Yo flight plans identification

nm.releases@eurocontrol.int

2- Impact of the FB

• Stakeholder(s) impacted:
• Flow Manager (FMP) – Initially participants in the YYDG.
• Airspace User (Civil) – Initially participants in the YYDG.
• Post-ops analyst
• AO or CFSP – Initially participants in the YYDG.
• ARO
• Air Navigation Service Provider (ANSP)

179

FB 980

Service affected Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Data structure User Interface Yes Procedures Training Awareness to YYDG B2B Other

FB980: Predictability: Yo-Yo flight plans identification

nm.releases@eurocontrol.int

3- New features

• Based on predefined filtering criteria, NM systems identifies Yo-Yo flight

plans under agreed initial YYDG criteria.

• Through the NOP/CHMI flight list AOs and FMPs can identify if an specific

flight plan contains Yo-Yo profile.

• Additional details are available to FMPs when at least one portion of Yo-Yo

profile is within their area of responsibility.

180 FB980: Predictability: Yo-Yo flight plans identification

nm.releases@eurocontrol.int

• Predefined criteria acc. YYDG - e.g. 2000/4000 ft (= 4000/2000 ft)

and above.

• New column in CHMI/NOP flight list (YY) identifies YoYo flights.
• AOs and FMPs have different level of detail.
• Initially, limited number of stakeholders (YYDG members +) to

agree on criteria and further evaluate the process (to be agreed at the YYDG) would show this column.

• Later (based on the YYDG assessment) functionality will be

enabled to all AOs/FMPs and communicated to all stakeholders.

Highlights

181 FB980: Predictability: Yo-Yo flight plans identification

nm.releases@eurocontrol.int

• New column (YY), 2 characters:
• The first – indicates that there is a YoYo in the FPL
• The second provides additional information on flight evolution
• When YY is present before departure, participating AOs (YYDG) may

refile - but in any case to adhere to filed FPL.

• More details in Oplog
• Archived – to support post OPS analysis by AOs/ CFSPs

AOs view

182 FB980: Predictability: Yo-Yo flight plans identification

nm.releases@eurocontrol.int

• New column (YY), 2 characters:
• The first – indicates that there is a YoYo in the FPL
• The second character gives the FMP additional information on flight

evolution when querying on an Airspace and/or a TV based on airspace

• Airspace intersection:
• C : Complete, YoYo completely overlaps with the airspace.
• S : Start, there is a YoYo starts within the airspace.
• E : End, there is a YoYo ends within the airspace.
• A : Airspace, YoYo overlaps completely airspace, but not the start or end.
• O: Outside, there is no yoyo overlapping with the airspace but there is at least one outside this airspace.
• Blank: There is no yoyo at all or detection has never been performed.
• N: no YoYo in one of the columns when detected in another
• Archive – based on the AUA – eg EDYYUTA
• More details will be provided to YYDG participants.

FMPs view

183 FB980: Predictability: Yo-Yo flight plans identification

nm.releases@eurocontrol.int

4- Questions

Any questions?

Contact: nm.flightefficiencysupport@ops.cfmu.eurocontrol.int boris.radovanovic@eurocontrol.int

184 FB980: Predictability: Yo-Yo flight plans identification

nm.releases@eurocontrol.int

• CR_040712: As from NM23.5 (Q4-2019), CACD will be populated

with new aerodromes that may have empty ICAO and/or IATA identifiers

• NM will generate identifiers for these Aerodromes (rules available in

the NM Release Notes)

• These aerodromes will be exported via NM B2B.
• Flight plans and related messages output in ICAO or ADEXP format

remain unchanged with still ZZZZ for these ADs.

• cf NM Release Notes §2.1.4 for more information.

185

As from Q4-2019 CR_040712: NM plans to allow into CACD Aerodromes with no ICAO or IATA identifier

NM23.0: Way forward

Presentation of NM23.0

nm.releases@eurocontrol.int

2.1- NM23.0: The OPT (Operational Testing) (Release Notes §4.1.3)

187

NM23.0 will be available for testing with the OPT (operational testing) session!

• NM23.0 OPT session will start on the 28th of February and end on the 28th of March.
• With the NM23.0 OPT you are able to:
• Test NM23.0 on your systems with your procedures.
• Download and test the new NM23.0 CHMI.
• Test the new NM23.0 NOP Portal.
• Test some new FBs (operational scenario provided in the OPT guide).
• B2B: NM23.0 will be available on PREOPS (as from 01/04/2019-14:00 UTC)
• All you need is to already have access to NM systems. No registration required

(unless you want to exchange FPL messages with OPT platform).

⇒ Questions: nm.opt@eurocontrol.int

nm.releases@eurocontrol.int

Way forward to NM23.0 migration

188

• NM23.0 migration is planned to start on the 30/04/2019 (last around 1 week)
• Detailed Release migration plan may be found in the NM Release Notes (§4.1.4).
• As for any release, the date of migration is subject to the output from final technical

and operational testing.

• To receive information on the Release (including NM Release Notes updates,

OPT information, presentations, etc.): subscribe to the mailing (cf. §1 of the NM Release Notes)

• Any question related to the Release: nm.releases@eurocontrol.int

nm.releases@eurocontrol.int

Any questions?

189

nm.releases@eurocontrol.int

Many thanks for your participation!

190