Leap years occur every four years as a way to help synchronise the calendar year with the solar year, or how long it takes the Earth to orbit the sun. While this is necessary, leap years require our security systems to account for an extra day, apart from its normal schedule. As a result, leap years create problems with computing and can cause major issues to access control system functionality if a provider is not leap year compatible. There are a few things to keep in mind as we near February 29 to ensure you and your system are prepared for this uncommon occurrence.
Why doesn't my access control system work on a leap year day?
A leap year doesn’t occur that often, but if your system is newer than four years old, then this may be the first time you are being hit with this issue. It may be something as simple as the fact that the manufacturer of the system failed to account for leap day in their QA/testing procedures when designing the product. Regardless of the reasoning, it is important to recognise the issues that could arise so you can be prepared. An access control system malfunctioning never leads to a good outcome.
What are some of the issues I could run into if my system isn’t leap year compatible?
If you have your doors on a schedule, it could lead to doors being open on a Saturday or Sunday — which is the case this leap year — when they should not be open. This could naturally lead to unauthorised individuals gaining access to sensitive areas, putting company assets at risk. This could also lead to problems with credentials that were set to start or expire on a certain date, which could cause problems for new employees needing access, or could extend access privileges to contract workers whose employment terms have ended. In addition to credentialing, other scheduled events will also be off in the system. For example, some access control systems automatically lock or unlock doors on a set schedule based on business hours. With no defined schedules in place for a day that only occurs once every four years, this could lead to issues with scheduling for both authorised and unauthorised individuals.
What can I do to ensure my system is ready for Feb. 29? Anything?
If your manufacturer hasn’t alerted you that your system is leap-year compatible, it is best to set up your system in a test lab and simulate the leap-year date. This allows you to verify that all of your scheduling type events work correctly. If it works in a simulation, it will work on the actual day. However, beware waiting until the last moment to test your system, in case you do run into challenges that need to be addressed.
Are there solutions available that account for this already?
This is an important question to ask if you are evaluating a new system. While there are some systems that do not account for a leap day, many systems, like Hirsch Velocity, already do. In fact, Hirsch products have been leap-year compatible for many years now, allowing end-users to ignore the inconvenient day altogether.
What if my system doesn’t?
If you know for a fact that your system is not leap-year compatible, ask your provider before that date to test and ensure that your system will work properly. If you do this and encounter scheduling issues, you can opt to push off all of your scheduled events until March 1 and validate scheduled doors being opened on February 29 to plan accordingly. While leap day is inconvenient, it is addressable. It is just important to do so early to catch any issues before they arise. Failure to acknowledge the challenges associated with leap years will inevitably lead to difficulties when the day comes.