1.0 Introduction
This feature implements a calendar based on the Site. Site Calendar offers the ability to automatically schedule events that need to occur at a specific time. There are hardware control scheduled events, such as: synchronizing the controller at a specific time, temporarily unlocking a particular reader or multiple readers, and masking door contacts, inputs and outputs. There are also actions that can schedule activation and de-activation of Site Lock/Lockout/Lockdown and Site Unlock. The events created in the calendar will contain Subject, Category, Start, and End time. The calendar events can be displayed on a daily, weekly or monthly view.
Note: The Site Calendar feature is controlled by a feature flag to allow us to evaluate and monitor
the performance before a wider rollout. To request access to use this feature, please contact your
integrator or regional sales manager.
2.0 Site Calendar Options
2.1 Hardware Control
The following is a list of actions you can perform on the hardware:
- Lock - Lock a specific door.
- Unlock - Unlock a specific door.
- Temp Unlock - Temp unlock a specific door (for the duration of the programmed strike time).
- Card & PIN - Configure a keypad to go into Card & PIN mode.
- Card or PIN - Configure a keypad to go into Card or PIN mode (only supported on NXT-MSC and Mercury controller types).
- PIN Only - Configures a keypad to go into PIN only mode (only supported on NXT-MSC and
Mercury controller types).
Notes:
- If you are using keypads, the Card + PIN option will not display as an end action until 'Keypad Enabled' has been selected in the keypad's reader properties.
- If you are using NXT-MSC or Mercury controllers, the Card Or PIN and PIN-Only options will not display as end options until you have unique PINs enabled on the system. This setting can be found in System Settings (menu item) >> PIN Settings. Set the number of PIN digits to be used and set Require Unique PINs to Yes.
- Mask Forced - Masks a specific reader's door forced functionality.
- Unmask Forced - Unmasks a specific reader's door forced functionality.
- Mask Held - Masks a specific reader's door held functionality.
- Unmask Held - Unmasks a specific reader's door held functionality.
Note: Masking and unmasking door held and door forced is not supported with PXL controllers.
- Mask - Masks an input (this suppresses input alarm and input secure events).
- Unmask - Unmasks an input (this re-enables input alarm and input secure events).
Note: Masking and unmasking inputs is not supported with PXL controllers.
- Turn Off - De-activates an output which is active.
- Turn On - Activates an output which is inactive.
- Pulse - Temporarily activates an output for the output's programmed pulse time.
2.2 Site Lock/Site Unlock
- Site Lock/Lockout/Lockdown - Allows you to schedule the site to go into Site Lock/Lockout/Lockdown (depending on which Site Lock type is configured for the site).
Site Lock will lock all doors which are unlocked. Site Lockout will also lock all unlocked doors - all cardholders will then be denied access but the RTE will still function. Site Lockdown will lock all unlocked doors - cardholders will be denied access and the RTE will not function.
- Site Unlock - Allows you to schedule a time and date when all doors on the site will unlock.
Notes:
- To schedule a Site Lock or Site Unlock, the settings must already be configured on the Sites screen (via the Actions menu), otherwise the Site Lock/Unlock option will not appear in the
Categories list.
- Site Lock and Site Unlock can be configured in reader settings to be ignored, except for PXL
controllers. Site Lock and Site Unlock can only be enabled/disabled per PXL primary controller. When disabled on a PXL primary controller it will also be disabled for all secondary PXLs on that local PXL network.
- Site Lock/Site Unlock is supported with Keri KB, Keri NXT, NXT-MSC, Mercury and PXL
controller types. It is not supported on Switch Tech locks.
- Site Lockdown will not be fully functional if the access control hardware uses a manual egress device, such as; a crash bar, doorknob, lever, paddle, etc. since these devices mechanically retract the latch to allow for exit.
2.3 Sync
Sync - Allows you to sync specific changes or to sync all changes to a controller at a certain time or date. This will ensure the controller is completely in sync with the data that is in the cloud. You can setup multiple events to sync multiple controllers.
2.4 Event Occurrence
2.5 End Options
The end option is what you want to happen at the end time. For example, with hardware control, this could be setting the door back to being locked after it has been unlocked or put into Card & PIN mode. Or unmasking a door contact or an input after it has been masked.
Note: There are certain actions that do not have an opposite end action; such as; pulsing an output or temp unlocking a door.
3.0 Schedule Site Calendar Events
The following steps explain how to setup an example event that will put a site into lockdown mode. When lockdown is active, all cardholders will no longer be granted access and the Request-to-Exit devices will not work. For example, you may wish to lockdown an entire site for the duration of a specific weekend. The same steps are applied to scheduling other event types as well.
3.1 Configure a One-Time Event
- From the Borealis main menu, click on Sites >> Calendar.

- The Site Calendar screen will appear.
- Click the CREATE EVENT button located in the upper-right.

- In the Subject field, enter a name for the new event.
- From the Categories menu, select Site Lock/Unlock.
- Select the One Time option.
- Set the start time and the end time.
- Set the start date that you wish the event to begin.
- Set the end date when you wish the event to end.

- Click Next
- For the start action, select the situation/mode that you wish to activate (site lock)
- For the end action, select the situation/mode that you wish to activate (restore to normal).

- Click Save.
- The event will then be displayed on the Site Calendar grid.
- You can click on the display option buttons to select between viewing the calendar month, weeks or days.

3.2 Configure Recurring Events
When setting up an event it can either be 'One-Time' or 'Recurring'. A recurring event can be
scheduled to occur at various frequencies. The following example explains how to configure
a controller sync to occur daily but also outlines which other recurring options are available.
- Create a new event.
- Name the event.
- Select Recurring.

- Specify the start time and end time.
- Select the start date.
- From the Repeat drop-down menu, select either: Daily, Every Weekday, Weekly on (current day of the week), Annually (current date), or custom frequency period (such as every 2 days).

- End options - this determines when the recurring event will no longer function.
- Never - This does not specifically mean that the event will occur indefinitely. It will occur approximately 500 times and will then need to be recreated.
- On - You can specify a date when the event will stop occurring.
- After occurrences - You can specify how many times the event will occur before it stops
functioning.
- Click NEXT.
- From the Actions list, select what data you wish to sync or select All to sync all the data.
- Select the specific controller you wish to sync.
- Click SAVE.

4.0 Edit a Site Calendar Event
The following steps explain how to edit an event. For example, you may wish to change the time that the event starts.
Note:
- From the Calendar grid, click on one of the events.

- Select to edit only the selected event or all events (if it is a recurring event).

- Change the start or the end time, or make a different modification, such as the repeat
frequency or the end option. - Click NEXT.
- You can then edit the Action settings - such as the selected reader or the end action.
- Click SAVE to commit the changes.
5.0 Delete an Event
To delete an existing event from the calendar:
- Click the event that is displayed on the calendar grid.
- Click the red DELETE button.
- Confirm that you wish to proceed with deleting the scheduled event.

- The entire event will be deleted, including all days included in the event and all occurrences of the event if it is set to recurring.
 |  P/N: 02482-001 Rev. A
|