Timezones support

Ask a question

Sigur supports different time zones, which allow you to create custom access rules and accurately track working time at companies with a wide network of branches.

Access control and reporting

Imagine that the headquarters of your company is located in Moscow, where your PACS server is deployed. And your company also has an office in Vladivostok. In Sigur, you will be able to set work and access schedules at that remote office using their local time. In this case, all events will be also recorded using local time and not Moscow time used by your PACS server.

Setting time zones

When you connect your checkpoint to Sigur controller, one of the configurable parameters you will see is its time zone. Time zones are set depending on the controller location relative to the server.

For instance, if the headquarters where the PACS server is deployed is located in Moscow and its time zone is GMT+3, then the turnstile at the checkpoint in Chelyabinsk will be at GMT+5. Thus, the system will take into account the time zone differences between the regions.

Accurate time and attendance tracking

Time zones in Sigur will help you avoid manual calculations, save your workforce’s time and eliminate human errors.

Geographically distributed architecture

Sigur architecture is designed so that all devices and equipment can be connected into a single system regardless of their geographical location. Most of Sigur controllers are network-enabled and are standard IP devices that can communicate with the system server over the Internet.

They also have an integrated memory, which can store information about all events in the system (including all access events). The date and time of the recorded events will be registered using a real-time clock, i.e. local time.
Therefore, even if the server is temporarily not responding, all data are saved. As soon as the connection is restored, all events are automatically transferred to the PACS server.