Digital NOTAM Event Specification Digital NOTAM Event Specification

  • Slides: 31
Download presentation
Digital NOTAM – Event Specification

Digital NOTAM – Event Specification

Digital NOTAM Event Specification Content Introduction General requirements AIXM Event Schema Event Scenarios Data

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 Developed by Focus Group • NOTAM operators • NOTAM users (airlines, ATC, service provider, etc. ) • Eurocontrol & FAA Version 1. 0 • Released June 2011

Digital NOTAM Event Specification - Purpose Event data Target: application developers ! Restricted area

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: 560028 N 0111656 E - 560643 N 0111026 E - 561500 N 0112400 E 561500 N 0113600 E -560112 N 0114736 E - 555730 N 0113830 E - 560028 N 0111656 E. between SFC and 60000 FT AMSL RELEVANT ATS UNITS REF. AIP DENMARK ENR 5. 1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN Rules Data encoding rules Data validation rules Digital NOTAM AIXM 5. 1 encoded data output NOTAM production rules Text NOTAM ICAO Format (Snnnn/yy NOTAMN Q) EKDK/QRRCA/IV/BO /W /000/600/5606 N 01130 E 012 A) EKDK B) 0711010800 C) 0711011100 E) TEMPORARY RESTRICTED AREA ESTABLISHED AS FOLLOWS (NORTH OF SJAELLANDS ODDE): 560028 N 0111656 E - 560643 N 0111026 E - 561500 N 0112400 E 561500 N 0113600 E -560112 N 0114736 E - 555730 N 0113830 E -

Scenario definition - example

Scenario definition - example

Examples • Restricted area North of Sjaellands Odde TEMPORARY RESTRICTED AREA IS ESTABLISHED daily

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: 560028 N 0111656 E - 560643 N 0111026 E - 561500 N 0112400 E 561500 N 0113600 E -560112 N 0114736 E - 555730 N 0113830 E 560028 N 0111656 E. between SFC and 60000 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 1430 2 NM AROUND 4952 N 00737 E PFERDSFELD 10 NM E KIRN VOR KIR between GND and 6000 FT AMSL

Event data possibly End possibly, more possibly

Event data possibly End possibly, more possibly

Event data – mapped with example type Restricted Area designator (optional) name (optional) start

Event data – mapped with example type Restricted Area designator (optional) name (optional) start time 07 NOV 08: 00 end time (optional) 17 NOV 17: 00 schedule (optional) Daily 08: 00 -17: 00 horizontal limits 560028 N 0111656 E - 560643 N 0111026 E – 561500 N 0112400 E - 561500 N 0113600 E – 560112 N 0114736 E - 555730 N 0113830 E – 560028 N 0111656 E controlling unit note (optional) Relevant ATS units ref. AIP Denmark ENR 5. 1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN excluded airspace (optional) activity (optional) location note (optional) North of Sjaellands Odde lower limit SFC upper limit 6000 FT AMSL note (optional) TEMPORARY RESTRICTED AREA IS ESTABLISHED daily from 08: 00 -17: 00 between 07 NOV and 17 NOV AS FOLLOWS NORTH OF SJAELLANDS ODDE: 560028 N 0111656 E - 560643 N 0111026 E - 561500 N 0112400 E - 561500 N 0113600 E -560112 N 0114736 E - 555730 N 0113830 E - 560028 N 0111656 E. between SFC and 60000 FT AMSL RELEVANT ATS UNITS REF. AIP DENMARK ENR 5. 1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN.

AIXM Mapping FLOOR - CEILLING

AIXM Mapping FLOOR - CEILLING

Rules – data encoding Identifier Data encoding rule ER-01 The special activity area shall

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 Time. Slices shall be created; and a new Airspace, for which PERMDELTA and subsequent BASELINE Time. Slices shall be created; the property "event: the. Event" of the Airspace Time. Slices shall refer to the Event mentioned above. ER-02 The Airspace BASELINE shall contain one Airspace. Activation object with status=ACTIVE, IN_USE or INTERMITTENT (as appropriate) which shall also include the "activity" data and the values "FLOOR, uom=OTHER" for lower. Limit and "CEILING, uom=OTHER" for the upper. Limit of the associated Airspace. Layer. 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 time. Interval/Timesheet properties for the Airspace. Activation 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 Airspace. Activation 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 Airspace. Geometry. Component with operation=SUBTR, operation. Sequence as dictated by the order of the element, contributor. Airspace/Airspace. Volume. Dependency. 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 Airspace. Volume(s) of the controbutor. Airspace (lower. Limit, lower. Limit. Reference, upper. Limit. Reference, horizontal. Projection, etc. ) shall be copied in the Airspace. Volume(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. The activity types that do not match a pre-defined value in the Code. Airspace. Activity. Type 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

Rules – event schedules encoding

Rules – event schedules encoding

OPADD - Item D • If the first period of activity starts on 062300

OPADD - Item D • If the first period of activity starts on 062300 and ends on 070500 and a series of subsequent 2300 -0500 periods starts on 102300 and ends on 150500: D) 06 AND 10 -14 2300 -0500 • If the activity times in the series differ and the first period (2300 -0500) starts on 062300 and ends on 100500 and the final period (2200 -0600) starts on 102200 and ends on 110600: D) 06 -09 2300 -0500 AND 10 2200 -0600 NAV 32517. 4. 3938 Copyright 2005 EUROCONTROL 11

Rules – data encoding ER-08 It is recommended that an alphanumeric designator is allocated

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

Digital NOTAM – AIXM 5. 1 encoding

Digital NOTAM – AIXM 5. 1 encoding

NOTAM production – Q code

NOTAM production – Q code

NOTAM production – E field

NOTAM production – E field

NOTAM production – item D • Abbreviate Months as: JAN FEB MAR APR MAY

NOTAM production – item D • Abbreviate Months as: JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC • and Days as: • Use ‘AND’ before last date: D) APR 04 06 08 AND 11 • or before last times: D) MAR 04 0600 -0800 AND 1000 -1200 • Use - not /: D) 0700 -1000 • and link continuous period: D) WED 1900 -FRI 0600 • or when using SR & SS: • If activity spans ‘midnight’ UTC, use the following format …. . / MON TUE WED THU FRI SAT SUN D) SR MINUS 30 -SS PLUS 30 NAV 32517. 4. 3938 Copyright 2005 EUROCONTROL 16

Resulting NOTAM (Snnnn/yy NOTAMN Q) EKDK/QRRCA/IV/BO /W /000/600/5606 N 01130 E 012 A) EKDK

Resulting NOTAM (Snnnn/yy NOTAMN Q) EKDK/QRRCA/IV/BO /W /000/600/5606 N 01130 E 012 A) EKDK B) 0711010800 C) 0711011100 D) DAILY 0800 -1700 E) TEMPORARY RESTRICTED AREA ESTABLISHED (NORTH OF SJAELLANDS ODDE) AS FOLLOWS : 560028 N 0111656 E - 560643 N 0111026 E - 561500 N 0112400 E 561500 N 0113600 E -560112 N 0114736 E - 555730 N 0113830 E 560028 N 0111656 E. RELEVANT ATS UNITS REF. AIP DENMARK ENR 5. 1 ITEM 3: AARHUS APP/TWR, ACC KOEBENHAVN. F) SFC G) 60000 FT AMSL)

Obstacles

Obstacles

Scenario definition • “establishment of a new temporary or permanent obstacle” • Includes •

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

Examples • Temporary crane at the airport Construction crane at ETAR From 01 OCT

Examples • Temporary crane at the airport Construction crane at ETAR From 01 OCT 2007 05: 31 till 30 OCT 2007 18: 26. PSN 492623 N 0073604 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 2007 04: 30 till 09 OCT 2007 14: 29, daily 04: 30 -14: 29. Position: 513759 N 0072024 E with elevation 675 FT/483 FT GND. ICAO marked. • Mobile obstacle: Boat From 01 AUG 2007 20: 00 till 15 AUG 2007 04: 00 as follows: daily 20: 00 till next day 04: 00. Floating south of AD between 200 m to 1, 5 NM from Mike Helistop. height: 42 M. Night marked.

Event data possibly alternatives possibly End possibly, more

Event data possibly alternatives possibly End possibly, more

AIXM Mapping

AIXM Mapping

AIXM Mapping

AIXM Mapping

Prerequisites: assumptions for baseline (static) data • It is assumed that the Area 2

Prerequisites: assumptions for baseline (static) data • It is assumed that the Area 2 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

Rules – data encoding

Rules – data encoding

Rules – automatic validation

Rules – automatic validation

Automatic NOTAM creation Temporary crane at the airport Construction crane at ETAR From 01

Automatic NOTAM creation Temporary crane at the airport Construction crane at ETAR From 01 OCT 2007 05: 31 till 30 OCT 2007 18: 26 PSN 492623 N 0073604 E (500 FT South of Control Tower) Maximum height 858 FT MSL / 85 FT GND. Night marked Automatic NOTAM Generation (P 4246/07 NOTAMR P 2786/07 Q) EDGG/QOBCE/IV/M /A /000/999/4926 N 00736 E 005 A) ETAR B) 0710010531 C) 0710301826 E) CONSTRUCTION CRANE 500 FT SOUTH OF CONTROL TOWER AT PSN 492623 N 0073604 E. MAX HEIGHT 858 FT MSL / 85 FT GND. NIGHT MARKED. )

NOTAM production rules – E field

NOTAM production rules – E field

Resulting NOTAM (Snnnn/yy NOTAMN Q) EDGG/QOBCE/IV/M /A /000/999/4926 N 00736 E 005 A) ETAR

Resulting NOTAM (Snnnn/yy NOTAMN Q) EDGG/QOBCE/IV/M /A /000/999/4926 N 00736 E 005 A) ETAR B) 0710010531 C) 0710301826 E) TEMPORARY CRANE AT ETAR 492623 N 0073604 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. )

Event Specification - summary • Identify categories of events • temporary obstacle at the

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

Questions?

Questions?