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

Transcription

1 A presentation of the NM18.5 to Externals via video-conference took place on the 9 th of July Please find below: The link toward the recording of this presentation: The link toward the NM18.5 Release Notes: The slides used during the Presentation. If any questions: nm.releases@eurocontrol.int

2 Presentation of NM18.5 to Externals EUROCONTROL Network Manager Directorate 09/07/2014 v1.3

3 Welcome to the Presentation of NM18.5 to Externals Agenda 1- Introduction and interface set-up 2- Release Functional Blocks presentation 3- Way forward toward NM18.5 migration 3

4 Recording Presentation is recorded and will be available on the Eurocontrol public website in a few days: nm.releases@eurocontrol.int 4

5 Preparation To be done now: 1- Click on the green tab on the middle-top of the screen: 2- Click on «Participants» 3- Click on «Chat» 5

6 Ask questions Questions may be asked at the end of each Functional Block presentation. Questions may be ask orally or by chat. How to ask a question orally: 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» 4- If for any reason you did not get the floor, click on the micro and speak nm.releases@eurocontrol.int 6

7 Ask questions How to ask a question by chat: 1- Type your question in the Chat window, start with your company name 2- Select «Everyone» and click on «Send» 3- The presenter will read the question and reply to it orally nm.releases@eurocontrol.int 7

8 Release presentation Goals of the presentation: Present the new features of the Release Assess their impacts for you Ask questions (today or by ) Why doing the presentation now? SHOM2 (Software Hand-Over Meeting) is passed. 8

9 NM18.5 Release presentation Only Functional Blocks impacting operations and Externals are presented. NM-01 - Free Route Airspace FB576 FRA (Free-Route Airspace) evolutions NM-02 - Airspace Management and AFUA FB510 ASM interoperability level 2 - Live Updates NM-05 - NOP Information Services FB630 NOP Access to event information consolidation NM-08 - Operations Improvements FB626 Provision of Departure data FB638 ASM monitoring FB657 CSST improvements FB659 ATFCM Domain improvements FB660 Flight Planning Domain improvements FB661 Improve CHMI Services FB668 Performance Work Programme RD-02 - Airspace Users Operations R&D FB619 Slot swapping process nm.releases@eurocontrol.int 9

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

11 Presentation of NM18.5 FB576: Free Route Airspace (FRA) Evolutions v1.0

12 New features 1. Reject FPLs where routes are filed along or adjacent to operational airspace boundaries 2. Stop boundary clipping 12

13 1- Reject FPLs along or adjacent to operational airspace boundaries 1.1- Background IFPS shall identify and reject a flight plan where a flight files a DCT route between published points aligned with operational airspace boundaries (ie boundary of Area of Responsibility of ATC Unit) nm.releases@eurocontrol.int 13

14 1- Reject FPLs along or adjacent to operational airspace boundaries 1.1- Background Why? Routing is not acceptable from an ATC perspective Problems encountered in Ireland, UK, Portugal, Latvia and Finland Request for change made at ODSG and RMG prior to 2012 Route Availability Document (RAD) - no fly DCTs have been created to mitigate this problem by ANSPs IAA created more than 150 no fly DCTs in the RAD alone - to ensure this type of routing is not filed. Entries could be removed if the requirement is implemented at the IFPS processing level FRA part of SESAR Deployment Implementing Rule for Pilot Common Projects - deadline 2022 Number of occurrences expected to increase with greater freedom of choice given to Users with pan-european cross border deployment of FRA nm.releases@eurocontrol.int 14

15 1- Reject FPLs along or adjacent to operational airspace boundaries New Feature Detects FPLs exactly on a boundary, but also FPLs immediately adjacent to a boundary Detection done by shifting the relevant DCT segment in the profile to the left and the right and recalculating airspace intersection (see drawing next slide) nm.releases@eurocontrol.int 15

16 1- Reject FPLs along or adjacent to operational airspace boundaries New Feature Y Parameters create border window for search: - width: shift to left and right - length: max length along border Airspace A Airspace B DCT segment close to airspace border Width - at each side - shift to left and right: 0.5nm Length - max length along border: 15nm X Initial Parameters agreed at RAD MG 24 Prototype demonstration provided to IAA and NATS nm.releases@eurocontrol.int 16

17 1- Reject FPLs along or adjacent to operational airspace boundaries Impact of the FB Reduce workload/cost on ANSPs to prepare, submit and maintain RAD restrictions to mitigate the problem Helps to simplify RAD Meets operational need to avoid this type of routing, saving workload for aircrew and ATC if detected early on at flight planning phase nm.releases@eurocontrol.int 17

18 New features 1. Reject FPLs where routes are filed along or adjacent to operational airspace boundaries 2. Stop boundary clipping 18

19 2- Stop boundary clipping 2.1- Background Stop boundary clipping - change of 15nm re-entrance parameter for Free Route Airspace During airspace validation testing for FRA implementation several ANSPs requested the removal of this feature and requested the parameter be reduced to 0nm Airspace B Airspace A nm.releases@eurocontrol.int 19

20 2- Stop boundary clipping 2.1- Background IFPS accepts free route DCT segments to exit and then re-enter the same Free Route Airspace when the distance between exit and re-entry is less than 15nm To mitigate the effects of the rule some ANSPs have created No fly DCTs in the RAD i.e. BULATSA (86) and ROMATSA (46) 20

21 2- Stop boundary clipping New Feature In NM Release 18.5 the parameter will be changed to 0nm and flight plans will be rejected nm.releases@eurocontrol.int 21

22 2- Stop boundary clipping Impact of FB Prevents boundary clipping - expected to increase with the large scale implementation of FRA where Users are given greater freedom of choice Enables simplification of RAD by removing no fly DCTs nm.releases@eurocontrol.int 22

23 Questions Any questions? 23

24 Presentation of NM18.5 FB510: B2B Publication of ATM Live Updates v1.0

25 1- Background Continuation of work started under the Airspace Data Repository programme. To provide airspace users with the most up to date and consistent view of operational airspace data and to improve ASM interoperability. FB510 impacts B2B Services only. Specifically the data exported via Aeronautical Information Exchange Model (AIXM) i.e. the AirspaceServices. 25

26 1- Background NM Release: 15/ e-rad in EAD (AIXM 4.5) e-ami pilot phase EAUP on NOP (AIXM 5.1) e-ami operational FRA/DCT restrictions with e-rad e-restrictions via ftp operational Access to AIRAC static operational data (FB 441) pilot phase PTRs available on ftp server (AIXM 4.5) All restrictions available in AIXM 5.1 via NM B2B services (FB555) Migrate e-rad clients from EAD to NM B2B (FB555) Dynamic updates available in AIXM 5.1 via B2B services (FB510) (including CRs for LARA V3 Deployment.) 26

27 2- Current (NM18) features Daily AIXM 5.1. baselines of CACD Airspace data. Baseline for subsequent AIRAC available from AIRAC -6 days (2 data sets available). 27

28 2- New features Availability of Airspace data dynamic updates i.e. within 10 minutes of CACD entry. Includes: CDR and Airspace activation/availability from AUP/UUP Route NOTAM changes NAT Tracks All Restriction modifications SID/STAR availability (N.B for Restriction reference only). Corrections to NM AIRAC data definition 28

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

30 3- Impact of the FB No impact on current AIXM 5.1 service or procedures. New features can be exploited gradually. 30

31 4- Questions Any questions? 31

32 Presentation of NM18.5 FB630: NOP access to Event information V0.1

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

34 Network Events Portlet Access Network Manager Public Portal No access restriction (no need for password/token/etc.) Accessible on all Tabs: Strategic, Pre-tactical, Tactical, Post-Operations FB630 Impact on users: None 34

35 Network Events Before March 2014 (pre - NM 18.0) nm.releases@eurocontrol.int 35

36 Current Status: what we have achieved so far 36

37 Network Events in NM Now nm.releases@eurocontrol.int 38

38 Network Events in NM 18.5 (FB630) 39

39 Search Network Events 40

40 Search Results Now 41

41 Search Results NM 18.5 Search Result statistics Click on name to open Event Details View 42

42 Network Event Details now NM

43 Network Event Details General Information Summary Name Type Sub Types Status Estimated Period Confirmed Period Locations Short Description Last Published Description and Expected Benefits Description Expected Benefits Originator Organisation Name, Type, ICAO Code Description Measures and Scenarios Reference Publications Remarks and Comments Originator Comments Network Manager Comments Activities and Impacts For each Activity/Phase of the Event the following information is provided General Information Period Locations Description Attachments Impact on Capacity and/or Flight Efficiency For each impact the following information may be available: Period Network Impact Description Capacity Variation Sector Configuration Traffic Sample Description Traffic Sample Description Impacted Locations Possible Bottleneck Sectors Comments Attachments Milestones When no information is available in the database then the text not defined or none is shown. 44

44 Notifications NM

45 Notification Results (example) NM

46 Objectives: what we want to achieve A Collaboration Platform on NM Portal for Network Event Information exchange and integration in the overall Network Planning and ATFCM Processes nm.releases@eurocontrol.int 47

47 Network Events Goal ANSP, ACC, ATC, FAB, Airport, Tower, Military, etc. External Systems/ database s NET Input Events NM Units (OPL, NOS, NMC, APT, OMR, CACD, STATFOR, PRISMIL, etc.) Event data production & update NM Portal NET Repository Event data storage & quality management NET View Events ANSP, ACC, ATC, FAB, Airport, Tower, Military, etc. External Systems NM Systems (DDR,NEST, etc.) NM Units (OPL, NOS, NMC, APT, OMR, CACD, STATFOR, PRISMIL, etc.) Event data consumption nm.releases@eurocontrol.int 48

48 Network Events Portlet Phase 1 Events Data owners DNM External Input Events ANSP, ACC, ATC, Mil, FAB, etc. OP L MILIT ARY Network Events Input Airport, Tower, Military, etc. APT Input Events Event data production ERNIP Airport Corner NET Repository & Interfaces Events Data consumer DNM External OP L ERNIP Event s View ERNIP MILO NO S ANSP, ACC, ATC, FAB, etc. Transitio n Plan DD R Network Events FMP & other events list Network Events View Military events list Airpor t Event s View Airport Corner PRISMIL NMC OMR APT Airport, Tower, Military, etc. Event data storage & quality management Event data consumption nm.releases@eurocontrol.int 50

49 Benefits of NET why we want it Increase efficiency of data collection and dissemination: Centralise the events information collected through various sources Improve the visibility of the complete set of data on events information available in the agency Cost reduction, complexity reduction Improve information sharing internal and external Enable access to event information according to user needs/interest Increase awareness on events and their potential updates Reduce occurrences of missing information Increase event data quality Reduce data duplication Improve data content (coherence and consistency checks between events) Improve modelling of the event(s) to include them in planning processes (and tools) Expected Result: Support a more efficient response to the traffic demand Better use of human resources (more time for analytical tasks, less time for editorial/admin tasks); Refine traffic demand (flight intentions) and required mitigation actions, taking into consideration the impact of event(s) on the Network operations; Better use of sector capacity and/or airspace structures improving flight efficiency; Reduce delays, shorten routes flown nm.releases@eurocontrol.int 51

50 What we have achieved so far Integration of 5 event data sources: ERNIP ATFCM Special Events AXIS Events Military Events (Airport Corner Events some issues to be resolved before NM 18.5) Transition Plan for Major Projects Unrestricted Access to information according to users needs Events can be searched 10 years in the past and 20 years in the future; In Calendar only events relevant to the specific month/day are listed; Deleted events are accessible (visible; no archiving yet); All changes are recorded, along with author and timestamp Ability to subscribe to notifications increasing awareness on events Ability to increase event data quality Improved coherence in event data modelling Ability to identify potential duplicates nm.releases@eurocontrol.int 26 Sep

51 What remains to be done 01/06 /2013 Start 30/06 /2013 NM 18.0 NM 18.5 NM 19.0 NM 19.5 Preparation Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Deliverables : Project Charter Project Plan Deliverables : NET1 Package 1 Functionality Deliverables : Package 2 Functionality Deliverables : Package 3 Functionality Deliverables : Package 4 Functionality Deliverables : Package 5 Functionality Network Events Phase 1 operational since 12 March2014 (R18.0) Model Improvement s Calendar Reporting/ Notifications improvemen ts Search improvemen ts Map View B2B interface Map improvement s Integration Pack nm.releases@eurocontrol.int 53

52 What next for you Access Network Events portlet and get familiar to current functions/presentation Participate to OPT in September 2014 Provide comments ) On-line help will be deployed with NM18.5 Web training may be developed if needed Further improvements in next NM releases refer to the future NM Release Notes nm.releases@eurocontrol.int 54

53 Questions 55

54 Presentation of NM18.5 FB626: Provision of Departure data v1.0

55 Background FB626: Provision of Departure data NM receives DPI (Departure Planning Information) messages from CDM Airports (Collaborative Decision Making Airports). The DPI messages of a flight can contain TOBT and TSAT information. TOBT (Target Off-Block Time): Provider: Aircraft Operator or Ground Handler What is TOBT: Estimation by the Aircraft Operator or Ground Handler of the time that an aircraft will be ready: all doors closed, boarding bridge removed, pushback vehicle available and ready to start up / push back immediately upon reception of clearance from the TWR. TSAT (Target Start-Up Approval Time): Provider: Tower - ATC What is TSAT: The time provided by ATC that an aircraft can expect for its start up / push-back approval, taking into account TOBT (Target Off-Block Time), CTOT (Computed Off-Block Time) and/or the traffic situation. nm.releases@eurocontrol.int 57

56 FB626: Provision of Departure data Today (NM18.0) Available today (NM18.0) TOBT and TSAT are currently received from 5 A-CDM Airports: EBBR (Brussels), LSZH (Zurich), ENGM (Oslo), LIRF (Roma), LEMD (Madrid). TOBT and TSAT information are available in the Operational Log of a flight: CHMI NOP Portal nm.releases@eurocontrol.int 58

57 Request: FB626: Provision of Departure data NM18.5 Today, the TOBT and TSAT are lost inside the operational log. The Aircraft Operators request to see the TOBT and TSAT fields for their flights departing from CDM-Airports. Benefit: Improve operations of AOs by providing them situational awareness when their flights are at an outstation CDM-Airport. New features of NM18.5: The TOBT and TSAT fields will be displayed for flights departing from a CDM-Airport on the NOP Portal and CHMI. This information will be presented in the Flight Data (CHMI) / Flight Details (NOP Portal). nm.releases@eurocontrol.int 59

58 FB626: Provision of Departure data NM18.5: CHMI 60

59 FB626: Provision of Departure data NM18.5: NOP Portal 61

60 Impact: FB626: Provision of Departure data Impact No impact for Users that don t use TOBT and TSAT TOBT and TSAT are now available in a more user friendly manner. nm.releases@eurocontrol.int 62

61 4- Questions Any questions? 63

62 Presentation of NM18.5 FB638: Airspace Management Monitoring v1.0

63 1- Background NM shall support the European Commission by providing relevant input for the preparation of the Single European Sky Performance Scheme - includes Union-wide performance targets and Key Performance Indicators (KPIs), - before the reference periods and for monitoring the achievements during the periods nm.releases@eurocontrol.int 65

64 1- Background Environment Key Performance Area - KPIs Reference Period to 2019 Rate of planning CDRs - the ratio of aircraft filing flight plans via CDRs and the number of aircraft that would have planned them Effective use of CDRs - ratio of aircraft using CDRs and the number of aircraft that would have planned them Becomes mandatory for NM and Member States to monitor the effectiveness of the booking procedures for FUA nm.releases@eurocontrol.int 66

65 2. New Features Work already started on KPIs in FB601 - Release Improve the algorithm for calculating the alternate route for a given CDR segment Improved algorithm will take into consideration the geographical coordinates of the points to calculate distances and directions of routes which is mandatory for the fully correct and stable assessment of the FUA KPIs nm.releases@eurocontrol.int 67

66 2. New Features 68

67 2. New Features Compute the ASM FUA KPIs for Free Route Airspace As described in the updated version of the ASM Handbook - Section 7 nm.releases@eurocontrol.int 69

68 3- Impact of the FB No operational impact on NM users KPIs will be reported through existing ASM CDM processes and available through NM Interactive Reporting Meets need of NM and Member States for SES Performance Scheme RP2 Starting 1 January 2015 nm.releases@eurocontrol.int 70

69 4- Questions Any questions? 71

70 Presentation of NM18.5 FB657: CSST (Call-Sign Similarity Tool) improvements v1.0

71 1- Background FB657 Developed to improve CSST Version 18.0 following user feedback. Enhance CSST functionality and make the application more attractive to existing and new users. 73

72 2- Modification to Transformation Rule default setting The idea behind the transformation rule is that the user wants to keep a link as far as possible between the Commercial Flight Number (CFN) and Call Sign (Example 1234 becomes 123A). Current default behaviour : CSST tries to find a conflict free solution according to the transformation rule. Where it finds no solution CSST defaults to ATC format and preferences rule and proposes solutions which are NOT according to the transformation rule. New behaviour : With a modification to the deconfliction screen, when user selects transformation rule, the ATC Format and preferences rule is disabled. Conflicts not resolved with Transformation rule are marked as No Solution. The user can then analyse these conflicts separately. nm.releases@eurocontrol.int 74

73 Current Behaviour Selecting Transformation rule. 75

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

75 3- Impact of the FB Transformation rule operates according to user expectations. 77

76 Call Sign Similarity Tool Access Access using NM token id enabled for CSST (free for existing tokens) Step 1: NM Service Request Form at: Step 2: CSST Stand alone access at: tml 78

77 4- Questions Any questions? Further information at 79

78 Presentation of NM18.5 FB659: ATFCM Domain Improvements v1.0

79 Scope Changes in Scope CR_ Change in traditional flight suspension message comment CR_ Visibility of flights adjusted to the clock CR_ Delay Confirmation Threshold nm.releases@eurocontrol.int 81

80 CR_ Change in traditional flight suspension message comment Airports opened can be not available for different reasons. The comment of the suspension in case of Zero Rates (XCD/FCM) has been harmonized from CLOSED to AERODROME OR AIRSPACE OR POINT NOT AVAILABLE. 82

81 Scope Changes in Scope CR_ Change in traditional flight suspension message comment CR_ Visibility of flights adjusted to the clock CR_ Delay Confirmation Threshold nm.releases@eurocontrol.int 83

82 CR_ Visibility of flights adjusted to the clock A regulated flight can become not regulated whenever a regulation is cancelled or period is adjusted. A slot cancel message (SLC) is sent. The regulation ID and the delay suffered are still presented in the flight lists for information. In this situation the flight is adjusted to the clock. An a will be presented in the Delay column to identify those flights. ` nm.releases@eurocontrol.int 84

83 Scope Changes in Scope CR_ Change in traditional flight suspension message comment CR_ Visibility of flights adjusted to the clock CR_ Delay Confirmation Threshold nm.releases@eurocontrol.int 85

84 CR_ Delay Confirmation Threshold 1- Background Flights crossing exceptional regulations (strike, scenarios) are suspended (FLS). Airspace Users have to confirm (FCM) to operate. Objectives: Inform of the closure. Give airspace users the possibility to confirm to receive a slot or cancel. Improve predictions and free capacity. Limitations No alternatives given. No delay information in the suspension message. Initial slot is lost. Consequences Prediction and capacity objectives not achieved. Flights close to the end of the closure are suspended. Sequence based on confirmation time stamp. nm.releases@eurocontrol.int 86

85 CR_ Delay Confirmation Threshold 2- New Features Operational Groups (ODSG and AOG) supported NM system enhancements on the flight confirmation process in order to: Alleviate Airspace Users of unnecessary workload. Improve network predictability and capacity. Improve CDM process during suspension mechanism. The New Delay Threshold Feature will: Instead of suspending all flights, establish a Delay Threshold at regulation level. Allocate flights with delays below threshold value. Suspend flights with delays above (EOBT-2h). Include the delay information in the suspension message. Book the initial slot during the response by time period (20 ). Allocate flights that are confirmed during the response by time period. Keep suspended and free the slot of flights that are not confirmed after response by time period. Delay Threshold value will be published in the AIM and showed in regulation description. This improved mechanism will be used in a trial mode for Scenarios (rerouting and level cap). The usage will be extended later on to other operational situations (strikes, airport non availability). nm.releases@eurocontrol.int 87

86 CR_ Delay Confirmation Threshold 2- New features Before Estimated Off Block Time (EOBT) 2 hours Flight not suspended nm.releases@eurocontrol.int 88

87 CR_ Delay Confirmation Threshold 2- New features ` Regulation Description nm.releases@eurocontrol.int 89

88 CR_ Delay Confirmation Threshold 2- New features At Estimated Off Block Time (EOBT)- 2 hours nm.releases@eurocontrol.int 90

89 CR_ Delay Confirmation Threshold 2- New features During Resp.by time period (20 ) nm.releases@eurocontrol.int 91

90 CR_ Delay Confirmation Threshold 3- Impact of the FB [NEW] Flight Suspension Message Format Example Message : Sent to: Message description:-title FLS -ARCID AFR8788 -IFPLID AA ADEP LFPO -ADES GMMN -EOBD EOBT PTOT 1000 Provisional Take-Off Time -RESPBY 0630 Response by -REGUL DTS9811 -COMMENT SUSPENDED DUE TO DELAY EXCEEDING THRESHOLD VALUE. SEND FCM BEFORE RESPBY TO SECURE PTOT. ALTERNATIVELY, REROUTE, OR UPDAT EOBT WITH A DLA MSG, OR CNL -TAXITIME REGCAUSE CE 81 nm.releases@eurocontrol.int 92

91 Impact of the FB on Airspace Users current procedure, Monitor suspended flights. Confirm the flight, slot already lost. Flight gets the delay but slot lost. Consider other alternatives before EOBT-2h (rerouting). New procedure, Monitor delayed flights that could be suspended at EOBT-2h. Consider alternatives before EOBT-2h (rerouting). Monitor suspended flights 2h before estimated off block time. Take action on suspended flights between EOBT-2h and the next 20 minutes. Systems, CR_ Delay Confirmation Threshold 3- Impact of the FB New Provisional Take Off Time (PTOT) field in the suspension message New Response By field in the suspension message. nm.releases@eurocontrol.int 93

92 CR_ Delay Confirmation Threshold 3- Extra Information A dedicated OPT session (registration required) will be organized between 1/9/2014 to the 12/9/2014 (weekdays). To participate and receive more details, please send an to nm.releases@eurocontrol.int. Training Material can be found in Eurocontrol Training Zone. ATFCM_Users_Manual will be updated and published by 1 st August. nm.releases@eurocontrol.int 94

93 Any questions? 95

94 Presentation of NM18.5 FB660: Flight Planning Improvements v1.0

95 1- Background FB660 has been included in the NM18.5 release to continue the evolution of the NM Flight Planning Services 97

96 2- New features CR_ Check that an EOBT update does not create a duplicate flight plan Background One of the IFPS fundamental rules is that no two flight plans with the same call sign should be allowed to exist within the IFPS Zone for flights where the calculated profiles overlap in time. This rule is enforced by IFPS for FPL messages as part of the association functionality. However, the rule is not currently enforced for other flight plan associated messages that may cause two flight plans with the same call sign to overlap in time. Change in NM18.5 IFPS shall identify flight plan associated messages that update the EOBT of a stored flight and cause two flight plans with the same call sign stored in IFPS to overlap in time and include a warning in the outputted ACK message of the flight plan associated message. nm.releases@eurocontrol.int 98

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

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

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

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

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

102 3- Impact of the FB Impact of FB660 on externals ANSP flight plan data processing systems that receive IFPS messages may need to be upgraded to process correctly the change to the ACH messages and the new IFP/ indicators. Flight plan originator procedures, MMI and systems may need to be updated to correctly handle the ACK messages for DLA/CHG messages that overlap, and the change to the text of the PROF201 error. 104

103 4- Questions Any questions? 105

104 Presentation of NM18.5 FB661: CHMI Improvements v1.0

105 1- Background FB661 CHMI Improvements: Occupancy counts are becoming the primary tool used by core area FMPs for traffic monitoring. OTMVs (Occupancy Traffic Monitor Values) are archived but occupancy counts cannot be queried on Data Warehouse. The Monitoring of flight profile are becoming of primary importance for the analysis of traffic complexity in the context of STAM (Short-Term ATFM Measures). PTRs (Profile Tuning Restrictions) and intruders are two criteria that need to be investigated in post-ops. For the time being no post-ops analysis is supported by CHMI on STAM procedures. This is necessary for monitoring the correctness of OTMVs and perform STAM post-ops analysis. New features: CR_035841: Ability to see the PTRs in Archive CR_033641: Archiving OTMVs CR_031145: Access to Occupancy counts in CIFLO Archive menu 107

106 2- New features CR_031145: Access to Occupancy counts in CIFLO Archive menu 108

107 2- New features CR_033641: Archiving OTMVs 109

108 CR_035841: Ability to see the PTRs in Archive 2- New features 110

109 3- Impact of the FB CR_031145: Access to Occupancy Counts on Archive is new in the Data Warehouse architecture, there is a risk of long response time. For this reason the NM 18.5 implementation is prototype in order to validate the technical solution. FMP pilot sites will be requested to validate the implementation. There is no impact on external systems and procedures. nm.releases@eurocontrol.int 111

110 4- Questions Any questions? 112

111 Presentation of NM18.5 FB668: Performance Work Program v1.0

112 1- Background Short background of the FB: The new NMIR document is available for NMIR users (Network Manager Interactive Reporting tool) impacted by the ATFM IR It is composed of 3 reports: The ATFM Compliance - Slot Tolerance The ATFM Compliance - Departure Tolerance The ATFM Compliance - Flight Plan Suspension These reports retrieve weekly figures and flights list for a given country for each of the reports The name of the document is «ATFM Compliance Weekly Monitoring» and is placed under the «Statistics > Overall Pictures» categories For any questions concerning the access to the NMIR tool, please to contact nm.releases@eurocontrol.int nm.releases@eurocontrol.int 114

113 2- New features ATFM Compliance Slot Tolerance 115

114 2- New features ATFM Compliance Departure Tolerance 116

115 2- New features ATFM Compliance Flight Plan Suspension 117

116 3- Impact of the FB The only impact for the externals is the availability of the document if they are users of the NMIR 118

117 4- Questions Any questions? 119

118 Presentation of NM18.5 FB619: Slot swapping process v1.0

119 1- Background ATFM Slot-swapping already exists, but needs to be improved to meet Airspace Users needs. The UDPP (User Driven Prioritisation Process) project team and the NM Slot-Swapping Task Force joint forces to collaboratively propose new processes to answer Airspace Users expectations. The UDPP Step-1 is a SESAR project, with a deadline to provide the Validation Results by End The changes need to be implemented in time to be able to run the Live Trial that will validate the Slot-swapping improvements. Several B2B Users requested more information on Regulations to be available by B2B. The FB619 will provide via B2B information required for the trial in the operational environment, available for all users. nm.releases@eurocontrol.int 121

120 2- New features FB619 will provide the ATFCM regulations list and details via B2B: Regulation id Applicability period Regulation state Regulation reason Cherry picked (or not) Location (TV id, TV description (as in ANM), TV flight levels, reference location) Regulation rates per time period (normal, pending, equipment, supplementary as in CHMI or NOP Portal) Others: Remark (as in ANM), autolink (or not) and linked regulations, No delay window (around ETO). The data and interface requirements will be described in the FlowServices B2B Reference manual. 122

121 3- Impact of the FB No impact for the users not using this information. Need to adapt Users systems to use the information. 123

122 4- Questions Any questions? 124

123 Presentation of NM18.5 NM18.5: Way forward v1.0

124 Way forward to NM18.5 Migration Mid-July 2014: Recording of the Presentation available Mid-July 2014: New version of NM Release Notes with Release migration plan From the 1/9/2014 to the 12/9/2014: NM18.5 OPT (Operational Testing) covering: CHMI no registration required NOP Portal no registration required NOP B2B (pre-ops environment) no registration required FB659: ATFCM Domain improvements - CR_ (New Delay Threshold regulation) - registration required Instructions for OPT will be sent in August via the Release Notes (and associated mailing). NM18.5 migration: start on the 23 September 2014 (1 week) Any question: nm.releases@eurocontrol.int nm.releases@eurocontrol.int 126

125 Any more questions? 127

126 Thank you for your participation 128