Purpose and Scope
Some feature properties may have their own cyclic variation in time according to an established schedule. For example, a navaid can be operational during day time and unserviceable during night time, etc. To model such situations, the concept of “properties with schedule” has been introduced since AIXM version 5.1. It associates the properties that have cyclic varying values with "timesheets” that describes the times when each value is applicable for those attributes. At the feature level, all the properties that change according to the same schedule are located in a separate class, which inherits from an abstract class called “PropertiesWithSchedule”.
| Child pages (Children Display) |
|---|
...
- "daily from 09:00 to 17:00"
- "every Monday and Friday from 13:00 to sunset"
- "every week from MON 07:00 till FRI 17:00, except HOL"
- etc.
AIXM supports the encoding of schedules that contain both:
- repetitive time periods, such as "daily...", "every MON...", "SAT 09:00 - SUN 19:00", etc.
- occasional occurrences, such as "on 1, 2, 15 and 25 of October", "on 1/10 09:00-15:00 and on 3/10 10:00-12:00", etc.
This section describes the most frequently encountered types of schedules used in the aeronautical information domain. Application developers might consider offering HMI templates for such situations, in order to facilitate a correct and harmonised encoding of such common schedules.
Coded value schedules
The following codes are sometimes used in aeronautical information publications and messages in order to indicate the opening hours of a facility or the operating times of a service: H24, HJ, HN, HX, HO, NOTAM
H24: shall be encoded explicitly if the service or facility is explicitly provided H24. How it is exactly encoded might remain a local decision. Recommendation: a single Timesheet with 00:00-24:00 local time (UTC +/-xx hours)
HJ: Meaning: sunrise to sunset. Recommendation: a single Timesheet with only startEvent = 'SR', endEvent = 'SS' and excluded = 'NO'. Any exceptions should be encoded with excluded = 'YES'.
HN: Meaning: sunset to sunrise. Recommendation: a single timesheet with only startEvent = SS, endEvent = SR and excluded = NO. Any exceptions should be encoded with excluded = YES.
HX: Meaning: no specific working hours. Recommendation: A note, propertyName = timeInterval, purpose = WARNING and note = HX (no specific working hours). If limited to a specific time period add timesheets with excluded = NO.
HO: Meaning: service available to meet operational requests. Recommendation: A note, propertyName = timeInterval, purpose = WARNING and note = HO (service available to meet operational requests). If limited to a specific time period add timesheets with excluded = NO.
NOTAM: Meaning: activity periods to be published by NOTAM. Recommendation: A note, propertyName = timeInterval, purpose = WARNING and note = activity periods to be published by NOTAM. If limited to a specific time period add timesheets with excluded = NO.
"Daily" schedules
This applies to schedules that occur every day during the validity period of the data, without distinction between weekdays. However, it is possible to exclude specific dates from the applicable times of the schedule. For example:
- "daily from 09:00 to 17:00"
- "daily from SR+30 min until SS or 18:00, whichever is earliest"
- "daily from 07:00 to 23:00 except for 25 Dec and 1st Jan"
The data elements that are specified for such schedules are indicated in the diagram below:
where Start_Event and End_Event are detailed in the following diagrams:
The graphical elements included in this diagram have the meaning explained in the following table:
Item | Coding | Comments |
|---|---|---|
[TS] and [/TS] | All the elements that appear between [TS] and [/TS] are encoded as a single timesheet | |
start date | Timesheet.startDate | |
end date | Timesheet.endDate | |
start time | Encoded as Timesheet.startTime | |
start event | Encoded as Timesheet.startEvent | |
rel. start | Encoded as Timesheet.startTimeRelativeEvent | Positive values indicate that the actual start time is after the event. |
switch | Encoded as startTimeRelativeEvent | Indicates which one takes precedence between the start/end time and the start/end event (including the eventual time relative to the event) |
end time | Encoded as Timesheet.endTime | |
end event | Encoded as Timesheet.endEvent | |
rel. end | Encoded as Timesheet.sendTimeRelativeEvent | Positive values indicate that the actual end time is after the event. |
note | Encoded as Timesheet.annotation | Examples of such notes: |
excluded date | Encoded as a separate Timesheet with excluded="YES", startDate equal to endDate equal to the "excluded date" value, day='ANY', startTime='00:00' endTime='24:00', timeReference='UTC+/-X' (local time as UTC zone). | |
schedule note | Encoded as Note associated with the class that owns the schedule, with propertyName='timeInterval' and purpose='REMARK'. |
"Weekday" schedules
This applies to schedules that occur with a weekly pattern, during the validity period of the data. It is possible to specify both individual weekdays (MON, TUE, etc.) and weekday ranges (from FRI 17:00 to MON 07:00). It is possible to exclude specific dates or special days (such as holidays) from the applicable times of the schedule. For example:
- "MON, TUE, WED, THU, FRI from 13:00 to sunset; SAT, SUN. from 13:00 to 15:00"
- "SUN, 2300 (2200) to MON, 0500 (0400)"
- "MON to FRI, 09:00 to 17:00, excluding HOL"
The data elements that are specified for such schedules are indicated in the following diagram:
where Start_Event and End_Event are detailed in the following diagrams:
The graphical elements included in this diagram have the meaning explained in the following table:
Item | Coding | Comments |
|---|---|---|
[TS] and [/TS] | All the elements that appear between [TS] and [/TS] are encoded as a single timesheet | |
start date | Timesheet.startDate | |
end date | Timesheet.endDate | |
on weekday | Encoded as Timesheet.day | Any weekday values is allowed, including HOL |
from weekday | Encoded as Timesheet.day | Any weekday values is allowed, including HOL |
to weekday | Encoded as Timesheet.dayTill | Any weekday values is allowed, including HOL |
start time | Encoded as Timesheet.startTime | |
start event | Encoded as Timesheet.startEvent | |
rel. start | Encoded as Timesheet.startTimeRelativeEvent | Positive values indicate that the actual start time is after the event. |
switch | Encoded as startTimeRelativeEvent | Indicates which one takes precedence between the start/end time and the start/end event (including the eventual time relative to the event) |
end time | Encoded as Timesheet.endTime | |
end event | Encoded as Timesheet.endEvent | |
rel. end | Encoded as Timesheet.sendTimeRelativeEvent | Positive values indicate that the actual end time is after the event. |
note | Encoded as Timesheet.annotation | Examples of such notes: |
excluded date | Encoded as a separate Timesheet with excluded="YES", startDate equal to endDate equal to the "excluded date" value, day='ANY', startTime='00:00' endTime='24:00', timeReference='UTC+/-X' (local time as UTC zone). | |
excluded day | Encoded as a separate Timesheet with excluded="YES", day equal to the "excluded day" value, startTime='00:00' endTime='24:00', timeReference='UTC+/-X' (local time as UTC zone). | It does not make sense to use the normal days of the week in this case, only 'HOL', 'BEF_HOL', 'AFT_HOL', 'WORK_DAY', 'BEF_WORK_DAY', 'AFT_WORK_DAY', 'BUSY_FRI' make sense here |
schedule note | Encoded as Note associated with the class that owns the schedule, with propertyName='timeInterval' and purpose='REMARK'. |
...
Examples
Use the following document for examples: AIXM Coding - Schedules - Examples.xlsx
...