Definition
...
- the current practice in many NOTAM Offices is to issue a single NOTAM containing all route segment closures for a given period of time, such as the next 24 hours. This practice does not strictly comply with the ICAO principle for NOTAM of one subject and one condition per NOTAM. From a Digital NOTAM point of view it is recommended to group in a single Event (and issue one single NOTAM) for all the route segments closures that have a common cause, such as the activation of a given restricted area. In a digital environment, this would facilitate the automatic generation and processing of the Events. This might increase the number of NOTAM messages, but the advantage would be the clarity of the information. For example, this would also enable calculating more precise centre/radius of influence for these NOTAM;
- this scenario does not include the permanent modification of the availability of a route; such events will be dealt with as a separate scenario;
- this scenario does not include the unidirectional closure of a route; such events will be dealt with as a separate scenario;
- the encoding of this event requires the use of the "eASM" extension in order to know the BASELINE CDR status of the route segment concerned.
This will probably need to be replaced with the ADR extension, which declares exactly the same elements, but in the ADR namespace. It is the follow-up of the eASM extension.
Event data
The following diagram identifies the information items that are usually provided by a data originator for this kind of event:
| Code Block | ||||
|---|---|---|---|---|
| ||||
input = "route availability" \n
"route designator" "start point" "end point" {"lower limit" "upper limit"} {"route designator" "start point" "end point" {"lower limit" "upper limit"}} \n
"start time" "end time" ["schedule"] \n
{note}. |
The table below provides more details about each information item contained in the diagram. It also provided the mapping of each information item within the AIXM 5.1 structure. The name of the variable (first column) is recommended for use as label of the data field in human-machine interfaces (HMI).
Data item | value | AIXM mapping |
|---|---|---|
route availability | An explicit indication that the route portion is closed. | RouteSegment/RouteAvailability.status with the list of values CodeRouteAvailabilityType |
route designator | The published designator of the route concerned. This information, in combination with the start/end point is used to identify the route segments concerned. | RouteSegment.routeFormed |
start point | The designator and eventually the type (in the case of a Navaid) of the significant point from where the route availability is affected. This information, in combination with the route designator and the end point is used to identify the route segments concerned. | RouteSegment.start/EnRouteSegmentPoint.pointChoice |
end point | The designator and eventually the type (in the case of a Navaid) of the significant point until where the route availability is affected. This information, in combination with the route designator and the start point is used to identify the route segments concerned. | RouteSegment.end/EnRouteSegmentPoint.pointChoice |
lower limit | The vertical level above which and including that level is affected by the closure. | RouteSegment/RouteAvailability/AirspaceLayer.lowerLimit and lowerLimitReference |
upper limit | The vertical level below which and including that level is affected by the closure. | RouteSegment/RouteAvailability/AirspaceLayer.upperLimit and upperLimitReference |
start time | The effective date & time when the closure starts. This might be further detailed in a "schedule". | RouteSegment/RouteSegmentTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition |
end time | The effective date & time when the closure ends. | RouteSegment/RouteSegmentTimeSlice/TimePeriod.endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for {{Events with estimated end time}} |
schedule | A schedule might be provided in case the closure is only effective according to a regular timetable, within the period between the start time and the end time. | RouteSegment/RouteAvailability/Timesheet/… according to the rules for {{Schedules}} |
note | A free text note that provides further details concerning the route closure, such as reason, alternate routes, etc. | Route/RouteAvailability.annotation with purpose=”REMARK” |
...