[email protected]The presentation to Externals of the NM22.5 Release via video-conference took place on the 18 th of September 2018. Please find below: • The link toward the video recording of this presentation: https://www.eurocontrol.int/node/12347 / • The link toward the NM22.0 Release Notes: https://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release- deployment/nm-release-notes-current.pdf • The slides used during the Presentation (below in this pdf)
The presentation to Externals of the NM22.5 Release via video-conference took place on the 18th of September 2018.
Please find below:• The link toward the video recording of this presentation:https://www.eurocontrol.int/node/12347/
• The link toward the NM22.0 Release Notes:https://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/nm-release-notes-current.pdf
• The slides used during the Presentation (below in this pdf)
Presentation is recorded; recording (audio and slides) will be availableon the Eurocontrol public website in a few days: http://www.eurocontrol.int/lists/publications/network-operations-library?type=3317&keyword=(URL available in §1 of the NM Release Notes)
• Goals of the presentation:• Present the new features of the Release NM22.5.• 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 [email protected]).
• Why doing the presentation now? ⇒ SHOM3 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.
• 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:http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/nm-release-notes-current.pdf• 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)
2.1- NM22.5: The OPT (Operational Testing)(Release Notes §4.2.2)
11
NM22.5 is available for testingwith the OPT (operational testing) session!
NM22.5 OPT session started on the 17th of September and will end on the 7th of October.
With the NM22.5 OPT you are able to: Test NM22.5 on your systems with your procedures. Download and test the new NM22.5 CHMI. Test the new NM22.5 NOP Portal. Test some new FBs (operational scenario provided in the OPT guide).
B2B: NM 22.5 will be available on PREOPS (as from 15/10/2018 - 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).⇒ OPT Instructions (Release Notes § 4.2.2):
2.1- NM22.5: Important notifications(Release Notes §2.2)
12
•Browsers recommended in NM22.5:• Internet Explorer 11• Edge• FireFox• ChromeThe NM web-based HMIs will have been fully tested on Internet Explorer 11, Edge and FireFox.
• The recommended operating system is Windows 10, Windows 7 will also be supported.
• NM B2B: Decommission of NM B2B NM20.5 webservice.
The improvements will allow AMCs to perform the following allocation combinations via AUP/UUP: Overlapping area reservations and associated FBZs: NM will allow
overlapping reservations/FBZs by time/level. Overlapping FBZ reservations: NM will allow overlapping reservations of
FBZs by time/level. Overlapping area reservations: NM will allow different reservations of the
same area to overlap with each other by time and/or level. Partial overlapping area reservations and associated FBZs: NM will
allow overlapping reservations/partial FBZs by time/level.
NM system will provide a warning to the local AMCs to ensure that the combinations selected are based on clear decisions and not by mistake
CR_043707CR_043707: Process T-DPI-s received after forced CTOT
1- New features A T-DPI-s message received after the CTOT was forced will no longer be rejected Such a T-DPI-s will be processed according to the rules for processing a T-DPI-s with a
TTOT later than the upper bound of the STW, which usually results in a new CTOT 2- Background - Why Through a TTOT value (included in the T-DPI-s) which is later than the upper bound of the
STW, the CDM airport informs NM they are not able to comply with the forced CTOT3- Impact of the CR TWR will receive a new CTOT when they are not able to make the STW, even when the
previous CTOT was forced Cherry picked flights that were forced in the slot list due to an MCP (Mandatory Cherry
Pick) regulation can be unforced by a T-DPI-s message received from the CDM airport The concerned AO(s), FMP(s) and NMOC are not immediately alerted when this occurs
4- Future improvements As a future improvement, when the CTOT was forced due to an MCP regulation, the owner
of the regulation and the AO should be informed in order to ease the coordination process
1- New features An A-DPI received for a flight suspended by the airport via a C-DPI will be rejected An ERR message with ATFM comment “FLIGHT IS SUSPENDED” is sent
2- Background - Why No network impact assessment is performed on reception of an A-DPI; the flight can
therefore create an over-delivery
3- Impact of the CR An A-DPI received after a C-DPI will be rejected CDM airports should establish procedures to update TOBT or TSAT which trigger a T-DPI-t
or a T-DPI-s message (instead of sending A-DPI directly after C-DPI) Advanced ATC TWR airports should establish procedures to advise the pilot to send
DLA/CHG, which de-suspends the flight
4- Future improvements In a future release, Advanced ATC TWR airports will have the option to send a Tower
Update A-DPI that will de-suspend the flight and trigger a slot re-computation
CR_043611: Preserve TOBT and TSAT after EOBT update
1- New features The rules for preserving the TOBT and TSAT values will be changed as follows: TOBT and TSAT will be reset upon → reception of a DPI message without these values TOBT and TSAT will be preserved upon → reception of a flight plan update (DLA/CHG), a
manual de-activation, a forced CTOT
2- Background - Why Improving the rules for deciding to preserve/disseminate or reset the TOBT and TSAT
values; keep the alignment with the values from the airport as much as possible
3- Impact of the CR The operational stakeholders using the NM B2B and B2C applications should be aware of
the updated rules for resetting/preserving the TOBT and TSAT values These TOBT and TSAT values are more aligned with the values available locally at the
The impact is on B2B clients who may see the name field of a point as blank which was not allowed before. Note: Name field is different from Point ID.
This is an enabler for the European AIS Database (EAD) download of Annex 15 data to Central Airspace and Capacity Database (CACD).
This FB is to prepare the NM Airspace data model:For the Aeronautical Information Exchange Model(AIXM V 5.1)Downloading worldwide Annex 15 data from EAD, Points, Navaids, aerodromes, FIRs, UIRs, Routes and Other Airspaces.Merge Annex 15 data with NM ATFCM data,Merge Annex 15 data with NM ASM data,The import will be a staged Process and not a big bang.
Stakeholder(s) impacted : Flow Manager (FMP) Airspace Manager (AMC) Airspace User (Civil) Airspace User (Military) ENV data provider AO or CFSP ARO Internal NM Air Navigation Service Provider (ANSP)
36
FB965
Service affected
Flight Planning FlowAeronautical
Information/AS data
Reporting
Other
Internal computation
Data structureUser Interface
ProceduresTraining Yes Yes
B2B Yes
Other
Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed.
CR_043836 - IFPS to warn when new NAS (National Airspace) entered after route generation
IFPS will send a warning to the IFPS Staff for new NAS that are entered to try to prevent a rerouting that is not operationally acceptable to the Aircraft Operator. The errors are associated to the manual processing of AFP/FNM/MFS messages that have a new route constructed by IFPS.
The external visibility of the error is unlikely, but is possible when the message is manually rejected by the IFPS Operator (not normal procedure).
Users may see the new error if they have sent an AFP to IFPS that is manually rejected by the IFPS Operator.
CR_043824 - STS/MEDEVAC shall be the same as STS/HOSP and STS/SAR for 8.33 error
Today, IFPS raises an error when a flight that is not 8.33 equipped (no Y in item 10a) but flies into Airspace requiring 833 equipment, except for special flights STS/HOSP and STS/SAR.
With NM22.5, STS/MEDEVAC flights will also be excluded.
FAM functionality ETFMS monitors regulated and non-regulated flights to identify flights that were planned to
be airborne but were not reported as such (no CPR/FSA/DEP received); Identified flights are shifted in their ATOT by 5 minute steps; If the flight is still not confirmed airborne, it is suspended after a time parameter of 30 or
120 minutes; FLS message with the comment ‘NOT REPORTED AS AIRBORNE’ is sent to the AO &
ATC -> then a DLA/CHG message or a DPI from CDM airport is required to de-suspendthe flight;
Purpose of FAM is to improve network predictability (e.g. release unduly occupied slots)
FAM applicability NM22.0 30 minute parameter - flights departing from and / or landing at areas where CPRs are
received by the NM and FAM activated. Flights departing from and landing in non CPR-covered areas are not affected by FAM, irrespective if they fly through CPR covered ornon CPR-covered areas en-route.
120 minute parameter – flights departing from non-FAM-enabled areas and with adestination in FAM-enabled area with EET of more than 3 hours.
FAM is applied on all flights, whether regulated or not, that are: departing from landing in
crossingan area where CPRs are received by the NM and FAM is activated.
30 minute FAM parameter is reduced to 25 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.
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;
52
Extension of FAM applicability and reduction of FAM parameter from 30 to 25 minutes
CPR coverage area has extensive and uniform coverage;
The change will allow for better traffic counts on the ACC crossed by these flights, better predictability and homogenous approach to traffic analysis.
3.2- Background2. Reduction of FAM parameter from 30 to 25 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;
NM 22.5 marks the first step of reduction from 30 min to 25 min;
The objective is to 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
2.1- NM22.5: The OPT (Operational Testing)(Release Notes §4.2.2)
58
NM22.5 is available for testingwith the OPT (operational testing) session!
NM22.5 OPT session started on the 17th of September and will end on the 7th of October.
With the NM22.5 OPT you are able to: Test NM22.5 on your systems with your procedures. Download and test the new NM22.5 CHMI. Test the new NM22.5 NOP Portal. Test some new FBs (operational scenario provided in the OPT guide).
B2B: NM 22.5 will be available on PREOPS (as from 15/10/2018 - 14:00 UTC)
All what you need is to already have access to NM systems. No registration required (unless you want to exchange FPL messages with OPT platform).⇒ OPT Instructions (Release Notes § 4.2.2):
NM22.5 migration has been postponed by one month due to the implementation of further improvements identified following the NM system outage on 3 April 2018.
NM22.5 migration is planned to start on the 13/11/2018 (last around 1 week) Detailed Release migration plan may be found in the NM Release Notes (§4.2.3). 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)
