Nop Portal Users Guide

EUROCONTROL CFMU
SUPPLEMENT TO THE CFMU HANDBOOK
NOP PORTAL
NOP PORTAL USERS GUIDE
Edition N: 2.0
http://www.cfmu.eurocontrol.int
Amendment date: 23 August -2010
EDITION 2.0.23 Edited & produced by the CFMU/User Relations and Development Bureau 2009 European Organisation for the Safety of Air Navigation (EUROCONTROL)
NOP PORTAL USERS GUIDE i
NOP Portal - User Guide Table of Contents

1. 2. 3. Disclaimer Changes and Updates The Portal 3.1. Purpose 3.2. Technical Prerequisites 3.2.1. Enabling Javascript 3.3. Login to the Protected Portal 3.3.1. Token 3.4. Self - Registration 3.5. Login to the Public Portal 3.6. Global Layout 3.7. Printing from the Portal 4. Header 4.1. Timeline Navigation Concept 4.2. Header Buttons 4.2.1. Global Help 4.2.2. Setting Preferences 4.3. Searching the Portal 4.3.1. Search Text 4.3.2. Search Results 4.4. Logout 5. Portlets and Detached Views 5.1. Portlets General Features 5.1.1. Portlet Definition 5.1.2. Portlets Scope 5.1.3. Portlet Availability 5.1.4. Contextual Help 5.2. Detached Views 5.2.1. Error Messages 5.2.2. Printing mode 6. Portlets from A to Z 6.1. Access Request 6.2. ACC Info
Edited & produced by the CFMU/User Relations and Development Bureau 2009 European Organisation for the Safety of Air Navigation (EUROCONTROL) - V2.0.23 - 23/08/2010 - page /172
1 2-3 4 4 4-6 6-8 8-11 11 11 11-13 13-14 14-15 16 16-17 17 17-18 18 18-19 19 19-21 21-22 23 23 23 23-24 24-25 25-26 26-27 27-28 28-29 30 30 30-31
NOP Portal - User Guide

6.3. AIM 6.3.1. Querying AIM from within the Detached View 6.4. Airport Info 6.5. Airspace Data 6.5.1. Airspace Data - Traffic Volume Query 6.5.2. Airspace Data - Aerodrome 6.5.3. Airspace Data - Route 6.5.4. Querying Airspace Data from within the Detached View 6.5.4.1. Traffic Volume 6.5.4.2. Traffic Volume Set 6.5.4.3. Aerodrome 6.5.4.4. Aerodrome Set 6.5.4.5. Air Route 6.5.4.6. Route Catalogue 6.6. Airspace Structure 6.7. ANM 6.8. ATFCM Events 6.8.1. Consulting ATFCM Events per Category 6.8.2. Consulting the Description of an Event 6.8.3. Consulting Scenarios associated to an Event 6.9. ATFCM Scenarios 6.9.1. The ATFCM Scenarios Detached View 6.9.2. Consulting a Scenario Details 6.10. ATFCM Network Situation 6.10.1. Viewing the ATFCM Network Situation in the Tactical phase 6.10.2. Viewing the ATFCM Network Situation in the Post-Operations phase 6.10.3. The (static) ATFCM Network Situation Detached View 6.10.4. ATFCM Network Situation Interactive Map 6.10.4.1. The Map Menu Bar 6.10.4.2. Tools - Location 6.10.4.3. Tools - Area 6.10.4.4. Tools - Levels 6.10.4.4.1. Tools - Level Ruler 6.10.4.4.2. Setting the Flight Levels on the Map
31-32 32-33 33-36 36-37 37-38 38-39 39 39-41 41-42 42-43 43-45 45 45-47 47-48 48 48-49 49-50 50-51 51-52 52-53 53 53-55 55-56 56-57 57-58 58-59 59-60 60-61 61-62 62-63 63-64 64-65 65-66 66

6.10.4.5. Tools - Time 6.10.4.6. Tools - Queries 6.10.4.6.1. Plotting Flights on the Map 6.10.4.6.2. Displaying Regulations from the Map 6.10.4.6.3. Plotting CRAM on the Map 6.11. ATFCM Situation Data 6.11.1. The ATFCM Situation Data Detached View 6.11.2. Digging into the Delay Causes 6.12. ATFCM Network Daily Plan 6.12.1. The Static Daily Plan 6.12.2. The Interactive Daily Plan 6.13. Calendar 6.13.1. Calendar in details 6.14. CFMU ATFCM Reports 6.15. CFMU News 6.16. Contingency 6.17. CRAM 6.18. EAD 6.19. EAUP 6.19.1. EAUP Details - ATS Route and CDR Type 1 Closure 6.19.2. EAUP Details - CDR Type 2 Availability 6.19.3. EAUP Details - Level 1 RSA Allocations 6.19.4. EAUP Details - Level 2 RSA Allocations 6.19.5. Compare with Predecessors 6.20. E -conference 6.21. Events and Meetings 6.22. F A Q 6.23. Flights 6.23.1. Querying Flights from the Detached View 6.23.1.1. ARCID List 6.23.1.2. Flight List 6.23.1.2.1. Aerodrome 6.23.1.2.2. Aerodrome Set 6.23.1.2.3. Aircraft Operator
66-68 68-70 70-71 71-72 72 72-73 73-74 74-75 75-77 77-78 78-82 82-84 84-88 88-89 89-90 90 90-91 91-92 92 92-93 93-94 94-95 95-96 96-97 97-98 98 98-99 99 99-101 101-103 103 103-107 107-108 108-110

6.23.1.2.4. Airspace 6.23.1.2.5. Point 6.23.1.2.6. Regulation 6.23.1.2.7. Traffic Volume 6.23.1.3. Flight Details 6.23.1.3.1. Details 6.23.1.3.2. Point Profile 6.23.1.3.2.1. Elaps.Time PT Profile 6.23.1.3.2.2. Act. Time PT Profile 6.23.1.3.2.3. Elaps. Time AS Profile 6.23.1.3.2.4. Act. Time AS Profile 6.23.1.3.3. Flight History 6.23.1.3.4. Operational Log 6.23.1.3.5. Alternate Routes 6.23.1.3.6. Messages 6.23.1.4. Plotting flights on the Map 6.24. IFPUV 6.24.1. Free Text Editor - FPL Validation 6.24.2. Free Text Editor - Propose Routes 6.24.3. Structured Editor - FPL Validation 6.24.4. Structured Editor - Propose Route 6.25. Main Reports 6.26. Measures 6.26.1. Regulation 6.26.2. Rerouting 6.26.3. Querying Measures from within the Detached View 6.26.3.1. Regulation List 6.26.3.2. Regulation Details 6.26.3.3. Regulation Delays 6.26.3.4. Rerouting List 6.27. Network Axis Management 6.28. Network Headline News 6.29. Network Operations Strategic Plan 6.30. NOP Processes
110-111 111-112 112-113 113-114 114 114-117 117-118 118-119 119-120 120-122 122-123 123-124 124-125 125 125-126 126-127 127 127-129 129-132 132-135 135-138 138 138-139 139-140 140 140-141 141-142 142-144 144-146 146-147 147 147-149 149 149-150

6.31. NOP Updates 6.32. Planning of ATM Network Changes 6.33. Portal Assistance 6.34. Portal Release Information 6.35. Pre-validation exercises 6.36. RAD 6.37. SAFA 6.38. Training 6.39. All Other Portlets 7. Case Studies 7.1. Messages 7.2. AOWIR 8. 9. Download the Manual Glossary 150 150-151 151-152 152-153 153 153-154 154 154 154-158 159 159 159-160 161 162-165
NOP Portal - User Guide 1 Disclaimer
Access Restrictions / Single Sign On to CFMU Applications

It should be noted that the Single Sign On(*) has been enabled for the following applications:

CCMS Web (CFMU Claims) CIR (CFMU Interactive reporting) CENTRA (CFMU Training)
(*)- Single Sign On (SSO) allows users to access the application without re-authentication. However, this is of course subject to the user subscribing to the relevant service.
2009 European Organisation for the Safety of Air Navigation (EUROCONTROL). All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of EUROCONTROL.
Edited & produced by the CFMU/User Relations and Development Bureau 2009 European Organisation for the Safety of Air Navigation (EUROCONTROL) - V2.0.23 - 23/08/2010 - page 1/172
NOP Portal - User Guide 2 Changes and Updates
Document Version: 2.0 Online Revision Version: 23 Last Update: 23/08/2010 Date Section 23/08/2010 Portlets 17/08/2010 Flight Details 17/08/2010 Case Studies 08/06/2010 Technical Prerequisites 07/06/2010 02/06/2010 Flights 31/05/2010 Fights Details 31/05/2010 Portal Release Information 27/05/2010 Network Axis Management 27/05/2010 Airspace Structure 11/05/2010 EAUP 24/03/2010 24/04/2010 Flights 23/03/2010 IFPUV 23/03/2010 Flights 18/03/2010 Portlets 17/03/2010 Portlets ATFCM Scenarios / Daily Plan 29/10/2009 ATFCM Network Situation 20/10/2009 ATFCM Network Situation 05/11/2009 12/10/2009 ATFCM Network Daily Plan 09/10/2009 ATFCM Network Situation 09/10/2009 02/09/2009Glossary 02/09/2009Flights 09/07/200909/07/2009AIM & ANM 18/06/2009 Portal 13/03/2009 Help 13/03/2009 Portlets 25/02/2009 17/02/2009 Glossary 16/02/2009 Airspaces 16/02/2009 Contingency 13/02/2009 Flights Detail Airport Info added Section Updated Section updated Section updated EAUP and Flights Sections updated Section updated Section updated New Portlet New Portlet New Portlet Corrections in the Compare function Removed reference to the former CIA Section updated Section updated Plotting flight from the flight list - addition SAFA added EAUP added Sections updated Section updated Section updated Section updated Section updated Updated the CRAM, ... Definitions added Section updated Printing mode added go (Section 6.23) go (Section 5.2.2) go ('General' in the on-line documentation) go (Section 6.10) Link go (Section 6.4)
go (Section 6.34) go (Section 6.27) go (Section 6.6) go (Section 6.19.5)
go (Section 6.23) go (Section 6.24) go (Section 6.23.1.4) go (Section 6.37) go (Section 6.19)
New messages highlighted Printing improved go (Section 3.7) User assistance updated ACC Info added go (Section 6.2) Various typo's corrected Definitions added Traffic Volume & Traffic go (Section Volume Set pages completed 6.5.4) Set Portlet scope to TACTICAL only New screenshots captured go (Section Elements from CIA User Guide 6.23) incorporated
NOP Portal - User Guide 3 The Portal
3.1 Purpose
What is the purpose of the NOP Portal?
The NOP Portal aims at facilitating the CFMU Users access to all kinds of dynamic data and operational information in a consolidated way. Information is displayed according to the ATFCM phases: Strategic, Pre-tactical, Tactical, & Post Operations. The ultimate goal is to facilitate decision making for all ATFCM actors by sharing the most up to date view on the Network Operations situation along the ATFCM cycle (plans, events, scenarios, real-time information on flights and measures, etc.).
Objectives
The NOP Portal achieves the following objectives, as defined in the DMEAN Concept of Operations: 1. 2. 3. 4. Reflect the ASM / ATFCM decision status at the time they have been taken; Enable a common understanding of the Network situation; Present potential disturbances that could impact the Network and that could induce appropriate actions for risk mitigation; Assist Airspace Users to take their operational decisions
5. Assist Planners to build their local ATM plans and adjust them along the ATFCM phases, in full mutual coordination. All in all, the NOP Portal is the enabler of the operational CDM processes supporting ATM in Europe.
Content management
The NOP Portal is updated dynamically according to operational needs. This means that the frequency of updates may be seasonal, daily, or ad-hoc in real-time depending on the nature of the information. The publication cycle of the operational information follows the principles described in the CFMU Basic Handbook / ATFCM User Manual. The NOP Portal content is managed by a CFMU NOP office team for general and strategic information during office hours and by the CFMU operations teams on duty for the pre-tactical and tactical information.
Evolutions
The NOP Portal is evolving on a continuous basis. It is intended to extend progressively its functionalities to accommodate users requirements and to follow the overall evolution of the ATFCM Network Operations towards a more dynamic management of capacity. The use of state-of-the-art technologies allows the fast implementation of new features (additional portlets, navigation updates, etc.). It is therefore intended to deliver short term improvements in the portal layout several times across the year independently of the CFMU releases development cycle. In the medium term, evolutions are foreseen to allow content customization per category of users, content personalization by the end-user, and to integrate new collaboration tools in support of the CFMU CDM (Collaborative Decision Making) processes. The roadmap for the NOP Portal evolutions will be established in conjunction with the CFMU users groups.
3.2 Technical Prerequisites

The Portal will work best with Internet Explorer (version 7) and Firefox (version 3.6 and above) on a high resolution screen. The ideal display size would be 1600x1200. You will also need a recent Flash plugin installed (minimum 10)- check your current configuration on: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_15507 (http://www.macromedia.com/software/flash/about/)

You can also get the most recent version from http://get.adobe.com/fr/flashplayer/. (http://get.adobe.com/fr/flashplayer/)
Configuration Details
1. 2. The Portal will work best with Internet Explorer (version 7 - MSIE7) and Firefox (version 3.6 and above). In case you are using Internet Explorer 8 (MSIE8), some Portal feature may not work properly. We therefore suggest to turn the Compatibility View on (in the Tools Menu):
3.
To check your version of Internet Explorer, simply follow these steps: 1. Open your browser and click Help from the main menu, then click the About Internet Explorer menu item. 2. In the dialogue box that appears, look for the word Version and beside you will find a number, this is your browser build version (as shown below). Click OK to close the dialogue box.
4.
To check your version of Firefox, simply open your browser and click Help from the main menu, then click the About Mozilla Firefox menu item.
5. The ideal display size would be 1600x1200. To check or change your display settings (this is for WIndows XP - the procedure might vary depending on your Operating System): 1. Click the Start button on the bottom left of your computer to display the Start menu. Choose the Control Panel option from the right side of the Start menu. The Control Panel window will open onto your desktop.
2. Double-click the Display icon from the Control Panel to open the Display Properties dialog box. You can then select the Settings tab from the top of the dialog box. 3. Slide the bar under the Screen resolution setting of the Display Properties dialog box to decrease or increase the screen resolution. The chosen resolution will be displayed under the sliding bar. 4. Optionally, use the Color quality drop-down list to choose the type of quality you want your computer to use. You can choose to have the color quality be "Medium," "High" or "Highest. 5. Click the Apply button at the bottom of the Display Properties dialog box to apply the settings. If you are not happy with the settings you can change them as instructed in the steps above. 6. Choose the OK button when you are happy with your display setting changes. The Display Properties dialog box will close and the settings will be saved. 6. You will also need a recent Flash Player plugin installed (minimum 10). Check your current configuration on http://kb.adobe.com/selfservice/viewContent.do? externalId=tn_15507 You can also get the most recent version www.adobe.com/shockwave/download/download.cgi? P1_Prod_Version=ShockwaveFlash (http://www.adobe.com/shockwave/download/download.cgi? P1_Prod_Version=ShockwaveFlash). Note that administrator privileges may be required to carry out the installation. Your browser should be configured to run JavaScript. This is usually the case by default - but some users or organisations disable it.
7.
3.2.1Enabling Javascript
JavaScript Test

If you are connected to the Internet, click here to run a quick and simple test. If you just saw an pop-up alert box like the one shown below, your computer should be able to use javascript.
If you just got the page you see here now, with no pop-up box first, your browser doesn't support JavaScript. Here are some solutions for this problem:

If you are using an older browser, upgrade to a newer version. If you have a fairly new browser (version 4 and above), check to determine whether javascript is enabled:
3.2.1.1 Internet Explorer:

1. 2. 3. 4. Select Tools, then Internet Options from the browser menu. click on the Security tab at the top of the options panel. Click on Internet at the top of the panel, then move the slider near the bottom of the panel to "Medium" to allow Javascripts to run. Click on the Apply button to save this setting.
3.2.1.2 Mozilla (Firefox):

1. 2. Select Tools, then Options from the browser menu. In the box that appears, select Web Features.

3. Check the box to enable Javascript.
Note: In some cases the administrative rights on a given computer may be restricted. If you can not manage to change the above settings, please ask your IT Department for assistance.
3.3 Login to the Protected Portal

The NOP Protected Portal contains information for clients involved in ATM operations and is only available after acceptance of the CFMU Terms and Conditions. It is accessed via RSA SecureID - users need to log in via their CFMU Token . Note to first time users of the NOP Portal The CFMU has by default allocated access to all token users. The same UserID and Password as for the other applications shall be used when logging in to the Portal.
1. Access to the Portal

The NOP Portal is accessible from the CFMU public website homepage, from a button in the CFMU Applications section if the right side links section.
2. The login screen


This button opens the login page to the CFMU Applications:
If you see the above screen, you can skip point 3. below and go directly to point 4.
3. Alert Messages
However, depending on your system's configuration, you may get the alert message below (the look and wording may differ from one browser make and version to another):
It is perfectly safe to continue and open the website - this is a known issue and will be resolved in the near future so that windows will not show anymore. Another message is then likely to pop up:
10
Again, it is perfectly safe to continue - besides this message might never show, as it is resulting from your personal Internet settings...
4. Filling in the login form

Insert you UserID (e.g. p0abc, r1ab0, etc - in lower case) in the UserName field, along with the password generated by your token in the Passcode (RSA SecurID) field. If the login fails, it is strongly recommended to clear your Browser cache (for Internet Explorer, in Tools > Internet Options > Delete Temporary Internet Files) before attempting to login again.
5. Role and Domain Selection

You should now see the CFMU Login Page. Depending on your authentication level, the procedure will be slightly different but driving to the same concept: entering your UserName in the first field, then typing in your Passcode (or Password) in the relevant field. In case you can have access to several roles, next comes a screen prompting you to select a Role and a Domain. The proposed options may vary according to your access rights - all you need is to select the one that applies to you and/or to the task you wish to perform with the Portal. In case your UserName is associated to a single role, you will not see this and will go directly to the Portal.
Click on the Go Sign In button to get directed to the Portal default page. When successful, you should be able to view the portal main view in Tactical phase
NOP Portal - User Guide 3.3.1Token

Although Hardware token do exist, only Software token will be presented here.
11
In order to get access to the Protected Portal, you will need to get the necessary credentials. The most typical way is currently by means of a Token. A Token is a piece of software made available to a user and installed on one single identified computer. If you do not already have one, you can ask (Section 6.1) the CFMU Customer Support.
3.4 Self - Registration This feature is not implemented yet - It will be documented when the access will be available.
3.5 Login to the Public Portal

The NOP Public Portal contains information to assist the CFMU clients involved in ATM operations. However, some elements which are subject to a service agreement are only accessible from the NOP Protected Portal (Section 3.3). The NOP Public Portal is only available after self-registration.
1. Access to the Portal

The NOP Portal is accessible from the CFMU public website homepage, from a button in the CFMU Applications section if the right side links section.
2. The login screen

This button opens the login page to the CFMU Applications:
12
If you see the above screen, you can skip point 3. below and go directly to point 4.
3. Alert Messages
However, depending on your system's configuration, you may get the alert message below (the look and wording may differ from one browser make and version to another):
It is perfectly safe to continue and open the website - this is a known issue and will be resolved in the near future so that windows will not show anymore. Another message is then likely to pop up:
Again, it is perfectly safe to continue - besides this message might never show, as it is resulting from your personal

Internet settings...
13
4. Filling in the login form

In case you already are a Self-Registered user, you will simply need to insert your UserID (the email address you provided when you first registered) and your password and click on the Sign In button to get directed to the Portal default page. In case you are not yet registered, please follow the instructions described in the Self-Registration (Section 3.4) section of this package. When successful, you should be able to view the portal main view in Tactical phase
3.6 Global Layout

The NOP Portal layout consists in a Header (that manages the navigation) and 5 main areas, which correspond to the ATFCM phases:

Strategic Pre-tactical Tactical Post-Operations Resources (general reference information, not specifically related to any ATFCM phase).
More information of the ATFCM phases in the Timeline Navigation Concept (Section 4.1). The NOP Portal layout is consistent across all the pages to facilitate users navigation. For instance, News and Calendar are always displayed at the top right, ATFCM Messages at the top left, the main information of the period at the top centre, the ATM functions at the middle right, and the collaboration functions at the bottom centre. The overall layout is summarised below.
14
Each Portal main page is made of Portlets: individual content boxes each with its own title bar displaying text, images, links or data dynamically fed by the CFMU back-end applications (ETFMS, IFPS, DWH,...) or by the Portal content editor named WIND. Each portlet can be collapsed or expanded by means of or buttons in the Portlet title bar. Your setup will be saved within your browser settings, and restored if you use the same browser for another session (even after reboot). The layout settings will later be part of the Users Preferences (Section 4.2.2), allowing the layout settings to be restored on any browser and computer where you will log in. In a similar way, the button will open a Contextual Help (Section 5.1.4) window.
3.7 Printing from the Portal

A. Printing from the Main View This may differ from each make and version, but is basically obtained under the "File..." and then "Print ..." function of your browser. Consider having a look at the additional setting capabilities of your configuration to select more appropriate (combination of) settings where relevant:
the Properties linked with your printer and printer's driver of your printer
15
the Page Setup linked with your browser
B. Printing from a Detached (Section 5.2) View Since no toolbar is present in the detached view, you will need to hit the <Ctrl> and the <P> keys of your keyboard to invoke the print dialog box. You can beforehand specify the display mode of the detached view, using the Display toggle button located in the header, right after the right Set button.
This is the setting by default - the Screen mode. The header is kept visible at all times, and the vertical scrolling only affects the data tables. Click on the icon to toggle in the Print mode. The Print mode is used when you want to keep the header and the data together in one piece - typically for sending the whole content of a page to a printer. Click on the icon to toggle in the Screen mode.
Consider having a look at the additional setting capabilities of your configuration to select more appropriate (combination of) settings where relevant:

the Properties linked with your printer and printer's driver of your printer the Page Setup linked with your browser (more specifically the orientation of the paper: Portrait or Landscape) Please note that, due to their nature (they are rendered with the Flash plugin) the graphical elements will most probably not print as you may expect. This issue is recognised and we endeavour to solve it as soon as feasible. This is the case for the ATFCM Network Situation, the ATFCM SItuation Data, the ATFCM Network Daily Plan and the Calendar.
NOP Portal - User Guide 4 Header
16
4.1 Timeline Navigation Concept

This is the Header of the Portal, from which you can navigate across the different areas of the Portal.
The Timeline features 4 different Phases tabs, based on the ATFCM cycle: Post-Operations, Tactical, PreTactical and Strategic. Each covers a specific time span, as outlined below (D being the current date):

Post-Operations: D+1 at 00:00 onwards Tactical: D (00:00 to 24:00 UTC) PreTactical: D-6 to D-1 inclusive Strategic: D-12 months to D-7 days inclusive
These tabs allow you to navigate from one Phase to another. In addition, the selected tab rises to provide a visual indication of where you stand in the ATFCM cycle. A fifth tab is featured as well, opening the Resources page containing reference material not linked to time.
Navigate in Time
The Portal opens by default with the Tactical phase selected. A first way to change from one phase to another, and see the Portal content from a different time perspective, is by means of the Date Picker, to be found in the Target Date pane as shown in the red box below.
Clicking on the
icon opens the Date Picker.
The Date Pickers behaves as you may expect from its layout, the left and right arrows going one month back or forth, and the square recalling the current date.
Once a date is clicked, the Date Picker vanishes and the Target Date pane shows, and the Date field (with the pale green background) is updated with the selected value - in this example, November 14th, 2008. Note that the Target Date has not been changed yet. You need to first click on the blinking Set button to change it to the selected value (red outline).

Doing so updates the Target Date and resets the Date field.
17
Note that you can also type the next target date directly in the Date field, following the DD/MM/YYYY format (and confirm with the Set button).
4.2 Header Buttons

Depending on the user role and profile, a number of buttons are available to provide additional functionalities to the Header.
HELP: opens the Global Help pages (All users) PREFERENCES: opens the Preferences Editor - detailed below (All users) VERSION: shows the current version of the Portal (Developers) WIND: opens the NOP Portal content editor (Contributors) VIEW: shows the Publishing workflow (Contributors) The two orange buttons (VIEW and WIND) are actually reserved to Portal Contributors. You may therefore not see them when you login to the Portal - this is simply because you will not need them.
4.2.1Global Help
A global Help function is made available from the header:
Clicking on the Help button opens a pop up window, giving access to a comprehensive Help document. A complete navigation system allows the user to search, browse, bookmark and print any page within the Help system.
18
Contextual Help (Section 5.1.4) is also available from each portlet, which directly opens the relevant Help page.
4.2.2Setting Preferences
Clicking on the PREFERENCES button will open the Preferences Settings
The Time direction option sorts the Phase tabs from the past (on the left side) to the far future (on the right side) as shown below:
On the other hand, the Workflow direction reflects the logical sequence in an operational perspective: planning ahead (Strategic), refining the plan (PreTactical), operating (Tactical) and finally assessing results (PostOperations).
NOP Portal - User Guide 4.3 Searching the Portal

The Search function is located in the top right corner of the Header in the Main View..
19
Type in your query in the light green text field and click on the SEARCH button to open a Search Detached View listing all the found matches. The query is case insensitive, and can be one or several words separated by spaces. You can also directly click on the SEARCH button to open the Detached View and launch your query from there.
4.3.1Search Text
Definitions
In order to make the best use of the Search function, here are a few definitions as how the Portal considers your queries:
4.3.1.1 Text
A Text is a sequence of one or more Items, separated by a space. Example: "a collection of words" +single_word -another_single_word one_last_word
4.3.1.2 Item
An Item is a group consisting of an (optional) sign in from of a Term. Example: +single_word or -"first_word second_word"
4.3.1.3 Term
A Term is a single word, or a collection of words within opening and closing double quotes. The quotes are telling the system that the space between the words is not to be interpreted as a separator - ore more simply, that the text string between the quotes is the entity for which you are searching a match. Example: "first_word second_word third_word"
Searching for Text

If an unsigned term matches a keyword with a Damerau-Levenstein distance of at the most 2, the application considers this term as a match (effectively, the search algorithm allows the user up to 2 spelling mistakes) and, depending on the result of the matching process of signed terms, the document will be added to the search result.
Refining the Search

Additional features allow you refine your search:
the "+" sign right in front of the term: the related term must match a keyword in exactly the same spelling, baring letter casing the "-" sign: if a keyword exists that matches the related term then the whole document is struck from the set of matching documents
4.3.2Search Results
The Portal Search Detached View lists all the entries matching the searched term(s).

If the search was initiated from the NOP portal header, the results are displayed in a new search window. If the search was initiated from the search window, the search window is refreshed with the results. A color coding tells you the quality of the found match:

20
a partial match is indicated with an orange bullet: a full match is indicated with a green bullet:
See below an example with the query 'EBBR EDDY':
This tells you that 15 matches were found in 5 FCUs: ATFCM Events, Country, etc. Notice the two green expand boxes , indicating that they contain one or more full match. The fully expanded view looks like this:
21
Drilling down information

Move your mouse over a result bullet to reveal the matching keyword(s) and scoring:
In similar fashion, move your mouse over a title (light blue link) to get its summary, providing there is something to show. As a matter of fact, the tooltip is not available in all FCUs.
4.4 Logout
The Logout function is located in the top right corner of the Header. It is part of the User Credentials module, showing the user ID with which you have logged on the Portal.
22
This is for display only, you cannot directly edit the content of this field. The only possible action here is to click on the LOGOUT button, which will terminate your Portal session in a clean way, close the Portal window and bring you to the CFMU Public Website homepage.
NOP Portal - User Guide 5 Portlets and Detached Views
23
5.1 Portlets General Features 5.1.1Portlet Definition

A portlet is a window providing a synthetic piece of content on a portal page. This content may be static, or dynamic with interfaces for dialogue with the user, and with data/graphical information/transactions provided by back-end applications. This window is configurable within the portal, and gives access to more detailed information: tools and applications, news, reference material, web pages. In the Portal, the Portlets are grouped by nature and usage, as explained in the Global Layout (Section 3.6) section.
There are two buttons in the Title bar, one collapsing or expanding the portlet to respectively its content, and the other to call a Contextual help (Section 5.1.4) window.
reveal or
hide
A portlet will typically show a very synthetic rendering of the data, and whenever relevant present some basic navigation, filtering or querying mechanism to facilitate the retrieval of more detailed information. This information is presented through a pop up window called Detached View (Section 5.2) in the context of the Portal. Several detached views can be left open at a time, for comparison purposes or for later reference.
5.1.2Portlets Scope
Every Portlet does not show on all pages. Depending on its scope, it will be displayed according to the ATFCM Phase in which the Header is set.
Portlet Availability Matrix

The table below shows the default settings for the Portlets presence in each of the Phases. Resources Access Requests ACC Info AIM Airport Info Airspace Data Airspace Structure AIS Agora ANM ATFCM Daily Plan ATFCM Events ATFCM Network Situation
PostPreTactical Strategic Operations Tactical

ATFCM Scenarios ATFCM Situation Data Calendar CFMU ATFCM Reports CFMU Developments CFMU Handbook CFMU Interactive Reporting CFMU News CFMU Operations Overview Charts Claims CODA Contacts Contingency CRAM EAD European AUP/UUP E-conferences Events and Meetings FAQs Flights IFPUV Main Reports Measures Network Axis Management Network Headline News Network Operations Strategic Plan NEVAC NOP Process NOP Updates One Sky Online Planning of ATM Network Changes Portal Release Information Portal Assistance Pre-validation Exercises RAD RVSM SAAM SAFA Skyview Statfor Training
24
5.1.3Portlet Availability
It is of importance to understand that not all Portlets are available in every ATFCM Phase. Whenever irrelevant, they simply do not appear on the screen. This is the case for the RAD portlet, not showing in Post-Operations. In a similar way, CIR will not appear in Strategic. It may also happen that a Portlet is present (showing the border and title bar), but displays no content. In this case, a message will tell the reason for the absence of data, as for instance (the exact wording may vary between Portlets, but the overall meaning will be the same):
The [name of the Portlet, for instance "Network Daily Plan"] is currently not yet available : this

means that the data is not available yet for the context (day and/or time) in which it is requested.
25
You are not authorized to see [name of the Portlet, for instance "Flights"]: this means that your profile does not grant you access to some restricted information. Data is no longer available: this means that the requested data is no longer accessible from the Portal.
This list is not exhaustive, but as a general rule the displayed message will be such as to make clear the cause of the data unavailability.
5.1.4Contextual Help
Each portlet has its own contextual Help page, which can be opened at any time by clicking on the Help button located in the title bar.
Each Help page provides, whenever relevant, links to other concepts of interest, in the form of See also links as shown below, taken from the ATFCM Events page.
Should it not be sufficient, the whole navigation system (Table of Content, menu buttons and toolbar) is available as well to provide every possible mean to dig for additional information.
26
5.2 Detached Views

Detached Views come in different sizes and layouts - depending on their content - but with always the same purpose:

provide additional information to what was summarized on the parent Portlet allow to further dig in the data by means of elaborate querying.
27
Detached Views appear under the same NOP header reminding that they are issued from the Portal - be it on your screen or when printed. The header may also display the name of their portlet of origin when relevant. A Target Date selector is sometimes also present in the header, to modify the dates for which queries can be launched. Navigation tabs and query areas typically reside at the top of the window, whereas the body content can be of various nature:

messages lists links etc.
Whenever relevant, one -or more- query areas allow further filtering or sorting operations on the current query result, or the launch of new queries within the same context.
Loading data - Waiting time

Some queries can put a significantly heavy load on the Portal server, and take some time to be calculated and presented back in your browser. To provide a strong visual clue that your computer is indeed waiting for a response from the server and not simply frozen, the classical hourglass pointer has been replaced with a light indigo transparent overlay, telling you that your query is being processed.
5.2.1Error Messages
When a query can not be performed, the Detached View window freezes and is shaded with a light red transparent overlay indicating that an error was encountered. A pale yellow Alert box also appears, detailing the cause of the error, and if possible providing information on how to solve the problem. You need to click on the OK button to close the Alert box, unfreeze the window and resume working.
In the above example, the query was launched with no data in the Airspace search field - while it is a mandatory field which must contain at least 1 alphabetic or numeric character. In the other example below, the message tells you that the requested service is momentarily not available.
28
5.2.2Printing mode
A Display toggle switch is present in the header of a Detached View displaying large tables (like i.e. in Flights, Airspace Data, ...) This button switches between the change mode. Screen mode (set by default) to the Print mode - simply click on it to
Screen Mode
The vertical scrolling only affects the data tables. This allows the table headers to be visible at all times, for an easier on-screen reading.
This setting is however ill-suited for printing, since it only prints what is visible in the window - and in some cases only one of the frames (the header OR the table).
Print Mode
This mode is used when you want to keep the header and the data together in one piece - typically for sending the whole content of a page to a printer. See how the scroll bar on the left of the image now encompasses the whole window:
29
NOP Portal - User Guide 6 Portlets from A to Z
30
6.1 Access Request

Typical Scope:
This Portlet has been designed for requesting the subscription of a CFMU Service. It covers in particular the subscription of a "CFMU Access Service" which in turn provides access to a CFMU Application, such as:

NOP Portal CIR CCMS-Web the portfolio of CHMI applications etc.
6.2 ACC Info

Typical Scope:
This Portlet allows you to view all the details for the queried ACC. An autosuggest mechanism will propose you, in a range gradually narrowing as you type in, all matching ACCs identified in the ACC plan whose display period include the current portal UTC date.
Detached View
The ACC Detached View displays the ACC info for the selected ACC.
31
6.3 AIM
Typical Scope:
CFMU Operations send an AIM (Air Traffic Flow and Capacity Management Information Message) to inform the Aviation community whenever they consider it relevant. These AIMs are also accessible through an AFTN address, via the CHMI Applications. A simple table lists the most recent valid AIMs for the selected Target Date, giving as title a short description of the message along with its released date and time. Note the More link at the bottom of the Portlet, which opens a Detached View listing all AIMs valid for the

selected Target Date.
32
Highlights
Newly released AIM messages are displayed against a colored background, to draw the attention of the user.
This highlight disappears when one of the actions below are performed:

You manually refresh the Portal - and as a result reset the 15 min. timer You open the highlighted message (or any other message displayed in the Portlet).
Opening an AIM
The light blue color of the AIM titles indicate a hyperlink opening a Detached View with the full AIM content, as shown in the example below.
6.3.1Querying AIM from within the Detached View

The AIM Detached View lists a number of all AIMs matching a given query (by default, for the currently set Target Date).
33
Query
The 1 Target Date query field enables you to search for AIMs for a different day - simply type in the new Target Date as dd/mm/yyyy then click on the Set button. The 2 Current and Future AIMS allows you to incorporate future AIMS in your query, which you launch with the 3 Go button A 4 Timestamp is generated on each query, as shown against the green background in the example above. An 5 orange arrow indicates if a column has been manually sorted, and according to which order ( or descending). You then need to click on the 6 title of an AIM to open it. You need to click on the title of a column to sort it - providing of course it is sortable... ascending
Result
For each AIM message that is valid for the current day or later, the AIM list displays the following details:

Valid from: Date from which the AIM message is valid. Until: Date until which the AIM message is valid. UFN may be displayed to represent "until further notice". Description: Short description of the AIM. Released on: Release day and time.
Default Sort Order By default, the AIM list is sorted by Valid from, with the latest date displayed at the top of the list. Sortable Columns The AIM list can be sorted by any one of the following fields:
Valid from: Initial sort direction being in the order of the message with the latest date displayed at the top of the list. Released on: Initial sort direction being in the order of the message with the latest date and time displayed at the top of the list.
6.4 Airport Info


Typical Scope:
34
This Portlet allows you to view all the details for the queried Airport. An autosuggest mechanism will propose you, in a range gradually narrowing as you type in, all matching Airports.
Detached View
The Airport Indo Detail Detached View displays available info for the selected Airport. The Airport Info Details screen comprises 7 tabs, described below:
6.4.1 Forecast % Traffic evolution and Operational Contact
This first tab expresses in plain text the traffic evolution planned for the period. It also presents a list of contacts.
6.4.2 Declared Capacity
The Declared Capacity tab mostly consists in a table presenting the following figures:

Runway Config Max Arrivals Max Departures Global Optimum.
Some additional information can also pre presented, depending on the case.
6.4.3 Traffic & ATFCM Situation
35
The Traffic & ATFCM Situation tab presents a summary of the ATFCM situation over the previous season.
6.4.4 Ongoing & Planned Activities
This tab lists all known activities, either planned or ongoing.
6.4.5 Weather Management
The Weather Management tab presents weather data provided by the Airport.
6.4.6 Actual Traffic & Follow-up
36
This tab mostly consists in a table presenting the following figures, for the last 5 years:

Average Daily Movements Traffic evolution (in%) Daily average delayed traffic Daily average airport delay % of delayed arrival traffic % of days regulated % of delay due to weather conditions (W/D)
Some free text may also be appended, depending on the needs.
6.4.7 Expected Significant Events
The Expected Significant Events tab presents all events associated to the selected Airport, and for the selected display period. The listed events may in turn provide links with other parts or content of the NOP Portal, such as Events details, or links to external sources such as the NOTAM and/or AI SUP. Four subsections are presented, namely Axis Management, Special Events, Military Events, Continency & Critical Events. They are all featured on the screen, regardless of them having or not any content. Filled in subsections are typed in black, and a collapsible arrow icon allows you to display the content (as in the second one on the above example), while empty ones are just typed in grey to show they are inactive.
6.5 Airspace Data

Typical Scope:
The Airspace Data Portlet is meant to execute queries on Airspace Data (previously called Environment Data).
37
The layout of Airspace Data in the NOP Portal varies slightly from the Environment Data in CIA; however the query functions are identical. The Portlet is divided in three tabs, each one featuring a simple querying interface for:

Traffic Volume Aerodrome Route
Any query in one of these tabs will open the same Detached View, however already opened on the appropriate Main tab and Secondary tab, and with the retrieved matching data displayed under a much more elaborate querying panel. Go to the topic of your choice to learn more: Traffic Volume (Section 6.5.1) | Aerodrome (Section 6.5.2) | Route (Section 6.5.3)
6.5.1Airspace Data - Traffic Volume Query

The Traffic Volume retrieves the list of traffic volumes associated with an FMP (Traffic Volume Set) or a given location (Airspace, Aerodrome, Aerodrome Set or Point) for the selected Target Date.
6.5.1.1 1. Traffic Volume per Airspace
The query displays the following:

Where: the selected filter (Airspace in this case) Is: field to enter the Airspace identifier (empty by default)
6.5.1.2 2. Traffic Volume per Aerodrome

Where: the selected filter (Aerodrome in this case) Is: Aerodrome identifier (empty by default) Category: A drop-down list containing: a) Global. b) Departure. c) Arrival.

By default, Global is set.
38
6.5.1.3 3. Traffic Volume per Airspace

Where: the selected filter (Aerodrome Set in this case) Is: Aerodrome Set identifier (empty by default) Category: A drop-down list containing: a) Arrival. b) Departure. c) Global. By default, Global is set.
6.5.1.4 4. Traffic Volume per Point

Where: the selected filter (Point in this case) Is: Point identifier (empty by default)
6.5.1.5 5. Traffic Volume per FMP

Where: the selected filter (Traffic Volume Set in this case) Is: This field supports a drop-down list containing the system known traffic volume sets. The Display Traffic Volume Set List link opens a Detached View with all the system known traffic volume sets.
Irrespectively of the selected filter(s), click on the Go button to launch the query and open the Airspace Detached View. You can alternatively press the Enter key to launch the query
6.5.2Airspace Data - Aerodrome

Querying from the Portlet with the Aerodrome option selected from the full-down menu lists the aerodromes that are grouped in the selected aerodrome set for the selected Target Date. Similarly, selected Aerodrome Sets lists the set of aerodrome for the selected Target Date.
39

Where: the selected filter (Aerodrome or Aerodrome Set) Is: Identification of the Aerodrome / Aerodrome Set for which you want to retrieve data.
Irrespectively of the selected filter(s), click on the Go button to launch the query and open the Airspace Detached View.
6.5.3Airspace Data - Route

The Air Routes tab searches for the availability details of the designated Air Route for the selected Target Date.

Air Route: Identification of the air route. (From Point): First point on the route to be displayed (optional group with To point). (To Point):Last point on the route to be displayed (optional group with From Point).
6.5.4Querying Airspace Data from within the Detached View

You do not need to come back to the Portlet to work with Airspace Data. The Navigation and Query panel provide all the necessary elements to make all the queries, as shown on the image below.
40
Access Structure
The tree below summarizes the various searching possibilities offered by this View (the first bullet level representing a primary tab, the second level a secondary tab).
Traffic Volume

Airspace Aerodrome Aerodrome Set Point Traffic Volume Set
Traffic Volume Set Aerodrome

Aerodrome List Aerodrome Details
Aerodrome Set Air Route

CDR Downstream CDR Upstream
Route Catalogue
Mandatory Fields / Optional Fields

All fields in a Query panel are mandatory, except when their name is between brackets. On the example below, the fields ADEP, ADES, IOBD and IOBT and mandatory, while (EET) is optional.
Time Stamp
All result lists are marked with the date and time at which the corresponding query was made, as well as the number of matching entries (which can be 0 in some cases). The time stamp is rendered against a pale green bar separating the Query area from the Result area:
41
Submitting a Query
Once all required fields have been filled in, you can launch the Query either by clicking on the pressing the Enter key on your keyboard. button or
6.5.4.1Traffic Volume Traffic Volume

The Traffic Volume List page displays the list of traffic volumes associated with an FMP (traffic volume set) or a given location (airspace, aerodrome, set of aerodromes or point) for the selected Target Date.
Regardless of the selected tab(s), all Airspaces detached views are constructed in the same way: 1 Query Panel On the top of the window, the Query panel gathers all necessary navigation elements and query mechanisms to access the Airspace data. 2 Result Summary Time stamp and number of items matching the query. 3 Display Panel This is where the query results will be listed in a table format.
Query
6.5.4.1.1 When Invoked for an Airspace
Airspace: Airspace identifier. By default, this field is empty.
6.5.4.1.2 When Invoked for an Aerodrome

42
Aerodrome: Aerodrome identification. By default, this field is empty. Category: A drop-down list containing: a) Global - set by default b) Departure. c) Arrival.
6.5.4.1.3 When Invoked for an Aerodrome Set
Aerodrome Set : Aerodrome Set identification. By default, this field is empty. Category: A drop-down list containing: a) Global - set by default b) Departure. c) Arrival.
6.5.4.1.4 When Invoked for a Point
Point: Significant point identifier. By default, this field is empty.
6.5.4.1.5 When Invoked for a Traffic Volume Set
Point: Significant point identifier. By default, this field is empty.
Result
For each traffic volume matching the submitted query, the traffic volume list displays the following details:

ID - Traffic volume id Name - Traffic Volume name Reference Location - Reference location type and identifier related to the traffic volume Flows - Related flows (1 per line) with the role if any.
The traffic volume list is sorted in ascending alphanumeric order of ID. Click on the title of a column to sort its content (ascending or descending).
6.5.4.2Traffic Volume Set

NOP Portal - User Guide Traffic Volume Set
43
The Traffic Volume Set List page lists the FMPs (traffic volume sets) defined on the selected Target Date.
Query
The query area does not contain any specify field. Clicking on the Go button will submit the query to retrieve all Traffic Sets for the set Target Date.
Result

Set ID: Identification of the FMPs (traffic volume sets). Name: Description of the FMPs (traffic volume sets). The Set ID field provides a link to access the Traffic Volume List page for that set.
6.5.4.3Aerodrome Aerodrome List
The Aerodrome List tab lists the aerodromes that are grouped in the selected aerodrome set for the selected

Target Date. On access of the Aerodrome List page from the Aerodrome Sets List tab, the results of the default query are automatically displayed (i.e. the Go button does not have to be clicked by the user to submit the default query).
44
Query
Aerodrome Set: Identification of the aerodrome set. If the Aerodrome List page is accessed from the Portlet, by default, this field is empty. If the Aerodrome List tab is accessed from the Aerodrome Sets List tab, by default, this field is set to the aerodrome set name for which this tab was invoked.
Results

ID: ICAO code of the aerodrome. Aerodrome Name: Name of the aerodrome.
By default, the aerodrome list is sorted by ID, in ascending alphanumeric order. Simply click on the name of a column to modify the sorting order. The ID field provides a link to access the Aerodrome Details tab for the selected Aerodrome.
Aerodrome Details
The Aerodrome Details page lists the detailed data for the selected aerodrome for the selected Target Date. On access of the Aerodrome Details tab from the Aerodrome List tab, the results of the default query are automatically displayed (i.e. the Go button does not have to be clicked by the user to submit the default query). The time stamp shows when the information was retrieved from the CFMU system as well as the number or entries retrieved.
Query
Aerodrome: ICAO identification of the aerodrome. If the Aerodrome Details page is accessed from the Aerodrome List tab, by default, this field is set to the aerodrome name for which this tab was invoked.
Results

WEF: Start date and time (dd-hh:mm format) for the period. UNT: End date and time (dd-hh:mm format) for the period DEP: Departure runway. Taxi: Taxi time for the departure runway.

45
TIS: Time to insert in sequence. TRS: Time to remove from sequence. ARR: Arrival runway. Taxi: Taxi time for the arrival runway.
6.5.4.4Aerodrome Set
The Aerodrome Sets List tab lists the set of aerodrome for the selected date. On access of the Aerodrome Sets List panel, the results of the default query are blank - you need to click the Go button to submit the default query. The time stamp shows when the information was retrieved from the CFMU system as well as the number or entries retrieved. For each aerodrome set matching the submitted query, the Aerodrome Sets List displays the following details:

ID: Identification of the set of aerodromes. Aerodrome Set Name: Name of the set of aerodromes.
The aerodrome sets list can be sorted by ID or Name, in ascending or descending alphanumeric order. The ID field provides a link to access the Aerodromes List (Section 6.5.4.3) page (list of aerodromes in that set).
6.5.4.5Air Route
The Air Routes page tab the availability details of the selected Air Route for the selected Target Date. Within the main tab, two secondary tabs display the air route (portion) in the opposite Downstream / Upstream directions.
CDR Downstream
46
CDR Upstream
The Air Routes tab shows the availability details of the selected Air Route for the selected Target Date.
Query

for Air Route: Identification of the air route. By default, this field is empty. (From Point): First point on the route to be displayed (optional group with To point). By default, this field is empty. (To):Last point on the route to be displayed (optional group with From Point). By default, this field is empty. If both From Point and To point are provided, they must be different from each other.
Results
air routes list 3 n lines of air route availability details per air routes (there can be multiple air routes with the same for Air Route name). For each point along the route, the air routes list displays the following details:
Point ID: Identification of the point. If the point is the start of a new portion of the route on which availability data are defined, a horizontal separator line is drawn through the other columns of the list. The sequence of points included in a route portion is listed between two horizontal separator lines.

47
FL Lower/Upper: The range of available flight levels, from the lowest to the highest. FL Series: Flight level series CDR Cat: The CDR category.
Point ID, FL Lower/Upper and FL Series delimit a route portion in three dimensions. For each route portion, a CDR category is defined for the associated Weekly Applicability. Possible values are: 1. 2. 3. 4. ATS: when ATS route is always plannable. 1: for permanently plannable conditional route. Closure is published in AUP part B and CRAM. 2: for non permanently plannable conditional route. Opening can be published in a CRAM. 3: for non plannable conditional route used only at short notice on ATC instructions.
5. Not Available: for non plannable conditional route.
6.5.4.6Route Catalogue
The Route Catalogue page lists all routes that match the provided city pair from the route catalogue for the selected Target Date.
Query

ADEP: ICAO Identification of the departure aerodrome. By default, this field is empty. ADES: ICAO Identification of the destination aerodrome. By default, this field is empty. IOBD: Initial Off-Block Date This field supports a drop-down list containing the dates of Today and of Tomorrow. By default, this field is set to the Today. IOBT: Initial Off-Block Time. By default, this is set to 0000 (in hhmm format - must be equal to or between 0000 and 2359) (EET): Estimated Elapse Time (optional). By default, this field is empty. If not, the input must be an integer value equal to or between 0 and 9999 minutes.
Results

Path/Route ID: Identifier of the route (ADEP / ADES / sequence number) CDR: Conditional route category. Possible values are: 1. empty: when the ATS route is always plannable. 2. 1: for permanently plannable conditional route. Closure is published in AUP part 'B' and CRAM.

3. 2: for non permanently plannable conditional route. Opening can be published in a CRAM. 4. N: for non plannable conditional route.

48
NM: Distance in nautical miles Path/Route Details: Detail description of the route/path less the ADEP and ADES.
By default, the route list is sorted by Path/Route ID, in ascending alphanumerical order of ADEP followed by alphanumerical order of ADES followed by increasing numerical order of sequence number. The route list can be sorted by any one of the following fields: Path/Route ID, ADEP or ADES.
6.6 Airspace Structure

Typical Scope:
The Airspace Structure Portlet presents some elements formerly carried by the seasonal Network Operations Plan. This is were you will find information and documents on some Airports best practices, or other Airport related facts to be brought to the attention of the whole community.
6.7 ANM
Typical Scope:
The ANM (ATFCM Notification Message) is a message issued by the CFMU Operations to notify all concerned in the Aviation community of any ATFCM regulations. The ANMs resulting from the ATFCM Daily Plan are sent the day before the day of operations upon finalisation and release of the plan around 16.00/17.00 UTC summer/winter time. Each ANM has an associated released date/time stamp. When the Portlet is refreshed - and if the ANM has a newer date/time stamp that the former one - the "new" item is displayed against a colored background, to draw the attention of the user.
Note: Clicking on the link returns the Portlet to its normal status (the color background is removed). Clicking on the highlighted link opens the ANM List window depicted below, listing all regulations matching the default query - which means all regulations for the selected Day of Operation, with no filter applied, and sorted by FMP Identifier and Regulation Number. Note that the query area at the top of the window features filtering and sorting options.
49
6.8 ATFCM Events

Typical Scope:
50
The ATFCM Events portlet lists in 4 different categories the most recent ATFCM Events relevant to the selected Target Date:
Special Events: foreseen events that may lead to a substantial drop in the capacity of the European Network, requiring ATFCM actions to minimize consequences and to optimize network capacity. Axis Management: a CDM process which optimizes seasonal flows of traffic across the European Network. Military Events: large military exercises/activities requiring a special reservation/segregation of airspace that have significant impact on the available routes and capacity within the European ATM network. Critical Events: sudden and usually unforeseen events that lead to a substantial drop in the capacity of the ATM network, requiring immediate ATFCM action to minimize consequences and to retrieve network stability.
They all share a common ATFCM Events List Detached View, but clicking on one of the highlighted categories will open the ATFCM Events List window with the relevant tab (Special Events, Axis Management, Military Events or Critical Events) already selected. Here the More button displays all the events for the target date, however unfiltered, in the Detached View.
6.8.1Consulting ATFCM Events per Category

Consulting the events per Category
A definition of each type of event is provided under each tab: Axis Management: Axis Management is a CDM process which optimises seasonal flows of traffic across the European Network. The process starts in advance and has as an output ATFCM Measures (e.g., re-routings, FL capping or alternative routings) that would be further consolidated and applied on the day of operations. This output is discussed and agreed through dedicated CDM conferences (either via a meeting or an econference) and there is a monitoring process to fine-tune the event management as well. Special Events Special Events are plannable events that may lead to a substantial drop in the capacity of the European Network, requiring ATFCM actions to minimise consequences and to optimise network capacity. They are of different nature (ATM changes, including changes in ACC configurations and locations and in systems, sporting events, major social events, etc) expected to affect the demand and have a significant impact on Operations. These events are early notified, allowing an advanced assessment of the likely impact, and a collaborative planning to define the appropriate ATFCM measures to minimise the effects on airspace users and to ensure network stability. Military Events Military Events are large military exercises/activities requiring a special reservation/segregation of airspace that have significant impact on the available routes and capacity within the European ATM network. These events are early notified, allowing an advanced assessment of the likely impact, and a collaborative planning to define the appropriate ATFCM measures, like the suspension of part of the RAD for specified
51
periods and/or additional routeings, in such a way that they can be accommodated while minimising the effects on other airspace users and ensuring network stability. Critical Events Critical Events are sudden and usually unforeseen events that lead to a substantial drop in the capacity of the ATM system, requiring immediate ATFCM action to minimise consequences and to retrieve network stability.
In this example, the Special Events scheduled for the selected Target Date are displayed in a list, inside the Online Special Events panel which is selected by default. On the other hand, the Archived Special Events contain all the archived events matching the selection criteria (in this case, Target Date + Special Events) The three other ATFCM Event categories (Axis Management, Military Events or Critical Events) feature a similar filtering between online events and archived ones. From the ATFCM Events List Detached View, you can browse between the different categories without needing to come back to the Portlet on the main page. Please continue with the next topic (Section 6.8.2)...
6.8.2Consulting the Description of an Event

Result of a Query
The events matching the submitted query are listed in a 5-column table (Occurrence, Event, ACCs, Scenarios and Last Updated), with the most recent entry on top.
1. Clicking on a highlighted Event opens an ATFCM Events Detail window with all the details of the selected Event, as shown below:
52
Finally, Clicking on one of the highlighted Scenarios identifier (FL1ACUU, RR2ACUU, ...) opens a Scenarios Detail window.
6.8.3Consulting Scenarios associated to an Event
53
2. Clicking on the highlighted Scenarios labels (Section 6.9.2) proposed in the Events list will open another Detached View - nominally associated with the ATFCM Measures (Scenarios) Portlet - with all Scenarios corresponding to the selected Event,
6.9 ATFCM Scenarios

Typical Scope:
The ATFCM Scenarios portlet lists provides the Scenario List link, which opens the ATFCM Scenarios List (Section 6.9.1) Detached View.
6.9.1The ATFCM Scenarios Detached View

Online Scenarios
This is the header of the Scenarios List Detached View, as it opens by default with the Online Scenarios tab selected.
6.9.1.1 Content of the query area

Origin: Where the flow of the traffic to which the scenario applies, is coming from. ATFCM Events: Drp-down list of events valid for the selected Target Date. Area: The specific airspace(s)/point(s) of congestion alleviated by the application of the scenario. Destination: Where the flow of the traffic to which the scenario applies, is going to. Title: the Scenario name. Status: allows you filter the query by status. Possible values can be: a) Only Active

b) Non-Draft c) Only Draft
54
Types: Type(s) of scenarios - select one or more: Possible values can be:
a) AR - Alternative Route scenario. b) FL - Flight Level scenario c) FL-CAP - Flight Level Cap scenario. c) PR - Preferred Routing scenario. d) RR - Re-Route scenario.
Note that he Target Date can also be changed in the header of the detached view, to any other date in the future or in the past.
Archived Scenarios
Selecting the Archived Scenarios brings a new query area, very similar to the one in use for the Online Scenarios - except for the Status filter.
Result
The result of a query from the Scenarios Detached View is a list of scenarios, displayed right below the 1. Query Area. The date and time at which a given query has been made is indicated in the 2. Query Results area (in the green banner), along with the number of matching scenarios. The matching scenarios are listed in 3.
55
Finally, clicking on one of the Scenarios identifier (in blue in the Title column) opens a Scenarios Detail (Section 6.9.2) window.
6.9.2Consulting a Scenario Details

Scenario Details can come with or without a picture, as shown on the two examples below.
Definitions of the field labels


56
Identifier: The Scenario name (in the blue header) Origin: Where the flow of the traffic to which the scenario applies, is coming from. Destination: Where the flow of the traffic to which the scenario applies, is going to. Types: AR - Alternative Route scenario: A route (usually non-RAD compatible) opened to alleviate congestion in an area. Due to the non-standard nature of the route, this flow is usually regulated when available. FL - Flight Level Cap scenario: the flow of traffic is level-capped (for a portion of its route) to take it out of a congested area. PR - Preferred Routing scenario: a suggested route which the concerned ACCs on a particular axis would prefer the flow to follow. This field can be empty. RR - Re-Route scenario: the flow of traffic is forced to refile geographically to avoid a congested area. Refile: Specific condition(s) to which the of traffic is required to comply. Suggested Alternative Routes: Proposed profiles for the Aircraft Operators to consider when selecting a route in order to comply with the Condition(s) Comments: Used to provide additional information relating to the scenario. For example: RAD restrictions which will be ignored by IPFS to allow compliance with the Condition(s) or Refile fields. Location (Area): The specific airspace(s)/point(s) of congestion alleviated by the application of the scenario. On-load Areas: The key airspaces which may expect to receive additional traffic as a result of the application of the scenario. Off-load Areas: The key airspaces which may expect to receive less traffic as a result of the application of the scenario. Applicability: If the availability of the scenario for the ATFCM use is limited to a specific period they are listed here. For example: weekend only during the ski season. Status: can be either Published, Agreed or Active

Published: Used to indicate if the scenario is in 'draft' mode or has been 'published' for operational use. Agreed: The specific periods (dates + hours) for which the concerned FMPs and Network Operations Division have agreed to apply the scenario. Active: The actual specific periods (dates + hours) for which the scenario is/was applied, derived from the ETFMS.
Explanations of the map labels

Map labels contain information from the scenario definition and are used to highlight on the map items of specific interest or which are worthy of particular care and attention.
6.10ATFCM Network Situation

Typical Scope:
57
The ATFCM Network Situation displays a map of Europe, where certain ACC areas are colour coded to indicate ATFCM delays for these areas. Four types of delays are displayed, ranging from over 45 minutes to less than 15 minutes. < 15 min < 30 min < 45 min > 45 min For the Token (Section 3.3.1) Users (users of the Protected Portal), two buttons currently appear at the bottom of the Portlet, namely Beta and More. The users of the Public Portal (not requiring a login) will only see the More button so all information pertaining to the Interactive Map is not relevant in that context. For the Token (Section 3.3.1) Users, two buttons currently appear at the bottom of the Portlet, namely Beta and More. The Beta button opens a Detached View (Section 6.10.3) displaying a map connected to the operational system, enabling you to extract operational information. This beta function will be available in dual mode with the former static map, available under the More button. This dual mode will be sustained until the release of CFMU14 (scheduled around may 2010), where the dynamic operational map will replace the static one for good.
This Portlet is present in two ATFCM Phases. The measurements upon which it is based is different, and therefore the rendered map different as well. See the following topics for details:

ATFCM Network Situation - Tactical (Section 6.10.1) ATFCM Network Situation - Post-Ops (Section 6.10.2)
6.10.1Viewing the ATFCM Network Situation in the Tactical phase

Viewing the ATFCM Network Situation in the TACTICAL phase
58
When in Tactical phase, the ATFCM Network Situation displays a map of Europe, where certain elements are colour coded to indicate the foreseen ATFCM delays for these elements at the time of consultation.
6.10.2Viewing the ATFCM Network Situation in the PostOperations phase

Viewing the ATFCM Network Situation in the Post-Operations phase
In the Post-Operations phase, the ATFCM Network Situation map for the selected target date displays the cumulated ATFM delay recorded per ACC over that day (00:00 am to 11:59 pm), displayed with the same color code as in the Tactical phase.
59
6.10.3The (static) ATFCM Network Situation Detached View

The More button on the ATFCM Network Situation Portlet has opened the detached view with a full screen view of the map. The legend explaining the colour codes can be displayed or hidden on a simple click. A navigator which aims at locating a zoomed area in the map can also be displayed or hidden on a click.
A toolbar is provided at the bottom of the map, featuring a couple of display functions (hide/show Legend and Navigator) as well as a drill down box where you can select the forecast period (H, H+1, up to H+4) and a Loop check box.
Show Legend
Toggle off or on the Legend bar on top of the window, displaying the color code.
Show Navigator
60
Toggle off or on the Navigator overlay on top right of the window, highlighting which area of the Map is currently displayed .
Loop
When checked, each 30 seconds the forecast delay data is automatically stepped forward by 1 hour in a H to H+4 cycle.
6.10.4ATFCM Network Situation Interactive Map

This is how the Interactive Map looks like when first opened:
Note: for the time of the testing, and until the release of the CFMU 14 release, the disclaimer below will pop up each time you start a new browser session.
From this interface, a vast number of actions and queries can be performed, as summarized here:
Zoom, pan, move


61
Choose the area of the world to be displayed on the screen Choose the flight levels Choose the time period for the information displayed on the map Gather info details on the plotted entities, e.g. FIR, regulation delays, flights, etc. Plot the following upon querying by the user, via the map interface

Regulation Delays Daily Plan CRAM Flights Airspace Data
6.10.4.1The Map Menu Bar

The Menu Bar contains the main commands. This is how the Map Menu Bar looks at the top of the Map detached view:
Overview
6.10.4.1.1 Tools
The Tools Menu gives access to a number of tools, namely Location (Section 6.10.4.2), Area (Section 6.10.4.3), Levels (Section 6.10.4.4), Time (Section 6.10.4.5) and Queries (Section 6.10.4.6).
62
6.10.4.1.2 Clear View

Clears all windows and floating panels from view, granting the maximum of space to display the Map.
6.10.4.1.3 Gather Info

Use the Gather Info tool to draw a rectangular area from which to want to retreive data.
6.10.4.1.4 Move
Use the Move tool to grab and move the Map.
6.10.4.1.5 Pan
Use the Pan tool to define a translation vector - can be also used to show parts of the Map not currently visible.
6.10.4.1.6 Zoom
Use the Zoom tool to define a rectangular area into which you want to zoom (in or out).
6.10.4.1.7 Settings
Use the Settings tool to access the Map settings.
6.10.4.2Tools - Location
The Location panel contains the Location Pad and Mode buttons. The Location Pad features in a very compact interface, a number of powerful functions:
63
1. 2. 3. 4.
Direction Arrows You can incrementally Pan the Map by clicking on one of the arrows (Left, Right, Up and Down). Zoom in and out You can incrementally Zoom in or out by clicking the zoom buttons. Maximise Map Gets a map which fills the window. Reset Map Resets the Map to its basic layer of countries (not implemented in this beta version).
The buttons in the right part of the panel are the Mode Buttons:
These functions may appear elsewhere in the Map - but their usage is always the same: 1. 2. 3. 4. Use the Pan tool to define a translation vector - can be also used to show parts of the Map not currently visible. Use the Gather Info tool to draw a rectangular area from which to want to retreive data. Use the Zoom tool to define a rectangular area into which you want to zoom (in or out). Use the Move tool to grab and move the Map.
Note: The Pan and Zoom functions are also available from the Menu Bar. Click on the link to go to the next topic: Area (Section 6.10.4.3).
6.10.4.3Tools - Area
64
The Area Panel is used to set the area of the Map to be displayed. You can either drag and stretch the rectangle selector, or directly enter numeric values in the A and B fields. The Windows ratio button keeps he clipping rectangle proportional to the Detached View window Click on the link to go to the next topic: Levels (Section 6.10.4.3).
6.10.4.4Tools - Levels
There are many different ways to specify the upper and lower Flight Level with the Map. They are briefly outlined below. You can also watch a short demo movie here (films\map_levels.html).
65
This is how the Flights Levels component looks like when first opened - be it docked or floating.
6.10.4.4.1Tools - Level Ruler

A Level Ruler is visible by defaults on the left side of the screen:
This vertical scale graphically displays the flight levels array. You can adjust its upper and lower values by clicking and dragging the upper and lower limit handles respectively. When you modify a value, the Apply button appears, on which you simply click to filter the display according to the new settings.

The Level Ruler is dynamically linked with the Circular Level Ruler (Section 6.10.4.4) - changing the settings on one is reflected on the other.
66
6.10.4.4.2Setting the Flight Levels on the Map

By default, the full range of Flights levels is selected. You can adjust it in three ways 1. 2. 3. Drag the limit handlers in the circular Levels Selector (from the palette). Click on a predefined set title: UIR, UAS, RVSM, ... (form the palette). Clicking on "ALL" will of course reset the values at the maximum range. Drag the limit handlers in the vertical Levels Rulers - read the Levels (Levels.html) section for more information (left side of the Map).
Finally click on the Apply button to change the values to your new setting - and see how it is synchronized with the vertical Flight Levels Ruler.
Settings
Ruler Scale Sets the granularity on the flight level ruler. Available scales are 1/1, 1/2, 1/5, 1/10, 1/20 and 1/50. The Unit is expressed in ten's of feet per tick (1/10 = 100 feet per tick)(colored mark in the ruler).
Note that the scale does not impact the Circular level ruler.
Maximum Flight Level Sets the maximum level. The two defined values are FL600 and FL1000. The maximum range is set for both the vertical and circular sliders.
6.10.4.5Tools - Time
The Time Panel gathers all settings and commands in relation with time date and time.
Show Time Ruler

67
This button alternatively shows and hide the Time Ruler - providing that you work in the 'ABS' Time Mode (see further).
Time Mode
Two toggle buttons allow you to set the Time Mode in which you wish to work - selecting either one, or both.
6.10.4.5.1
Loop Mode
While in Loop Mode, the display is refreshed every 30 seconds, looping through an H to H+4 cycle.
6.10.4.5.2
ABS Mode
The ABS Mode is used to set a 'from - to' period for which to display data (using two clocks) - or a fixed time (using the first clock). You can change the dates and times in different ways: Time: directly editing the figures, or moving the clock handles with the mouse; Date: using the Calendar.
Forecast Filter
68
Click on the +1, +2, +3 or +4 buttons to set the forecast filter to the Current time + 1 hour, + 2 hours, + 3 hours or + 4 hours respectively. Note: the Current time is the time as set in the Clock component. Click on the link to go to the next topic: Queries (Section 6.10.4.6).
6.10.4.6Tools - Queries
The Queries panel is used to enter the query parameters of five types: Delays, Daily Plan, Cram, Flight and Geo Env. Each parameters gets its own setting interface, as detailed below.
Delays
You can select any combination of Delay value: Low, Normal, Medium or High. The Show All Types toggle button selects all four values in one click.
Daily Plan
69
You can select any combination of Daily Plan type: Headline, Event, ACC, NAT, Weather or Other. The Show All Types toggle button selects all six values in one click.
CRAM
There is only one action possible here: show (or hide, when the Show button is off) the CRAM on the Map.
Flight
This is where you type (or paste) the ARCID of the flight you want to plot on the Map. You can enter more than one, separated with a coma. The time mode must be set to ABS and encompass the flight's EOBT.
Geo Env.
This parameter is further broken down in a number of sub-filters, namely AB (Airblock), AS (Airspace), AD (Aerodrome), AZ (Set of aerodromes), PT (Point), TV (Traffic Volume), RT (Route), OTS RT (OTS Route) and RS (Restriction).
6.10.4.6.1 Setting the Geo Env. filters

All but two of the filters expect only one value: the parameter ID - or IDs, if separated with a coma. The exceptions are: AS
In addition to the IDs field, AS allows to further refine the query with the following types: AOI, AOP, AREA, AUA, AUAG, CS, CRSA, ERSA, ES, FIR, NAS, PIR , REGION and UIR. The Show All Types toggle button selects all fourteen types in one click. RT
In addition to the IDs field, RT allows to further refine the query with the following types: ATS, CDR1, CDR2, CDR3 and N/A. The Show All Types toggle button selects all five types in one click.
70
6.10.4.6.1Plotting Flights on the Map

For the time being, it is not yet possible to directly plot a flight from a flight list (the Flights Detached View). However, a flight can be plotted on the interactive Map:
All you need is following a few simple steps as outlined in the sample below. You can also watch a short demo movie here (films\map_flight.html).
Plotting a Flight
1. 2. 3. 4. 6. 7. Click on the the Flight List link in the Flights Portlet and run any relevant query in order to get a desired ARCID. Close the Flight Detached View Click on the Beta link in the ATFCM Network Situation Portlet to open a Detached View with the dynamic Map. Check that the (Tools) Time Mode is set to ABS and that the ABS period covers the EOBT of the flight. Select the 3 Flights tool and enter the desired 4 ARCID Then click on 5 Apply to launch the query
5. Click on the 2 Queries button from the 1 Tools palette
71
Important: do not forget to set the Time to 'ABS' (from the Tools menu) to be able to display this kind of content. Several ARCIDs can be entered in the query field - simply separated with a coma.
6.10.4.6.2Displaying Regulations from the Map

Regulations can be shown and detailed on the Map with a few simple steps as outlined in the sample below. You can also watch a short demo movie here (films\map_regulation.html).
Displaying Regulation
1. 2. Click on the Beta link in the ATFCM Network Situation Portlet to open a Detached View with the dynamic Map. Click on the Gather Info button from the Menu Bar

3. 4. 6. 7. 8. 9. Position the mouse on the top left corner of the area you wish to explore Click to set the origin point of the selection rectangle Click to set the ending point - a new window will appear with the collected list of data matching the query Make sure the Delays filter is set to 'on' Select the desired item in the list Click on the Show details button
72
5. Move the mouse across the window to draw the selection area
6.10.4.6.3Plotting CRAM on the Map

Regulations can be shown and detailed on the Map with a few simple steps as outlined in the sample below. You can also watch a short demo movie here (films\map_cram.html).
Plotting the CRAM

1. 2. 3. 4. Click on the Beta link in the ATFCM Network Situation Portlet to open a Detached View with the dynamic Map. Click on the Queries button from the Tools palette Select the CRAM tool Click on the Show button to activate it
5. Click on the Apply button to show the CRAM Important: do not forget to set the Time to 'ABS' (from the Tools menu) to be able to display this kind of content.
6.11ATFCM Situation Data

Typical Scope:
73
The ATFCM Situation Data portlet is complementary to the Map displayed right above it, in the ATFCM Network Situation Portlet. It provides high level indicators at Network level on the real time status of: traffic, delays, delay causes and measures. The indicators are refreshed every 10 minutes by the CFMU ETFMS system. Every hour, a screenshot of the indicators is taken and archived. This allows displaying the evolution of the ATFCM Situation over the day. By clicking on the More button, a detached view appears which provides:

Customisable graphical representations of the indicators, A list of the delay causes with sorting functions, A list of the most penalising regulations with various sorting functions.
The portlet includes indicators which are public and others which are only accessible to users with strong authentication (token access):

Flights, Delays, and Delay causes are public Slot window compliance, suspended flights, and the regulations details in the detached view are only accessible to users with strong authentication.
6.11.1The ATFCM Situation Data Detached View

The ATFCM Situation Data Detached View comprises the 5 same sections as the Portlet, only to provide more details on their respective scope:

1. 2. 3. 4. Flights are rendered in a graphical way, allowing you to switch between modes. The same applies for Slot Window Compliance. The Delays in minutes and the Suspended Flights, similar to the one provided in the Portlet. And finally the Delay Causes. pie chart and bar graph
74
Learn More (Section 6.11.2) about the Show regulations button...
6.11.2Digging into the Delay Causes

The Delay Causes table contains all the regulations for the Target Day. You can click anywhere in the column headers to sort the data as you need (ascending or descending). The Show regulations (Hide regulations) opens a secondary table listing all associated regulations.
75
These columns are again fully sortable in any desired fashion - see examples below (notice how the sort arrow is oriented).
6.12ATFCM Network Daily Plan

Typical Scope:
76
The ATFCM Daily Plan is a set of Tactical ATFCM measures (e.g. activation of Routing Scenarios, regulations, etc.) prepared by the CFMU and agreed with all partners concerned during the planning phase. Published every day around 1600UTC, it is accessible via the NOP Portal and also promulgated via AFTN by means of the ANM and Network News messages. The ATFCM Network Daily Plan may be updated at any time according to the needs. The updates are issued by the CFMU Network Management Cell on duty during office hours 7 days/7. The map in this portlet displays with color codes the areas which are affected by an ATFCM Event or by a Network Headline News (meaning a significant ATFCM event) at the moment of publication. Note: The ATFCM Network Daily Plan uses the same Map component as the ATFCM Network Situation. please refer to that specific section (Section 6.10.4) to get detailed help, useful information and demo movies on the general Map features.
Opening a Detached View

Six links are grouped on the top pf the Portlet: Headline, Events, ACC's, NAT, Weather and Other:
Clicking on each of these shortcuts will open the same ATFCM Network Daily Plan Detached View - the difference being that the (sometimes very lengthy) document will be presented with the relevant section expanded and the other ones collapsed, to save screen space and facilitate the reading.
77
The above example results from a click on the NAT shortcut - see that all sections are collapsed except the NAT one.
Accessing the Map

Two buttons currently appear at the bottom of the Portlet, namely Beta and More.
The Beta button opens a Detached View (Section 6.10.3) displaying a map connected to the operational system, enabling to to extract operational information. This beta function will be available in dual mode with the former static map, available under the More button. This dual mode will be sustained until the release of CFMU14 (scheduled around may 2010), where the dynamic operational map will replace the static one for good. Using the More link opens the static Daily Plan (Section 6.12.1), while using the Beta link opens the new interactive Daily Plan (Section 6.12.2).
6.12.1The Static Daily Plan
78
The Static version of the Daily Plan provides an enlarged view of the annotated map proposed on the Main view with no other feature than basic vertical panning. This map is to be dropped on releasing CFMU 14 - when the current beta version of the new Map will replace all previous occurences.
6.12.2The Interactive Daily Plan
79
When opened in a Detached View, the ATFCM Network Daily Plan looks very similar to what you can get from the ATFCM Network Situation (Section 6.10.4) Map - in fact, they both rely on the same Map component.
Getting the Daily Plan

A few simple steps will allow you to retrieve all you need in relation with the Daily Plan. First click on the Gather Info button to draw a selection rectangle around the target area; click a first time to set a corner of the rectangle, drag the mouse to draw the desired rectangle, and click a second time to set the opposite corner. A red overlay is now showing the selection area:
80
As soon as you release the mouse button, a list appears, with all the items present in the selected area, according to the filter settings. The Daily Plan filter was the only one activated for this examples - see here (Section 6.10.4.6) how to work with queries and filtering.
Select the Daily Plan item (there could be more items available such as Delays, Flights, etc depending on your filter setting) and click on the Show Details button at the bottom of the panel:
81
This action results in producing a list of affected Reference Locations:
We have selected for you the EDUUHVSOSHY Airspace - as highlighted below:
Most columns are sortable - just click in the column header to modify the display order (see above). Clicking on the Details button of the selected item opens the Details panel.

This is how it looks like for an Airspace (keeping in mind that similar details panels are available for Aerodrome, points, ...) with the Info details option selected...
82
... or with the Spaceblocks details option selected:
In a similar way, you can also examine the Composition and Configuration.
6.13Calendar
Typical Scope:
83
A colored symbol indicates that there is an event scheduled for the selected day. Each symbol stands for one given event - the color telling the type of event. Moving the mouse over a marker reveals a summary of the selected event, in the bottom frame of the Portlet. Leaving the mouse over an event marker for a little longer will reveal a summary of that event, inside a tooltip box.
Another method to select an Event is go directly to the Events tab and check all the events scheduled for the target date.
84
Click on a listed Event title opens a Detached View with the relevant event details.
See the full Calendar Manual (Section 6.13.1) for further information.
6.13.1Calendar in details
NOP Portal - User Guide CALENDAR MANUAL

1 General View
Here is a snapshot of the Calendar application, from the NOP Portal.
85
2 Navigate in Time
When launched, the current date is set on the current portal time. The selected day (highlighted day cell) is set on the portal target date. The calendar header shows the current calendar date, and the navigation controls.
Click on the square to set display date to portal simulated time. Click on the left/right arrow to go to the previous/next month. Hold Down the Shift-Key to go to the previous/next year.
3 Change the view mode

You can view events in 3 ways by clicking on the tabs just under the header.
Month (Selected by default) Click on this tab to display the calendar view with events.
86
Day Click on this tab to display the events that start on the selected day.
Checking the Show starting events only button filters down the displayed list of events to the ones starting on the selected day - Uncheking it reveals all events for the day, including those having started earlier but which are not ended yet...
Filtering Events Categories Event categories can be filtered by means of the menu revealed by the Filter Icon at the right of the tabs bar
A pop-up menu appears from which you can select / deselect the desired category filters.
87
The filters do not only apply to the list views, but also to the calendar view.
3 Calendar View
The calendar view displays the days of the selected month, and the events associated to each event. Moving the mouse over a marker reveals a summary of the selected event, in the bottom frame of the Portlet. Leaving the mouse over an event marker for a little longer will reveal a summary of that event, inside a tooltip box.
Event Marks Event Marks can have two shapes, rectangle or triangle. A rectangle shape indicates that an event is starting on this day. A left arrow (on first day of a month) indicates an event is ongoing, which has started the month(s) before. A right arrow (on last day of a month) indicates that an ongoing event is continuing on the next month(s).
88
Selecting Events Clicking on an event mark displays the event overlay and event information. This is somewhat similar to the result of the mouse over action, the difference being that the information remains visible until another overlay or Event Mark is clicked. See a selected event (The event mark is framed with a thin black line) the example below.
The Prev or Next indicators appear in case there is a previous or future occurrence of this event. For events that started in the past (triangle mark), clicking the Prev indicator displays the starting day for the event. Another click displays the previous occurrence (if relevant).
6.14CFMU ATFCM Reports

Typical Scope:
This portlet gives access to several CFMU post-operations reports via 2 methods:
The top part of the portlet displays automatically the reports which correspond to the target date chosen in the Portal. The links to the reports are organised via 3 tabs:

Public reports: they are accessible to all users, authenticated as well as self registered OPS Reports: Operations reports - they are only accessible to Aeronautical professionals and therefore require authentication (via Token ) DOP Reports: they are only accessible to the members of the DOP (Directors of Operations Group) via OnseSky Online. They will be accessible with a single sign on.
The bottom part of the portlet displays by default the latest public reports which are available on the Target Date (the same way as today via the CFMU public website), as shown below.
89
6.15CFMU News
Typical Scope:
The CFMU News Portlet displays the last 3 of a selection of the most relevant (for the actors involved in Network Operations) news items published on the CFMU public website. Below a short summary, and aligned to the left, a More link opens the full news as published on the CFMU Public Website, or to any web page providing supplementary information about the selected News. At the very bottom of the Portlet itself, and aligned to the right, a button opens the full list of the selection.
90
6.16Contingency
Typical Scope:
The Contingency Portlet belongs to the ATFM Information Messages group, as well as the AIM, the ANM and the CRAM Portlets. Its purpose is to display in a very compact way the status of the CFMU operations. The possible status can be:

Normal Continged
This Portlet also provides a link to the CFMU Contingency Plan .
6.17CRAM

Typical Scope:
91
The CRAM contains the list of available CDRs 2 and additionally, when applicable, information on foreseen period (s) of non-availability of CDRs 1. The CRAM covers the 24 hour time period between 06.00 UTC the next day to 06.00 UTC the day after (D 06.00hrs to D+1 06.00hrs). The CRAM is issued by the CFMU each day by 14.00/15.00 UTC (summer/winter time) to AOs, ACCs/FMPs concerned, all AMCs and selected AROs on behalf of all ECAC States. One method to use this Portlet is by simply entering a route in the Route query field and click on the Go button. The Portlet will expand to reveal a very simple list with the matching result (we used route UM82 for the example below).
On the other hand, clicking on the Display Full CRAM button opens the CRAM List window with all data relevant to the selected Day of Operation. Note that the Portlet provides the two tabs - ATS Route and CDR Type 1 Closure and CDR Type 2 Availability.
6.18EAD
Typical Scope:
EAD is the world's largest Aeronautical Information System, a centralised reference database of quality-assured aeronautical information. EAD provides access to worldwide NOTAM and related static data, as well as access to AIP information in both PDF and AIXM format for the ECAC region.

The EAD Portlet provides direct links to EAD Basic and EAD Pro:
92
EAD Basic is the EAD general access for private pilotes, general aviation, training schools and any member of the public searching for aeronautical information. EAD Pro is the database's service for professional, high-volume users such as air operators, airlines, aviation service companies and Aeronautical Information Services (AIS) data providers. EAD Pro is available on a dedicated terminal (ECIT) or through a secure internet connection using SSL technology.
6.19EAUP
Typical Scope:
The European AUP/UUP Portlet lists the EAUPs and their updates:

EAUP: The European Airspace Use Plan EUUP: The European Updated Airspace Use Plan Move your mouse over the Valid WEF link to get a tooltip message with the date and time of release.
Note that some entries may appear against a blue background. This simply means that they are active, with their validity period compatible with the Portal time setting (Section 4.1).
Opening a European AUP/UUP

Click on the Valid WEF link of your choice and the EAUP Details Detached view will open - with the CDR Type 2 Availability tab selected by default. You can alternatively click on the More link to get a EAUP List Detached View with the list of currently valid EAUPs, and open the desired EAUP from there:
6.19.1EAUP Details - ATS Route and CDR Type 1 Closure
93
Query

Route ID: The Route Identification. (max 7 alphanumerics). RSA ID: The Area Identification FIR: Indicates the FIR that the available area lies within (either wholly or partially) (4 characters). UIR: Indicates the UIR that the available area lies within (either wholly or partially) (4 characters).
Results

Route ID: The Route Identification Between: The starting point of the route portion that is impacted by this route statement (2 to 5 characters) And: The last (ending) point of the route portion that is impacted by this route statement (2 to 5 characters). MNM FL: The minimum flight level of the available area (3 digits or GND). MAX FL: The maximum flight level of the available area (3 digits or UNL). WEF: The start time of the available area (hh:mm). UNT: The end time (de-allocation) of the available area (hh:mm). FIR: Indicates the FIR that the available area lies within (either wholly or partially) (4 characters). UIR: Indicates the UIR that the available area lies within (either wholly or partially) (4 characters).
6.19.2EAUP Details - CDR Type 2 Availability
94
Query

Route ID: The Route Identification. (max 7 alphanumerics). RSA ID: The Area Identification FIR: Indicates the FIR that the available area lies within (either wholly or partially) (4 characters). UIR: Indicates the UIR that the available area lies within (either wholly or partially) (4 characters).
Results

Route ID: The Route Identification Between: The starting point of the route portion that is impacted by this route statement (2 to 5 characters) And: The last (ending) point of the route portion that is impacted by this route statement (2 to 5 characters). MNM FL: The minimum flight level of the available area (3 digits or GND). MAX FL: The maximum flight level of the available area (3 digits or UNL). WEF: The start time of the available area (hh:mm). UNT: The end time (de-allocation) of the available area (hh:mm). FIR: Indicates the FIR that the available area lies within (either wholly or partially) (4 characters). UIR: Indicates the UIR that the available area lies within (either wholly or partially) (4 characters).
NOP Portal - User Guide 6.19.3EAUP Details - Level 1 RSA Allocations
95
Query

Route ID: The Route Identification RSA ID: The Area Identification FIR: Indicates the FIR that the available area lies within (either wholly or partially) (4 characters). UIR: Indicates the UIR that the available area lies within (either wholly or partially) (4 characters).
Results

RSA ID: The Area Identification MNM FL: The minimum flight level of the available area (3 digits or GND). MAX FL: The maximum flight level of the available area (3 digits or UNL). WEF: The start time of the available area (hh:mm). UNT: The end time (de-allocation) of the available area (hh:mm). FIR: Indicates the FIR that the available area lies within (either wholly or partially) (4 characters). UIR: Indicates the UIR that the available area lies within (either wholly or partially) (4 characters).
6.19.4EAUP Details - Level 2 RSA Allocations
96
Query

Route ID: The Route Identification RSA ID: The Area Identification FIR: Indicates the FIR that the available area lies within (either wholly or partially) (4 characters). UIR: Indicates the UIR that the available area lies within (either wholly or partially) (4 characters).
Results

RSA ID: The Area Identification MNM FL: The minimum flight level of the available area (3 digits or GND). MAX FL: The maximum flight level of the available area (3 digits or UNL). WEF: The start time of the available area (hh:mm). UNT: The end time (de-allocation) of the available area (hh:mm). FIR: Indicates the FIR that the available area lies within (either wholly or partially) (4 characters). UIR: Indicates the UIR that the available area lies within (either wholly or partially) (4 characters).
6.19.5Compare with Predecessors
A Compare link is available at the bottom of each EAUP Detached View. It will however only be meaningful in case of a EUUP. Clicking on Compare will in effect open an overlay listing the Predecessors, allowing you to pick one of them for comparison purposes, in order to check the changes having occurred between the original EAUP and its updated EUUP version. Please note that an EUUP can in turn be updated by another EUUP - in which case both will be listed in the Compare overlay. The number of cumulative updates is presently limited to two.
97
In the example below, the EAUP Details Detached View displays the cumulative updates having been applied to an original EAUP released on 19/03/2010 and updated twice:once by the EUUP released on 22/03/2010, and once by the EUUP from which the Compare action has been launched.
The background color indicates the following:

White: no changes Green: Update Orange: Original data before update
6.20E -conference
Typical Scope:
98
CFMU E-conferences for Collaborative decision Making (CDM) are usually run using EUROCONTROL econferencing (previously known as CENTRA). The following e-conferences are accessible: Planning and Review of ATFCM Situation CDM Conferences Each day at 14.00/15.00 UTC (summer/winter) the CFMU briefs attendees on the current ATFCM situation in Europe and prospects for the following day based upon the plan CFMU has constructed that day. Daily Tactical Briefing Each day at 08.00/09.00 UTC (summer/winter) the CFMU provide an overview of the current ATFCM situation in Europe and give a prediction of developments up to 14.00/15.00 UTC (summer/winter). Seasonal CDM Conferences Seasonal CDM conferences are held during the summer (e.g. South-West Axis, etc.) and winter (e.g. Ski, etc.) seasons on a weekly basis. Any scenarios to be applied are decided through a CDM process and agreed by all concerned. Ad-hoc CDM Conferences Ad-hoc CDM conferences are organized whenever there is a need to discuss a course of action, in order to prepare and monitor events such as industrial actions, important sporting events, etc.
6.21Events and Meetings

Typical Scope:
This Portlet holds a list of links to pages of the CFMU and EUROCONTROL web sites providing information on events and meetings, which have been selected for their relevance with Network Operations.
6.22F A Q
Typical Scope:
Each phase has its own FAQ (Frequently Asked Questions) as depicted above. They will grow as the Portal develops and as we collect the most significative topics...
Structure of a FAQ page
99
1. The Questions are listed on the top of the window - you simply select one by clicking on its title. 2. The answer ir displayed on the bottom of the window.
6.23Flights
Typical Scope:
The Flights portlet is meant to execute queries on Flights lists and Flights details. The Portlet features 3 simplified methods to access the Flights Data:

An ARCID field and a Go for direct query A Flight List shortcut
Any action by one of these methods will open the same Detached View, however already opened on the appropriate Main tab and Secondary tab, and in the case of an ARCID search, with the matching data displayed under a much more elaborate querying panel. (Section 6.26.2)
6.23.1Querying Flights from the Detached View

You do not need to come back to the Portlet to work with Flights. The Navigation and Query panel provide all the necessary elements to make all the queries, as shown on the image below.
100
Access Structure

ARCID List (Section 6.23.1.1) Flight List

Aerodrome (Section 6.23.1.2.1) Aerodrome Set (Section 6.23.1.2.2) Aircraft Operator (Section 6.23.1.2.3) Airspace (Section 6.23.1.2.4) Point (Section 6.23.1.2.5) Traffic Volume (Section 6.23.1.2.7)
Time Stamp
Submitting a Query
Plotting Flights
The Plot Selected Fights opens the ATFCM Network Situation Interactive Map (Section 6.10.4) and plots all flights whose checkbox has been ticked on.
Showing route(s)
In addition to the possibility to plot flights, you can also easily get its route definition. Clicking on the Route button will expand the flight data line and reveal the flight route. Show
Simply click again on the Show Route button to collapse the flight route line - or on the Collapse All button to hide all opened flight route lines.
101
6.23.1.1ARCID List
The ARCID List tab shows the list of flights with the selected aircraft identification.
Query
ARCID: Aircraft identification. By default, this field is empty - unless when invoked from any of the flight detail pages (including any of the flight message pages), in which case the ARCID is kept from the referring query. (ADEP): Aerodrome of departure (optional). By default, this field is empty. (IOBT): Initial Estimated Off-Block Time (hhmm format) (optional). By default, this field is empty. Select on IOBD/T: A checkbox to indicate if the flight selection must include date and time criteria. By default, this option is checked.
Result
For each aerodrome matching the submitted query, the Aerodrome list displays the following details:

Checkbox to select a flights prior plotting Toggle arrow to display on/off the flight details box (F15-Route) IOBT: Initial Estimated Off-Block Time STA: The status of the flight. Possible values are: a) LF for Late Filer. b) LU for Late Updater. c) LFU for Late Filer and Updater. d) empty when not applicable. ARCID: Aircraft identification - Opens a Detached View with the flight details for that flight. ADEP: ICAO code of the aerodrome of departure for the flight. ADES: ICAO code of the aerodrome of destination of the highest available requested model for the flight. D: Diversion indicator. The symbol > is displayed for a diverted flight. T: Type of flight data. Possible values are: a) A for ATC activated. b) I for IFPL. c) P for PFD. d) R for RPL. e) T for TACT activated. f) E for Terminated. RFL: The highest Requested Flight Level of the flight.

102
ATYP: Aircraft Type. U: Suspension status. Possible values are: a) Empty if the flight is not suspended. b) ST for SIT Time Out. c) SM for Slot Missed. d) RC for Flight Confirmation Message (FCM) required. e) TV for RVR. f) NR for Not Reported as airborne. g) RV for FP_Revalidation. E/CTOT: (Estimated | Calculated) Take Off Time. The time is followed by 'E' for an estimated time or by 'C' for a calculated time S: Ready status. Possible values are: a) I when the flight is in Request For direct Improvement mode (RFI). b) S when the SIP Wanted Message mode is on (SWM), per opposition to the RFI mode. c) R when the flight is REAdy to depart (REA message received). The REA state has priority (overwrites) over the RFI and SWM states. A/TTOT: Actual/Target Take-Off Time. Is either the actual take off time from the DEP, FSA, APR or CPR, or is the same as the E/CTOT when the flight is Tact activated.

00:00blank Tact or ATC activated, departing a non-CDM airport departing from a CDM airport: 00:00e Estimated = latest target take off time from an Early DPI (E -DPI) 00:00t Targeted = latest confirmed AO Target Take off time (T-DPI-c) 00:00s Pre-sequenced = latest sequence ATC target take off time (T-DPI-s) 00:00c previous DPI data no longer valid, new TOT unknown 00:00a Actual take off time when flight is confirmed as airborne 00:00x (italic) when DPI with (future) ATOT has been received. 00:00x (in RED) when a CDM discrepancy is detected
Delay: Delay in minutes (between '*' if slot not yet published). R: Rerouting indicator composed of a reason and optionally a state. The rerouting reason code may be: a) N for not rerouted. b) M for ATFCM rerouting. c) C for CFMU rerouting (CWIR). d) A for auto rerouting (AWIR). e) O for AO rerouting (AOWIR). If the rerouting reason is N, there is no state. Otherwise, the rerouting state code may be: a) P for Produced. There is a valid rerouting going on, waiting to be realised by either an FPL or a CHG. b) E for Executed. Rerouting has been done. c) T for Timed out. No FPL/CHG received on time. d) R for Rejected. Rerouting proposal has been rejected. e) V for Revoked. Rerouting proposal has been revoked. f) N for No match. Message received did not match the proposal. Rerouting has been invalidated. Opp: Opportunity indicator Set to (Y) if an opportunity for a shorter route exists, blank otherwise. W: The AO What-If Reroute indicator code. Indicates if the flight can be re-routed : a) N for No, cannot be rerouted. b) T for Try is allowed. c) A for Apply and Try are allowed. Provides a link to access the Alternate Routes (Section 6.23.1.3.5) page for that flight. MSG: Type of the last message sent or received for the flight. Case Study: Messages (Section 7.1)
REGUL+: Identification of the most penalising regulation for the flight. O: Indication (Y for Yes, N for No) of the existence of Other regulations besides the one indicated in the REGUL+ column.
103
Last column (without heading) The text MSG is displayed providing a link to the messages (Section 6.23.1.3.6) page for that flight if :
ETFMS messages for the flight can be issued (flights in status A (ATC activated), P (PFD) and E (terminated) should not have access to ETFMS messages) and The user profile permits the user to send these messages. Case Study: Messages (Section 7.1)
Click on the title of a column to sort its content (ascending or descending).
6.23.1.2Flight List 6.23.1.2.1Aerodrome
The Aerodrome tab shows the detailed information for one flight.
Query

Aerodrome: Aerodrome identification. By default, this field is empty. Category: A drop-down list containing: a) Global (set by default) b) Departure

c) Arrival

104
(AO): Aircraft Operator (optional). By default, this field is empty. Traffic Type: Type of traffic. This field supports a drop-down list containing: a) Traffic Load (set by default) b) Traffic Demand c) Reg Traffic Demand WEF: Start time of the query period. By default, this field is set to the <current UTC time> rounded down to the nearest hour. UNT: End time of the query period. Compare: when checked, gives the possibility to compare the current flight list with a flight list based on another type of traffic to spot intruders. With (associated with the Compare filter): This field supports a drop-down list containing (defaults values):

TL vs RD TD vs TL RD vs TD
D. Time Threshold: The absolute threshold value for the difference in time (in minutes) between the displayed flight list and the comparison flight list. A D.Time value is only shown if equal or greater than Abs. D.Time Threshold value. D. Level Threshold: The absolute threshold value for the difference in flight level between the displayed flight list and the comparison flight list. A D.Level value is only shown if equal or greater than Abs. D.Level Threshold value. D. Pos Threshold: The threshold value for the difference in position (in Nm) between the displayed flight list and the comparison flight list. A D.Pos value is only shown if equal or greater than the D.Pos Threshold value.
Result
For each aerodrome matching the submitted query, the Aerodrome list displays the following details:

Checkbox to select a flights prior plotting Toggle arrow to display on/off the flight details box (F15-Route) TOT or TOT/TA or ENTRY or OVER This can be: a) The Take-Off Time (TOT) for the queries based on Aircraft Operator. b) The Take-Off Time (TOT) or Time of Arrival (TA) for the queries based on Aerodrome and Aerodrome Set. c) The ENTRY time for the queries based on Airspace, Regulation and Traffic Volume. d) The time OVER for the queries based on Point. These times are appended with an indication of the source which can be one of the following: a) E for Estimated, when based on the estimated flight profile. b) C for Calculated, when based on the calculated flight profile (allocated slot). c) A for Actual, when based on actual flight profile (after departure).
STA: Late Filer and/or Late Updater (LF | LU | LFU). ARCID: Aircraft identification - clicking on an ARCID opens a Detached View with the flight details for that flight. Note: you can in this way maintain several Flight Details windows at the same time. ATYP: Aircraft type code. ADEP: ICAO code of the aerodrome of departure for the flight. ADES: ICAO code of the aerodrome of destination of the highest available requested model for the flight. i.e. for a diverted flight, it displays: a) The filed ADES when the requested Traffic Type is Traffic Demand or Reg. Traffic Demand. b) The new ADES when the requested Traffic Type is Traffic Load. D: Diversion indicator. The symbol '>' is displayed for a diverted flight.
105
T: Type of flight data. Possible values are: a) A for ACT b) I for IFPL c) P for PFD d) R for RPL e) T for TACT f) E for TERM RFL or ARF : Requested Flight Level or Actual Requested Flight Level For query by Aerodrome, Aerodrome Set or Aircraft Operator, RFL is the highest Requested Flight Level of the flight. For query by Point, Airspace, Traffic Volume or regulation, RFL is the Requested Flight Level applicable on the portion of the flight route that penetrates the sector. When the Flight List is based on the Traffic Demand or the Regulated Demand, the displayed Requested Flight Level (RFL) corresponds to the Flight Level filed by the AO. When the Flight List is based on the Traffic Load, the displayed Actual Requested Flight Level (ARF) corresponds to the Flight Level possibly adapted by profile recalculation for the active flights, otherwise it is the Flight Level filed by the AO. U: Suspension status. Possible values are: a) Empty if the flight is not suspended. b) ST for SIT Time Out. c) SM for Slot Missed. d) RC for Flight Confirmation Message (FCM) required. e) TV for RVR. f) NR for Not Reported as airborne. g) RV for FP_Revalidation. E/CTOT: (Estimated | Calculated) Take-Off Time. The time is followed by 'E' for an estimated time or by 'C' for a calculated time (this field is not shown if the slot is not yet published). X: The number of regulations from which the flight is excluded. X may be preceded by a "!" when the flight is excluded from one or more regulations defined on the Traffic Volume used for the Flight List selection. If the flight was previously excluded from one or more regulations but is no longer, a 'W' will be displayed. F: The Flight Activation Monitoring (FAM) status. Possible values for F are (note, case sensitive): a) N for not under FAM yet or never under FAM. b) F for currently subject to FAM, if no data received, flight will be shifted soon. c) f was subject to FAM but airborne data received before first shift. d) S for currently shifted by FAM. e) s was shifted by FAM, FPL data received when shifted. f) a was shifted by FAM, airborne data received when shifted, g) U for currently suspended by FAM. h) u was suspended by FAM, FPL data received when suspended. i) A was suspended by FAM, airborne data received when suspended. S: The Ready Status. Possible values for S are: a) I when the flight is in Request For direct Improvement (RFI) mode. b) S when the SIP Wanted Message (SWM) mode is on, per opposition to the RFI mode. c) R when the flight is REAdy to depart (REA message received). The REA state has priority (overwrites) the RFI/SWM state. A/TTOT: Actual/Target Take-Off Time. Is either the actual take off time from the DEP, FSA, APR or CPR, or is the same as the E/CTOT when the flight is Tact activated.

00:00blank Tact or ATC activated, departing a non-CDM airport departing from a CDM airport: 00:00e Estimated = latest target take off time from an Early DPI (E -DPI) 00:00t Targeted = latest confirmed AO Target Take off time (T-DPI-c) 00:00s Pre-sequenced = latest sequence ATC target take off time (T-DPI-s) 00:00c previous DPI data no longer valid, new TOT unknown 00:00a Actual take off time when flight is confirmed as airborne 00:00x (italic) when DPI with (future) ATOT has been received. 00:00x (in RED) when a CDM discrepancy is detected
Delay: Delay in minutes (between '*' if slot not yet published).

106
R: Rerouting indicator composed of a reason and optionally a state. The rerouting reason code may be: a) N for not rerouted. b) M for ATFCM rerouting. c) C for CFMU rerouting (CWIR). d) A for auto rerouting (AWIR). e) O for AO rerouting (AOWIR). If the rerouting reason is N, there is no state. Otherwise, the rerouting state code may be: a) P for Produced. There is a valid rerouting going on, waiting to be realised by either an FPL or a CHG. b) E for Executed. Rerouting has been done. c) T for Timed Out. No FPL/CHG received on time. d) R for Rejected. Rerouting proposal has been rejected. e) V for Revoked. Rerouting proposal has been revoked. f) N for No match. Message received did not match the proposal. Rerouting has been invalidated. Opp: Opportunity indicator Set to (Y) if an opportunity for a shorter route exists, blank otherwise. W: The AO What-If Reroute indicator code may be. Indicates if the flight can be re-routed: a) N for No, cannot be rerouted. b) T for Try is allowed. c) A for Apply and Try are allowed. MSG: Type of the last message sent or received for the flight. Case Study: Messages (Section 7.1) REGUL+: Identification of the most penalising regulation for the flight. O: Indication (Y for YES, N for NO) of the existence of Other regulations besides the one indicated in the REGUL+ column. D. Time: The time difference in minutes (max 4 digits) between the flights entry time at the reference location in the displayed flight list and in the comparison flight list. The value is preceded by a + or a - indicating if the entry time in the displayed flight list is later than or before respectively the matched flight in the systems comparison flight list. If the difference is zero, the value is not displayed (blank). The column is only displayed if the Compare checkbox was checked. If a flight in the displayed flight list is not matched with a flight in the systems comparison flight list, the value +9999 is displayed in Intruder colour (blue) to indicate undefined. D.Level The flight level difference (3 digits with leading zeros if necessary) between the flights entry flight level at the reference location in the displayed flight list and in the comparison flight list. The value is preceded by a + or a - indicating if the entry flight level in the displayed flight list is higher than or lower than respectively the matched flight in the systems comparison flight list. If the difference is zero, the value is not displayed (blank). The column is only displayed if the Compare checkbox was checked. If a flight in the displayed flight list is not matched with a flight in the systems comparison flight list, the value +999 is displayed in Intruder colour (blue) to indicate undefined. D.Pos The distance in nautical miles between the geographical position of the flights entry point into the reference location in the displayed flight list and in the comparison flight list. If the difference is zero, the value is not displayed (blank). The column is only displayed if the Compare checkbox was checked. If a flight in the displayed flight list is not matched with a flight in the systems comparison flight list, the value 9999 is displayed in Intruder colour (blue) to indicate undefined. TI: Indication of flight trend at the reference locations entry point as follows: a) Cruise. This is indicated as '='. A cruise indication is shown when the flight vector that includes the entry point (as an end point for trend in) is a cruise vector. b) Climb. This is indicated as '/'. A climb indication is shown when the flight vector that includes the entry point is a climb vector. c) Descent. This is indicated as '\'. A descent indication is shown when the flight vector that includes the entry point is a descent vector. EFL: The flight level over the entry point of the associated reference location. TO: Indication of flight trend at the reference locations exit point as follows:
107
a) Cruise. This is indicated as '='. A cruise indication is shown when the flight vector that includes the exit point (as a start point for trend out) is a cruise vector. b) Climb. This is indicated as '/'. A climb indication is shown when the flight vector that includes the exit point is a climb vector. c) Descent. This is indicated as '\'. A descent indication is shown when the flight vector that includes the exit point is a descent vector. The TI, EFL and TO column are not displayed for Aerodrome, Aerodrome Set or Aircraft Operator queries..
Last column (without heading) The text MSG is displayed providing a link to the messages (Section 6.23.1.3.6) page for that flight if :
CASA messages for the flight can be issued (flights in status A (ATC activated), P (PFD) and E (terminated) should not have access to CASA messages) and The user profile permits the user to send these messages. Case Study: Messages (Section 7.1)
6.23.1.2.2Aerodrome Set
Query

Aerodrome Set: Aerodrome set identification. By default, this field is empty. Category: A drop-down list containing: a) Global (set by default) b) Departure c) Arrival (AO): Aircraft Operator (optional). By default, this field is empty.
108
Traffic Type: Type of traffic. This field supports a drop-down list containing: a) Traffic Load (set by default) b) Traffic Demand c) Reg Traffic Demand WEF: Start time of the query period. By default, this field is set to the <current UTC time> rounded down to the nearest hour. UNT: End time of the query period. Compare: when checked, gives the possibility to compare the current flight list with a flight list based on another type of traffic to spot intruders. With (associated with the Compare filter): This field supports a drop-down list containing (defaults values):

Result
The result table for the whole Flights List Detached view is nearly the same from one query method to another please go to the Aerodrome (Section 6.23.1.2.1) page to get the details. Case Study: Messages (Section 7.1)
6.23.1.2.3Aircraft Operator
109
Query

Operator: Aerodrome set identification. By default, this field is empty. Traffic Type: Type of traffic. This field supports a drop-down list containing: a) Traffic Load (set by default) b) Traffic Demand c) Reg Traffic Demand WEF: Start time of the query period. By default, this field is set to the <current UTC time> rounded down to the nearest hour. UNT: End time of the query period. Compare: when checked, gives the possibility to compare the current flight list with a flight list based on another type of traffic to spot intruders. With (associated with the Compare filter): This field supports a drop-down list containing (defaults values):

Result

110
6.23.1.2.4Airspace
Query

Airspace: Airspace identification. By default, this field is empty. (AO): Aircraft Operator (optional). By default, this field is empty. Traffic Type: Type of traffic. This field supports a drop-down list containing: a) Traffic Load (set by default) b) Traffic Demand c) Reg Traffic Demand WEF: Start time of the query period. By default, this field is set to the <current UTC time> rounded down to the nearest hour. UNT: End time of the query period. Compare: when checked, gives the possibility to compare the current flight list with a flight list based on another type of traffic to spot intruders. With (associated with the Compare filter): This field supports a drop-down list containing (defaults values):

D. Time Threshold: The absolute threshold value for the difference in time (in minutes) between the

displayed flight list and the comparison flight list. A D.Time value is only shown if equal or greater than Abs. D.Time Threshold value.
111
D. Level Threshold: The absolute threshold value for the difference in flight level between the displayed flight list and the comparison flight list. A D.Level value is only shown if equal or greater than Abs. D.Level Threshold value. D. Pos Threshold: The threshold value for the difference in position (in Nm) between the displayed flight list and the comparison flight list. A D.Pos value is only shown if equal or greater than the D.Pos Threshold value.
Result
6.23.1.2.5Point
Query

Point: Significant point identifier. By default, this field is empty. FL: Min Minimum flight level. This field supports a drop-down list containing: a) Values from 000 to 290 in steps of 5, followed by b) Values from 290 to 650 in steps of 10, followed by c) unl, for unlimited. By default, this field is set to 000. Max: Maximum flight level. This field supports a drop-down list containing: a) Values from 000 to 300 in steps of 5, followed by b) Values from 310 to 650 in steps of 10, followed by c) unl, for unlimited. By default, this field is set to unl. (AO): Aircraft Operator (optional). By default, this field is empty. Traffic Type: Type of traffic. This field supports a drop-down list containing: a) Traffic Load (set by default) b) Traffic Demand c) Reg Traffic Demand WEF: Start time of the query period. By default, this field is set to the <current UTC time> rounded down to the nearest hour. UNT: End time of the query period.
112
Compare: when checked, gives the possibility to compare the current flight list with a flight list based on another type of traffic to spot intruders. With (associated with the Compare filter): This field supports a drop-down list containing (defaults values):

Result
6.23.1.2.6Regulation
Query

Regulation: Regulation identifier. By default, this field is empty. (AO): Aircraft Operator (optional). By default, this field is empty. Traffic Type: Type of traffic. This field supports a drop-down list containing: a) Traffic Load (set by default) b) Traffic Demand c) Reg Traffic Demand WEF: Start time of the query period. By default, this field is set to the <current UTC time> rounded down to the nearest hour. UNT: End time of the query period. Compare: when checked, gives the possibility to compare the current flight list with a flight list based on

another type of traffic to spot intruders.
113
With (associated with the Compare filter): This field supports a drop-down list containing (defaults values):

Result
6.23.1.2.7Traffic Volume
Query

114
Traffic Volume: Traffic volume set identifier. By default, this field is empty. (Flow): Flow identifier (optional). (AO): Aircraft Operator (optional). By default, this field is empty. Traffic Type: Type of traffic. This field supports a drop-down list containing: a) Traffic Load (set by default) b) Traffic Demand c) Reg Traffic Demand WEF: Start time of the query period. By default, this field is set to the <current UTC time> rounded down to the nearest hour. UNT: End time of the query period. Compare: when checked, gives the possibility to compare the current flight list with a flight list based on another type of traffic to spot intruders. With (associated with the Compare filter): This field supports a drop-down list containing (defaults values):

Result
The result table for the whole Flights List Detached view is nearly the same from one query method to another please go to the Aerodrome (Section 6.23.1.2.1) page to get the details.
Case Study: Messages (Section 7.1)
6.23.1.3Flight Details 6.23.1.3.1Details
115
The Details tab shows the detailed information for one flight. Query The query for which the Flight Details detached View is generated is reminded on top of the window:

ARCID: Aircraft identification. ADEP: Aerodrome of departure. IOBD: Initial Estimated Off-Block Date (Today or Yesterday) IOBT: Initial Estimated Off-Block Time. ADES: Aerodrome of Destination
Result
1. General Flight Information

AO: ICAO code of the aircraft operator. OPR AO: ICAO code of the operating aircraft operator. FPL Origin : Originator of the flight plan. Aircraft Type: Type of aircraft. Initial RFL: Initial Requested Flight level. Registration Mark: Aircraft registration mark. RVR: Runway visual range. CEQPT: The list of radio communication, navigation and approach aid equipment types as provided in the flight plan.
2.
Timing Information (group header Time)
Last EOBT: Last received Estimated Off-Block date and Time (dd-hh:mm format).

116
ETOT: Estimated Take-Off Time. CTOT: Calculated Take-Off Time. ATOT: Actual Take-Off Time. Prop CTOT : Eventual ETFMS Proposed Calculated Take-Off Time. EET: Estimated Elapsed Time. Taxi Time: Taxi Time in minutes. Actual Taxi Time: Actual Taxi Time in minutes. Resp By: The time by which the Prop CTOT has to be accepted or rejected. ETA: Estimated Time of Arrival. CTA: Calculated Time of Arrival. ATA: Actual Time of Arrival.
3.
Status Information (group header Status)

Flight Type: Type of flight. (ACT, IFPL, PFD, RPL, TACT, TERM). Late Filer: If the flight is a late filer. Late Updater: If the flight is a late updater. Exempt Flight: If the flight is exempted from regulation. RFI: If the flight is in Request For Improvement mode (RFI=Y). Or if the flight is in SIP Wanted Message mode (RFI=N). REA: If a REAdy to depart message has been received for this flight. TIS: Time needed to Insert in Sequence. TRS: Time needed to Remove from Sequence.
4.
Airport CDM Information (group header Airport)
Status : The CDM Flight Status. Possible CDM Status are : a) "Not departing from a CDM airport" with no time that follows. b) "Departing from a CDM airport" with no time that follows. c) "Estimated" (a valid E-DPI has been received) d) "Targeted" (a valid T-DPI_c has been received) e) "(Pre)Sequenced" (a compliant T-DPI_s has been received). f) "Actual Off-Block" (a valid ATC DPI has been received). TW: Slot Tolerance Window for Regulated Flights or Departure Tolerance Window for Non-Regulated Flights. SID : The Departure procedure fixed connecting point. Aircraft Type : The ICAO identifier of the Aircraft Type. It is appended with the warning symbol (!) and both are displayed in discrepancy colour if different from the field aircraft type. Registration Mark: The Registration Mark, if any. It is appended with the warning symbol (!) and both are displayed in discrepancy colour if different from the field registration mark. No Slot Before: The No Slot Before Time, if any. Departure Status: if not Ok. Provisional Info: The Provisional CDM Information, if any, is grouped in a specific box. The Provisional CDM Information consists of: Provisional target TOT=HH:MM Evaluation at HH:MM, possibly appended on subsequent line with:(No problem to report), or appended with any combination of the following on subsequent lines: (REGUL+=REG12345) (Poss CASA TOT=HH:MM) (Suspension=reason) (Departure Status=xxxx)
5. Regulation and Rerouting Information (group header Regulation)

117
Rerouting warning message: The rerouting status and AOWIR possibilities. The rerouting status is only displayed if applicable. It is composed of a reason and a state. If the flight has been rerouted, the displayed rerouting reason may be: a) ATFCM rerouting. b) CFMU rerouting (CWIR). c) Auto rerouting (AWIR). d) AO rerouting (AOWIR). When there is a rerouting reason, it is followed by one of these rerouting states: a) Produced for a valid rerouting going on, waiting to be realised by either an FPL or a CHG. b) Executed when the rerouting has been processed. c) Timed-out when no FPL/CHG was received on time. d) Rejected for a rerouting proposal that has been rejected. e) Revoked for a rerouting proposal has been revoked. f) No-match when the message received did not match the proposal. Rerouting has been invalidated. The AOWIR indicator may be one of the following: a) Reroute TRY and Apply NOT allowed. b) Reroute Try possible. c) Reroute TRY and Apply possible.
FLS Resp By: Time limit for the Confirmation message (FCM) after the issue of a Flight Suspension (FLS). Rerouting Ref: The reference of the rerouting affecting the flight. Most Penal Reg: The reference of the most penalising regulation affecting the flight. Regcause: The code of the cause for the regulation. Delay: The resulting delay for the flight (between * if not yet published). RRP Resp By: The time limit to reply to the proposed rerouting. Slot Tol Viol: The slot tolerance violation in minutes (ATOT vs. CTOT). Last MSG Sent/Received: Last ATFCM message sent or received for the flight. Originator: Eventual originator of the last message. Regulation Table: List of regulations affecting the flight plan. 1. Regulation: Regulation identifier 2. FCM : Indication that a Flight Confirmation Message (FCM) is still required. In this case, the keyword Req is displayed. 3. Ref Location : Corresponding list of reference locations on which regulations are defined. 4. suspension warning Only displayed when Suspension Status is different from Not Suspended. Possible reasons for suspension are: a) Flight suspended SIT Time Out. b) Flight suspended Slot Missed. c) Flight suspended FCM Required. d) Flight suspended RVR. e) Flight suspended Not Reported as Airborne. f) Flight suspended FP Revalidation
6.23.1.3.2Point Profile
Possible values for TYPE are: a) ES: Elementary sector. b) CS: Collapsed sector.

c) FIR: Flight Information Region. d) REG: Region. e) AUA: ATC Unit Airspace. f) RSA: Restricted Airspace. g) CDA: Client Defined Airspace. h) AUAG: ATC Unit Airspace Group. i) NAS: National Airspace. j) AREA: CFMU or EUROCONTROL defined area. k) IFPZ: IFPS zone.
118
6.23.1.3.2.1Elaps.Time PT Profile
The Elaps. Time PT Profile is based on the time over the points The Elaps. Time PT Profile Tab shows a table divided in four main sections: 1. 2. 3. Elapsed Time - time elapsed since departure Estimated - list based on Estimated profile from the flight plan Calculated - list based on Calculated profile when available. Calculated profile is calculated after the ATFCM measures are applied (regulations will modify the times, rerouting may also modify the route). Actual - list based on Actual profile when available. Actual profile is calculated according to the effective departure time.
4.
A Show Vector Elements check box, checked On by default, allows to include or exclude from the displayed list Vector Elements calculated by the ETFMS system. For each Estimated route point, the list details the following:
Route: The route identifier (Air Route, Departure / Arrival procedure, ), sometimes replaced by keyword

Direct when flying direct.

119
Point: Point identification. FL: Estimated Flight Level over the point. Time Over: Estimated Time Over the corresponding point.
For each Calculated route point, the list details the following:
Route: The route identifier (Air Route, Departure / Arrival procedure, ), sometimes replaced by keyword Direct when flying direct. Point: Point identification. FL: Estimated Flight Level over the point. Time Over: Calculated Time Over the corresponding point.
For each Actual route point, the list details the following:
Route: The route identifier (Air Route, Departure / Arrival procedure, ), sometimes replaced by keyword Direct when flying direct. Point: Point identification. FL: Actual or Estimated Flight Level over the point. Time Over: Actual Time Over the corresponding point.
6.23.1.3.2.2Act. Time PT Profile
120
The Act. Time PT Profile is based on the time over the points The Act. Time PT Profile Tab shows a table divided in four main sections: 1. 2. 3. Time Over - time over the corresponding point. Estimated - list based on Estimated profile from the flight plan Calculated - list based on Calculated profile when available. Calculated profile is calculated after the ATFCM measures are applied (regulations will modify the times, rerouting may also modify the route). Actual - list based on Actual profile when available. Actual profile is calculated according to the effective departure time.
4.
A Show Vector Elements check box, checked On by default, allows to include or exclude from the displayed list Vector Elements calculated by the ETFMS system. For each Estimated route point, the list details the following:
Route: The route identifier (Air Route, Departure / Arrival procedure, ), sometimes replaced by keyword Direct when flying direct. Point: Point identification. FL: Estimated Flight Level over the point. Elapsed Time: Estimated Elapsed Time Over the corresponding point.
For each Calculated route point, the list details the following:
Route: The route identifier (Air Route, Departure / Arrival procedure, ), sometimes replaced by keyword Direct when flying direct. Point: Point identification. FL: Estimated Flight Level over the point. Time Over: Calculated Elapsed Time Over the corresponding point.
For each Actual route point, the list details the following:
Route: The route identifier (Air Route, Departure / Arrival procedure, ), sometimes replaced by keyword Direct when flying direct. Point: Point identification. FL: Actual or Estimated Flight Level over the point. Time Over: Actual Elapsed Time Over the corresponding point.
6.23.1.3.2.3Elaps. Time AS Profile
121
The Elaps. Time AS Profile is based on the elapsed flying time since take off to the time of entry of the flight into the airspace.
The Elaps. Time AS Profile Tab shows a table divided in four main sections: 1. 2. 3. 4. Elapsed Time - time elapsed since departure Estimated - list based on Estimated profile from the flight plan Calculated - list based on Calculated profile when available. Calculated profile is calculated after the ATFCM measures are applied (regulations will modify the times, rerouting may also modify the route). Actual - list based on Actual profile when available. Actual profile is calculated according to the effective departure time.
A Acive ES+CS only check box, checked On by default, allows to show only the ES and CS Active Airspaces or to o include in the displayed all airspaces types traversed along the profiles For each airspace type along the route, the Estimated list details the following: Id: Airspace Identification Type: Airspace type. Entry: Elapsed Flying Time at Entry of the flight in the airspace Exit: Elapsed Flying Time at Exit of the flight from the airspace
For each airspace type along the route, the Calculated list details the following: Id: Airspace Identification Type: Airspace type. Entry: : Elapsed Flying Time at Entry of the flight in the airspace Edited & produced by the CFMU/User Relations and Development Bureau 2009 European Organisation for the Safety of Air Navigation (EUROCONTROL) - V2.0.23 - 23/08/2010 - page 121/172

Exit: Elapsed Flying Time at Exit of the flight from the airspace.
122
For each airspace type along the route, the Actual list details the following: Id: Airspace Identification Type: Airspace type. Entry: Elapsed Flying Time at Entry of the flight in the airspace Exit: Elapsed Flying Time at Exit of the flight from the airspace.
6.23.1.3.2.4Act. Time AS Profile
The Actual. Time AS Profile is based on the time of entry of the flight into the airspace.
The Actual. Time AS Profile Tab shows a table divided in four main sections: 1. 2. 3. 4. Entry Time Entry Time in the airspace Estimated - list based on Estimated profile from the flight plan Calculated - list based on Calculated profile when available. Calculated profile is calculated after the ATFCM measures are applied (regulations will modify the times, rerouting may also modify the route). Actual - list based on Actual profile when available. Actual profile is calculated according to the effective departure time.
A Acive ES+CS only check box, checked On by default, allows to show only the ES and CS Active Airspaces or to include in the displayed all airspaces types traversed along the profiles Edited & produced by the CFMU/User Relations and Development Bureau 2009 European Organisation for the Safety of Air Navigation (EUROCONTROL) - V2.0.23 - 23/08/2010 - page 122/172

For each airspace type along the route, the Estimated list details the following: Id: Airspace Identification Type: Airspace type. Entry: Estimated Time of Entry of the flight in the airspace Exit: Estimated Time of Exit of the flight from the airspace.
123
For each airspace type along the route, the Calculated list details the following: Id: Airspace Identification Type: Airspace type. Entry: Calculated Time of Entry.of the flight in the airspace Exit: Calculated Time of Exit of the flight from the airspace.
For each airspace type along the route, the Actual list details the following: Id: Airspace Identification Type: Airspace type. Entry: Actual Time of Entry of the flight in the airspace Exit: Actual Time of Exit of the flight from the airspace.
6.23.1.3.3Flight History
For each flight event history, the Flight History tab list lists the following:

124
Event Type: Type of the event received for the flight. At: Date and time (dd-hh:mm format) of the event. Resulting Status: Status of the flight after the event. New OBT: New Off-Block date and Time (dd-hh:mm format) after the event. EFD: E is displayed if an ETFMS Distribution Message (EFD) has been sent. FUM: F is displayed if a Flight Update Messages (FUM) has been sent.
The columns are NOT sortable here.
6.23.1.3.4Operational Log
The Operational Log tab displays a list of operational logs - within the 24 hours ending one minute after the query was executed. For each operational log that satisfied the query submitted (automatic or manual), the list displays the following details:

Stamp: The date and time (DD-HH:MM:SS format) when that log entry was recorded. TACT ID: The ETFMS unique identification key for the flight. IFPS ID: The eventual IFPS unique identification key for the flight. Oplog Type: Composed of a classification code and the event kind description. The classification code can be: a) UD for Undefined. b) IM for Incoming Message. c) ER for Erroneous Incoming Message. d) OM for Outgoing Message. e) VI for Violation.

f) HI for History. g) WA for Warning. h) PE for Process Error. i) EM for Error Message. j) EN for Environment Message. k) UC for User Command. l) TM for Text Message.

125
Correspondent: The eventual identification of the issuer of the message. Details: The detailed text of the message. These are revealed when you click on the above example, the details for the second event have been expanded. arrow button. On the
The columns are NOT sortable here.
6.23.1.3.5Alternate Routes
The Alternate Route tab shown above is limited to certain user profiles - you might very well not see it in your detached view of the Flight Details.
Case Study: AOWIR (Section 7.2)
6.23.1.3.6Messages
//Under development

Case Study: Messages (Section 7.1)
126
6.23.1.4Plotting flights on the Map

Plotting a flight from the Flight List detached view is very straightforward. All you need to do is check in the list the flight(s) you wish to plot on the Map and click on the Plot Selected Flights button, as highlighted below:
A new window opens with the selected route(s) against the Map:

The Map background may differ from what you see here, depending on your map preference settings. Check this section (Section 6.10.4) to get all the details on the Map and on the various plotting functions availagle in the NOP.
127
6.24IFPUV
Typical Scope:
The IFPUV portlet gives access to the IFPS Validation system (IFPUV). It is aimed to allow Airspace Users and Aerodrome Reporting Offices to submit their flight plans to a dedicated test system for validation, prior to their submission to the operational system. It may also be used to find an IFPS compliant route. The tool delivers the shortest possible IFPS compliant routes taking into consideration some user defined constraints (e.g. via a point or airspace, avoiding a point or airspace). The IFPUV contains the current IFPS software and receives copies of updates to the operational environment database, fed by live updates. The IFPUV is therefore an accurate reflection of the operational system. The Free Text Editor and the Structured Editor both feature two tabs, one for FPL Validation and the other to Propose Routes. The FPL Validation mode is set as default for both the Free Text Editor and the Structured Editor. The main difference between the two editor modes resides in the way to enter the flight plan : one single text field for the Free Text Editor against a set of form elements ensuring data quality in the Structured Editor. Caution:

Flight plans submitted to IFPUV for pre-validation are not stored. Manual correction is not possible. The IFPUV response is automatic. Flight plan originators are reminded that flight plan messages must be submitted to the IFPS to ensure acceptance in the operational system. The routes that are proposed by IFPUV are not to be considered as CFMU recommended routes. IFPUV is NOT a flight planning system. The responsibility to ensure operational acceptance of the IFPUV proposed routes before filing to IFPS is with the flight plan originator.
6.24.1Free Text Editor - FPL Validation
128
The Free Text Editor tab allows you to enter a flight plan directly in ADEXP format and then validate it.
Query
Introduce a flight plan: An edit text area to enter a flight plan in ADEXP format. By default, this field is empty.
Result

Flight plan entered: The Flight plan as you entered it Results: Message area.
If the submitted flight plan is correct, the message is "NO ERRORS". The flight plan is therefore considered as validated. If the submitted flight plan is not correct, a message indicating the affected parameter and the nature of the error is displayed - see example below. You can then make the necessary corrections and resubmit the query, until the "NO ERRORS" message is returned.
129
6.24.2Free Text Editor - Propose Routes
130
Query
Introduce a flight plan: An edit text area to enter a flight plan. By default, it is set to the text entered whilst in the FPL Validation tab. Via point(s): List of published points to be overflown. By default, this field is empty. Via airspace(s): List of airspaces that must be traversed (in 2D projection), separated by space. The CFMU airspace identification must be used to indicate an airspace to be traversed. By default, this list is empty. Avoiding point(s): List of published points to be avoided, separated by a aspace. By default, this field is empty. Avoiding airspace(s): List of airspaces that must be avoided (in 2D projection), separated by a space. The CFMU airspace identification must be used to indicate an airspace to be avoided. By default, this field is empty. Frozen first point: The end point of a route segment to be frozen at the beginning of the route. All proposed routes shall contain the route segment from the departure aerodrome up to the indicated point. In the case of circular routes, the first point encountered is considered, resulting in the minimal frozen portion. Note: Freezing will NOT preserve any information present in a VFR, OAT or STAY portion of route.
Last point: The start point of a route segment to be frozen at the end of the route. All proposed routes shall contain the route segment from the indicated point up to the destination aerodrome. In the case of circular routes, the last point encountered is considered, resulting in the minimal frozen portion.

Note: Freezing will NOT preserve any information present in an invisible portion (e.g. VFR segments).
131
Propose only RAD compliant routes: When checked, IFPUV only returns routes that are RAD compliant. If not checked, it returns all possible routes. By default, the field is checked. Max number of proposals: Maximum number of proposed routes required from IFPUV. By default, the field is set to 5. New FPL: Reset all the values to default prior to validating a new flight plan.
Result

Flight plan entered: The entered flight plan. Results: IFPUV reply. The reply may display: a) In FPL Validation mode:

A list of errors in the entered flight plan. Indication of 'No errors'.
b) In Propose Routes mode:

A list of errors in the query. A list of proposed routes. Indication of 'No routes found'.
See below the reply for the requested flight plan, with no airspace or point restriction, limited to a maximum of 3 proposed routes.
132
6.24.3Structured Editor - FPL Validation
133
The Structured Editor tab allows you to fill in various fields of a flight plan and then validate it against IFPUV.
Query

MESSAGE TYPE: A read-only field set to FPL. AIRCRAFT ID: Aircraft identification. By default, the field is empty. FLIGHT RULES: Flight rules. In the Flight Assistant mode, a drop-down list allows to select a possible value from: a) I for IFR. b) V for VFR. c) Y for IFR changing to VFR. d) Z for VFR changing to IFR. e) Empty the default value. TYPE OF FLIGHT: Flight type. A drop-down list allows selecting a possible value from: a) S for scheduled. b) N for non-scheduled. c) G for general. d) M for military. e) X for training. f) Empty the default value. NUMBER: Number of aircraft, if more than one in case of formation flights. By default, the field is empty. TYPE OF AIRCRAFT: Aircraft type. By default, the field is empty. WAKE TURBULENCE CAT: Wake turbulence category indicating maximum certified take-off mass of the aircraft. A drop-down list allows selecting a possible value from: a) J for super. b) H for heavy. c) M for medium. d) L for light. e) Empty the default value.
134
EQUIPMENT: Comprises of the following two fields: a) Radio communication, navigation and approach aid equipment. b) Surveillance equipment. By default, both the fields are empty. ADEP: ICAO code of the aerodrome of departure. By default, the field is empty. TIME: Estimated Off-Block time. By default, the field is empty. CRUISING SPEED: The true airspeed for the first or the whole cruising portion of the flight. By default, the field is empty. LEVEL: Requested cruising level. By default, the field is empty. ADES: ICAO code of the aerodrome of destination. By default, the field is empty. TOTAL EET: Total Estimated Elapsed Time (hhmm). By default, the field is empty. ALTN AERODROME: ICAO code of the first alternate aerodrome of destination. By default, the field is empty. 2ND ALTN AERODROME: ICAO code of the second alternate aerodrome of destination. By default, the field is empty. ROUTE: Flight plan route. By default, the field is empty. OTHER INFORMATION: Any other necessary information in the form of the appropriate abbreviation followed by an oblique stroke and the information to be recorded. By default, the field is empty. New FPL: Link to reset all the values to default prior to validating a new flight plan.
Result

Flight plan entered: The Flight plan as you entered it Results: Message area.
If the submitted flight plan is correct, the message is "NO ERRORS". The flight plan is therefore considered as validated. If the submitted flight plan is not correct, a message indicating the affected parameter and the nature of the error is displayed - see example below. You can then make the necessary corrections and resubmit the query, until the "NO ERRORS" message is returned.
See below an example for a correct Flight Plan.
135
6.24.4Structured Editor - Propose Route

Access to the Propose Routes mode is restricted by security profile and limited to the ARO. This section may therefore not concern you.
136
Query

MESSAGE TYPE: A read-only field set to FPL. AIRCRAFT ID: Aircraft identification. By default, the field is empty. FLIGHT RULES: In the Propose Route mode, FLIGHT RULES is pre-set to I. TYPE OF FLIGHT: Flight type. A drop-down list allows selecting a possible value from: a) S for scheduled. b) N for non-scheduled. c) G for general. d) M for military. e) X for training. f) Empty the default value. NUMBER: Number of aircraft, if more than one in case of formation flights. By default, the field is empty. TYPE OF AIRCRAFT: Aircraft type. By default, the field is empty. WAKE TURBULENCE CAT: Wake turbulence category indicating maximum certified take-off mass of the aircraft. A drop-down list allows selecting a possible value from: a) J for super. b) H for heavy. c) M for medium. d) L for light. e) Empty the default value. EQUIPMENT: Comprises of the following two fields: a) Radio communication, navigation and approach aid equipment. b) Surveillance equipment. By default, both the fields are empty. ADEP: ICAO code of the aerodrome of departure. By default, the field is empty.

137
TIME: Estimated Off-Block time. By default, the field is empty. CRUISING SPEED: The true airspeed for the first or the whole cruising portion of the flight. By default, the field is empty. LEVEL: Requested cruising level. By default, the field is empty. ADES: ICAO code of the aerodrome of destination. By default, the field is empty. TOTAL EET: Total Estimated Elapsed Time (hhmm). By default, the field is empty. ALTN AERODROME: ICAO code of the first alternate aerodrome of destination. By default, the field is empty. 2ND ALTN AERODROME: ICAO code of the second alternate aerodrome of destination. By default, the field is empty. Via point(s): List of published points to be overflown. By default, the field is empty. Via airspace(s): List of airspaces that must be traversed (in 2D projection). By default, the field is empty. Avoid point(s): List of published points to be avoided. By default, the field is empty. Avoid airspace(s):List of airspaces that must be avoided (in 2D projection). By default, the field is empty. Propose only RAD compliant routes: When checked, IFPUV only returns routes that are RAD compliant. If not checked, it returns all possible routes. By default, the field is checked. Max number of proposals: Maximum number of proposed routes required from IFPUV. By default, the field is empty. New FPL: Link to reset all the values to default prior to validating a new flight plan.
Result

Flight plan entered: The entered flight plan in ADEXP format. Results: IFPUV reply. The reply may display: a) A list of errors in the entered flight plan. b) A list of possible routes. c) Indication of no errors.
138
See above the reply for the requested flight plan to include the point ETENO and avoid the point SOPUL.
6.25Main Reports
Typical Scope:
The Main Reports Portlet offers links to the main CFMU reports published periodically (yearly, seasonally).
6.26Measures
Typical Scope:
139
The Measures Portlet is meant to execute queries on ATFCM Measures. The Portlet is divided in two tabs, each one featuring a simple querying interface for:

Regulation Rerouting
Any query in one of these tabs will open the same Detached View, however already opened on the appropriate Main tab and Secondary tab, and with the retrieved matching data displayed under a much more elaborate querying panel. Go to the topic of your choice to learn more: Regulation (Section 6.26.1) | Rerouting (Section 6.26.2)
6.26.1Regulation
In the Regulation tab, the Query pull-down menu proposes three different filters: Regulation List, Regulation Details and Regulation Delays. Irrespectively of the selected filter(s), click on the Go button to launch the query and open the Measures Detached View and get the results. You can alternatively press the Enter key to launch the query
Regulation List

Query: the selected filter (Regulation List in this case) Traffic Volume Set: A drop-down list containing all system known traffic volume sets Active Regulation Only: When checked, it indicates that only active regulation measures are to be retrieved.
Regulation Details
Query: the selected filter (Regulation Details in this case) Regulation: The Regulation identifier (empty by default)
Regulation Delays
140
Query: the selected filter (Regulations Delays in this case) Regulation: The Regulation identifier (empty by default)
6.26.2Rerouting
In the Rerouting tab, the Traffic Volume Set pull-down menu proposes a list containing all system known traffic volume sets. Make your selection and click on the Go button to launch the query and open the Measures Detached View and get the results. You can alternatively press the Enter key to launch the query
6.26.3Querying Measures from within the Detached View

You do not need to come back to the Portlet to work with Measures. The Navigation and Query panel provide all the necessary elements to make all the queries, as shown on the image below.
Access Structure
141
Regulation

Regulation List (Section 6.26.3.1) Regulation Details (Section 6.26.3.2) Regulation Delays (Section 6.26.3.3)
Rerouting (Section 6.26.3.4)
Time Stamp
Submitting a Query
6.26.3.1Regulation List
The Regulations List page lists the regulation measures for one or all FMPs (traffic volume sets) for the selected Target Date.
Query

Traffic Volume Set: a drop-down list of all system known FMPs. By default, this field is set to ALL. Active: A checkbox. When checked, it indicates that only active regulation measures are to be retrieved. When unchecked, it indicates that all regulation measures are to be retrieved. By default, the checkbox is unchecked.
Result
For each regulation matching the submitted query, the Regulation List displays the following details:

REG ID: Reg ID Identification of the regulation. Status: Status of the regulation measure. Possible values are: a) Not Active

b) Activating c) Active d) Modifying e) Terminated f) Cancelling g) Cancelled

142
Traf Vol: Traffic volume affected by the regulation Ref Location: Reference location of the traffic volume. WEF: Start date and time (dd-hh:mm format) of the regulation. UNT: End date and time (dd-hh:mm format) of the regulation. LFRSX: Concatenation of the following 5 regulation statuses: a) L: The link state indicates that the regulation is linked to other regulations to calculate the delays. Set to: A for Automatic Link, M for Manual Link or L when Both Automatic and Manual Links are present. b) F: The indication that a Confirmation message is required when a flight is affected by this regulation. Set to F if applicable, otherwise remains empty. c) R: The indication that a Runway Visual Range (RVR) is associated to one or more sub-periods. Set to R if applicable, otherwise remains empty. d) S: The indication that flights affected by this regulation have to be shifted for one or more sub-periods. Set to S if applicable, otherwise remains empty. e) X: The indication for exemption from other regulations. Set to X if applicable, otherwise remains empty. Reason: Regulation reason. Possible values are: a) ATC CAPACITY b) ATC IND ACTION c) ATC ROUTEINGS d) ATC STAFFING e) ATC EQUIPMENT f) ACCIDENT/INCIDENT g) AERODROME CAPACITY h) DE-ICING i) EQUIPMENT NON-ATC j) IND ACTION NON-ATC k) MILITARY ACTIVITY l) SPECIAL EVENT m) ENVIRONMENT ISSUES n) WEATHER o) OTHER
By default, the regulations list is sorted by WEF in increasing time order (taking into account the date and time), and then for the same WEF, in ascending alphanumeric order of Reg ID. You can modify the sort status and direction of any of the column by simply clicking of its title (with exception to the last delays column). The Reg ID and delays fields provide direct link to respectively access the Regulation Details (Section 6.26.3.2) and Regulation Delays (Section 6.26.3.3) tabs for the selected regulation.
6.26.3.2Regulation Details
143
The Regulation Details tab lists the details of the selected Regulation Measure for the selected Target Date.
Query
Regulation: Identification of the regulation. If the Regulation Details page is accessed from the Portlet, by default, this field is empty. If the Regulation Details page is accessed from the Regulations List tab, by default, this field is set to the regulation identification for which this tab was invoked.
Result
The Regulation Details displays the following information:

Regulation ID: Identification of the regulation. Traffic Volume: Traffic volume affected by the regulation. Status: Status of the regulation measure. Possible values are: a) Not Active. b) Activating. c) Active. d) Modifying. e) Terminated. f) Cancelling. g) Cancelled. Period: Start and end date and time of the regulation. Exempted: Indication (Yes/No) if flights affected by this regulation are exempted from other regulations. Reason: Regulation reason. Possible values are: a) ATC CAPACITY b) ATC IND ACTION

c) ATC ROUTEINGS d) ATC STAFFING e) ATC EQUIPMENT f) ACCIDENT/INCIDENT g) AERODROME CAPACITY h) DE-ICING i) EQUIPMENT NON-ATC j) IND ACTION NON-ATC k) MILITARY ACTIVITY l) SPECIAL EVENT m) ENVIRONMENT ISSUES n) WEATHER o) OTHER

144
Description: Full text description, if any, of the regulation. Window Width: The window width related to the regulation. AutoLink: Indication (Yes/No) if the local delay given by this regulation will be taken into account to compute the delay in other regulations.
For each Supplementary Period of the regulation, the sub periods list displays the following details:
Start: The start date and time (dd-hh:mm format) within the Regulation activity period. This sub-period ends when the next one starts or at the end of the Regulation activity period if no other sub-period follows. End: The end date and time (dd-hh:mm format). Rate: The associated rate for the supplementary sub-period.
The Details also provide a direct link to access the Regulation Delays (Section 6.26.3.3) tab for the selected regulation.
6.26.3.3Regulation Delays
145
The Regulation Delays tab presents in tabular and graphical forms the regulated traffic demands and delay statistics of the selected regulation measure for the associated regulation period.
Query
Regulation: Identification of the regulation. If the Regulation Details page is accessed from the Portlet, by default, this field is empty. If the Regulation Details page is accessed is accessed from either the Regulations List tab or the Regulation Details tab, by default, this field is set to the regulation identification for which this tab was invoked.
Result
The Regulation Delays displays the following details for every 20 minute intervals of the regulation duration:

Time: Delay statistics for the duration of the regulation period at 20 minute intervals. Regulated Traffic Demand: CASA Delayed Regulated Traffic Demand in number of Flights for the time interval. Delayed Traffic: Delayed Traffic Load in number of Flights for the time interval. Average Delay: The average delay in minutes for the time interval. Maximum Delay: The maximum delay in minutes for the time interval. Total Delay: The total delay in minutes for the time interval.
The Details also provide a direct link to access the Regulation Delays (Section 6.26.3.3) tab for the selected

regulation. Note that the columns are not sortable in the Regulation Delays result table.
146
6.26.3.4Rerouting List
The Rerouting List tab lists the rerouting measures applied on one or all FMPs (traffic volume sets) for the selected Target Date.
Query
Traffic Volume Set: a drop-down list of all system known FMPs. By default, this field is set to ALL.
Result
The Rerouting List displays the following details:

Rrt. Ref: Rerouting measure reference. Mode: The rerouting measure Mode. One shot when the rerouting measure will be applied only once on the selected flights. Recurrent when the rerouting measure will be applied on selected flights and will be applicable to all future received flights that are affected by the measure. A recurrent mode rerouting measure will be effective until the end of the reference period or until it is cancelled. Traf. Vol: Traffic volume affected by the rerouting measure. Ref. Location: The reference location of the traffic volume. WEF: The start time of the rerouting measure, if any. UNT: The end time of the rerouting measure, if any. New Route: The new route identification. Description: The new route description. 26.3.2. Default Sort Order By default, the rerouting list is sorted by WEF in increasing time order (taking into account the date and the time), and then for the same WEF, in ascending alphanumerical order of Rrt. Ref. 26.3.3. Sortable Columns The rerouting list can be sorted by any one of the following fields: a) Rrt. Ref: initial sort direction being in ascending alphanumeric order. b) Mode: initial sort direction being in ascending alphabetic order. c) Traf. Vol: initial sort direction being in ascending alphanumeric order. d) Ref. Location: initial sort direction being in ascending alphanumeric order. e) WEF: initial sorting direction being blank first then in increasing time order (taking into account the date and the time). f) UNT: initial sorting direction being blank first then in increasing time order (taking into account the date and the time).
147
By default, the Rerouting List is sorted by WEF in increasing time order (taking into account the date and the time), and then for the same WEF, in ascending alphanumerical order of Rrt. Ref. You can modify the sort status and direction of any of the column by simply clicking of its title (with exception to the last Description column).
6.27Network Axis Management

Typical Scope:
The Network Axis Management Portlet presents some elements formerly carried by the seasonal Network Operations Plan. This is were you will find background information in the major flows:

South West Axis South East Axis North East Axis
6.28Network Headline News

Typical Scope:
This Portlet announces events that have a significant impact on the ATFCM Network the same way the headlines of a newspaper announce the main events of the day. These events may be foreseen or not. Examples:

Industrial action, Airspace closure, Sporting event, Bad weather with significant regional impact, etc. Headline news must not be confused with AIMs (ATFCM Information messages). Events with minor or local impact on the ATFCM Network may be announced via an AIM while significant events will be announced via both media. It will be let to the CFMU operations to determine the events that come within the Headline News category.
148
The titles of the Network Headline News of major importance and/or requiring immediate action are highlighted in red. A summary of the News is revealed when clicking on the expand button, as shown below.
Clicking on the News title opens a Network Headline News Detail detached view with the fully detailed News item:
Lastly, the More button at the bottom right of the Portlet opens another detached view listing all Network Headline News, be they Online News or Archive News - by means of their respective tabs:
Here again the News title links to the corresponding Headline News Detail window.
149
6.29Network Operations Strategic Plan

Typical Scope:
This Portlet opens the Network Operations Strategic Plan website.
The navigation is possible from the header, with tabs which display: the topics of the NOP Document, the plan per ACC and the plan per Airport. The content can also be browsed via the left-hand menu tree. The NOP Strategic Plan can be printed per section or as a complete document.
6.30NOP Processes
Typical Scope:
150
NOP Processes: Information on the latest status of the reviews of the current NOP Strategic Plan and on the production of the NOP Strategic Plan for the next season
6.31NOP Updates
Typical Scope:
NOP Updates: Information on the dates and scope of the NOP Strategic Plan last updates
6.32Planning of ATM Network Changes

Typical Scope:
The Planning of ATM Network Changes Portlet presents the major ATM upgrades end events expected over the next four years, to facilitate the planning and coordination of these events at network level. Updates and additions should be provided to the CFMU NOP Office (nop.office@eurocontrol.int) via the nominated NOP focal points per ANSP.
151
6.33Portal Assistance
Typical Scope: In case of problem or questions, contact the NOP Office team via the Nop Portal Assistance Portlet.
This portlet provides links to two Portal Assistance Request forms.
Protected Portal
This form is intended for the operational user. Note the Attachment field, allowing you to attach an annex (typically, a screenshot of the encountered issue) to your form.
We will provide you with a 1st level support or, if necessary, redirect you to the correct section within CFMU for additional support. This support will be offered from 0700-1700 (CET), and will not be available on weekends. If you are experiencing technical problems with authentication process when accessing the Portal, contact should be made with CFMU System Operations (CSO) Helpdesk, as per the following contact information: http://www.cfmu.eurocontrol.int/cfmu/public/standard_page/contact_operational_technical.html.
Public Portal
This form is intended for the generall public user. Note the User Feedback link to the NOP Public Portal Survey, where you can leave us your feedback about your Portal experience.
152
6.34Portal Release Information

Typical Scope:
The Portal Release Information Portlet lists the last changes implemented in the Portal, as well as some insight on future releases and evolution. Click on the arrow to open the Summary of a given item:
153
Click on the Title on an item to open a full description in a Detached View, or on the more link to open another detached view with all issued items, under the Online or Archived tab depending on their date of issue:
6.35Pre-validation exercises
Typical Scope:
Pre-validation exercises: Information on the dates and scope of the on-going or planned pre-validation exercises. The Pre-validation exercises Portlet is currently not activated on the Portal
6.36RAD
Typical Scope:
154
6.37SAFA
Typical Scope: Access to the SAFA Portlet is restricted by security profile. This section may therefore not concern you.
The objective of the SAFA Portlet is to check whether the Flight Plans accepted by IFPS concern aircraft / aircraft operators and/or countries on which ECAC Member States would have decided banning or safety inspections. The main process is to check continuously the flight plan data coming from IFPS according to some selection criteria. An Alert mail message is sent in case of a match. Dedicated Help and User manual are separately available to the appropriate profiles - by means of the Button. Help
6.38Training
Typical Scope:
The Training Portlet provides links to the CFMU Training website, containing all the training dates and registration information.
6.39All Other Portlets

The other portlets are simple to use: they are made of a summary text - sometimes illustrated - and most of the times propose organized shortcuts and links to the CFMU website or the EUROCONTROL website.
AIS Agora: link to the Agora
155
CFMU Developments: links to several pages of the CFMU website describing the CFMU systems and evolutions including reference documents in the CFMU Library
CFMU Handbook: Link to the official documents describing the procedures for interacting with CFMU Operations
CFMU Interactive Reporting: Link to the CIR application
CFMU Operations overview: Link to CFMU web pages providing a high level view of the CFMUs main operational processes
156
Charts: Link to the EUROCONTROL website providing ATM maps
Claims: Link to the CFMU Claim Management System (CCMS)
CODA: Link to the EUROCONTROL CODA website
Contacts: Link to pages of the CFMU and EUROCONTROL web sites providing various useful contact points
NEVAC: Link to the EUROCONTROL NEVAC web site
157
OneSky Online: Link to EUROCONTROLs extranet, OneSky Online
RVSM: Link to the EUROCONTROL RVSM web site
SAAM: Link to the EUROCONTROL SAAM web site
Skyview: Link to the EUROCONTROL Skyview web site
Statfor: Link to the EUROCONTROL Statfor web site
158
NOP Portal - User Guide 7 Case Studies
159
Disclaimer
Please note that the portal is under development as we are building this training material. As a result, some presented features may look inconsistent. However, the functionnalities should remain the same and therefore the instructions delivered by this programme, accurate enough. Should you however point out bugs, errors or omissions, please be kind enough as to report them to cfmu.webmaster@eurocontrol.int
User Instructions
Simply pick up a topic from the menu and follow the instructions on screen.
User Interface
These Case Studies packages consist in an automatic animated presentation of some specific NOP functions. Larger presentations may include several chapters, indicated by 'glassy' buttons like the one shown below.
Simply pick up any one of the proposed topics from the starting screen to play the selected animation. Upon completion you will be automatically led back to the starting screen.
Explanatory balloons will guide you through these short movies:
Lastly, be aware that you can monitor and control the movies progress with the player bar attached at the bottom of each animation:
Do not forget to clear your browser's cache on a regular basis (method varying from one make and version to another - refer to you computer's literature) to be sure to always get the most recent content.
7.1 Messages
Flash Movie Placeholder
Your movie will appear in this box in Preview or when the help system is built Movie URL (internet URL or relative path to a file in the project): films/messages.swf Movie Width: 902 Movie Height: 702 Background Color (HTML color code): #ffffff
NOP Portal - User Guide 7.2 AOWIR

Flash Movie Placeholder
Your movie will appear in this box in Preview or when the help system is built Movie URL (internet URL or relative path to a file in the project): films/aowir.swf Movie Width: 902 Movie Height: 702 Background Color (HTML color code): #ffffff
160
NOP Portal - User Guide 8 Download the Manual
161
Download here (images\NOP Portal - User Guide.pdf) the pdf version of the NOP Portal User Guide Version 2.0
The online HTML version of the NOP Portal Help will be maintained and kept up to date on a regular basis. The pdf manual, on the contrary, will only be generated on more important revisions. As a result, the pdf version (and the material printed from it) can be potentially outdated by the time you wish to use it. Whenever in doubt, please always refer to the online version for the most recent information.
NOP Portal - User Guide 9 A

AIM ATFCM Information Message AIS Aeronautical Information Services ARO Air Traffic Services Reporting Office ATFCM Air Traffic Flow and Capacity Management - A service that is enhancing ATFM with the objective of managing the balance of demand and capacity by optimising the use of available resources and coordinating adequate responses, in order to enhance the quality of service and the performance of the ATM system. ATM Air traffic management - The dynamic, integrated management of air traffic and airspace including air traffic services, airspace management and air traffic flow management safely, economically and efficiently through the provision of facilities and seamless services in collaboration with all parties and involving airborne and ground-based functions. Axis (Seasonal) Flows of traffic across the European Network.
162
Glossary
C
CCMS-Web Web based CFMU Claim Management System - The CCMS Web is an independent application where the CFMU is enabling authenticated clients to access and submit incident reports, user requirements or requests for support in their field of activity. CDM Collaborative Decision Making CFMU Central Flow Management Unit CFMU Public Website Available to the general public, without any registration. It contains information relevant to the CFMU core business, but information of an operational nature, which are accessible from the NOP Portal. CHMI CFMU Human Machine Interface - CHMI provides a new graphical interface to the CFMU operational systems which enables users to display data and graphical information (such as routes, route attributes, airspaces, flight plan tracks, etc.) via map displays. As these maps are updated dynamically, therefore CHMI provides a more user-friendly display of 'real time' information. CIA CFMU Internet Applications CIR CFMU Interactive Reporting CRAM Conditional Route Availability Message
D
Daedalus CFMU tool to dynamically calculate a route which is valid according to all airspace and flow management constraints known to the CFMU i.e. Conditional Route Availability Message (CRAM), RAD & ATFCM Notification Message (ANM). DMEAN

Dynamic Management of European Airspace Network Docked Status of a Map window or component, when it is attached to the Menu Bar on top of the Map detached view. DWH Data Ware House - The DWH system contains archived data from other CFMU systems, together with derived performance and quality indicators. It is used to provide an assessment of ATFCM performance and enable corrective action by facilitating comparison of the actual traffic situation with the ATFCM plan, and to assist the CFMU and its users in the preparation of their Strategic, Pre-Tactical and Tactical activities, by providing a forecast flight demand model based on historical data.
163
E
EFD ETFMS Flight Data - significant flight data updates sent by ETFMS to ANSP's in the form of EFD messages. ETFMS ETFMS provides the overall traffic situation for the CFMU area, both current and future, based upon flight plan data updated with current traffic position data, allowing a precise anticipation of the traffic demand. ETFMS brings benefits in the management of both routine traffic situations as well as unusual or 'exceptional' conditions.
F
FAAS Flight Assessment and Alert System (3 letter acronym: FAS) - The CFMU system hosting the SAFA application. FCR File Content Repository - The root folder where all the Portal content are stored FCU File Configurable Unit - The smallest content package that can be updated independently. In most cases, it will be a single FCU item - but some items do share common or crossed links and will therefore be grouped within an FCU folder. Floating Status of a Map window or coponent, when it is freely movable and draggable in the main display area. FMP Flow Management Position FUM Flight Update Messages - aimed at making CFMU partners aware of the situation of a given flight, in particular regarding the Estimated Landing Time.
I
IFPS Integrated Initial Flight Plan Processing System. IFPS fulfils two primary functions: 1. provides a centralised flight planning system for the States within the CFMU area with the object of rationalising reception, initial processing and distribution of flight plan data to ATC Units.
2. provides Repetitive Flight Plan (RPL) and Filed Flight Plan (FPL) data for use by the OPSD for ATFCM planning, monitoring and slot allocation.
N
Nav Aid Any visual or electronic device, airborne or on the surface, that provides point-to-point guidance information or position data to aircraft in flight.
NOP Portal - User Guide P

Portlet Portal Element - Configurable window providing a synthetic piece of static or dynamic content on a portal page. Post-Operations One of the 4 ATFCM Phases as used in the Portal. Covers the period from "Day +1" 00:00 onwards Pre-Tactical One of the 4 ATFCM Phases as used in the Portal. Covers the period from "Day -6" to "Day -1" inclusive. Protected Portal The NOP Protected Portal contains information for clients involved in ATM operations and is only available after acceptance of the CFMU Terms and Conditions. It is accessed via RSA SecureID (see Token). Public Portal Available only after self-registration. The NOP Public Portal contains information to assist the CFMU clients involved in ATM operations - however, some elements which are subject to a service agreement are only accessible from the NOP Protected Portal.
164
R
RAD The RAD is a sole-source flight-planning document, which integrates both structural and ATFCM requirements, geographically and vertically. The RAD is updated each AIRAC cycle following a structured standard process of 1. Requirement 2. Validation 3. Publication by the Central Flow Management Unit (CFMU) in cooperation/coordination with the States and the Aircraft Operators.
S
Scenario ATFCM measure applied as a result of an ATFCM Event, either planned or unplanned. Self-Registered The Self-Registration allows a non-authenticated user to create an account (with userID and static password) to access certain services and data from CFMU. SESAR Single European Sky ATM Research Strategic One of the 4 ATFCM Phases as used in the Portal. Covers the period from "Day -12 months" to "Day -7 days" inclusive.
T
TACTICAL One of the 4 ATFCM Phases as used in the Portal. Covers the Day currently selected in the header, from 00:00 to 24:00 UTC. Target Date The date which has been set in the Portal Header, and therefore for which the queries do apply. The Target Date can also be modified from within the Header of some Detached Views (typically, for all views where you can submit a query). TIL Stands for 'Until' - the end date and time of a period. Token A software-based one-time password authentication method of protecting network resources, typically used for remote access. It is a small independent program that runs on the PC and that generates every

minute a random number called the token code. The SecurID software licenses are bought from RSA Security Corp, therefore the installation
165
U
UserID Your UserName or UserID is a login name which has been assigned to your User account by the CFMU. (For example: p0xxx1). The UserName is not case sensitive.
W
Way Point A pre-determined geographical position, used for route or approach definition or progress reporting purpose. Two Way Points define a route segment. WEF With Effect From - the start date and time of a period. WIND Web Interface for NOP Data - This content and workflow management software is used to maintain the content of the Portal (for the static content) and manage the presentation of the content from back-end systems. WYSIWYG What You See Is What You Get - A descriptive designation for a form of visual display or graphical user interface (gui) that shows (on the screen) the actual appearance of a document being processed.
NOP Portal - User Guide Index

ACC Info, 30-31 Access Request, 30 Act. Time AS Profile, 122-123 Act. Time PT Profile, 119-120 Aerodrome, 43-45, 103-107 Aerodrome Set, 45, 107-108 AIM, 31-32 Air Route, 45-47 Aircraft Operator, 108-110 Airport Info, 33-36 Airspace, 110-111 Airspace Data, 36-37 Aerodrome, 43-45 Aerodrome Set, 45 Air Route, 45-47 Querying Airspace Data from within the Detached View, 39-41 Route Catalogue, 47-48 Traffic Volume, 41-42 Traffic Volume Set, 42-43 Airspace Data - Aerodrome, 38-39 Airspace Data - Route, 39 Airspace Data - Traffic Volume Query, 37-38 Airspace Structure, 48 All Other Portlets, 154-158 Alternate Routes, 125 ANM, 48-49 AOWIR, 159-160 ARCID List, 101-103 ATFCM Events, 49-50 ATFCM Network Daily Plan, 75-77 ATFCM Network Situation, 56-57 ATFCM Network Situation Interactive Map, 60-61 ATFCM Scenarios, 53 ATFCM Situation Data, 72-73 ATFM Information Messages AIM, 31-32 ANM, 48-49 Contingency, 90 CRAM, 90-91 Calendar, 82-84 Calendar in details, 84-88 Case Studies, 159
166

CFMU ATFCM Reports, 88-89 CFMU News, 89-90 Changes and Updates, 2-3 Compare with Predecessors, 96-97 Consulting a Scenario Details, 55-56 Consulting ATFCM Events per Category, 50-51 Consulting Scenarios associated to an Event, 52-53 Consulting the Description of an Event, 51-52 Contextual Help, 25-26 Contingency, 90 CRAM, 90-91 Daily Plan The Interactive Daily Plan, 78-82 The Static Daily Plan, 77-78 Detached Views, 26-27 Details, 114-117 Digging into the Delay Causes, 74-75 Disclaimer, 1 Displaying Regulations from the Map, 71-72 Download the Manual, 161 Downstream, 45-47 E -conference, 97-98 EAD, 91-92 EAUP, 92 EAUP Details - ATS Route and CDR Type 1 Closure, 92-93 EAUP Details - CDR Type 2 Availability, 93-94 EAUP Details - Level 1 RSA Allocations, 94-95 EAUP Details - Level 2 RSA Allocations, 95-96 Elaps. Time AS Profile, 120-122 Elaps.Time PT Profile, 118-119 Enabling Javascript, 6-8 Error Messages, 27-28 Events and Meetings, 98 F A Q, 98-99 Flight History, 123-124 Flights, 99 Act. Time AS Profile, 122-123 Act. Time PT Profile, 119-120 Aerodrome, 103-107 Aerodrome Set, 107-108 Aircraft Operator, 108-110 Airspace, 110-111 Alternate Routes, 125 ARCID List, 101-103
167

Details, 114-117 Elaps. Time AS Profile, 120-122 Elaps.Time PT Profile, 118 -119 Flight History, 123-124 Messages, 125-126 Operational Log, 124-125 Plotting flights on the Map, 126-127 Point, 111-112 Point Profile, 117-118 Querying Flights from the Detached View, 99-101 Regulation, 112-113 Traffic Volume, 113-114 Free Text Editor - FPL Validation, 127-129 Free Text Editor - Propose Routes, 129-132 Global Case Studies, 159 Changes and Updates, 2-3 Disclaimer, 1 Enabling Javascript, 6-8 Error Messages, 27-28 Global Layout, 13-14 Login to the Protected Portal, 8-11 Login to the Public Portal, 11-13 Printing from the Portal, 14-15 Printing mode, 28-29 Purpose, 4 Self - Registration, 11 Technical Prerequisites, 4-6 Token, 11 Global Help, 17-18 Global Layout, 13-14 Header Global Help, 17-18 Header Buttons, 17 Logout, 21-22 Search Results, 19-21 Search Text, 19 Searching the Portal, 18 -19 Setting Preferences, 18 Timeline Navigation Concept, 16-17 Header Buttons, 17 IFPUV, 127 Free Text Editor - FPL Validation, 127-129 Free Text Editor - Propose Routes, 129-132
168

Structured Editor - FPL Validation, 132-135 Structured Editor - Propose Route, 135-138 Login to the Protected Portal, 8-11 Login to the Public Portal, 11-13 Logout, 21-22 Main Reports, 138 Map ATFCM Network Situation Interactive Map, 60-61 Displaying Regulations from the Map, 71-72 Plotting CRAM on the Map, 72 Plotting Flights on the Map, 70-71 Setting the Flight Levels on the Map, 66 The Map Menu Bar, 61-62 Tools - Area, 63-64 Tools - Level Ruler, 65-66 Tools - Levels, 64-65 Tools - Location, 62-63 Tools - Queries, 68-70 Tools - Time, 66-68 Measures, 138-139 Querying Measures from within the Detached View, 140-141 Regulation Delays, 144-146 Regulation Details, 142-144 Regulation List, 141-142 Rerouting List, 146-147 Messages, 125-126, 159 Network Axis Management, 147 Network Headline News, 147-149 Network Operations Strategic Plan, 149 NOP Processes, 149-150 NOP Updates, 150 Operational Log, 124-125 Planning of ATM Network Changes, 150-151 Plotting CRAM on the Map, 72 Plotting Flights on the Map, 70-71, 126-127 Point, 111-112 Point Profile, 117-118 Portal Assistance, 151-152 Portal Release Information, 152-153 Portlet ACC Info, 30-31 Access Request, 30 Airport Info, 33-36 Airspace Data, 36-37
169

Airspace Data - Aerodrome, 38-39 Airspace Data - Route, 39 Airspace Data - Traffic Volume Query, 37-38 Airspace Structure, 48 All Other Portlets, 154-158 ATFCM Events, 49-50 ATFCM Network Daily Plan, 75-77 ATFCM Network Situation, 56-57 ATFCM Scenarios, 53 ATFCM Situation Data, 72-73 Calendar, 82-84 Calendar in details, 84-88 CFMU ATFCM Reports, 88-89 CFMU News, 89-90 Compare with Predecessors, 96-97 Consulting a Scenario Details, 55-56 Consulting ATFCM Events per Category, 50-51 Consulting Scenarios associated to an Event, 52-53 Consulting the Description of an Event, 51-52 Contextual Help, 25-26 Detached Views, 26-27 Digging into the Delay Causes, 74-75 E -conference, 97-98 EAD, 91-92 EAUP, 92 EAUP Details - ATS Route and CDR Type 1 Closure, 92-93 EAUP Details - CDR Type 2 Availability, 93-94 EAUP Details - Level 1 RSA Allocations, 94-95 EAUP Details - Level 2 RSA Allocations, 95-96 Events and Meetings, 98 F A Q, 98 -99 Flights, 99 IFPUV, 127 Main Reports, 138 Measures, 138-139 Network Axis Management, 147 Network Operations Strategic Plan, 149 NOP Processes, 149-150 NOP Updates, 150 Planning of ATM Network Changes, 150-151 Portal Assistance, 151-152 Portal Release Information, 152-153 Portlet Availability, 24-25 Portlet Definition, 23
170

Portlets Scope, 23-24 Pre-validation exercises, 153 Querying AIM from within the Detached View, 32-33 RAD, 153-154 Regulation, 139-140 Rerouting, 140 SAFA, 154 The (static) ATFCM Network Situation Detached View, 59-60 The ATFCM Scenarios Detached View, 53-55 The ATFCM Situation Data Detached View, 73-74 Training, 154 Viewing the ATFCM Network Situation in the Post-Operations phase, 58-59 Viewing the ATFCM Network Situation in the Tactical phase, 57-58 Portlet Availability, 24-25 Portlet Definition, 23 Portlets Scope, 23-24 Pre-validation exercises, 153 Printing from the Portal, 14-15 Printing mode, 28-29 Purpose, 4 Querying AIM from within the Detached View, 32-33 Querying Airspace Data from within the Detached View, 39-41 Querying Flights from the Detached View, 99-101 Querying Measures from within the Detached View, 140-141 RAD, 153-154 Regulation, 112-113, 139-140 Regulation Delays, 144-146 Regulation Details, 142-144 Regulation List, 141-142 Rerouting, 140 Rerouting List, 146-147 Route Catalogue, 47-48 SAFA, 154 Search Results, 19-21 Search Text, 19 Searching the Portal, 18-19 Self - Registration, 11 Setting Preferences, 18 Setting the Flight Levels on the Map, 66 Structured Editor - FPL Validation, 132-135 Structured Editor - Propose Route, 135-138 Technical Prerequisites, 4-6 The (static) ATFCM Network Situation Detached View, 59-60 The ATFCM Scenarios Detached View, 53-55
171

The ATFCM Situation Data Detached View, 73-74 The Interactive Daily Plan, 78-82 The Map Menu Bar, 61-62 The Static Daily Plan, 77-78 Timeline Navigation Concept, 16-17 Token, 11 Tools - Area, 63-64 Tools - Level Ruler, 65-66 Tools - Levels, 64-65 Tools - Location, 62-63 Tools - Queries, 68-70 Tools - Time, 66-68 Traffic Volume, 41-42, 113-114 Traffic Volume Set, 42-43 Training, 154 Tutorials AOWIR, 159-160 Messages, 159 Viewing the ATFCM Network Situation in the Post-Operations phase, 58-59 Viewing the ATFCM Network Situation in the Tactical phase, 57-58
172

Nop Portal Users Guide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Nop Portal Users Guide

Hochgeladen von

Copyright:

Verfügbare Formate

EUROCONTROL CFMU

SUPPLEMENT TO THE CFMU HANDBOOK

NOP PORTAL USERS GUIDE

Amendment date: 23 August -2010

NOP PORTAL USERS GUIDE i

NOP Portal - User Guide Table of Contents

NOP Portal - User Guide

NOP Portal - User Guide

NOP Portal - User Guide

NOP Portal - User Guide

NOP Portal - User Guide 1 Disclaimer

Access Restrictions / Single Sign On to CFMU Applications

NOP Portal - User Guide 2 Changes and Updates

go (Section 6.34) go (Section 6.27) go (Section 6.6) go (Section 6.19.5)

NOP Portal - User Guide

NOP Portal - User Guide 3 The Portal

3.2 Technical Prerequisites

NOP Portal - User Guide

NOP Portal - User Guide

NOP Portal - User Guide

3.2.1.1 Internet Explorer:

3.2.1.2 Mozilla (Firefox):

NOP Portal - User Guide

3.3 Login to the Protected Portal

1. Access to the Portal

2. The login screen

NOP Portal - User Guide

NOP Portal - User Guide

4. Filling in the login form

5. Role and Domain Selection

NOP Portal - User Guide 3.3.1Token

3.5 Login to the Public Portal

1. Access to the Portal

2. The login screen

NOP Portal - User Guide

NOP Portal - User Guide

4. Filling in the login form

3.6 Global Layout

NOP Portal - User Guide

3.7 Printing from the Portal

NOP Portal - User Guide

the Page Setup linked with your browser

NOP Portal - User Guide 4 Header

4.1 Timeline Navigation Concept

icon opens the Date Picker.

NOP Portal - User Guide

4.2 Header Buttons

NOP Portal - User Guide

Clicking on the PREFERENCES button will open the Preferences Settings

NOP Portal - User Guide 4.3 Searching the Portal

Searching for Text

Refining the Search

NOP Portal - User Guide

See below an example with the query 'EBBR EDDY':

NOP Portal - User Guide

Drilling down information

NOP Portal - User Guide

NOP Portal - User Guide 5 Portlets and Detached Views

5.1 Portlets General Features 5.1.1Portlet Definition

Portlet Availability Matrix

PostPreTactical Strategic Operations Tactical

NOP Portal - User Guide