A presentation of the NM18.5 to Externals via video ... · PDF fileA presentation of the NM18.5 to Externals via video-conference took place on the 9th of July 2014. ... Stop boundary

Presentation of NM18.5 to Externals – 09/07/2014

A presentation of the NM18.5 to Externals via video-conference took place on the 9th of July 2014.

Please find below: • The link toward the recording of this presentation: http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/20140709-presentation-of-nm-18.5-to-externals.mp4

• The link toward the NM18.5 Release Notes: http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/nm-release-notes-next.pdf

• The slides used during the Presentation.

If any questions: [email protected]

http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/20140709-presentation-of-nm-18.5-to-externals.mp4

http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/20140709-presentation-of-nm-18.5-to-externals.mp4

http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/nm-release-notes-next.pdf

http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/nm-release-notes-next.pdf

mailto:[email protected]

v1.3

Presentation of NM18.5 to Externals

EUROCONTROL – Network Manager Directorate 09/07/2014


Welcome to the Presentation of NM18.5 to Externals

Agenda 1- Introduction and interface set-up 2- Release Functional Blocks presentation 3- Way forward toward NM18.5 migration

[email protected] 3


Recording

Presentation is recorded and will be available on the Eurocontrol public website in a few days: http://www.eurocontrol.int/lists/publications/network-operations-library?title=&field_term_publication_type_tid=252&year[value][year]=

[email protected] 4

http://www.eurocontrol.int/lists/publications/network-operations-library?title=&field_term_publication_type_tid=252&year%5Bvalue%5D%5Byear%5D=

http://www.eurocontrol.int/lists/publications/network-operations-library?title=&field_term_publication_type_tid=252&year%5Bvalue%5D%5Byear%5D=


[email protected] 5

To be done now: 1- Click on the green tab on the middle-top of the screen:

Preparation

2- Click on « Participants » 3- Click on

« Chat »


Ask questions

Questions may be asked at the end of each Functional Block presentation. Questions may be ask orally or by chat. How to ask a question orally:

[email protected] 6

2- When the micro icon is grey: you can ask your question; start with your name and company name

3- At the end of the exchange: - Mute your micro (shall be in red) - Click on « Lower hand »

1- Click on « Raise hand » and wait

4- If for any reason you did not get the floor, click on the micro and speak


Ask questions

How to ask a question by chat:

[email protected] 7

1- Type your question in the Chat window, start with your company name 2- Select « Everyone » and click on « Send » 3- The presenter will read the question and reply to it orally


8

• Goals of the presentation: • Present the new features of the Release • Assess their impacts for you • Ask questions (today or by eMail)

• Why doing the presentation now? ⇒ SHOM2 (Software Hand-Over Meeting) is passed.

Release presentation

[email protected]


NM18.5 Release presentation

NM-01 - Free Route Airspace FB576 FRA (Free-Route Airspace) evolutions NM-02 - Airspace Management and AFUA FB510 ASM interoperability level 2 - Live Updates NM-05 - NOP Information Services FB630 NOP Access to event information consolidation NM-08 - Operations Improvements FB626 Provision of Departure data FB638 ASM monitoring FB657 CSST improvements FB659 ATFCM Domain improvements FB660 Flight Planning Domain improvements FB661 Improve CHMI Services FB668 Performance Work Programme RD-02 - Airspace Users Operations R&D FB619 Slot swapping process

[email protected] 9

Only Functional Blocks impacting operations and Externals are presented.


Important notification for NM18.5

Impact: Users downloading the eRAD files from the NM FTP server. The eRestriction services on the NM FTP server (including the eRAD files in AIXM 4.5) will no more be available as from NM18.5 (23 September 2014). The restriction information are available (in AIXM 5.1) since NM17.5 via the NM B2B services.

[email protected] 10

Presentation of NM18.5

v1.0

FB576: Free Route Airspace (FRA) Evolutions


New features

1. Reject FPLs where routes are filed along or adjacent to operational airspace boundaries

2. Stop boundary clipping

12 [email protected]


IFPS shall identify and reject a flight plan where a flight files a DCT route between published points aligned with operational airspace boundaries (ie boundary of Area of Responsibility of ATC Unit)

1- Reject FPLs along or adjacent to operational airspace boundaries 1.1- Background



Why? • Routing is not acceptable from an ATC

perspective Problems encountered in Ireland, UK, Portugal, Latvia and Finland Request for change made at ODSG and RMG prior to 2012

• Route Availability Document (RAD) - “no fly

DCTs” have been created to mitigate this problem by ANSPs IAA created more than 150 “no fly DCTs” in the RAD alone - to ensure this type

of routing is not filed. Entries could be removed if the requirement is implemented at the IFPS processing level

FRA part of SESAR Deployment Implementing

Rule for Pilot Common Projects - deadline 2022 Number of occurrences expected to increase with greater freedom of choice given

to Users with pan-European cross border deployment of FRA

1- Reject FPLs along or adjacent to operational airspace boundaries 1.1- Background



1- Reject FPLs along or adjacent to operational airspace boundaries 1.2 - New Feature

Detects FPLs exactly on a boundary, but also FPLs

immediately adjacent to a boundary

Detection done by shifting the relevant DCT segment in the profile to the left and the right and recalculating airspace intersection (see drawing next slide)



Airspace A Airspace B

X

Y

Parameters create “border window” for search: - width: shift to left and right - length: max length along border

DCT segment close to airspace border Width - at each side - shift to left and right: 0.5nm Length - max length along border: 15nm

Initial Parameters agreed at RAD MG 24 Prototype demonstration provided to IAA and NATS

1- Reject FPLs along or adjacent to operational airspace boundaries 1.2 - New Feature



Reduce workload/cost on ANSPs to prepare, submit and maintain RAD restrictions to mitigate the problem

Helps to simplify RAD

Meets operational need to avoid this type of routing, saving workload for aircrew and ATC if detected early on at flight planning phase

1- Reject FPLs along or adjacent to operational airspace boundaries 1.3 - Impact of the FB



New features

1. Reject FPLs where routes are filed along or adjacent to operational airspace boundaries

2. Stop boundary clipping



2- Stop boundary clipping 2.1- Background

Stop boundary clipping - change of 15nm re-entrance parameter for Free Route Airspace During airspace validation testing for FRA implementation several ANSPs

requested the removal of this feature and requested the parameter be reduced to 0nm

Airspace A

Airspace B



2- Stop boundary clipping 2.1- Background

IFPS accepts free route DCT segments to exit and then re-enter the same Free Route Airspace when the distance between exit and re-entry is less than 15nm

To mitigate the effects of the rule some ANSPs have created “No fly DCTs” in the RAD i.e. BULATSA (86) and ROMATSA (46)



2- Stop boundary clipping 2.2 - New Feature

In NM Release 18.5 the parameter will be changed to 0nm and flight plans will be rejected



2- Stop boundary clipping 2.3 - Impact of FB

Prevents boundary clipping - expected to increase with the large scale implementation of FRA where Users are given greater freedom of choice

Enables simplification of RAD by removing “no fly DCTs”



Questions

Any questions?



v1.0

FB510: B2B Publication of ATM Live Updates


1- Background

Continuation of work started under the Airspace Data Repository programme. To provide airspace users with the most up to date and consistent view of

operational airspace data and to improve ASM interoperability .

FB510 impacts B2B Services only.

Specifically the data exported via Aeronautical Information Exchange Model (AIXM) i.e. the AirspaceServices.



1- Background


e-RAD in EAD (AIXM 4.5)

e-AMI pilot phase EAUP on NOP (AIXM 5.1)

2009 2010 2011 2012 2013 2014

NM Release: 15/15.5 16 16.5 17 17.5 18.5

PTRs available on ftp server (AIXM 4.5)

Access to AIRAC static

operational data (FB 441)

pilot phase

e-AMI operational

Dynamic updates available in AIXM 5.1 via B2B services (FB510) (including CRs for LARA V3 Deployment.)

FRA/DCT restrictions with e-RAD

e-Restrictions via ftp operational

All restrictions available in AIXM 5.1 via NM B2B services (FB555) Migrate e-RAD clients from EAD to NM B2B (FB555)


2- Current (NM18) features

Daily AIXM 5.1. baselines of CACD Airspace data. Baseline for subsequent AIRAC available from AIRAC -6 days (2

data sets available).



2- New features

Availability of Airspace data dynamic updates i.e. within 10 minutes of CACD entry. Includes:

CDR and Airspace activation/availability from AUP/UUP Route NOTAM changes NAT Tracks All Restriction modifications SID/STAR availability (N.B for Restriction reference only). Corrections to NM AIRAC data definition



29

2- New features

Export of NAT Tracks in AIXM 5.1 format, Non-operational sector data (aka Test Sectors) will not be exported, AIXM 5.1 ADR extension time information adaptation, better use of core model, Additional features requested for ASM clients (results from workshop 2012). Subsequent AIRAC data will be exported in one timeline from AIRAC-6.


3- Impact of the FB

No impact on current AIXM 5.1 service or procedures.

New features can be exploited gradually.



4- Questions

Any questions?



V0.1

FB630: NOP access to Event information


33

Presentation Objectives

Present Network Events Portlet (FB630) Current Status – what we have achieved so far; Objectives – what we want to achieve; Benefits – why we want it; What remains to be done.

Answer questions

[email protected]


Network Manager Public Portal

http://www.public.nm.eurocontrol.int/PUBPORTAL/gateway/spec/index.html

•

• No access restriction (no need for password/token/etc.)

• Accessible on all Tabs: Strategic, Pre-tactical, Tactical, Post-Operations

FB630 Impact on users: None

34

Network Events Portlet Access

[email protected]

http://www.public.nm.eurocontrol.int/PUBPORTAL/gateway/spec/index.html


Network Events Before March 2014 (pre - NM 18.0)



Current Status: what we have achieved so far



Network Events in NM 18.0 - Now



Network Events in NM 18.5 (FB630)



Search Network Events



Search Results Now



Search Results NM 18.5

Search Result statistics

Click on name to open Event Details View



Network Event Details

NM 18.5 now



Network Event Details

General Information Summary

Name Type Sub Types Status Estimated Period Confirmed Period Locations Short Description Last Published

Description and Expected Benefits Description Expected Benefits

Originator Organisation Name, Type, ICAO Code Description

Measures and Scenarios Reference Publications Remarks and Comments

Originator Comments Network Manager Comments

Activities and Impacts For each Activity/Phase of the Event the following information is provided

General Information Period Locations Description Attachments Impact on Capacity and/or Flight Efficiency For each impact the following information may be available:

Period Network Impact Description Capacity Variation Sector Configuration Traffic Sample Description Traffic Sample Description Impacted Locations Possible Bottleneck Sectors Comments Attachments

Milestones When no information is available in the database then the text “not defined” or “none” is shown.



Notifications – NM 18.5



[email protected]

Notification Results (example) – NM 18.5

46


47

Objectives: what we want to achieve

A Collaboration Platform on NM Portal for Network Event Information exchange

and integration in the overall Network Planning and

ATFCM Processes

[email protected]


NM Portal

Network Events Goal

NET Repository

Event data production & update

Event data consumption

Event data storage & quality

management

NET Input Events

NET View Events

NM Units (OPL, NOS, NMC, APT, OMR, CACD, STATFOR, PRISMIL, etc.)

ANSP, ACC, ATC, FAB, Airport, Tower, Military, etc. NM Systems

(DDR,NEST, etc.)

External Systems

ANSP, ACC, ATC, FAB, Airport, Tower, Military, etc.

NM Units (OPL, NOS, NMC, APT, OMR, CACD, STATFOR, PRISMIL, etc.)

External Systems/ databases



Network Events View Events Data

“consumer” Event data

consumption DNM

External

MILO OPL

NOS

NMC DDR

PRISMIL OMR APT

ANSP, ACC, ATC, FAB, etc.

Airport, Tower, Military, etc.

ERNIP Event

s

Network Events

Event data storage & quality

management

NET Repository &

Interfaces Transition Plan

FMP & other

events list

Military events

list

Airport

Events View

ERNIP View

Airport Corner

MILITARY

OPL

APT

Network Events Input

ANSP, ACC, ATC, Mil, FAB, etc.

Airport, Tower, Military, etc.

Event data production

ERNIP

Input Events

Airport Corner

Input Events

Events Data “owners”

DNM

External

Network Events Portlet Phase 1



Benefits of NET – why we want it Increase efficiency of data collection and dissemination:

Centralise the events information collected through various sources Improve the visibility of the complete set of data on events information available in the

agency Cost reduction, complexity reduction

Improve information sharing internal and external Enable access to event information according to user needs/interest Increase awareness on events and their potential updates Reduce occurrences of missing information

Increase event data quality Reduce data duplication Improve data content (coherence and consistency checks between events) Improve modelling of the event(s) to include them in planning processes (and tools)

Expected Result: Support a more efficient response to the traffic

demand Better use of human resources (more time for analytical tasks, less time for editorial/admin tasks); Refine traffic demand (flight intentions) and required mitigation actions, taking into consideration

the impact of event(s) on the Network operations; Better use of sector capacity and/or airspace structures improving flight efficiency; Reduce delays, shorten routes flown



26 Sep 2014

What we have achieved so far Integration of 5 event data sources:

ERNIP ATFCM Special Events AXIS Events Military Events (Airport Corner Events – some issues to be resolved before NM 18.5) Transition Plan for Major Projects

Unrestricted Access to information according to users needs Events can be searched 10 years in the past and 20 years in the future; In Calendar – only events relevant to the specific month/day are listed; Deleted events are accessible (visible; no archiving yet); All changes are recorded, along with author and timestamp

Ability to subscribe to notifications – increasing awareness on events

Ability to increase event data quality Improved coherence in event data modelling Ability to identify potential duplicates



What remains to be done 01/06/2013

30/06/2013

NM 18.0

Start

NM 19.5

Preparation

Project Charter Project Plan

Deliverables:

Phase 1

Package 1 Functionality

Deliverables:

NM 18.5

NM 19.0

Phase 3


Deliverables:

Phase 4


Deliverables:

Model Improvements

Calendar

Reporting/ Notifications improvements

Search improvements

Map View Map improvements

Integration Pack

NET1

Network Events Phase 1 operational

since 12 March2014 (R18.0)

B2B interface

Phase 5


Deliverables:

Phase 2


Deliverables:



What next for you Access Network Events portlet and get familiar to current

functions/presentation Participate to OPT in September 2014 Provide comments ([email protected];

[email protected] ) On-line help will be deployed with NM18.5 Web training may be developed if needed Further improvements in next NM releases – refer to the future NM

Release Notes





Questions



v1.0

FB626: Provision of Departure data


FB626: Provision of Departure data Background

NM receives DPI (Departure Planning Information) messages from CDM Airports (Collaborative Decision Making Airports).

The DPI messages of a flight can contain TOBT and TSAT information. TOBT (Target Off-Block Time):

Provider: Aircraft Operator or Ground Handler What is TOBT: Estimation by the Aircraft Operator or Ground Handler of the time

that an aircraft will be ready: all doors closed, boarding bridge removed, push-back vehicle available and ready to start up / push back immediately upon reception of clearance from the TWR.

TSAT (Target Start-Up Approval Time): Provider: Tower - ATC What is TSAT: The time provided by ATC that an aircraft can expect for its start

up / push-back approval, taking into account TOBT (Target Off-Block Time), CTOT (Computed Off-Block Time) and/or the traffic situation.



FB626: Provision of Departure data Today (NM18.0) Available today (NM18.0)

TOBT and TSAT are currently received from 5 A-CDM Airports: EBBR (Brussels), LSZH (Zurich), ENGM (Oslo), LIRF (Roma), LEMD (Madrid).

TOBT and TSAT information are available in the Operational Log of a flight:


CHMI

NOP Portal


FB626: Provision of Departure data NM18.5

Request: Today, the TOBT and TSAT are “lost” inside the operational log. The Aircraft Operators request to see the TOBT and TSAT fields for their

flights departing from CDM-Airports.

Benefit: Improve operations of AOs by providing them situational awareness when

their flights are at an outstation CDM-Airport.

New features of NM18.5: The TOBT and TSAT fields will be displayed for flights departing from a

CDM-Airport on the NOP Portal and CHMI. This information will be presented in the Flight Data (CHMI) / Flight Details

(NOP Portal).





NM18.5: CHMI

[email protected]




NM18.5: NOP Portal


FB626: Provision of Departure data Impact

Impact: No impact for Users that don’t use TOBT and TSAT TOBT and TSAT are now available in a more user friendly manner.



4- Questions

Any questions?



v1.0

FB638: Airspace Management Monitoring


NM shall support the European Commission by providing relevant input for the preparation of the Single European Sky Performance Scheme - includes Union-wide performance targets and Key Performance Indicators (KPIs), - before the reference periods and for monitoring the achievements during the periods

1- Background



66

Environment Key Performance Area - KPIs Reference Period 2 - 2015 to 2019 • Rate of planning CDRs - the ratio of aircraft filing flight plans via CDRs and the number of aircraft that would have planned them • Effective use of CDRs - ratio of aircraft using CDRs and the number of aircraft that would have planned them Becomes mandatory for NM and Member States to monitor the effectiveness of the booking procedures for FUA

1- Background

[email protected]


Work already started on KPIs in FB601 - Release 17.5.2 Improve the algorithm for calculating the alternate route

for a given CDR segment Improved algorithm will take into consideration the geographical coordinates of the points to calculate distances and directions of routes which is mandatory for the fully correct and stable assessment of the FUA KPIs

67

2. New Features

[email protected]


68

2. New Features

[email protected]


2. New Features

• Compute the ASM FUA KPIs for Free Route Airspace As described in the updated version of the ASM Handbook - Section 7



3- Impact of the FB

No operational impact on NM users

KPIs will be reported through existing ASM CDM processes and available through NM Interactive Reporting Meets need of NM and Member States for SES

Performance Scheme RP2 – Starting 1 January 2015



4- Questions

Any questions?



v1.0

FB657: CSST (Call-Sign Similarity Tool) improvements


1- Background

• FB657 Developed to improve CSST Version 18.0 following user feedback.

• Enhance CSST functionality and make the application more

attractive to existing and new users.



2- Modification to Transformation Rule default setting

The idea behind the transformation rule is that the user wants to keep a link as far as possible between the Commercial Flight Number (CFN) and Call Sign (Example 1234 becomes 123A).

Current default behaviour : CSST tries to find a conflict free solution according to the transformation rule. Where it finds no solution CSST defaults to ‘ATC format and preferences’ rule and proposes solutions which are NOT according to the transformation rule.

New behaviour : With a modification to the deconfliction screen, when user selects transformation rule, the ‘ATC Format and preferences’ rule is disabled. Conflicts not resolved with Transformation rule are marked as No Solution. The user can then analyse these conflicts separately.



75

Current Behaviour Selecting Transformation rule.

[email protected]


New Behaviour with modified screen: If user selects Transformation rule then ATC Format and preferences are disabled



77

3- Impact of the FB

• Transformation rule operates according to user expectations.

[email protected]


Call Sign Similarity Tool Access

Access using NM token id enabled for CSST (free for existing tokens)

Step 1: NM Service Request Form at: http://www.eurocontrol.int/network-operations/access-service-request-

form Step 2: CSST Stand alone access at:

https://www.nm.eurocontrol.int/PORTALCSST/gateway/spec/index.html


http://www.eurocontrol.int/network-operations/access-service-request-form












79

4- Questions

Any questions? Further information at [email protected]

[email protected]



v1.0

FB659: ATFCM Domain Improvements


Scope

Changes in Scope CR_035917 - Change in traditional flight suspension message comment

CR_036439 - Visibility of flights adjusted to the clock

CR_036021 - Delay Confirmation Threshold



CR_035917- Change in traditional flight suspension message comment


Airports opened can be not available for different reasons. The comment of the suspension in case of Zero Rates (XCD/FCM) has been

harmonized from CLOSED to AERODROME OR AIRSPACE OR POINT NOT AVAILABLE.


Scope







A regulated flight can become not regulated whenever a regulation is cancelled or period is adjusted. A slot cancel message (SLC) is sent.

The regulation ID and the delay suffered are still presented in the flight lists for information. In this situation the flight is ‘adjusted to the clock’. An ‘a’ will be presented in the Delay column to identify those flights.


`


Scope






CR_036021 - Delay Confirmation Threshold 1- Background

Flights crossing exceptional regulations (strike, scenarios) are suspended (FLS).

Airspace Users have to confirm (FCM) to operate. Objectives:

Inform of the closure. Give airspace users the possibility to confirm to receive a slot or cancel. Improve predictions and free capacity.

Limitations No alternatives given. No delay information in the suspension message. Initial slot is lost.

Consequences Prediction and capacity objectives not achieved. Flights close to the end of the closure are suspended. Sequence based on confirmation time stamp.



CR_036021 - Delay Confirmation Threshold 2- New Features

Operational Groups (ODSG and AOG) supported NM system enhancements on

the flight confirmation process in order to: Alleviate Airspace Users of unnecessary workload. Improve network predictability and capacity. Improve CDM process during suspension mechanism.

The New Delay Threshold Feature will: Instead of suspending all flights, establish a Delay Threshold at regulation level. Allocate flights with delays below threshold value. Suspend flights with delays above (EOBT-2h). Include the delay information in the suspension message. Book the initial slot during the response by time period (20’). Allocate flights that are confirmed during the response by time period. Keep suspended and free the slot of flights that are not confirmed after response by time period. Delay Threshold value will be published in the AIM and showed in regulation description. This improved mechanism will be used in a trial mode for Scenarios (rerouting and level cap). The usage will be extended later on to other operational situations (strikes, airport non availability).



CR_036021 - Delay Confirmation Threshold 2- New features

Before Estimated Off Block Time (EOBT) – 2 hours


Flight not suspended



Regulation Description `




At Estimated Off Block Time (EOBT)- 2 hours




During Resp.by time period (20’)



CR_036021 - Delay Confirmation Threshold 3- Impact of the FB

[NEW] Flight Suspension Message Format Example Message : Sent to: LFFAPVPX @AFTN YKTESTCA @AFTN GMMMZQZX @AFTN TLSMDAF

@SITA LFPOZPZX @AFTN LFPOYEYX @AFTN. Message description:-TITLE FLS -ARCID AFR8788 -IFPLID AA00002595 -ADEP LFPO -ADES GMMN -EOBD 981111 -EOBT 0810 -PTOT 1000 -RESPBY 0630 -REGUL DTS9811 -COMMENT SUSPENDED DUE TO DELAY EXCEEDING THRESHOLD VALUE. SEND FCM BEFORE RESPBY TO SECURE PTOT. ALTERNATIVELY, REROUTE, OR UPDAT EOBT WITH A DLA MSG, OR CNL -TAXITIME 0010 -REGCAUSE CE 81


Provisional Take-Off Time Response by


Impact of the FB on Airspace Users current procedure,

Monitor suspended flights. Confirm the flight, slot already lost. Flight gets the delay but slot lost. Consider other alternatives before EOBT-2h (rerouting).

New procedure, Monitor delayed flights that could be suspended at EOBT-2h. Consider alternatives before EOBT-2h (rerouting). Monitor suspended flights 2h before estimated off block time. Take action on suspended flights between EOBT-2h and the next 20 minutes.

Systems, New Provisional Take Off Time (PTOT) field in the suspension message New Response By field in the suspension message.


CR_036021 - Delay Confirmation Threshold 3- Impact of the FB


CR_036021 - Delay Confirmation Threshold 3- Extra Information

A dedicated OPT session (registration required) will be organized between 1/9/2014 to the 12/9/2014 (weekdays).

To participate and receive more details, please send an eMail to [email protected].

Training Material can be found in Eurocontrol Training Zone.

ATFCM_Users_Manual will be updated and published by 1st August.




Any questions?



v1.0

FB660: Flight Planning Improvements


1- Background

FB660 has been included in the NM18.5 release to continue the evolution of the NM Flight Planning Services



2- New features

CR_023755 - Check that an EOBT update does not create a duplicate flight plan Background One of the IFPS fundamental rules is that no two flight plans with the same call sign should be allowed to exist within the IFPS Zone for flights where the calculated profiles overlap in time. This rule is enforced by IFPS for FPL messages as part of the association functionality. However, the rule is not currently enforced for other flight plan associated messages that may cause two flight plans with the same call sign to overlap in time.

Change in NM18.5 IFPS shall identify flight plan associated messages that update the EOBT of a stored flight and cause two flight plans with the same call sign stored in IFPS to overlap in time and include a warning in the outputted ACK message of the flight plan associated message.



2- New features

CR_033322 - Modify PROF201 error message Background Currently, the PROF201 error when related to an undefined route reads: PROF201 CANNOT CLIMB OR DESCEND ON MTL A3 EVALA IN FL RANGE CLOSED, BECAUSE OF UNAVAILABLE LEVELS ON A3. The "CLOSED" is misleading. There is a fundamental difference when the route is closed. For closed routes; IFPS will modify the route, whereas when the route is undefined, DCT may be used. Change in NM18.5 The PROF201 error text shall be reworded to correctly reflect the difference between a closed route and an undefined route.



2- New features

CR_035119 - Enhancement of IFP indicators feature Background With experience gained in operations, it has been requested that IFPS Staff have the possibility to include two new IFP/ indicators in distributed flight plan messages, one for invalid equipment and one to identify when the routing has been coordinated with ATC. Change in NM18.5 The error message flag: IFP/ERREQPT shall be added to the list of Message Error Flags available to the IFPS operator. The error message flag: IFP/ERRRTECOORD shall be added to the list of Message Error Flags available to the IFPS operator.



2- New features

CR_033624 - Include field 15 in an ACH resulting from an AFP for a change of flight level Background Currently, when an AFP only changes the flight level, the field 15 is not inserted in the resulting ACH. Change in NM18.5 When the change of flight level in the AFP generates an error in the rest of the route, the field 15 will be repeated in the ACH sent to ATC Units. This change only applies to ICAO format ACH messages because the ADEXP format IACH messages already contain full data.



2- New features

CR_036651 - ACH message shall respect the field 18 rules for output Background Following ICAO 2012, the ACH message is the only message that does not respect the correct field 18 output format. The output of Field 22 does not contain all the field 18 information as it should, but only the DOF/, SRC/ and ORGN/ indicators. Change in NM18.5 The output in an ACH of Field 18 shall contain complete Field 18 content. This change only applies to ICAO format ACH messages because the ADEXP format IACH messages already contain full data.



2- New features

CR_036651 - Integration of IFPS users manual into NOP Portal Background This change supports the future electronic publication of the IFPS Users manual. Change in NM18.5 When an error is presented on the IFPS Validation (IFPUV) interface on the NOP Portal, the User will be able to hyperlink to the relevant page if the IFPS Users Manual where requirements, explanation and procedures are detailed.



3- Impact of the FB

Impact of FB660 on externals ANSP flight plan data processing systems that receive IFPS

messages may need to be upgraded to process correctly the change to the ACH messages and the new IFP/ indicators.

Flight plan originator procedures, MMI and systems may need to be updated to correctly handle the ACK messages for DLA/CHG messages that overlap, and the change to the text of the PROF201 error.



4- Questions

Any questions?



v1.0

FB661: CHMI Improvements


1- Background

FB661 CHMI Improvements: Occupancy counts are becoming the primary tool used by core area FMPs for

traffic monitoring. OTMVs (Occupancy Traffic Monitor Values) are archived but occupancy counts cannot be queried on Data Warehouse.

The Monitoring of flight profile are becoming of primary importance for the analysis of traffic complexity in the context of STAM (Short-Term ATFM Measures). PTRs (Profile Tuning Restrictions) and intruders are two criteria that need to be investigated in post-ops.

For the time being no post-ops analysis is supported by CHMI on STAM procedures. This is necessary for monitoring the correctness of OTMVs and perform STAM post-ops analysis.

New features: CR_035841: Ability to see the PTRs in Archive CR_033641: Archiving OTMVs CR_031145: Access to Occupancy counts in CIFLO Archive menu


http://www.cfmu.eurocontrol.int/arsys/servlet/ViewFormServlet?form=CFMU:Change_Request&server=remedyops&eid=CR_035841




2- New features


CR_031145: Access to Occupancy counts in CIFLO Archive menu



CR_033641: Archiving OTMVs

2- New features




CR_035841: Ability to see the PTRs in Archive

2- New features




3- Impact of the FB

CR_031145: Access to Occupancy Counts on Archive is new in the Data Warehouse architecture, there is a risk of long response time.

For this reason the NM 18.5 implementation is prototype in order to validate the technical solution.

FMP pilot sites will be requested to validate the implementation. There is no impact on external systems and procedures.



4- Questions

Any questions?



v1.0

FB668: Performance Work Program


1- Background

Short background of the FB: The new NMIR document is available for NMIR users (Network Manager

Interactive Reporting tool) impacted by the ATFM IR It is composed of 3 reports:

The ATFM Compliance - Slot Tolerance The ATFM Compliance - Departure Tolerance The ATFM Compliance - Flight Plan Suspension

These reports retrieve weekly figures and flights list for a given country for each of the reports

The name of the document is « ATFM Compliance – Weekly Monitoring » and is placed under the « Statistics > Overall Pictures » categories

For any questions concerning the access to the NMIR tool, please to contact [email protected]



2- New features


ATFM Compliance – Slot Tolerance


2- New features


ATFM Compliance – Departure Tolerance


2- New features


ATFM Compliance – Flight Plan Suspension


3- Impact of the FB

The only impact for the externals is the availability of the document if they are users of the NMIR



4- Questions

Any questions?



v1.0

FB619: Slot swapping process


1- Background

ATFM Slot-swapping already exists, but needs to be improved to meet Airspace Users needs. The UDPP (User Driven Prioritisation Process) project team and the NM Slot-Swapping Task Force joint forces to collaboratively propose new processes to answer Airspace Users expectations.

The UDPP Step-1 is a SESAR project, with a deadline to provide the Validation Results by End-2014. The changes need to be implemented in time to be able to run the Live Trial that will validate the Slot-swapping improvements.

Several B2B Users requested more information on Regulations to be available by B2B.

The FB619 will provide via B2B information required for the trial in the operational environment, available for all users.



2- New features

FB619 will provide the ATFCM regulations’ list and details via B2B: Regulation id Applicability period Regulation state Regulation reason Cherry picked (or not) Location (TV id, TV description (as in ANM), TV flight levels, reference

location) Regulation rates per time period (normal, pending, equipment, supplementary

as in CHMI or NOP Portal) Others: Remark (as in ANM), autolink (or not) and linked regulations, No

delay window (around ETO). The data and interface requirements will be described in the

FlowServices B2B Reference manual.



3- Impact of the FB

No impact for the users not using this information. Need to adapt Users’ systems to use the information.



4- Questions

Any questions?



v1.0

NM18.5: Way forward


Way forward to NM18.5 Migration

Mid-July 2014: Recording of the Presentation available

Mid-July 2014: New version of NM Release Notes with Release migration plan

From the 1/9/2014 to the 12/9/2014: NM18.5 OPT (Operational Testing) covering: CHMI – no registration required NOP Portal – no registration required NOP B2B (pre-ops environment) – no registration required FB659: ATFCM Domain improvements - CR_036021 (New ‘Delay

Threshold’ regulation) - registration required Instructions for OPT will be sent in August via the Release Notes (and

associated mailing).

NM18.5 migration: start on the 23 September 2014 (1 week)

Any question: [email protected]




Any more questions?



Thank you for your participation


Documents

A presentation of the NM18.5 to Externals via video ... · PDF fileA presentation of the NM18.5 to Externals via video-conference took place on the 9th of July 2014. ... Stop boundary