ENGAGE - Schedule Guidelines

REVISION CONTROL RECORD

Introduction

The primary purpose of this document is to provide guidelines for the creation of required schedules for onsite operations. Also included are several test cases for exceptions and how to handle unusual situations.

This document was designed for a technically competent audience with an in-depth understanding of how to set device schedules within a site.

Abbreviations and Definitions

Schedule Guidelines

Schedule Priorities

Table 1: Schedules

NOTE: General guidelines for special cases (On Power-up, Out of Reset, Exit from Frozen State, Exit from Privacy, Restore Prior State), The Device always goes first to the known state, then requests the current schedule and acts upon the schedule as required. On special events (Time Change, Lock Function Change) the Device requests the current schedule and acts upon the schedule as required.

Scenarios

Scenario 1: Overlapping Holidays Crossing Midnight

At midnight (periodic schedule alarm) the lock executes the Holiday based on which is active Holiday, Not the one which has begun first on the previous day.

NDE Devices always scan through all Holidays and executes the one that starts first.

NDE behavior: In case of overlapping Holidays, the device will run the master scheduler at the end of the first Holiday and if there are any pending Holidays, the device executes that.

Example: Holiday 1- 02:00 to 03:00, Holiday 2- 02:30 to 3:30. The Device starts Holiday 1 and at the end of Holiday 1, the master scheduler starts pending Holiday 2 from 3:00 to 3:30.

The AD tool does not allow creation of overlapping Holidays.

Example: Holiday 1- 02:00 to 04:00, Holiday 2- 3:00 to 03:30. The Device starts Holiday 1 and ignores Holiday 2. At the end of Holiday 1, the Device goes to secure state.

Scenario 2: Auto-unlock Event on Previous Day and Holiday on Next Day

After a Holiday ends, the Device does not go back to passage state, because it does not find any auto-unlock event on the next day.

After Holiday expiration, the Device runs the master scheduler. If no event is in the master schedule, the device goes to secure state.

For any auto-unlock situation, the Device checks for the following condition:

(dbmEsAutoEvt.dbmFncEsRtc_Hour < dbmEsRtcCurrentTime.mqxDate.HOUR)

Auto-unlock is ignored if its starting time is greater than the current RTCC time.

If auto-unlock starts at 23:00 and the master scheduler is run the next day at 02:00, the condition is not satisfied. Because there is no event scheduled, the Device goes to secure state.

AD Devices behave in the same way.

Scenario 3: Scheduling a Holiday that Ends Exactly at 00:00

Scheduling a Holiday that ends exactly at 00:00, does not cause the Device to move out of Holiday state at 00:00.

NDE Devices always end the Holiday at end time.

AD Devices behave in the same way.

Scenario 4: Present a Toggle Credential at 04:00

In this Scenario, when a toggle credential is presented at 04:00, the Device moves to passage state. At 05:00 the Device moves to RS Holiday. At 06:00 the Device moves out of Holiday state and goes to secure state.

This Scenario is essentially the same as Scenario 2; After Holiday expiration, the Device runs the master scheduler. If no event is in the master schedule, the Device goes to secure state.

AD Devices behave in the same way.

Scenario 5: Auto-unlock with Midnight Crossing

NDE Devices remain in passage state after crossing midnight because the NDE Device does not send an event to lock state manager on midnight alarm. If RTCC changes on the next day or any Holiday ends, the NDE Device runs the master scheduler. If no event is in the master schedule, the NDE Device goes to secure state.

AD Devices do not allow the creation of an auto-unlock event without an end event; therefore, AD Devices go to secure state at midnight.

Scenario 6: Device is in Passage State

The Device is in passage state, battery is removed and replaced after some time (before RTCC loss).

On power up, the Device runs the master scheduler and if there is no passage event, the Device goes to secure state.

Devices never remain in passage state if there is no schedule event. If there is a schedule event, the Device first goes to passage state, then acts on the schedule event.

Scenario 7: First Holiday Time has Priority

In the event of overlapping Holidays, the first Holiday scheduled has priority.

For Example:

Holiday 1 – Thursday Dec 24 Start time 8:00 AM to End Thursday 11:59 PM 

Holiday 2 – Thursday Dec 24 Start time 11:50 PM to End Friday Dec 25 11:50 PM

Only Holiday 1 will be executed.

Test Cases

All Test Cases are executed with respect to Orca timings for NDE and LE Devices.

All three locks evaluated observed the same outcome.