30.01.2015 Views

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

Picture Perfect 4.6 User Manual - UTCFS Global Security Products

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 10<br />

Schedules, modes, and events<br />

193<br />

Events overview<br />

Use the Events forms to define and schedule the desired characteristics for Area Events, Reader<br />

Events, Door Events, Alarm Events, Input Group Events, Output Group Events, Backup Events, or<br />

Report Events, and assign the appropriate mode to each of them.<br />

Two types of event scheduling options are available: Runtime and Start/End.<br />

• Runtime lets you schedule an event to cycle within a mode, and can occur at a particular time<br />

on any days of the week.<br />

• Start/End schedules the event to take place only once, either at mode start or at mode end.<br />

Notes: Mode Events will not execute while in emergency mode, regardless of how the emergency mode was initiated,<br />

until the emergency mode is exited.<br />

Schedules that run on the micros can update the database. This is configurable on the Parameters form using the<br />

field Schedules Update Database. With this feature enabled, as long as there is communication with the micro, the<br />

host reflects the scheduled state of the device. (For example, if a door is scheduled to unlock at 8 AM, the host<br />

record is updated to reflect the change.) If this feature is disabled, the host record only reflects the host database<br />

information<br />

Runtime events<br />

Runtime Events are events scheduled to occur in weekly cycles for selected areas, readers, doors,<br />

alarms, input groups, and output groups. A runtime event can occur on one or more days per week at<br />

the start time that you select. Runtime events are frequently used for the normal operating mode.<br />

Runtime events must be created in “pairs,” so that the entire cycle of events can be completed.<br />

Therefore, you need to create two events for each cycle and make sure both events are assigned to<br />

the same mode.<br />

For example, an “unlock door at 8 AM” event is paired with a “lock door at 5 PM” event to define a 24-<br />

hour cycle for that door. Both events are scheduled for weekdays only. The door does not require a<br />

runtime schedule for weekends, because the door locks at 5 PM on Friday and remains locked until<br />

Monday at 8 AM when the “unlock door” event occurs (unless someone manually unlocks the door).<br />

Runtime events can be used to allow certain people access to an area at certain times, such as with<br />

multiple shifts of workers. You can assign an area certain categories from 8 AM to 5 PM, and other<br />

categories for later shifts or for weekends. (Each shift must have its own category, which must be on<br />

the appropriate badges.) To do this, set up a series of Area Events that change categories. After you<br />

set the days and the time for each event (category change) to occur, the events continue to occur on<br />

a weekly cycle.<br />

Start/end events<br />

Start/end events occur only once during the mode, either at mode start or at mode end. Start/end<br />

events are frequently used for Emergency and Holiday modes.<br />

A mode-start event may require a parallel mode-end event to “undo” the change. This may not be<br />

necessary, however, since the next normal mode change may accomplish the desired change.<br />

For example, a Fire Mode could be set up using mode-start and mode-end events. When the<br />

operator uses the Mode Command form to select Fire Mode, all the events associated with this mode

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!