| Table of Contents |
|---|
...
The data type or the list of allowable values associated with each Timesheet attribute in a Digital NOTAM encoding are marked in orange in the following diagram:
Schedule data
...
Supported schedules
There are three types of schedules supported for Digital NOTAM Events:
- daily schedules, e.g. "daily from 09:00 to 17:00";
- date based schedules, e.g. "1/10 09:00-15:00 and on 3/10 10:00-12:00"
- weekday based schedules, e.g. "every Monday from 13:00 to sunset".
The information items that may occur in the definition of schedules are identified in the diagrams below. Each of these schedule types is detailed in one diagram.
...
Note that the concept of "weekday ranges" (such as "MON-WED") is also not supported in this specification because it does not have a direct mapping in the current AIXM model for Timesheets and because sometimes there are confusions between MON-FRI and "working days". However, the automatic NOTAM generation rules for item D ensure that a set of consecutive weekdays with a similar start/end time will generate a "weekday range", according to the OPADD recommendations. This does not exclude implementing an HMI that allows the input of weekday ranges, for efficiency reasons. They will have to be converted into individual weekday records in AIXM.
Finally, schedules in the form "from date & time" - "to date & time" (such as "MAR 02 09:00 - 09 16:00") are definitively not supported. This type of schedules do not fit easily in the Timesheet class of AIXM, because the startTime and endTime properties are, by definition, related only to day and/or dayTill. The AIXM definitions could be changed, but that would also change the meaning of the existing schedules, already encoded for AIXM 4.5 static data. Such semantic changes would significantly complicate the mapping between AIXM 4.5 and AIXM 5.1 data sources. It is also highly questionable if such schedules are really needed, as they can easily be seen as individual occurrences of similar Events.
The table below provides more details about each information item shown in the diagrams. It also provides 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).
...
The table below provides more details about each information item shown in the diagrams. It also provides 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 | Description | AIXM mapping |
|---|---|---|
| daily | An indication that the time schedule defined further applies every day. | Timesheet.day with the value "ANY" |
| start time | The time of the day (hour and minute) when the period included in the schedule starts. | Timesheet.startTime |
| start event | An event (like sunset or sunrise), the occurrence of which indicates when the period included in the schedule starts. | Timesheet.startEvent with this list of valuesCodeTimeEventType |
| rel. start | A number of minutes indicating the start of the period included in the schedule, relative to the event. | Timesheet.startTimeRelativeEvent and Timesheet.startEventInterpretation |
| end time | The time of the day (hour and minute) when the period included in the schedule ends. | Timesheet.endTime |
| end event | An event (like sunset or sunrise), the occurrence of which indicates when the period included in the schedule ends. | Timesheet.endEvent with this list of valuesCodeTimeEventType |
| rel. end | A number of minutes indicating the end of the period included in the schedule, relative to the event. | Timesheet.endTimeRelativeEvent and Timesheet.endEventInterpretation |
| on date | A specified date of a month that is included in the schedule, such as 02 FEB, 30 JUN, etc. | Timesheet.startDate and Timesheet.endDate Note that both startDate and endDate get the same value. |
| date range | A series of consecutive days of a year that are included in the schedule, such as 02-15 FEB, 23 MAR - 04 APR, etc. | Timesheet.startDate and Timesheet.endDate |
| on weekday | A specified day of the week that is included in the schedule, such as MON, TUE, etc. | Timesheet.day with this list of valuesCodeDayType |
| from weekday | A day of a week that, combined with a start time or event, indicates the start of the period included in the schedule. For example, "From MON 09:00...", etc. | Timesheet.day with this list of valuesCodeDayType |
| to weekday | A day of a week that, combined with an end time or event, indicates the end of the period included in the schedule. For example, "...till FRI 17:00", etc. | Timesheet.day with this list of valuesCodeDayType |
| exc. date | A specified date of a month that is fully excluded from the schedule. | Timesheet.startDate and Timesheet.endDate;in addition, theTimesheet.excluded shall get the value "YES". Note that both startDate and endDate get the same value (see also further data encoding rules). |
| exc. weekday | A specified day of the week that is fully excluded from the schedule. | Timesheet.day with this list of valuesCodeDayType;in addition, theTimesheet.excluded shall get the value "YES". |
Not supported schedules
Combining different schedule types in a single NOTAM is forbidden. It is considered that such combined schedules could become too complex for being understood and would have a high potential for providing conflicting information. For example, "daily 0900-1700 and each MON 1900-2300" would not have a clear meaning. Is the schedule for Mondays just 1900-2300, or is it both 0900-1700 and 1900-2300? Therefore, such combined schedules are not supported.
Note that the concept of "weekday ranges" (such as "MON-WED") is also not supported in this specification because it does not have a direct mapping in the current AIXM model for Timesheets and because sometimes there are confusions between MON-FRI and "working days". However, the automatic NOTAM generation rules for item D ensure that a set of consecutive weekdays with a similar start/end time will generate a "weekday range", according to the OPADD recommendations. This does not exclude implementing an HMI that allows the input of weekday ranges, for efficiency reasons. They will have to be converted into individual weekday records in AIXM.
Finally, schedules in the form "from date & time" - "to date & time" (such as "MAR 02 09:00 - 09 16:00") are definitively not supported. This type of schedules do not fit easily in the Timesheet class of AIXM, because the startTime and endTime properties are, by definition, related only to day and/or dayTill. The AIXM definitions could be changed, but that would also change the meaning of the existing schedules, already encoded for AIXM 4.5 static data. Such semantic changes would significantly complicate the mapping between AIXM 4.5 and AIXM 5.1 data sources. It is also highly questionable if such schedules are really needed, as they can easily be seen as individual occurrences of similar Events.
HMI recommendations
...
Some schedules may be relatively complex and this may lead to difficulties for the operator when trying to get the global picture of what is being encoded. The purpose of this section is to give some recommendations for the developers of schedule coding interfaces, based on the experience gathered in this area through trials and previous projects.
...