Production rule - Weekdays

If there are multiple Timesheet (i.e. multiple time periods included in the schedule), then the following algorithm is proposed:

• first, order by TS.day
• then, for each group of consecutive Timesheet that have the same TS.day value order by TS.startTime or TS.startEvent (whichever is present). Note: see the recommendations provided in rule (7) of the Production rule - Daily with regard to ordering Timesheets by startTime and startEvent)
• then, for each Timesheet apply the rules described in the following lines of this table.

Use this branch when:

• TS.dayTil does not have a value, or
• TS.dayTil has the value of the next week day after TS.day and TS.endTime has the value '00:00' (the convention for end of day was applied in the coding).

Otherwise use the alternate branch.

If TS.startTime has a value then use this path. Otherwise, if TS.startEvent has a value, then use the alternate path.

Format the data contained in TS.startTime according to NOTAM syntax for this item: hhmm.

Decode this value as follows: 'SR' → "SR", 'SS' → "SS"

If TS.endTime has a value then use this path. Otherwise, if TS.endEvent has a value, then use the alternate path.

Format the data contained in TS.endTime according to NOTAM syntax for this item: hhmm.

If TS.endTime is '00:00', then the value “2359” shall be used as hhmm group in the NOTAM (the convention for end of day was applied in the coding).

The algorithm proposed above could still result into consecutive week days in item D that have the same time periods. That's because the ordering/grouping of the Timesheet is done only by similar day/dayTil. For example, this could result into the following: "D) MON 0700-0900 1300-1400 TUE 0700-0900 1300-1400 WED 0700-0900 1300-1400 THU 0600-1500". Based on the current NOTAM practice, the first three week day/time groups should be collapsed into a single week-day range, because they have the same times: "D) MON-WED 0700-0900 1300-1400 THU 0600-1500". 

This streamlining of the resulting schedule text could be done at the end of the text generation process or directly in the production rule, with a more sophisticated algorithm. The resolution of this issue is left for the implementers.

If there are any timesheets containing TS.excluded elements with the value 'YES', denoting a schedule with exceptions, select all of them and use this path, otherwise go through the bypass path.

Use all the Timesheet that have TS.excluded='YES' at once and apply the following algorithm:

• order these Timesheet by the calendar order of TS.startDate;
• format each TS.startDate to show the month abbreviation followed by two digits (MMM DD), eg. "except AUG 23", according to item D NOTAM syntax. Add space (" ") between the consecutive values;
• if two consecutive values have the same MMM value, then eliminate the repeated MMM value: for example, "except AUG 23 AUG 30" needs to be replaced with "except AUG 23 30"