The presentation to Externals of the NM22.5 Release via video-conference took place on the 18 th of September 2018.

Transcription

1 The presentation to Externals of the NM22.5 Release via video-conference took place on the 18 th of September Please find below: The link toward the video recording of this presentation: The link toward the NM22.0 Release Notes: The slides used during the Presentation (below in this pdf)

2 Presentation of NM22.5 to Externals EUROCONTROL Network Manager Directorate 18/09/2018 v1.1 Classification TLP : White (Public)

3 Welcome to the Presentation of NM22.5 to Externals Agenda 1- Introduction and interface set-up 2- NM22.5 Release presentation: 2.1- Important notifications related to NM22.5 migration OPT (operational testing) session 2.2- FBs (Functional Blocks) presentation 3- Way forward toward NM22.5 migration NM22.5 migration has been postponed to the 13/11/

4 1- Introduction: Recording Presentation is recorded; recording (audio and slides) will be available on the Eurocontrol public website in a few days: (URL available in 1 of the NM Release Notes) 4

5 1- Introduction 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 at ). Why doing the presentation now? SHOM3 Gate (Software Hand-Over Meeting) is passed. System testing and Operational Acceptance testing are still ongoing, so Release content may slightly change until the Release migration. 5

6 1- Introduction: Webex interface set-up To be done now: 1- Click on the blue tab in the middle-top of the screen: 2- Click on «Participants» 3- Click on «Chat» 6

7 1- Introduction: How to ask questions - by chat Questions may be asked: By chat (preferred) or orally. At the end of each Functional Block presentation. How to ask a question by chat: 1- Type your question in the Chat window 2- Select «Everyone» and click on «Send» 3- The presenter will read the question and reply to it orally 4- If at the end of the answer you still need clarifications, please type them in the Chat window. You can type your question during the presentation 7

8 1- Introduction: How to ask questions orally 0- Go to the participant list 1- Click on «Raise hand» and wait 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» If for any reason you did not get the floor, click on the micro and speak 8

9 2- NM22.5 Presentation 9

10 2.1- The NM Release Notes 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: es/content/documents/nm/networkoperations/release-deployment/nmrelease-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) 10

11 2.1- NM22.5: The OPT (Operational Testing) (Release Notes 4.2.2) NM22.5 is available for testing with the OPT (operational testing) session! NM22.5 OPT session started on the 17 th of September and will end on the 7 th 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/ :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): Questions: nm.opt@eurocontrol.int 11

12 2.1- NM22.5: Important notifications (Release Notes 2.2) Browsers recommended in NM22.5: Internet Explorer 11 Edge FireFox Chrome The 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. 12

13 Any questions? 13

14 2.2- NM22.5 FBs and CRs presentation Only new features impacting operations and Externals are presented Airspace Management and Advanced FUA FB951 ASM - Advanced FUA process improvement Airport and TMA Network Integration FB949 DPI Improvements EAIMS (European ATM Information Management Service) Operations Improvements FB957 NM airspace model evolution FB965 Airspace Data Domain improvements FB964 Flight Planning Domain improvements FB966 ATFCM Domain improvements 14

15 Presentation of NM22.5 FB951: ASM Advanced FUA Process Improvements v1.3

16 Background Problem statement: Current NM systems do not support local requirements for more flexibility in the management of AUP/UUP in consequence of: Goals: Increased management of RSA in FRA environments; Increased FBZs (Flight Buffer Zones) Implementation; Increased interoperability via B2B with Local ASM tools. Allow local AMCs to manage airspace structures allocation with more flexibility. Expected Benefits: More efficient airspace management, optimizing the airspace allocation. 16

17 Changes introduced 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 17

18 Partial/NO overlapping area reservations and associated FBZs Partial overlap between Area and FBZ can be either horizontal or vertical. Partial vertical overlap dependent FBZs As per AIS publication (e.g. partial level band coverage) dynamically defined (e.g. levels band dynamically allocated) Partial horizontal overlap with published FBZs set of limited FBZs including dependent FBZ one FBZ with horizontal limited dimension regular FBZ with sub-modules set of FBZs with horizontal limited dimension 18

19 New features A warning instead of an error message 19

20 New features The systems impacted by the software changes are the following: CIAM: allow the simultaneous publication of RSA and associated FBZs via AUP/UUP. ASM Local Tools: being able to manage the simultaneous publication of RSA and associated FBZs via AUP/UUP. NM Web Services: being able to process the simultaneous publication of RSA and associated FBZs via AUP/UUP The identifier of a FBZ can contain a new character in case of multiple FBZs For example, given an RSA TSA21, the associated FBZs may be named TSA21Z, TSA21Z1, TSA21Z2, TSA21Z3,... TSA21Z9 20

21 Impact of the FB Service(s) impacted: B1-3 Airspace management B9-3 Network Manager Business-to-business (B2B) web services B9-2 Network Operations Portal B9-1 Collaboration Human Machine Interface Service affected FB951 Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Yes Data structure User Interface Procedures Training B2B Yes Yes Airspace Management Network Operations Portal Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. Yes Yes Interface with ASM tool Update ASM Tools 21

22 Stakeholder(s) impacted: Airspace Manager (AMC) AO or CFSP Impact of the FB AMC YES NO Remark Procedures X Current ASM Handbook procedures Systems X Local ASM Tools allow overlapping Way of working X Process new warning messages Other X AOs or CFSPs YES NO Remark Procedures X Current ASM Handbook procedures Systems X Process possible overlapping of Restrictions Way of working X More complex airspace volume notification. Not a issue via B2B Other X 22

23 Questions Any questions? 23

24 Presentation of NM22.5 FB949: DPI Improvements v1.2

25 Stakeholders impacted: Flow Manager (FMP) AO or CFSP Non-CDM Airport CDM-Airport Advanced ATC TWR Airports 1- Impact of the FB FB949 Internal computation Data structure User Interface Procedures Training B2B Flight Planning Service affected Aeronautical Flow Information/AS data Yes Yes Yes Yes Reporting Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. 25

26 CR_043707: Process T-DPI-s received after forced CTOT CR_ 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 CTOT 3- 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 26

27 CR_ CR_043706: Send SLC when flight no longer affected by regulation 1- New features When a flight not yet confirmed airborne becomes de-regulated, due to a regulation cancellation, an SLC is always sent (even when its OBT is too close or the flight is already taxiing) 2- Background - Why The TWR controllers from CDM airports asked to be informed when the flight becomes deregulated, no matter how late that happens, for increased awareness of their margin for operation 3- Impact of the CR Airports may expect a late SLC, i.e. even when the flight is already taxiing 27

28 CR_ CR_044026: Reject A-DPI received after C-DPI 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 28

29 CR_ 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 airport 29

30 Any questions? 30

31 Presentation of NM22.5 FB957: NM Airspace Data Model Evolution v1.1

32 1- FB957 Background 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. 32

33 2- FB957 New features CR_ Point Name blank: CACD will allow the point name field to be blank for: Reference Point name. Terminal Point name. Way point name. This was previously not allowed and is required for downloading points from EAD. 33

34 4- FB957Questions Any questions? 34

35 Presentation of NM22.5 FB965: Airspace Data Domain improvements v1.1

36 1- Impact of the FB 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) Service affected FB965 Flight Planning Flow Aeronautical Information/AS data Reporting Other Internal computation Data structure User Interface Procedures Training Yes Yes B2B Yes Other Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. 36

37 2- Impact of the FB In NM 20.5, a new Restriction type forbidden For DCT was introduced which could only be used to define restrictions related to FRA. For NM 22.5 we will have the tool to allow forbidden for DCT for all types of Airspace. 37

38 2- New features The user needs the ability to express ForbiddenForDct restrictions in all Airspace types In slices of airspace and in time. Any type (also different from FRA) airspace. Capture DCTs planned through Restricted Airspaces (RSAs) etc.. Value: Correct capture of FPLs crossing airspaces illegally on DCTs Safety related as FPLs planning to cross active RSAs is an issue. 38

39 3- Background Why To capture flights filing on DCTs crossing an activated RSA. But not to capture flights filing on Routes (if allowed) crossing the same RSA. The RSA will have a minimum and maximum level defined where DCTs must be captured. Examples: EDR100A DCT's to be captured between FL100 and FL220 Finland accepts FPL that allow traffic to cross active RSA on ATS routes but not on DCT, and this also when FRA is applicable. To capture flights filing on DCTs crossing any other type than RSA of airspace where it is forbidden. To capture flights filing on DCTs in a particular slice of airspace where it is forbidden. 39

40 Any questions? 40

41 Presentation of NM22.5 FB964: Flight Planning Improvements v1.3

42 1- Impact of the FB Stakeholder(s) impacted: Airspace User (Civil) Airspace User (Military) AO or CFSP Non-CDM Airport CDM-Airport ARO FB964 Internal computation Data structure User Interface Procedures Training B2B Other Flight Planning Yes Yes Yes Yes Flow Service affected Aeronautical Information/AS data Reporting Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. Other 42

43 1- Impact of the FB For Users filing Flight Plan Messages to IFPS: The originator may see a change to the IFPS error text if they have sent an ATC Flight Plan (AFP) to IFPS that is manually rejected by IFPS Staff. Under certain conditions, flights with special status MEDEVAC will be automatically accepted in IFPS compared to the previous manual acceptance. 43

44 2- New features CR_ 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. 44

45 2 - New features -TITLE REJ -MSGTYP IAFP -FILTIM ORIGINDT BEGIN ADDR -FAC EGLLZTZX -END ADDR -ERROR ROUTE41: PLEASE CHECK NAS OF GENERATED PORTION: EI. -OLDMSG -TITLE IAFP -ARCID TSV0403 -ADEP KSEA -ADES LFPG -ROUTE M082F370 SAVRY 59N050W 59N040W 58N030W 57N020W SUNOT KESIX -FLTTYP S -ESTDATA -PTID SUNOT -ETO FL F370 45

46 2- New features CR_ 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. 46

47 Any questions? 47

48 Presentation of NM22.5 FB966: ATFCM Domain improvements v1.5

49 Stakeholder(s) impacted: Flow Manager (FMP) Airspace User (Civil) AO or CFSP Non-CDM Airport CDM-Airport Air Navigation Service Provider (ANSP) 1- Impact of the FB FB966 Internal computation Data structure User Interface Procedures Training B2B Other Flight Planning Flow Yes Yes Yes Service affected Aeronautical Information/AS data Reporting Other 49

50 1- Impact of the FB External impact mainly on FMP, AO/CFSP and Airports in terms of: Procedures; Client systems. In order to cope with two changes of the Flight Activation Monitoring (FAM) mechanism: 1. Extension of FAM applicability CR_043232: Flights overflying CPR coverage area to be subject to Flight Activation Monitoring 2. Reduction of FAM parameter from 30 to 25 minutes CR_042961: FAM parameter reduction 50

51 2.1 FAM overview 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-suspend the flight; Purpose of FAM is to improve network predictability (e.g. release unduly occupied slots) FAM applicability NM 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 CPRcovered areas are not affected by FAM, irrespective if they fly through CPR covered or non CPR-covered areas en-route. 120 minute parameter flights departing from non-fam-enabled areas and with a destination in FAM-enabled area with EET of more than 3 hours. 51

52 2.2 New Features Extension of FAM applicability and reduction of FAM parameter from 30 to 25 minutes 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. 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

53 FAM applicability 2.3 New Features 1. X FAM parameter: 25 minutes FAM parameter 25 minutes for EET less than 3 hours FAM parameter 120 minutes for EET more than 3 hours 2. X 3. FAM parameter 25 minutes for EET less than 3 hours FAM parameter 120 minutes for EET more than 3 hours X = FAM enabled CPR-covered areas 53

54 3.1- Background 1. Extension of FAM applicability 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. 54

55 2. Reduction of FAM parameter from 30 to 25 minutes 3.2- Background 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: Or contact: nmfamreduction@eurocontrol.int 55

56 Any questions? 56

57 Presentation of NM22.5 NM22.5: Way forward

58 2.1- NM22.5: The OPT (Operational Testing) (Release Notes 4.2.2) NM22.5 is available for testing with the OPT (operational testing) session! NM22.5 OPT session started on the 17 th of September and will end on the 7 th 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/ :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): Questions: nm.opt@eurocontrol.int 58

59 Way forward to NM22.5 migration 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 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) Any question related to the Release: 59

60 Any questions? 60

61 Many thanks for your participation! 61