Basic scheduling information
Schedules are configured per task from within the asset type in a compliance scheme (or template). Whilst most types of schedule can be achieved with ZetaSafe it is always recommended that you speak with your ZetaSafe Account Manager to make sure you are getting the most out of the scheduling tools and the wide variety of options.
There are six basic schedule types:
- Hourly
- Daily
- Weekly
- Monthly
- Annually
- Not Scheduled
All schedule types can be set to exclude weekends. Schedules can be edited at any time and a number of options are available as to how those changes are pushed to your barcoded assets within the ZetaSafe system. All tasks must have a schedule; Not Scheduled is the default schedule type for new tasks in ZetaSafe.
The ZetaSafe week runs from MONDAY to SUNDAY
The ZetaSafe weekend is SATURDAY and SUNDAY.
The ZetaSafe day runs from 00:00 to 23:59 (Time is recorded as UTC)
Schedules can be generalised as follows:
Non-Hourly Schedules
All non-hourly schedules (and their respective tolerance periods) are counted in whole days, task events (with the possible exception of the first event) will be due at 00:00 on their due dates. Non hourly schedule tolerances are discussed in terms of days, weeks, months and years.
Hourly Schedules
The hourly schedule is counted in single hours, tasks are due on the hour, or any minute of an hour, per the schedule. Hourly task tolerances are defined in minutes. An hourly schedule tolerances are discussed in terms of minutes where the standard tolerance is the minute in which the task is actually due. Hourly schedules can be set to run only within certain time restraints during a day (for example between 9AM and 5PM)
NOTE, EXERCISE CAUTION: When changing a schedule for a task it is always recommended to set a new seed date from which the schedule should be in place. When utilising the Temporarily Suspended status for assets, a new seed date should be selected before they are returned online or the ORIGINAL seed date will be used again and any ‘gaps’ in the historic schedule may be filled with missed tasks.
Tolerances
Task schedules can have tolerance. This is a window of time around the scheduled event and it means that any result entered within this window is completed 'on time' and it will be signed off. If a result is entered outside of the tolerance window then it is 'ad-hoc' and will not sign off the event.
Standard Tolerance
Standard tolerance can be applied to the following schedule types:
- WEEKLY – tolerance = the calendar week the event is scheduled in
- MONTHLY – tolerance = the calendar month the event is scheduled in
- ANNUALLY – tolerance = the calendar year the event is scheduled in
A result entered within these periods will sign off the scheduled event the tolerance is associated with.
Standard tolerances on any single task cannot overlap.
User Defined Tolerance
User defined tolerance is defined in MINUTES or DAYS (depending on the schedule type) and can be applied to all schedule types.
- HOURLY - tolerance defined in minutes before and after event
- DAILY - tolerance defined in days before and after the event
- WEEKLY - tolerance defined in days before and after the event
- MONTHLY - tolerance defined in days before and after the event
- ANNUALLY - tolerance defined in days before and after the event
User defined tolerances can overlap – this is because months have different lengths, using this type of tolerance would mean either having gaps in tolerance – where the schedule will not be signed off where results are entered on those days, or tolerances from Month A and Month B’s scheduled events will overlap during the transition from one month to the next.
NOTE: Overlapping user defined tolerances can cause confusion! Where a result is entered within a period of overlapping tolerance ZetaSafe will calculate (to the nearest millisecond) which of the two scheduled events is closest to the result entered and that is the event which will be signed off.
Tasks are scheduled at 00:00 in the morning of each day with the exception of hourly tasks.
Comments
0 comments
Please sign in to leave a comment.