Schedules

Schedules define times of availability and unavailability. The built-in "Always" schedule is a schedule that is simply always active. Defining new schedules is easily done through the Gateway's configuration web interface. Schedules can also be administered inside a Vision Client by using the Schedule Management Panel component.

Defining a Standard Schedule

Each standard schedule is defined by which days of the week it is active for, and during what times. Standard schedules can also be defined with repeating patterns that repeat either weekly or daily. When defining time ranges, use 24-hour format and commas to break up different spans. For example, if you want the schedule to be active from 8am-5pm with a 45 minute break starting at noon, you'd use: 8:00-12:00, 12:45-17:00

Defining a Composite Schedule

Composite schedules are made from combining two other schedules, either standard schedules or other composite schedules. A composite schedule is active when either of its component schedules is active. This allows you to build very complex schedules.

Be careful when designing composite schedules not to have circular references, where schedule A includes schedule B somewhere in its tree of included schedules and schedule B also includes schedule A.

For Alarm Notification

Schedules are always used by the alarm notification system. When an alarm notification pipeline reaches a notification block, it looks at all of the users defined in that block's configured on-call roster. Only those users whose schedules are currently active will be notified. This way, you can group people in call rosters by role, not by shift. For example, suppose you have alarms that should be sent to all supervisors. You can put all of the supervisors in one call roster, and the scheduling system will automatically only notify those supervisors who are on-shift when the alarm goes active.

For Restricting Login

Schedules may optionally be used to restrict users' ability to log in. To enable this, check the "Schedule Restricted" option on the user source in question. That user source will then reject logins for users whose schedule is inactive, even if their credentials were accurate.