Daily Counter#
Time Rule Overview#
This time rule counts the separate occurrences for time codes such as OT, IN LATE or OUT EARLY. It can also be used for counting the number of meals taken in a day, or to track/count the number of days an employee has physically worked.Requirements / Features#
- Filtered by the time code set specified in the Target Time Code Set field, this time code set should include the time codes that are used to count the amount of non-contiguous time . For example: When used to count the number of meals taken in a day, all of the meal time codes would be defined in the Target Time Code Set.
- If an employee takes back-to-back meals (the next meal starts at the same time that the first one ends) these meal times would not count towards the total.
Implementation#
- The time code on the time rule should have a basis of ‘Unit’.
- All meal time codes should be included in the Target Time Code Set.
Additional Info#
- Frequency predefined as Every Day
Implementation#
The time rule should be set up in IDWR as shown below.| Cycle | Frequency | Seq | Time Rule Type | Band | From | To | Value | Day | Time Code | Premium | Target Time Code Set | Apply Time Code Set | Action |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Every Day | 955 | No | No | No | No | No | Allowed | No | Allowed [1] | Add |
[1] All meal time codes should be included in the Target Time Code Set.
