...
Note that the concept of "weekday ranges" (such as "MON-WED") is also not supported in this specification. 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.
Also not supported are schedules that use both startTime and StartEvent or both endTime and endEvent, such as "SR or 07:00, whichever is earliest". Such schedules are sometimes encountered for static data, as they need to cover longer time periods. It is not justified to use such combinations in a NOTAM schedule.
In addition, according to the OPADD, item D is not allowed to exceed 200 characters. The application interface should check the length of the item D that results from the schedule encoding and invite the operator to split the NOTAM into two separate events in case this limit is exceeded. The HMI should allow copying a draft event into a second draft event.
...
| Identifier | Data encoding rule | Remarks (column to be deleted at the end) |
|---|---|---|
| TSH.EVT-01 | Any Timesheet that is part of a TimeSlice associated with an Event that isNotifiedBy NOTAM shall have timeReference='UTC' | In NOTAM is mandatory to use UTC times only. |
| TSH.EVT-02 | Any Timesheet that is part of a TimeSlice associated with an Event that isNotifiedBy NOTAM shall have daylightSavingAdjust='NO' | In NOTAM it is not allowed to use auto-adjusted summer time values. |
| TSH.EVT-03 | Any Timesheet that is part of a TimeSlice associated with an Event that isNotifiedBy NOTAM and that has assigned values for startDate and endDate, must have day equal-to 'ANY'. | In NOTAM it is not possible to mix date ranges with week days. |
| TSH.EVT-04 | Any Timesheet that is part of a TimeSlice associated with an Event that isNotifiedBy NOTAM cannot use 'WORK_DAY', 'BEF_WORK_DAY', 'AFT_WORK_DAY', 'HOL', 'BEF_HOL', 'AFT_HOL' and 'BUSY_FRI' as day or dayTill values. | HOL and similar are not allowed in NOTAM schedules |
| ||
| new | The startTimeRelativeEvent@uom cannot be other-than 'MIN' | proposed by Indra/Avitech, based on OPADD 4.1, section 2.3.20.2 |
| new | The endTimeRelativeEvent@uom cannot be other-than 'MIN' | proposed by Indra/Avitech, based on OPADD 4.1, section 2.3.20.2 |
| new | The startTimeRelativeEvent value cannot be higher-than 99 | proposed by Indra/Avitech, based on OPADD 4.1, section 2.3.20.2 |
| new | The endTimeRelativeEvent value cannot be higher-than 99 | proposed by Indra/Avitech, based on OPADD 4.1, section 2.3.20.2 |
| new | It is not allowed to have both startTime and startEvent in the same Timesheet | following comments made in the decoding scenarios |
| new | It is not allowed to have both endTime and endEvent in the same Timesheet | following comments made in the decoding scenarios |