NETWORK MANAGER RELEASE NOTES

EUROCONTROL Network Manager

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014

NETWORK MANAGER RELEASE NOTES

PLANNED FOR IMPLEMENTATION IN 2013-2014

Edition N°: 3.5 http://www.eurocontrol.int/content/network-management

Edition date: 20/11/2013

©2013 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

©2013 The European Organization for the Safety of Air Navigation (EUROCONTROL). This document is published by EUROCONTROL for information purposes. It may be copied in whole or in part, provided that EUROCONTROL is mentioned as the source and the extent justified by the non-commercial use (not for sale). The information in this document may not be modified without prior written permission from EUROCONTROL. Edition No: Edition Issue date: File name: Number of pages:


3.5 20/11/2013 Network Manager Release Notes planned for implementation for 2013-2014 59

Edition 3.5 [email protected] ©2013 The European Organisation for the Safety of Air Navigation (EUROCONTROL) p.i



Table of Contents 1.

INTRODUCTION

4

2.

RELEASES CONTENT

5

2.1. 2.2.

3.

Browser compatibility Operating System compatibility

6 6

EVOLUTION PROGRAMMES

7

3.1. Network Operations Management and Monitoring 3.1.1. Programme NOS-01: Coordinated process ASM-ATFCM 3.1.2. Programme NOS-02: Airports interface with Network Operations 3.1.3. Programme NOS-43: ATFCM Planning 3.1.4. Programme NOS-45: Dynamic ATFCM 3.2. ATM Gateway to Network Operations 3.2.1. Programme NOS-21: Free Route Airspace Network-wide 3.2.2. Programme NOS-44: Flight Plan interoperability 3.3. Network Information Management and Sharing 3.3.1. Programme NOS-03: Airspace data repository 3.3.2. Programme NOS-24: Demand Data Repository Phase 2 3.3.3. Programme NOS-41: Network Operations Plan 3.3.4. Programme NOS-48: NM-FOS Prototype validation 3.4. Support to pan-European functions 3.4.1. Programme NOS-12: Call-Sign Similarities (CSST) 3.4.2. Programme NOS-14: Aircraft Identification 3.4.3. Programme NOS-42: Alignment to Performance framework

4.

DEPLOYMENT

7 7 7 7 7 8 8 8 8 8 8 8 8 9 9 9 9

10

4.1. Release 17.0 migration 4.1.1. OPT session 4.2. Release 17.5 migration 4.2.1. Presentation of NM17.5 to externals 4.2.2. OPT session 4.3. Release 17.5.2 migration 4.4. Validation exercises

10 10 10 10 10 11 12

5.

14

NETWORK MANAGER EVOLUTIONS

5.1. Introduction 5.2. Release 17.0 5.2.1. NOS-01 - Coordinated Process for ASM/ATFCM 5.2.2. NOS-03 - Airspace Data Repository - Phase 1 5.2.3. NOS-12 - Call-Sign Similarity (CSST) 5.2.4. NOS-14 - AirCraft IDentification 5.2.5. NOS-21 - Free Route Airspace Network-wide 5.2.6. NOS-41 - Network Operations Plan 5.2.7. NOS-42 - Alignment to Performance framework 5.2.8. NOS-43 - ATFCM Planning 5.2.9. NOS-44 - Flight Plan interoperability 5.2.10. NOS-45 - Dynamic ATFCM 5.2.11. NOS-48 - NM-FOS Prototype validation 5.2.12. ATFCM Domain 5.2.13. Flight Planning Domain 5.2.14. Airspace Data Domain 5.2.15. Correction and Tuning 5.3. Release 17.5 Edition date: 20/11/2013

14 16 16 17 18 19 20 20 22 23 24 27 28 28 29 30 32 33

Edition 3.5 [email protected] ©2013 The European Organisation for the Safety of Air Navigation (EUROCONTROL) p.1



5.3.1. NOS-01 - Coordinated Process for ASM/ATFCM 5.3.2. NOS-03 - Airspace Data Repository - Phase 1 5.3.3. NOS-12 - Call-Sign Similarity (CSST) 5.3.4. NOS-14 - Aircraft Identification 5.3.5. NOS-41: Network Operations Plan 5.3.6. NOS-42: Alignment to Performance framework 5.3.7. NOS-44: Flight Plan interoperability 5.3.8. NOS-45: Dynamic ATFCM 5.3.9. ATFCM Domain 5.3.10. Airspace Data Domain 5.3.11. Correction and Tuning 5.3.12. Technical Blocks 5.4. Release 17.5.2 5.4.1. NOS-01 - Coordinated Process for ASM/ATFCM 5.4.2. NOS-41: Network Operations Plan

33 33 34 35 36 38 39 39 42 46 47 49 51 51 52

6.

54

ABBREVIATIONS





Document Changes Record Ed. 1.0

Status Release

Date 03/08/2012

2.0

Release

25/01/2013

2.1 2.1.1 2.2

Release Release Release

04/02/2013 05/02/2013 26/02/2013

2.3

Release

11/03/2013

2.3.1 2.3.2 3.0


12/03/2013 15/03/2013 07/05/2013

3.1

Release

25/06/2013

3.1.1

Release

01/07/2013

3.2

Release

07/08/2013

3.3

Release

10/09/2013

3.4 3.4.1 3.5


08/10/2013 21/10/2013 20/11/2013


Reason for change Deployment information added, Release notes information updated, detailed migration plan added. Additional information on OPT, precision on B2B deployment. Typo in the year §4.2.2 Migration dates updated (§4.1). CSST migration date updated (§4.1). B2B migration dates clarified. Adaptations in the Release Migration dates (§4.1) Adaptations in the Release Migration dates (§4.1) Information on NM17.5 Additional information in particular on FB522, FB598, TB100, TB138. Information on the “Release presentation to externals” and OPT. Updated information on ADR Programme and on OPT session content. Additional information on some Functional Blocks (in particular FB598). NM17.5 migration information. NM17.5.2 initial content. NM17.5 OPT postponed by one day (16/09/2013) NM17.5 migration information updated Additional information on NM17.5.2 Additional information on browsers compatibility (§2.1) CSST migration dates in NM17.5 updated in pink underlined (§4.2) Information on NM17.5.2 migration and content



1.


INTRODUCTION This document describes the new or modified functions that are delivered by the Network Manager as part of the Network Manager software Releases. The objective of this document is to provide customers of the Network Manager Services with advance notice of modifications in order to anticipate any impact upon their operational procedures and/or systems. The Network Manager Releases include many changes arising from different sources and coordinated through the Operations Coordination Group and its sub-groups. It allows the implementation of new functionalities to cope with Network Manager Directorate Business plans and in particular with DMEAN objectives. The Network Manager Release Notes document is organized as a rolling document describing the functions currently under development for future releases. Other functions considered for possible development but without reaching yet a maturity status allowing their presentation are not included in this paper. The Release Notes document contains 3 main parts: • The “Evolution Programmes” part summarizing the main development Programmes. • The “Deployment” part providing precise information on the Release deployment schedule. • The “Network Manager Evolutions” part listing the delivered evolutions per Release and Functional Block. It contains also information on the deployment of the Functional Blocks that was previously stored in the Deployment Plan document. Important: The Release Deployment Plan document has been integrated into the current Release Notes document in order to centralize in a single document all information related to the Release content. The Release Deployment Plan will thus no more be edited. The current document is available at: http://www.eurocontrol.int/lists/publications/network-operations-library?type=3317&keyword= To receive automatically by eMail the new versions of the Release Notes, please register at: http://www.eurocontrol.int/network-operations/self-registration-form (Choose "Subscribe to receive e-mail notifications when the NM Release Notes are updated" in the field “purpose of the request”). Any questions or comments regarding the Releases shall be sent at: [email protected]




2.


RELEASES CONTENT

Programme

Functional Block

NOS-01 - Coordinated Process for ASM/ATFCM §3.1.1 FB283 Network Impact Assessment FB601 ASM monitoring FB594 ASM Monitoring (part2) NOS-03 - Airspace Data Repository - Phase 1 §3.3.1 FB556 eRestrictions (including FPR) FB569 SDO Download - EAD / CACD Comparison FB572 Prepare Ops Validation with ASM Tools FB555 eRestrictions (eRAD) NOS-12 - Call-Sign Similarity (CSST) §3.4.1 FB568 CSST C&T FB588 CSST C&T NOS-14 - AirCraft Identification §3.4.2 FB537 Post-Deployment CCAMS C&T - 2 FB575 Post-Deployment CCAMS C&T - 3 NOS-21 - Free Route Airspace Network-wide §3.2.1 FB526 FRA Improvements NOS-41 - Network Operations Plan §3.3.3 FB557 NM customisable platform for all users FB584 Updating the NOP, CHMI and Login page banners Real-time network situation displays FB560 Updating the CFMU URLs FB592 FB605 EVITA Phase II for Volcex exercise FB591 NOP access to event information consolidation - Phase 1 NOS-42 - Alignment to Performance framework §3.4.3 FB456 Alignment to Performance framework FB589 Support to flight efficiency - NM17.5 NOS-43 - ATFCM Planning §3.1.3 FB360 Scenario Data management NOS-44 - Flight Plan interoperability §3.2.2 Increase planned flight trajectory consistency between AO and FB460 NM FB499 Use of AO 4D profile - Prototype FB554 FIXM Strategy in SESAR FB522 Use of AO 4D profile -shadow exercise NOS-45 - Dynamic ATFCM §3.1.4 FB533 Support TTA Trial (May 2013) FB140 STAM Decisions promulgation (proto) FB229 Traffic Complexity NOS-48 - NM-FOS Prototype validation §3.3.4 FB544 Initial Flight Object Prototype - 1

NM 17.0

NM 17.5

NM 17.5.2

§5.2.1 §5.3.1 §5.4.1 §5.2.2 §5.2.2 §5.2.2 §5.3.2 §5.2.3 §5.3.3 §5.2.4 §5.3.4 §5.2.5 §5.2.6 §5.2.6

§5.3.5 §5.4.2 §5.2.7 §5.3.6 §5.2.8 §5.2.9 §5.2.9 §5.2.9 §5.3.7 §5.2.10 §5.3.8 §5.3.8 §5.2.11

ATFCM Domain FB524

ATFCM Domain improvements

FB598

ATFCM Domain improvements

Flight Planning Domain FB550 Airspace Data Domain FB527 FB528 Edition date: 20/11/2013

§5.2.12 §5.3.9

Reduce manual flight plan processing in IFPS

§5.2.13

CIAM Improvements

§5.2.14

Airspace Data Domain improvements

§5.2.14


EUROCONTROL Network Manager FB581


Airspace Data Domain improvements

§5.3.10

Correction and Tuning FB154

Reporting C&T for Release 17

FB536

Provision of Departure data - 8

§5.3.11

FB585

Reporting C&T for Release 17.5

§5.3.11

TB100

NOP map technology

§5.3.12

TB138

NOP HMI Customisation

§5.3.12

§5.2.15

Technical Blocks

[Update v2.0]: FB560 (Real time network situation displays) was removed from Release 17.0; its features have been included in the Technical Block TB100 (Map display for the NOP) planned for Release 17.5. [Update v3.1]: FB560 (Real-time network situation displays) has been replaced by the Technical Block TB100 (NOP map technology). FB592 (Updating the CFMU URLs) has been postponed to NM18.0. [Update v3.2] NM17.5.2 will be deployed in December 2013 (c.f. §4.3). It has a limited scope: • FB594 with the continuation of FB601 (impact only internal NM). • FB591: Provide NOP access to event information for the training session (not in the operational environment).

2.1.

BROWSER COMPATIBILITY The deliverables of NM17.5 that require a browser (e.g. the NOP) are tested with the following browsers: • Internet Explorer version 9 and 10. • FireFox version 20 and 21. Other types/versions of browsers might encounter functionality and/or performance issues. For Portal to work on Internet Explorer 9 it is necessary to un-tick the two check boxes "Display intranet sites in Compatibility View" and "Display all websites in Compatibility View". The user can find these settings in the "Compatibility View Settings" dialogue, available under Tools -> Compatibility View Settings. Regarding FireFox, by default and as a safety feature, this browser forbids scripts to raise windows and, subsequently, the Portal feature of bringing windows to the front cannot work. To overwrite this safety measure one has to open the options dialogue by selecting the menu entry Tools -> Options, select the Content tab, click on the Advanced button next to "Enable JavaScript" and ensure that the check box "Raise or lower windows" is selected.

2.2.

OPERATING SYSTEM COMPATIBILITY As from NM17.5, the CHMI will be compatible with Windows 7 and Windows XP.




3.


EVOLUTION PROGRAMMES You will find below a summarized description of each Programme that the Network Manager developments are serving. They are grouped in 4 main Evolution Areas.

3.1.

NETWORK OPERATIONS MANAGEMENT AND MONITORING

3.1.1.

Programme NOS-01: Coordinated process ASM-ATFCM The “Coordinated process ASM-ATFCM” Programme provides the frame for the further evolutions of the deliverables provided by the ASM Improvements Initiative that has introduced more dynamicity of the ASM/ATFCM processes during the last four years. The Programme will aim at: • Introducing performance driven operations based on the management of Airspace Configurations. • Providing processes that support the use of more dynamic and flexible elements. • Describing a seamless, CDM based process with an advanced real time management of Airspace Configurations as well as a continuous sharing of information among all ATM partners enabled by advanced technology. The main Lines of Improvement of the Programme are: • Airspace Configuration Definition and Operational Deployment. • A Collaborative Decision Making Process (ASM/ATFCM/ATC integration). • The Rolling Process. • ASM solutions to improve network performance. • ASM system support and data management. • ASM post ops and performance planning.

3.1.2.

Programme NOS-02: Airports interface with Network Operations Airports need to be seen as being a part of the whole ATM system in a “gate-to-gate” environment. As the tactical manager of the total network load, ATFCM has to collaborate with air traffic control, aircraft operators, and airports in a genuine partnership. The Programme aims at ensuring an efficient interface between the concerned partners through swift and effective collaborative decision-making and through the provision of the required data when and where they are needed. The Programme also covers the monitoring of airport slots (AMON) and the management of critical events leading to a better utilization of limited available capacity.

3.1.3.

Programme NOS-43: ATFCM Planning Covering the flow and capacity management several months before the operations, the strategic process will be improved in particular by ensuring the relation with longer-term planning (Airspace Design & Capacity Planning). The roles, procedures and tools used in the NMOC will be refined for managing efficiently ATFCM scenarios, including the elaboration, validation, negotiation and dissemination of ATFCM measures.

3.1.4.

Programme NOS-45: Dynamic ATFCM The responsibilities and supporting procedures between NM and the ANSP for the execution of Tactical ATFCM are currently under review to cope with the evolutions of the roles and responsibilities in ATFCM. The Programme will also improve the support to the NM stakeholders (helpdesk, AOLO, etc.) and the access to the NM services in particular for the FMPs (CIFLO, Web services, etc.) In order to close the gap between ATC and ATFCM, Short-Term ATFCM Measures (STAM) shall be developed requiring dynamic coordination between more than one ACC, the AOs and NM. The objective of STAMs is to prevent sector overloading, whilst reducing delays, by using air traffic flow management techniques, close and during real time operations.





Even if some STAMs measures already exist, they are often limited to solving specific local problems and they do not consider the Network. No standardized tool or procedures exist today to manage STAMs and the role of NM within STAMs processes must be clarified. The awareness on flight progress shall be improved by getting additional sources of flight data from the Aircraft Operators and the service providers, and by sharing the consolidate information with the partners.

3.2.

ATM GATEWAY TO NETWORK OPERATIONS

3.2.1.

Programme NOS-21: Free Route Airspace Network-wide The aim of the Programme is to adapt the FPL processing systems and processes to cope with the route network evolutions impacting the NM services, such as night DCTs, Week-end DCTs or Free Route Airspace Initiatives.

3.2.2.

Programme NOS-44: Flight Plan interoperability This Programme will enhance the flight plan data exchange between AOs/CFSPs and the Network Manager during the pre-filing phase, in order to improve the accuracy and consistency between 4D flight trajectories maintained by the different stakeholders. It will re-enforce the validity and consistency of the flight trajectory with the airspace availabilities and constraints, at least until the end of the pre-flight phase. The Programme will prepare for the further transmission by NM of acquired 4D trajectory information to ATC/ANSP. It will also pave the way to the implementation of the SESAR trajectory concept.

3.3.

NETWORK INFORMATION MANAGEMENT AND SHARING

3.3.1.

Programme NOS-03: Airspace data repository The objective of ADR Programme is to provide a common and consistent source of airspace information containing both static and dynamic elements that will support the ASM/ATFCM/ATC collaborative process. The Programme allows the use of electronic information by external systems (e.g. the electronic RAD message and shortly the eAMI, informing airspace users on the changes made to the airspace). The following ADR evolutions will electronically publish live updates on airspace data. It should be noted that ADR project has been re-scoped in the frame of Centralised Services. Accordingly the EAD data download to CACD (initially planned for NM18) is no longer planned. However manual data comparison between the two systems will continue: a data comparison tool (CASTAR) will produce reports to ease the manual data alignment between the two systems.

3.3.2.

Programme NOS-24: Demand Data Repository Phase 2 The objective of the DDR is to allow airspace users to provide their intentions to meet ATM planning requirements: the Traffic Demand will gradually be refined by integrating additional flight intentions (OAG, airport slots, RPLs, FPLs, etc.), allowing predictions based on actual intentions and/or historical operations. The scope of the DDR will vary from a few years until a few hours before the operations.

3.3.3.

Programme NOS-41: Network Operations Plan The NOP aims at building a consolidated interactive view of the network situation that incorporates the existing information and user requests on traffic demand and capacity plans, identifying bottlenecks and presenting the ATFCM and ASM measures foreseen to counterbalance them. The NOP will result from the integration of interdependent data including flight intentions, status of airspace, capacity, airport data and meteorological forecasts. NOP will also be updated taking into account the actual traffic situation and real time flow and capacity management.

3.3.4.

Programme NOS-48: NM-FOS Prototype validation The NM-FOS addresses the systems and operations evolution towards interoperability/flight data sharing amongst all partners involved in the flight. The fundamental idea is that a single logical entity, the FO (Flight Object) is kept up to date by all parties sharing information about a flight. As





such, all systems have the most up to date, accurate and consistent view of the flight data and plans. This single logical FO is physically distributed over a network of ‘FO Servers (FOS)’, each FOS being associated with an FDPS. Each FOS holds physical copies of the FOs of interest to its clients. The network of FOSs, not the clients, is responsible for ensuring that the different physical copies of the FO are kept consistent. In the pre-departure phase, the FO enables Communicating and Synchronising flight data and agreed trajectories (including strategic and tactical constraints, e.g. TSA closure/opening, TTA/TTO, etc.). When the flight is airborne, up to date FO improves not only the Network view available to controllers, but also allows ATC to participate to the implementation of ATFCM measures. In other words the FO is the opportunity for a better integration of ATFCM and the ATC. The FOS is an enabler not only for the Time Based Operations but also for further evolution to Trajectory Based Operations.

3.4.

SUPPORT TO PAN-EUROPEAN FUNCTIONS

3.4.1.

Programme NOS-12: Call-Sign Similarities (CSST) Air-Ground communication safety events are one of the biggest ATM safety priorities, forming 23% of all ATC safety reports. Today, 21% of all NM flights involve callsign similarity. Reliable mitigation for the risk imposed by similar callsigns (like 527F 527D or 361M 369M) can be achieved. The NM has established a Call Sign Management Cell (CSMC) to develop a centralized Service. One key element in providing the Service is the publication of agreed Call Sign Similarity Rules. These Rules are at the heart of the Call Sign Similarity Tool (CSS Tool). Development of the CSS Tool and its specifications by EUROCONTROL is closely coordinated with a Call Sign Similarity User Group (CSSUG), which includes representations from AOs, ANSPs and other aviation organizations (e.g. ICAO and IATA).

3.4.2.

Programme NOS-14: Aircraft Identification In line with PC/32 decision to organise unambiguous and continuous identification of aircraft through down linked aircraft identification for IFR GAT in ECAC, the three elements CCAMS, ORCAM and Mode S ELS have been brought together to form one Programme named AirCraft Identification Programme. The current ORCAM system is reaching its limits and SSR Code Conflicts already occur regularly today. The final goal is to have Mode S operational in the whole area but it is not being implemented fast enough to solve the problems at short term. Therefore CCAMS is implemented in some but not all states to overcome those shortages on a temporary basis, until Mode S is implemented everywhere.

3.4.3.

Programme NOS-42: Alignment to Performance framework The aim of this Programme is to align NM post-ops services (including datawarehouse and NMIR) to the NM performance IR. This includes a wide variety of activities such as the adaptation of databases, modification of interfaces graphical identity, new reports following users’ requests, etc.




4.


DEPLOYMENT Deployment Plan

2013 J

F

M

A

M

J

J

2014 A

S

O

N

D

J

F

M

A

M

J

J

A

S

O

N

D

Release 17.0

OPT Start of migration

13

Release 17.5 Presentation of NM17.5 to externals

15

OPT

22

Start of migration Release 17.5.2

5 3

Start of Migration

4.1.

RELEASE 17.0 MIGRATION The migration of NM systems from NM16.5 to NM17.0 took place from the 13/03/2013 to the 19/03/2013.

4.1.1.

OPT session An OPT session took place on the 6th and 7th of February 2013.

4.2.

RELEASE 17.5 MIGRATION The migration of NM systems from NM17.0 to NM17.5 will take start on the 22nd of October 2013 and will last around one week. Additional informational will be provided two months before the start of the migration.

4.2.1.

Presentation of NM17.5 to externals An audio conference took place on the 15th of July 2013. The aim was to present each FB or TB of the NM17.5 that would impact external users. Slides and recording of the presentation are available at: http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/releasedeployment/nm17-5-toexternals1-1.pdf

4.2.2.

OPT session An OPT session is a testing session on specific Functional Blocks that belong to the new Release. It always involves externals and is done to consider eventual impacts on actual operations. The OPT will take place from the 16/09/2013 to the 15/10/2013; it will cover: • TB100: NOP map technology (replace FB560: Real-time network situation displays) • FB229: Traffic Complexity • FB598: ATFCM Domain improvements (3/5) (Cherry Picking) • TB138 NOP HMI customisation • CHMI • B2B Registration is mandatory to get access to the OPT. To register, please contact [email protected].




4.3.


RELEASE 17.5.2 MIGRATION The migration to NM17.5.2 will start take place on the 5th 3rd of December 2013 during the usual maintenance window of the datawarehouse system. The only system impacted by the migration will be the datawarehouse (BIS/NMIR). No new version of CHMI will be delivered with the NM17.5.2. No OPT for NM17.5.2 will be organised.




4.4.


VALIDATION EXERCISES

May 2013

The following table provides the list of planned SESAR validation exercises. This list is still subject to modifications. SESAR Test FB Title Description WP Platform First step is to use current facilities of exchanging simulation between NMOC and external Network Impact FB360 NM OPS candidates in order to improve the pre-tactical Assessment trial process such as during the FABEC trial. No Departure prioritisation 7.6.4 TBD Dflex

May 2013

FB533

Date JanuaryFebruary 2013

FAIR STREAM Part I

TTA at congested location sent to aircrew and local Traffic Managers

SJU / 13.2.3

NMVP V3

7.6.2 / 13.2.1

TBD

7.6.5 / 13.2.3

NM OPS

June 2013

FB544

VP-659 - FOS trial I

The scope of this trial covers the communication of ETOs/TOs. It does not involve communication with the AOC but rather the exchange of information with the IOP ANSP. The NM FOS will exercise the role of FDU and FDC.

June 2013

FB533

VP-632 - TTA Ops Trial

The purpose is to assess the improvement in the flight handling at the airport when the predictability of the arriving flights is improved.

November 2013

FB499 FB522

VP-616 - Extended FPL validation Exercise

This trial exercise is a continuation of VP-311, where extended flight plans data are exchanged via Web Services

September 2013

FB533

FAIR STREAM Part II

February 2014

FB570

Newbridge - TTA supported by AOC data

March 2014

FB284

Interops with ASM Tools for real-time

March 2014

FB514

Crisis Management Ops Trial

Second part of FAIRSTREAM (the date will rely on the output of Part I) The trial is an extension of the TTA trial (May 2013) with post-departure trajectories received by the AOs from their airborne flights, are sent to the NM (e.g. via APR) to capture the predicted trajectories in the network view Enabler towards ASM/ATFCM coordination until the real-time activation of airspaces or routes: the purpose is to compare the performance of the network using the today’s procedures with the performance when more accurate data are used until the real time airspace activation status. Validate the use of Dynamically shaped reference locations

April 2014

No

OAT FPL

Validation of the OAT FPL

May 2014

FB140

VP-522 - STAM Ops Trial II

December 2014 January 2015

FB571

FOS trial II with TTA


Extension of the first STAM trial (Nov 2011) with enhanced processes and facilities for coordinating and applying STAM measures, new types of measures (on flows) and TTA update process The Operational Scenario covers the communication of planned measures (e.g. TTO/TTA) and derived measures (e.g. CTOT) to relevant actors as targets, aiming to ensure that the execution of the flight is performed in line with the plan. During this trial it is intended that the NM FOS will also perform the role of FDMP.

SJU / 13.2.3

NMVP V3 NMVP V2 validatio n NMVP V3

7.6.5 / 13.2.3

NMVP V3

7.5.2 / 13.2.1

TBD

7.6.2 / 13.2.1

7.6.5 / 13.2.1 7.6.2 / 13.2.1

TBD TBD

7.6.5 / 13.2.3

NMVP V3

7.6.2 / 13.2.1

TBD








5.

NETWORK MANAGER EVOLUTIONS

5.1.

INTRODUCTION Each Functional Block is described in a table with the following fields. Following consultations with users in March 2013, the categories have been reviewed for NM17.5 and re-structured. All descriptions are focused from an external NM point of view. FBxxx: Number and name of the Functional Block (optional) Internal NM “Internal NM” means that the Functional Block has no direct impact for externals NM users (on procedures, interfaces or systems). The Functional Block may have an indirect impact by improving the quality of the service delivered by NM. The categories of NM Users which are impacted by the new features of the Functional Block: U1. Flow Manager (FMP) U2. Airspace Manager (AMC) U3. Airspace User (Civil) U4. Airspace User (Military) U5. ENV data provider U6. Management (eg crisis management, performance management) Users impacted U7. Post-ops analyst U8. AO or CFSP U9. CAA, EASA U10. Airport U11. ARO U12. Internal NM U0. Other (specify): The NM application(s) or service(s) that will be impacted by the Functional Block: A1. CHMI A2. CIFLO, CIAO A3. CIAM A4. CACD A5. Flow management systems (Predict, ETFMS) A6. FPL (IFPS) Application impacted A7. Datawarehouse (NMIR) A8. CCAMS A9. CSST A10. NOP A11. B2B A12. ASM Tools A13. NMVP A0. Others (specify): Objective Operational objectives of the Functional Block. Description Description of the main features delivered to external NM users. Impact Technical or operational impact the Functional Block may have on the




NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 external users. I0. No impact. I1. Impact on procedures. I2. Impact on Man-Machine interface. I3. Impact on clients’ systems.

Impact description Service reference

Safety assessment

Operational deployment plan

Users’ validation Documentation publication Training sessions


Description of the impact for the external users. Hyperlink toward the NM activity(ies), service(s) and product(s) that will be impacted by this Functional Block. The global catalogue is available at the following address: http://www.eurocontrol.int/nm-services Output of the safety assessment carried out by DNM for the Functional Block: S1. FB decreases Safety S2. FB has no impact on Safety S3. FB increases Safety S4. Safety assessment to be performed or on-going The way the Functional Block will be deployed: D1. FB will be deployed in Operation along with the release migration. FBs deployed as D1 normally do not include new or changed ATFCM procedures. D2. FB will be subject to a Pilot Phase (Operational Trial) followed by a Go/NoGo decision for ops deployment after Release Migration. New ATFCM procedures or changed ATFCM procedures are normally only issued as a result of D2 deployment. These are issued via Ops Instructions after the consultation process agreed with ODSG. D3. FB will be subject to R&D ops validation (e.g. SESAR). Depending on the Operational deployment plan: • If D1: Is an OPT planned for this FB? • If D2 or D3: provide additional information on the activities that will take place (pilot phase, ops validation phase, etc.) The documentations that will be updated following the deployment of the Functional Block. Training sessions, i.e. the training dates, and the related links for access.




5.2.

RELEASE 17.0

5.2.1.

NOS-01 - Coordinated Process for ASM/ATFCM FB283: Network Impact Assessment Users impacted

Internal NMOC, Airspace Users, AMCs and FMPs.

Objective

Enhanced ASM and ATFCM co-ordination process relies upon a timely and accurate pre-tactical network impact assessment of airspace allocation. The assessment focuses upon improving route and airspace availability to best serve the needs of military and civil airspace users within the context of the anticipated network constraints. This FB has three main objectives: 1. ASM solutions for congested areas. Promote usage of CDRs/RSAs part of the AUP. 2. Flight Efficiency proposals for AO based on usage of CDRs/RSAs part of the AUP. 3. Validated/rejected consolidated AUP proposals at internal level to be proposed at external level (AMC/FMP) if needed for Objective 1 and 2. Objective 3 shall follow AUP/UUP time limitations as expressed in the ASM Manual. Enhance the NMOC tool support for D-1 network impact assessment of airspace allocation. These will include: • Improved data handling of operational AUP data in Predict and SIMEX tools. • Improved simulation of CDR and RAD constraints in Predict and SIMEX tools. • Improved Predict MAP tool identification of CDR routings and visualisation of network impacts. • Improved Predict and SIMEX simulated traffic reroutes: enhanced with more historic City pair routes and finer tuning of CDR and RAD constraints.

Description

• Improved data and trend analysis of historical AUP/UUP statistics. ASM/MIL benefits: improved civil and military information sharing. Airspace Users benefits: • Network configurations that respond to Airspace Users needs. • More opportunities to improve individual flight efficiency. NMOC/ATFCM benefits: • New AUP solutions to mitigate ATFCM hotspots. • Participation in AUP decision making process promoting efficient Network configurations to balance local and/or sub-regional airspace needs. • An improved understanding of the Airspace User needs. • Balancing the impacts of improvements in one area against other areas and the network.

Impact

No impact for external. Deployment information

Service reference

ID S212 - Airspace Real-Time Simulation

Safety assessment

G4: Changes which are normal changes for a Release.

Operational

The FB will be deployed first on a test chain from 15th of January. Test and




5.2.2.


deployment plan

operational validation sessions are planned for January - February 2013 period. If approved, the FB will be deployed along with the Release.

Documentation publication

High-level procedures (part of the Network Impact Assessment Process document) will be updated.

Training sessions

One training session per week will be organized for the MILO and NMC. Internal training on CIAM will be provided.

Users’ validation

The FB will be available for validation on a test chain from January 2013 until March 2013.

NOS-03 - Airspace Data Repository - Phase 1 FB556: eRestrictions (including FPR) Users impacted AOs, CFSPs and ATFM Objective To contribute to end user’s goal of filing fewer incorrect FPLs to NM IFPS. AOs and CFSPs do not have access to all Flow restrictions used during flight plan validation: Invalid Flight Plans being difficult to correct by AO’s as they do not know the contents of the Flow restriction that they need to respect. Description The objective is to make available to the airspace users the restrictions including Flight Profile Restrictions (FPLs) used by flight plan validation in order for them to have fewer invalid FPLs. The deployment will be done in AIXM 4.5 and though ftp server. Impact Impact on client application interfaces in order to process this data Deployment information Service reference

ID S334 - Airspace Data Management

Safety assessment

G3b: These changes will initially be used for validation purposes and will not be operationally deployed until the safety case has demonstrated that the service is “acceptably safe”.


The FB will be deployed along with the Release.


The eRestrictions by ftp server User Access Manual will be updated by NMNTS. The eRAD Conceptual Guidelines is under review.

Training sessions Users’ validation

None A limited validation with an external client will be on-going during SAT testing.

FB569: SDO Download - EAD / CACD Comparison Users impacted CACD, ADS, AOs, CFSPs and ASM Tools Development of an internal tool named “CASTAR” (Computer Aided Objective Synchronization Tool for Airspace Repositories) to automate data comparison between EAD SDO and CACD. This FB includes coupling and comparing of CACD data with EAD data within Description the agreed scope - Aerodromes and Points in a geographical area determined by the user (ADS). Impact mainly on CACD/ADS to provide higher data quality within CACD. Impact No impact for external stakeholders. Deployment information Service reference Edition date: 20/11/2013

ID S334 - Airspace Data Management



Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 G3b: These changes will initially be used for validation purposes and will not be operationally deployed until the safety case has demonstrated that the service is “acceptably safe”. First step of deployment covers Aerodromes and Points (NM17). Internal documentation available. Organised within ADS team. Done via two cycle of SAT/OPS testing sessions.

FB572: Prepare Ops Validation with ASM Tools Users impacted ASM Tools Prepare the OPS deployment for the full interoperability between NM and Objective ASM Tools This FB will bring two new B2B services to obtain the manageable Route Segments for an AMC. Description It will also complete the configuration of the Pre-OPS testing platform. Impact mainly on ASM Tools to develop interfaces benefiting from the above Impact services Deployment information Service reference Safety assessment Operational deployment plan Documentation publication

5.2.3.

ID S334 - Airspace Data Management G3a: These changes are part of the release safety assessment as they are likely to be operationally deployed before the ADR Service is deployed. The FB will be deployed along with the Release • B2B Refence Manual will be updated. • Improvements to documentation of AIXM Extension are planned for NM17.5.

Training sessions

None.

Users’ validation

The B2B data export and ASM services is currently in a pilot phase. Communication with Customers of this service is on-going and constant.

NOS-12 - Call-Sign Similarity (CSST) FB568: CSST C&T Users impacted AOs, CSMC Correction and tuning of delivered functionality in 16.5 (Single AOObjective Deconfliction) plus small remaining functionality User interface: • New button enables return to the state prior to auto-deconflict. • User is no longer required to enable Caps Lock before input of queries. Description

• View Name is now visible in all windows during workflow so navigation is easier. • User is no longer obliged to backup View data from previous CSST release. Views are now visible across releases. Operational function: • CSST by default, will not output solutions using leading zeroes unless un-




NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 flagged by user. • CSST will now use next flight AO designator when the next flight AO is different from original flight AO designator. • CSST will now read new column formats to enable AO to upload next flight details within schedule files. • CSST will now take into account CFN suffix when grouping flights. (XXX103J and XXX103 will not be handled as same aircraft). • CSST will now group flights during upload rather than during initialisation. This facilitates Back-End operation so it is transparent to user. Administration: • CSMC can see conflicts according to Original Flight ID and then compare with new Flight ID. This facilitates a more realistic sanity check. On systems: only CUA. For users’ perspective: Application more robust, more friendly and accessible from the NOP portal URL.

Impact

Deployment information Service reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation

5.2.4.

ID S321 - CSS Service - Call Sign Similarity Service G4: Changes which are normal changes for a Release. The FB will be deployed along with the Release. • CSST user guide will be updated and sent to registered user of CSST. • NOP on-line help will be updated. • CSST release notes have been updated and distributed. • No dedicated training is planned. • Demonstration of part of new features has been given during user group meetings. No validation planned.

NOS-14 - AirCraft IDentification FB537: Post-Deployment CCAMS C&T - 2 Users impacted NM internal operations, CCAMS units Objective Correction and tuning of features delivered in previous Release This Functional Block fixed some issues mainly on the back-end systems, on the business rules used by CCAMS and increases safety, contingency and efficiency. It will: Description

• Reduce the risk of code shortage. • Improve assignment logic. • Fix some safety issues. • Improve the contingency of CCAMS systems: NOP Portal can be used in contingency situation to display SSR codes information. No external impact except on the flight list displays in the NOP Portal.

Impact

Deployment information Service reference Safety assessment Edition date: 20/11/2013

ID S143 - CCAMS (Centralised SSR Code Assignment and Management System) G4: Changes which are normal changes for a Release.



Operational deployment plan Documentation publication Training sessions Users’ validation

5.2.5.

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 The FB will be deployed along with the Release. Portal Help will be updated Contingency procedures will be amended. CCAMS User Manual will be updated. Main users receive information via the CCAMS User Group. However, some general briefings are also given during the NM Users Day. Internal changes so validation done through internal SIT/SAT.

NOS-21 - Free Route Airspace Network-wide FB526: FRA Improvements Users impacted CHMI users, AOs, CFSPs, CRCO and ATFM • To improve the FRA network implementation. Objective

• To facilitate the maintenance of FRA Restrictions. • To ease and speed up the correction of Flight Plans.

Description

• In order to facilitate FPL corrections by IFPS operators and pro-active solutions (AOLO) to AOs, the map will allow presentation of the FRA points of the FRA airspaces that the profile plotted is crossing. • CHMI Map Display will include the temporality FL range for correcting/validating FPL's. The quality of the NM FRA infrastructure will be higher. The impact on HMI is high; however changes to back-end systems are limited to technical code refactoring.

Impact


5.2.6.

ID A211 - European Route Network Improvement Plan (ERNIP) ID S334 - Airspace Data Management G4: Changes which are normal changes for a Release. The FB will be deployed along with the Release. CHMI MAP user guide will be updated; no change in procedures so the eRAD user guide will not be impacted. Internal training sessions will be organised. An OPT is planned for this FB (cf §4.2).

NOS-41 - Network Operations Plan [Update v2.0] FB560 (Real time network situation displays) removed from Release 17.0; its features have been included in the Technical Block TB100 (Map display for the NOP) planned for Release 17.5. FB557: NM customisable platform for all users Users impacted NOP Portal users The NOP Portal intends to be the window on Network Manager processed and services. By 2016, the look & feel and ease of use will reflect this. The roadmap until then includes changes aiming to: Objective • Improve the general usability of the portal, both from the provision and the retrieval of information. • Provide personalisation.




NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 • Provide views of the NOP adapted to different roles. • Provide better access from mobile devices. The first step delivered with this release will provide: • Reinforced usability. • The possibility to customize the interface via a support to user in working environment personalization. • The introduction of workspace concept in NOP Portal. • Evolution of navigation base on different ATFM phases to an Application Desktop in the NOP Portal.

Description

• Persist Counts customizations: the customisations of the Counts application will persist in user preferences (colors, piling up order, etc.), stored centrally into NM systems in order to retrieve them where ever the user logs with the same token. It is implemented to better answer ATFCM monitoring needs. • Allow to Show / Hide columns in lists: when displaying a list of data (ex Flight Lists), the customer will be able to customise the list of displayed columns (Show/Hide). Such configuration will persist thanks to a central storage into NM systems. • Preference editor: a preference editor is implemented into the Portal to support the implementation of HMI customisation. • Central storage for Customisation parameters: A central storage of HMI Customisation parameters is developed, allowing retrieving the defined configuration when logging in from any device, using the same token. • Customisation of visible main views on main pages: When an authenticated customer customises the set of main views on each main page, this customisation is centrally stored for persistence purpose. NOP Portal usage procedure to be adapted to the various evolution of the interface. This will be addressed during Operational Trial before migration.

Impact


ID P348 - Network Operations Portal G1: Changes which are not implemented in the operational systems. The FB will be deployed along with the Release. The NOP Web-based help will be updated. No training. An OPT is planned for this FB (cf §4.2).

FB584: Updating the NOP, CHMI and Login page banners Users impacted Users of NOP, NMIR and CHMI Objective Update the NOP, NMIR and CHMI to the new NM logo and banners. Update of logo, banners, icons and text in the NOP and CHMI applications to Description cope with the new naming of these tools. Impact The impact will be only visual on the interface; no features will be modified. Deployment information Service Edition date: 20/11/2013

ID P348 - Network Operations Portal Edition 3.5 [email protected] ©2013 The European Organisation for the Safety of Air Navigation (EUROCONTROL) p.21

EUROCONTROL Network Manager reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation

5.2.7.

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 ID P349 - CHMI (Collaboration Human Machine Interface) Applications G4: Changes which are normal changes for a Release. The FB will be deployed along with the Release. No change in documentation. No training. No validation.

NOS-42 - Alignment to Performance framework FB456: Alignment to Performance framework (1/3) Users impacted CRCO Objective Improve the CRCO daily FTP export. CRCO (R2) is involved in the Emissions Trading Scheme project in partnership with the EU and requires the total actual route length to be added to the flight list. The FB will: Description • Add field ARU_FLT.FLT.FLT_C_RTE_LEN at end of flight table records (i.e. after CURRENT_ARRIVAL_AD_ICAO_ID) • Provide CRCO R2 and NM with explanations / documentation on how exactly this route length is calculated (more particularly regarding route portions outside the IFPS area). The FB will provide new data to CRCO

Impact


ID S315 - Load and capacity management G1: Changes which are not implemented in the operational systems. The FB will be deployed along with the Release. SRD document (internal) updated. No training planned. A set of data has been produced for test purposes.

FB456: Alignment to Performance framework (2/3) Users impacted NMIR users and users of “list of exempted flights” report • Adapt the NMIR layout to the new name (NMIR instead of CIR) Objective

• Improve existing reports dedicated to the exempted flights in the scope of the ATFM IR. • Change of the banner: NMIR banner instead of CIR banner.

Description

Impact Edition date: 20/11/2013

• Improve the "List of exempted flights" report by aligning this flight list with the one sent to the members states in the scope of the ATFM IR. This FB will align NMIR with ATFM IR and with the new graphical layout of NM. The report “list of exempted flight” and its content will be modified (one



NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 column added): only the “terminated plan” will be listed. Deployment information

Service reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation

ID S315 - Load and capacity management G1: Changes which are not implemented in the operational systems. The FB will be deployed along with the Release. The web-based help shall still be updated. No training planned No validation planned

FB456: Alignment to Performance framework (3/3) Users impacted CHMI users Objective Correct a problem of retrieval of delay figures. The regulation delay is wrongly retrieved, so the FB aims to correct the Description problem: the regulation delay was wrongly displayed in the CHMI for regulation over-midnight. Impact Positive impact as it corrects an existing problem. Deployment information Service reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation

5.2.8.

ID S315 - Load and capacity management G1: Changes which are not implemented in the operational systems. Caution: The deployment in NM17.0 of this part of the FB (3/3) still need to be confirmed. No documentation publication updated. No training planned No validation planned

NOS-43 - ATFCM Planning FB360: Scenario Data management Users impacted NOP users participating to the Network Impact Assessment trial Objective To improve SIMEX access and tools available to pre-tactical FMPs Caution, the scope is currently under review: • FMP initiation of a Predict SIMEX session (17.0). Description

Impact

• FMP edition of a Predict SIMEX regulation (17.x). • FMP proposal of a Predict regulation via Predict SIMEX (17.x). The FB will add a button into the NOP to launch a SIMEX session in a new window. No impact for the external user: Only those FMPs involved in the trial will get the button. Deployment information

Service Edition date: 20/11/2013

ID S315 - Load and capacity management Edition 3.5 [email protected] ©2013 The European Organisation for the Safety of Air Navigation (EUROCONTROL) p.23

EUROCONTROL Network Manager reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation

5.2.9.


G4: Changes which are normal changes for a Release. The FB will be deployed along with the Release. No update to the NOP web-based documentation as it is to be used for a trial. No training planned. No validation.

NOS-44 - Flight Plan interoperability FB460: Increase planned flight trajectory consistency between AO and NM Aircraft Operators, Flight Planning Service Providers, Aerodrome Reporting Users impacted Offices ARO Objective Increase performance of flight planning and ATFCM operations. This functional block contains a number of developments that are intended to increase flight trajectory consistency through a more extensive use of flight plan information already foreseen to be included in a filed flight plan in ICAO format as well as through the addition of some new flight plan data elements. It includes the following developments: 1. The IFPS shall use estimated elapsed time (EET) information provided within the filed flight plan or associated messages for the calculation of flight trajectories. Prior to using this information, the IFPS shall validate it against its own calculated EETs allowing for the provided EET to be within a pre-defined window around its calculated EET. EET values that fail this checking shall be ignored. They will not lead to the invalidation of the message. It should be noted that, with this change, the provision and updating of EET information within flight plan messages submitted to IFPS becomes an important means to ensure the IFPS calculated trajectory of a flight is synchronised in time with the trajectory calculated by the operator of the flight for the same flight, with a direct impact on the IFPS flight plan validation process. 2. It shall be possible for flight plan originators to include within the Field 18 RMK/ element of an ICAO format flight plan transmitted to IFPS the Description following data: •

Estimated taxi time

•

Top-of-climb (TOC) information for every transition from a climb phase to a cruise phase

•

Top-of-descent (TOD) information for every transition from a cruise phase to a descent phase

•

Bottom-of-climb (BOC) information for every transition from a cruise phase to a climb phase

•

Bottom-of-descent (BOD) information for every transition from a descent phase to a cruise phase

•

Distance at location (DAL)

• Take-off weight (TOW) Taxi time shall be indicated using the format: TAXI: is the estimated taxi time in hours and minutes, with the hours optional. The hours are compulsory for taxi times of duration longer than 59 minutes. TOC, TOD, BOC or BOD shall be indicated using the format: Edition date: 20/11/2013



Impact


NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 TOC: TOD: BOC: BOD: is the projected distance on the ground from take-off to the point where the TOC/TOD/BOC/BOD is reached expressed in nautical miles preceded by the letter “D”; is the estimated level at the TOC/TOD/BOC/BOD expressed as in Field Type15b; is the elapsed time from take-off to TOC/TOD/BOC/BOD in hours and minutes (hhmm) preceded by the letter “T”. The estimated level at the TOC/TOD/BOC/BOD should be equal to the requested cruising level on the route segment where it applies. Otherwise IFPS will ignore that TOC/TOD/BOC/BOD instance without raising an error. Distance at location shall be indicated using the format: DAL:. is the projected distance on the ground from take-off to the location expressed in nautical miles preceded by the later “D”. is the published designator of the location preceded by the letters “PT” or “AD”. The location may be either a point (PT) or the aerodrome of destination (AD). The corresponding ICAO 2 to 5 letters designator shall be indicated for a point. Only points that have a published designator may be indicated. They have as well to be part of the planned route of the flight. The ICAO four-letter indicator shall be indicated for the aerodrome of destination. Take-off weight shall be indicated using the format: TOW: is the total weight of the aircraft at take-off in kilograms. All new indicators shall be separated from other text included in RMK/ and between them by a space or end of line separator. Example: -EET/EDUU0012 EDVV0016 EBUR0046 LFFF0056 DOF/130601 RVR/200 RMK/TRAINING FLIGHT TAXI:15 TOC:D118F280T0020 TOD:D546F280T0122 DAL:D480PTNIPOR TOW:64290 Flight plan originators will need to adapt their systems and/or procedures in order to take advantage of the features implemented under this functional block. No error shall be raised for syntactically invalid indicators within RMK/. They will not be recognised by IFPS and therefore be ignored. All new information is optional. However, when included in the filed flight plan, the more information is provided the higher is expected to be the consistency of the calculated flight trajectories between NM and the originator of the flight plan. Therefore it is highly recommended to provide as much of it as possible. TOC/TOD/BOC/BOD information will be used by the NM systems only when the distance DAL/ at the aerodrome of destination is provided as well, as a minimum. Without it the use of TOC/TOD/BOC/BOD information alone may lead to an increase of inconsistency between trajectories. For messages transmitted via the AFTN network, due attention should be paid to the total length of the resulting flight plan message that should no exceed 1800 characters. The new flight plan data is intended to be used by the NM systems for flight trajectory calculation and, at least initially, be removed from NM output



NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 messages in order to avoid any possible impact on NM client systems. Information provided within the TOC, TOD, BOC, BOD and DAL indicators will be used by the NM systems only for flights that are entirely IFR/GAT and containing no STAY segments. Deployment information

Service reference Safety assessment


Documentation publication Training sessions Users’ validation

ID S325 - Flight Plan Processing and Distribution G4: Changes which are normal changes for a Release. The TOC, TOD, BOC, BOD and DAL indicators will be deployed initially on a trial basis. Pending on the results of the trial, they may later on be declared operational. The other developments included in this functional block are planned to go operational as soon as their corresponding Release is deployed to operations. IFPS user manual will be updated. Training will be included in the normal IFPS training. An OPT is planned for this FB (cf §4.2).

FB499: Use of AO 4D profile - Prototype Users impacted Participants to the SESAR validation exercise EXE-07.06.02-VP-311. Evaluate the impact of the Extended Flight Plan (EFPL) concept on the flight Objective plan validation by IFPS. The Extended Flight Plan concept refers to the enrichment of the current flight plan content with the 4D trajectory of the flight, as calculated by the originator of the flight plan, as well as climb / descent performance data in the conditions of the flight. Description Further details regarding this concept are provided within the Operational Service and Environment Definition (OSED) document of the SESAR Work Package Business/ Mission Trajectory Management (WP7.6.2). The prototype built under this functional block is intended to support an offline validation exercise of the Extended Flight Plan concept. Participants to the validation exercise will have to adapt their systems in Impact order to produce Extended Flight Plans. Deployment information Service reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation

ID S325 - Flight Plan Processing and Distribution Safety assessment under review by SESAR team. Not available yet. It is a prototype. Validation plan available to participants to the exercise. Not available yet. It is a prototype. Not available yet. It is a prototype.

FB554: FIXM Strategy in SESAR Edition date: 20/11/2013



EUROCONTROL Network Manager Users impacted Objective Description Impact

Planned for Implementation in 2013-2014 Internal NM systems Align NM systems with FIXM roadmap This FB is an envelop covering the NM engineering resources needed for the follow-up, interaction and alignment with the FIXM roadmap in 2012. No external impact (no deliverables to the externals). Deployment information


This FB covers R&D activities that are not cover yet by a Service. G1: Changes which are not implemented in the operational systems. No Deployment -

5.2.10. NOS-45 - Dynamic ATFCM FB533: Support TTA Trial (May 2013) Official SESAR WP7 trial participants (NMOC, Airspace Users, Flight Crew, Users impacted FMPs - possibly ATC en-route, tower)

Objective

Description

Impact

• To determine the feasibility of calculating and communicating target times at regulation hot spots. To measure flight crew adherence to flight execution phase targets. • To measure benefits of improved flight execution phase predictability. • To identify concept deficiencies. New optional flight list columns containing the new target values will be added to the ETFMS, NOP and CHMI. These columns will contain the flight target values and flight adherence measures. Please refer to SESAR OSED WP7.6.5 concept and §4.4. The week long operational trial(s) will be limited to approx. one ATFCM regulation per weekday. Participating airlines and ANSPs will be impacted by the HMI (ETFMS and NOP only) and procedural changes. Deployment information

Service reference

ID S315 - Load and capacity management

Safety assessment

G2: Changes which are prototyping activities to support the validation of future SESAR concept that will be deployed in dedicated validation environments.



The FB will be deployed along the Release process. Documentation (BSR and TSR) under finalization (trial is in May 2013) Training will be handled within the Fair Stream SESAR Trial. Training will also be covered for the VP-632 - TTA Ops Trial (not part of Fair stream). Covered in trial organisation.




5.2.11. NOS-48 - NM-FOS Prototype validation FB544: Initial Flight Object Prototype - 1 Users impacted NMVP or DEV/Test Platform Development of the NM-FOS (Flight Object Server) Prototype and the integration of the NM in the FOS network. Objective Exchange of Flight data (including ATFM constraints (i.e. target times)) with an ATC IOP (InterOPerability) systems by means of FO. A joint initiative between DNM, Indra and MUAC to enhance the current DNM systems with the capabilities to interoperate by means of using the FO and perform a SESAR verification exercise involving the MUAC ATC and DNM systems. Description The technical verification/validation exercise planned for Q2 or Q3 2013 will perform the preparatory work for an operational exercise to take place in 2014 with simulated traffic (subject of FB571 – NM18). No impact on Ops systems as the exercise will involve the “off-line” test systems. Impact (Prototyping aims to reduce the impact on the systems when the functionality goes operational and to refine the technical architecture options for the NM integration in the FOS network) Deployment information Service reference

ID P3411 - Data distribution

Safety assessment

G2: Changes which are prototyping activities to support the validation of future SESAR concept that will be deployed in dedicated validation environments.


The deployment of this FB will be done along the Release deployment. Documentation is handled by the SESAR WP13 Programme. No training. It will be done during the trials.

5.2.12. ATFCM Domain FB524: ATFCM Domain improvements Users impacted NMOC (ATFCM teams) To improve ATFCM service quality by local enhancement of internal NMOC Objective tools • Determine the validity period for each reroute Opportunity for flight efficiency. • Reducing the repetitive workload associated with Reroute proposals (RRP) by enabling the group sending of RRPs. Description

• Reduce time spent editing Exceptional Condition regulation AIM messages by automatically generating and sending them. • Improve the linking of regulations by system detection and alert of geographically independent regulations that should be manually linked. • Tuning the ETFMS tools that identify flights pushed by their regulation delay into restricted airspace. • Removing obsolete network effects from Predict traffic demand. • Improving User readability of regulation operational logs.




NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 • Automatic generation of Regulation Names. • Improvements to the filtering and sorting capability of ETFMS displays. The immediate impact will be to improve NMOC internal tool capability that supports Network Management service provision to ANSPs and AOCs.

Impact


ID S315 - Load and capacity management G4: Changes which are normal changes for a Release. FB will be deployed along with the Release process. “Re-routing opportunity” documentation will be updated. No external planning planned. No validation planned.

5.2.13. Flight Planning Domain FB550 (1/5): IFPUV - Highlight errors associated to known anomalies Aircraft Operators, Flight Plan Message Originators, Computer Flight Plan Users impacted Service Providers Indicate to IFPUV Users (NOP and B2B) that the FPL that is raising an error Objective in IFPUV may be manually accepted by IFPS Staff. When an error is displayed in the NOP Portal IFPUV that has been tagged by IFPS as a known anomaly caused by IFPS software or data limitation, the error will be highlighted in red and the text "WARNING: DUE TO A POSSIBLE ANOMALY, THIS MESSAGES MAY REQUIRE SPECIAL Description HANDLING IN IFPS" shall be displayed. When an error is or sent in reply to a B2B IFPUV query, the reply will be sent with a new flag to indicate the possibility of special handling in IFPS. Users will know that they may have their FPL accepted by IFPS even though Impact there is an error when validating via IFPUV. FB550 (2/5): Relax error reporting during IFPS profile checking Aircraft Operators, Flight Plan Message Originators, Computer Flight Plan Users impacted Service Providers Objective Reduce number of ROUTE DOES NOT EXIST errors IFPS may report the ROUTE DOES NOT EXIST error when the profile is in cruise or when the route portion is completely within undefined airspace (no Description route exists). The decision to report the error is controlled by parameters that will be adjusted to relax the check and reduce the number of occurrences that the error is reported. Impact Less invalid flight plan messages and reduced workload for IFPS Staff. FB550 (3/5): Send route proposal with IFPS REJ Message Aircraft Operators, Flight Plan Message Originators, Computer Flight Plan Users impacted Service Providers Objective Improve flight planning assistance When a FPL is rejected (automatic and manual) by IFPS for Profile or Description Routing Errors, a route proposal will be automatically generated and added Edition date: 20/11/2013



NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 to the REJ Operational Reply Message. The proposal will be added in the field 'POSRTE'. The field will not be present in the REJ message if no alternative route can be found by IFPS. Assist flight plan message originators in finding alternative routes and reduced workload for IFPS Staff.

Impact

FB550 (4/5): Consistent Content of REJ Message Aircraft Operators, Flight Plan Message Originators, Computer Flight Plan Users impacted Service Providers Objective Improve quality of IFPS REJ reply messages When IFPS sends a REJ message the flight plan data that it contains is always the message as filed by the originator. When IFPS Staff have solved an initial problem in the submitted message, the error message(s) that are included in the REJ do not match the flight plan data that is present in the Description REJ. As of the NM 17 release, the IFPS REJ ORM will contain the flight plan data as is currently displayed in the IFPS flight plan message editor at the time the message is rejected. Flight plan message originators will receive a REJ ORM containing a Impact consistent flight plan message and associated IFPS errors. FB550 (5/5): Auto-correct Date of Flight (DOF/EOBD). Aircraft Operators, Flight Plan Message Originators, Computer Flight Plan Users impacted Service Providers Objective Automatically correct error in IFPS Sometimes flight plans are invalid because the date of flight is not indicated using the correct format (YYMMDD) but the format (DDMMYY) is used Description instead. IFPS will detect such cases and automatically correct them.. Impact Less invalid flight plan messages and reduced workload for IFPS Staff. FB550: Reduce manual flight plan processing in IFPS Deployment information Service reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation

ID S325 - Flight Plan Processing and Distribution G4: Changes which are normal changes for a Release. The FB will be deployed along with the Release. Updated version of IFPS Users manual will be published one month before release migration start. Provided via the usual IFPS training session. An OPT is planned for this FB (cf §4.2).

5.2.14. Airspace Data Domain FB527: CIAM Improvements Users impacted ASM external and internal users. Objective Fine tuning of CIAM to enable more clients to benefit from CIAM functionality. Edition date: 20/11/2013



Description Impact

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 In order to allow full use of ASM B2B services, the FB provides a fine tuning of CIAM functionality in the Lead AMC concept and rules surrounding nilAUPs and rolling UUP. Impact mainly on CIAM back-end system. Deployment information


ID S334 - Airspace Data Management G3a: These changes are part of the release safety assessment as they are likely to be operationally deployed before the ADR Service is deployed. The FB will be deployed along with the Release. CIAM documentation would be updated. No training. No validation.

FB528: Airspace Data Domain improvements Users impacted Internal users but with participation of some external clients To increase the quality of the Airspace and Restriction data available to front Objective ATFM, FPL systems and external users. New CACD Validation tools available in particular regarding flight plan validation comparisons per AIRAC cycle: • New feature in ENV will avoid dual input in CACD and pre-validation environment.

Description

• New FTPS file type on the TEST, OPT and OPS environments: ENV data entered in a Pre-Validation exercise will be written to an FTP file (the data consists of generic ENV state information) which can then be retrieved and applied to the Preparation area of a different database. Correction of some errors: • RAD restriction validity period from present with Flow Routing a route only defined for a period in the future. • ENV Val should give an error for this case, the Restriction Validity period shall start in the future, when the route exists. Impact entirely on CACD back end system. The FB will have no impact on the NOP and no B2B is planned.

Impact

Deployment information Service reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation Edition date: 20/11/2013

ID S334 - Airspace Data Management G3a: These changes are part of the release safety assessment as they are likely to be operationally deployed before the ADR Service is deployed. The FB will be deployed along with the Release. Training documentation will be updated, available on request. No dedicated training session is foreseen. No need for OPT has been identified.




5.2.15. Correction and Tuning FB154: Reporting C&T for Release 17 Users impacted FMPs (CIFLO users) Objective Enhance Post-Ops analysis on OTMVs, Occupancy Counts and Flow Counts CHMI and NOP will provide access to OTMVs, Occupancy Counts and Flow Description Counts for Post-Ops analysis on Archived data. The displays will be similar to Tactical. Impact None Deployment information Service reference Safety assessment Operational deployment plan Documentation publication Training sessions Users’ validation


ID A121 - Network Operations Monitoring G1: Changes which are not implemented in the operational systems. The FB will be deployed along with the Release. CHMI user guides will be updated. CHMI training will be updated An OPT is planned for this FB (cf §4.2).




Planned for Implementation in 2013-2014

5.3.

RELEASE 17.5

5.3.1.

NOS-01 - Coordinated Process for ASM/ATFCM FB601: ASM monitoring Internal NM Users impacted Application impacted

Objective

Description Impact

A7. Datawarehouse (e.g. NMIR) The access to ASM archived data is required to fulfill the requirements of EC Regulation N. 691/2010 published the 29th of July 2010, laying down a performance scheme for air navigation services and network functions. Improved ASM monitoring and reporting will result from improved access to data that will support the measurement of the effective use of the civil/military airspace structures, KPI defined in the Environment performance area. This KPI will be monitored in the first reference period (2012-14) and then measured in the second reference period (2015-2020) with possible appropriate targets. The FB aims at archiving data in the NM datawarehouse system so that they can be used in reports and B2B in the future I0. No impact

Impact description

-

Service reference

ID S212 - Airspace Real-Time Simulation ID A221 - Airspace Management (ASM) Processes

Safety assessment Operational deployment plan Users’ validation Documentation publication Training sessions

5.3.2.

U12. Internal NM

S2. FB has no impact on Safety D1. FB will be deployed in Operation with the release migration. No OPT will be organised for this FB. No No

NOS-03 - Airspace Data Repository - Phase 1 FB555: eRestrictions (eRAD) Users impacted U8. AO or CFSP A1. CHMI A2. CIFLO, CIAO Application impacted A4. CACD A11. B2B Objective Publication of the CACD Restriction data in AIXM 5.1. format Pressure is heavy from AOs and CFSPs for the publication of NM constraints on the published Airspace data: Description

• EAD eRAD does not take into account the sometimes dynamic nature of the RAD data. • EAD eRAD cannot publish EU/EURO Restrictions, some FRA/DCT data, FlightProcessingRestrictions, AerodromeFlightRule and Terminal Procedure, Aircraft type Restrictions





Planned for Implementation in 2013-2014 • NM FTPS solution is a flat file only containing full snapshot of data. Not a formal publishing mechanism as promised by ADR. • Closed for Cruising levels are not currently published. • FRA DCT Restrictions can only be distinguished by parsing the OperationGoal. This Functional Block implements the ADR Project objective of publication of NM Restriction data in AIXM 5.1 format. Under the same FB, EAD eRAD functionality will also be phased out. As far as the Restrictions are concerned, there is no new data being exported: it is just in a different format. An explanation of the data will also be given in the document mentioned. All data types referenced by the FlightRestrictions will be added also to the current B2B export of NM data. The data types are: Operation sectors, groups of Operational Sectors and Clusters, FABs and terminal procedures. Precise details of data types to follow in the Release Notes and (with more details) in the documentation (see below). I1. Impact on procedures. I2. Impact on Man-Machine interface. I3. Impact on clients’ systems.

Impact Impact description Service reference Safety assessment Operational deployment plan Users’ validation


The impact on the interfaces still needs to be identified EAD eRAD functionality will be phased out ID S334 - Airspace Data Management S2. FB has no impact on Safety D1. FB will be deployed in Operation with the release migration. No dedicated OPT will be organised for this FB. Nevertheless, the B2B services provided by this FB will be available during the OPT. An eRAD Migration Plan is under review and will be made available to users in advance of deployment. (see below) The eRAD Conceptual Guidelines document will be updated in order to give further information about the content of the various Restriction types. (see below) The Conceptual Guidelines are available in the EAD Knowledgebase. The following documents are available at http://www.eurocontrol.int/lists/publications/network-operationslibrary?type=3317&keyword=: • Migration Plan for the eRAD Service from EAD to NM B2B Service • eRestrictions - Conceptual Guidelines (Draft)

Training sessions

5.3.3.

No

NOS-12 - Call-Sign Similarity (CSST) FB588: CSST C&T U8. AO or CFSP Users impacted U12. Internal NM Application A9. CSST





impacted Objective

Correction and tuning of delivered functionalities in NM17.0 and small additional changes to functionality. User Interface: • User does not have to check constraints to initialize ATC Flight ID's when uploading a csv schedule. • User can save download files as Excel csv with latest version of Office suite. The structure of the csv has not changed. The user now has the option to use extension .xlsx as well as extension .csv • This is used with MS Office Suite 2010 using xl version 2007 • User can more easily see which flights have been changed in downloaded CSST output. • IATA season dates visible. Operational function:

Description

• Downloaded conflict list contains new columns EOBT and Days of Operation. • Conflict qualifications (e.g. Same Aircraft) can be imported into a new View. • Refine capture of exaggerated parallel character conflicts (e.g.1 v 123). • Capture of conflicts containing duplicate letters in bigrammes (e.g. 12BA v 33AB). • Capture conflicts consisting of partial anagrams where last letter is similar (e.g. 628W v 236W). • Refine capture of conflicts between call signs of length format nnA (e.g. 89A v 91A) Administration: • CSMC will have the ability to refine certain rules using an offline simulation tool. I1. Impact on procedures. I2. Impact on Man-Machine interface.

Impact Impact description Service reference Safety assessment Operational deployment plan Users’ validation Documentation publication Training sessions

5.3.4.

Application interface will be more user friendly. It will meet user expectations concerning capture of Call sign conflicts. ID S321 - CSS Service - Call Sign Similarity Service S3. CBA increases safety D1. FB will be deployed in Operation with the release migration. No OPT will be organised for this FB. CSST User guide will be updated. • CSST Familiarisation Session may be organised at a future CSSUG in the Training box. • Ad-hoc training may be organised on request of users.

NOS-14 - Aircraft Identification FB575: Post-Deployment CCAMS C&T - 3 Internal NM Users impacted


U3. Airspace User (Civil): ANSP and pilots



Application impacted

Objective

Description Impact Impact description Service reference Safety assessment Operational deployment plan Users’ validation Documentation publication Training sessions

5.3.5.

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 U12. Internal NM: CCAMS office, AD team and TCF (Transponder Code Function) A4. CACD A8. CCAMS 1. Prioritise code selection On selected boundaries SSR code changes can be eliminated by sending flights with an SSR code that can be retained. Right now this is not always the case because CCAMS statically selects an SSR code from the list of eligible codes sequentially. Giving a priority to a certain series of codes from the same list for certain boundaries will greatly improve retention 2. Switch time to secondary CCAMS unit CCAMS has a secondary backup unit in IFPU2. In order to further minimize disruptions when switching for maintenance or contingency the switchover logic is reviewed to bring the accepted disruption time to an absolute minimum. 3. Enhance offline post-ops reporting Manual actions to start the post ops tools each day shall be automated. Post Ops reports shall contain defined information on ORCAM usage. This is needed to report to the EU. The FB will implement tools to: • Better retrieve data on usage of scarce resources. • Make more flexible assignments of CCAMS codes within the current limits to eliminate unnecessary code changes at none CCAMS boundaries. I0. No impact for external users. There will be less code changes implied by CCAMS at certain boundaries, meaning less workload and increased safety. This has no impact on external users. ID S143 - CCAMS (Centralised SSR Code Assignment and Management System) S3. CBA increases Safety D1. FB will be deployed in Operation with the release migration. No OPT will be organised for this FB. AD Ops manual will be updated None

NOS-41: Network Operations Plan FB592: Updating the CFMU URLs Users impacted Application impacted Objective Description Impact


This FB is postponed to NM18.0 U0. Other (specify): Users of NM website A0. Others (specify): NM web site Pursue the rebranding of the NM web site Update the URLs containing CFMU with NM. I1. Impact on procedures. I2. Impact on Man-Machine interface.



Impact description Service reference Safety assessment Operational deployment plan Users’ validation Documentation publication Training sessions

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 Possible impact on procedures or Users’ application referencing the old URL containing CFMU. General improvement of NM web site. S4. Safety assessment to be performed or on-going D1. FB will be deployed in Operation with the release migration. No OPT will be organised for this FB. No documentation updated None

FB605: EVITA Phase II for Volcex exercise U3. Airspace User (Civil) U6. Management (eg crisis management, performance management) Users impacted U8. AO or CFSP U11. ARO U12. Internal NM Application A10: NOP impacted Objective EVITA User Interface Improvements Reorganization of User Interface to facilitate the navigation inside EVITA: • Regroup of interface elements in a logical way to provides proximity consistency with the remaining window elements layout. • Text label and associated date/timestamp are isolated, being centered in middle of Forecast Details and Danger Area Details tables underneath Status Header text. Data is related to other Details, so group it together into its header text or place it into its own header. This would restore proximity consistency with the remaining window elements layout. • The Affected Area Details table and Prism Details table show isolated text data, being centered in the middle of each table. Its vertical alignment would be improved if the text was made left justified with the rest of the text in the Forecast window. Description

• Reduce vertical pane height when there is little data to display by making pane’s vertical size dynamic. User then doesn’t have to scroll up or down to display the full information. • In order to enhance the navigation, two hyperlinks have been added to the bottom right of the EVITA portlet: The first hyperlink named “D” points to Forecast detached view. The second hyperlink named “F” points to the Forecast detached view. • An alternative to the “Plot” feature has been created, named "Auto-fit". This new button (formerly known as Re-bound) opens the map window with the map zoomed to display what has been selected in the selector. • A button is added at the right hand side of each crisis row, which opens a menu that contains links to the Forecasts detached view or Danger areas detached view is requested to navigate faster. Information on EVITA may be found at: http://www.eurocontrol.int/articles/tools-available-times-crisis?tab_0_1





Impact

I2. Impact on Man-Machine interface.

Impact description

The FB slightly modify the EVITA interface.

Service reference

ID S316 - Crisis & Contingency Management ID A131 - EACCC - European Aviation Crisis Coordination Cell


5.3.6.


S2. FB has no impact on Safety D1. FB will be deployed in Operation with the release migration. Done during VOLCEX 2013 exercise (23-24 April 2013) NOP Portal online help. Usual NOP Portal training, EVITA part.

NOS-42: Alignment to Performance framework FB589: Support to flight efficiency - NM17.5 Internal NM

Users impacted


Objective

Description

Impact

U3. Airspace User (Civil) U4. Airspace User (Military) U7. Post-ops analyst U8. AO or CFSP U12. Internal NM A1. CHMI A5. Flow management systems (Predict, ETFMS) A6. FPL (IFPS) A7. Datawarehouse (e.g. NMIR) Strengthen the processes already in place with NM17.0 by improving even more the internal system capabilities in exploring and disseminating the opportunity in European Route Network. The changes proposed aim at improving the reactivity from NM in following the AO business need in choosing route across the network. The opportunity tool will provide external users, via appropriate means such as mail, RRP, phone call, AFTN message, etc. a flight-planable solution valid for a certain period of time, offering the best route for this city pair. The changes will as well improve the capabilities from NM to identify the benefits achieved by airspace users and demonstrate the contribution from NM to the Flight Efficiency Plan. Users will be able to better use the current route network availability with the help from NM that will help them benefit of the dynamicity of the Route Network. I0. No impact on externals’ tools or procedures.

Impact description

No impact on externals’ tools or procedures.

Service reference

ID S315 - Load and capacity management ID S325 - Flight Plan Processing and Distribution

Safety assessment Operational deployment plan Edition date: 20/11/2013

S2. FB has no impact on Safety D1. FB will be deployed in Operation with the release migration.



5.3.7.


Users’ validation Documentation publication

No OPT will be organised for this FB.

Training sessions

No dedicated training. Awareness campaign are already going on and will be reinforced

IFPS Users manual will be updated

NOS-44: Flight Plan interoperability FB522: Use of AO 4D profile -shadow exercise U0. Other (specify): Participants to the SESAR validation exercise EXEUsers impacted 07.06.02-VP-616 A11. B2B Application impacted A13. NMVP Evaluate the impact of the Extended Flight Plan (EFPL) concept on flight plan Objective filing to IFPS and ETFMS air traffic predictability. The Extended Flight Plan concept refers to the enrichment of the current flight plan content with the 4D trajectory of the flight, as calculated by the originator of the flight plan, as well as climb / descent performance data taking into account the flight conditions. Further details regarding this concept are provided within the Operational Description Service and Environment Definition (OSED) document of the SESAR Work Package Business/ Mission Trajectory Management (WP7.6.2). The prototype built under this Functional Block is intended to support an online validation exercise of the Extended Flight Plan concept. New related B2B services will be made available to participants to the validation exercise for filing and updating of Extended Flight Plans. Impact I3. Impact on clients’ systems. Impact description

Participants to the validation exercise will have to adapt their systems in order to produce Extended Flight Plans and transmit them to the NM via B2B.

Service reference

ID S325 - Flight Plan Processing and Distribution

Safety assessment

S4. Safety assessment to be performed or on-going Safety Assessment will be provided by SESAR Work Package 7.6.2


D3. FB will be subject to R&D ops validation (SESAR).

Users’ validation

Users’ participation to the validation exercise is under consideration as part of the definition of the validation plan.

Documentation publication Training sessions

5.3.8.

Validation plan will be made available to participants to the exercise. Not available yet.

NOS-45: Dynamic ATFCM FB140: STAM Decisions promulgation (proto) U1. Flow Manager (FMP) U3. Airspace User (Civil) Users impacted U8. AO or CFSP U13. CDM-Airport U12. Internal NM A5. Flow management systems (Predict, ETFMS) Application impacted A10. Prototype in new NOP infrastructure




Objective

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 A13. NMVP This FB aims at developing a Prototype that will not be used on NM operational platform but on the NMVP platform. Based on Hotspot flight list, FMP shall be able to select amongst a predefined set of STAM cherry-picking options locally applicable, a specific type of STAM cherry-picking to be applied to a flight selected by FMP. FMP shall use a CDM tool to coordinate the STAM Measures with the Actors concerned (below referred to as M-CDM process). STAM editor and supporting functionalities: • Enhanced STAM Measures like Local Rerouting for non-airborne and airborne, includes changing SID and STAR • Traffic Counts: Improve Hotspot HMI definition, Indicate “Proposal” count level on top of Normal count bar, linked filtering of flights in Hotspot Flight List when selecting 1 Hotspot count • New information added to Flight Lists, like Flight M-CDM state, new filtering capabilities • Measure Editor Display per measure type (Delay measure, Rerouting measure, M-CDM measure)

Description

• Lists all Measures linked to a Hotspot (or a Measure Set) Collaboration dashboard: development of the timeline, list and view • Timeline: The timeline resumes ongoing relevant STAM M-CDM and highlight upcoming due times. • dDCB M-CDM list: The dDCB M-CDM list allows filtering quickly the STAM M-CDM relevant to the connected actor with an immediate view on milestones and states. • dDCB M-CDM view: A dDCB M-CDM view allowing to display full details and participate to the M-CDM process. The FB will implement the STAM editor and the Coordination tool supporting the collaboration between the Actors involved. The interface will be implemented in FB625 (NM18.0). I1. Impact on procedures I2. Impact on Man-Machine interface.

Impact Impact description

Draft procedures will be in Operational handbook Man-Machine interface prototype in New NOP infrastructure

Service reference

ID S315 - Load and capacity management


S2. FB has no impact on Safety Safety assessment made in context of VP522 (Safety assessment on-going for the cherry-picked regulation). D3. FB will be subject to R&D ops validation (SESAR). This FB will be implemented on NMVP. Validation on NMVP V3 during VP522 planned in May 2014 VP522 will develop operational Handbook for the Validation Exercise. Training sessions for external users will be planned as part of VP522 exercise.

FB229: Traffic Complexity Users impacted U1. Flow Manager (FMP) Edition date: 20/11/2013



Application impacted Objective

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 A2. CIFLO, CIAO A10. NOP Portal Provide more precise information on flight complexity within an Airspace This Functional Block will provide additional information into CIFLO, CIAO and the NOP Portal. To give a correct indication of the flight complexity within an airspace, 5 items must be shown on the flight list: • The Entry vertical movement indicator • The Entry flight level • The Airspace vertical movement indicator • The Exit flight level • The Exit vertical movement indicator The Entry vertical movement indicator must be the trend (climb, cruise or descend) of the vector (whatever its length) • starting before the co-ordinates of the penetration in the airspace and

Description

• ending at or after the co-ordinates of the penetration in the airspace The Airspace vertical movement indicator must be the general trend (climb, cruise or descend) resulting of the comparison between • the Entry flight level and • the Exit flight level This Airspace vertical movement indicator is needed to be able to sort the flight list or to select similar flights. The Exit vertical movement indicator must be the trend (climb, cruise or descend) of the vector (whatever its length) • starting before or at the co-ordinates of the exit of the airspace and • ending after the co-ordinates of the exit of the airspace By "before or after the co-ordinates of” it is meant in the direction of the flight. For any kind of vertical movement indicator (Entry, Airspace, Exit): • The trend climb will be represented by the symbol

/

• The trend descend will be represented by the symbol \ • The trend cruise will be represented by the symbol I1. Impact on procedures. I2. Impact on Man-Machine interface.



=

Users’ procedures and user guide may need to be updated. ID S315 - Load and capacity management S4. Safety assessment to be performed or on-going D1. FB will be deployed in Operation with the release migration. An OPT session will be organised for this FB. CHMI Reference guide will be updated FMP training materiel will be updated


EUROCONTROL Network Manager 5.3.9.


ATFCM Domain FB598: ATFCM Domain improvements (1/5) Internal NM Users impacted Application impacted

Objective

Description

Impact

U12. Internal NM A3. CIAM (MILO-simul profile) A5. Flow management systems (Predict, ETFMS) The objective of the change is to improve NMOC ASM-ATFCM tools in order to anticipate Network Impact Assessment of the FUA data. These improvements will facilitate the analysis of AUP and UUP data during pre tactical and tactical operation. The execution of those anticipated analysis can help to ensure consistency at a local and Network level. In particular, the change implemented in release 17.5 will make possible to import UUP draft data from CIAM into PREDICT/Simul and ETFMS/Simul systems. The application of the FUA concept ensures that, through the daily allocation of flexible airspace structures, any necessary segregation of airspace is based on real usage within a specific time period and airspace volume. Airspace Use Plan (AUP) and Updated Airspace Use Plans (UUPs) are produced by AMCs to allow concurrent civil-military operations. These plans need to be incorporated into pre-tactical and tactical operations with minimum disruption to civil traffic as well as allowing effective military operations. NMOC has to contribute to ensure that improvements in one KPA do not lead to the performance deterioration in other KPA Network wise. NMOC has to contribute to ensure that solutions developed locally and /or proposed by Network Manager do not create a problem in other locations across NM area. NMOC has to contribute to ensure that the ASM-ATFCM process can bring the basis for improvements on flight efficiency and capacity and additionally to negotiate/coordinate revised airspace opening or closure times. I0. No impact for externals.

Impact description

No impact for externals

Service reference

ID S315 - Load and capacity management ID A221 - Airspace Management (ASM) Processes


S4. Safety assessment to be performed or on-going D1. FB will be deployed in Operation with the release migration. No OPT will be organised for this FB. No external documentation will be updated No training is planned

FB598: ATFCM Domain improvements (2/5) U1. Flow Manager (FMP) Users impacted U3. Airspace User (Civil) U4. Airspace User (Military) Edition date: 20/11/2013



NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 U8. AO or CFSP U12. Internal NM


Description


A5. Flow management systems (Predict, ETFMS) Accept REA only after EOBT-15 Currently the REA message is accepted if it is received after EOBT-30. This is for historic reasons because in the past, flights were allowed to depart up-to 30min before the flight plan EOBT. Justification: ICAO only allows departures up to EOBT-15min (see ICAO Doc 7030) unless the AOs Cancel (CNL) and re-file the flight plan. ETFMS' acceptance criteria of the REA are now aligned with ICAO requirements. I1. Impact on procedures. Up to now REA messages that are sent before EOBT-30min are rejected. After the change, REA messages are rejected up to EOBT-15min. The change has been agreed with ODSG and is not expected to have a high impact on operations because AOs should already comply with this ICAO rule since many years. ID S315 - Load and capacity management S4. Safety assessment to be performed or on-going D1. FB will be deployed in Operation along with the release migration. No OPT is planned for this FB unless required by eMail at [email protected]. ATFCM user manual will be updated. None

FB598: ATFCM Domain improvements (3/5) U1. Flow Manager (FMP) Users impacted U12. Internal NM A1. CHMI Application impacted A5. Flow management systems (Predict, ETFMS) NM Ops Center conducted different ops trials with Maastricht UAC during 2012. The purpose of the ops trial was to validate the concept of one of the procedures in the Enhanced Network Ops programme, namely Network Cherry picking. In essence, Network Cherry Pick is the use of a limited number of CTOTs to replace the traditional regulation. Its purpose is to solve short peaks in enObjective route sectors by delaying minimal numbers of flights and allowing the majority to operate without a CTOT. It is complementary to STAM but carried out by NMOC at network, not local, level. Some system improvements have been implemented to support the trials that will take place after the 17.5 migration date. Description Improvement on the visualization of the Cherry Picked flights in CHMI. Edition date: 20/11/2013



NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 I1. Impact on procedures. I2. Impact on Man-Machine interface.

Impact

Impact ONLY for trial participants: • The regulations (named CPXXX) are created by NMOC in coordination with trial participants.

Impact description

• HMI Improvement on the way the cherry picked flights are presented. The background of the ‘REGUL+’ column is presented in pink. The cherry picked flights color (pink) is not visible from other queries different from the CPXXX regulation. • Procedures Improvement on the monitoring phase of the Cherry pick regulation. Flight plans crossing the cherry pick regulation after the regulation is created are automatically exempted. NB: The CPXXX regulations are visible by all users (trial participants and not participants).

Service reference Safety assessment


Users’ validation Documentation publication Training sessions

ID S315 - Load and capacity management S2. FB has no impact on Safety D2. FB will be subject to a Pilot Phase (Operational Trial) followed by a Go/NoGo decision for ops deployment after Release Migration. If trial participants are satisfied with the results at the end of the trial: - MCP (Mandatory Cherry Picking) for en-route traffic will become a permanent operational procedure for these two units. - MCP for en-route will become a service available from NMOC to any ANSP who would like use it. It shall be noted that only ANSPs whose flow management/traffic management staff work with Occupancy Counts and are adept at solving short peaks with local STAM/TCM (Tactical Capacity Management) will have the necessary expertise to use it. An OPT session will be organised for this FB. Updated operational instruction for trial participants will be provided before migration date. Briefings to internal staff and to external trial participants.

FB598: ATFCM Domain improvements (4/5) Users impacted U8. AO or CFSP A1. CHMI Application impacted A10. NOP Change the time parameter for AOWIR RRP from “45 minutes before EOBT” Objective to EOBT. Before NM 17.5 the possibility for the AO to send an AOWIR to NMOC was limited at 45 minutes before EOBT. There is a need from Airspace Users to extend this period, especially in those Network situations where the number of impacting regulations is high. Description The change on the parameter for non tac/tac flights can facilitate the operations at Network level and at aircraft operators’ level. The parameter has been changed from “45 minutes before EOBT” to EOBT. Impact I2. Impact on Man-Machine interface. Impact description Edition date: 20/11/2013

There is not possibility to send an AOWIR as from the activation of the flight.



Service reference Safety assessment Operational deployment plan Users’ validation Documentation publication Training sessions

NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 ID S315 - Load and capacity management S2. FB has no impact on Safety D1. FB will be deployed in Operation along with the release migration. No OPT is planned for this FB. Information Notice and Release Notes. None

FB598: ATFCM Domain improvements (5/5)

Users impacted


Description

U1. Flow Manager (FMP) U3. Airspace User (Civil) U4. Airspace User (Military) U8. AO or CFSP U12. Internal NM A11. B2B Include RTFM in the EFD before SIT1 Currently, in the EFD messages, no information is sent about the impact of ATFM regulations on the flight before the Slot Issue Time (SIT1), i.e. 120 minutes before EOBT. When the flight is regulated earlier than SIT1, related EFDs sent before SIT1 mention that the flight is "Slot Allocated" but contain only the FTFM. In order to have a better view on the traffic predictions for the planning tools relying on the EFD messages, information about the impact of ATFM regulations on the flight will be available already before SIT1 (EOBT - 2 Hrs), according to the following: EFD sent more than 5 Hrs before EOBT: • Flight Model: FTFM • Flight Status: "Slot Allocated“ if already regulated EFD sent less than 5 Hrs before EOBT: • Flight Model: RTFM model if regulated, FTFM otherwise. • Flight Status for regulated flights: • Before SIT1: "Slot Allocated" • After SIT1: "Slot Issued" To avoid system overloads, an EFD will not be sent following a delay change of less than or equal 5 minutes. Furthermore an EFD will not be sent if the previous EFD was sent less than 5 minutes before. I3. Impact on clients’ systems.

Impact

Impact description


There is no modification in the format of the EFDs. The only change is for regulated flights: a new combination occurs between 5 hours and 2 hours before EOBT: • Flight Model: RTFM • Flight Status: "Slot Allocated” No change 5 hours before EOBT (FTFM + "Slot Allocated”) nor 2 Hours after EOBT (RTFM + "Slot Issued”).





Planned for Implementation in 2013-2014 ID S315 - Load and capacity management S4. Safety assessment to be performed or on-going D2. FB will be subject to a Pilot Phase (Operational Trial) followed by a Go/NoGo decision for ops deployment after Release Migration. The new feature will not be directly deployed with the NM17.5 migration, but instead will be initially subject to an ops validation (pilot phase) None None

5.3.10. Airspace Data Domain FB581: Airspace Data Domain improvements (1/2) This part (1/2) of FB581 will not be implemented with the Release migration in October 2013. It may be implemented via a patch after the Internal NM migration. Users impacted U12. Internal NM Application A4. CACD impacted Objective Reduce the incorrect processing of FAM messages in ETFMS The “FAM areas” are defined in ENV as AUAG Airspaces linked to Units of type EntryNode. Those AUAGs should correspond to a contiguous volume of airspace monitored by the EntryNode. Since AUAGs are composed manually based on a set of AUAs, and in addition AUA definitions can evolve over time, sometimes holes are left inside the AUAG volume. These holes can result in incorrect processing of FAM messages in ETFMS Description Inside the reference airspace volume, all gaps and holes detected by a geometrical calculation that are not included in the list of known intentional gaps and holes, are real erroneous gaps and holes. because This solution can provide a strong validation that produces blocking errors: inside the reference volume, every hole that is not an intentional one is by definition a real erroneous hole Impact I0. No impact for external users. Impact description Service reference Safety assessment Operational deployment plan Users’ validation Documentation publication Training sessions

No impact for external users. ID S334 - Airspace Data Management S3. FB increases Safety D1. FB will be deployed in Operation with the release migration. No OPT will be organised for this FB. The Airspace Data Operations Manual (available for National ENV Coordinators) will be updated. No

FB581: Airspace Data Domain improvements (2/2) Edition date: 20/11/2013



Users impacted


Objective

Description


NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 U7. Post-ops analyst U12. Internal NM A1. CHMI A4. CACD A7. Datawarehouse (NMIR) A11. B2B Deliver FAB Coordinator's Progress Report on the Functional Airspace Blocks RAD shall evolve to contain Functional Airspace Block and Regional RAD requirements. A naming convention has been agreed to accommodate those pan-European restrictions BLFAB: BALTIC FAB BMFAB: BLUE MED FAB CEFAB: FAB CE - FAB CENTRAL EUROPE DSFAB: DENMARK / SWEDEN FAB DUFAB: DANUBE FAB ECFAB: FABEC - FAB EUROPE CENTRAL IUFAB: UK / IRELAND FAB NEFAB: NORTH EUROPEAN FAB PEFAB: SOUTH WEST FAB (Spain / Portugal) I1. Impact on procedures. I2. Impact on Man-Machine interface. I3. Impact on clients’ systems. The FB is required for Statistics and trials/testing with FAB deployment. ID S334 - Airspace Data Management S3. FB increases Safety D1. FB will be deployed in Operation along with the release migration. Not required Airspace Data OPS manual under review. Not required

5.3.11. Correction and Tuning FB536: Provision of Departure data - 8 U3. Airspace User (Civil) U4. Airspace User (Military) Users impacted U12. Internal NM U0. Other (specify): CDM Airports Please choose in the following list (one or more): A1. CHMI Application A2. CIFLO, CIAO impacted A5. Flow management systems (Predict, ETFMS) A7. Datawarehouse (e.g. NMIR) Edition date: 20/11/2013




Objective Description Impact

Planned for Implementation in 2013-2014 A10. NOP Portal A11. B2B A13. NMVP Improve interface with CDM Airports by providing additional data. Collect TOBT & TSAT from CDM Airports and provide them to the AOs via CHMI, NOP portal, EFD data and B2B web services. Improve the processing of DPI messages. I2. Impact on Man-Machine interface. I3. Impact on clients' systems.

Impact description

The AOs will have two more data elements (TOBT and TSAT) for their own personal use. Less DPI messages will be incorrectly rejected.

Service reference

ID P3411 - Data distribution ID S315 - Load and capacity management


S2. FB has no impact on Safety D1. FB will be deployed in Operation with the release migration No OPT is planned for this FB. CHMI, NOP and B2B user manuals will be updated as well as The CFMU Flight Progress messages document as well as the DPI Implementation Guide. No

FB585: Reporting C&T for Release 17.5 U6. Management (eg crisis management, performance management) U7. Post-ops analyst Users impacted U12. Internal NM U0. Other (specify): Representatives of the EU Member states for the ATFM IR A5. Flow management systems (Predict, ETFMS) Application impacted A7. Datawarehouse In the scope of the ATFM IR, the statistics related to the Slot Adherence must be reviewed to take into account some particular cases; new counts will also be added. Objective In parallel new technical capabilities will be put in place to capture the saved delays in order to measure the NMPP 5.2 objectives related to the reduction of Network delays. This for internal use. The computation of the slot adherence statistics will take into account the two following particular cases: Description

• The problematic of the “Adjusted to the clock” flights which need to be filtered out of the regulated list and associated to the non-regulated list.

Impact

• The flights having a non-standard slot window. The real window has to be the reference instead of the standard -5/+10 minutes window. I1. Impact on procedures.

Impact description

The external users’ procedures may be impacted by the slight changes impacting the computation of the slot adherence statistics.





NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 ID A121 - Network Operations Monitoring S2. FB has no impact on safety D1. FB will be deployed in Operation with the release migration. No OPT will be organised for this FB. None None

5.3.12. Technical Blocks TB100: NOP map technology U1. Flow Manager (FMP) U3. Airspace User (Civil) U4. Airspace User (Military) U6. Management (eg crisis management, performance management) Users impacted U8. AO or CFSP U9. CAA, EASA U10. Airport U11. ARO U0. Other (specify): Public accessing the Public Portal Application A10. NOP Portal impacted Objective Improve the Map functionalities. Implement the needed technical improvements to allow future Map evolutions. First visible improvement in this release is reflected in the ATFCM Network Situation Static map by allowing zooming dynamically, solving the Description current label overlaps. This Technical Block replaces the FB560 (Real-time network situation displays). Impact I2. Impact on Man-Machine interface. Impact description Service reference Safety assessment Operational deployment plan Users’ validation Documentation publication Training sessions

Additional features in the navigation into the ATFCM Network Situation Static map ID P348 - Network Operations Portal S4. Safety assessment to be performed or on-going D1. FB will be deployed in Operation with the release migration. An OPT session will be organised for this FB. NOP Portal online help to be updated. The standard NOP Portal training to be amended to include this map evolution.

TB138: NOP HMI Customisation Users impacted U1. Flow Manager (FMP) Edition date: 20/11/2013



NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 U2. Airspace Manager (AMC) U3. Airspace User (Civil) U4. Airspace User (Military) U5. ENV data provider U6. Management (eg crisis management, performance management) U7. Post-ops analyst U8. AO or CFSP U9. CAA, EASA U10. Airport U11. ARO U12. Internal NM U0. Other (specify): NOP protected area users


Description

Impact for external

Impact description



A10: NOP Provision of features for a customisable NOP to the users of the protected NOP. This TB provides NOP users through the protected NOP some additional features to customise the NOP according to their specific usage. In addition to the existing possibility to customise the NOP main Page and the Flights and Counts application, this TB would allow customisation of the E-Helpdesk, Measures and IFPUV applications. I1. Impact on procedures. I2. Impact on Man-Machine interface. As the changes done for customisation purposes will persist on token basis, the organisation may have to draw procedures according to their own organisation. A professional NOP user holding a token will be able to change the appearance of some of the views retrieved by the NOP (for example, changing colors, changing the order of columns or hiding some of them). ID P348 - Network Operations Portal S4. Safety assessment to be performed or on-going D1. FB will be deployed in Operation with the release migration. An OPT session will be organised for this FB. NOP online help will be updated. None





5.4.

RELEASE 17.5.2

5.4.1.

NOS-01 - Coordinated Process for ASM/ATFCM FB594 : ASM Monitoring (part 2) (1/2) Internal NM Users impacted Application impacted Objective

Description

U7. Post-ops analyst A7. Datawarehouse (NMIR) Improve statistics and therefore the strategic plans on ASM/ATFCM processes. The data delivered includes providing a NMD restricted access to the last 5 years of AUP/UUP data and provide a NMD restricted access FUA (Flexible Use of Airspace) indicators as described in Section 7 of the ASM Handbook. The FB will provide to approved external users (via NMIR): • Access of AUP/UUP for the last 5 years • Access of EAUP/EUUP for the last 5 years • Access of traffic data for the last 5 years, both, flight plan data and radar data


• FUA KPIs calculation for the last 5 years. I0. No impact None ID A221 - Airspace Management (ASM) Processes S2. FB has no impact on Safety D1. FB will be deployed in Operation along with the release migration. No OPT is planned Internal NMD documentation will be updated. None

FB594: ASM Monitoring (part2) (2/2) Users impacted Application impacted

Objective

Description Edition date: 20/11/2013

Internal NM U6. Management (e.g. crisis management, performance management) A7. Datawarehouse (NMIR) Access to ASM archived data is required to fulfill the requirements of EC Regulation N. 691/2010 published the 29th July 2010, laying down a performance scheme for air navigation services and network functions. The access to data will support the measurement of the effective use of the civil/military airspace structures and KPIs defined in the Environment performance area. This KPI will be monitored in the first reference period (2012-14) and then measured in the second reference period (2015-2020) with appropriate targets. This Functional Block is the continuation of FB601 (NM17.5)




Impact

I0. No impact

Impact description

No impact for external users.


5.4.2.


ID A221 - Airspace Management (ASM) Processes S2. FB has no impact on Safety D1. FB will be deployed in Operation along with the release migration. No OPT is planned No documentation update. None.

NOS-41: Network Operations Plan FB591: NOP access to event information consolidation - Phase 1 Internal NM

Users impacted

U1. Flow Manager (FMP) U2. Airspace Manager (AMC) U3. Airspace User (Civil) U4. Airspace User (Military) U5. ENV data provider U6. Management (e.g. crisis management, performance management) U7. Post-ops analyst U8. AO or CFSP U9. CAA, EASA U10. Airport U11. ARO U12. Internal NM U0. Other (specify): All customers interested in any ATFCM event


A10. NOP Publication of all the Network related Events in a single location to: • Improve the visibility of the complete set of data on events information. • Increase efficiency of data-collection and dissemination (cost reduction).

Objective

• Reduce data duplication and increase data consistency. • Improve the quality of data management. • Earlier access to any NM known event.

Description

• Set the basis for supporting the rolling nature of events information. At a high level, from the NM perspective, an event is an activity that may have an impact on network operations shaping either demand or capacity or both. A tool is developed to provide access to all the Network related Events, via the NOP Portal, including following functionalities: • Regular loads of information from sources, including estimation of impact. • Data management and publication via lists (including calendar). • Automatic Notification of Suggested duplicates or Issues with data source




NETWORK MANAGER RELEASE NOTES Planned for Implementation in 2013-2014 interfaces: duplicates could come from different sources, from different users on the same source, from forgetful users on the same source, etc. In phase 1, sources are airport corner, ERNIP and possibly "manual" input. • Publication of Events and Events updates. • Initial set of reports on events taking place in specified geographical areas and/or during a specified period. • Querying and free text searching.

Impact

Impact description Service reference Safety assessment Operational deployment plan

Users’ validation

Documentation publication Training sessions


• Display on a MAP. I1. Impact on procedures. I2. Impact on Man-Machine interface. The aim is to evolve towards a single point of access “ATM Events repository” for all Network information; it will be a new dedicated area into the NOP Portal. This will require associating the different planning and coordination processes with events at network and local level. ID P348 - Network Operations Portal S4. Safety assessment to be performed or on-going D2. FB will be subject to a Pilot Phase (Operational Trial) followed by a Go/NoGo decision for ops deployment after Release Migration. D1. FB will be deployed in Operation along with the release migration. FB will be subject to a training period followed by activation on ops. None FB will be delivered on an internal NM test chain before being migrated on operations with NM18.0. Training material and NOP Portal help module None Training sessions will be planned by the end of 2013. None



6.


ABBREVIATIONS

ACC AD ADR ADS AFTN AIM AIRAC AIXM AMC AMON ANSP AO AOC AOLO AOWIR APR ARO ASM ATC ATFCM ATFM ATM AUA AUAG AUP B2B BIS BOC BOD BSR C&T CAA CACD CASTAR CBA CCAMS CDM CDR CE CFMU CFN CFSP CHMI CIAM CIAO CIFLO CIR CNL CRCO Edition date: 20/11/2013

Area Control Centre or Area Control Aerodrome Airspace Data Repository Airspace Data Service Aeronautical Fixed Telecommunication Network Air Traffic Flow Management Information Message Aeronautical Information, Regulation and Control Aeronautical Information Exchange Model Airspace Management Cell Airport Slot Monitoring Air Navigation Service Provider Aircraft Operator Airline Operational Control Centre Aircraft Operators Liaison Officer Aircraft Operator What-if Reroute Aircraft Position Report Air Traffic Services Reporting Office Airspace Management Air Traffic Control Air Traffic Flow and Capacity Management Air Traffic Flow Management Air Traffic Management ATC Unit Airspace ATC Units Airspaces Grouping Airspace Use Plan Business-to-Business Business Intelligence System Bottom-Of-Climb Bottom-Of-Descent Business Services Requirement Correction and Tuning Civil Aviation Authority Central Airspace and Capacity Database (new name of ENV) Computer Aided Synchronization Tool for Airspace Repositories Cost Benefit Analysis Centralised SSR Code Allocation & Management Cooperative Decision Making Conditional Route Central Europe Central Flow Management Unit Commercial Flight Number Computerised flight plan service provider Collaboration Human Machine Interface Collaboration Interface for AMCs Collaboration Interface for AO Collaboration Interface for Flow management position CFMU Interactive Reporting (now NMIR) Cancellation Message Central Route Charges Office Edition 3.5 [email protected] ©2013 The European Organisation for the Safety of Air Navigation (EUROCONTROL) p.54

EUROCONTROL Network Manager CSMC CSS CSST CSSUG CTOT CUA DCT DDR DEV DMEAN DNM DOF DPI EACCC EAD e-AMI EASA EAUP EC ECAC EET EFD EFPL ELS ENV EOBD EOBT eRAD ERNIP ETFMS ETO EU EUROCONTROL EUUP EVITA FAB FABEC FAM FB FDC FDMP FDPS FDU FIXM FL FMP FO FOS FPL FPR FRA Edition date: 20/11/2013


Call-Sign Management Cell Call-Sign Similarities Call-Sign Similarities Tool Call-Sign Similarity User Group Calculated Take-Off Time Common User Access Direct Route Demand Data Repository Development Dynamic Management of European Airspace Network Directorate Network Management Date of Flight Departure Planning Information European Aviation Crisis Coordination Cell European AIS Database Electronic Airspace Management Information European Aviation Safety Agency European Airspace Use Plan European Commission European Civil Aviation Conference Estimated Elapsed Time ETFMS Flight Data Extended Flight Plan Elementary Surveillance NM Environment System (former name of CACD) Estimated Off Block Date Estimated Off Block Time Electronic Route Availability Document European Route Network Improvement Plan Enhanced Tactical Flow Management System Estimated Time Over European Union European Organization for the Safety of Air Navigation European Update airspace Use Plan European Crisis Visualization Interactive Tool for ATFCM Functional Airspace Block Functional Airspace Block Europe Central Flight Activation Monitoring Functional Block Flight Data Contributor Flight Data Manager and Publisher Flight Data Processing System Flight Data User Flight Information Exchange Model Flight Level Flow Management Position Flight Object Flight Object Server Flight Plan message (ICAO format) Flight Profile Free Route Airspace Edition 3.5 [email protected] ©2013 The European Organisation for the Safety of Air Navigation (EUROCONTROL) p.55

EUROCONTROL Network Manager FTFM FTP FTPS FUA GAT HMI IATA ICAO ID IFPS IFPUV IFR IOP IR KPA KPI MCP MIL MILO MS MUAC NB NM NMC NMD NMIR NMOC NMPP NMVP NOP NOS NTS OAG OAT ODSG OPS OPT ORCAM ORM OSED OTMV PC PC PT R&D RAD REA REGUL REJ RMK RPL Edition date: 20/11/2013


Filed Tactical Flight Model File Transfer Protocol FTP Server System Flexible Use of Airspace General Air Traffic Human-Machine Interface International Air Transport Association International Civil Aviation Organization Identifier Integrated Initial Flight Plan Processing System IFPS Unit for Validation Instrument Flight Rules InterOPerability Implementing Rule Key Performance Area Key Performance Indicator Mandatory Cherry Picking Military Military Liaison Officer Microsoft Maastricht Upper Area Control Centre Nota Bene Network Manager Network Management Cell Network Manager Directorate NM Interactive Reporting (former CIR) Network Manager Operations Centre Network Manager Performance Plan Network Manager Validation Platform Network Operations Plan DNM Network OperationS unit Network Technical Systems (DNM) Official Airlines Guide Operational Air Traffic Operations and Development Sub-Group Operations Operational testing Originating Region Code Assignment Method Operational Reply Message Operational Service and Environment Description Occupancy Traffic Monitor Values Personal Computer Provisional Council Point : ENV data entity type Research and Development Route Availability Document Ready Message Regulation Reject Message Remark Repetitive Flight Plan Edition 3.5 [email protected] ©2013 The European Organisation for the Safety of Air Navigation (EUROCONTROL) p.56

EUROCONTROL Network Manager RRP RSA RTFM RVR SAT SDO SESAR SID SIMEX SIT SIT1 SJU SRD SSR STAM STAR TB TBD TCF TCM TOBT TOC TOD TOW TSA TSAT TSR TTA TTO UAC UK URL UUP VOLCEX VP



Rerouting Proposal Message Restricted Airspace Regulated Tactical Flight Model (by ATFM Measures) Runway Visual Range System Acceptance Test Static Data Operation Single European Sky ATM Research Standard Instrument Departure SIMulation and EXperiment (NM tool) System Integration Team Slot Issue Time 1 SESAR Joint Undertaking Software Requirements Document Secondary Surveillance Radar Short-Term ATFM Measures Standard Terminal Arrival Route Technical Block To Be Defined, Determined or Discussed Transponder Code Function Tactical Capacity Management Target Off Block Time Top-Of-Climb Top-Of-Descend Take-Off Weight Temporary Segregated Area Target Start-Up Approval Time Technical Services Requirement Target Time of Arrival Target Time-Over Upper Area Control Centre The United Kingdom Uniform Resource Locator Updated Airspace Use Plan Volcanic Ash Exercise Validation Plan


NETWORK MANAGER RELEASE NOTES

NETWORK MANAGER RELEASE NOTES

Suggest Documents

Cisco UCS Performance Manager Release Notes, Release 1.1.1

Cisco UCS Performance Manager Release Notes, Release 1.1.1

Release Notes

Release Notes

Release Notes for Cisco Router and Security Device Manager 2.5

HP Service Manager Release Notes software version 7.11

Release Notes for Cisco Router and Security Device Manager 2.5

Release Notes

Release Notes

Release Notes

Release Notes

Release Notes

Release Notes

Release Notes

Release Notes

Release Notes

Release Notes

Release Notes

Release Notes for Cisco Router and Security Device Manager 2.5

RES Workspace Manager 2012 SR3 Release Notes - RESguru ...

RES Workspace Manager 2012 SR3 Release Notes - RESguru

RES Workspace Manager 2012 SR1 Release Notes - RESguru ...

Release Notes for Cisco Router and Security Device Manager 2.5

RES Workspace Manager 2012 SR1 Release Notes - RESguru ...