Fun facts regarding schedules and time zones in DL Windows Software

Here are some basic rules to follow with schedules and how our schedules work in conjunction with our products. There are also different ways to get the same results. 

 

• The lock accepts the user(s) based on how to programmed them, enabled (green) or disabled (red) in the global user screen. 

• Schedules activate (enable) or de-activate (disable) the user(s) or group(s) as it “rolls into” a schedule.  Time zones/schedules are not retro active.  The clock moves forward, never backward.

• If you set a future schedule and send the user/group enabled (green), they will be enabled until the start time of the schedule and from then on the schedule takes over.

• If you set a future schedule and send the user/group disabled (red), they will be disabled until they “roll into” the schedule (start time) and from then on the schedule takes over.

• Example – if you create a schedule for 8am – 5pm Monday thru Friday to enable a group of users and your send group 2 enabled (green) and its 2pm on Wednesday, Group 2 users will be enabled until Thursday at 5pm; because it never rolled into the start time of the schedule.  We call this the 24hr rule.  We recommend that you send programming when possible prior to the start of schedules.

• If you send users disabled without a schedule, they will always be disabled.  However, when you send users/groups disabled (red) and there is a schedule in the future, the schedule will enable the user/group and then will follow the set schedule until a change is made. 

• Many companies put all users in every lock and disable (red) them in the locks they don’t want them to have access to.  This time and date stamps a “user denied access” and allows the company to see where employees are attempting to gain access on the audit log.

• Same goes for a holiday schedule.  We call it a suppression schedule.  If you don’t want users to have access on July 4^thand you have a schedule of 8am – 5pm M-F.  Simply create a conflict for July 4^thon the correct day of the week and set a start time of 8am and make the stop time blank.  By creating a conflict, the locks sees an enable and disable at the exact same start time, disable overrides enable and lock overrides unlock.

 

Please feel free to send you comments to me at Bswoope@alarmlock.com or click here to go to our web site

Comments

[bfs]

I've spent the last one and a half hours trying to schedule my DL2800s both at the lock and through the DTM, and almost launched the DTM across the parking lot in frustration. The 'rolling into' the schedules thing is probably what's going on. Thanks for this info.