rad user manual · 2020. 8. 11. · applications as delivered in the nes - and as a result,...

RAD User Manual

4.2 - 4126 June 2020

1 Changes and Updates

RAD HELP

NES Version: 4.2 for NM24.0

Document Version: 41Last Update: 26/06/2020

Version History - RAD

Date Version Detail Link

26/06/20 4.2-41 NM24.0 release -

06/03/20 4.0-38 Update for NCO-8405 -

28/02/20 4.0-37 - -

10/12/19 4.0-34 Sprint 105 -

04/12/19 4.0-33 Migration from HelpStudio2018 to HelpStudio2019 -

21/11/19 4.0-32 Sprint 104 -

02/10/19 3.7-29 Update for NCO-13353 -

11/09/19 3.7-27 Sprint 99 -

29/08/19 3.7-26 NM23.5 release -

27/06/19 3.0-22 Map added -

3.0-16 NM23.0 release -

3.0-11 Aladdin migration initiated -

18/05/18 2.7-6 Section updated -

23/02/18 2.7-1 Aladdin project initiated -

NM EUROCONTROLDocument Title:

RAD User Manual

Last saved: 26 June 2020 Version 4.2-41 Page 1

2 Welcome

Purpose of the Package

This Help Package aims at delivering online and contextual help service, along with operational and referencedocumentation (in both HTML and PDF format) on the NES applications.

Document structure

Change and UpdatesTechnical PrerequisitesLogin and AccessGlobal information - Common featuresPer application, Application features and usageHelp


RAD User Manual


3 Technical Prerequisites

Operating System

The NES applications can be used on any Operating System, as they run via a web browser. As part ofNM24.0, the recommended system is however Windows 10.

Browser

The following browsers are supported in version 4.2:

Firefox - Recommended Chrome - RecommendedEdge

Internet Explorer is no longer supported as from NM24.0

Screen resolution

The Application will be best used on displays with a minimum screen resolution of 1280x1024 pixels - higherresolutions allowing more space.

Note: The application being web-based, it provides all the services and features brought forth by theBrowser, such as screen refresh, printing, managing views in windows and/or tabs, etc.


RAD User Manual


4 Login and Access

The NES contains information for clients involved in ATM operations and is only available after acceptance of the NMTerms and Conditions. It is accessed via RSA SecureID - users need to log in via their Token.

If you do not yet have a user profile, please contact your Unit Administrator and check how to get one.

You start by entering your credentials on the Network Manager Applications login page:

After successful validation of your credentials on the Network Manager Applications login page, you will be prompted forfurther identification on the Portal homepage, via the Access Management component:

Click on the Continue button to proceed:


RAD User Manual


Note: In cases where multiple values could be associated with a single token (i.e. several persons sharing thesame token, or an individual granted several profiles), select the appropriate one using the E-mail Combo box:

Upon successful login, you get access to the NES landing page:

From here, you can select the desired application among the ones which your credential give access to...


RAD User Manual


Logout

Use the Logout command from the User menu to end your session and exit the Portal:


RAD User Manual


5 Applications - Common Features

This section presents the transversal functions and various features shared by some or all of the businessapplications as delivered in the NES - and as a result, available to RAD users.

Note: The NES applications being web-based, they do share all the services and features brought forthby the Browser, such as screen refresh, printing, managing views in windows and/or tabs, etc.

The following features are covered in this version:

Panels and Accordions - go (Section 5.1)Browser Windows and Tabs - go (Section 5.2)Sorting Tables and Lists - go (Section 5.3)Using Dates - go (Section 5.4)Paging - go (Section 5.5)

Please use the links provided above to go to the desired section.

5.1 Panels and Accordions

Foreword: The following features and functions are shared across the various NES applications. Some featuresare however not available to some applications, and some applications may not be visible to you, as access isprofile-based.

Landing Page

The NES Landing page is common to all applications. It is where you are lead to once you are successfully logged in.

From this point, use the provided navigation to the desired application or function.

Accordions

An accordion is a content management tool, useful for compressing many elements in a compact space.

In NES, the content is presented through two or three vertical accordions, that you can at will expand or collapse toshow or hide their content. You can achieve any combination that best suits your usage, as accordions can beindividually expanded or collapsed, added or deleted - such as in this CAL example:


RAD User Manual


The first segment is typically to host the query and filter parameters, the second segment is where the results arelisted, and the third segment is used to display the details of selected item(s).

But in some cases, as expressed above, the application allows you to create additional accordions:

Managing Accordions

Note: Depending on the application concerned (AIRSPACE, CAL, DNP, ...) some of the icons or functionsdescribed below may not be available...

Accordions can be dynamically arranged, by means of the following actions:

Collapse to close the selected panel and hide its content (all apps);

Expand to open the selected panel and show its content (all apps);

Click in the left control bar to collapse/expand a given accordion (RAD); Remove to delete the selected panel (AIRSPACE, CAL);

Move down to position the selected panel under the other one(s) and so obtain an horizontal stacking(AIRSPACE, CAL); Move up to (re)position the selected panel next to the other(s), and so achieve/restore a vertical


RAD User Manual


stacking (AIRSPACE, CAL);

or Resize: drag the separator to the desired position to expand or shrink vertical or horizontal (CAL,RAD);

Footer

Present at all times and all screens, the Footer provides, in addition to the usual copyright information, links to theOnline Help and to the Legal Notice, and displays the application version number.

5.2 Browser Windows and Tabs

The NES applications being web-based, you can benefit from browser built-in features to manage Windows andViews:

open Links (i.e. Details views) from the same Application in multiple tabs within same ornew windows,simultaneously open and use different Applications in multiple windows,etc.

Use your mouse pointer to right-click on a given link to open this dialog and select the desired action:

Note: The above dialog will look differently depending on the OS and browser used.

NES applications may also - irrespective of the browser window and/or tab context - make use of Accordion.

Note: Please refer to the Panels and Navigation section for more information on Accordions(Section 5.1).

5.3 Sorting Tables and Lists

Some columns featured in the results tables can be sorted and filtered to best suit your needs

Sorting Tables

You can sort a column by clicking directly in the title of the column - or move the mouse pointer anywhere over the columnheader to locate the Sort icon, click on it and modify the sorting order:

Example in Cal

Example in RAD


RAD User Manual


Descending

Ascending

Click on the lower triangle (arrow pointing down) or on the upper one (arrow pointing up) to toggle between descending andascending order

Note: The icon changes to reflect Ascending ( ) or Descending ( ) selected order.

Filtering

Click on the Filter icon to set the filtering options available for the concerned item:

Textual (CAL):

type in the text by which you want to restrict the results table;click on the Search button to execute;use the Reset button to return to the unfiltered state and clear the search field.

Textual (RAD):

type in (the first letters of) the text by which you want to restrict the results table;pick the correct match from the autosuggest list.

Contextual (RAD):


RAD User Manual


Depending on the nature of the concerned item, collections of check boxes allow you to select theappropriate filter criteria.

Note: CAL does not feature contextual filtering for the moment.

5.4 Using Dates

Dates and period do play a key role in the NES.

Use Date Picker to open the calendar (interface and label may differ depending on the context of theimplementation) ...

... then determine the date mode, which can be:

by Date,by Airac.

Note: Depending on the application and context, the Date mode - or conversely, the Airac mode - maynot be available (since irrelevant).

Date mode

In the Date mode, the date picker is presented in the form of a typical calendar sheet:

and : respectively backward and forward incremental navigation from Year to Year,

and : respectively backward and forward incremental navigation from Month to Month,

: Current Month and Year,

: shortcut to current Day,

: current Day,


RAD User Manual


: AIRAC Date and Number,

: Click on the Date or Airac tab to toggle between Date and Airac mode

Use the appropriate navigation until you can click on the target date to set the intended date.

UFN

In certain context (i.e. when defining a validity period), an additional UFN button will appear next to the Endfor a quick selection of this abstract time:

Note: Use UFN (acronym for Until Further Notice) in the End date field to leave the end date to be laterspecified (if ever).

Tip: You can also use keyboard shortcuts:

Previous year: Control + left Next year: Control + rightPrevious month: PageUpNext month: PageDown

Note: Another method to quickly select a month and/or a year will be by means of the current Monthand Year links:


RAD User Manual


Click on the Month link to get to select from the provided table:

Click on the Year link to get to select from the provided table:

Airac mode

In the Airac mode, the Airac numbers for the selected year are presented in a convenient table:


RAD User Manual


1. Past AIRACs are showed in gray, and disabled;2. Current AIRAC is showed in light blue, and disabled;3. Future AIRACs are the only ones you can select.

If need, be, use the left and right arrows to shuffle the years back or forth, then click on the desiredtarget Airac number to set the intended period.

5.5 Paging

The Paging (or Pagination) is aimed at facilitating the viewing of large amounts of items. It allows you control to howthe results are grouped to be displayed, and to navigate from page to page.

The bottom of lengthy tables listing resulting from queries in certain applications presented in the NES may thereforefeature this navigation mechanism:

Navigation

- go to the Previous page

- go to a given page

- Current page

- jump forward by batches of 5 pages

- go to the Last page

- go to the Next page

- select the Number of items per page:


RAD User Manual



RAD User Manual


6 RAD

The RAD Application provides a single, fully integrated and co-ordinated routeing scheme. It enablesStates/FABs/ANSPs to maximise capacity and reduce complexity by defining restrictions that preventdisruption to the organised system of major traffic flows through congested areas with due regard to AircraftOperator requirements.

6.1 The RAD Concepts

RAD GENERAL DESCRIPTION

Introduction

The Route Availability Document (RAD) is created based on COMMISSION REGULATION (EU) No 255/2010 of25 March 2010 laying down common rules on air traffic flow management where in accordance with Article 4 -General obligations of Member States, paragraph 4 where a common reference document containing thepolicies, procedures and description for route and traffic orientation shall be created. It also includes routenetwork and free route airspace utilisation rules and availability.

The RAD is also created based on COMMISSION REGULATION (EU) No 677/2011 of 7 July 2011 laying downdetailed rules for the implementation of air traffic management (ATM) network functions and amendingRegulation (EU) No 691/2010, Annex I - The European Route Network Design (ERND) Function, Part B -Planning principle 5(d) stating that the European Route Network Improvement Plan (ERNIP) shall include routenetwork and free route airspace utilisation rules and availability.

The RAD is designed as a part of the Network Manager Air Traffic Flow and Capacity Management (ATFCM)operation.

The RAD is also an ATFCM tool that is designed as a sole-source flight-planning document, which integratesboth structural and ATFCM requirements, geographically and vertically. The RAD is updated each AIRAC cyclefollowing a structured standard process of Requirement, Validation and Publication by the NM incooperation/coordination with the States and the AOs. The RAD is only applicable to the IFR part of the flightplan.

This section contains the main definition of terms used in the RAD to describe and express the utilization of theEuropean airspace.

The provisions from this section are supplementary to those described in the ERNIP, Part 1, Chapter 8 and Part4 and are relevant for the entire RAD process. These provisions are for further clarification of the RAD contentto the Operational Stakeholders.

The Document is a property of the RAD Management Group (RMG) and was produced by the NM RAD Teambased on initial proposal presented at RMG/21 (8th - 9th November 2012) by Lufthansa Systems.

Basic Principles

The objective of the RAD is to facilitate flight planning, in order to improve ATFCM, while allowing aircraftoperators’ flight planning flexibility. It provides a single, fully integrated and co-ordinated routeing scheme. Except where otherwise specified the RAD affects all areas where the Network Manager provides ATFCMservices.

The RAD enables States/FABs/ANSPs to maximise capacity and reduce complexity by defining restrictions thatprevent disruption to the organised system of major traffic flows through congested areas with due regard toAircraft Operator requirements.


RAD User Manual


The RAD is designed as a part of the Network Manager (NM) ATFCM operation. It is organising the traffic intospecific flows to make the best use of available capacity. Whilst, on its own, it will not guarantee theprotection of congested ATC sectors during peak periods, it should facilitate more precise application of tacticalATFCM measures.

The RAD should also assist the Network Manager in identifying and providing re-routeing options. Globalmanagement of the demand will, potentially, lead to an overall reduction of delays. It is important to notethat to achieve this, some re-distribution of the traffic may be required through the implementation ofScenarios. This may result in modified traffic/regulations in some areas where, under normal circumstances,they would not be seen.

The content of the RAD shall be agreed between the Network Manager and the Operational Stakeholdersthrough an appropriate Cooperative Decision Making (CDM) process.

The RAD is subject to continuous review by the Network Manager and the Operational Stakeholders to ensurethat the requirements are still valid and take account of any ATC structural or organisational changes that mayoccur.

The RAD is updated each AIRAC cycle following a structured standard process of:

1. Requirement;2. Validation;3. Publication by the Network Manager in cooperation/coordination with all Operational Stakeholders.

The RAD is only applicable to the IFR part of the Flight Plan.

Each State shall ensure that the RAD is compatible with their AIP with regard to the airspace organisationinside the relevant FIR/UIR.

The NM is responsible for preparing of a common RAD reference document, collating, coordinating, validatingand publishing it, following the CDM process as described in this section.

Structure

Document Structure

The RAD consists of:

General description;6 (six) Appendices:

1. Appendix 2 - Area Definition2. Appendix 3 - Flight Level Capping limits3. Appendix 4 - En-route DCT limits4. Appendix 5 - Airport connectivity5. Appendix 6 - Flight Profile Restrictions6. Appendix 7 - FUA Restrictions

A Network wide Pan-European Annex;A separate Annex for special events, if necessary, containing restrictions of temporary nature (i.e.European/World Sport Events, Olympic Games, large scale Military exercises, economic forums …).

General description

It defines the basic principles, general structure of the RAD, the structure of RAD restrictions, period ofvalidity, application, amendment process, temporary changes, some flight planning issues, routeing scenarios,publication, tactical operations and RAD review process.

Appendix 2

It defines a number of airfields included in the RAD described by the following terms:

“Group” - defines a number of 3 (three) or more airfields that may be subject to the same restrictions. Forexample a major destination may have a number of minor satellite airfields in the vicinity; this constitutes a“Group”;“Area” - defines as a number of airfields within the same region and may comprise several “Groups”, orindividual airfields.Appendix 3

It defines FL capping limitations imposed by each State/FAB/ANSP and is applied from airport of departure(ADEP) to airport of destination (ADES).

Appendix 4

It defines the en-route DCT (Direct) flight plan filing limitations imposed by each State/FAB or ATC Unit in


RAD User Manual


accordance with provisions of ICAO Doc 4444 - ATM (PANS-ATM).

Appendix 5

It defines the DCT (Direct) flight plan filing connections defined by each State/FAB/ANSP to/from the airportswithout SIDs/STARs or with SIDs/STARs which are not able to be complied due to certain aircraft limitations. This is done only to support/facilitate the processing of flight plans. Based on relevant State AIPs AOs shall beinformed about the airspace organisation at/around the airports.

Appendix 6

It defines the vertical profile elements of the LoAs between adjacent ATC Units. This purely operational data isnot published through AIS.

Appendix 7

It defines the airspace restrictions (FUA restrictions) caused by restricted airspace (RSA) activation within eachState/FAB/ANSP.

Network wide Pan-European Annex

The Annex contains a list of restrictions valid for each States/FABs/ANSPs on specific:

Significant point/s; orATS route segment/s; orAirspace volume/s (ATC Unit, AoR of relevant ATC Unit - CTA/UTA, TMA, CTR or individual control sector/swithin an ATC unit).The Annex also contains the relevant restrictions included in Letters of Agreement (LoA) between adjacent ATCUnits requested to be “H” Hard checked. These restrictions are named “Cross-border”.

Restriction structure

The RAD is designed as a part of the Network Manager Air Traffic Flow and Capacity Management (ATFCM)operation.

Each restriction is hierarchical and specific and has been arranged to facilitate parsing of the information intocomputer systems.

For the usage of the restricted object (significant point, ATS route segment, defined DCT, airspace volume(ATC Unit, AoR of relevant ATC Unit - CTA/UTA, TMA, CTR or individual control sector/s within an ATC unit),etc.) there are three main types of restrictions:

1. Not available for …Flight planning via restricted object is forbidden for described flow(s).

2. Only available for …Flight planning via restricted object is allowed exclusively for described flow(s).

3. Compulsory for …Flight planning via restricted object is the only valid option for described flow(s).

A combination of restriction types “Only Available” and “Compulsory” is possible. The conditions ofapplicability refer to both sub-types in the same way. For the combination of elements that define the flow oftraffic, there are 2 (two) types of restrictions - inclusive and exclusive:

INCLUSIVE restriction - traffic must meet ALL of the conditions to be subject to the restriction. Theimplicit logical operator between the listed conditions is an “AND” - Logical Conjunction.EXCLUSIVE restriction - traffic only needs to meet ONE of the numbered sub-conditions to besubject to the restriction. The implicit logical operator between the numbered conditions is an “OR” -Logical Disjunction.A restriction shall not qualify for inclusion in the RAD unless it has at least one condition expressiondescribing the particular characteristics of the affected traffic flows. A flow element is defined asaffecting either:

Departures from an Airfield/Group/Area;

Arrivals to an Airfield/Group/Area;Traffic flying between Airfields/Groups/Area;Overflying traffic (traffic via another object - significant point, route, airspace).

Attributes

To classify the strength of the requirements in regards to the RAD, the following conventions are used:

The word "shall" denotes a mandatory requirement and is used only in RAD restriction definition;The word "should" denotes a preferred requirement and is used only in Operational Goal definition.


RAD User Manual


The words "may" - an optional requirement and "will" - a statement of intent to implement a requirement arenot used in RAD.

General Restriction Design

Restricted Object

The Restricted Object specifies the geographic location where the restriction is applied.The Restricted Object is a mandatory section of each restriction and uses flow elements.

Condition / Utilization

The Condition / Utilization is a mandatory section of each restriction and uses flow elements, level expressions,time conditions and special terms to specify parameters which flights have to match in order to be subject tothe restriction.

Restriction Applicability

For each RAD restriction, the period of applicability has to be defined.

Operational Goal

For further information about the restriction, the Operational Goal can be specified.Stating the Operational Goal of a restriction is not mandatory. However, such information is considered asvaluable additional information (background, origin, etc.).When provided the Operational Goal shall not include any part of the restriction’s condition.

CDM PROCESS

Amendments to the General Description of the RAD, or the period of validity, shall be co-ordinated betweenthe Network Manager and the Operational Stakeholders via the RAD Management Group (RMG) and approvedby NETOPS team. Inclusion or withdrawal of additional Annexes or Appendixes shall follow the same process.

The Operational Stakeholders shall provide their request for changes to the NM RAD Team, taking into accountagreed publication and implementation dates, in accordance with AIRAC procedures and HandbookSupplement for the Provision of Environment data.

All new RAD restrictions, amendments and changes will be checked by the NM RAD Team versus airspaceorganisation in the area. Any possible discrepancies will be notified to the States/FABs/ANSPs concerned assoon as possible.

Suspension of NAVAIDS, and/or replacement by temporary mobile units will be promulgated via the Pan-European Annex. States should ensure that the NM RAD Team is notified of these changes.

The final content of any amendment to the RAD shall be positively agreed between the NM RAD Team andState/FAB/ANSP concerned. This agreement shall be reached in a form of e-mail confirmation, meetingreport/minutes or any other means reflecting final mutual agreement for change. These agreements will beproperly recorded by the Network Manager.

Amendments will be published by the NM RAD Team as follows:

34 days in advance of the relevant AIRAC cycle;Until the establishment of an automated RAD process amendments will be highlighted in RED/BLUEBOLD and will be annotated by abbreviation NEW/AMD;Restrictions that have been removed will be annotated abbreviation DEL;“Last minute” changes:

are changes required due to exceptional circumstances and/or only when they have asignificant impact on operational requirements;shall be:

announced by the NRCs as ordinary amended or new RAD requirements;exceptionally annotated as such;

sent via e-mail to the NM RAD Team in accordance with ERNIP Part 4;will be promulgated on the NM NOP portal via the “Increment File”.will be announced by the NM RAD Team via e-mail to the Operational Stakeholderssimilarly as RAD distribution.

PUBLICATION

The RAD is created in accordance with ICAO publication procedures and is published on the NM NOP website,34 days in advance prior to the relevant AIRAC cycle.


RAD User Manual


Each State may promulgate the RAD by any one of the following methods:

Publish the RAD in its entirety as an AIP Supplement (the onus is on the State to ensure that theRAD is kept up to date);Publish relevant Appendices and State/FAB/ANSP part of the Pan-European Annex of the RAD as anAIP Supplement;Publish reference to the NM NOP website in the AIP.

DAY PROCESS ACTION

D-63 Notification to States/FABs/ANSPs "One week to Cut-off". NM

D-56 Finalisation of States/FABs/ANSPs requirements. States/FABs/ANSPs

Cut-off date. States/FABs/ANSPs provide amendments to the NM.

Three weeks to compile the RAD and to resolve errors/conflicts. NM

D-34 Publication. NM

Two weeks to assess impact of new restrictions.

D-14 Results of impact assessment of new restrictions. NM

Changes/amendments to be promulgated via the “Increment File” onthe NM NOP Portal.

D-10 Freeze of ENVironment tape for AIRAC. NM

Where applicable, publication of route availability in national aeronautical information publications shall be fullyconsistent with this common reference document.

TACTICAL OPERATIONS

The Network Manager in conjunction with the FMPs will monitor the actual situation during the day ofoperation to ensure the RAD is achieving the balance of traffic required.

During periods of unanticipated high demand the Network Manager may co-ordinate an extension to the periodof validity of routeing scenarios with the relevant FMPs. This will be published by AIM, giving at least threehours notice.

During periods of significant improvement to the ATFCM situation, the Network Manager will co-ordinate withthe relevant FMP, a reduction in the period of validity of scenarios. This will be published by AIM.

If, due to a major unexpected event, there is a significant disturbance to traffic patterns, after co-ordinationwith the relevant parties (FMPs and AO’s), the Network Manager may suspend part of the RAD and providealternative routeings.

With effect from AIRAC -6 day (D -6), implemented RAD Data is considered as Operational. Management ofsuch changes to the RAD is the responsibility of the NRC of the originating State

If, after AIRAC -6 day (D -6), a State discovers an error or omission to the RAD that is SAFETY RELATED, thenit is the responsibility of the NRC to contact the NM RAD Team to request a live update of the NM CACD inorder to correct the problem. The safety related RAD error or omission shall be exceptionally annotated assuch and shall be sent via e-mail to the NM RAD Team in accordance with ERNIP Part 4. The NM RAD Team willonly act after consultation with the NRC or his designated Deputy. Following the consultation process the NMRAD Team shall create the necessary DMR and the change shall be promulgated via the “Increment File”. During the weekend, the ACC shall contact the Current Operations Manager and the matter shall be handled


RAD User Manual


MANually. A second alternative is to request that the restriction in question be DISABLED in ENVironment sothat there will not be a check at IFPS.

RAD REVIEW

The NM RAD Team is responsible for coordination of the entire RAD review process.

The RAD review is required to ensure that all data contained within the RAD is current and correct. The reviewis also the opportunity to ensure that any modifications, within the incremental update to the NetworkManager Operational systems, are reflected in the construction of RAD restrictions.

A RAD review for each and every Annex/Appendix, including cross-border restrictions, shall be completedannually during designated meetings and as a rolling process by the NM RAD Team. The existing South West,South East, North West, North East or Ski - Airspace or ATFCM meetings could be used for RAD reviewpurposes. Additional ad-hoc RAD review meetings could be organised in case of any urgent issues to bediscussed.

The outcome of each RAD review shall be properly documented through the report or minutes. Thereports/minutes will be stored by the NM RAD Team.

Each State/FAB/ANSP shall convene an internal RAD review with the airlines concerned. Such an internalreview shall be announced to the NM RAD Team and shall cover as minimum the validity of all restrictions; thetimeliness of restrictions; the completeness of all restrictions. The NM RAD Team may offer items to becovered. The results of such an internal review shall be passed to the NM RAD Team as soon as possible.

For each cross-border RAD review the NM RAD Team shall perform a RAD impact assessment on each relevantrestriction. This analysis shall be carried out together with the Operational Stakeholders.

The NM RAD Team shall maintain a List of proposed/requested by the AOs RAD restrictions for considerationby the States/FABs/ANSPs. The List shall contain the restrictions traceability and shall record the proposal’sstatus as change/removal/update till RAD restriction resolution or deletion.

6.2 DMR Workflow

The RAD Data Modification Request (DMR) is a container for all changes that relate to the same businesspurpose and the same responsible user, normally NRC or LRC.

States

Initial: Details only visible to owner/creator.Draft: Similar to initial but visible to all RAD users.Ready: Ready to be validated by NM RAD team.Published: Visible to all - no more editable.

Workflow

The NRC or LRC creates a DMR to handle a set of RAD object changes (restrictions and/oraerodrome sets) related to a single and well-defined reason, which was decided to call its “generalpurpose”. The reason can be the one of a big project for example “AIRAC 1912” but it can be assimple as “RAD Updates” as well.The global RAD lifecycle is to be seen as a rolling “release” plan: the DMRs from various Europeansources evolve through the phases of the DMR workflow, and deliver their contents first in a releasefor RAD publication, and second must be implemented in CACD where the RAD object changes gointo force i.e. impact the NM system behavior (IFPS and ETFMS, via CACD).The RAD object changes conveyed by a DMR can affect a restriction in the current AIRAC or anytime in the future.Amendments MUST be included in a DMR.

State Visible to Editable by Possible next steps

Initial Creator LRC, NRCfrom the samecountryNM-RAD(*)

Creator LRC, NRCfrom the samecountryNM-RAD(*)

Creator LRC, NRCorNM-RAD

Initial Draft

Draft All LRC, NRC Creator LRC, NRC Creator NRC


RAD User Manual


NM-RAD from the samecountryNM-RAD(*)

NM-RAD

Draft Ready

Ready All LRC, NRCNM-RAD

NM-RAD NM-RAD

Draft Ready Published

Published All users No user No possible nextstep

(*) NM RAD Team is an exception during the transition period.

Deleted vs. Stopped DMR

A DMR can only be deleted when in status Initial.

As soon as its lifecycle has been initiated, and so when in status Draft or Ready, a DMR can only be stopped(... and eventually resumed).

6.3 RAD Grammar

In the scope of this chapter, the term RAD restriction or RS refers to those parts of an RS that are needed forthe translation of the RS into an internal model, which the RAD application uses to provide additional features,especially the advanced and deep search and the MAP presentation.

This chapter does not discuss the Appendix 2 - Area Definitions (Aerodrome Sets).

1. The initial vision for the RAD application included a grammar that would understand the RS to theextend that the RAD application could correctly explain an RS’s meaning.

2. To reach this goal, we would have needed to change some illogical parts of the grammar

3. Furthermore, the initial vision for the RAD application called for a replacement of the Excel files bypublishing the RAD via a publicly reachable part of the B2C.

4. Both changes would require the acceptance of the wider user group and would have needed time fordiscussion and operational implementation.

5. The re-prioritisation of our work in autumn 2018 removed these features from the immediate plan forimplementation.

6. Subsequently, the current implementation continues to support some of the illogicalities (Section6.3.17) and the division of fields along the existing Excel columns.

7. When speaking of the grammar, the following text refers to the RestrictionGrammar.g4 file containingthe syntactical (structural) rules in an abstract manner.

8. When speaking of the Java code, the following text refers to less abstract code written predominantly inthe programming language Java.

9. This separation allows NM to update those parts of the implementation via configuration that representdata rather than structure, for example equipment codes or aircraft families.

10. The Java class ADDTest.java contains most of the below used examples in an executable form.

11. This chapter marks keywords in bold.

Content

Normalised Restriction vs RAD Appendices (Section 6.3.1)Traffic Availability (Section 6.3.2)Principle Utilisation Structure (Section 6.3.3)The Conditioned Flow Tree (Section 6.3.4)The Conditioned Flow (Section 6.3.5)The Flow List (Section 6.3.6)The Single Flow (Section 6.3.7)


RAD User Manual


http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/rad/browse/nconect.rad.grammar/src/test/java/eurocontrol/nconect/rad/grammar/ADDTest.java#13

List of Entities (Section 6.3.8)Special Case "except" Operator (Section 6.3.9)Special Cases "&", "and-then" and "and-directly" Operators (Section 6.3.10)RAD Entities (Section 6.3.11)Type Definitions (Section 6.3.12)Flight Level Ranges (Section 6.3.13)Time Applicability (Section 6.3.14)Logical Date and Time Formats (Section 6.3.15)Physical Date and Time Formats (Section 6.3.16)The "Compulsory" Problem (Section 6.3.17)

6.3.1 Normalised Restriction vs RAD Appendices

1. All normalised RS follow the same structure:

rs restricted-object traffic-availability (Section 6.3.2) conditioned-flow-tree

(Section 6.3.4) time-applicability (Section 6.3.14)

2. However:

a. the Excel file and, subsequently, the Excel file based user interface for Appendix 3 — City PairFlight Level Capping do not allow for the restricted object.

On the other hand, the grammar supports already today the possibility to change the user’sapproach to Appendix 3 by allowing the presence of a restricted object, for example the list ofairspaces impacted by the flight level capping.

b. in Appendix 4 — Enroute DCTs / General Limits, the RS in the Appendix 4-1 form exceptionsof the general information given in Appendix 4-2.

The complete and normalised RS would have to be formed from the applicable general conditionand the related exceptions.

The grammar does not support appendix 4-2 because its content does not adhere to a grammaryet but consists rather of free text.

Therefore, the grammar does not undertake the effort of presenting a normalised version forAppendix 4 restrictions.

c. in Appendix 5 — Airport Connectivity, the RS in the Appendices 5 — DEP and 5 — ARR formexceptions of the general information given in Appendix 5 — General ARR DEP Conditions.

The complete and normalised RS would have to be formed from the applicable general conditionand the related exceptions.

The grammar does not support appendix 5 — General ARR DEP Conditions because the contentdoes not adhere to a grammar yet but consists of free text.

Therefore, the grammar does not undertake the effort of presenting a normalised variant forAppendix 5 restrictions.

Also, users enter exception restrictions that do not actually define an exception in order collectall related items to ensure completeness of their work.

d. Appendix 7 — FUA Restrictions contains exceptions to the EAUP/EUUP document, which is notpart of the RAD application.

Therefore, it is currently and in the foreseeable future impossible to generate complete andnormalised restrictions.

3. The restricted-object is the focus of the restriction supporting the user in collecting relevantinformation about one object within the Excel file.

4. This arrangement of the restriction elements allows for a clear and pleasing reading flow:

rs as:AS1 not-available-for-traffic dep ad:LION & arr ad:CALF & above FL215 H24

Read as: Airspace AS1 is not available for traffic for flights departing aerodrome LION and arrivingaerodrome CALF and fly above FL215 during H24.

5. Of the above mentioned structure, only the time applicability is mandatory for all restrictions.

In Appendix 7 — Free Use of Airspace (FUA), users do not normally enter a time applicability.


RAD User Manual


However, users have done so as an exception and the NM-RAD team has confirmed the usefulness ofthis information.

Therefore, users need to always enter a time applicability, which, in the absence of an actual timeapplicability, consists of the keyword refer-to-EAUP or its short form EAUP.

6.3.2 Traffic Availability

1. The RAD application provides these keywords for the traffic availability:

a. only-available-and-compulsory-for-traffic

b. not-available-for-traffic

c. only-available-for-traffic

d. compulsory-for-traffic

2. Staying close to the Excel file, the UI allows users to enter this value as text or via a drop-down list boxsimilar to the usage in the related appendix.

3. See also here (Section 6.3.17) some thoughts on the application of the compulsory keywords.

6.3.3 Principle Utilisation Structure

1. The grammar converts the restriction text into lower case prior to parsing it.

2. The text-case normalisation leads to the situation that the second level numbering allows only for theeight values a, b, c, d, e, f, g and h because the grammar reads the subsequent letter i as Romannumeral 1 and as part of the third level numbering.

3. The grammar supports three counting levels:

a. Latin numerals 1..99;

b. Latin letters a..h;

c. Roman numerals i..lxxxix;

Authors can apply the Roman digits I, L, V and X only because especially C (100) and D (500)fall into the range of a..h for the Latin letters.

LXXXIX (89) is the largest valid Roman number based only on I, L, V and X. 90 would be XC.

4. The grammar expects at least one single space character as delimiter between grammar elements.

It sanitises surplus white space characters and creates proposals that optimise the text.

5. This imaginary test example for the conditioned-flow-tree shows the maximum number of levelssupported by the RAD application:

LEXUS not-available-for-traffic

1. dep SAAB and-then via L112

when-available crossing YUGOFIR

when-not-available crossing POLOFIR except

a. via FELIS, HIPPO except

i. crossing LAMBFIR

when-available via BUICK, ASTRA, AURIS, EDSEL

this-traffic-shall-file

(

1. via KOALA & via BISON except

a. via LEMUR when-available via LLAMA

i. via ZEBRA when-available via SLOTH


RAD User Manual


when-not-available via WHALE

ii. via TIGER

b. via HORSE

c. via CAMEL

2. via GOOSE

3. via PUPPY except

a. via MOUSE

b. via SHEEP

)

other-traffic-shall-file

(

1. via LOTUS when-not-available via MAZDA

a. via PINTO when-available via SKODA

except

i. via VOLVO when-available via SMART

when-not-available via ISUZU

ii. via MOOSE

iii. via RHINO

iv. via SNAIL

b. via KOALA

2. via OTTER

3. via ADDER

)

ii. arr AUDI


via pt:HONDA

b. arr LADA

other-traffic-shall-file

via pt:DACIA

2. arr MOLE

3. dep-arr MULE

H24

6.3.4 The Conditioned Flow Tree

1. The conditioned-flow-tree consists of at least one conditioned flow followed by optional lower levels ofthe flow tree structure:

counter? conditioned-flow (Section 6.3.5) lower-level-flow-tree?

2. In order to structure the flows on multiple levels, authors need to apply the counter and use a lower-level-flow-tree.

For simpler and unstructured RS, authors do not need to enter the counter.

Authors must either apply a count on all appropriate places or not at all.

The grammar does not accept a conditioned-flow-tree that starts without number but starts havingnumbers in between.


RAD User Manual


3. The lower-level-flow-tree is a flow-tree itself.

Authors can apply up to two levels of lower-level-flow-tree below the top level flow-tree.

4. Authors can apply the and or except (Section 6.3.9) keyword in order to "multiply out" commonparts of the flow expressions.

5. By default, the application assumes that a higher level flow tree connects to the lower level flow treevia the AND command.

Authors do not need to write this command and the proposal feature will not insert the command text.

For example: 1. dep EG <AND> a. arr LF b. via EH

meaning: matches flights departing in EG AND (arriving in LF OR flying via EH).

6. Authors can apply the except (Section 6.3.9) keyword in order to limit a previous flow.

For example: 1. via as:ABC123 except a. via pt:TIGER b. arr EGLL

meaning: matches flights via ABC123 unless they (fly via TIGER or arrive EGLL).

7. If the expression is so simple that authors do not need to structure it then they can ignore thecounters:

For example: LEXUS only-available-for-traffic dep SAAB

6.3.5 The Conditioned Flow

1. A conditioned-flow has this structure:

flow-list (Section 6.3.6)

when-available flow-list (Section 6.3.6)

when-not-available flow-list (Section 6.3.6)

when-scenario-active <Scenario IDs>

when-scenario-not-active <Scenario IDs>

this-traffic-shall-file-clause ( conditioned-flow-tree (Section 6.3.4) )

other-traffic-shall-file-clause ( conditioned-flow-tree (Section 6.3.4) )

2. Both availability clauses are optional.

If authors applies both, then they have to arrange them in the above mentioned order.

3. Both scenario clauses are optional.


The author must add at least one scenario ID or multiple scenario IDs in a comma separated list.

4. Both shall-file clauses are optional.


5. The grammar needs the brackets '(' and ')' in the shall-file clause to prevent collissions of counterswithin the this/other-traffic-shall-file clause and its surrounding conditioned-flow-tree.

6. Being in a "shall-file" clause, authors must not apply another this/other-traffic-shall-file clause within athis/other-traffic-shall-file clause.

The grammar will fail on an expression like this:

LEXUS not-available-for-traffic dep SAAB


(

via BUICK

this-traffic-shall-file <= illegal

(

via ASTRA

)


RAD User Manual


http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#OperatorSpecialCaseExcept


)

7. However, this expression is correct:

LEXUS not-available-for-traffic

1. dep SAAB


(

via BUICK

)

2. arr SAAB


(

via ASTRA

)

6.3.6 The Flow List

1. A flow-list combines single flows (Section 6.3.7) via these operators, in descending order ofprecedence:

In order to be affected by this flow-list, a flight must fulfil:

and-then all single flows in that order:via pt:ZEBRA and-then via pt:HORSEflow: all flights passing first via ZEBRA and afterwards via HORSE.see Special Cases "&", "and-then" and "and-directly" (Section 6.3.10)

& all single flows combined via & (and):via pt:ZEBRA & via pt:HORSEflow: all flights passing via ZEBRA and via HORSE either asZEBRA ⇒ HORSE or HORSE ⇒ ZEBRA.ZEBRA ⇒ HORSE ⇒ ZEBRA etc. also match the flow list.see Special Cases "&", "and-then" and "and-directly" (Section 6.3.10)

, at least one of the given single flows combined via , (or):via pt:ZEBRA , via pt:HORSEflow: set of all flights flying via ZEBRA combined with all flights flying viaHORSE.

( ) Users can apply round brackets to influence the operator precedence, pleasesee the example below.

2. The grammar uses & (ampersand) and , (comma) as operators because the the grammar couldmisunderstand the related texts and and or as ICAO entities.

Having a minus/hyphen character between its words, neither human nor machine can misunderstandthe and-… operator as an ICAO entity because ICAO entities do not have hyphens.

3. The user can override the standard precedence by applying brackets ( ):

crossing as:TOADFIR, via as:HAREFIR & not-via pt:DACIA

Based on the standard precedence, the grammar understands the expression above as (a)

crossing as:TOADFIR, ( via as:HAREFIR & not-via pt:DACIA )

// flow: combined set of all flights crossing TOADFIR

// with the set of all flights via HAREFIR but not

// the set of flights via HAREFIR and via DACIA

and not (b)


RAD User Manual


( crossing as:TOADFIR, via as:HAREFIR ) & not-via pt:DACIA

// flow: all flights crossing TOADFIR or via HAREFIR,

// then deduct flights passing via DACIA from both FIRs;

// The "not-via pt:DACIA" applies also to TOADFIR

4. The user can but does not need to apply the brackets as demonstrated in (a) because the defaultoperator precedence leads to the same result with or without brackets.

However, the user must apply the brackets as demonstrated in (b) to express such a flow.

6.3.7 The Single Flow

1. In the RAD expression, the single flow is an expression that results in a, possibly empty, set of flights.

2. A single flow consists of a single flow keyword and a list of entities (Section 6.3.8).

3. These entities could refer to CACD entities or RAD entities, especially RAD Aerodrome Sets.

4. The grammar provides these entity types: aerodromes, aerodrome sets, airspaces, airway portion,FABs, points, routes, SIDs and STARs.

Out of these types, the table below lists the types permitted for each keyword.

Note The current implementation does not yet validate the relation between entity type and entity.

5. Instead of the keyword/entity expression, a flow could be one or multiple type definitions (Section6.3.12) or flight level ranges (Section 6.3.13).

6. Authors can prefix each but the bidi command with not- in order to negate the command’s meaning.

On 12 December2019, the grammar does not support the bidi single flow keyword any more.

However bidi is still available in the airway portion (Section 6.3.11) definition.

7. The keywords are:

Keyword Matching flights Types

arr, not-arr landing at a given aerodrome or any aerodrome on theprojection of a given airspace on the ground

aerodromes,aerodrome sets,airspaces, FABs

bidi <A> to-from <B>

being first in <A> and then in <B> or being first in <B>and then in <A>


crossing, not-crossing

entering AND existing airspace without departure or arrivalon projection of the airspace on the ground including flightscrossing horizontal "walls" (ceiling and floor) up- ordownwards

airspaces, FABs

dep, not-dep starting from a given aerodrome or any aerodrome on theprojection of a given airspace on the ground


dep-arr, not-dep-arr

landing at or starting from a given aerodrome or anyaerodrome on the projection of a given airspace on theground


overfly, not-overfly

flying over the given item, especially flying over anairspace without touching it

airspaces, FABs

via, not-via passing and touching the given entity in any way airspaces, airwayportion, FABs,points, routes,SIDs, STARs


RAD User Manual


8. Authors have applied single flow keywords such as arr-outside or dep-outside . In extension, thegrammar should then also support not-arr-outside and not-dep-outside .

Applying these keywords on an airspace AS1, one can recognise these relations:

a. arr-outside AS1 expresses the same as not-arr AS1 ;

b. not-arr-outside AS1 expresses the same as arr AS1 ;

c. dep-outside AS1 expresses the same as not-dep AS1 ;

d. not-dep-outside AS1 expresses the same as dep AS1 ;

Therefore, the grammar does not support the *outside keywords.

9. Authors have applied single flow keywords such as entering and exiting .

Applying these keywords on an airspace AS1, one can recognise these relations:

a. entering AS1 expresses the same as via AS1 & arr AS1 ;It does not imply arr AS1 because layered airspaces would allow a flight to arrive at anaerodrome on the ground projection of AS1 without touching AS1.If one does not want to express the arrival, then one should use only via .

b. exiting AS1 expresses the same as dep AS1 & via AS1 ;It does not imply dep AS1 because layered airspaces would allow a flight to depart from anaerodrome on the ground projection of AS1 without touching AS1.If one does not want to express the departure, then one should use only via .

Since the keywords entering and exiting do not add to the expressive strength of the language, thegrammar does not support them.

Keyword Matching flights Types

6.3.8 List of Entities

1. The RAD application supports these entity types: aerodromes, aerodrome sets, airspaces, airwayportion, FABs, points, routes, SIDs, STARs.

2. Users can add one or many entities to the single flows (Section 6.3.7).

3. Users can combine multiple entities via these operators, in descending order of precedence:

Operator Matching flights that

except touch any of a given set of entities on the left of the except keyword except forthe list of entities on the right side of the keywordarr ad:LI* except (ad:LION)flow: all flights arriving on any aerodrome in Italy except for LION.see Special Case "except" Operator (Section 6.3.9)

and-directly touch the entities in that order and without touching other entities:via pt:ZEBRA and-directly pt:HORSEflow: all flights passing first via ZEBRA and afterwards HORSE and that do nottouch any other point in between.see Special Cases "&", "and-then" and "and-directly" Operator (Section6.3.10)On 12 December 2019, the grammar does not support and-directly.

and-then touch the entities in that order:via pt:ZEBRA and-then pt:HORSEflow: all flights passing first via ZEBRA and afterwards HORSE.see Special Cases "&", "and-then" and "and-directly" Operator (Section6.3.10)

& touch all entities:via pt:ZEBRA & pt:HORSEflow: all flights passing via ZEBRA and HORSE.see Special Cases "&", "and-then" and "and-directly" Operator (Section6.3.10)


RAD User Manual


, touch any of the listed entities:via pt:ZEBRA , pt:HORSEflow: all flights passing via ZEBRA combined with all flights passing HORSE.

( ) fulfil expressions with complex entity lists as parameters:via (pt:ZEBRA, as:EB) and-then (pt:HORSE, as:ED)orarr (az:SOUTH_BRUSSELS_GROUP, az:NORTH_BRUSSELS_GROUP) except (EBBR)

Operator Matching flights that

6.3.9 Special Case Except Operator

1. In the current Excel files, authors apply the keyword except in many different variants with manymeanings.

2. Mostly, authors want to exclude:

a. entities from larger sets of entities, for example excluding single aerodromes from RADaerodrome sets; or

b. flights from the set of flights that touches some entity but that do touch other entities, forexample exclude flights passing a particular point from all flights within an airspace.

3. Independently, authors occasionally apply the except operator to "multiply out" common parts ofcomplex restrictions:

as:EG1234 not-available-for-traffic

1. dep ad:EG & not-arr ad:LF

2. dep ad:EG & not-via as:EH

H24

would become:

as:EG1234 not-available-for-traffic

1. dep ad:EG except

a. arr ad:LF

b. via as:EH

H24

The RAD application continues to permit the usage of the except keyword in this case.

However, the RAD application proposes the usage of the new keyword unless in order to reduce thedouble usage of the except keyword.

4. In order to separate these concerns in a very obvious way, the grammar continues to use the exceptkeyword for case (a) and introduces the negated form for case (b).

5. This is the principle structure of an entity list:

larger set except ( smaller set of same kind )

Simple examples:

a. ad:EB* except (EBBR)

b. as:EB* except (EBR20)

c. BRUSSELS_GROUP except (EBBR)

d. MON..FRI except (HOL)

e. acft-family (B737) except acft-type (B737)

6. The aircraft family example is an exception in as far as that it contains the left side values alreadywithin brackets and that it explicitly mentions the type of the excluded values.


RAD User Manual


http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#TheSingleFlow

The left side brackets exist because authors usually create lists of values anyway, see below.

The mentioning of the excluded type serves the readability:acft-family (B737) except (B737)

could be considered an empty result, which is not the author’s intention.

The exclusion of aircraft types from aircraft families is the only application of the except keyword inthe type definitions.

7. When combining entity lists to a single flow, the except keyword has the highest precedence.

This means that this single flow:arr C*, K*, M* except (CYOW, KIAD, MMMX)

excludes the arrival in Ottawa (CYOW) and Washington (KIAD) from the arrivals in Mexico (M*)because the precedence binds the excluded list to the M* and not to the whole list of country codes.

8. Correct versions would be:

a. arr ( C*, K*, M* ) except (CYOW, KIAD, MMMX)

b. arr C* except (CYOW), K* except (KIAD), M* except (MMMX)

9. The current grammar implementation analyses, partitions and re-combines all permitted types of dateand time expressions but it does not calculate actual periods.

Hence, authors can write semantically erroneous date/time expressions such as:via EB* FIRST AIRAC JUN except(JAN)

and the current grammar implementation will not mark it as an error.

Apart from that limitation, authors are almost completely free to exclude sub periods from largerperiods.

10. Authors often used this way of expressing an RS:as:EBUUUIR not-available-for-traffic except via pt:NIK H24

The grammar does not allow this double negation and forces the user to apply this identical but simplerand clearer variant:as:EBUUUIR only-available-for-traffic via pt:NIK H24

11. However, when authors create complex expressions (PAN ID YX2063) the conversion into a positiveform could change the meaning of the expressions:

EDYYUTA Not available for traffic

DEP (ad:EDDF/FE/FZ, ETOU)

except-via

1. RKN, RORUS, AMSAN

2. BITBU Y181 MAKIK UY181 DEMUL

3. OBOKA UZ28 DIBIR

4. BITBU Y180 NISIV UY180 DIK - TOLVU

5. NATSU Y150 TOLGI

6. OBOKA UZ29 TINIK UZ29 / UZ291 TORNU

H24

12. Before discussing the except keyword any further, we need to correct the syntax:

a. The numbering cannot start in the middle of the expression, either the numbering starts in thebeginning of the expression or no numbering at all.

b. Each entity list needs a preceding flow keyword.

c. The minus/hyphen character in line 4 is invalid.

d. The forward slash in line 6 is an incorrect usage of the short-cut operator.

not-available-for-traffic

1. dep ad:EDDF/FE/FZ, ETOU & via EDYYUTA except

a. via RKN, RORUS, AMSAN


RAD User Manual


b. via BITBU Y181 MAKIK UY181 DEMUL

c. via OBOKA UZ28 DIBIR

d. via BITBU Y180 NISIV UY180 DIK and-then TOLVU

e. via NATSU Y150 TOLGI

f. via OBOKA UZ29 TINIK (UZ29, UZ291) TORNU

H24

Now, the expression above conveys the same information as the original text but passes the grammar.

13. Converting the except into a form without the except keyword leads to this expression:

only-available-for-traffic

dep ad:EDDF/FE/FZ, ETOU & via EDYYUTA &

(

via RKN, RORUS, AMSAN,

via BITBU Y181 MAKIK UY181 DEMUL,

via OBOKA UZ28 DIBIR,

via BITBU Y180 NISIV UY180 DIK and-then TOLVU,

via NATSU Y150 TOLGI,

via OBOKA UZ29 TINIK (UZ29, UZ291) TORNU

)

H24

This variant passes the grammar and still conveys the same message but it might be less readablebecause the author cannot apply any numbering.

14. However, the RAD community in co-operation with the CACD world needs to decide for whom theywrite the RAD restrictions.

The above listed expressions focus on the management of entities.

But, finally, the entities and their restrictions have to serve the creation of flight plans.

15. The following expression also passes the grammar and conveys the the same message but from thepoint of view of an aircraft operator (AO) planning a flight:

not-available-for-traffic

dep ad:EDDF/FE/FZ, ETOU & via EDYYUTA


(

1. via RKN, RORUS, AMSAN

2. via BITBU Y181 MAKIK UY181 DEMUL

3. via OBOKA UZ28 DIBIR

4. via BITBU Y180 NISIV UY180 DIK and-then TOLVU

5. via NATSU Y150 TOLGI

6. via OBOKA UZ29 TINIK (UZ29, UZ291) TORNU

)

H24

16. Some might say that the latter expression states that the flowdep ad:EDDF/FE/FZ, ETOU & via EDYYUTAis unavailable while it is actually available if the AO files the flight along any of the permitted entities.

Although this statement is correct in itself, it would not show that the earlier expressions are better perse because the application of the except keyword implies that the permitted entities are part of theflow defined on the left side of the except keyword.

However, the points' locations might be outside of the EDYYUTA airspace as well.

17. The grammar will support all variants until further notice.


RAD User Manual


We might restrict the grammar as result of a common decision of the long-term future of the RAD withregard to automation towards CACD.

6.3.10 Other Special Cases

Special Cases "&", "and-then" and "and-directly" Operators

On 12 December 2019, the grammar does not support the keyword and-directly.However, it had been implemented, then removed, then discussed again and the final verdict about the futureof and-directly is not yet certain.Therefore, the chapter still serves the decision process on the future grammar.

1. The ampersand & operator stands for the keyword and because the term and could also mark anCACD point.

2. The keywords and-then and and-directly are free from such ambiguity because they have aminus/hyphen character in the middle.

3. The image above has three airspaces A, B, C and three flows 1, 2, 3.

4. Flow 1 represents the and operator.

Two single flows combined with the and keyword match all flights that pass through both single flows.

Here, it does not matter if the flight touches first airspace A and later airspace C or vice versa.

5. Flow 2 represents the and-then operator.

Two single flows combined with the and-then keyword match all flights that pass through both singleflows in the given order.

The flow line is similar to flow 1 with the exception of the arrow.

Hence, all flights match such a flow list if the touch first airspace C and then airspace A but not theother way around.

6. Flow 3 represents the and-directly operator.

Two single flows combined with the and-directly keyword match all flights that pass through bothsingle flows in the given order without touching any other CACD entity within the scope of the givenCACD entities.

The flow line is similar to a reverse flow 2 except for the fact that the flight must enter airspace Cdirectly from airspace A without touching airspace B.via C and-directly A

The above mentioned statement without touching any other CACD entity within the scope of the givenCACD entities refers to a problem of definition.

Although the flight passes from C to A without touching any other airspace, it might pass via a pointlocated at the border between the two airspaces C and A. Or it might cross a route.


RAD User Manual



Either way, by mentioning only airspaces in the RS, the author wants to express that the and-directlyoperator applies to airspaces only and subsequent readers, may they be humans or machines, shouldfocus on airspaces to understand the meaning of the RS.

7. This restriction is syntactically correct:only-available-for-traffic via as:B and-directly pt:TIGER 10:00..12:00

and in very special circumstances a flow from an airspace to a point might be reasonable.

Hence, the RAD application allows it but future business validation might remark on it.

8. The grammar allows the operators in:

a. Flow List: for example via pt:ZEBRA and-then via pt:HORSE ;

b. List of Entities: for example via pt:ZEBRA and-then pt:HORSE ; and

c. Airway Portion: via BXL E40 LGG should be read asvia BXL and-directly E40 and-directly LGG . The grammar treats the two expressionsidentically.

However, the current grammar allows forvia bidi:EBBR R12 EGLL

but not for

via bidi(EBBR and-directly R12 and-directly EGLL) .

9. The operators are available in flow- as well as entity lists because when users want to combine differententity types then they might have to use the flow-list operator instead of the entity list operator:

applying entity list operator: via pt:ZEBRA and-then ad:LADA

is invalid because a flight cannot go via an aerodrome, instead:

applying flow-list operator: via pt:ZEBRA and-then arr ad:LADA

is a valid restriction.

6.3.11 RAD Entities

1. The RAD grammar supports these entity types:

Type Prefix Syntax Example

Aerodrome ad: generic-valueshort-cut

ad:BULL/CK

entity ID withwild-card short-cut

ad:EB*FIR/ACC, ad:K*

Aerodrome Set az: Aerodrome SetName

az:LONDON_GROUP

Airspace as: generic-valueshort-cut

as:EBBUCTA/FIR

entity ID withwild-card short-cut

as:EB*FIR/ACC

Airway ICAO airwayshort-cut

T123, UT123, T/UT123

Airway portion point (routepoint)-at leastonce

bidi:pt:TIGER rt:R12pt:OKAPI

(TIGER, HORSE, CAMEL) R1(PUPPY, MOUSE, SHEEP)


RAD User Manual


http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#TheFlowList

http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#ListOfEntities

http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#RADEntities

TIGER (R1, R2, R3) SHEEP

(TIGER, HORSE, CAMEL)(R1, R2, R3) (PUPPY,MOUSE, SHEEP)

FAB fab: generic-value fab:EC

Point pt: generic-value "@"generic-value

pt:NIK@EB

pt:NIK@LY

Route rt: generic-value rt:R12

SID sid: generic-valueshort-cut

sid:CIV7D/2Q

STAR star: generic-valueshort-cut

star:TULNI3A/B

2. A generic value consists of one letter A..Z followed by zero or more letters A..Z or digits 0..9.

3. A short cut consists of a forward slash symbol / followed by at least one letter A..Z or digit 0..9.

4. An entity ID with wild-card consists of at least one letter A..Z followed by one asterisk symbol *followed by zero or more letters A..Z or digits 0..9.

5. An aerodrome set name starts with a letter A..Z or digit 0..9 followed by zero or more letters A..Z,digits 0..9 or underscore symbols _ and ends on either "_AREA", "_GROUP" or "_YZ_GROUP".

6. The grammar is so vague on the structure of these normally well defined items because the RADapplication should perform the actual entity validation against the CACD or other databases.

Furthermore, it is very well possible that NRCs create restrictions against not yet existing entities.

Beyond the availability of the entity, the RAD application might require business logic to validate forexample the ownership of entities.

Therefore, the grammar concerns itself with the principle structural correctness and leaves any furthervalidation to the Java code.

Type Prefix Syntax Example

6.3.12 Type Definitions

1. The grammar treats a type definition in a similar way to a single flow and authors can combine themwith other single flows:not-available-for-traffic via rt:R12 & eng-type(P) & not-flt-sts(HOSP) 06:00..09:00

Route R12 is not available for traffic using piston engines from 06:00 to 09:00 except for hospitalflights.

Type Definition Example

acft-eqpt, not-acft-eqpt acft-eqpt(C, D, L, M1, O, U, V, Y)

acft-family, not-acft-family acft-family(A300, B737) except acft-type(A3ST,B737)

acft-type, not-acft-type not-acft-type(SR71)

eng-type, not-eng-type not-eng-type(J)

flt-sts, not-flt-sts flt-sts(HEAD, STATE)

flt-type, not-flt-type not-flt-type(N, G)


RAD User Manual


http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#Validation


acft-desc-category, not-acft-desc-category acft-desc-category(H, G, T)

1. Authors can apply the except keyword only to the aircraft family:acft-family(B737) except acft-type(B737)

Please find here further explanations on the except keyword.

2. As for the RAD entities, the details of the permitted values are not part of the grammar but of the Javacode in order to achieve flexibility.

A Java based validation allows for run-time configuration and better error messages.

Type Definition Example

6.3.13 Flight Level Ranges

1. The grammar treats a flight level range in a similar way to a single flow and authors can combine themwith other single flows:only-available-for-traffic via rt:R12 & below FL305

Route R12 is only available for traffic below flight level 305.

2. Authors can apply open or closed flight level ranges.

3. The flight level clause has this structure:<keyword> <open or closed flight level> <location>

4. Open flight level ranges have one altitude value and allow the flow to be above or below this value.

5. The self-explanatory keywords for open flight level ranges are: above, not-above, with-rfl-above,with-rfl-not-above, below, not-below, with-rfl-below, with-rfl-not-below; rfl stands forrequested flight level.

6. Closed flight level ranges have two altitude values and allow the flow to be betwen or outside thesevalues.

7. The self-explanatory keywords for closed flight level ranges are: between, not-between, with-rfl-between, with-rfl-not-between; rfl stands for requested flight level.

8. The grammar permits these altitude values:

a. "FLxxx" standing for flight level xxx, xxx must consist of three digits and the RAD applicationwill check for the correct application of the numbering format for different altitudes.

b. Named constant values:

a. GND: Ground

b. UNL: Unlimited

c. MSA: Minimum Safe Altitude (not Minimum Sector Altitude)

d. MEA: Minimum En-route Altitude (ICAO)

c. "xxxxFT" standing for an altitude in feet, any number of feet is possible.

9. The location definition allows two variants:

a. in ( <an airspace> ) or

b. at ( <a point> ) .

The current implementation does not check the application of the correct English term in/at in relationto the following entity.However, in the interest of clarity, authors should take care of entering the keyword with theappropriate meaning.Also, we might add this validation at a later moment.

10. At the position of an airspace or a point, authors can apply a list of entities with all its possibleoperators and combinations, for examplebelow FL195 in (as:LARGEAS except (as:PARTOFLARGEAS))


RAD User Manual



http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#RADEntities


http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#ListOfEntities

6.3.14 Time Applicability

1. The document on Business Item Versions puts the time applicability into the context of other date/timerelated characteristics.

2. The RAD time applicability value allows for a sub set of the date/time related B2C Base Types.

3. The following constants are specific to RAD:

HO-Day prior to a holiday.

HO+Day after a holiday.

4. Furthermore, the grammar uses these standard abbreviations:

H24Continuous day and night service.

HOLHoliday.

5. The time applicability is a mandatory value.

In the absence of any stricter time applicability, authors have to define it at least as H24.

6. The logical date and time formats define a time applicability that is not bound to a specific calendarmoment, especially calendar year, and will repeat itself unless the validity period of the restriction stateinterferes.

7. The physical date and time formats define exact calendar periods.

Therefore, some physical date format features could overlap with the validity periods.

8. For example, one could express the applicability of a restriction for the AIRACs 1810..1901 via the

a. validity period of a restriction AIRAC 1810..AIRAC 1901 , or the

b. AIRAC based time applicability AIRAC 1810..AIRAC 1901 .

The operational outcome should be the same.

9. However, in the interest of simplification of the restriction conditions, the grammar does not allowauthors to enter a time applicability AIRAC 1810..AIRAC 1901 but expects the authors to use thevalidity period and to provide H24 as time applicability.

10. The time applicability starts with an optional keyword time-appl.

11. Its purpose is the definitive separation from previous text which might end with any of the date/timerelated constants.

12. Valid CACD point IDs include any of

a. MON, TUE, WED … ;

b. JAN, FEB, MAR … ;

c. BFR or HOL.

13. Hence, a list of CACD entities ending on any of the above mentioned values could confuse the grammarinto believing that a date/time value is a point or vice versa:via NIK R12 MON TUE

Is MON a point or a day?

14. Applying the time-appl keyword avoids ambiguity:via NIK R12 MON time-appl TUE

15. As long as the RAD application uses either Excel based data or has a UI with separated fields, users donot need to pay attention to this keyword.

Instead, the grammar pre-processing adds the keyword automatically.

16. The RAD application does not apply the time applicability to the MAP presentation of RAD restrictions in


RAD User Manual


http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/commonDefinitions/B2C_Item_Versions/B2C_Item_Versions.adoc

http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/commonDefinitions/B2C_BaseTypes/B2C_Base_Types.adoc#_dates

http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#LogicalDateAndTimeFormats

http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#PhysicalDateAndTimeFormats

the delivery of Spring 2019.

17. The reason is the complexity of some of the RAD restriction, which have multiple and different RADtime applicabilities for different parts of a year (summer/winter) or different sub-flows of onerestriction.

18. Subsequently, the MAP plots all parts of a RAD restriction as permanently existing items.

19. Should the users find this approach as being too simplistic then we will prepare a paper outlining thedifficulties in detail, give possible solutions and ask the RMG to drive the process.

6.3.15 Logical Date and Time Formats

1. In contrast to the physical time, the logical time does not contain a year information.

Hence, every logical time definition repeats itself when the next start moment occurs.


❶ marks references to the base types.

3. Please find here additional information on the SST (Summer Shift Time).

4. The time applicability is always a period, hence, authors cannot use these types on their own but theyserve in defining the permitted types:

Type Structure Example

Time hhmm ❶ or hh:mm ❶optionally followed by SST

1400, 14:00, 14:00(s), 1400(1530),14:00(15:30)

Day and Time Day Time MON 1400, BFR 14:00

SST following a Time (s) or (Time )

see Time

5. These simple date/time values form a period by themselves and authors can apply them directly intime applicabilities:


AIRAC first or last ❷ AIRACMonth

first AIRAC DEC

Day EEE ❶, HO-, HOL, HO+,BFR

MON

Day w/o Year DD-MMM ❶ 06-FEB

Month MMM ❶ JAN

❷ first or last are optional, if omitted, the grammar assumes first

6. Authors can enter ranges on these simple types or their combinations:

a. Time Range: 16:00..22:00

b. Day Range: MON..FRI or BFR..TUE or HO-..HO+

c. Day w/o Year Range: 1 FEB..25 MAR

d. Day and Time Range: MON 08:00..FRI 22:00

e. Month Range: JUL..AUG

f. AIRAC Range: AIRAC JUL..last AIRAC AUG or first AIRAC DEC..15 APR or 1 JUL..AIRAC SEP

The examples show the ranges using the DotDot operator, Authors can also apply the range syntaxusing the squared brackets.

7. Furthermore, authors can embed one or many of the above mentioned items in brackets in order to


RAD User Manual



http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/commonDefinitions/B2C_BaseTypes/B2C_Base_Types.adoc#_summer_shift_time_a_id_sst_a

except a list of other periods.

In JAN, MAR, JUN except (HOL, BFR) , the except clause relates only to June.

In (JAN, MAR, JUN) except (HOL, BFR) , the except clause relates to all listed months.

6.3.16 Physical Date and Time Formats

1. In contrast to the logical time, the physical time relates to a fixed calendar period.

This means, every physical time or date value must contain a date containing a year.


❶ marks references to the base types.

3. Please refer to the Logical Date and Time Formats chapter for details on the basic time and dateelements.

4. The time applicability is always a period, hence, authors cannot use these types on their own but theyserve in defining the permitted types:


Time stamp Date Time optionallyfollowed by SST

06-FEB-2019 14:00(s)

5. These simple date/time values form a period by themselves and authors can apply them directly intime applicabilities:


Date DD-MMM-YYYY ❶ 06-FEB-2019

6. Authors can enter ranges on these simple types or their combinations as described in Ranges:

a. Time stamp Range: 06-FEB-2019 16:00(s)..08-12-2019 22:00(s)

b. Date Range: 06-FEB-2019..08-12-2019

The examples show the ranges using the DotDot operator, Authors can also apply the range syntaxusing the squared brackets.

7. The grammar does not permit the usage of physical AIRAC numbers, for example AIRAC 2014 or, asrange, AIRAC 1910..AIRAC 2003 .

Instead, authors should create related validity periods and use H24 as time applicability.

6.3.17 The Compulsory Problem

TODO: update: users like both variants: manage airspace vs tell AO what to do

1. RAD authors apply the keyword compulsory-for-traffic to express that flights matching the followingflow need to file a flight plan via the location given in the left columns. For example:

AIRWAY Y138

FROM LUPOS

TO BEROK

Utilisation compulsory-for-trafficarr ad:LIRP & via as:LIPPACCthis-traffic-shall-filevia pt:TODNO except via pt:GAVRA

Applicability 06:00..21:00 (05:00..21:00)


RAD User Manual



http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/add/business/rad/RAD_ADD.adoc#LogicalDateAndTimeFormats

http://dhwebd05.cfmu.corp.eurocontrol.int:7990/bitbucket/projects/NCO/repos/docs/browse/src/commonDefinitions/B2C_BaseTypes/B2C_Base_Types.adoc#_ranges

ID Number LI2125

2. The actual meaning of this RS is:

for-traffic

arr ad:LIRP & via as:LIPPACC


via LUPOS Y138 BEROK &

via pt:TODNO except via pt:GAVRA

06:00..21:00 (05:00..21:00)

3. In principle, the grammar is able to make this conversion on all "compulsory" RS but, as explainedabove, the RAD application still produces the RAD as a set of Excel files.

4. In order to fill-in the AIRWAY, FROM and TO columns, the RAD application would be forced todisassemble the corrected expression, which would be practically impossible if the user has changed itas such:

for-traffic

arr ad:LIRP & via as:LIPPACC


via pt:BISON &

via LUPOS Y138 BEROK &

via pt:TODNO except via pt:GAVRA

06:00..21:00 (05:00..21:00)

Now, the RAD application would not know if it had to fill in the AIRWAY, FROM and TO columns, or thePOINT or AIRSPACE column.

5. Instead, the RAD application continues to permit the illogical keywords compulsory-for-traffic andonly-available-and-compulsory-for-traffic until we have the possibility to modernise the grammar.

6. Also, the linevia pt:TODNO except via pt:GAVRAcould refer to the POINT or AIRSPACE column, except for the fact that it contains the except keyword,which is not permitted in the POINT or AIRSPACE column.

This shows quite clearly that the syntax in the Excel files has not kept up with the development of thebusiness.

6.4 Screen Layout


RAD User Manual


1. Main Applications Menu: All applications available to you are listed side by side - being based on your profile andauthorisations, it may therefore look different than in the example above

2. Time - UTC time indication: Mouse over the Time to display the Date3. User management: Identifies the user currently logged, and provides a clean Logout function4. Application submenu: Lists all available options (if any) and provides link to the desired view/function/action:

Home: gets you back to the RAD Home (Section 6.5.1) page;Restrictions: Opens the Restrictions (Section 6.5.2) view;Aerodrome sets: Opens the Aerodrome sets (Section 6.5.3) view;DMR: Opens the DMR (Section 6.5.4) view;Map: Opens a Map (Section 6.5.5) window;Export: Opens the Export (Section 6.5.6) view.

5. Search (accordion): To specify the query criteria6. Results of Query (accordion): To display the query results7. Footer - Present at all times and all screens, the Footer provides, in addition to the usual copyright information, linksto the Online Help and to the Legal Notice, and displays the application version number.

6.5 Using the RAD Application

6.5.1 Home

Foreword: We assume that you are successfully logged in to the NES. Please refer to the AccessingApplications (Section 4) chapter for more information on how to connect to the ATM Information Portal andget to view the screen below.

Opening the RAD application gets you by default to the Homepage:


RAD User Manual


Note: The Homepage structure and content differ from the typical RAD pages, whose screen layout andnavigation principles are described in the Screen Layout (Section 6.4) chapter.

Published AIRACS:

The left-hand column provides at all times, shortcuts to the annexes belonging to the current AIRAC, the next AIRACand during a short period of 6 days before the next AIRAC switch, the frozen AIRAC+2 (from D-34 to D-28).

The right-hand column is divided in three collapsible sections

Increments:

Lists increments - amendments done after the AIRAC has been frozen.

Publication Priority:


RAD User Manual


For NCRs: Lists the DMRs in status DRAFT.The items are sorted on priority: the most urgent DMRs that still needs to be moved to READY – forvalidation by the NM RAD Team – are on top of the table.In case the responsible NRC does not move the DMR on time, the deadline will be missed and the includedamendments will not be published in the RAD - and will consequently not be implemented in CACD.For NM RAD team: : Lists the DMRs in status READY.The items are sorted on priority: the most urgent DMRs that still needs to be moved to PUBLISHED – aftervalidation by the NM RAD Team – are on top of the table. In case the NM RAD Team does not move the DMRon time, the deadline will be missed and the included amendments will not be published in the RAD andconsequently will not be implemented in CACD.

Note: The Attention icon is placed before a Publication Deadline to indicate that the intendeddeadline has been missed.

Note: DMRs printed in red in the Publication Priority pane are increments (this to differentiate fromamendments).

Upcoming CACD Changes:

Upcoming changes/updates to CACD entities that are referenced in RAD objects are listed in the Upcoming CACDChanges table.

The table is filled with data per country, so a given country only sees potential impact of upcoming changes to CACDentities to their own RAD objects (i.e. mainly restrictions).

The ID and CACD ID columns provide links to respectively open the corresponding Restriction Details (for restrictions)or Datasheet (for airspace entities) sections.


RAD User Manual


6.5.2 Restrictions

The Restrictions tab is primarily designed to provide easy means of querying the RAD database for specificRestriction(s).

The query layout is initially divided in two accordions :

1. Search - where you specify the query filters in the Search Restrictions section2. Results of Query - where the results are displayed in the Result list section.

Note: Once a query has been launched in the Search accordion, and a restriction selected in the Result listaccordion, a third Restriction details (Section 6.5.2.1.1) accordion will open, causing the Search one tocollapse.

More information on managing accordions in this chapter (Section 5.1).

Two basic workflows

Go to the Search Restrictions (Section 6.5.2.1) section if your primary intention is to check for existingRestrictions and potentially make modifications,Go to the Create Restriction (Section 6.5.2.2) section if your primary intention is to create a newRestriction.

6.5.2.1 Search Restrictions

The Search Restrictions form provides the possibility to query the restrictions by the following filters :


RAD User Manual


Appendix: Select/unselect the Appendix by means of their respective Select check boxes:

Remove selected items my means of their respective Close button:


RAD User Manual


Remove all present selected items with a click on the Close all button

Object ID: type in (part of) the name of the target item(s) to be retrieved.

Note: The search string may be start with a * wildcard, OR end with a * wildcard (i.e. *4000returns EDLK4000; *00 returns EDEP400, EDLK4000, EDLY500, LSLF400, etc.; LS* returnsLSAG1, LSLF400; LSLI4001, etc.)

Country Code: 2-letter ICAO Code for the CountryOnly Owned by: Restrictions only owned by the provided Country CodeDelegated to: Restrictions that are delegated from a given Country to the providedCountry CodeDelegated by: Restrictions that are delegated by the provided Country Code at a givenCountryCross borders: Checked to include cross-border restrictions (in both directions and at thesame time)

Full Text Search: Enter search word, no wildcardsDMR: Name or General purposeCACD Entity: ID of the CACD Entity(ies) you are searching forChange Indicator: specify the kind of change (NEW for a creation, AMD for an update, DELfor deleted and UNCHANGED for a period where no changes occurred).Change Between: Start AIRAC of the search rangeAnd: Stop AIRAC of the search rangeShow under work and published / Show under work only / Show published only: Radiobutton to select the appropriate search context.

Button Bar

The Button Bar associated to the Search form features the following commands:

Query: to launch the query,Clear: to clear the form from any entered parameter,Reset: to reset the form to its default values.

Results of the Query

Having specified the intended filters and parameters, click on the Query button to get the matching itemsdisplayed in the Results of Query (Section 6.5.2.1.2) accordion.

6.5.2.1.1 Restriction Details

The Restriction Details accordion is triggered by the selection of a given restriction from the Result list:


RAD User Manual


Layout


RAD User Manual


The Restriction details accordion is divided in three distinct sections:

1. Attributes (Section 6.5.2.2.1) -2. Validity (Section 6.5.2.2.2) - Listing all periods with a complete restriction expression.3. History (Section 6.5.2.2.4) - Keeping track of all the changes applied to a given Restriction.

Note: Please refer to their respective sections under Manage Restrictions (Section 6.5.2.2) chapter fordetailed information.

6.5.2.1.2 Results

The Results of query accordion presents the Result list, where all items matching the search criteria are sorted byAppendix Type - themselves differentiated by color:


RAD User Manual


Header

The Result List header features a Timestamp indicating the date and time of the query, indicates applied filters if any,and the found restrictions count.

The count is further broken down by appendix - and each type is associated to a different color:

Blue: Appendix 3 Red: Appendix 4Green: Appendix 5Magenta: Appendix 7Purple: Annex - Pan

You can use the color buttons to filter on or off the corresponding appendices.

Button Bar

Bulk Update: Apply the same amendment to multiple selected items (i.e. amend in bulk).Add to (new) DMR: Add one or more selected items to an existing DMR, or create a new DMR for thatpurpose.

Results Table

In each Appendix section, the Results table contains the following columns:


RAD User Manual


a check box to select the corresponding item.

The first column header features a Select All / Deselect All check box to globally select (or deselect)all listed items.

Ind: Change Indicator (can be NEW, AMD, DEL or UNCHANGED)ID: Unique Identifier of the Restriction.

Note: The presence of a vertical purple line in front of the ID indicates a published version - no barcorresponding to under work material.

Summary: Computed field Grouping : line 1 = restricted object; line 2 = Traffic availability; line 3 = FlowexpressionDMR: Associated to under work restrictions, displays the custom name of the DMR as specified in the Namefield and provides an hyperlink to directly access and open the corresponding DMR:

Note: The columns can be sorted and filtered - please refer to this section (Section 5.3) for details.

Restriction Details

Click on the Row of a given restriction ...

... to open the corresponding Restriction Details in the side accordion:


RAD User Manual


Note: The Increment icon are increments (this to differentiate from amendments).

Important: The background color of a given Validity indicates whether the considered period is ongoing (lightblue ), future (light green ) ... or past (grey )

6.5.2.2 Manage Restrictions

EB*This section gathers all you need to know when it comes to manage restrictions:

CreateEditCompare VersionsRevert

Create

A Restriction can be created with one of the following two fashions:

1. From the Search Restriction accordion2. From the DMR Details accordion

From the Search Restriction accordion

A Create new button is available from the Search accordion, allowing you to initiate the process of creating a new restriction:

The process of creating a restriction is obviously specific to each restriction type - but the principle is fundamentally the samefor all:

1. Specify the Appendix type:


RAD User Manual


2. The corresponding restriction editor (DCT_ARR in this example) then pops up :

3. Fill in the appropriate fields in the Attributes section,

Note: Please refer to the Attributes (Section 6.5.2.2.1) chapter for detailed information on how to create andmanage attributes.

4. Create the Validity period(s) in the Validity section,

Note: Please refer to the Validity (Section 6.5.2.2.2) chapter for detailed information on how to create andmanage validity periods.

5. Click on the Save button to complete the creation,

6. Select an existing DMR to which you intend to attach the restriction, or create a new one by means of the Create newDMR,

7. In the latter case, fill in the form then click on the Create and add rs button,


RAD User Manual


Note: Please refer to the Create New DMR (Section 6.5.4.2) chapter for detailed information on how to createand manage DMR.

From the DMR Details accordion

A Create button is available to you, under the Restriction Changes collapsible section, in the List of Restrictions header:

The rest of the creation process is the same as above described.

Edit

1. Query for the Restriction to edit:


RAD User Manual


2. Locate the Target item and click anywhere on the corresponding table row:

3. The corresponding Restriction Details view opens in a side accordion, its content ready for you to edit (in accordanceto your user profile and usage context):


RAD User Manual


4. Make your changes ...

5. ... and click on the Save button:

6. As in points 6 and 7 above, specify the target DMR (Existing or New)7. You get a notification upon successful update ...

8. ... And the History section reflects the update:

Compare Versions

1. Click on the Compare Versions button ...


RAD User Manual


2. ... and check what has been changed between Version States:

Note: Use the provided Radio Buttons to specify the two states to be compared.

Revert

Click on the Revert link of a given State row to restore the situation as it was back then.

6.5.2.2.1 Attributes

Note: The Attributes section is common to all types or restrictions (with the exception of the Military parameter,not relevant and therefore not present for DCT_LIM_AD nor DCT_TP)

The Attributes section of the Restriction Editor features a number of fields. Some read-only fields will already containdata, or will be automatically populated when the restriction is saved:

Restriction type (automatically set): The Type of the RestrictionOwner (mandatory - automatically set based on profile - editable): The Owner is the only user allowed toedit the restriction, except when the restriction is delegated.Delegatees (optional) : to indicate explicitly the country(ies) to which you want to give delegations on theRestriction - see below for more details on Restriction Delegation.Military (type-dependent): set by default to Non Military - can be toggled to Military

Restriction Delegation

Implicit and Explicit Delegation are available:


RAD User Manual


Country CodesFAB Codes

Add Country or FAB Codes by typing in the field Delegatees.Remove Codes by clicking the ‘x’ in the tagSave the edited set with the Save Delegation icon.

Example: MUAC

Restriction owned by YXImplicitly Editable by

EHEBEDEC

6.5.2.2.2 Validity

Note: The background color of a given Validity indicates whether the considered period is ongoing (light blue ), future (light green ) ... or past (grey )

Depending on the Status of the Restriction (Published or Under Work), the 0wnership (Owned or Delegated), and theEdit mode (Read Only or Edit), different actions can be available to you.

From the action buttons series

Paste from Clipboard... (Section 6.5.2.2.2.1)Copy to Clipboard... (Section 6.5.2.2.2.1)Create from... (Section 6.5.2.2.2.2)Validate (Section 6.5.2.2.2.3)Compare Validity (Section 6.5.2.2.2.4)Copy Validity (Section 6.5.2.2.2.5)Split Validity (Section 6.5.2.2.2.6)Delete Validity (Section 6.5.2.2.2.7)Add Utilization

In addition, the Validity parameters will vary depending on the Appendix Type - as detailed in the Parameters byType (Section 6.5.2.2.3) section.

From the Add Utilization link

Add Utilization... (Section 6.5.2.2.2.8)

6.5.2.2.2.1 Paste From - Copy To Clipboard


RAD User Manual


Use the Copy to Clipboard... button to capture the selected validity details of a given restriction and store it to thecomputer clipboard - from where you can then paste it to another restriction:

Use the Paste from Clipboard... button from the details of another restriction to insert the copied validity:

Adapt Start and End dates if relevant and click on the Select button, then confirm when prompted by means of theYes button:

The new validity is added to the restriction:


RAD User Manual


Lastly, click on the Save button to add this new restriction to an existing ADMR - or create a new one:

6.5.2.2.2.2 Create From

This function serves to create a new restriction based on an existing one, instead of starting from scratch. Select thebase validity you want to clone into a new restriction, and click on the Create From... button:

From the provided Create Restriction template, apply the desired update or addition then save the changes:


RAD User Manual


6.5.2.2.2.3 Validate

The Validate button is only available when a single Validity period is selected:


RAD User Manual


This function allows you to validate - per validity period - the current restriction expression against the currentimplementation of the RAD grammar.

The validation results can be:

SuccessFailure with ProposalFailure without Proposal

Only modified (selected by default) only displays the lines that were modified:

All displays the whole content of the validity:

The Utilizations button opens or closes the


RAD User Manual


6.5.2.2.2.4 Compare Validity

The Compare Validity button is only available when multiple Validity periods are selected:

A Compare validity states popup window displays the comparison with selected states. It is set to by default to OnlyModified - focusing on highlighting the changes:

Set to All to view the whole content:

6.5.2.2.2.5 Copy Validity

The Copy Validity button is only available when a single Validity period is selected:


RAD User Manual


Provide Start and End dates in the Copy dialog:

6.5.2.2.2.6 Split Validity

The Split Validity button is only available when a single Validity period is selected:

This command allows you to split an existing period by providing a new (earlier) End date in the Split dialog:


RAD User Manual


The provided (D) date is used as new End date for the first segment of the split, and a (D+1) date is set as Start datefor the second segment of the split:

6.5.2.2.2.7 Delete Validity

The Delete Validity button is only available when a single Validity period is selected - and is disabled when only oneValidity exists or remains:

Confirm when prompted ...

... And Save the changes.


RAD User Manual


6.5.2.2.2.8 Add Utilization

Use the Add Utilization link at the bottom of a Validity component (in Edit mode) ...

.. to add one (or more) entries:

Click on the Delete button of a given Utilization entry to remove it:

... And do not forget to Save your changes.

6.5.2.2.3 Parameters by Type

Common Parameters

Start: Indicates when the period starts - set by default to the project Operations AIRAC.End: Indicates when the period ends.

Type-specific parameters

Appendix 3Appendix 4

P2PFRALIM

Appendix 5ARRDEPTPGENERAL CONDITIONS

Appendix 7Annex - Pan Europe

Appendix 3 - CP


RAD User Manual


From (ADEP): Aerodrome of DepartureTo (ADES): Aerodrome of ArrivalCondition: Describes conditions for applying FL capping for relevant DEP/ARR airport area/groupFlight Level Capping: Describes FL limitations imposed by States/FABs/ANSPs.Time applicability: Describes the time period in which each DCT segment is available.Operational Goal: Describes the reason for allowance or non-allowance of each DCT segment presented bythe States/FABs/ANSPs. For the DCT segments the operational goal is not mandatory and this column mightcontain "BLANK BOX".Remarks: Describes for each DCT segment all possible remarks concerning the airspace crossed by eachallowed DCT.

Appendix 4 - P2P

Exception(s): There is an exception on top of the general condition that applies.From (mandatory): Starting point of the DCT segment. It contains either two or three letter abbreviation ofrelevant NAVAID or five-letter name code (5LNC) of relevant waypoint. <PT> expression.To (mandatory): Ending point of the DCT segment. It contains either two or three letter abbreviation ofrelevant NAVAID or five-letter name code (5LNC) of relevant waypoint. <PT> expression.Lower Vert. Limit (mandatory): Lower limit of the vertical slice. It contains either relevant altitude or FL orabbreviation GND (Ground) provided/required by the States/FABs/ANSPs or abbreviation/s MSA (MinimumSector Altitude) and/or MEA (Minimum En-route Altitude) if no altitude or FL defined by theStates/FABs/ANSPs. <FL> expression. Optionally {} used for altitudes.Upper Vert. Limit (mandatory): Upper limit of the vertical slice. It contains either relevant FL orabbreviation UNL (Unlimited) provided/required by the States/FABs/ANSPs. <FL> expression. Optionally {}used for altitudes.Allowed: Describes allowance or non-allowance of each DCT segment by using Yes or No.Cruising Level Direction: Describes the direction of cruising levels used along relevant DCT segment: ODDor EVEN. This data is for information purposes only, not mandatory and is included if provided by theStates/FABs/ANSPs. The FL orientation scheme (FLOS) applied by each State normally shall be published inAIP ENR 1.7. The NM systems are not checking the compatibility between the Direction of Cruising Levels andflight plans filed.ATC Unit (mandatory): Describes for each DCT segment the relevant ATC Unit coding to which itbelongs/passing. The column is for searching purposes as only possibility to sort the DCT segments byStates/FABs/ANSPs as ID number is not compulsory. The relevant ATC Unit code is not required for the NMsystems and for States/FABs/ANSPs with more than one ACC/UAC different codes might be used. ATC Unitcodes might be either for ACC or UAC.Remarks: Describes for each DCT segment all possible remarks concerning the airspace crossed by eachallowed DCT.Traffic Availability: pull-down menu containing the following options:

Not available for trafficMandatory for trafficOnly available for trafficOnly available and compulsory for traffic

Flow: list of flow conditions which describe the utilization of each DCT segment structured in accordance withRAD General Description provisions. Time applicability: Describes the time period in which each DCT segment is available.Operational Goal: Describes the reason for allowance or non-allowance of each DCT segment presented bythe States/FABs/ANSPs. For the DCT segments the operational goal is not mandatory and this column mightcontain "BLANK BOX".


RAD User Manual


Appendix 4 - FRA

ATC Unit (mandatory): Describes for each DCT segment the relevant ATC Unit coding to which itbelongs/passing. The column is for searching purposes as only possibility to sort the DCT segments byStates/FABs/ANSPs as ID number is not compulsory. The relevant ATC Unit code is not required for the NMsystems and for States/FABs/ANSPs with more than one ACC/UAC different codes might be used. ATC Unitcodes might be either for ACC or UAC.ATC Vertical Limit: The lower/upper vertical limits of the relevant ATC Unit where the DCT enroute limit isapplied.CB DCT Limits: Allowed or not allowed DCT en-route limits across the ATC Unit borders.ID DCT Limits: NM system code given to the relevant Not Allowed Cross-border DCT en-route limit.Time applicability: optional time applicability for the restriction.Remarks: Optional remarks.

Appendix 4 - LIM

ATC Unit (mandatory): Describes for each DCT segment the relevant ATC Unit coding to which itbelongs/passing. The column is for searching purposes as only possibility to sort the DCT segments byStates/FABs/ANSPs as ID number is not compulsory. The relevant ATC Unit code is not required for the NMsystems and for States/FABs/ANSPs with more than one ACC/UAC different codes might be used. ATC Unitcodes might be either for ACC or UAC.ATC Vertical Limit: The lower/upper vertical limits of the relevant ATC Unit where the DCT enroute limit isapplied.CB DCT Limits: Allowed or not allowed DCT en-route limits across the ATC Unit borders.ID DCT Limits: NM system code given to the relevant Not Allowed Cross-border DCT en-route limit.Time applicability: optional time applicability for the restriction.Remarks: Optional remarks.

Appendix 5 - DCT_ARR

Exception(s): There is an exception on top of the general condition that applies.ARR AD (mandatory): Involved aerodromes in this restriction/exception, if not a RAD aerodrome set.First PT STAR/STAR ID (mandatory if DCT ARR PT empty - and the other way around):

Describes the initial waypoints of a STAR. It contains either two or three letter abbreviation ofrelevant NAVAID or five-letter name code (5LNC) of relevant waypoint.Describes the coded designator of relevant STAR. It contains from three and seven alphanumericcharacters in accordance with ICAO Annex 11. The ID of a STAR: <STAR> expression.

DCT ARR PT: Describes the initial waypoints of an arrival DCT. It contains either two or three letter


RAD User Manual


abbreviation of relevant NAVAID or five-letter name code (5LNC) of relevant waypoint.Traffic Availability: Pull-down menu containing the following options:


Flow: Describes the utilization of each ARR Airport Connectivity or ARR FRA requirement in accordance withRAD General Description provisions. Time applicability: Describes the time period in which each DCT segment is available.Operational Goal: Describes the reason for applying each ARR AD Restriction or ARR FRA requirementpresented by the States/FABs/ANSPs.Remarks: Optional free text.

Appendix 5 - DCT_DEP

Exception(s): There is an exception on top of the general condition that applies.DEP AD (mandatory): Involved aerodromes in this restriction/exception, if not a RAD aerodrome set.Last PT SID/SID ID (mandatory if DCT ARR PT empty - and the other way around):

Describes the final waypoints of a SID. It contains either two or three letter abbreviation ofrelevant NAVAID or five-letter name code (5LNC) of relevant waypoint.Describes the coded designator of relevant SID. It contains from three and seven alphanumericcharacters in accordance with ICAO Annex 11. The ID of a SID: <SID> expression.

DCT DEP PT: Describes the final waypoints of a departure DCT. It contains either two or three letterabbreviation of relevant NAVAID or five-letter name code (5LNC) of relevant waypoint..Traffic Availability: pull-down menu containing the following options:


Flow: Describes the utilization of each DEP Airport Connectivity or DEP FRA requirement in accordance withRAD General Description provisions. Time applicability: Describes the time period in which each DCT segment is available.Operational Goal: Describes the reason for applying each DEP AD Restriction or DEP FRA requirementpresented by the States/FABs/ANSPs.Remarks: Optional free text.

Appendix 5 - DCT_TP

SID/STAR Requirements: Describes in plain free text the content of SID/STAR Requirements for State /FAB / ANSP Airport Connectivity.Time applicability: Describes the time period in which each DCT segment is available.

Appendix 5 - GENERAL CONDITIONS


RAD User Manual


Limits: Describes in plain text the content of DCT Limits and SID/STAR Requirements for State / FAB / ANSPAirport Connectivity.Time Applicability: Describes the time period in which each DCT segment is available.

Appendix 7 - FUA

AIP RSA ID: Identification/Coded name of Restricted Airspace causing FUA Restriction. Identification is asper State AIP.CACD RSA ID: Identification/Coded name of Restricted Airspace implemented in NM systems. Non-identicalRSA name may be required due character limitations in CACD.Affected ATS route(s)/DCT(s): When relevant, describes all ATS routes and/or DCTS affected/closed.Description: Not available for traffic during the times and within the vertical limits allocated atEAUP/EUUP (mandatory)Exceptions: Describes the utilization of each FUA Restriction structured in accordance with RAD GeneralDescription provisions.Operational Goal: Describes the reason for applying each FUA Restriction presented by theStates/FABs/ANSPs (mandatory for each Routing Restriction).Remarks: Free text.

Annex - Pan Europe

Restricted Airway: Identification of ATS route where relevant Routing Restriction is applied. Identificationis by relevant Route Designator (RD) letter with or without prefix "U". The prefix "U" in the RD differentiaterelevant ATS route in lower and upper airspace.From: Describes first/start point of ATS route segment where relevant Routing Restriction is applied Itcontains either two or three letter abbreviation of relevant NAVAID or five-letter name code (5LNC) ofrelevant waypoint.To: Describes last/end point of ATS route segment where relevant Routing Restriction is applied. It containseither two or three letter abbreviation of relevant NAVAID or five-letter name code (5LNC) of relevantwaypoint.Point or Airspace: Describes the point or airspace where relevant Routing Restriction is applied. It containseither two or three letter abbreviation of relevant NAVAID or five-letter name code (5LNC) of relevantwaypoint or airspace name as coded in CACD. A list of points: <PT_LIST> expression or an airspace:<AS_LIST> expression.ATC Unit: Describes for each DCT segment the relevant ATC Unit coding to which it belongs/passing. Thecolumn is for searching purposes as only possibility to sort the DCT segments by State/FABs/ANSPs as IDnumber is not compulsory. The relevant ATC Unit code is not required for the NM systems and forStates/FABs/ANSPs with more than one ACC/UAC different codes might be used. ATC Unit codes might beeither for ACC or UAC.Traffic Availability: pull-down menu containing the following options:


Flow: Describes the utilization of each Routing Restriction structured in accordance with RAD General


RAD User Manual


Description provisions.Time applicability: Describes the time period in which each DCT segment is available.Operational Goal: Describes the reason for applying each Routing Restriction presented by theStates/FABs/ANSPs. For each Routing Restriction the operational goal is mandatory and this column shall notcontain "BLANK BOX".Remarks: Describes for each RAD unit, all possible remarks concerning the utilization.

6.5.2.2.4 History

The History section keeps track of all the changes applied to a given Restriction:

The above summary reflects the evolution of the following Restriction (BOT meaning, in this context, the date when theRestriction was Created):

Use the Compare Versions button to compare between various versions of a given Restriction.

You can visualize the changes occurred in the resulting segment - specified by means of the provided Radio buttons(the left-hand button determining a Start date and the right-hand button determining an End date.

The Only Modified option is selected by default - highlighting the changes:


RAD User Manual


Select the All option to get the full content of the compared versions.

CLastly, you may lick on the Revert link of a given State row to restore the situation as it was back then:

6.5.3 Aerodrome Sets

The Aerodrome sets tab follows the same navigation principles as exposed in the Restrictions (Section 6.5.2)chapter.


RAD User Manual


1. a Search accordion on the left - where you specify the query filters in the Search Aerodrome Sets section2. a Results of Query accordion on the right - where the results are displayed in the Result list section.

Note: Once a query has been launched in the Search accordion, and a restriction selected in the Result listaccordion, a third Aerodrome Set Details (Section 6.5.3.1.1) accordion will open, causing the Search one tocollapse.

More information on managing accordions in this chapter (Section 5.1).

Two basic workflows

Go to the Search Aerodrome Sets (Section 6.5.3.1) section if your primary intention is to check forexisting Restrictions and potentially make modifications,Go to the Create Aerodrome Set (Section 6.5.3.2) section if your primary intention is to create a newRestriction.

6.5.3.1 Search Aerodrome Sets

The Search Aerodrome Sets form provides the possibility to query the Aerodrome Sets by the following filters :


RAD User Manual


Name: The name provided to identify the Aerodrome Set.Object Owner: The Owner is the only user allowed to edit the Aerodrome Set.Full Text Search: Enter search word, no wildcardsDMR: Name or General purposeCACD Entity: ID of the CACD Entity(ies) you are searching forChange Indicator: specify the kind of change (NEW for a creation, AMD for an update, DEL forremoval/deletion from the publication and UNCHANGED for a period where no changes occurred) - shouldonly be used in combination with a date rangeChange Between: Start AIRAC of the search rangeAnd: Stop AIRAC of the search rangeShow under work and published / Show under work only / Show published only: Radio button toselect the appropriate search context.

Button Bar



Results

The Results of query accordion presents the Result list, where all items matching the search criteria are sortedalphabetically:


RAD User Manual


The Result List header features a Timestamp with the date and time of the query; indicates applied filters if any, aswell as the found restrictions count.

Note: The columns can be sorted and filtered - please refer to this section (Section 5.3) for details.

Results Table

The Results Table contains the following columns:

a check box to select the corresponding item.

The first column header features a Select All / Deselect All check box to globally select (ordeselect) all listed items.

Ind: Change Indicator Status.Name: The name of the object, as provided in the Name field.

Note: The presence of a vertical purple line in front of the Name indicates a published version - nobar corresponding to under work material.

Type: Can be one of the following:

AREA - Defines as a number of airfields within the same region and may comprise several“Groups”, or individual airfields.GROUP - Defines a number of three or more airfields that may be subject to the samerestrictions. For example a major destination may have a number of minor satellite airfields inthe vicinity; this constitutes a “Group”.YZ_GROUP - Defines a group of Aerodrome Sets.

Definition: Defined composition on the Aerodrome Set.

Note: The Increment icon are increments (this to differentiate from amendments).

Owner: 2-letter ICAO Code for the Country to which belongs the object author.DMR: Associated to under work restrictions, displays the custom name of the DMR as specified in the Namefield and provides an hyperlink to directly access and open the corresponding DMR:

The Add to (new) DMR button allows you to add the selected item(s) to an existing DMR, or to create a new DMR(Section 6.5.4.2) for that purpose:

Aerodrome Set Details


RAD User Manual


Click anywhere in the table row of a given Aerodrome Set...

... to open the corresponding Aerodrome Sets Details in a new accordion:

Note: Please refer to the Aerodrome Set Details (Section 6.5.3.1.1) chapter for more information.

6.5.3.1.1 Aerodrome Set Details

The Aerodrome Set Details accordion (on the right of the graphic below) is triggered by the selection of a givenAerodrome Set from the Result List (from the Result of Query accordion):

AZ Details: The Aerodrome Set Identifier, which is a concatenation of the Aerodrome Set Owner, Name and Type.Table: The Validity section lists all periods (i.e. start date and end date) with a defined composition of the AerodromeSet.History: The History section keeps track of all the changes applied to a given Aerodrome Set.

Screen layout - Object management - Using Validities ...

Note: Due to strong similarities between how Restrictions and Aerodrome Sets are handled in the NES, pleasekindly refer to the descriptions provided in the Restriction Details (Section 6.5.2.1.1) and the ManageRestrictions (Section 6.5.2.2) chapters.

6.5.3.2 Manage Aerodrome Set

This section gathers all you need to know when it comes to manage restrictions:

Create


RAD User Manual


EditCompare Versions - same behavior as described in the Restrictions chapterRevert - same behavior as described in the Restrictions chapter

Create

An Aerodrome Set can be created with one of the following two fashions:

1. From the Search Aerodrome Sets accordion2. From the DMR Details accordion

Create from the Search Aerodrome Sets accordion

A Create new button is available from the Search accordion, allowing you to initiate the process of creating a new AerodromeSet:

The creation process is the following:

1. In the Create Aerodrome Set form ...

2. Fill in the appropriate fields in the Attributes section:

Name: Composed of a first field for the Name of the Aerodrome Set, followed by a second (unlabelled) fieldto specify the Type.Owner: Update the Owner if need be

3. Create the Validity period(s) in the Validity section,4. Click on the Save button to complete the creation,


RAD User Manual


5. Select an existing DMR to which you intend to attach the restriction, or create a new one by means of the Create newDMR,

6. In the latter case, fill in the form then click on the Create and add az button,

Note: Please refer to the Create New DMR (Section 6.5.4.2) chapter for detailed information on how to createand manage DMR.

Create from the DMR Details accordion

A Create button is available to you, under the Aerodrome Set Changes collapsible section, in the List of Aerodrome Setsheader:

The rest of the creation process is the same as above described.

Edit


RAD User Manual


1. Query for the Aerodrome Set to edit:

2. Locate the target item and click anywhere on the corresponding table row:

3. The corresponding AZ Details view opens in a side accordion, its content ready for you to edit (in accordance to youruser profile and usage context):

4. Select the Validity on work on - this enables the action buttons :


RAD User Manual


5. Make your changes and click on the Save button:

6. As already explained in above, specify the target DMR (Existing or New)7. You get a notification upon successful update ...

6.5.4 DMR

The DMR is presented, as the other RAD modules, in two main accordions: the first for querying, the second to displayresults.


RAD User Manual


Search

The Search DMR form provides the possibility to query by the following filters :

Name: The name of the DMR (free text)General purpose: Reason for the DMR to be created (free text) - Features a combo listing existing namesfor anyone to be (re)used - providing homogeneity and facilitating the creation of subsets using aconsolidated naming convention.Full text search: Search for exact text string - no wildcards - caps irrelevantOwner: Country code of the logged in profile that created the DMRStatus: list of possible status DMR workflow

Initial: details only visible to owner/creator - can be moved forward by NRC or LRCDraft: similar to initial but visible to all RAD users - can only be moved forward by NRCReady: Ready to be validated by NM RAD team - can be pushed back only by NM RAD Team (norecall) - upon validation, can only be moved forward by NRC => publishedPublished: cannot be changed anymore by anyone changes via new DMR (and object becomesPUBLISHED and no longer UNDER WORK)


RAD User Manual


Stopped: Select between No, Yes and Both.Change Between / And: Allows to query for DMR containing objects that changed in the provided daterange.

Button Bar



Result List

The Results of query accordion presents the Result list, where all items matching the search criteria are listed(alphabetically sorted on name by default):

Header

The Result List header features a Timestamp of the date and time of the query; and indicates the applied filters (ifany) as well as the found DMRs count.

Button Bar

The Preview button allow you to preview - and eventually in a second step export this preview in a printabledocument - all the amendments you made to the selected DMR (the changes being highlighted as in the current Excelfile)

In addition, a Delete button appears in the title bar for DMR with status Initial. Use it to delete the selected items.

Note: this function is only available

Table

The Results table contains the following columns:

a check box to select the corresponding item(s).

The first column header features a Select All / Deselect All check box to globally select (or deselect)all listed items.

Status / Owner / Name : See definitions above. General Purpose: Reason for the DMR to be created (free text) - Features a combo listing existing namesfor anyone to be (re)used - providing homogeneity and facilitating the creation of subsets using aconsolidated naming convention.

Note: The columns can be filtered and sorted - please refer to this section (Section 5.3) for details.

DMR Details

Click anywhere in the table row of a given DMR to open the corresponding DMR Details (Section 6.5.4.1) accordion:


RAD User Manual


6.5.4.1 DMR Details

The DMR Details accordion features a header and four collapsible sections:

Header

Groups high level information and actions

DMR: Owner, Name and General Purpose fields as earlier describedStart Date: Indicates the current Start Date - it is editable and allows you to move the DMR to a laterchange data (i.e. start date) and updates all included objects' validity periods accordingly.Preview: Allows you to preview - and eventually in a second step export this preview in a printabledocument - all the amendments you made to the selected DMR (the changes being highlighted as in thecurrent Excel file)Ongoing: A switch that can be set to Stopped or Ongoing. Delete: The Delete button is only present in DMR in Initial status.(unnamed) Phase Transition Combo: Provides context-sensitive navigation to the next available Status. Validation: Signals possible Errors (red) or Warnings (yellow) on the DMR situation - and their respectivenumber.Click on the Validation button to get the Validation Report listing all encountered Errors and Warnings.


RAD User Manual


Note: Please refer to the Validation Report (Section 6.5.4.3) chapter for more information.

Comments

Comments: Free Text - General comments visible to anyone allowed to see the DETAILS of a DMR.Internal comments: Free text - only visible to members having the same Country code as the DMR owner.

Restriction Changes

The List of Restrictions behaves as the Restriction Results component described in the Search Restriction (Section6.5.2.1) chapter. Not only does it display the current situation, it also allows changes on the fly, by means of thefollowing functions:

Button Bar

Move to (new) DMR

Click on the Move to (new) DMR button to split and attach the selected restriction(s) to an existing DMR, or create anew one on the fly.

Note: Please refer to the Create New DMR (Section 6.5.4.2) chapter for more information on this process.

Create

The Create button allows you to create Restrictions of the selected type directly within the current DMR:


RAD User Manual


Add

The Add button allows you to search for a given Restriction, and add it to the current DMR.

Remove

Click on the Remove button to deleted selected Restriction(s) from the DMR.

Aerodrome Set Changes

The Aerodrome Set Changes section behaves as does the Restriction Changes one described right above:

DMR Documentation

The DMR Documentation section allows to add files and attachments to the current DMR:

Use the Add Documentation function to select and upload documents - Click on the Delete button to remove selectedfile(s).

Note: The Private switch allows you to restrict the corresponding document to members of your Country group.By default, the switch is not activated, so the document is visible to all.

6.5.4.2 Create New DMR

A DMR can be created with one of the following three fashions:

1. From the Search DMR accordion2. From the Restriction or Aerodrome Set Details accordion3. From the Restriction or Aerodrome Set Result of Query accordion

Search DMR accordion

A Create new button is available from the Search accordion, allowing you to initiate the process of creating anew DMR:


RAD User Manual


The creation process is the following:

1. In the Create New DMR form ...

2. ... Fill in the appropriate fields:

Name: The name of the DMRGeneral Purpose: Same as earlier definedStart Date: (optional) The start date for which you want to make changes and used as STARTfor the validity period - can be considered and used as a smart method to split periods.Comments / Internal Comments: Same as earlier defined

3. Click on the Create button to complete the creation,


RAD User Manual


4. This is the notification you get when the process is successful:

Details accordion

A Save button is available that allows you to Add to (new) DMR (valid for a single amended object):

The rest of the process is descried above...

Results of Query accordion

The Add to (new) DMR button is available after selecting more then one object from the result list:


RAD User Manual


6.5.4.3 Validation Report

The Validation button is featured in the top right corner for all unpublished DMRs (in other words, in states Initial,Draft or Ready).

A color patch dot indicates the number and type of issues to be reviewed/resolved prior to publication.

The color indicates the severity: yellow = warning while red = error. Errors are blocking issues are taking precedenceover warnings.

Rules:

Concurrent Editing

Overlapping states with different content in different DMR, issues an errorNon-overlapping states with different content in different DMR, issues a warning

Ownership/delegation

RAD Objects (RS/AZ) in the DMR without ownership or delegation, issues an error

RAD Object Content

Absence of RAD Object (RS/AZ) in the DMR, issues a warningUnchanged RAD Object (RS/AZ) in the DMR, issues a warning

The numeral indicates the number of issues of the displayed type.

In cases where the validation report covers both types, blocking issues will be the only ones displayed via the counter.

The Validation Report is generated and displayed when you click on the Validate button:


RAD User Manual


The issues found are listed and grouped by restriction, and the reasons for raising the issue are detailed.

For errors, links are provide for quick access to the concerned restrictions and facilitate the edition/correctionprocess.

Furthermore, a Propose Solution button is available for each individual error to assist the deconfliction process.The proposed changes are listed for you to accept with the OK button, or reject with the Cancel button:


RAD User Manual


Click on the Close button to exit the Validation Report.

6.5.5 Map

Note: The Map color scheme has been changed since the screenshots below were taken - Land has now a lightershade of gray, and Water a light shade of green:

Tools and functions are however unchanged...

The Map is accessed via the Map button on the Menu bar:

This results in displaying a void Map - ready for you to use: create a new map, retrieve data from a previously savedDossier, ...


RAD User Manual


Note: Please refer to the Map Dossier (Section 6.5.5.1) chapter for detailed information on using theDossiers.

The Map component allows CACD Entities (routes, areas, points, aerodromes, ...) to be plotted on a Map, featuring arange of tools and functions further described in the Map Controls (Section 6.5.5.2) chapter:

Map Layout


RAD User Manual


Map Dossier Tray

Info Tray

Map display

Controls

Map Dossier Tray

The Map Dossier is a container that can be created, saved to your user profile, retrieved and otherwise edited. TheMap Dossier Tray is the management component allowing you to perform all actions linked to the usage of MapDossier.

Note: Please refer to the Map Dossier (Section 6.5.5.1) chapter for detailed information.

Info Tray

The Info Tray is located in the top right corner of the Map - click on the Expand arrow to open it:

1. Collapse arrow - to close the Info Tray2. Name of the Dossier

Note: A newly created Dossier is automatically named "untitled_x" by the system, and is referenced by thisunique name until it is explicitly saved.

The * sign is appended to a Dossiers's name to indicate that it contains yet unsaved changes.

3. UTC Time4. Link to the Help package

Map Display


RAD User Manual


This is the main area, where the CACD entities are plotted. Several mouse actions are available to you to dictate howthe content is to be displayed:

Zooming

Wheel controls

Roll up to zoom in - roll down to zoom out

Tip: Press and hold the [Ctrl] key down while rolling up or down the mouse wheel to get smaller/finerincrements.

Click controls

Left-Double-click to zoom in - Right-double-click to zoom out

About Zoom factor

(A zoom factor can be assimilated to a zoom "speed" - the higher the factor, the faster the zoom ...)

Zoom In / Out using a scale factor of 2 based on “+” / “-“ buttons of the navigation controller also withcorresponding shortcuts on “+” / “-“ and numpad “+” / “-“ keyboard keys

+ mouse wheel scroll on mouse pointer using a scale factor of 1.5

+ CTRL-mouse wheel scroll on mouse pointer using a scale factor of 1.1

Panning

Click and drag the map in any direction to have map follow the mouse movements.

Controls

A series of controls and indications are grouped at the bottom of the Map display:

They comprise the following features:

Coordinates: Indicates the coordinates of the point designated by the tip of the mouse

pointer.

Scale: Indicates the scale of the map as set by the current zoom factor (ranges from 2 NM to 2000 NM).

Draw within Boundaries: Used to limit the plotting within the boundaries of the current display window.

LevelBand: Certain entities, like for instance a route, are defined for a given altitude or range. Make use of this

tool to get to see the object as defined at the desired flight level.

Timeline: Navigate back and forth in time and have the objects subject to specific timestamp and validities to

visually reflect the changes in the course of the day, the week, the year, ...

Azimuth: Defines the parameters of the Azimuth filter.

Measuring tool: Allows you to measure distances on the map.

Vertical view: Displays the vertical definition for a given selected entity, along a user defined A-B line.

Map legend: Provides compact access to the meaning of the various icons and symbols you may find on the

Map.

Note: Please refer to the Map Controls (Section 6.5.5.2) section for detailed information.

Plotting on the Map

Objects to be plotted need to be first queried/introduced and subsequently selected using the Map Search component -simply type in the starting letters of the target entity to narrow down the list of proposed matching items:


RAD User Manual


Actions from the Map

For every Entity displayed on the Map, contextual menus are available at the tip of your mouse pointer, suppressing theneed to go to the Dossier tray for the most common actions:

Get info

Mouse over an Entity to get a details tooltip (Entity Type / Entity ID / Name):

Action Menu


RAD User Manual


Right-click on the icon of an Entity to get a contextual menu featuring the following commands (what you get to seemay vary depending on the nature of the concerned entity):

Fit on map: Zooms in in such a way that the selected entity (or entities) fully occupies the available mapspace:

Unfit on map: Action reverse to Fit on Map

Where used: Builds and open a table listing all usage occurrences of the selected entity, grouped by EntityType:


RAD User Manual


Remove from map: Deletes the selected entity from the Map (and consequently, from the Dossier)Details: Opens a new browser window displaying the Details for the selected entity - Please refer tothe Details (on-line documentation) chapter for more information.Show decomposition: From a selected composite entity, use that command to reveal the composingobjects:


RAD User Manual


Hide decomposition: Action reverse to Show decompositionShow coordinates: For Airblocks, shows the coordinates for each composing point:


RAD User Manual


Hide coordinates: Action reverse to Show coordinates

Stacked Objects

When multiple objects are displayed on top of each other, the contextual menu will allow you to differentiate the layers,and facilitate the selection or intended action:

Managing Maps

All actions in relation with Map management are occurring in the Map Dossier Tray - Please refer to the Map Dossier(Section 6.5.5.1) chapter for detailed information on managing Airspace Maps

6.5.5.1 Map Dossier

Airspace maps can be saved and later retrieved for edition (or deletion) - by means of a data container named MapDossier.

In addition to the various Entities having been added onto the Map, the Dossier also keeps track of the filtering settings(such as zoom and pan, time- or level-dependent states or objects, ...) - all this under a user-defined name. EveryDossier you create is associated to your User Profile.

All actions in relation with Map management are occurring in the Map Dossier Tray - click on the arrow to openit ...


RAD User Manual


... and conversely, click on the arrow to close:

Dossier Layout

1. Search CACD IDs: Used to query the ENV syste:m2. Map Content List: Table grouping by Type the various items participating in the Map3. Dossier Management: Where you create, save and delete your Dossiers


RAD User Manual


4. Paging system: To navigate between multiple display page

Actions from the Map Dossier

All global actions commonly associated to the usage of map data are present in the Dossier:

Create (and save)QueryPlotOpen (and retrieve)EditDelete

Note: Some of these actions are also available directly from each Entity contextual menu - please referto Actions from the Map (Section 6.5.5) section for more information.

Create a Dossier

Creating a Dossier from scratch

Open a new Map window from the main header:

Optionally enter some content, then perform the following actions:

1. Provide a Name for the Dossier (Demo_2 in this example),2. Click on the Save button

As you can check, the newly Demo_2 created Dossier is now listed:


RAD User Manual


Creating a Dossier from current data

From an already populated Map ...

... type in a name for the new Dossier ...

... and click on the Save button:


RAD User Manual


The newly created LFPG_SPH Dossier has been successfully created and is now listed with the Dossiers available toyour profile:

Query for CACD Entities

Start to type in the ID you are searching for, and note how the Results list is populated as you go:


RAD User Manual


... and when the list has been narrowed down sufficiently for you purpose, simply located the searched item and clickon it:

Plotting on the Map

No further action than querying as presented above is required to have the selected Entity plotted on the Map:

Repeat the operation to add more elements:


RAD User Manual


Open a Dossier

Opening a Dossier is just a matter of locating it in the list, and clicking on its Name:

Edit a Dossier

To edit a Dossier, start by opening it (if not already so), then make some modifications. When ready, click on theOverwrite button of the target Dossier from the list:

Delete a Dossier

Deleting a Dossier is a quite simple operation:

Click on the Delete button corresponding to the item to be deleted...


RAD User Manual


... then confirm the command by clicking on the Yes button:

Actions from the Map Content List

At a finer level, these actions featured in the Map Content List allow additional control on data:

1. Select: Mouse over to reveal on the Map,2. Expand/collapse subsections,3. Actions at Type level:

Hide [Type] Show [Type] Delete

4. Actions at Entity level:Hide [Type] Show [Type] Delete Fit on Map Unfit on Map


RAD User Manual


Where used Show/Hide Coordinates on Map (Entity = AIRSPACE, see below)

5. Global delete at List level: results in a blank map

6.5.5.2 Map Controls

The Map component allows you to plot and work with various Airspace entities: routes, areas, points, aerodromes, ...

A series of controls and indications are grouped at the bottom of the Map display:

They comprise the following features:

Info sectionDraw within BoundariesLevelBandTimelineAzimuthMeasuring toolVertical viewMap legend

Multiple tools can be used at the same time, and the active components have their icon painted in green:


RAD User Manual


Saved Settings

Whenever some changes have been applied to the settings of a filter, the Icon corresponding icon gets a green band toreflect the customisation:

Even when the filter is deactivated and its layer removed from the map, the settings are persisted:

These settings will be kept along with the rest of the content of any Dossier you decide to Save - and can therefore belater retrieved when you load that Dossier.

Note: Please refer to the Map Dossier (Section 6.5.5.1) chapter for detailed information on Map Dossiermanagement.

Show Settings

Filter settings are revealed in a tooltip when you mouse over the filter icon:

Reset Filters

Active filter settings can be manually reset (right-click on the target filter):


RAD User Manual


Info

Coordinates: Indicates the coordinates of the point designated by the tip of the mouse

pointer.

Scale: Indicates the scale of the map as set by the current zoom factor (ranges from 2 NM to 2000 NM).

Draw Within Boundaries

Set the zoom factor at desired level, then use this tool to draw the selected entities within the strict boundaries of thedisplay window (and in the process, reduce the number of entities to be drawn, and augment overall performance):

1. Set the pan and zoom,2. Select the desired entities,3. click on the Display button:

The entities are plotted only in the specified area:


RAD User Manual


... and this is the same selection, with a lower zoom factor:

4. A temporary dossier, corresponding to the plotted series, is automatically added in the Dossier tray:

5. A selection of temporary items can easily be added to your currently opened Dossier:

6. And this temporary dossier can alternatively be saved to your Map Dossiers collection by means of the Savebutton:


RAD User Manual


Note: Please refer to the Map Dossier (Section 6.5.5.1) chapter for detailed information on Map Dossiermanagement.

LevelBand

The Levelband serves to specify the Range inside which Entities and all related objects are to be drawn or displayedon the map.

By default, the Range is FL0 > FL700:

Use the mouse pointer to set the Upper and/or Lower slider to the desired value - see how moving up the Lower valueto FL250 impacts the display, the segments out of the selected range being "ghosted":


RAD User Manual


Use the button located on top of the vertical FL scale to toggle between Range and Slice mode:

Timeline

Objects and layers plotted on the Map have a specific timestamp and validity and so may vary in the course of the day,the week, the year, ...

Use the Timeline component to dynamically reflect the changes on the map (showing or hiding objects or entities,changing color, ...).

Selection mode

Three time scales are available, from coarser to finer time resolution: AIRAC, Date and Time:

In AIRAC mode, the available increments are AIRAC numbers:

In Date mode, the available increments are Dates:


RAD User Manual


In (UTC) Time mode, the available increments are block of 60 minutes:

Set target Date - by Calendar

Click on the Calendar icon ...

... then pick the target date from the Date Picker (Date Mode left, AIRAC Mode right):

1. Backward and forward incremental navigation from Year to Year,2. backward and forward incremental navigation from Month to Month,3. Display of the Month and Year of the date currently selected - each providing link to select different Month andYear respectively,

4. Shortcut to select the date of Today,5. The date of Today,6. The Date currently selected,7. AIRAC date,8. Tabs to toggle Mode from/to Date and AIRAC.

Tip: You can also use the following keyboard shortcuts:

Previous Year (keyboard shortcut: Ctrl + Left)

Previous Month (keyboard shortcut: PageUp)

Next Month (keyboard shortcut: PageDown)

Next Year (keyboard shortcut: Ctrl + Right)

Set target Date - By increment

Use the Backward / Forward arrows to move the timeline back or forth by 1 incremental unit (Day in this case).

Set target Date - via the Timeline

Click on the End handle to activate it , keep the mouse button down and move the pointer along the timeline tothe desired location, then release the mouse button:


RAD User Manual


Note: you can alternatively simply click on the desired target location, and the cursor will move accordingly.

Set target Time - by increment

Use the Backward / Forward arrows to move the timeline back or forth by 1 incermental unit (Hour in thiscase).

Set target time - via the Timeline

Click on the End handle to activate it , keep the mouse button down and move the pointer along the timeline tothe desired location, then release the mouse button:

Azimuth

The Azimuth controller provides a widget allowing the definition of the azimuth filter, and is therefore only relevant(and working) for entities which have a direction.

The filter is represented by this compass when no filtering is applied (meaning that directional objects - i.e. routes orsections of routes - are all displayed regardless of their orientation):

When values are set to the filter, only the segments falling in the designated range are highlighted.

Example for Route EBEBU1B:


RAD User Manual


Setting Arc values

Simply click and drag one of the handles and release the mouse button at the desired location(s):

Another quick method to determine a 45° arc will be to clink in the center of the compass, then select one of theproposed eight half-winds:


RAD User Manual


Measuring Tool

This tool allows you to draw straight segments between locations identified by a sequence of left-click selection andcompute both the segments length and the running total length based on the sum of the shortest distances on greatcircle to go from one point to another point, expressed in NM:

Note: Keep the <Ctrl> key down do draw a sequence of segments - and Right-click to delete the measure(s)

Vertical View

The Vertical View tool allows you to draw a straight line along which the vertical definition of the displayed entity willbe displayed in a to dimensional graph:

1. Click on the Vertical View tool button,2. Click on a first (A) point and a second (B) point across the Map to determine the start and end of the referenceline,

3. If need be, move the vertical view graph to have it optimally fit your screen (click and drag), and/orzoom (using the mouse wheel),

4. Set the horizontal and vertical scale of vertical view graph:


RAD User Manual


5. Whenever relevant, move the line along a perpendicular path to reveal the changes in vertical definition:

6. You can also move the start or end point of the line to redraw:


RAD User Manual


7. And at any time, you can click on the Vertical view button again, to hide the vertical view graph and have theMap background return to full size:

Fit to window

Click on the Fit icon ...


RAD User Manual


... to reset all zooming factors in such a way that the profile is displayed in full in the available window space:

Map Legend

The Map Legend tool provides compact access to the meaning of the various icons and symbols you may find on theMap.

6.5.6 Export

The Export function allows you to generate the RAD for a given date range:


RAD User Manual


From the Export accordion (left), select a Start date/AIRAC and/or an End date/AIRAC - and optionally narrow thescope to a specific General Purpose:

The corresponding RAD and their appendices are immediately generated on the fly and available from the RouteAvailability Document (RAD) accordion (right):


RAD User Manual


Note: Please refer to the Using Dates (Section 5.4) section for detailed information on dates and Airacselection.

Then from the list of generated documents , click in the one to download:

Note: How the downloaded files are represented - and where they are located - will dependent on your browsermake and version, and on its settings.The above screenshot was obtained using Chrome 74.


RAD User Manual


7 Help

This section provides brief instructions on how to use the present Help system, using the example of the RADapplication.

Online Help

Links to the Online Help are available from the footer featured at the bottom of each of the NES screens, giving accessto the Help page:

Navigation

The right panel is used to display the page content.

The left panel provides three navigation methods:

A. From the Table of Contents tab, via the Tree Menu:


RAD User Manual


B. From the Index tab:

Enter the (first) letters of the term you want to search for in the Index entries and select the appropriate match fromthe listed results, or simply locate and click on the desired Index entry from the list (sorted alphabetically);


RAD User Manual


C. From the Search tab :

Use the text input field where to enter the words to search for and click on the Search button:

Use the Highlight search terms check box to highlight the matching words:


RAD User Manual


Note: You can combine the words to search using OR and AND to execute a complex query.

Important: Wildcards are not supported - you need to enter the exact match (however case insensitive).

Glossary

Some important terms are highlighted in green and underlined with a dotted line:

Bringing the mouse pointer over such a link, 'NES' in this example, opens a pop-up with the definition as entered in theGlossary.

Simply click on the pop-up - or anywhere in the window - to close it.


RAD User Manual


The whole Glossary page is also directly accessible from the Table of Contents pane:

User Manual PDF

A printer-friendly, fully searchable and navigable PDF version of the comprehensive Online Help is also made availableto you. Remember to make use of the Bookmarks feature of the Adobe Acrobat Reader for easier browsing of thedocument:


RAD User Manual



RAD User Manual


Table of Contents

1. Changes and Updates 1

2. Welcome 2

3. Technical Prerequisites 3

4. Login and Access 4-6

5. Applications - Common Features 7

5.1. Panels and Accordions 7-9

5.2. Browser Windows and Tabs 9

5.3. Sorting Tables and Lists 9-11

5.4. Using Dates 11-14

5.5. Paging 14-15

6. RAD 16

6.1. The RAD Concepts 16-21

6.2. DMR Workflow 21-22

6.3. RAD Grammar 22-23

6.3.1. Normalised Restriction vs RAD Appendices 23-24

6.3.2. Traffic Availability 24

6.3.3. Principle Utilisation Structure 24-25

6.3.4. The Conditioned Flow Tree 25-26

6.3.5. The Conditioned Flow 26-27

6.3.6. The Flow List 27-28

6.3.7. The Single Flow 28-29

6.3.8. List of Entities 29-30

6.3.9. Special Case Except Operator 30-33

6.3.10. Other Special Cases 33-34

6.3.11. RAD Entities 34-35

6.3.12. Type Definitions 35-36

6.3.13. Flight Level Ranges 36-37

6.3.14. Time Applicability 37-38

6.3.15. Logical Date and Time Formats 38-39

6.3.16. Physical Date and Time Formats 39

6.3.17. The Compulsory Problem 39-40

6.4. Screen Layout 40-41

6.5. Using the RAD Application 41

6.5.1. Home 41-43


RAD User Manual


6.5.2. Restrictions 44

6.5.2.1. Search Restrictions 44-46

6.5.2.1.1. Restriction Details 46-48

6.5.2.1.2. Results 48-51

6.5.2.2. Manage Restrictions 51-56

6.5.2.2.1. Attributes 56-57

6.5.2.2.2. Validity 57

6.5.2.2.2.1. Paste From - Copy To Clipboard 57-59

6.5.2.2.2.2. Create From 59-60

6.5.2.2.2.3. Validate 60-61

6.5.2.2.2.4. Compare Validity 62

6.5.2.2.2.5. Copy Validity 62-63

6.5.2.2.2.6. Split Validity 63-64

6.5.2.2.2.7. Delete Validity 64

6.5.2.2.2.8. Add Utilization 65

6.5.2.2.3. Parameters by Type 65-70

6.5.2.2.4. History 70-71

6.5.3. Aerodrome Sets 71-72

6.5.3.1. Search Aerodrome Sets 72-75

6.5.3.1.1. Aerodrome Set Details 75

6.5.3.2. Manage Aerodrome Set 75-79

6.5.4. DMR 79-82

6.5.4.1. DMR Details 82-84

6.5.4.2. Create New DMR 84-87

6.5.4.3. Validation Report 87-89

6.5.5. Map 89-97

6.5.5.1. Map Dossier 97-105

6.5.5.2. Map Controls 105-117

6.5.6. Export 117-119

7. Help 120-125


RAD User Manual


rad user manual · 2020. 8. 11. · applications as delivered in the nes - and as a result,...

Documents