The presentation to Externals of the NM21.0 Release via videoconference took place on the 15 th of March 2017.

Transcription

1 The presentation to Externals of the NM21.0 Release via videoconference took place on the 15 th of March Please find below: The link toward the video recording of this presentation: The slides used during the Presentation. The link toward the NM21.0 Release Notes: If any questions:

2 Presentation of NM21.0 to Externals EUROCONTROL Network Manager Directorate 15/03/2017 v1.5

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

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) nm.releases@eurocontrol.int 4

5 1- Introduction Goals of the presentation: Present the new features of the Release NM21.0. Operational Project Managers will present their Functional Block. Enable you to assess the impacts on your procedures or systems. Ask questions (today or by at Why doing the presentation now? SHOM2 Gate (Software Hand-Over Meeting) is passed. System testing and Operational Acceptance testing are still ongoing. 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. nm.releases@eurocontrol.int 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 nm.releases@eurocontrol.int 8

9 2- NM21.0 Presentation 9

10 2.1- NM21.0: Important notifications 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-next.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) nm.releases@eurocontrol.int 10

11 2.1- NM21.0: Important notifications (Release Notes 2.1) Browsers recommended in NM21.0: Internet Explorer 11 Firefox 52 ESR (Extended Support Release) In addition, NM applications are still supported on Firefox 45 ESR on best effort basis (regression testing has been performed) Windows versions other than Windows 7 are not supported for CHMI. Decommission of NM B2B NM19.0 webservice. Decommission of old NM B2B URLs on OPS: Before NM21.0 (port 16443), URLs start with: After NM21.0 (port 443), URLs start with: c.f. NM Release Notes for more information. nm.releases@eurocontrol.int 11

12 2.1- NM21.0: The OPT (Operational Testing) (Release Notes 4.1.2) You will be able to test NM21.0 in 5 days by participating to the OPT (operational testing) session! NM21.0 OPT session will start on the 20/03/2017 and last 5 weeks! With the NM21.0 OPT you will be able to: Download and test the new NM21.0 CHMI. Test the new NM21.0 NOP Portal. Test some new FBs (operational scenario provided in the OPT guide). All what you need is to have already access to NM systems. No registration required (unless you want to exchange FPL messages with OPT platform). OPT Instructions (Release Notes 4.1.2): Questions: nm.opt@eurocontrol.int nm.releases@eurocontrol.int 12

13 Any questions? 13

14 2.2- NM21.0 FBs and CRs presentation Only new features impacting operations and Externals are presented Topics order differs slightly from the order in the Release Notes. FB737 Support to flight efficiency Airspace Management and Advanced Flexible Use of Airspace (AFUA) FB780 Lead AMC Live Updateable Airport Programme FB778 DPI Improvements FB800 Airport Programme Free Route Airspace (FRA) FB781 Part Free Route Implementation at ACCs Cooperative Traffic Management (CTM) FB731 Scenario management FB826 Develop Arrival Planning Information B2B in NMOPS (PJ.24) FB839 Slot swapping - Front End FPFDE (Flight Plan and Flight Data Evolution) FB834 Improved restriction model and ATFM processes through use of enhanced flight plan data Operations Improvements CR_ Flight plan message filing and distribution in FIXM format via B2B FB819 NM B2B improvements FB814 IFPS Workload Evolutions FB820 Flight Planning Domain improvements FB821 Airspace Data Domain improvements FB822 ATFCM Domain improvements nm.releases@eurocontrol.int 14

15 Presentation of NM21.0 FB737: Support to flight efficiency v1.0

16 Objective Several actions executed by the Network Manager have been set to further improve flight efficiency in order to ensure appropriate benefits for the airspace users and fulfil the European environment/flight efficiency target. Our objective, through all initiatives, is to enhance the visibility for aircraft operators on possible other options in using the route network, post IFPS flight planning. Initial FPL is filed; Further analysis is done considering users constraints and real state of the network; Proposals are displayed back on the FPL originator; Last choice is yours. 16

17 Modifications Automatic RRPs generations based on the GRRT template parameters; Segregation of RRP generated by MILO position and IFPS. 19

18 Automatic RRPs generations based on the GRRT template parameters Group re-routing tool (Opportunity tool) will send RRPs to the subscribed AOs in automatic manner, in scheduled intervals. RRPs will be treated automatically, if this feature is requested by the user and defined in the GRRT template. AOs interested in receiving flight efficiency related RRPs/OPPs will have to subscribe to this service by submitting an to: Recommendation for AOs: review existing GRRT templates. 20

19 Automatic RRPs generations based on the GRRT template parameters 21

20 Segregation of RRP generated by MILO position and IFPS The RRP message will have a new comment COMMENT PURPOSE IS CDR OPPORTUNITY if proposal is generated by the MILO (Military Officer) position in NMOC. With this modification, it will be possible to distinguish RRPs created by MILO from those generated for the Flight Efficiency Initiative purposes. -TITLE RRP -ARCID XYZ53U -IFPLID AT ADEP LTFJ -ADES EDDL -EOBD EOBT ORGRTE N0439F380 TUDBUIJ Q26 TIXIP L602 BUDOP DCT PATAK DCT LALES L602 BABUS DCT SOPGA T170 RAPET T843 ARNIX T852 EKSAK/N0389F220 T852 TINSA T854 DOMUX DOMUX2G -RRTREF LTFJEDDL5003 -NEWRTE N0439F380 TUDBUIJ TUDBU Q26 DEGET DCT BELGA DCT DEXIT DCT SULUS T852 EKSAK/N0389F220 T852 TINSA T854 DOMUX DOMUX2G -RESPBY REASON OUTREG -COMMENT PURPOSE IS CDR OPPORTUNITY -TAXITIME 0015 nm.releases@eurocontrol.int 22

21 4- Questions Any questions? 23

22 Presentation of NM21.0 FB780: Lead AMC Live Updateable v1.5

23 1- Background The lead AMC concept is based on the delegation of AMCs responsibilities for coordinating Cross Border Areas (CBA) allocation, the availability of Conditional Routes (CDR), and in case of cross-border DCTs planned to be managed via AUP/UUP. The lead AMC concept is already applied for CBAs and each crossborder CDR 2 which extends through the area of responsibility of more than one AMC. Today the CHMI allows to update the lead AMC on an AIRAC cycle basis only. nm.releases@eurocontrol.int 25

24 2- New features (1/3) AMCs able to update the lead AMC on a daily basis as long as there is no impact on active AUPs/UUPs. Scope of the FB limited to AMC-Manageable Areas (AMA). RSA responsibility delegated to another AMC according to a Time Table List (TTL). Overlaps in allocation times avoided by means of the TTL. Conflicts in concurrent ENV/CIAM updates avoided having AMCs making changes within their own leadership time interval. AMC-A Lead AMC AMC-B Lead AMC Lead AMC Lead AMC nm.releases@eurocontrol.int 26

25 2- New features (2/3) RSA delegation implemented by CADF on D-1 at latest. Once the live update on the airspace delegation is committed, an Incremental Data Set (IDS) is produced and made available via B2B. 27

26 2- New features (3/3) Release presentation to externals 28

27 3- Impact of the FB Harmonisation of the AUP/UUPs promulgation process. Promotion and facilitation of the establishment and the coordination of Cross Border Operations (CBO) amongst different States. For the CADF to have a single PoC, especially needed in case of operational incident or network disruption situations. nm.releases@eurocontrol.int 29

28 4- Questions Any questions? 30

29 Presentation of NM21.0 FB778: DPI Improvements v1.5

30 1- Background Currently, SID (Standard Instrument Departure) information can be sent to ETFMS in DPI, FSA messages or FlightUpdate requests via B2B WS Acceptable values in the SID field: The ICAO designator of a SID as published in the AIP Since NM19.5 the value DCT treated by NM as direct clearance from TWR to the first en-route point The TWR/ATC is a reliable source and has better knowledge about the actual value of the SID, in accordance with the clearance given DCT clearances used especially for small airports. nm.releases@eurocontrol.int 32

31 2- New features CR_ CR_ further improve the acceptance and processing of the actual flown SID for the following SID values: A further point on the route The ICAO designator of a nearby waypoint or navigation aid point These will be treated as DCT clearance from TWR to the specified point! Provided a matching departure procedure has been defined in the NM database (CACD) Otherwise, the value will be rejected and an Oplog NOT_FULLY_PROCESSED with reason Unknown SID will be created NMOC will look for an optimal and realistic trajectory to connect the specified point with the route. nm.releases@eurocontrol.int 33

32 3- Impact of the FB On an operational need basis: CDM airports and Adv ATC TWR systems may update their systems to be able to send waypoints or navigation aid points in the DPI ANSP systems may be updated to be able to send waypoints or navigation aid points in the FSA or via the FlightUpdate request (B2B) The TWR/ATC, via the ENV coordinator, should notify NMOC to update the NM database (CACD) accordingly, using the dedicated procedure for notification of CACD updates to NMOC Processing the actual flown SID will result into improved flight profiles and improved traffic counts 34

33 4- Questions Any questions? 35

34 Presentation of NM21.0 FB800: Airport Programme v1.5

35 1- Background CDM Data originated from a CDM airport better disseminated by NM Increased situational awareness for Airlines outstations of their CDM departures Increased situational awareness for FMPs of the CDM flights in their area of responsibility nm.releases@eurocontrol.int 37

36 2- Background CR_ (Display TOBT / TSAT / Taxi time to ops users ) CDM information from DPI messages: TOBT Target Off Block Time TSAT Target Start-up Approval Time Taxi Time Airlines and IATA requested these fields in the Flight List of the NOP Portal and of the CHMI, in addition to the Flight Data display (since NM18.5) The rationale is to: Centralize all relevant CDM information Facilitate flight management Enhance situational awareness of the AOCCs (Airline Operations Centre) for their flights Implemented on the NOP Portal (Flight List) in NM20.5 CR_ Display TOBT / TSAT / Taxi time to ops users Concerned interfaces Flight List of CHMI (CIFLO + CIAO) nm.releases@eurocontrol.int 38

37 2- New features CR_ (Display TOBT / TSAT / Taxi time to ops users ) CHMI CIAO Interface for airlines nm.releases@eurocontrol.int 39

38 2- New features CR_ (Display TOBT / TSAT / Taxi time to ops users ) CHMI CIFLO Interface for FMPs nm.releases@eurocontrol.int 40

39 3- Impact CR_ (Display TOBT / TSAT / Taxi time to ops users ) CHMI users will be able to consult the TOBT, TSAT or TT directly in the Flight List nm.releases@eurocontrol.int 41

40 2- Background CR_ (Display C-DPI Reason-field to ops users) At the reception of a Cancel-DPI message NMOC suspends the flight Often the AOCC does not understand the suspension reason of their flight CDM information from Cancel-DPI message: REASON field Reason value Possible transmission reasons Possible Actions NO AIRPORT SLOT TOBT UNKNOWN OR EXPIRED TSAT EXPIRED RETURN TO STAND FLIGHT PLAN INVALID FLIGHT CANCEL IN AODB The airport did not have an airport slot for the departure The TOBT was deleted, the pilot did not request start-up or report ready in accordance with the procedures at the Airport, The pilot did not request start-up in accordance with the CDM procedures at the airport After having started taxi, the flight returned back to stand/ramp The discrepancy between TOBT and EOBT is larger than 15min (and needs to be resolved before start-up will be issued) Cancellation of the airport slot or Schedule before the ICAO FPL has been cancelled (CNL). AO to request an airport slot or to CNL the flight plan AO/Handling Agent to update the TOBT, to file a DLA message, AO to CNL the flight plan, AO/Handling Agent to update the TOBT, to file a DLA message, AO to CNL the flight plan, AO/Handling Agent to update the TOBT, to file a DLA message, to CNL the flight plan, AO/Handling Agent to update the TOBT or send a DLA message Cancel ICAO flight plan nm.releases@eurocontrol.int 42

41 2- New features CR_ (Display C-DPI Reason-field to ops users) CR_ Display C-DPI Reason-field to ops users Concerned interfaces NOP Portal & CHMI (Flight Data), B2B (CDMinfo) nm.releases@eurocontrol.int 43

42 3- Impact of the CR CR_ (Display C-DPI Reason-field to ops users) AOCC s will be able to consult the reason for suspension Based on the reason, the AOCC can take the required action Note that not all CDM airports are providing the reason in the C-DPI yet. nm.releases@eurocontrol.int 44

43 4- Questions Any questions? 45

44 Presentation of NM21.0 FB781: Part Free Route Implementation at ACCs CR_ New Airspace type FRA v1.6

45 1- Background Short background of the FB: Why was it developed? Current (NM20.5) FRA Airspace volumes must be composed of a single vertical slice of an AUA or an AUAG. To support the incremental implementation of FRA, particularly in the complex core area of the Network, there is a need by a number of ANSPs to define FRA on the basis of sectors belonging to an AUA and even to include partial sectors. What was the problem it intends to solve? By creating a new Airspace Type FRA we do not encounter anymore discrepancies between FRA s based on CTA, FIR, with or without delegated Airspace services. Simplify defining FRA borders. nm.releases@eurocontrol.int 47

46 New features brought by the FB781: 2- New features New type as RAS airspace with subcategory as FRA and DCT. *RAS: Regulated Airspace (new type) With subcategory: FRA and DCT Eras: Elementary restricted airspace Cras: Composed restricted airspace 48

47 3- Impact of the FB 1. It is possible to define FRA Airspace volumes as a composition of one or more Airblocks, AUAs, Elementary Sectors or Collapsed. 2. It is possible to define separate vertical limits for each constituent airspace in the FRA Airspace volume composition. 3. The system will validate for no overlaps between FRA and DCT definitions in 3D volume and time. 4. The system will validate for no gaps in the FRA border definition. 5. allow coexistence of FRA/DCT Restrictions based on RAS and FRA/DCT Restrictions based on AUA/AUAG * Due to the complexity of this software change and testing still on going, delay may be expected for getting this software into operations nm.releases@eurocontrol.int 49

48 4- Questions Any questions? 50

49 Presentation of NM21.0 FB731: Scenario Management v1.6

50 1- Scenario Management Background NM st STEP TOWARDS IMPROVEMENT OF SCENARIO MANAGEMENT PROCESS Why this FB is being developed? To improve the publication of scenarios To enhance the maintenance and validation of scenarios To efficiently reduce high workload in the creation, simulation and implementation of scenarios To support local & network evaluation tools What is the main business objective? To support internal NM system changes for B2B exchange and n-conect implementation nm.releases@eurocontrol.int 52

51 2- New format of published scenarios in the NOP ADEP/ADES renamed => FROM/TO Content extracted from flow description in ENV «Refile» renamed => «Level constraints» Suggested Alternative Route = Field 15 Addition of Event(s) the scenarios are linked to (e.g. ERATO) New Naming Convention: Existing Scenarios: Current Name (TV ID) + (Type_#_Reference Location) New scenarios: Type_#_Reference Location Standardised On/Off Load sector Box When relevant: RAD information box Standardised Map - All points - Red: initial route - Green: suggested reroutings - Blue: common segments between initial route and rerouting Addition of Scenario Owner FMP nm.releases@eurocontrol.int 53

52 Creation of Scenario Repository Gradual upgrade of the most used scenarios 3- External Impact of FB731 in NM21.0 Scenario Repository NM/FMPs to clean up current collection of scenarios => Temporary procedure for the generation scenarios NM/FMPs to validate/review the initial repository via extended OPT session =>Temporary procedure for the re-validation scenarios Usage of Scenario Repository Automated Publication of scenario in the NOP using information of the Scenario Repository => Limited impact on published scenarios format in the NOP Reference Scenario AIRAC revalidation 54

53 4- Questions Any questions? 55

54 Presentation of NM21.0 FB826: Develop Arrival Planning Information B2B in NMOPS (PJ24) v1.0

55 1- Background Short background of the FB: Why was it developed? This FB has been developed to support SESAR Very Large Scale Demonstrations (VLD) that will take place over the coming three years. To adapt NM traffic demand trajectories with received arrival information, To enhance ATFCM arrival measures with local ANSP/Airport priorities and targets. What was the business need? To include flight arrival planning information in Network Operations Planning What was the problem it intends to solve? Improvements to NM traffic demand picture (STAR etc.) Improved ATFCM arrival regulation slot allocation (better alignment with airport needs). 57

56 2- New features New features brought by the CR/FB compare to today. New B2B services (only accessible to trial airports during explicit trial periods) B2B services communicate airport arrival information to the network During periods of airport capacity constraint, B2B services communicate airport flight target times to the network 58

57 3- Impact of the FB Impact of the FB on externals: Changes only available to SESAR Demonstration participants. The projects will be responsible for announcing the precise dates and content for the operational demonstrations in due course. (PJ24, PJ25 CEF2015) These enhancements will generally manifest as: New Arrival Planning Information messages in the flight CHMI / NOP Portal / B2B OPLOG which is visible for all users accessing this log. For some flights: during the trial exercises: arrival regulations may now become the most penalising regulation to explicitly fulfil airport arrival flow flight prioritisation that is put in place to best serve TMA, airport resources and aircraft turnaround planning optimisations. nm.releases@eurocontrol.int 59

58 4- Questions Any questions? 60

59 Presentation of NM21.0 FB839: Slot Swapping Front End v1.0

60 1- Background Short background of the FB: Slot Swapping has been developed as a SESAR Step 1 solution #56 What was the business need? Slot swapping is a means for the AU to reduce the impact of ATFCM delays. What was the problem it intends to solve? Even if some slot flexibility exists today with ATFCM regulation slot-swapping It is often difficult for AOCs to quickly identify suitable flights to swap with delayed flights that have higher business priorities. Once identified, issuing a slot-swap request relies on tedious manual operations. nm.releases@eurocontrol.int 62

61 2- New features New features brought by the CR/FB compare to today. This function facilitates AUs (Airspace Users) in the identification, assessment and request of eligible flights for ATFCM Slot Swapping. Uses NOP portal to identify candidate flights for ATFCM regulation Slot Swapping; Presents swap assessment information for the subject and object flights; Simple interface to request eligible swaps directly to the NM e-help desk 63

62 How to access and use the new feature: 64

63 65

64 66

65 67

66 68

67 69

68 70

69 71

70 3- Impact of the FB The existing procedures in the ATFCM Users manual (8.4.4.) remain unchanged 72

71 4- Questions Any questions? 73

72 Presentation of NM21.0 FB834: Improved restriction model and ATFM processes through use of enhanced flight plan data v1.7

73 Flight planning able to process CNS capabilities 1- Background FPFDE (Flight Plan and Flight Data Evolution) Programme scope Regulation able to process PBN capabilities for mixed/non mixed environment (*) Traffic load flows extension 75

74 1- Background Current NM restriction model and traffic volume/flow model has limitations The reduced use of plan information (CNS) limits the possibilities of the flight planning and flow management services Example: RNAV checking is performed in IFPS on RNAV5 capabilities when the aim would be to check RNAV1 capabilities EG2726B: EKNIV M87 UMTUM ONLY AVAILABLE FOR TRAFFIC DEP EGLC RNAV1 EQUIPPED Currently there are 93 restrictions with simplified RNAV requirements in CACD 76

75 The new restriction model allows for IFPS checking of flight plan elements in item 10a, 10b and 18 PBN/ (CNS) 2- New features The new flow model (included, excluded, exempted, included-exempted), permits to improve the load monitoring by differentiating: Traffic based on additional flight status (delay threshold) or Traffic containing specific information in item 10a, 10b and 18 PBN/ (CNS) The new flow model permits to create ATFM regulations targeted for specific CNS equipment 77

76 3- Impact of the FB NM cannot convert the current RAD/EU restrictions into the new model without authorisation from the ANSPs therefore RAD/ENV coordinators are expected to: Review the current restrictions for which they are the owner Transmit to NM the restrictions that are still required with the precise requirements based on the new functionality by the end of April 2017 Those restrictions which are not reviewed will be deleted at the AIRAC1706 on 25th May 2017 New requests shall follow existing publication (AIP) procedures and stakeholders consultation process (NETOPS, ODSG, RMG, ENV_COOR) It is recommended for the ANSPs to test the new feature during the OPT (March-April) 78

77 3- Impact of the FB Support to ICAO 2012 information: 79

78 4- Questions Any questions? 80

79 Presentation of NM21.0 CR_039708: Flight plan message filing and distribution in FIXM format via B2B v1.6

80 1- Background CR_039708: Flight Plan Message filing and distribution in FIXM format. B2B flight plan preparation (validation, filing, updating) B2B flight plan distribution via Publish Subscribe available since NM19.5 Available in NM B2B format Goals: Use international standard Increases interoperability among all air traffic stakeholders 82

81 2- New features CR_039708: Flight Plan Message filing and distribution in FIXM format. Available for the following NM B2B web services: Flight Plan Validation Flight Plan Creation Flight Plan Update Flight Plan Retrieval Flight Plan message distribution via Publish / Subscribe All being available either in FIXM4.0 or current B2B format. nm.releases@eurocontrol.int 83

82 3- Questions Any questions? 84

83 Presentation of NM21.0 FB819: NM B2B improvements v1.1

84 1- Background CR_041835: Make flight version number available via B2B. Provide version number of any given flight update via Publish / Subscribe and via Request / Reply. help determine which flight update is the latest support system recovery after failure: means to (re)synchronize with latest NM data CR_041836: Support update of multiple tactical plans at once in B2B. Provide ability to update tactical plans on several Traffic Volumes at once. Capacity plan, Update OTMV plan, TV activation Improve Resource usage Improve the efficiency in processing the tactical updates nm.releases@eurocontrol.int 86

85 2- CR_041836: Support update of multiple tactical plans at once in B2B <fw:capacityplanupdaterequest <plans> <dataid>o </dataid> <dataset> <type>operational</type> </dataset> <day> </day> <tvcapacities> <item> <key>lfe2f</key> <value> <clientschedule> </clientschedule> </item> <item> <key>lfe4e</key> </item> <item> <key>lfe4h</key> </item> </tvcapacities> </plans> </fw:capacityplanupdaterequest>> Schedule for TV 1 Schedule for TV 2 Schedule for TV 3 nm.releases@eurocontrol.int 87

86 3- Impact of the FB By concept, changes in B2B interface require changes on Client Application to be able to benefit from them. Reminder: significant impact on TACTICAL_UPDATES NM 21.0: Development and test to be done on PRE-OPS before deployment on OPS Deployment on OPS according to the B2B Operational Deployment Process Documentation: B2B Flow Service Group Reference Manual 88

87 4- Questions Any questions? 89

88 Presentation of NM21.0 FB814: IFPS Workload Evolutions v1.0

89 1 and 2 - Background and new feature Allow the use of POSRTE for DLA messages It is possible for a DLA message to be invalid in IFPS and the required action is for the AO to file a new route. For IFPS to be able to give routing assistance, IFPS will be able to send a possible route (POSRTE) in the reject message. -TITLE REJ -MSGTYP IDLA -FILTIM ORIGINDT BEGIN ADDR -FAC EVRAZPZX -END ADDR -POSRTE N0422F360 VALED DCT ADAXA M864 KOLJA M611 DEGUL UN872 PAM UL980 REFSO UY76 ODROB Y76 ERING -ERROR PROF199: GOBOT UZ701 EEL IS A CLOSED CDR 2 IN FL RANGE F245..F660 -OLDMSG (DLA-WIN23EW-EVRA0545-EGKK-DOF/170307) nm.releases@eurocontrol.int 91

90 3- Impact of the FB If a DLA message is rejected by IFPS for a route/profile error, the filer of the DLA message may now see the POSRTE field in the REJ message. This may have an impact on the procedures in place. nm.releases@eurocontrol.int 92

91 4- Questions Any questions? 93

92 Presentation of NM21.0 FB820: Flight Planning Domain improvements v1.0

93 2- New features CR_041417: Add IFP indicator after IFPSRA (IFPS Re-route Accepted) Objective of this change is to make sure that any route change without coordination by IFPS is clearly identified in the distributed flight plan. A new IFP indicator IFPSROUTEMOD will be made available. The IFP/IFPSROUTEMOD indicator will be inserted into the Item 18 of the flight plan when IFPS automatically changes the route after processing the IFPSRA indicator from the filed flight plan, or makes an automatic route change, or can be manually inserted by the IFPS Operator. (FPL-WIN72E-IG -F2TH/M-SBDE2E3FGHIJ1J3J4J5M1RWXYZ/LB1D1 -EDDB2100 -N0451F430 BKD7X BKD UL619 AMLUH UM852 ALASA DCT LO -EKBI0050 EKAH -PBN/A1B1C1D1L1O1S2 NAV/SBAS COM/CPDLC DOF/ REG/GBWIN EET/EDVV0020 EKDK0036 SEL/AASW CODE/WE56R RVR/300 IFP/IFPSROUTEMOD OPR/WIN ORGN/EGNHWINO PER/C RMK/TCAS EQUIPPED) Impact: The new IFP indicator may have an impact on systems that receive flight plan messages from IFPS. The new IFP indicator may mean changes to procedures for the airspace users or ANSPs. nm.releases@eurocontrol.int 95

94 2- New feature CR_ Allow ARCADDR in AFP message IFPS will allow the -ARCADDR field in ADEXP format AFP messages, and the CODE field in ICAO format AFP messages. The ARCADDR/CODE field received in an AFP message shall be used to update the field 18 content of the associated flight plan. These fields will be used in combination of the other field 18 content of the associated flight plan to build a complete field 18 within the ACH message. CODE/ARCADDR field is already present in IFPS output. CR has no impact unless ATC adapt their systems to start sending the CODE/ARCADDR. nm.releases@eurocontrol.int 96

95 2- New features CR_041322: Prevent VFR levels Following the Standardised European Rules of the Air (SERA) Regulation (IR 923/2012, binding since ), flying VFR is (in principle) not allowed above FL195. Despite appropriate information held in the relevant AIPs, flights that traversed controlled airspace above FL195 VFR have repeatedly caused significant problems to the ATCOs involved. The corresponding flight plans had successfully passed IFPS validation. An error will be raised when a FPL has an RFL above F195 within the VFR portion. nm.releases@eurocontrol.int 97

96 2- New features CR_041322: Prevent VFR levels Starting VFR with a change to IFR with an RFL above F195 - is OK (FPL-KWOOP-ZG -GLF5/M-SDGY/S -EGGD0900 -N0330F130 DCT CITY DCT POL/N0310F230 IFR N601 GRICE P600 GLESK -EGPD0300 LFMC -0) The level F230 at POL is accepted. nm.releases@eurocontrol.int 98

97 2- New features CR_041322: Prevent VFR levels IFR with an RFL above F195 commencing a decent to a VFR level - is not OK. (FPL-HWOOP-YG -GLF5/M-SDGY/S -EGGD0900 -N0330F230 BCN N864 NITON P17 POL/N0310F190 VFR N601 GRICE P600 GLESK -EGPD0300 LFMC -0) The initial level F230 is not accepted. nm.releases@eurocontrol.int 99

98 2- New features CR_041322: Prevent VFR levels IFR with an RFL below F195 commencing a climb to a level above F195 under VFR - is not OK. (FPL-JWOOP-YG -GLF5/M-SDGY/S -EGGD0900 -N0330F130 BCN N864 NITON P17 POL/N0310F220 VFR N601 GRICE P600 GLESK -EGPD0300 LFMC -0) The level F220 at POL is not accepted. nm.releases@eurocontrol.int 100

99 2- New features CR_041322: Prevent VFR levels An error will be raised when a flight plan message has an RFL above F195 that does not end in 0 (e.g. 255) within the IFR/GAT portion. Example: (FPL-IFR012-IS -GLF5/M-SDGY/S -EGGD0900 -N0330F185 BCN N864 NITON P17 POL/N0330F235 N601 GRICE P600 GLESK -EGPD0300 LFMC -0) (FPL-VFR012-ZG -GLF5/M-SDGY/S -EGGD0900 -N0330F185 DCT POL/N0330F235 IFR POL N601 GRICE P600 GLESK -EGPD0300 LFMC -0) The level F185 is accepted The level F235 is not accepted. nm.releases@eurocontrol.int 101

100 3- Impact CR_041322: Prevent VFR levels The new rules for processing the VFR part of the route in IFPS may have an impact on organizations that file flight plan messages to IFPS. 102

101 4- Questions Any questions? 103

102 Presentation of NM21.0 FB821: Airspace Data Domain improvements Multiple Dependent Applicability v1.7

103 1- Background Short background of the FB: Why was it developed? To reference more than one Area or Route when dependent Applicability is required for a RAD restrictions. What was the problem it intends to solve? Limitation of the CACD system and to avoid workarounds like creating more than one RAD restriction to full fill the requirements of our stakeholders. To simplify the RAD restriction for Airspace Users nm.releases@eurocontrol.int 105

104 2- New features New features brought by the CR/FB compare to today. 106

105 3- Impact of the FB Impact of the FB on externals: 1. It is possible to define RAD Restrictions with Dependent Applicability referencing more than one RSA. 2. It is possible to define RAD Restrictions with Dependent Applicability referencing more than one CDR. 3. It is possible to define RAD Restrictions with Dependent Applicability referencing a combination of RSA and CDR. 4. Multiple references can be combined with logical operators AND, OR and NOT. * Due to the complexity of this software change and testing still on going, delay may be expected for getting this software into operations nm.releases@eurocontrol.int 107

106 4- Questions Any questions? 108

107 Presentation of NM21.0 FB822: ATFCM Domain improvements v1.0

108 FB822: ATFCM Domain improvements 1. CR_ Parameter to control additional suspensions 2. CR_ Improve True Revision Process nm.releases@eurocontrol.int 110

109 1.1- Background CR_ Parameter to control additional suspensions The Delay Threshold Mechanism is used in Scenarios Satisfactory Procedure Satisfactory threshold value (20 ) nm.releases@eurocontrol.int 111

110 1.1- Background CR_ Parameter to control additional suspensions The Delay Threshold Mechanism is NOT used for unavailability & High Delay & RVR Use Cases Differentiation Shall be based on FCM application Benefits based on delay stability Delay Threshold Value Insufficient for global application (2h) Minimum Value for CNL (3h) Additional suspension parameter Identified need Number of suspensions Delay (t) nm.releases@eurocontrol.int 112

111 1.2- New features CR_ Parameter to control additional suspensions Additional suspension parameter The objective is to avoid re-suspension of flights that already confirmed. This situation can happen when a regulation is modified resulting in a small increase of delays Characterization of traffic based on flight status (FB834) nm.releases@eurocontrol.int 113

112 1.3- Impact of the FB CR_ Parameter to control additional suspensions Less likelihood of receiving further FLS messages for confirmed (FCM) flights that had been suspended before by the same regulation For the generation of a new FLS, the delay has to be 50% greater than the previously accepted delay Example: 1 st suspension = 3h 2 nd suspension= 4,5 h nm.releases@eurocontrol.int 114

113 2.1 and 2.2- Background and new features CR_ Improve True Revision Process The ETFMS applies a True Revision Process to try to improve the CTOT of flights that have been issued a slot This currently happens every 5 minutes With the NM software release 21.0, the process will be performed every minute nm.releases@eurocontrol.int 115

114 2.3- Impact of the FB CR_ Improve True Revision Process The change will allow the ETFMS an earlier usage of released slots It could potentially mean more slot improvements sent to AOs with a resulting delay reduction Less need to contact the FM Helpdesk nm.releases@eurocontrol.int 116

115 4- Questions Any questions? 117

116 Presentation of NM21.0 NM21.0: Way forward

117 Way forward to NM21.0 migration NM21.0 OPT session will start on the 20/03/2017: All what you need is to have already access to NM systems. No registration (unless you want to exchange FPL message with OPT platform). You can download and test the new NM21.0 CHMI You can test the new NM21.0 NOP Portal You can test some new FBs Questions: OPT instructions: Next week: Slides and recording of the Presentation available (mailing to participants, Release Notes, forums (ODSG, etc.), B2B users). 119

118 Way forward to NM21.0 migration NM21.0 migration is planned to start on the 02/05/2017 (last around 1 week) Detailed Release migration plan may be found in the NM Release Notes ( 4.1.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: nm.releases@eurocontrol.int nm.releases@eurocontrol.int 120

119 Any questions? 121

120 Many thanks for your participation! 122