The presentation to Externals of the NM22.0 Release via video-conference took place on the 15 th of March 2018.

Transcription

1 The presentation to Externals of the NM22.0 Release via video-conference took place on the 15 th of March 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) Any questions:

2 Presentation of NM22.0 to Externals EUROCONTROL Network Manager Directorate 15/03/2018 v2.1 Classification TLP : White (Public)

3 Welcome to the Presentation of NM22.0 to Externals Agenda 1- Introduction and interface set-up 2- NM22.0 Release presentation: 2.1- Important notifications related to NM22.0 migration OPT (operational testing) session 2.2- FBs (Functional Blocks) presentation 3- Way forward toward NM22.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 NM22.0. Operational Project Managers will present their Functional Block. Enable you to assess the impacts on your procedures or systems. Ask questions (today after each FB presentation, or by 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 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- NM22.0 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) nm.releases@eurocontrol.int 10

11 2.1- NM22.0: The OPT (Operational Testing) (Release Notes 4.1.2) NM22.0 is available for testing with the OPT (operational testing) session! NM22.0 OPT session started on the 9 th of March and will end on the 26 th of April. With the NM22.0 OPT you are able to: Test NM22.0 on your systems with your procedures. Download and test the new NM22.0 CHMI. Test the new NM22.0 NOP Portal. Test some new FBs (operational scenario provided in the OPT guide). B2B: NM 22.0 will be available on PREOPS (as from 27/03/ :00 UTC) 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 11

12 2.1- NM22.0: Important notifications For NM B2B users only: TLS migration (TLS: Transport Layer Security) - communicated via the NM B2B OneSkyTeam website - NM B2B Service are engaging in an increase of Security: NM B2B will very soon stop accepting any request that is not using TLS 1.2. TLS 1.2 is recommended by all National Cybersecurity offices. If no action taken NM Cybersecurity rating would drop. As from 2 May 2018 (NM22.0 migration): PREOPS will accept only TLS 1.2 All NM B2B versions are impacted on PREOPS As from 16 October 2018 (NM22.5 migration): OPS will accept only TLS 1.2 All NM B2B versions are impacted on OPS Operational access will be cut to software not implementing TLS 1.2 nm.releases@eurocontrol.int 12

13 2.1- NM22.0: Important notifications (Release Notes 2.1) NM22.0 migration will start on Wednesday the 2 nd of May 2018 (Migrations of previous Releases used to start on a Tuesday) Browsers recommended in NM22.0: 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.0 webservice. Output of IFP/IFPSROUTEMOD indicator in Flight Plans. nm.releases@eurocontrol.int 13

14 Any questions? 14

15 2.2- NM22.0 FBs and CRs presentation Only new features impacting operations and Externals are presented Important notification CR_ Output of IFP/IFPSROUTEMOD in FPLs Airspace Management and Advanced FUA FB723 Rolling AUP Airport and TMA Network Integration FB894 CTM (Cooperative Traffic Management) AOP/NOP Integration Extended DPI - Phase I FB890 API Developments FB916 Scenario Repository Publication via B2B FB918 Network Impact Assessments Analysis EAIMS (European ATM Information Management Service) FB893 NM airspace model evolution FPFDE (Flight Plan and Flight Data Evolution) FB833 PTR Counts - SKIPIN/SKIPOUT to TVs Operations Improvements FB846 FB906 FB907 FB967 FB924 Airborne message reception (APR, FNM/MFS) Flight Planning Domain improvements Airspace Data Domain improvements e-helpdesk improvement Rerouting Evolutions nm.releases@eurocontrol.int 15

16 Presentation of NM22.0 CR_043146: Output of IFP/IFPSROUTEMOD in FPLs v1.0

17 CR_043146: Output of IFP/IFPSROUTEMOD in FPLs With the NM21.5 release, the output of the IFP/IFPSROUTEMOD was included when IFPS automatically changes the Field 15 string. The implementation caused difficulties for some ANSPs because of the high number of FPLs that contained the indicator. To solve the issue for the ANSPs, the auto insertion was disabled. With NM22.0, the auto insertion will again be enabled. But this change (CR_043146) will reduce (compare to NM21.5) the occurrences of when the IFP/IFPSROUTEMOD is included. IFP/IFPSROUTEMOD indicator will be included in the FPL: When IFPS automatically changed the Field 15 string (like in NM21.5), EXCEPT IF only the 'DCT' or SID/STAR is removed as the first/last element of the route (new in NM22.0). Example: -PBN/A1B1D1L1S2 DOF/ REG/WOOPS EET/EGTT0021 EISN0104 RVR/075 IFP/IFPSROUTEMOD OPR/WOO ORGN/EIDWWOOU PER/C RMK/TCAS) 17

18 Impact of the CR The increase in the use of the IFP/IFPSROUTEMOD indicator may have an impact on systems that receive flight plan messages from IFPS. 18

19 4- Questions Any questions? 19

20 Presentation of NM22.0 FB723: Rolling AUP v2.0

21 1- Background - Global approach Statistics on Historic. BT Merge Historical data and SBT (and adjust Uncertainty Model) Enhanced Predicted Workload FBT (Forecast 4DTraj + Uncertainty Business Model Trajectory) 4D traj + Uncertainty RBT DCB = Imbalance Detection and Management = DCB (Need Predicted Workload) Airspace Configuration (Need predicted Workload) Airspace Requirements Major events AUP UUPs Demand Adjustment TOBT Time -18m -6m -4m -1w -3d -1d d0-4h Real Time 21

22 1- Background Problem statement: no notification process through the AUP allowing States to notify any information available in advance. Goals: Exchange draft information of airspace status during the pre-tactical phase before D-1. Allow AOs and CFSPs to be advised of CDRs and areas information in advance. Allow early coordination among AMCs, as well as between AMCs and NM for improving planning. 22

23 2- New features The NOP Portal will automatically collect all available DRAFT EAUP data from D-2 back to D-6. Possible use case: visualisation of predefined AUP for public holidays or large scale exercises. 23

24 2- New features All airspace structure information currently or planned to be processed via AUP/UUP are elements eligible for early publication. Implicit NAM allocations are calculated for all and only the DRAFT/READY AUPs provided before D-1. The publication of the official Released EAUP/EUUP starting at D-1 stays a service controlled by NM CADF operator. The official EAUP (D-1) can only be released when all AMCs have provided an AUP in status READY as it is today. nm.releases@eurocontrol.int 24

25 3- Process No mandatory for AMCs Start at D-6 until D-2. AMCs submit DRAFT or READY AUP (no deadline for publication). NM publishes DRAFT EAUP on the NOP Portal. No systematic network impact assessment, but ad hoc coordination when required. AMCs submit final AUPs at D-1 according to current procedures. Adaptation for extended process. 25

26 4- Impact of the FB No changes in current procedures: The publication of the early Draft/Ready AUP before D-1 is not compulsory for AMCs. Possibility to trigger coordination (e.g. ASM scenarios involved). No changes in local systems: Already possible to issue AUPs before D-1. Content and presentation of the DRAFT EAUP do not change. The publication of the official Released EAUP/EUUP starting at D-1 stays a service controlled by NM CADF operator. AUs possibility to retrieve data from NOP Portal: Up to them to consider their utilisation for FPL purposes. nm.releases@eurocontrol.int 26

27 5- Questions Any questions? 27

28 Presentation of NM22.0 FB894: AOP/NOP Integration Extended DPI Phase I v2.1

29 1- Background The A-CDM processes have matured and the next step is to further improve operational performance FB894 introduces an initial NM B2B enhancement to support Airport and Network Operations Plan (AOP-NOP) integration Extended Departure Planning Information (Extended DPI) Extending the time frame for airport data exchange (NM B2B only) Extending the data elements exchanged (NM B2B & AFTN) Such concept enhancements require careful introduction Pilot airports will participate in operational demonstrations in 2018 and 2019 There will be some minor impact to flight data visible to all users Full deployment is anticipated in late

30 1- Background NM22.0 ETFMS FPL (max = EOBT-20 hrs) FPL (max = EOBT 3hrs) P-DPI E-DPI, T-DPI-t, T-DPI-s B2B AFTN B2B AOP A-CDM nm.releases@eurocontrol.int 30

31 2- New features Extend the time frame for airport data exchange Predicted DPI (P-DPI) Contains extended DPI information First P-DPI trigger event is a Flight Plan entering into ETFMS (after EOBT-20hrs) P-DPI exchange continues until first E-DPI event New CDMStatus p / PREDICTED, indicates a P-DPI was received New NM B2B service called submitpredicteddpi 2018/2019 P-DPI will only be used by participating airports during published demonstrations nm.releases@eurocontrol.int 31

32 2- New features Extend the data elements exchanged Three types of Target Take Off Time will extend today s single TTOT: Turnaround TTOT Earliest TTOT Consolidated TTOT From the AO or Handler From the airport The new NM B2B P-DPI may contain all three Airport reaction to network constraint The E-DPI, T-DPI-t and T-DPI-s may also optionally provide these (AFTN or NM B2B) Existing A-CDM airports are NOT required to provide these and the TTOT will continue to be supported in these messages NM will communicate TTOT from Early and Target messages as Turnaround TTOT NM will communicate TTOT from Pre-Sequence messages as Earliest TTOT nm.releases@eurocontrol.int

33 Turnaround TTOT 2- New features Turnaround TTOT is the planning time of the Aircraft Operator or Handler Update triggered by e.g. Off Block Time updates NM uses the Turnaround TTOT to update the traffic demand (FTFM) FTFM = Filed Tactical Flight Model

34 Earliest TTOT 2- New features Earliest TTOT is the earliest time the constrained airport can launch the flight Update triggered by an airport when a departure capacity constraint exists e.g. reduction of runway availability NM uses the Earliest TTOT to create/update: 1) For an ATFM non-regulated flight Flight s traffic load (CTFM), but without Tac activating the flight 2) For an ATFM regulated flight Constraint for slot assignment or for slot improvement, i.e. equivalent of NoSlotBefore time nm.releases@eurocontrol.int CTFM = Current Tactical Flight Model

35 Consolidated TTOT 2- New features Consolidated TTOT is the airport take off time for a network constrained flight used to sequence the flight inside STW NM uses the Consolidated TTOT to create/update the flight s traffic load (CTFM) The Consolidated TTOT only visible during demonstration periods nm.releases@eurocontrol.int CTFM = Current Tactical Flight Model

36 2- New features CHMI / NOP Portal changes Changes to Flight Data on the CHMI / Flight Details on the NOP Portal: Turnaround TTOT / Earliest TTOT/ Consolidated TTOT values displayed New Airport CDM Status Predicted displayed after a P-DPI is processed The No Slot Before removed and replaced by Earliest TTOT No changes to the Flight List The Flight Oplogs will contain the new data nm.releases@eurocontrol.int 36

37 2- New features CHMI Flight Data NM22.0 Interface normal OPS 37

38 2- New features CHMI Flight Data NM22.0 Interface trials in OPS Consolidated TTOT 14:28 38

39 3- Impact of the FB SESAR PJ24 will perform operational demonstrations of Extended DPI upon three Spanish and Heathrow airports as follows: Q3 and Q Madrid, Barcelona and Palma de Mallorca Q Heathrow Airport NM will announce specific dates and timings Pilot deployment under the CEF 2015 call concerns Heathrow airport, Frankfurt airport and Aéroports de Paris (ADP) Heathrow airport planned first Frankfurt and ADP will follow at a later stage nm.releases@eurocontrol.int 39

40 3- Impact of the FB Impact for current CDM airports A-CDM airports not participating to the Extended DPI operational demonstrations or to the pilot deployment are not affected The existing DPI provision does not have to be changed The single TTOT field from A-CDM concept will continue to be supported Impact for FMPs The CTFM may exist prior to the E-DPI Impact for all stakeholders Extended TTOT fields disseminated via CHMI / NOP Portal and output via B2B CdmInfo nm.releases@eurocontrol.int 40

41 4- Questions Any questions? 41

42 Presentation of NM22.0 FB890: API Developments v2.0

43 1- Background FB890 provides timely exchange of airport ARRIVAL information using NM B2B exchanges. It enhances airport and network operations planning (AOP-NOP) and contributes towards the AOP-NOP collaborative rolling process. For 2018 and 2019 this integration is only offered to SESAR PJ24 and PJ25 consortium members and only during defined operational exercise periods. Arrival Planning Information (API B2B services) via: General Arrival Planning Information Acting on pre-departure ECAC (arrival) flights (Target Take Off API) Acting on airborne (arrival) flights (Target Time Over API) For 2018 and 2019 API capability is only offered to SESAR PJ24 and PJ25 consortium members and only during defined operational exercise periods 43

44 Used to inform the NOP: of estimated and actual Landing Time of a cancelled flight departing out of the ECAC area of STAR updates of a flight diverted to/from the airport of arrival: runway, terminal, apron updates of arrival terminal updates of inbound taxi time updates of minimum turnaround time updates of aircraft type, registration mark updates of of IBK, DBR and DBC status and to indicate Termination of the Flight of Impact Severity Indicator (of late inbound flight) 2- General API OBT TOT IDH LDT TOT TXO DIV GOA RTN RET Inbound SCH INI AIR FIR TMA FNL TXI IBK DBR DBC ATV STATUS Outbound CNX SCH INI BRD BRC RDY OBK DEP CNX APPLICABILITY OF SERVICE General API General API for cancellation For 2018 and 2019 API capability is only offered to SESAR PJ24 and PJ25 consortium members and only during defined operational exercise periods 44

45 2- Target Take Off API (ECAC pre-departure flight) In arrival capacity ATFM constrained situations the Target Take-off API service allows the airport/fmp to submit Target Time of arrival requests to the NOP. If the request is granted a new CTOT will be issued. Note that the createregulation service (B2B FLOW) may be used (by the FMP) to initiate the Regulation before Target Time of arrival requests can be sent. OBT TOT IDH LDT TOT TXO DIV GOA RTN RET Inbound ATV STATUS SCH INI AIR FIR TMA FNL TXI IBK DBR CNX SCH DBC Outbound INI BRD BRC RDY OBK DEP CNX APPLICABILITY OF SERVICE Target Take-off API For 2018 and 2019 API capability is only offered to SESAR PJ24 and PJ25 consortium members and only during defined operational exercise periods 45

46 2- Target Time Over API Airport local stakeholders inform the NOP about Target Times that they have given to flights that are exempted from being subject to a CTOT issued by NM (these flights are either airborne or non-ecac pre-departures). OBT TOT IDH LDT TOT TXO DIV GOA RTN RET Inbound ATV STATUS SCH INI AIR FIR TMA FNL TXI IBK DBR CNX SCH DBC Outbound INI BRD BRC RDY OBK DEP CNX APPLICABILITY OF SERVICE Target Time Over API for airborne flights For 2018 and 2019 API capability is only offered to SESAR PJ24 and PJ25 consortium members and only during defined operational exercise periods 46

47 3- Impact of the FB For 2018 and 2019 this B2B integration is only offered to SESAR PJ24 and PJ25 consortium members and only during defined operational exercise periods Specific dates will be notified later. Spanish airports: Barcelona, Madrid and Palma de Mallorca Q3-Q Heathrow airport Q Zurich airport Q Paris ACC affecting Paris CDG (2018 Q2/3 and Paris Orly 2018 Q3) arrival flows. Impacts for non-consortium members: Flight OP/ Event logs will update with API information received by the network. - Flights regulated by arrival regulations will be prioritised based upon ETA and airport stakeholder priorities to mitigate flight delay knock-on or to consider passenger connections etc. This will be seen as an update to a flight s Min-CTOT parameter. - Earlier arrival traffic demand stability and accuracy After 2019, pilot deployment planned to be undertaken at Heathrow, Frankfurt and (ADP) Paris airports. There is no backward compatibility between NM21.5 API and NM22.0 API services. For 2018 and 2019 API capability is only offered to SESAR PJ24 and PJ25 consortium members and only during defined operational exercise periods 47

48 3- Impact of the FB - example API OP Log 16-05:51 BAW41Y Incoming Message - Api LFLLDPIO Message : Received from: LFLLDPIO. Est. Xmit at: 17/12/16 05:51:49. Message description:-title API-ARCID BAW41Y -ADEP EGLL-ADES LFLL-EOBD EOBT 0725-APISTATUS TAKEOFF -ATVSTATUSINBOUND INI-MTTT 0025-TTOF -PTID ODEBU-TTODT REGUL FMOU16 For 2018 and 2019 API capability is only offered to SESAR PJ24 and PJ25 consortium members and only during defined operational exercise periods 48

49 4- Questions Any questions? 49

50 Presentation of NM22.0 FB916: Scenario Publication via B2B v1.0

51 1- Background Why this FB is being developed? To support Scenario Publication with more efficient and more correct data after previous improvements in NM 21.0: FB731 : Backend scenario repository NM 21.5: FB805: query, simulate and apply via B2B What is the main business objective? Provide common shared and maintained view of scenarios through the publication and re-validation process Support FMPs with pre-defined tactical solutions Support collaborative and transparent coordination for scenario creation and usage What was the problem it intends to solve? Improve data content and effect of Reference Scenarios Improve current query available in the NOP for impacting scenarios nm.releases@eurocontrol.int 51

52 2- New features NEW IMPROVEMENTS interesting for externals CR_ Scenario Publication improvements CR_ Scenario Attributes revalidation CR_ Scenario GRRT improvements (as part of FB924) CR_ Query by AO for impacting scenario Enable RAD DESCRIPTION Improved generation of on/off load airspaces New check to validate Reference Scenarios whenever there is a change in ENV Generation of more suggested alternative routes for different city pairs New field in B2B and NOP Portal flight list that indicates impacted by zero rate regulation (i.e. scenario) OBJECTIVE of external interest Obtain FMP desired effect when implementing a Reference Scenario Provide a better insight of the impact of a scenario to the rest of the Network To avoid storing obsolete scenarios or scenarios with the wrong capture of flights. Enlarge suggested alternative routes options for AOs whenever a Reference Scenario is applied Provides easier access to information about scenario which is impacting the flight nm.releases@eurocontrol.int 52

53 2- New features CR_ : Query by AO for impacting scenario Use Case New field in NOP Portal flight list that indicates impacted by zero rate regulation (i.e. scenario) Added value of the change Provides easier access to information about scenario which is impacting the flight Both textual and graphical explanations are available to AOs Two potential cases: AO decides to re-route before EOBT-2hrs AO decides to re-route after EOBT-2hrs (FLS received) nm.releases@eurocontrol.int 53

54 2- New features CR_ : Query by AO for impacting scenario Current procedure in NOP Find flight on the flight list Identify scenario which is impacting Flight impacted by level cap measure nm.releases@eurocontrol.int 54

55 2- New features CR_ : Query by AO for impacting scenario Current procedure in NOP Go back to home page of the NOP Select Scenario list Select scenario list nm.releases@eurocontrol.int 55

56 2- New features CR_ : Query by AO for impacting scenario Current procedure in NOP Manually find scenario which is identified on the flight list nm.releases@eurocontrol.int 56

57 2- New features CR_ : Query by AO for impacting scenario Current procedure in NOP When clicking on scenario, the description will appear: Textual description of scenario Graphical depiction of scenario nm.releases@eurocontrol.int 57

58 2- New features CR_ : Query by AO for impacting scenario Case 1: AO decides to re-route before EOBT-2hrs Access the flight list on the NOP New button Provisional delay assigned to AO if re-routing is not performed Delay is above 20min nm.releases@eurocontrol.int 58

59 2- New features CR_ : Query by AO for impacting scenario Case 1: AO decides to re-route before EOBT-2hrs Access the flight list on the NOP nm.releases@eurocontrol.int 59

60 2- New features CR_ : Query by AO for impacting scenario Case 1: AO decides to re-route before EOBT-2hrs Access the flight list on the NOP Textual description of scenario Graphical depiction of scenario nm.releases@eurocontrol.int 60

61 2- New features CR_ : Query by AO for impacting scenario Case 2: AO decides to re-route after EOBT-2hrs Access the flight list on the NOP New button nm.releases@eurocontrol.int 61

62 2- New features CR_ : Query by AO for impacting scenario Case 2: AO decides to re-route after EOBT-2hrs Scenario impacting selected flight is automatically pre-selected Scenario ID is automatically filled Selected scenario appears here nm.releases@eurocontrol.int 62

63 2- New features CR_ : Query by AO for impacting scenario Select desired scenario from the list Textual description of scenario Graphical depiction of scenario nm.releases@eurocontrol.int 63

64 3- Impact of the FB No direct operational impact for externals Only applicable procedure if used 64

65 4- Questions Any questions? 65

66 Presentation of NM22.0 FB918: Network Impact Assessment Analysis v1.0

67 1- Background Short background of the FB918: To improve the situational awareness of the users the access to the outcome of an efficient and improved Network Impact Assessment is needed. This Functional Block also aims to increase the Network Performance by allowing the local/external users to tune proposed measures they want to apply, in cooperation with NMOC, to be able to confirm the expected effect and reduce better the Network Impact. Further FB918 makes it possible to enhance a cooperative and transparent coordination, with a clear role for NM as the Network Manager nm.releases@eurocontrol.int 67

68 2- New features CR_ Make oplog available in simulations The results of a simulation and which are related to the Network Impact Assessments are stored in the Flight Operational log and in the Measure Operational log. These results are available to external users via B2B/B2C. This CR aims to improve and enhance the presentation in CHMI and NOP Portal with the results stemming from the use of rerouting in simulations and their presentation in the Network Impact Assessment logs via B2B/B2C nm.releases@eurocontrol.int 68

69 2- New features CR_ Make the Network Impact Assessment available via B2B The ETFMS create/update measure service will return a basic Network Impact Assessment (NIA) In B2B additional information will be made available on: fuel consumption and route charges: visible in the flight lists delta counts for impacted TVs delta ATFCM situation display (overall Network delay and active regulations) nm.releases@eurocontrol.int 69

70

71 3- Impact of the FB Impact on external (only B2B) users: Impact on coordination and procedures between FMP and NMOC, Impact on FMP assessment possibilities for making the best and efficient choices at measure level Impact on the local HMI to be able to visualize the B2B retrieved data 71

72 4- Questions Any questions? 72

73 Presentation of NM22.0 FB893: NM Airspace Model Evolution v2.0

74 Background FB893 constitutes the second wave of CACD data model adaptations to allow seamless Annex 15 data download from the EAD Several changes related to the Aerodrome domain have been already rolled out in scope of NM21.5 (FB862) The intention is to gradually roll out changes to this and other domains in the subsequent NM releases Objectives Internal NM model alignment to AIXM 5.1 Improve data quality by reducing manual manipulations to the published data Part of the NM Strategic Objective No. 2 implementation Summary Only one CR impacts externals that use NM B2B services (explained below) nm.releases@eurocontrol.int 74

75 Aerodrome domain adaptations [1] CR_040713: Aerodrome Field Elevation Some Aerodromes may have negative field elevation (e.g. Amsterdam -12ft) For some small world-wide Aerodromes field elevation may be unavailable CR changes business rules in CACD to allow negative and blank Aerodrome field elevation No impact on clients systems: negative and blank field elevation values will be converted to 0 CR_040563: Business rules adaptation for world-wide AD data Runway of type Heli is redundant and removed (AD type had been introduced as a separate property in NM21.5; allowed values are: AD, AH, HP, LS, OTHER) Allow blank taxi times for ADs outside of NM area to avoid keeping fictitious values, when taxi times are unknown Allow ADs outside of NM area to have associated SIDs and STARs Allow ADs outside of NM area to have associated Runway directions No impact on clients systems Default taxi time values will still be sent to clients systems nm.releases@eurocontrol.int 75

76 Aerodrome domain adaptations [2] CR_034863: Aerodrome Flight Rules Today AD flight rules (IFR/VFR) are defined as Flow Restriction both in CACD and NM operational systems Unlike in CACD, in AIXM model AD flight rules are an attribute of the AD object Allowed values are IFR, VFR, BOTH or OTHER Each value has an associated time schedule Starting from NM22.0, AD flight rules are no longer provided as a Flow Restriction, but as an attribute of the AD object with its associated schedule, as defined by AIXM 5.1 model This change impacts clients of the NM B2B services See NM22.0 Release Notes NM22.0 OPT Instructions NM B2B Manuals nm.releases@eurocontrol.int 76

77 Aerodrome domain adaptations [3] Following changes add missing AD properties as prescribed by AIXM 5.1 To facilitate AD data download from the EAD CR_041044: Adds property to water Aerodromes CR_041045: Adds property for abandoned or 24/7 closed ADs CR_041046: Adds uncontrolled property to Aerodromes CR_041047: Adds property private to ADs CR_041048: Adds property to allow distinguishing between international and domestic ADs (INTL or DOM) No impact on B2B clients CIREN users will see them 77

78 Questions Any questions? 78

79 Presentation of NM22.0 FB833: SKIP-IN/SKIP-OUT to TVs v1.0

80 Background Skip-in/skip-out intended to replicate the operational skip functionality Clear link with controller workload/traffic counts and not the airspace penetration Stakeholders reports/questioning: flight s airspace profiles contain holes and overlaps Todays evolved flow management techniques require revisiting old established requirements Need to evolve the NM tactical flow management system Allow addressing individual needs while providing a system for all stakeholders nm.releases@eurocontrol.int 80

81 Weaknesses of current model EFD airspace profile holes & overlaps EFD airspace profile made of Elementary Sectors (ES) A flight is always in an ES, and never in 2 ESs at the same time But due to skip-in/skip-out, EFD airspace profile contains holes and overlaps Applications handling EFD cannot fully re-create the Collapsed Sector (CS) profile Local tools give different counts compared to the CHMI on the CS, due to skip-in/skip-out Lack of flexibility you may want different skip-in/skip-out values per traffic volume For example: same airspace, but 2 TVs: One for the climbing traffic One for the cruising traffic nm.releases@eurocontrol.int 81

82 New concept/features Move elements directly linked to flow management (and controller workload) onto TV Further TV evolutions are foreseen (e.g. tuning flows entry/exit times, tuning duration per flow, etc.) Skip-in/Skip-out applied to TVs and not Airspaces Airspaces becomes physical elements TVs is the concept used for flow management Define skip-in/skip out values per TV If not provided, TV inherits the skip-in/skip-out values from its airspace refloc - airspace skip-in/skip-out value *only* used as default value for TV nm.releases@eurocontrol.int 82

83 CHMI 83

84 Impact of the FB Airspace lists not influenced anymore by airspaces skip-in/skip-out EFD flight airspace profile will show full list of ESs holes & overlap removed including portions VFR, OAT, STAY EFD client applications can properly derive the collapsed sector profiles Impact on the content returned to end users in response to the following queries (performed using the CHMI, NOP Portal or via B2B) returned without skip-in/skip-out or VFR\OAT\STAY portions: Flight lists on Airspace Counts performed on Airspace - will include all flights crossing that airspace) Airspace profile of individual flight from any flight lists - will include all ESs traversed by the flight Only the counts and flight lists performed on Traffic Volumes will be computed (returned by ETFMS) considering the skip-in/ skip-out parameters. nm.releases@eurocontrol.int 84

85 Example AC1 30sec AV1=ES_B TV1, ref_loc ES_B SKIP-IN=1min AC2 AC3 ES_C Flight list on AV1: - AC1 - AC2 - AC3 Flight list on TV1: - AC2 - AC3 ES_A ES_B Counts on AV1: 3 Flts (AC1+AC2+AC3) Counts on TV1: 2Flts (AC2+AC3) AC1 Airspace profile (NM21.5): - ES_A - ES_C AC1 Airspace profile (NM22): - ES_A - ES_B - ES_C nm.releases@eurocontrol.int 85

86 Any questions? 86

87 Presentation of NM22.0 FB846: Airborne messages reception (APR, FNM/MFS) v1.0

88 1- Background Short background of the FB: Why was it developed? This Functional Block will allow the AOs to provide AO Position Report (APR) type messages to NMOC and FNM/MFS via B2B Web Services too. As well, it will allow Gander (FNM Flow Notification Message), Shanwick and Santa Maria (MFS Message from Shanwick/Santa Maria) to start the implementation of these messages via NM B2B. What was the business need? Until now, the AFTN network has been the only available solution for establishing the communication between the ANSPs and the NMOC systems. However, web services are a more modern and more cost-effective way of exchanging data, based on internet technology. The aim is to increase the interoperability required in the future ATM systems. nm.releases@eurocontrol.int 88

89 2- New features NM will provide new B2B web service. It will ensure that the NMOC systems will be prepared to accept and process new type information sent by users applications. All the information will be present under OneSky Team NM B2B Service Documentation. An AO shall develop its own application in order to be able to successfully provide APR type information to NMOC systems. Same for Gander (FNM Flow Notification Message), Shanwick and Santa Maria (MFS Message from Shanwick/Santa Maria) messages. 89

90 3- Impact of the FB No impact on the current procedures, systems, way of working, etc; No change of ETFMS processing concerning the APR B2B compared with the actual APR received on AFTN; No change of IFPS processing concerning the FNM/MFS B2B compared with the actual FNM/MFS received on AFTN; No change in the way that the APR evaluation will be performed. Please follow the same steps described in the Flight Progress Messages document, Annex1. 90

91 4- Questions Any questions? 91

92 Presentation of NM22.0 FB906 Flight Planning Domain improvements v1.0

93 1- New features CR_040039: Suppress Copy REJ and MAN ORMs to AOA The change is requested following an Aircraft Operator complaint that the amount of -TITLE REJ for RQP messages received causes confusion and workload issues. The same problem exists for AFP, FNM, MFS, ACH, APL messages when they are rejected. The risk is that other REJ messages are overlooked due to the amount of copy REJ messages they are receiving for RQP/AFP/FNM/MFS not originated by them. By extension, the amount of -TITLE MAN could also cause confusion and workload issues. The change will also address the MAN messages in addition to the REJ. 93

94 1- New features CR_041608: Change SEQPT default for APL Because the standard surveillance equipment on commercial aircraft includes Mode_S, some ANSPs have problems when IFPS uses 'C' as the default surveillance equipment in the -SEQPT field (10b) of APL messages. During the AFP Workshop in May 2016, NM stakeholders asked that the default is changed to 'S'. An AFP with no SEQPT information that does not associate to a stored FPD. -TITLE IAFP -ARCID AIZ41 -FLTRUL I -FLTTYP S -ARCTYP B738 -WKTRC M -ADEP LLBG -ESTDATA -PTID ROLIN -ETO FL F150 -ROUTE N0320F150 ROLIN KTS -ADES UGKO -EOBD An APL is created with SEQPT set to 'S'. -TITLE IAPL -ADEP LLBG -ADES UGKO -ADESOLD UGSB -ARCID AIZ41 -ARCTYP B738 -CEQPT S -EOBD EOBT ORGNID ACCUGGG -ORIGIN -NETWORKTYPE AFTN -FAC UGGGZRZX -SEQPT S -WKTRC M -SRC AFP -FLTRUL I -FLTTYP S -ROUTE N0320F150 ROLIN KTS AFPEND -ESTDATA -PTID ROLIN -ETO FL F150 nm.releases@eurocontrol.int 94

95 1- New features CR_040806: Enhancement of the POSRTE field in IFPS REJ messages In an IFPS REJ message, the POSRTE field is present if the automatic creation of route alternative was successful or if it was set manually by an IFPS operator. To give the Airspace User's more information on the usefulness of the POSRTE field, it will include a difference indicator for the distance (expressed in +/- NM and +/- %). The difference indicator can be either 'PLUS' or 'MINUS', with a NM value and a percentage (PC) value. Example: -POSRTE N0450F400 TOR P601 BAVTA N873 TUSKA UN873 JUIST UP174 EEL UN872 PAM/N0450F410 UN872 DENOX UZ319 MOPIL/N0390F250: DIFF LENGTH PLUS 39NM 4PC nm.releases@eurocontrol.int 95

96 2- Impact of the FB ATC systems that receive APL messages from IFPS may be impacted by the change of the default for the surveillance equipment from C to S. Client systems that receive REJ messages from IFPS may be impacted by the change to the format of the POSRTE field in the message (AFTN/SITA/B2B). nm.releases@eurocontrol.int 96

97 3- Questions Any questions? 97

98 Presentation of NM22.0 FB907: Airspace Data Domain improvements v1.0

99 FB907: Airspace Data Domain improvements CR_ New AS type "CDA" Client Defined Area CR_ Designated significant Points for Helicopter Routes CR_ Terminal points for Aerodromes nm.releases@eurocontrol.int 99

100 CR_ New AS type "CDA" Client Defined Area 1- Background In CACD we already have today Test Airspaces. Some of them are indeed airspace which represent future sectorisation. Test means here not yet operational, hence do exclude them from validations. Next to future data there is also a need to define airspace volumes which do not fit in the regular concepts like ES constituent element of a CS and of an AUA, taking part in Clusters and Sector Configurations. Just an odd airspace volume needed for regulations or restrictions. But this volume, although it should be excluded from certain validations needs to be published to the users because it is referred by regulations or restrictions. nm.releases@eurocontrol.int 100

101 CR_ New AS type "CDA" Client Defined Area 2- New features A new classification of Airspaces: CDA Just a new attribute on Airspace externally available: Boolean (as we have already for Restrictions). Externally available attribute that allows the Airspace to be exported. The attribute is always set to true, for all airspaces except for test Airspaces, where it will be false. nm.releases@eurocontrol.int 101

102 CR_ New AS type "CDA" Client Defined Area 3- Impact of the FB New AS type "CDA" Client Defined Area CHMI: B2B: CDA is the same as Test Airspace, except CDA is B2B exported Test Airspace is not B2B exported CDA Sector will be exported as type SECTOR, with localtype= CDA localtype= CDA indicates that it is not a standard operational Sector but a Client Defined Airspace CACD Clients: no change: Test Airspace and CDA are category T nm.releases@eurocontrol.int 102

103 CR_ Designated significant Points for Helicopter Routes 1- Background Helicopter Routes cannot be defined in CACD as the PWP point syntax does not cover for the PWP used in these routes The syntax for the Helicopter Route Five-alphanumeric namecodes are described in Doc Example: See AIP Switzerland ENR nm.releases@eurocontrol.int 103

104 CR_ Designated significant Points for Helicopter Routes 2- New features Adapt the PWP syntax to Doc 8168 Paragraph 1.6 and allow 5 alphanumeric characters for PWP. The points must be unique in the database. Helicopter routes shall only be flight planned by Helicopters (Restriction to be implemented) nm.releases@eurocontrol.int 104

105 CR_ Designated significant Points for Helicopter Routes 3- Impact of the FB Implementation of published Switzerland Helicopter routes in CACD nm.releases@eurocontrol.int 105

106 CR_ Terminal points for Aerodromes 1- Background We received complaints from states that the syntax rules of the TER points in CACD is no longer adequate and not aligned with ICAO Doc CACD allows to link these points explicitly to a particular aerodrome. nm.releases@eurocontrol.int 106

107 CR_ Terminal points for Aerodromes 2- New features CACD Point Type TER ID syntax need to be adapted to cover for 5 alphanumeric. Full freedom of characters for Terminal points but a link with Aerodrome required (EH365: Point in Aerodrome Amsterdam) Link TER to an Aerodrome The point Id shall usually be constructed by the ICAO location indicator 3 and 4 and completed by 3 numeric. Only a syntax on the length (5 alphanumeric is needed) The points must be unique. nm.releases@eurocontrol.int 107

108 CR_ Terminal points for Aerodromes 3- Impact of the FB By relaxing the CACD business rule, we can now implement all official published TER points nm.releases@eurocontrol.int 108

109 4- Questions Any questions? 109

110 Presentation of NM22.0 FB967: E-Helpdesk improvement v2.0

111 1- Background Situation: Manual processing of individual delay improvement requests when Network situation does not allow to accommodate the improvement Manual processing of slot extension requests when extension not permitted Aircraft Operators waiting for requests to be processed E-Helpdesk improvements in order to: Provide faster processing of Aircraft Operators requests Allow NMOC focus on tasks with high added expert value to support the Network 111

112 2- Overview of new features 1. Automatic processing of delay improvement requests based on a global delay parameter 2. Automatic processing of delay improvement requests based on a specific regulation delay parameter 3. Automatic processing of slot extension requests nm.releases@eurocontrol.int 112

113 2.1 - Automatic processing of delay improvement requests based on a global delay parameter Procedure 1. Based on the Network situation, NMOC can enable, for a defined period of time, automatic processing of all delay improvement requests 2. All delay improvement requests will be automatically compared with the global delay parameter 3. Delay improvement requests with a delay lower or equal to the global delay parameter will be automatically processed 4. Delay improvement requests with a delay higher than the global delay parameter will be manually processed by NMOC Note: The automatic processing does not apply on flights in READY status. nm.releases@eurocontrol.int 113

114 2.2 - Automatic processing of delay improvement requests based on a specific regulation delay parameter Procedure 1. Based on the Network and specific regulation situation, NMOC can enable, for a defined period of time, automatic processing of delay improvement requests for a specific regulation 2. All delay improvement requests for flights captured by the specific regulation will be automatically compared with the specific regulation delay parameter 3. Delay improvement requests with a delay lower or equal to the specific regulation delay parameter will be automatically processed 4. Delay improvement requests with a delay higher than the specific regulation delay parameter will be manually processed by NMOC Note: The automatic processing does not apply on flights in READY status. nm.releases@eurocontrol.int 114

115 3 - Automatic processing of slot extension requests The E-Helpdesk automatically processes slot extension requests: 1. For flights departing from CDM airport: the slot extension request is not accepted 2. For flights departing from non-cdm or Advanced ATC TWR airports: A. The slot extension request is not accepted if the current time is outside the 20 min window before COBT (CTOT-TaxiTime) B. The slot extension request is not accepted if the current time has reached COBT (CTOT- TaxiTime) No extension possible as the clock time has reached COBT. The request shall be made by the FMP / TWR. nm.releases@eurocontrol.int 115

116 4- Questions Any questions? 116

117 Presentation of NM22.0 FB924: Rerouting Evolutions v1.0

118 1- Background Why this FB is being developed? To support users of NM rerouting services What is the main business objective? Improve the rerouting services provided by NM What was the problem it intends to solve? Improve the information associated to the alternatives Enhance the options available on the rerouting tools Improve the operational usability and user experience on: CHMI/NOP AOWIR NOP/CHMI IFPUV 118

119 2- New features CHMI/NOP AOWIR shall present IFPS valid alternatives Problem Statement When using CHMI/NOP AOWIR, the system provides alternatives that may or may not be IFPS compliant User has to try each alternative individually to visualize the possible errors The change will make AOWIR to present only IFPS valid alternatives Added value of the change Improving information presented on the route alternatives Improving usability to external users by displaying only routes which can be utilized Reduce unnecessary workload 119

120 2- New features CHMI/NOP AOWIR shall present IFPS valid alternatives AOWIR AOWIR current procedure in 21.5 Right click on desired flight Select option Rerouting function Choose flight to reroute 120

121 2- New features CHMI/NOP AOWIR shall present IFPS valid alternatives AOWIR AOWIR current procedure in 21.5 Right click on desired route Select option Reroute try Select desired reroute option 121

122 2- New features CHMI/NOP AOWIR shall present IFPS valid alternatives AOWIR AOWIR current procedure in 21.5 Potential outcome/system response: 122

123 2- New features CHMI/NOP AOWIR shall present IFPS valid alternatives AOWIR Improved procedure in 22.0 Select the desired flight from the flight list 123

124 2- New features CHMI/NOP AOWIR shall present IFPS valid alternatives AOWIR Improved procedure in 22.0 New checkbox Select IFPS compliant only Click Generate &Evaluate to create routes Only IFPS compliant routes are displayed! 124

125 2- New features CHMI/NOP AOWIR shall present overload valid alternatives and withdraw false overload positives Problem Statement Currently, AOWIR does not deliver any alternatives where the capacities have been reached (overload), while IFPS proposals do not check possible overloads. The change aims at allowing CHMI/NOP AOWIR to present reroutings alternatives without overload information where existing overloads are not deteriorated. 125

126 2- New features CHMI/NOP AOWIR shall present overload valid alternatives and withdraw false overload positives Flight s trajectory Overloaded area Proposed trajectory Overloaded area In NM 21.5 the Proposed trajectory is presented with an overload deterioration nm.releases@eurocontrol.int 126

127 2- New features CHMI/NOP AOWIR shall present overload valid alternatives and withdraw false overload positives 127

128 2- New features Additional AOWIR options and data to improve usability Problem Statement When using CHMI/NOP AOWIR, the user is not provided with relevant data on the alternatives that are generated. The user is not provided with important rerouting options to search for alternatives. Added value of the change Improving information presented on the route alternatives Improving usability to external users by displaying only routes which can be utilized

129 2- New features Additional AOWIR options and data to improve usability Freeze TP: Keeps the STAR/SID frozen in the computation of alternatives (before was always active). Horizontal Alternative / Vertical Alternative: Permits to explicitly search for horizontal or vertical alternatives (before was always horizontal). nm.releases@eurocontrol.int 129

130 2- New features Additional AOWIR options and data to improve usability Error: presents a summary of the IFPS/Overload/MAX Shift Delay reply on the alternative. FCI/RCI: Provides the fuel consumption indicator and route charge indicator for the alternatives presented. nm.releases@eurocontrol.int 130

131 2- New features Vertical rerouting improvements (Requested Flight Level sequence shaper improvement) Problem Statement Today flight planning tools users (NOP/CHMI IFPUV and CHMI/IFPS) cannot explicitly propose vertical alternatives to correct an invalid flight plan. The change aims at improving the alternative proposed by first providing a vertical alternative if available. To achieve that, whenever the system is proposing a route, it should first try a vertical alternative to correct errors and if none can be found, IFPS should try the horizontal alternatives. nm.releases@eurocontrol.int 131

132 3- Impact of the FB No direct operational impact for externals BUT Applicable on training if features are used 132

133 3- Impact of the FB Use the available Operational Testing Session period to familiarize with the features Complete Videos to explain the features will be produced and shared 133

134 Any questions? 134

135 Presentation of NM22.0 NM22.0: Way forward

136 2.1- NM22.0: The OPT (Operational Testing) (Release Notes 4.1.2) NM22.0 is available for testing with the OPT (operational testing) session! NM22.0 OPT session started on the 9 th of March and will end on the 26 th of April. With the NM22.0 OPT you will be able to: Test NM22.0 on your systems with your procedures. Download and test the new NM22.0 CHMI. Test the new NM22.0 NOP Portal. Test some new FBs (operational scenario provided in the OPT guide). B2B: NM 22.0 will be available on PREOPS (as from 27/03/ :00 UTC) 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 136

137 Way forward to NM22.0 migration NM22.0 migration is planned to start on the Wednesday 02/05/2018 (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 137

138 Any questions? 138

139 Many thanks for your participation! 139