Open/Close Schedules require values that allow users to arm (Close) and disarm (Open) the site and match to the monitoring of these events for any potential violations of the monitored schedule. Below are examples of Open/Close Schedules and Why they work, or don't work.
Good Schedule - Standard Open/Close with No Weekend Hours
Bad Schedule - Standard Open/Close with No Weekend Hours
Good Schedule - Checks only that the System is Armed Once a Day
This schedule allows the operations to only receive Late to Close events if, and only if, the system is not armed at 23:30 daily. This is a common schedule used for business and retail operations.
Bad Schedule - Checks only that the system is Armed Once a Day
This same schedule fails to allow for any items other than a closing at the EXACT time of the Must Close time.
Good Schedule - No Late to Close but Arm/Disarm after hours are exceptions.
This schedule sets the No Activity value at the general Must Close Time which prevents a Late to Close generating to an operator.
Bad Schedule - Must Close forces the Late to Close to an operator.
