Digital AIM Training - Digital NOTAM

Digital AIM Training - Digital NOTAM
EUROCONTROL Copyright 2011

Digital NOTAM Event Specification
Digital AIM Training - Digital NOTAM Digital NOTAM Event Specification Content Introduction General requirements AIXM Event Schema Event Scenarios Data encoding rules Digital NOTAM Services Annex 1 - EBNF sources Annex 2 - XML Examples Version 1.0 Released June 2011 Developed by Focus Group NOTAM operators NOTAM users (airlines, ATC, service provider, etc.) Eurocontrol & FAA Identify categories of events temporary obstacle at the airport ad-hoc restricted area etc. For each type of event, specify: the data usually provided the data encoding rules including AIXM mapping the data validation rules the conversion rules into text NOTAM (ICAO format) Examples Notes: EUROCONTROL Copyright 2011

Digital NOTAM Event Specification - Purpose
Digital AIM Training - Digital NOTAM Digital NOTAM Event Specification - Purpose Event data Target: application developers ! Restricted area North of Sjaellands Odde TEMPORARY RESTRICTED AREA IS ESTABLISHED daily from 08:00-17:00 between 07 NOV and 17 NOV AS FOLLOWS NORTH OF SJAELLANDS ODDE: N E N E N E N E N E N E N E. between SFC and FT AMSL RELEVANT ATS UNITS REF. AIP DENMARK ENR 5.1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN Rules Rules Rules Data encoding rules Data validation rules NOTAM production rules Digital NOTAM AIXM 5.1 encoded data output Text NOTAM ICAO Format (Snnnn/yy NOTAMN Q) EKDK/QRRCA/IV/BO /W /000/600/5606N01130E012 A) EKDK B) C) E) TEMPORARY RESTRICTED AREA ESTABLISHED AS FOLLOWS (NORTH OF SJAELLANDS ODDE): 560028N E N E N E - 561500N E N E N E - 560028N E. RELEVANT ATS UNITS REF. AIP DENMARK ENR 5.1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN. DANGER AREA WITHIN THE PORTION OF AIRSPACE OVER THE HIGH SEA. F) SFC G) 60000FT AMSL) EUROCONTROL Copyright 2011

Scenario definition - example
Digital AIM Training - Digital NOTAM Scenario definition - example In this example, we will study the rules for the encoding of a Digital NOTAM that announces the “establishment of a new restricted, dangerous, prohibited, etc. area or navigation warning, which did not exist as a published airspace” (scenario definitions). This is defined in section 4.4 of the Digital NOTAM Event Specification (version 1.0) "special activity area" = P, D, R and similar does not include the establishment of temporary ATS airspace (see the dedicated scenario) creation of permanent D or R area by NOTAM shall be an exceptional situation (supported, since same data is required) does not cover mobile airspace reservations Notes: EUROCONTROL Copyright 2011

Examples Restricted area North of Sjaellands Odde TEMPORARY RESTRICTED AREA IS ESTABLISHED daily from 08:00-17:00 between 07 NOV and 17 NOV AS FOLLOWS NORTH OF SJAELLANDS ODDE: N E N E N E N E N E N E N E. between SFC and FT AMSL RELEVANT ATS UNITS REF. AIP DENMARK ENR 5.1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN Aerobatics at Pferdsfeld AEROBATICS VMC on 07 OCT from 1330 till NM AROUND 4952N 00737E PFERDSFELD 10NM E KIRN VOR KIR between GND and 6000FT AMSL By analysing examples, we have identified the data that is provided by the originator for this scenario. Notes: EUROCONTROL Copyright 2011

Event data possibly possibly possibly possibly possibly End possibly possibly, more This following diagram identifies the information items that are usually provided by a data originator for this kind of event. Notes: EUROCONTROL Copyright 2011

Event data – mapped with example type Restricted Area designator (optional) name (optional) activity (optional) location note (optional) North of Sjaellands Odde start time 07 NOV 08:00 end time (optional) 17 NOV 17:00 schedule (optional) Daily 08:00-17:00 horizontal limits 560028N E N E – 561500N E N E – 560112N E N E – 560028N E excluded airspace (optional) lower limit SFC upper limit 6000 FT AMSL excluded airspace (optional) excluded airspace (optional) controlling unit note (optional) Relevant ATS units ref. AIP Denmark ENR 5.1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN note (optional) A very simplistic data encoding interface for this type of digital NOTAM could have the entry fields shown on this slide. Notes: TEMPORARY RESTRICTED AREA IS ESTABLISHED daily from 08:00-17:00 between 07 NOV and 17 NOV AS FOLLOWS NORTH OF SJAELLANDS ODDE: 560028N E N E N E N E N E N E N E. between SFC and FT AMSL RELEVANT ATS UNITS REF. AIP DENMARK ENR 5.1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN. EUROCONTROL Copyright 2011

Rules – data encoding Identifier Data encoding rule ER-01 The special activity area shall be encoded as: a new Event, for which PERMDELTA and subsequent BASELINE TimeSlices shall be created; and a new Airspace, for which PERMDELTA and subsequent BASELINE TimeSlices shall be created; the property "event:theEvent" of the Airspace TimeSlices shall refer to the Event mentioned above. ER-02 The Airspace BASELINE shall contain one AirspaceActivation object with status=ACTIVE, IN_USE or INTERMITTENT (as appropriate) which shall also include the "activity" data and the values "FLOOR, uom=OTHER" for lowerLimit and "CEILING, uom=OTHER" for the upperLimit of the associated AirspaceLayer. ER-03 If the area activity is limited to a discrete schedule within the overall time period between the "start time" and the "end time", then this shall be encoded using as many as necessary timeInterval/Timesheet properties for the AirspaceActivation with status ACTIVE/IN_USE/INTERMITTENT of the BASELINE Timeslice. See also the rules for Event Schedules. ER-04 If a schedule is provided, then the Airspace BASELINE shall contain a second AirspaceActivation object with status=INACTIVE, which shall explicitly specify the times not covered by the activity schedule. This shall be done automatically by the system and should not be visible to the operator. The "INACTIVE" times shall not be translated into NOTAM text. See also the rules for Event Schedules. ER-05 If one or more "exclude airspace" are specified, each shall be encoded as an AirspaceGeometryComponent with operation=SUBTR, operationSequence as dictated by the order of the element, contributorAirspace/AirspaceVolumeDependency.dependency=FULL_GEOMETRY and pointing to the airspace concerned. In addition, when the AIXM 5.1 encoded data is provided to a client, the data corresponding to the AirspaceVolume(s) of the controbutorAirspace (lowerLimit, lowerLimitReference, upperLimit, upperLimitReference, horizontalProjection, etc.) shall be copied in the AirspaceVolume(s) of the current Airspace. This will provide a complete description of the current Airspace, eliminating the need to traverse the xlink:href in order to get the full geometrical information. ER-06 The activity types that do not match a pre-defined value in the CodeAirspaceActivityType shall be encoded as follows: captive balloon -> activity=OTHER:CAPTIVE_BALLOON kite activities -> activity=OTHER:KITE demolition using explosive devices -> activity=OTHER:DEMOLITION mass movement of aircraft ->activity=OTHER:ACFT_MASS_MOVEMENT flying in formation -> activity=OTHER:ACFT_FORMATION aerial survey/photogrammetric flights -> activity=OTHER:AERIAL_SURVEY model flying -> OTHER:MODEL airborne spread of diseases -> activity=OTHER:BIO_HAZARD industrial action -> activity=OTHER:STRIKE volcanic activity, possibly indication imminent eruption -> activity=OTHER:VOLCANO_ACTIVE confirmed volcanic eruption -> activity=OTHER:VOLCANO_ERUPTION volcanic ash area of high contamination -> activity=OTHER:ASH_HIGH volcanic ash area of medium contamination -> activity=OTHER:ASH_MEDIUM volcanic ash area of low contamination -> activity=OTHER:ASH_LOW unspecified hazard -> activity=OTHER The specification provides very precise date encoding rules. These need to be considered by software developers. The system should support the operator in complying with these rules. It is not necessary for an operator to learn such rules by heart. Just to be aware of their existance, so that she/he is not take by surprise by the behaviour of the application. Example: “If the area activity is limited to a discrete schedule within the overall time period between the "start time" and the "end time", then this shall be encoded using as many as necessary timeInterval/Timesheet properties for the AirspaceActivation with status ACTIVE/IN_USE/INTERMITTENT of the BASELINE Timeslice. See also the rules for Event Schedules.” Notes: EUROCONTROL Copyright 2011

Rules – event schedules encoding
Digital AIM Training - Digital NOTAM Rules – event schedules encoding The specification supports a limited number of schedule types. These are based on: Real NOTAM examples The limitations set in the OPADD document (will be explained on the next slide) Notes: EUROCONTROL Copyright 2011

OPADD - Item D If the first period of activity starts on and ends on and a series of subsequent periods starts on and ends on : D) 06 AND If the activity times in the series differ and the first period ( ) starts on and ends on and the final period ( ) starts on and ends on : D) AND Some examples of rules specified in the OPADD. Notes: NAV Copyright 2005 EUROCONTROL 11 EUROCONTROL Copyright 2011 11

Rules – data encoding ER-08 It is recommended that an alphanumeric designator is allocated to a temporary area, in order to facilitate it's identification on graphical representations (such as airspace activity maps) and verbal communication. The composition rule is derived from the ICAO Annex 15 rules for P, D, R area designators: CCLnnnn-yy, where: • CC is the Country Code; this could be expanded into a full FIR identifier if necessary to have a finer granularity of the airspace reference; • L is a letter that corresponds to the area type; • nnnn is a number, unduplicated during the same year, within the State or territory concerned; this could also be the NOTAM number; • yy are the last two digits of the year date when the area becomes effective Coming back to the encoding rules for our event, one particular rules recommends creating a designator for every ad-hoc areas created by NOTAM, even temporary. Notes: EUROCONTROL Copyright 2011

Digital NOTAM – AIXM 5.1 encoding
Digital AIM Training - Digital NOTAM Digital NOTAM – AIXM 5.1 encoding Applying these encoding rules results in the encoding of an AIXM-XML message, which is practically the Digital NOTAM. Notes: EUROCONTROL Copyright 2011

NOTAM production – Q code
Digital AIM Training - Digital NOTAM NOTAM production – Q code The NOTAM text will now be automatically generated from the Digital NOTAM. This is done by the application. At the end, the NOTAM shall be presented to the operator for a final check and approval. This also concerns the Q line: depending on the type of area and the activity, a certain Q code is automatically allocated by the application, aplying rules defined in the event specification for the relevant scenario. Notes: EUROCONTROL Copyright 2011

NOTAM production – E field
Digital AIM Training - Digital NOTAM NOTAM production – E field A production rules is also provided for item E. The numbers on this diagram contain references to more detailed rules, such as: If BL.validTime.TimePeriod.endPosition is NIL and has the value "unknown" (the area is permanent), then insert the word "PERMANENT". Otherwise insert the word "TEMPORARY". The area type shall be included according to the following decoding table:BL.type Text recommended for item EP "PROHIBITED AREA"R "RESTRICTED AREA"D "DANGER AREA"D-OTHER "(WARNING) AREA"TSA "SEGREGATED AREA"TRA "RESERVED AREA"W "WARNING AREA"A "ALERT AREA"PROTECT "PROTECTION AREA"OTHER "AREA“ Notes: EUROCONTROL Copyright 2011

NOTAM production – item D Abbreviate Months as: JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC and Days as: MON TUE WED THU FRI SAT SUN Use ‘AND’ before last date: D) APR AND 11 or before last times: D) MAR AND Use - not /: D) and link continuous period: D) WED 1900-FRI 0600 or when using SR & SS: D) SR MINUS30-SS PLUS30 If activity spans ‘midnight’ UTC, use the following format ….. / Again, rules specified in the OPADD are included. These rules are applied in the automatic creation of the NOTAM text from the digital encoding. Notes: NAV Copyright 2005 EUROCONTROL 16 EUROCONTROL Copyright 2011 16

Resulting NOTAM (Snnnn/yy NOTAMN Q) EKDK/QRRCA/IV/BO /W /000/600/5606N01130E012 A) EKDK B) C) D) DAILY E) TEMPORARY RESTRICTED AREA ESTABLISHED (NORTH OF SJAELLANDS ODDE) AS FOLLOWS : 560028N E N E N E - 561500N E N E N E - 560028N E. RELEVANT ATS UNITS REF. AIP DENMARK ENR 5.1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN. F) SFC G) 60000FT AMSL) The NOTAM text automatically generated is shown in this slide. Note that the automatic generation of the NOTAM text will result in a visible standardisation of the NOTAM messages issued by different countries. Notes: EUROCONTROL Copyright 2011

Scenario definition “establishment of a new temporary or permanent obstacle” Includes Obstacles defined by point / line / polygon Mobile obstacles Group of similar objects located closely Airport and en-route obstacles Not covered in this scenario Obstacles composed of multiple parts Obstacles with variable elevations Only one elevation value can be provided Notes: EUROCONTROL Copyright 2011

Examples Temporary crane at the airport Construction crane at ETAR From 01 OCT :31 till 30 OCT :26. PSN N E (500 FT South of Control Tower). Maximum height 858 FT MSL / 85 FT GND. Night marked. Crane with schedule in FIR High crane erected within EDGG FIR From 01 OCT :30 till 09 OCT :29, daily 04:30-14:29. Position: N E with elevation 675FT/483FT GND. ICAO marked. Mobile obstacle Mobile obstacle: Boat From 01 AUG :00 till 15 AUG :00 as follows: daily 20:00 till next day 04:00. Floating south of AD between 200m to 1,5NM from Mike Helistop. height: 42M. Night marked. Notes: EUROCONTROL Copyright 2011

Event data possibly alternatives possibly alternatives possibly Group - An indication whether the obstacle consists of a number of closely situated similar objects, for a simple lat/long position (and eventually radius) is provided. Mobile - An indication whether the obstacle is expected to move around its nominal location Type - A type of vertical structure Description - A textual description of the obstacle, such as the number of similar items for a group, etc. Airport - Information such as designator or name used to identify the airport where the obstacle is located Location - A named geographical location where or close to which the obstacle is located (especially for Area 1 obstacles) Identifier - An alphanumerical designator by which the obstacle is identified in the national obstacle Position - The latitude, longitude and horizontal reference datum associated with the obstacle position. linear extent - Pairs of latitude/longitude values along a line, including the horizontal reference datum associated with the obstacle extent and location surface extent - Pairs of latitude/longitude values defining a polygon, including the horizontal reference datum associated with the obstacle extent and location Elevation - The elevation (distance from Mean See Level) at the top of the obstacle. Height - The distance between the uppermost and the lowermost parts of the obstacle. relative position - A free text description of the obstacle position in relation to relevant airport elements, such as a runway threshold or the control tower. Lighted - An indication if the obstacle is lighted. marking description - Further details of the obstacle lighting, such as times when lighting is available, compliance with the ICAO standards, etc. Also includes the description of visual markers (other than lights) that are installed on the obstacle, such as painting, flags, signs, etc. Note - A free text note that provides further details about the obstacle, such as the reason for which it exists, reduced hight at certain times, etc. Notes: End possibly, more EUROCONTROL Copyright 2011

AIXM Mapping The encoding of this information requires the “Vertical Structure” part of the AIXM model to be used. You see on this diagram the main components of this model. You see that a VerticalStructure can be composed of multiple parts. For example, if the obstacle is a transmission line, you could model the geometry/extent of each individual cable and pole. But this possibility is not used by this scenario, where a single geometry is allowed for the whole obstacle. If it is considered necessary to also offer the possibility to encode obstacles with complex geometries in Digital NOTAM, then a separate scenario will have to be created for such situations. Notes: EUROCONTROL Copyright 2011

AIXM Mapping A detailed mapping is then provided in the scenario definition. Each data item is defined together with its location to the AIXM model. Some of the information provided by the originator is captured as text notes, not as structured data. For example: If a description is provided, this is mapped as a Note associated with the obstacle type and having purpose=Description If the data originator specifies at which airport the obstacle is located, this is captured as a note with purpose=Warning. This information provided by the originator is not used to automatically relate the obstacle to an airport. The obstacle position (lat/long) will be used to automatically detect the airports for which the obstacle is situated in Area 2 Notes: EUROCONTROL Copyright 2011

Prerequisites: assumptions for baseline (static) data
Digital AIM Training - Digital NOTAM Prerequisites: assumptions for baseline (static) data It is assumed that the Area is available as BASELINE data for all airports that have an ICAO location designator and which are situated in the area of responsibility of the data provider In order for the digital encoding to be possible, there are some pre-requisites for static data availability. These are captured as “assumptions” in the scenario. In this case, the only important assumption is that the Area 2 geometries are available as baseline data, as they will be used to automatically detect the location of the obstacle in relation with existing airports. Notes: EUROCONTROL Copyright 2011

Rules – data encoding The details of the AIXM encoding, starting from the data provided by the originator, are captured as “data encoding rules”. For example, in this situation: In this case, as the information concerns a new obstacle, a Baseline will be crated for it. This is also true in the case of a temporary obstacle! The only difference from normal Baselines will be that the end of life is already known or at least estimated. A second rule requires a special treatment for obstacles that consist of a group of similar objects, situated close to each other. If such a group is situated in Area 2 of an airport, it is requested that the position of the group is provided as a polygon! This is necessary in order to met the end user requirements for precise obstacle data in the airport area, which can have a significant impact on performance calculations for the airlines. EUROCONTROL Copyright 2011

Rules – automatic validation
Digital AIM Training - Digital NOTAM Rules – automatic validation Some of the data encoding rules can be automatically checked once the data is encoded. As for the other scenarios, there is a minimal data availability rule, which says that the type of the obstacle is mandatory, together with information about the obstacle lighting. The only other rules identified for the Obstacle scenario until now concern the obligation to provide an explicit position (latitude and longitude)! It is not considered sufficient to provide a relative position (“such as 600 m east of runway THR”) because such values are typically rough estimates and do not satisfy the needs of the end users, in particular airlines. Notes: EUROCONTROL Copyright 2011

Automatic NOTAM creation
Digital AIM Training - Digital NOTAM Automatic NOTAM creation Temporary crane at the airport Construction crane at ETAR From 01 OCT :31 till 30 OCT :26 PSN N E (500 FT South of Control Tower) Maximum height 858 FT MSL / 85 FT GND. Night marked Automatic NOTAM Generation With the data encoding rules and data validation rules, we are able to encode the information and export it as a Digital NOTAM in AIXM 5.1 / XML format. This can be used by the end users who have the capability to read digital AIXM 5.1 data. For the legacy users, we also need to produce the classical ICAO NOTAM message. This is done in accordance with the rules for the production of text NOTAM, which is the last part of the scenario definitions. Notes: (P4246/07 NOTAMR P2786/07 Q) EDGG/QOBCE/IV/M /A /000/999/4926N00736E005 A) ETAR B) C) E) CONSTRUCTION CRANE 500 FT SOUTH OF CONTROL TOWER AT PSN 492623N E. MAX HEIGHT 858 FT MSL / 85 FT GND. NIGHT MARKED.) EUROCONTROL Copyright 2011

NOTAM production rules – E field
Digital AIM Training - Digital NOTAM NOTAM production rules – E field This diagram presents the NOTAM production rules, using AIXM terms (such as BL.type, which means the “type” property of the VerticalStructure baseline). The numbers designate particular rules, such as: Either the word “TEMPORARY” or the word “PERMANENT” shall be inserted, depending on the end of life of the obstacle; If it is a group, then insert the word “GROUP OF” etc. As for the other scenario, these rules ensure that all NOTAM of this kind, in particular the E item, are generated with exactly the same structure and words, as demonstrated on the next slide. Notes: EUROCONTROL Copyright 2011

Resulting NOTAM (Snnnn/yy NOTAMN Q) EDGG/QOBCE/IV/M /A /000/999/4926N00736E005 A) ETAR B) C) E) TEMPORARY CRANE AT ETAR 492623N E ELEVATION 858 FT MSL (HEIGHT 85 FT GND) 500 FT SOUTH OF CONTROL TOWER. LIGHTED. THE HEIGHT IS A MAXIMUM VALUE. LIGHTED ONLY AT NIGHT.) The E field is constructed automatically, following the pattern: Temporary/Permanent – type – airport (warning note) – position – elevation – height – relative location – lighted – other notes. Note that the obstacle being a crane, it is probably a mobile obstacle situated at an airport. Therefore, ideally, this should be encoded with as a surface, not as a single lat/long position! Notes: EUROCONTROL Copyright 2011

Event Specification - summary
Digital AIM Training - Digital NOTAM Event Specification - summary Identify categories of events temporary obstacle at the airport ad-hoc restricted area etc. For each type of event, specify: the data usually provided the data encoding rules including AIXM mapping the data validation rules the conversion rules into text NOTAM (ICAO format) Examples Version 1.0 available. Version 2.0 scheduled for end 2012. Notes: EUROCONTROL Copyright 2011

Digital AIM Training - Digital NOTAM

Similar presentations

Presentation on theme: "Digital AIM Training - Digital NOTAM"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Digital AIM Training - Digital NOTAM

Similar presentations

Presentation on theme: "Digital AIM Training - Digital NOTAM"— Presentation transcript:

Similar presentations

About project

Feedback