A presentation to Externals of the NM20.5 Release via videoconference took place on the 20 th of September 2016.

Transcription

1 A presentation to Externals of the NM20.5 Release via videoconference took place on the 20 th of September Please find below: The link toward the video recording of this presentation: The link toward the NM20.5 Release Notes: The slides used during the Presentation. If any questions: v1.7: Changes (after the presentation) in the release dates, OPT date and in FB795

2 Presentation of NM20.5 to Externals EUROCONTROL Network Manager Directorate 20/09/2016 v1.7

3 Welcome to the Presentation of NM20.5 to Externals Agenda 1- Introduction and interface set-up 2- NM20.5 Release presentation: 2.1- Important notifications related to NM20.5 migration 2.2- FBs (Functional Blocks) presentation 3- Way forward toward NM20.5 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 NM20.5. 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- NM20.5 Presentation 9

10 2.1- NM20.5: Important notifications (Release Notes 2.1.2) Browsers recommended in NM20.5: Firefox 45 ESR (Extended Support Release) Internet Explorer 11 In addition, NM applications are still supported on Internet Explorer 10 on best effort basis (regression testing has been performed) Windows versions other than Windows 7 are not supported for CHMI. Update of the Regulation Reason codes (REGCAUSE) based on IATA field code (c.f. FB772) Decommission of NM B2B NM18.5 webservice. Decommission of old NM B2B URLs on PREOPS: Before NM20.5 (port 16443): After NM20.5 (port 443): c.f. NM Release Notes for more information. nm.releases@eurocontrol.int 10

11 2.1- NM20.5: The OPT (Operational Testing) (Release Notes 4.3.2) You can already test NM20.5 by participating to the OPT (operational testing) session! NM20.5 OPT session is ongoing until the 12/10/ /11/2016! With the NM20.5 OPT you can: Download and test the new NM20.5 CHMI. Test the new NM20.5 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). questions: cf NM Release Notes ( 4.3.2) for the link toward the OPT Instructions guide. Careful: Slide has been modified since presentation. Slide above is the reference. nm.releases@eurocontrol.int 11

12 Any questions? 12

13 2.2- NM20.5 FBs and CRs presentation Only new features impacting operations and Externals are presented Topics order differs slightly from the order in the Release Notes. Airspace Management and AFUA FB720 ASM Improvements FB794 Correction & Tuning of FB725 (Dynamic creation and update of ad-hoc airspaces) CR_ EAUP / EUUP subscription Cooperative Traffic Management FB730 Slot swapping Operations Improvements FB798 Airspace Data Domain improvements FB799 ATFCM Domain improvements CR_ Show VFR/OAT flights in B2B, CHMI, NOP Portal flight lists by aerodrome (included in FB767) FB759 Post-Deployment CCAMS FB760 Extend 833 Warning Mechanism FB791 Subscription facility for the Initial/Dynamic Network Plan Performance Programme FB772 Performance Work Programme (Update of the IATA delaycodes in the REGCAUSE field) Airport Programme CR_ Display TOBT/TSAT/TT in the protected NOP Portal Flight list FB753 Airport Programme NOP Information Services B2B FB795 New NM B2B Web Service for First System Activation (FSA) FB767 NM B2B improvements FB785 Flight status/situation via publish/subscribe nm.releases@eurocontrol.int 13

14 Presentation of NM20.5 FB720: ASM Improvements v1.6

15 List of CRs CR_ RSA exclusively defined as AMA and NAM for the AUP CR_ Adapt Compare function of EAUP/EUUP on the NOP Portal CR_ ASM Post-Ops Reports nm.releases@eurocontrol.int 15

16 CR_ RSA defined as AMA and NAM for the AUP - Background FUA is more and more publishing managed Airspaces (RSA) while in the past mainly CDR Routes were published. In the national AIP, RSAs are published as AMC-Manageable Airspace (AMA) or Non-AMC-Manageable Airspace (NAM). On the NOP portal, RSAs allocations were displayed in 2 tabs: Level 1 and Level 2. NAM existing in CACD are automatically published in AUP according to the default data (FLs and Time) as notified to AD SVR (normally AIP data) When a NAM was allocated differently from default data, it used to move from the Level 1 to the Level 2 tab in the EAUP, possibly leading Airspace Users to believe that it was no longer allocated. Only the defined type of areas (AMA/NAM) should be kept as reference in the EAUP/EUUP. nm.releases@eurocontrol.int 16

17 CR_ RSA defined as AMA and NAM for the AUP - Background nm.releases@eurocontrol.int 17

18 CR_ RSA defined as AMA and NAM for the AUP - New features On the NOP Portal EAUP display, the two tabs "Level1 RSA Allocations" and "Level2 RSA Allocations" are replaced by a single "RSA Allocations" tab. Possibility to filter by RSA Category. No confusion possible for CIAM CHMI as it shows AMA/NAM and Level1/Level2. AIXM5.1 easm extension continues to support Level1/Level2/Level3. RSA category easily derived from Level1/Level2. nm.releases@eurocontrol.int 18

19 CR_ RSA defined as AMA and NAM for the AUP - New features nm.releases@eurocontrol.int 19

20 CR_ RSA defined as AMA and NAM for the AUP - Impact of the CR Improved transparency and easier notification process allowing a more efficient FPL process, with potential benefits for flight efficiency. nm.releases@eurocontrol.int 20

21 CR_ Adapt Compare function of EAUP/EUUP on the NOP Portal - Background Adaptation of the Compare Function of EAUP/EUUP on the NOP Portal in order to allow the visualization of only the changes to airspace structures (RSA and CDR) in terms of time and FLs, with reference to the start validity time of the latest EAUP/EUUP used for the comparison. nm.releases@eurocontrol.int 21

22 CR_ Adapt Compare function of EAUP/EUUP on the NOP Portal - New features The EAUP/EUUP comparison result shows all differences by displaying old and new data next to each other. Comparison information outside the validity period of the latest EUUP is not displayed since it is irrelevant and making the comparison result very difficult to interpret. nm.releases@eurocontrol.int 22

23 CR_ Adapt Compare function of EAUP/EUUP on the NOP Portal - New features nm.releases@eurocontrol.int 23

24 CR_ Adapt Compare function of EAUP/EUUP on the NOP Portal - Impact of the CR Avoid problems due to misinterpretation. Flight efficiency: better use of available Airspace. nm.releases@eurocontrol.int 24

25 CR_ ASM Post-Ops Reports - Background Follows ASMSG/51 and NETOPS/13 approvals. Member States considered these reports very useful for the post-ops analysis of the ASM aspects. NOP NMIR identified as tool to provide the reports based on post-ops ASM data available in DWH. nm.releases@eurocontrol.int 25

26 CR_ ASM Post-Ops Reports - New features Airspace releases in UUPs. Statistics of flights both planned and flown on a CDR. Statistics of flights both planned and flown through a TSA/TRA in FRA. FUA parameters (level 1, 2 and 3) are eliminated, keeping only the defined type of areas AMA and NAM as reference for the publication in EAUP. nm.releases@eurocontrol.int 26

27 CR_ ASM Post-Ops Reports - Screenshot nm.releases@eurocontrol.int 27

28 CR_ ASM Post-Ops Reports - Info Link to the procedure for obtaining access to NM's Operational Services and Products: Form allowing new and existing customers to apply for initial or additional access/es to NM Services, including NMIR: nm.releases@eurocontrol.int 28

29 4- Questions Any questions? 29

30 Presentation of NM20.5 FB794: Correction & Tuning of FB725 (Dynamic creation and update of ad-hoc airspaces) v1.5

31 List of CRs CR_040824: Dynamic creation and update of ad hoc Non AMC- Manageable (NAM) areas 31

32 CR_040824: Dynamic creation and update of ad hoc NAM areas - Background FRA and published DCTs require the implementation of ad-hoc areas on short term publication. Follows the implementation of the dynamic creation and update of ad-hoc AMA areas introduced in NM Rel Need to dynamically create and update NAM areas independently from AIRAC cycles by means of the AUP/UUP. nm.releases@eurocontrol.int 32

33 CR_040824: Dynamic creation and update of ad hoc NAM areas - New Features Create completely new ad hoc areas. Create airspace volumes out of existing airspaces. Make corrections on wrongly introduced (or missing) information in the data release of an AIRAC. Being classified as NAM, these areas will be automatically retrieved by CACD and published in AUP, including associated EU restrictions, if any. To be retrieved as published in NOTAM with EU restrictions associated. nm.releases@eurocontrol.int 33

34 CR_040824: Dynamic creation and update of ad hoc NAM areas - Screenshots 3 most used tabs from the Create AS screen. nm.releases@eurocontrol.int 34

35 CR_040824: Dynamic creation and update of ad hoc NAM areas - Impact of the CR No impact on current ASM procedures, as ad hoc areas are managed like any existing area via AUP/UUP. No CHMI Impact. nm.releases@eurocontrol.int 35

36 Questions Any questions? 36

37 Presentation of NM20.5 CR_040708: EAUP / EUUP subscription v1.5

38 1 - Background Improvement to existing NOP Portal subscription facility: To communicate by additional means ( ) the release of EAUP or EUUP. To facilitate flight planning usage of the latest updated route availability. nm.releases@eurocontrol.int 38

39 2 - New features Current Notification Subscriptions. In the coming NM Release nm.releases@eurocontrol.int 39

40 2 How to subscribe 1. Click the CUSTOMISATION ICON 2. Click the Customise Subscriptions LINK 40

41 2 How to subscribe 1. Then in the new window, click on the EDIT ICON 2. Tick on the EAUP BOX 3. Click on the SAVE ICON and then on the CLOSE ICON 41

42 2 When a new EAUP is released, the following will be distributed. Similarly, when a new EUUP is released, an equivalent will be distributed (reading EUUP instead of EAUP). nm.releases@eurocontrol.int 42

43 3 - Impact of the FB No impact. Voluntary subscription, Same basis as today. nm.releases@eurocontrol.int 43

44 4- Questions Any questions? 44

45 Presentation of NM20.5 FB730: Slot swapping v1.5

46 1- Background SESAR User (AU) Driven Priority Process trial demonstrated the operational feasibility and performance gains associated with swift identification and request to NM to swap ATFCM regulated flights eligible in line with AU priorities. AUs requested operational deployment of the tool, 46

47 2- New features NM20.5, NM deploys the necessary NM back-end system changes and includes a new facility based upon the flight list service B2B for external users to query which regulated flights are eligible for swapping. The User will still need to use the NOP E-help desk to request slot swaps to NMOC <flight:flightlistbyaircraftoperatorreply>... <flight> <flightid> <id>at </id> <keys> <aircraftid>klm16v</aircraftid>... <keys/> </flightid> <slotswapcounter> <currentcounter>0</currentcounter> <maxlimit>3</maxlimit> </slotswapcounter> <slotswapcandidatelist> <item> <ifplid>at </ifplid> <subjectdeltadelayminutes>8</subjectdeltadelayminutes> <candidatedeltadelayminutes>-8</candidatedeltadelayminutes> <swapdecidebytime> :22</swapDecideByTime> </item> </slotswapcandidatelist> </flight>... <flight:flightlistbyaircraftoperatorreply> nm.releases@eurocontrol.int 47

48 3- Impact of the FB None unless CFSP or AU wishes to build a tool to interface to the B2B facility. Otherwise, in time, NM plans to deploy an operational (NOP front end) version to the tool and integrated with the NOP E-help desk requests. This evolution is planned for NM21.0. nm.releases@eurocontrol.int 48

49 4- Questions Any questions? 49

50 Presentation of NM20.5 FB798: Airspace Data Domain improvements v1.5

51 1- Background Background Introduces improvements to Airspace Data Domain and Operations Addresses developing operational requirements Improves the quality of CACD operations 2 CRs nm.releases@eurocontrol.int 51

52 2- New features CR_039942: An APP can also control a CTA Currently there is no possibility to link a CTA to an APP except by a workaround using an airspace of TMA instead of a CTA Problem1 : desynchronization between publication and data Problem2 : difficulties with EAD downloads because of wrong airspace naming convention TMAs and CTRs could already be associated as Related Airspaces for an APP, this CR is extending that to CTAs With the introduction of this feature, an APP can also control one CTAs using the Related Airspaces functionality nm.releases@eurocontrol.int 52

53 2- New features CR_40638: Capture flights filed on DCTs in FRA Context Air Route DCT DCT RSA With the introduction of this feature, Restrictions can directly discriminate between flights filed on DCTs and on Routes, to allow crossing on Routes It is possible to define a Restriction that only forbids flights filing on DCTs from crossing an area. The flight plan is rejected when the Restriction is violated. nm.releases@eurocontrol.int 53

54 3- Impact of the FB Impact of the FB on externals Global improving CACD operations by: Aligning CTAs publication and CACD More flexibility for capturing FPLs crossing active RSAs Simplifying the description of FUA restrictions No impact for FPL filers 54

55 4- Questions Any questions? 55

56 Presentation of NM20.5 FB799: ATFCM Domain improvements CR_040540: Regulation Proposal via B2B v1.0

57 1- Background Short background of the FB: Why was it developed? ATFCM regulations are today transmitted via telephone call from FMPs to NMOC. The current coordination can be error prompted. The current coordination can the be inefficient during the transmission or interpretation or data. What was the business objective? To support SO5 Collaborative Traffic Management. To improve the cooperation between local optimization functionalities and network functions To support SO2 - Deploy interoperable and effective information management systems To exchange seamless, correct and real-time information sharing between all operational actors is essential in order to share performance and operational intelligence and enable operational CDM. What was the problem it intends to solve? Reduce coordination time Reduce coordination errors Improve the ATFCM measures queue management nm.releases@eurocontrol.int 57

58 2- New features Regulation_proposal_demo.htm For externals: Video is available on the recording 39mn 30s For internals: Phase of Operations PRE-TACTICAL TACTICAL Proposals Create Modify Cancel 58

59 3- Operational Deployment 1. Official Request 2. PRE_OPS Accessible for external applications testing Previous Certificate 3. ACCEPTANCE ACTIVITIES Performed during the 2 months after initial request (*) Technical Testing (& fixing) Use Cases & Acceptance criteria to be communicated Operational Evaluation (FMP & NMOC) 1 day session 4. Phase 1 (OPS) 3 months of duration Mandatory telephone coordination If major problems identified back to PRE_OPS 5. Phase 2 (OPS) Optional telephone coordination (*) If no major bug fixing problems

60 3- Impact of the FB Operational Instruction distributed for comments (DRAFT by 20 th September) Coordination process Detailed fields editable & convention Detailed fields convention ODSG Action Paper ATFCM Manual (DRAFT by end September the OI is temporary) B2B Reference Manual (DRAFT by end September) NOP Portal Integrated Documentation (by end September) Operational Instruction B2B Reference Manual Contact 60

61 4- Questions Any questions? 61

62 Presentation of NM20.5 FB767: NM B2B improvements CR_040778: Show VFR/OAT flights in B2B, CHMI, NOP Portal flight lists by aerodrome v1.6

63 2- New features CR_040778: Show VFR/OAT flights in flight lists by aerodrome Aim of the CR_ : provide the VFR / OAT flights in Flight list by aerodrome / set of aerodromes, Flight list by traffic volume when the reference location is an aerodrome or set of aerodromes, Traffic counts by aerodrome / set of aerodromes. It is available : via B2B (Request/Reply only), On NOP portal, On CHMI. Via B2B <flight:flightlistbyaerodromerequest>... <dataset> <type>operational</type> <dataset> <includeproposalflights>false</includeproposalflights> <traffictype>load</traffictype> <trafficwindow> <wef> :45</wef> <unt> :45</unt> </trafficwindow>... <includeinvisibleflights>true</includeinvisibleflights>... <aerodrome>lfpg</aerodrome> <aerodromerole>departure</aerodromerole> </flight:flightlistbyaerodromerequest> nm.releases@eurocontrol.int 63

64 2- New features CR_040778: Show VFR/OAT flights in B2B flight lists by aerodrome In the NOP Portal In the CHMI VFR / OAT nm.releases@eurocontrol.int 64

65 4- Questions Any questions? 65

66 Presentation of NM20.5 FB759: Post-Deployment CCAMS v1.0

67 1- Background The FB759 addresses the Centralised Code Assignment and Management System (CCAMS) and Mode S users requests for new facilities and improves the overall SSR transponder code usage: Facilitate shadow operations for CCAMS users CR_ Introduction of the possibility to have individual and independent addressing for code requests reception and code assignment transmissions Optimise the CCAMS use of omnidirectional codes CR_ No Mini Flight Data (MFD) for circular flights Support ATSUs in cases of local Mode S contingency situations CR_ Possibility to suppress the insertion of the MODE S ELS IFPS FLAG (IFP/MODEASP) into an FPL using restrictions nm.releases@eurocontrol.int 67

68 2- New features CR_ Possibility to suppress the insertion of the MODE S ELS IFPS FLAG (IFP/MODEASP) into an FPL using restrictions Today the Mode S flagging is based on static ENV data that can be modified only on AIRAC dates (worst case 28 days) The flagging is used to indicate that a flight is eligible for the use of the conspicuity code A1000 This change allows the suppression of the Mode S flag on short notice (e.g. minutes) in case of local ATSU failures or maintenance It reduces the need for coordination with adjacent centres and the likelihood of human errors and lack of correlation nm.releases@eurocontrol.int 68

69 2- New features CR_ Introduction of the possibility to have individual and independent addressing for COR reception and CAM transmission. Required by CCAMS users in support to migration to new ATS systems Facilitates the shadow operations during transition to new ATS systems Today ATSU/ Instance 1 Code request Code assignment CCAMS ATSU/ Instance 2 nm.releases@eurocontrol.int 69

70 2- New features NM 20.5 ATSU/ Instance 1 ATSU/ Instance 2 Code request Code assignment CCAMS nm.releases@eurocontrol.int 70

71 2- New features CR_ No MFD for circular flights Today a Mini Flight Data set is created for flights for which a code request (COR) is received and for which a corresponding flight plan is not found in ETFMS Most cases are VFR and/or military flights departing and landing at the same airport (circular flights) that can use local codes Some systems still send code requests to CCAMS even if they don t actually use the CCAMS code The change will enable CCAMS to reject such requests and will save omnidirectional codes for relevant use The CCAMS change done at central level avoids the need for multiple local ATS systems changes nm.releases@eurocontrol.int 71

72 3- Impact of the FB Impact of the FB on partners The only visible effects for the users will be The improved reaction time for Mode S flagging in case of local failures The improved protection against code conflicts The increased flexibility for migration to new ATS Systems nm.releases@eurocontrol.int 72

73 4- Questions Any questions? 73

74 Presentation of NM20.5 FB760: Extend 833 Warning Mechanism v1.5

75 1- Background EU Implementing Regulation IR 1079/2012 lays down requirements for voice channel spacing for the Single European Sky Extends the applicability of 8.33 Voice Channel Spacing (VCS) area below FL195 in Switzerland, Norway and EU Member States Sets requirements for airspace users equipage (8.33 VCS compatible VHF radio equipment and exemptions: e.g. State aircraft) Sets specific provisions for State, ANSP, airspace users etc. VHF frequency assignments below FL195 gradually converted in 8.33VCS until 2018 Aircraft entering the new 8.33 airspace will require to be properly equipped. ANSPs manifested their interest in the possibility of implementing a warning mechanism Early awareness of airspace user of the incoming change as a means of mitigating the lack of information Increase airspace users knowledge of the gradual conversion and associated requirements of the airspace below FL195 nm.releases@eurocontrol.int 75

76 2- New features Based on the previous 8.33VCS implementation October 1999, 8.33 khz above FL245 in ICAO EUR region and March 2007, 8.33 khz above FL195 in ICAO EUR region The 8.33 Warning Mechanism (FB760) will provide: An 8.33 warning in the form of a comment in the ACK message An indication of the crossed FIRs which may require 8.33 equipage before IR date (2018) The 8.33 Warning Mechanism addresses: All accepted FPL for non-8.33 equipped (non Y ) aircraft operating in/crossing the area below FL195 of the concerned States Including currently exempted flights (e.g. state aircraft, etc.) nm.releases@eurocontrol.int 76

77 2- New features ACK message -COMMENT MANDATORY 8.33KHZ RADIO EQUIPMENT REQUIRED FROM 01/01/2018. LOVV, EDGG, EDWW FIR MAY REQUIRE 8.33KHZ RADIO CARRIAGE BEFORE THIS DATE. CHECK AIP/AIC. 77

78 3- Impact of the FB No changes in IFPS procedures. IFPS client systems shall be able to accept COMMENT field in ACK messages (ADEXP format). COMMENT field in ACK is not a new field (IFPS Users manual 20.0): Size of ACK messages may be slightly larger if several COMMENT s are present. Note: The message will be available from AIRAC 1612 November 10 th, 2016 nm.releases@eurocontrol.int 78

79 4- Questions Any questions? 81

80 Presentation of NM20.5 FB791: Initial / Dynamic Network Plan (INP/DNP) CR_ Subscription facility for the Initial / Dynamic Network Plan v1.5

81 1 - Background Improvement to existing NOP Portal subscription facility: To communicate by additional means ( ) the release of the Initial/Dynamic Network Plan (INP/DNP). To enhance awareness of the INP release. nm.releases@eurocontrol.int 83

82 2 - New features Current Notification Subscriptions. In the Release NM 20.5 nm.releases@eurocontrol.int 84

83 2 - How to subscribe 1. Click the CUSTOMISATION ICON 2. Click the Customise Subscriptions LINK nm.releases@eurocontrol.int 85

84 2 - How to subscribe 1. Then in the new window, click on the EDIT ICON 2. Tick on the HEADLINE NEWS and Initial Network Plan box 3. Click on the SAVE ICON and then on the CLOSE ICON nm.releases@eurocontrol.int 86

85 2 - When a new INP is released, the following will be distributed. nm.releases@eurocontrol.int 87

86 3 - Impact of the FB No impact Voluntary subscription, Same basis as today. nm.releases@eurocontrol.int 88

87 4- Questions Any questions? 89

88 Presentation of NM20.5 FB772: Update of the IATA delaycodes in the REGCAUSE field of the SAM, SRM & FLS CR_ Update Regulation REASON codes based on IATA v1.5

89 1- Background Update of the IATA delaycodes in the REGCAUSE field of the SAM, SRM & FLS. 91

90 1- Background (cont d) The REGCAUSE field includes the NM Regulation Cause and Location code combination (e.g. CE & AA) and the corresponding IATA delaycode as per the published correlation table between IATA Delaycodes and NM Regulation Reasons. Early 2016 IATA published an updated correlation table between IATA Delay Codes and the NM Regulation Reasons: Following the introduction of a new NM Regulation Cause and Location combination: V-E which had not yet been linked to an IATA delaycode Following a general update in the main IATA delaycodes and subcodes of the AHM730 & AHM731 The correlation table is published in: NM ATFCM Users Manual (Annex 5) IATA Airport Handling Manual AHM730. nm.releases@eurocontrol.int 92

91 2- New features Six NM Regulation Causes and Location Code combinations saw a change in the corresponding IATA delaycode: 1. G-D => IATA delaycode G-A => IATA delaycode E-D => IATA delaycode E-A => IATA delaycode W-E => IATA delaycode V-E => IATA delaycode 81 nm.releases@eurocontrol.int 93

92 3- Impact of the FB772 ATFCM Users Manual Changes compared to NM

93 4- Questions Any questions? 95

94 Presentation of NM20.5 CR_037419: Display TOBT/TSAT/TT in the protected NOP Portal Flight list v1.5

95 1- Background CDM information from DPI messages: TOBT Target Off Block Time TSAT Target Start-up Approval Time Taxi Time Already available on the NOP Portal & CHMI Flight Data Display Airlines and IATA requested these fields in the Flight List of the NOP Portal and of the CHMI Their rationale was to: Centralize all relevant CDM information Facilitate flight management Enhance situational awareness of the AOCCs (Airline Operations Centre) for their flights Implementation in NM 20.5 limited to the NOP Portal CHMI implementation will follow most probably in NM

96 2- New features 98

97 3- Impact of the FB NOP Portal Users will be able to consult the TOBT, TSAT or TT directly in the Flight List 99

98 4- Questions Any questions? 100

99 Presentation of NM20.5 FB753: Airport Programme v1.5

100 FB753: Airport Programme In the scope of the Airport-CDM Programme, NM will: Modify the validation parameter for TTOT of E-DPI, T-DPI-t and T-DPI-s (CR_039930) Improve TOBT & TSAT usage implementation (CR_039928) 102

101 1- CR_039930: Modify validation parameter for TTOT of E-DPI, T-DPI-t and T-DPI-s Background: TTOT value is used to reflect the most accurate take-off time to update the flight's profiles and update the counts Acceptance windows used by ETFMS: To identify TWR or Airport CDM systems wrong inputs To reduce negative impact on predictability Change: CR_ will adjust the Acceptance windows following operational experience: The margins of acceptance will be generally extended Lower risk of TTOT/message rejection When criteria not met, the DPI messages are rejected with PROVIDED TAKE OFF TIME OUT OF BOUNDS 103

102 2- CR_039928: Improve TOBT & TSAT usage implementation Background: TOBT and TSAT values are displayed on CHMI & NOP Portal and can be retrieved via B2B TOBT could be used by NM to automatically trigger a DLA (delay) message on behalf of an airline The Acceptance windows are used by ETFMS to identify wrong inputs of TWR or Airport CDM systems The CR aims at improving the validation rules applied for the TOBT and TSAT nm.releases@eurocontrol.int 104

103 Changes: 2- CR_039928: Improve TOBT & TSAT usage implementation The margins of acceptance have been generally extended for TOBT A TSAT earlier than TOBT will no longer be accepted An Oplog message TOBT missing will be generated when: Message received after ETFMS_OBT - 40 minutes And it does not contain a TOBT value In the CDM concept, TSAT and TOBT are related: A TSAT will no longer be accepted without an associated (and valid) TOBT When criteria not met, TOBT or TSAT value will be ignored and also a previously received TOBT or TSAT value will be erased. The rest of the DPI message will be processed nm.releases@eurocontrol.int 105

104 3- Important note 106

105 4- Questions Any questions? 107

106 Presentation of NM20.5 FB795: New NM B2B Web Service for First System Activation (FSA) v1.5

107 First System Activation (FSA) message The purpose of the FSA message is to inform the NMOC about the progress of airborne flights and to supply the NMOC with updated information on airborne flights. The FSA may supply the NMOC with the Actual Take-Off Time (ATOT) from the aerodrome of the departure or with estimated time, level and point of entry into the airspace of the FDPA. The FSA will also supply the NMOC with significant changes in the flight plan route to allow for reliable predictions of the future flight profile. This message will be received and processed by ETFMS. It will be used to update ETFMS flight data, in order to get a more accurate prediction of the sector counts. nm.releases@eurocontrol.int 109

108 1- Background Short background of the FB: Why was it developed? This Functional Block will allow the ANSPs to provide First System Activation (FSA) type messages to NMOC via B2B Web Services too. 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 110

109 2- New features NM will provide a new B2B web service. It will ensure that the NMOC systems will be prepared to accept and process FSA type information sent by users applications. An ANSP or TWR shall develop its own application in order to be able to successfully provide FSA type information to NMOC systems. nm.releases@eurocontrol.int 111

110 Examples: Careful: Slide has been modified since presentation. Slide above is the reference. 112

111 Examples: Example 2: Flight Update on departure with departure procedure included Careful: Slide has been modified since presentation. Slide above is the reference. 113

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

113 4- Questions Any questions? 115

114 Presentation of NM20.5 FB767: NM B2B improvements v1.5

115 1- Background Objective: Improve various existing B2B services to better support operations and business in various domains. Need for making new information available: CFSPs need for covering SID/STAR Synonym Ids (e.g. for use in ARINC424) CR_041033: link between ICAO Id and Synonym Ids added in B2B. Need for improving correctness of flight correlation CR : Aircraft address added in B2B Need for adding flexibility and decreasing size of EAUP P/S messages CR_041035: Need for customizing EAUP message content via P/S Need for organising NM B2B web services in a logical way nm.releases@eurocontrol.int 117

116 2- New features CR_041033: Export Terminal Procedure synonyms Terminal Procedures (TP) in airspace database may have synonyms. AIXM5.1 CACD export now contains TP ICAO Id and Synonym Id Extension to the Procedure feature of AIXM5.1 <aixm:standardinstrumentarrival> <aixm:timeslice> <aixm:standardinstrumentarrivaltimeslice>... <aixm:designator>ablin1l</aixm:designator>... <aixm:extension> <adrext:procedureextension "> <adrext:hassynonym> <adrext:synonym > <adrext:synonymid>abli1l</adrext:synonymid> </adrext:synonym> </adrext:hassynonym> </adrext:procedureextension> </aixm:extension> </aixm:standardinstrumentarrivaltimeslice> </aixm:timeslice> </aixm:standardinstrumentarrival> 118

117 2- New features CR_041034: Provide aircraft address via B2B The 24 bit aircraft address is now available via B2B: Request/Reply as a <requestedflightfield> in flightlist and flightretrieval. Note: already available in Publish/Subscribe -Flight Data- since NM 20.0 The 24 bit aircraft address present in about 30% of flight plans. Often included in the airborne messages received by TACT (e.g. CPRs). Allow to improve the correctness of flight correlation. Request <flight:flightlistbyaerodromerequest> <requestedflightfields>aircraftaddress</requestedflightfields> <flight:flightlistbyaerodromerequest> Reply <flight:flightlistbyaerodromereply <data> <flight> <flightid>... </flightid> <aircraftaddress>3c66a6</aircraftaddress> </flight> </data> <flight:flightlistbyaerodromereply> nm.releases@eurocontrol.int 119

118 2- New features CR_041037: Provide highest profile for PT, AS, RS via B2B R/R Scope: query on a flight via B2B Request/Response, Possibility to require the most accurate (that s to say highest) profiles for Points, Airspace, and/or Restrictions profiles. The most accurate profile available is then returned 1. FTFM (Filed Tactical Flight Model) 2. RTFM (Regulated Tactical Flight Model (by ATFM Measures) 3. CTFM (Current Tactical Flight Model) E.G FlightRetrievalRequest Flight Field enumeration: highestmodelpointprofile highestmodelairspaceprofile highestmodelrestrictionprofile E.G FlightRetrievalReply reuse the existing flight fields: ftfm/rtfm/ctfmpointprofile ftfm/rtfm/ctfmairspaceprofile ftfm/rtfm/ctfmrestrictionprofile nm.releases@eurocontrol.int 120

119 2- New features CR_041035: Make P/S EAUP Message customizable Scope: P/S EAUP Message Possibility to configure the content of received messages EAUP summary only (returned by default) + CDR Openings / Closures + RSA/ Allocations See below example of subscription <publishsubscribe:subscriptioncreationrequest > <topic>eaup</topic> <payloadconfiguration-eauppayloadconfiguration> <includecdropeningsclosures>true</includecdropeningsclosures> <includersaallocations>false</includersaallocations> </payloadconfiguration-eauppayloadconfiguration> </publishsubscribe:subscriptioncreationrequest> nm.releases@eurocontrol.int 121

120 2- New features CR_041036: Move tactical updates operations to FlowServices All tactical updates operations now belong to the Flow Services group. New port type: TacticalUpdates queryhotspots & updatehotspot move to TacticalUpdates port type List of Tactical updates operations retrievesectorconfigurationplan updatesectorconfigurationplan retrievecapacityplan updatecapacityplan retrievetrafficvolumeactivationplan updatetrafficvolumeactivationplan retrieveotmvplan updateotmvplan retrieverunwayconfigurationplan updaterunwayconfigurationplan 122

121 2- New features CR_041038: Add reason For Change to PS Subscription Technical Message The Subscription Technical Message now convey information about the reason for the latest update of state. USER _ REQUEST, MSG_EXPIRED, MAINTENANCE <publishsubscribe:subscriptiontechnicalmessage > <lastupdatedby>nm_admin</lastupdatedby> <lastupdatedon> :49:44</lastUpdatedOn> <lastupdatereason>msg_expired</lastupdatereason> </publishsubscribe:subscriptiontechnicalmessage> PAUSE Create PAUSED Resume <publishsubscribe:subscriptiontechnicalmessage> ACTIVE <lastupdatedby>tstxb2b7</lastupdatedby> <lastupdatedon> :39:24</lastUpdatedOn> <lastupdatereason>user_request</lastupdatereason> </publishsubscribe:subscriptiontechnicalmessage> Example of Resume done by user and Pause automatically done by NM nm.releases@eurocontrol.int 123

122 3- Impact of the FB By concept, changes in B2B interface induce changes on Client Application to be able to benefit from them. Significant impact to benefit from these improvements Extension to the Procedure feature of AIXM5.1 Change of service group for the Tactical updates Subscription management adaptation: EAUP payload configuration, technical msg. Documentation: B2B Airspace Service Group Reference Manual B2B Flow Service Group Reference Manual B2B Publish Subscribe Service Group Reference Manual 124

123 4- Questions Any questions? 125

124 Presentation of NM20.5 FB785: Flight status/situation via publish/subscribe v1.6

125 1- Background Flight Plan and Flight Data via Publish/Subscribe introduced in NM20.0 Identified Needs : Customize the Flight Data message payload (i.e. content). CR_ Make Flight Data message customizable Expand the data available in Flight Data messages. CR_ Flight Data fields. Enhance the message filtering. CR_ CR_041058: Flight Data / Flight Plan subscription filtered by FPL originator Objectives: Improve usability Reduce size of messages Reduce over-subscription to get the needed information. nm.releases@eurocontrol.int 127

126 2- New features CR_ : Make Flight Data message customizable <publishsubscribe:subscriptioncreationrequest>... <topic>flight_data</topic>... <messagefilter-flightdatamessagefilter>... </messagefilter-flightdatamessagefilter> New <payloadconfiguration-flightdatapayloadconfiguration> <flightfields> <item>lastknownposition</item> <item>highestmodelpointprofile</item> </flightfields> </payloadconfiguration-flightdatapayloadconfiguration> </publishsubscribe:subscriptioncreationrequest> nm.releases@eurocontrol.int 128

127 2- New features CR_ and CR_041057: Flight Data fields NM20.0 flightid (IFPLId, ADEP, ADES, EOBT) Aircraft operator operatingaircraftoperator FlightState suspensionstatus Estimated/calculated/actual TakeOffTime Estimated/calculated/actual TimeOf Arrival TaxiTime cdmdata mostpenalizingregulation Highest point profile (ftfm/rtfm/ctfm) Diverted AerodromeofDestination Last Known position NM20.5 flightid (IFPLId, ADEP, ADES, EOBT) aircrafttype aircraftoperator operatingaircraftoperator icaoroute filedregistrationmark aircraftaddress flightstate suspensionstatus Estimated/calculated/actual TakeOffTime Estimated/calculated/actual TimeOf Arrival cdmdata currentlyusedtaxitime readystatus delay mostpenalisingregulation mostpenalisingregulationcause hasotherregulations regulationlocations targettimeoverfix divertedaerodromeofdestination confirmedctfm highestmodelpointprofile highestmodelairspaceprofile lastknownposition Default Configurable 129

128 2- New features CR_ / CR_041058: Flight Data / Flight Plan subscription filtered by FPL originator flight plan originator the originator of the first FPL message. new flightplanoriginators added in FlightSetDefinitionElement class FlightPlanSubscriptionModel FlightSetDefinitionElement + aerodromes :flight:aerodromeidandrole[] + aircraftoperators :flight:aircraftoperatoricaoid[] + aircraftregistrations :flight:aircraftregistrationmark[] + anuids :airspace:airnavigationunitid[] + flightplanoriginators :airspace:airnavigationunitid[] NOTE: Impact on Request / Reply Modification made in flightlist and flightretrieval field removed: flightplanoriginator Replaced by two fields: very first FPL message (new information). MessageOriginator initialfplmessageoriginator originator of the lastest flight plan-related message MessageOriginator lastfplmessageorig nm.releases@eurocontrol.int 130

129 3- Impact of the FB By concept, changes in B2B interface induce changes on Client Application to be able to benefit from them. Significant impact to use NM 20.5 definition: Change in Subscription management of Flight Data and Flight Plan P/S Documentation: B2B Publish Subscribe Service Group Reference Manual 131

130 4- Questions Any questions? 132

131 Presentation of NM20.5 to Externals NM20.5: Way forward

132 Way forward to NM20.5 migration NM20.5 OPT session is ongoing until the 12/10/ /11/2016! 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 NM20.5 CHMI You can test the new NM20.5 NOP Portal You can test some new FBs questions: cf NM Release Notes ( 4.3.2) for the link toward the OPT Instructions guide. OPS CHMI is available for download since today (20/09/2016). Cf. Headline News and AIM issued this morning. Next week: Slides and recording of the Presentation available (mailing to participants, Release Notes, forums (ODSG, etc.), B2B users). [NM B2B] NM PRE-OPS environment will be available shortly is available (communication via OneSky Team). NM20.5 B2B draft documentation is available will be available in the coming days on OneSkyTeam. Careful: Slide has been modified since presentation. Slide above nm.releases@eurocontrol.int is the reference. 134

133 Way forward to NM20.5 migration NM20.5 migration is planned to start on the 18/10/ /11/2016 (last around 1 week) Detailed Release migration plan may be found in the NM Release Notes ( 4.3.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 Careful: Slide has been modified since presentation. Slide above is the reference. nm.releases@eurocontrol.int 135

134 Any questions? 136

135 Many thanks for your participation! 137