The presentation to Externals of the NM23.0 Release via - PowerPoint PPT Presentation

FB1001: ATFCM Domain improvements 2- New features  FAM is applied on all flights, whether regulated or not, that are:  departing from  landing in  crossing an area where CPRs are received by the NM and FAM is activated.  25 minute FAM parameter is reduced to 20 minutes – applies on flights  departing from, landing in or crossing (with less than 3 hour flying time to) areas where CPRs are received by the NM and FAM activated.  No change - 120 min FAM parameter – applies on flights  departing from non-FAM-enabled areas but with a destination in or crossing a FAM enabled area with more than 3 hours flying time to the FAM enabled area; 26 nm.releases@eurocontrol.int

FB1001: ATFCM Domain improvements 2- New features  FAM applicability FAM parameter: 20 minutes 1. X FAM parameter 20 minutes for EET less than 3 hours FAM parameter 120 minutes for EET more than 3 hours 2. X FAM parameter 20 minutes for EET less than 3 hours FAM parameter 120 minutes for EET more than 3 hours X 3. = FAM enabled CPR-covered areas 27 nm.releases@eurocontrol.int

FB1001: ATFCM Domain improvements 3- Background Reduction of FAM parameter from 25 to 20 minutes  After consultation and approval of ODSG/41 the 30 min FAM parameter will be gradually reduced to 15 min by 5 min step every NM Release;  NM22.5: first step of reduction from 30 min to 25 min;  NM23.0: second step of reduction from 25 min to 20 min;  Objective  improve network predictability and reinforce IFPS compliance (checking updated EOBT);  In addition, according to ICAO Doc 7030 any changes to the EOBT of more than 15 minutes for any IFR flight within the IFPZ shall be communicated to the IFPS which further supports the FAM parameter adaptation.  Follow-up/Results of the change will be presented at the next ODSG & AOG meetings;  Further information is available at: http://www.eurocontrol.int/articles/enhanced-tactical-flow-management- system-etfms  Or contact: nmfamreduction@eurocontrol.int 28 nm.releases@eurocontrol.int

FB1001: ATFCM Domain improvements Questions Any questions? 29 nm.releases@eurocontrol.int

Presentation of NM23.0 CR_043914: TACT activation versus Expecting FSA & AOWIR services v1.1

CR_043914: TACT activation versus Expecting FSA & AOWIR services 1 - Background TACT Activation and FSA Expected A flight is TACT Activated if:  the clock reaches ETOT/CTOT  At the reception of T-DPI-s/A-DPI for non-regulated flights or a compliant T-DPI-s/A-DPI for a regulated flight. Once the flight is TACT Activated, a flight is flagged either:  with no FSA expected  with FSA expected A flight is flagged as TACT Activated with FSA expected if departs from a aerodrome where departure FSA are received  These aerodromes are set in ENV as part of an Aerodrome Set 32 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 1 - Background TACT Activation and FSA Expected 33 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 1 – Background (Limitation 1) Flights departing from the A-CDM aerodromes are not flagged as TACT Activated with FSA Expected 34 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 1 – Background (Limitation 1) TACT Activated flights departing from an A-CDM aerodrome are not subject to AOWIR function 35 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 2 – Functional Improvements The NM plans to remove the early TACT activation by T-DPI-s in order to: • Solve the deficiencies on the expecting FSA mechanism for A- CDM departures reported by Flow Management Units. • Support DCB activities by improve the count details and the flights lists information (see impact). • Overcome the Aircraft Operators What-It rerouting (AOWIR) limitations reported by Aircraft Operators. • Simplify the current complexity of the flight status structure experienced by the ATM community. 39 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 3- Impact of the change Service affected Aeronautical Flight Reporting Flow Information Other Planning /AS data Internal Yes computation Data structure User Yes Interface Yes Procedures Yes Training Yes B2B Other  Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. 42 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 3- Impact of the change • ETFMS Flight Data (EFD) users processing flight data containing a CTFM profile shall consider that there is not anymore an association with FLTSTATE TA (TACT Activated). • B2B flight data users processing CTFM data shall consider that there is not anymore an association with Flight Type TACT_ACTIVATED. • Flight Update Messages (FUM) users processing data and considering the FLTSTATE TA (TACT Activated) shall evaluate the proposed change. 43 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 3- Impact of the change • CHMI/NOP users shall note that the TACT Activated status as a result of processing a T- DPI-s will not appear or update to ‘t’ the column ‘Type of Flight Data’. • The flight will remain as Filed ‘I’. This is also applicable to the flight details display. 44 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 3- Impact of the change • CHMI/NOP users shall note that, depending on the FSA_Category of the departure aerodrome, the traffic count details presented for each count interval: • Will exclusively consider as ‘TACT activated with FSA expected’ flights for which the clock has reached the ETOT or a valid TTOT from A-DPI has been processed. • Similar criteria as above for the case ‘TACT activated with no FSA expected’. 45 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 3- Impact of the change • All users shall note that there are no changes in the way CASA gives CTOT improvements 46 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services 4- Communication Plan • The communication process started in spring 2018. • The NM communication plan included different stakeholders (Airspace Users, Flow Management Units, and Airports) and FUM/EFD/B2B users • The NM communication plan was discussed in • Consultation groups (AOG, ODSG, DPI-WG) • For more details on the functional block • NM 23.0 Release Notes 47 nm.releases@eurocontrol.int

CR_043914: TACT activation versus Expecting FSA & AOWIR services Questions Any questions? 48 nm.releases@eurocontrol.int

Presentation of NM23.0 FB1019: NM Helpdesk Improvements FB917: CTM Coordination evolutions DCB Measure proposal via B2B v1.1

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 1- NM Helpdesk Service  To solve urgent particular operational problems beyond the use of ATFM message exchange:  Assisting stakeholders on specific flight actions  Providing information concerning ATFCM measures.  Available via:  electronic means (NOP Portal e-Helpdesk)  electronic requests with priority over phone calls.  phone when no internet access (mainly business aviation). 50 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 2- Background – Why CTM - FB917 NM - FB1019 S18 Experience S18 Experience • Capacity shortfalls • MUAC Customer Initiative to help their • Exponential increase of requests customer improve operation • Jeopardize the Network service • When possible flight exclusion/improvement to NMOC by email S19 Strategy • Enhance Network support S19 Strategy • Automation • MUAC Continuation Customer initiative • Integration • Introduce flight request to NMOC via • Request classification B2B Less workload / phone communication (NMOC and other stakeholders) 51 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 3- Impact of the FBs FB917 FB1019 Impacted Stakeholders Impacted Stakeholders • FMP • FMP / TWR / AO • NMOC • NMOC • Post Ops • Post Ops Service affected Aeronautical Reporting FB1019/FB 917 Flight Planning Flow Information/AS Other data Internal computation Data structure Yes User Interface Yes Procedures Yes Training Yes B2B Yes Other 52 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B FMP AO/TWR/FMP Local Local I identify my need I identify my and send my System System need on my request to NMOC directly from my working system working system B2B Manual NM Systems HelpDesk (NOP/Phone) Flight Exclusion Request Flight Exclusion Request Slot Improvement Request Regulation Creation Request Slot extension request Slot Improvement Request Slot Swap request …. Manual B2B NMOC staff analyze the results and I introduce the introduce the answer request from to the request in the the e-helpdesk e-helpDesk/Phone into the ETFMS I receive the request on system , I analyse and NM System accept/reject the request NMOC Staff NMOC Staff B2B B2C nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 4- FB917/FB1019 Overall view FB917 Avoid duplicates. FB1019 AUTOMATION Avoid duplicates. Comments! FB917 FB1019 Integrated Coordination / FMP Order in queue Rationalization Originator FB1019 URGENCY Objectives CTOT USER + FMP (CTM + E-Helpdesk) +TWR FB917 Ongoing. INTERFACE FB917 Digitalised proposal FB1019 NOP 54 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 4- CTM - FB917 New features FMP EDYY FMP systems EXCLUDE B2B IMPROVE PROPOSED NMOC NM systems ACCEPTED/ FB917 Features: REJECTED AFR1234 EXCL REG_A18 RYR4567 IMPR REG_B18 • EXCLUDE flight from regulation(s) B2B proposal • IMPROVE flight in B2B regulation B2B proposal ACKNOWLEDGED NMOC REVIEW PROCESS 55 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 4- E-Helpdesk FB1019 New features  Access for TWR and FMP (CR_045011)  To relax the telephone line - overall faster response  FMP/TWR will be able to make following requests:  Request for slot extension  Request for slot improvement  Requests exclusion from regulation 56 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 4- FB1019 New features  Classification of FMP/TWR/AO requests (CR_045012)  New queue management, to focus on critical requests.  Criterias for sorting requests: 1. Originator of the request (CDM > Adv. TWR > Std. TWR > FMP > AO) 2. Type of the request (Extensions > Exclusions > Improvements > Other) 57 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 4- FB1019 New features  Automatic processing of requests For requests before EOBT-2h (SIT1) (CR_045015) • • Requests for Slot Improvement and Slot Extension that arrive before the Slot allocation time (SIT1 = EOBT-2h) will be automatically processed by the NM system. • For duplicate requests (CR_045014) • In order to focus the workload on the critical requests and increase the customer satisfaction, NMOC will strengthen the mechanism for identification of duplicate requests. Based on average delay (CR_044319) • • During the high workload periods, NMOC staff will have the possibility to automatically process the requests which are below the Local Average Delay 58 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 5- Steps to deploy in operations 1) Fill in Helpdesk Survey for your TWR/FMP 2) Ensure internet connection / web browser compatibility 3) Request secure Network Manager NOP Portal access a. For using the E-Helpdesk in OPS, fill in the request form http://www.eurocontrol.int/network-operations/access-service-request-form Select Type ANSP and Sub-type TWR or FMP In III. PURPOSE OF REQUEST, write “ E-Helpdesk use” and specify clearly if you are ALREADY USING the NOP PORTAL or are a NEW USER . i. If you are already using the NOP PORTAL (with token) your access B2C rights will be updated ii. If you are NEW USER (without token) your access will be created (NOP) More details http://www.eurocontrol.int/network-operations/nm-operational-services-and-products http://w.eurocontrol.int/network-operations/nm-operational-services-and-products-fees 4) Ensure your request comes as soon as possible if you wish to participate in OPT (from 28 th February) and are a NEW USER. 5) If you are ALREADY USING the NOP PORTAL your access will be temporarily upgraded for OPT. 6) Follow ATFCM manual updates and testing sessions 7) Train your staff using external training and Youtube material 59 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 5- Steps to deploy in operations 1) Fill in Helpdesk Survey for your FMP 2) Get insight on B2B use cases and documentation 3) Standard B2B validation process a) Implement locally in my ATFCM tool B2B b) Perform a PRE OPS validation (technical and business) c) Get Certificate for OPS deployment 4) Update local procedures 5) Train your staff using external training and Youtube material 60 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 5- Steps to deploy in operations Deployment Information NOP Portal Network Operations Handbook  Survey  NOP access  Functional Changes  Best Practices  + more info. 61 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B 6- How to use the service and best practices o It is strongly recommended to reduce to the minimum the use of the telephone coordination. o The telephone coordination shall not be used to request TELEPHONE improvements, exclusions from regulations or extensions requests before COBT-20 (exceptional reasons permit TWR to contact afterwards). o It is strongly recommended to use the electronic coordination means (B2B/NOP) to transmit the necessary requests. This has INTERFACE a beneficial effect on the treatment of most urgent requests. o FMP using electronic desk shall choose between B2B or B2C interface and never use the two channels simultaneously. o Review the ATFCM manuals to understand when and where you are entitled to request helpdesk assistance. PROCEDURES o Remember that helpdesk requests have limited possibilities subject to Network capacity constraints . Train your operational staff with the new features and remind the TRAINING procedures and operational best practices. 62 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B NM 23.0 Deployment support Milestones for the HelpDesk deployment nm.releases@eurocontrol.int 63

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B More Information? For further information on the upcoming improvements or any other question related to the Helpdesk Service: nm.releases@eurocontrol.int e-helpdesk@eurocontrol.int 64 nm.releases@eurocontrol.int

FB1019: e-HelpDesk improvements and FB917: DCB Measure proposal via B2B Any questions? 66 nm.releases@eurocontrol.int

Presentation of NM23.0 FB971: NM Airspace model evolution v1.2

FB971: NM airspace data model evolution Impact of the FB  Stakeholder(s) impacted:  Airspace User (Civil)  AO or CFSP  Air Navigation Service Provider (ANSP) Service affected Aeronautical Reporting FB 971 Flight Planning Flow Information/AS Other data Internal Yes computation Data structure Yes User Interface Yes Procedures Training Yes Yes Yes B2B IFPUV Access  Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. 68 nm.releases@eurocontrol.int

FB971: NM airspace data model evolution FB971: NM Airspace model evolution  Background  FB971 constitutes the forth wave of CACD data model adaptations to allow seamless Annex 15 data download from the EAD  Several changes mainly related to the Aerodrome domain have been already rolled out in scope of NM21.5, 22.0 and 22.5 (FBs 862, 893, 957)  The intention is to gradually continue rolling out changes in this and 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  Two CRs impact externals (explained below) 69 nm.releases@eurocontrol.int

FB971: NM airspace data model evolution CR_043842 & CR_045206: Timesheets to allow sunsets and sunrises  Background  In NM22.0 an Aerodrome operations attribute (IFR/VFR/BOTH) was introduced at an aerodrome level. It has an associated time schedule  Corresponding AD Flight Rule restrictions are generated for NM client systems and external users to prevent IFR flights when AD operates only VFR  Content  Timesheets for AD operations, often refer to sunrises (SR) and/or sunsets (SS), sometimes with additional time shift, e.g. from SR-30 minutes to SS+30 minutes  To enable AD download from the EAD, CACD will support such timesheets  CACD will calculate SR/SS times for each AD location  Impact on clients  Impact on the clients who use AD flight rules in Airspace B2B  No impact on the clients who use AD Flight Rule restrictions  CHMI users will see them 70 nm.releases@eurocontrol.int

FB971: NM airspace data model evolution Questions Any questions? 71 nm.releases@eurocontrol.int

Presentation of NM23.0 FB1000: Airspace Data Domain Improvements Evaluate FPL against AIRACs earlier v1.2

FB1000: Airspace Data Domain improvements Impact of the FB  Stakeholder(s) impacted:  Airspace User (Civil)  AO or CFSP  Air Navigation Service Provider (ANSP) Service affected Aeronautical Reporting FB 1000 Flight Planning Flow Information/AS Other data Internal computation Data structure User Interface Procedures Training B2B Yes IFPUV Access Yes  Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. 73 nm.releases@eurocontrol.int

FB1000: Airspace Data Domain improvements New features AO’s & CFSP’s & ANSP’s have today IFPUV access 5 days before the AIRAC switch, meaning they can start validating Flight Plans against the new NM Airspace Data. AIXM NM Airspace data sets available via B2B As from NM 23.0 release: In addition of today’s IFPUV usage:  Flight plan validation via NOP Portal/B2B at ± 15 days before AIRAC switch ;  Flight plan validation via NOP Portal/B2B at n_days before AIRAC becomes effective;  No new token required 74 nm.releases@eurocontrol.int

FB1000: Airspace Data Domain improvements New features 75 nm.releases@eurocontrol.int

FB1000: Airspace Data Domain improvements New features Access to the NM Airspace data for ENV Query and MAP  AO’s & CFSPs & ANSPs will have early access to the NM Airspace Data for next AIRAC and Ad-Hoc AIRAC’s* via CHMI * Ad Hoc AIRAC : 1) ± 35 days before AIRAC becomes effective (two AIRAC’s in advance) 2) n_days before AIRAC becomes effective (Pre- validation projects) 76 nm.releases@eurocontrol.int

FB1000: Airspace Data Domain improvements New features  Access to the NM Airspace data for ENV Query and MAP 77 nm.releases@eurocontrol.int

FB1000: Airspace Data Domain improvements New features NM Airspace data available ± 15 days before AIRAC switch is still subject to NM Airspace data changes (Internal NM validation process, Late publication, …); NM Airspace data available for Ad-Hoc AIRAC(s) will be incomplete in NM system. Only required pre validation NM Airspace Data will be available; The availability of access to the NM Validation / Pre-validation systems depends on the availability of both systems; NM Operational validation / Pre-validation exercise has priority 1 on the usages of the validation / Pre-validation NM systems. 78 nm.releases@eurocontrol.int

FB1000: Airspace Data Domain improvements Questions Any questions? 79 nm.releases@eurocontrol.int

Presentation of NM23.0 FB943: n-CONECT - Airspace New CIREN (CHMI for ENV Coordinators) v1.1

FB943: n-CONECT - Airspace 1- Impact of the FB  Stakeholder(s) impacted:  Air Navigation Service Provider (ANSP)  Other: ENVCOOR Service affected Aeronautical Reporting FB 943 Flight Planning Flow Information/AS Other data Internal computation Data structure User Interface Yes Replaces CIREN Procedures Training B2B Other  Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. 81 nm.releases@eurocontrol.int

FB943: n-CONECT - Airspace 1- Impact of the FB It provides the same There is no need for The FB943 replaces functionality however local installation with improved anymore however the CIREN (CHMI for ENV Coordinators) usability, ergonomy use requires PENS or and a better map internet FMPs and AOs will Existing tokens for continue to use the AMC will continue to the login will be used existing CHMI use CIAM (CIFLO, CITO, CIAO) At the ANSPs, if the FMPs and AO will local documenation New n-CONECT CIREN upgrade at later contained pictures, and current CIREN will be both available releases these pictures shall be updated 82 nm.releases@eurocontrol.int

FB943: n-CONECT - Airspace 2- New features The new application will run from a web browser (Chrome preferred) No local installation required, therefore less maintenance required. Improved Map Better organised more logical User Interface which will probably increase productivity Better use of multiple screens and maps. It provides the possibility to save user queries, name certain maps, and there new way to handle the map dossier New feature: contains Sunset, Sunrise values Is is possible to display elaboration and production braches of airspace data 83 nm.releases@eurocontrol.int

FB943: n-CONECT - Airspace Screenshots 84 nm.releases@eurocontrol.int

FB943: n-CONECT - Airspace Map screenshot with vertical view, level ban and azimuth filter, and with a timeline 85 nm.releases@eurocontrol.int

FB943: n-CONECT - Airspace 3- Background The application was developed as part of n-CONECT programme which aimed to merge all existing NM interfaces It replies to the business need of providing effective services to all stakeholder at a reduced cost Benefits are increased usability and less maintenace, later stage integrated CDM workflow with the stakeholders. It can run literally from everywhere, so the application is portable Possible next steps are: • Inclusion of a workflow (similar to RAD) • Comparaison between elaboration and production data • Better ENV dossier, CACD forms 86 nm.releases@eurocontrol.int

FB943: n-CONECT - Airspace Questions Any questions? 87 nm.releases@eurocontrol.int

Presentation of NM23.0 FB999: Flight Planning Improvements v2.1

FB999: Flight Planning Domain improvements 1- Impact of the FB  Stakeholder(s) impacted:  Airspace User (Civil)  Airspace User (Military)  AO or CFSP  Non-CDM Airport  CDM-Airport  ARO  Air Navigation Service Provider (ANSP) Service affected Aeronautical Reporting FB 999 Flight Planning Flow Information/AS Other data Internal Yes computation Data structure User Interface Procedures Yes Training Yes B2B Yes Other 89 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 1- Impact of the FB CR_044325 - Prevent multiple flight planning Flight Plan Originators (AFTN/SITA/NOP/B2B) should be aware of the new error that will be returned if they file two flights that overlap with the same aircraft registration. CR_044418 - Remove the special overlap association logic for Type of Flight ‘X’ Flight Plan Originators who submit flight plans with Type of Flight ‘X’ should not expect the specific flight association rule that used to be applied in IFPS. CR_044506 - Reduce output of IFP/IFPSROUTEMOD in FPLs ANSPs that receive FPLs that contain the IFP/IFPSROUTEMOD indicator should understand the new rules for the inclusion in IFPS. CR_043145 - Improve logic for associating RQP to multiple FPLs ANSPs that receive FPLs that contain the IFP/IFPSROUTEMOD indicator should understand the new rules for the inclusion in IFPS. 90 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_044325 - Prevent multiple flight planning  NM has received reports that some AUs file multiple flight plans (with different ARCIDs) in an attempt to get a CTOT close to EOBT.  To prevent this, it has been decided to implement a mechanism in IFPS to prevent multiple flight plan submissions.  Note: FB977 REROUTING EVOLUTIONS:  AUs (Airspace Users) have the possibility to assess the CTOT prior filing of the FPL (NOP Protected IFPUV Validate/Try). 91 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_044325 - Prevent multiple flight planning  With this change, IFPS will reject any FPL that is submitted that matches a valid FPL with same  REG  ADEP  ADES  And overlapping flying period between the two FPLs.  New error: EFPM321: FPL WITH SAME REG MARKINGS AND OVERLAPPING FLYING PERIOD EXISTS:WOO86P EDDF1550 EBBR0035 DOF/181225. 92 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_044325 - Prevent multiple flight planning VALID FPL IN IFPS NEW SUBMISSION MATCHING REG, ADEP, ADES, and time overlap, with a valid FPL in IFPS (FPL- WOO86 -IS -A333/H-SDE1E2E3FGHIJ4J5RWXYZ/LB1D1 (FPL -WOO86P -IS - EDDF1550 -A333/H-SDE1E2E3FGHIJ4J5RWXYZ/LB1D1 -N0470F180 SOBRA Y180 BITBU Y181 GOPAS - EDDF1520 N852 LNO -N0470F180 SOBRA5P SOBRA Y180 BITBU - EBBR0035 EHAM Y181 GOPAS N852 LNO -PBN/A1B1C1D1L1O1S1S2 NAV/T1T2 RNP2 - EBBR0035 EHAM DAT/1PDC REG/WOOPS ) -PBN/A1B1C1D1L1O1S1S2 NAV/T1T2 RNP2 DAT/1PDC REG/WOOPS ) EFPM321: FPL WITH SAME REG MARKINGS AND OVERLAPPING FLYING PERIOD EXISTS:WOO86 EDDF1550 EBBR0035 DOF/181225 93 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_044418 - Remove the special overlap association logic for Type of Flight ‘X’  For historical reasons, Type of Flight ‘X’ (mostly training flights) have had a specific flight (overlap) association logic in IFPS.  With NM 23.0 we will remove this specific treatment and Type of Flight ‘X’ will be treated the same way as other flight types (Scheduled flights ‘S’, non-scheduled ‘N’, General aviation ‘G’ or Military flights ‘M’). 94 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_044418 - Remove the special overlap association logic for Type of Flight ‘X’ NEW SUBMISSION: VALID FPL IN IFPS Old IFPS behaviour; second FPL = ACK . (FPL- WOOPS -IG (FPL- WOOPS -I X -DA42/L-SDGHY/S -DA42/L-SDGHY/S - EBAW1230 - EBOS1245 -N0140F060 NIK L179 COA -N0140F060 COA L179 NIK - EBOS0030 EBAW -EBAW0030 EBOS -0) -0) NEW SUBMISSION: IFPS behaviour with NM 23.0: second FPL = REJ . (FPL- WOOPS -I X -DA42/L-SDGHY/S - EBOS1245 -N0140F060 COA L179 NIK -EBAW0030 EBOS -0) EFPM217: FPL WITH SAME ARCID AND OVERLAPPING FLYING PERIOD EXISTS:WOOPS EBAW1230 EBOS0030 DOF/190225 95 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_044506 - Reduce output of IFP/IFPSROUTEMOD in FPLs  Currently, the presence of IFP/IFPSROUTEMOD in a FPL output is the result of:  A manual insertion by an IFPS staff or  An automatic insertion by IFPS  Automatic insertion reasons:  Speed changed from knots to Mach at oceanic entry point  DCT replaced by co-located ATS route designator  SID/STAR designator inserted for AD that require SID/STAR in FPL  IFPS elegant output feature (removing duplicate ATS route designators)  Etc… 96 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_044506 - Reduce output of IFP/IFPSROUTEMOD in FPLs  Large number of flagged FPLs is causing some issues:  AOs have to identify what has been modified.  ANSP: at least one ANSP introduced a warning to their controllers when IFPSROUTEMOD was present.  In NM 23.0, automatic insertion of the IFP indicator IFPSROUTEMOD will be disabled . 97 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_044506 - Reduce output of IFP/IFPSROUTEMOD in FPLs  Only occurrences will be by manual insertion by an IFPS staff (when IFPSRA is present in the FPL or after phone coordination).  Presence of the indicator means that the trajectory has been laterally and/or vertically modified between first and last en-route point.  AOs and ANSPs should understand the new rules for the insertion of the IFP indicator: IFPSROUTEMOD. 98 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_043145 – Improve logic for associating RQP to multiple FPLs  It is recommended to send RQP with the EOBT and the DOF:  (RQP-ABC123-EBBR-LFML-0)  (RQP-ABC123-EBBR 1200 -LFML- DOF/190225 )  This is used to associate the RQP to the correct FPL (when multiple FPLs with same ARCID, ADEP, ADES exist) .  Currently when a RQP matches multiple FPLs, it is passed for manual processing.  The new logic will avoid the manual processing and improve the quality of the replies to RQP messages. 99 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_043145 – Improve logic for associating RQP to multiple FPLs  Upon reception of an RQP matching multiples FPLs:  It will only associate to those FPLs valid in IFPS than have an EOBT up to 6 hours in the future when compared to the IFPS system time.  If all matching FPLs have an EOBT later than 6 hours when compared to the IFPS system time, then the RQP shall associate to all of them. 100 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_043145 – Improve logic for associating RQP to multiple FPLs  FPL: ABC123 EBBR 1100 LFML DOF/190225  FPL: ABC123 EBBR 1700 LFML DOF/190225  @1145: (RQP-ABC123-EBBR-LFML-0)  Any valid FPL with EOBT up to 1745 (1145+0600) → 2 FPLs matching  In response to the RQP, IFPS sends automatically both FPLs. 101 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_043145 – Improve logic for associating RQP to multiple FPLs  FPL: ABC123 EBBR 1100 LFML DOF/190225  FPL: ABC123 EBBR 1800 LFML DOF/190225  @1145: (RQP-ABC123-EBBR-LFML-0)  Any valid FPL with EOBT up to 1745 (1145+0600) → 1 FPL matching  In response to the RQP, IFPS sends automatically the FPL with EOBT1100. 102 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 2- New features  CR_043145 – Improve logic for associating RQP to multiple FPLs  FPL: ABC123 EBBR 1800 LFML DOF/190225  FPL: ABC123 EBBR 1800 LFML DOF/1902 26  @1145: (RQP-ABC123-EBBR-LFML-0)  Any valid FPL with EOBT up to 1745 (1145+0600) → 0 FPL matching before 1745, but 2 matching later than 1745, then:  In response to the RQP, IFPS sends automatically both FPLs, the one of today and the one for tomorrow. 103 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 3- Background – Why  Short background of the FB:  Change IFPS behavior as requested by the EUROCONTROL NM Stakeholders. 104 nm.releases@eurocontrol.int

FB999: Flight Planning Domain improvements 4- Questions Any questions? 105 nm.releases@eurocontrol.int

Presentation of NM23.0 FB972 – ASM Advanced FUA process improvements v2.0

FB972: ASM - Advanced FUA process improvement 1- Impact of the FB  Stakeholders impacted:  Airspace Manager (AMC) Service affected Aeronautical Reporting FB 972 Flight Planning Flow Information/AS Other data Internal Yes computation Data structure User Interface Procedures Training B2B Other  Internal computation: Change in the way the various parameters exposed to externals (eg. CTOT) are computed. 107 nm.releases@eurocontrol.int

FB972: ASM - Advanced FUA process improvement 1- Impact of the FB CR_ID Title  way of working CR_036912 CDR expansion to consider RELATED/CROSSING/OFFLOAD routes vertical limits  CR_042633 Complex FUA Restrictions Systems CR_042424 Restriction Grouping CR_041209 FUA KPIs Updated Reports Impact of the FB on externals: Current procedures NO Way of working NO Systems YES CHMI; CIAM; CACD; 108 nm.releases@eurocontrol.int

FB972: ASM - Advanced FUA process improvement 2- New features CDR expansion to consider RELATED/CROSSING/OFFLOAD CR_036912 routes vertical limits Background User Requirement New Features Currently, automatic closure of the The User shall be able to trigger The CDR Route can be closed or routes affected by an RSA allocation RELATED/CROSSING/OFFLOAD opened for the complete vertical limits only closes the affected routes within routes through CDR expansion as they of the Route CDR definition, the vertical limit of the allocation. In are specified, not limiting the update to independent of the vertical limits of the certain situations routes above and/or the vertical limits of the allocated RSA. RSA allocation. below the allocated range should also be closed to guarantee the flights’ safety 109 nm.releases@eurocontrol.int

FB972: ASM - Advanced FUA process improvement 2- New features • If the request is "expand above", the expansion will be until the upper limit of the Route CDR definition but taking the lower limit of the RSA allocation into account. • If the request is "expand below", the expansion will be until the lower limit of the Route CDR definition but taking the upper limit of the RSA allocation into account. 110 nm.releases@eurocontrol.int

FB972: ASM - Advanced FUA process improvement 2- New features CR_042633 Complex FUA Restrictions Background User Requirement New Features FUA restrictions are often complex • The NM ENV system shall support • If the FUA Restriction Group is and in order to effectively define the the maintenance and validation of activated, it will automatically required constraint several sub- Complex FUA Restrictions by activate all FUA Restrictions restrictions are needed. combining them in a "FUA" belonging to the group. Restriction Group. • If any FUA Restriction belonging to • The NM ENV and CIAM systems the group is activated, it will shall guarantee that all FUA automatically activate all FUA Restrictions belonging to a FUA Restrictions belonging to the group Restriction Group are activated / including the FUA Restriction de-activated together. Group itself. 111 nm.releases@eurocontrol.int