With Sigur synchronization tools, you will never need to enter your PACS employee database twice as long as you have already had it in other systems. Information about your employees will be automatically copied from an external source and, when changed, will be automatically updated in the PACS.
Synchronization of PACS employee database with a third-party system is essential for large and medium-size facilities. Large companies can already have their own internal system, which stores all information about their employees.
Manual migration of these data to a PACS is a dull and time-consuming work that takes a lot of effort and can often result in errors.
During a sync process, the same synchronization cycles are consistently repeated. Each synchronization cycle identifies and eliminates any differences between Sigur database and the external database. These cycles are run by Sigur server automatically with the defined periodicity. Several external data sources can by synced simultaneously.
If an ODBC database is used as an external system, Sigur will also be able to sync all registered access events. All events will be sent as they are being recorded, without delays
This synchronization option can be used with any ODBC-compatible database such as MS SQL, Oracle, MySQL, Firebird, PostgreSQL, dBase, MS Access, Paradox, etc.
Supported functionality:
As an additional optimization mechanism, the system can skip synchronization cycles if the database version of the external system has not changed. The external system can provide access to this parameter and ensure it is updated when any data relevant for the PACS change.
The external system can store photos as JPEG, BMP, GIF, PNG. Sources photos in the external system can be of any size: the graphic format is defined automatically, the size is also automatically adjusted to be compatible with Sigur.
Photo upload is optimized (it is recommended to use this feature if possible). This is how it works: the external database provides access not only to photos but to their versions being a value which changes every time when the photo changes.
For instance, as a photo version, the time of the last change of this photo can be used, its hash or any even prime number increased by one by the external database with every update of the photo in it.
In this case, Sigur will most of the time request and compare only photo versions, which is significantly less resource-intensive than comparing the photos every time. The photo will be requested from the external database only if the PACS does not have the up-to-date photo.
Synchronization of ID numbers
Sigur can process ID numbers in several formats, including decimal and hexadecimal numbers, from the external system. Sigur can also send ID numbers assigned to employees by the PACS to the external system. ID numbers are sent to the external system in one of the selected formats.
This synchronization option provides you with auto updates on the cardholders from 1С:Enterprise database. For this synchronization to work, you will need to ensure that:
This option has some specific requirements to 1С:Enterprise configuration. 1С:Enterprise configuration must have the following catalogs: Employees of Organisations (or Employees), Departments of Organisations and Organisations. These requirements are satisfied in such configurations as Payroll and HR Management and Manufacturing Enterprise Management.
This functionality can be used together with export of a time and attendance report from the PACS to 1С. Based on access events recorded by the PACS, the system will generate a standard time and attendance report, e.g. Т-13 Form, and export these data to 1С for payroll purposes.
When a request to 1С database is written, you will need to specify how the response columns will be interpreted by the PACS. The received value can be processed in the following ways:
If enabled, this feature performs automatic update of personnel data in Sigur against 1С:Enterprise database. The following data on each employee are synced: name, department, position, employee ID, photo. If several organizations are included in 1С:Enterprise database, either one of them or all of them can be synced. If all of them are synced, sections for each organization will be automatically created in Sigur database and then, inside these sections, departments will be created.
This synchronization scenario uploads all fields for each employee, including ID numbers and lists of access levels, from the source. LDAP (Lightweight Directory Access Protocol) is a protocol that provides access to catalogs containing various elements. These elements also have naming attributes.
A LDAP server stores these catalogs and provides access to them to LDAP clients via the network, including such features as search through the elements and loading attribute values. Sigur server can be used as a LDAP client.
In Sigur, you can specify the relevant catalog to search entries in and configure additional filters, i.e. which entries will be uploaded to the PACS. The result of the request will be entered into Sigur database.
Active Directory domain controller is a special case of a LDAP server. Active Directory elements can be accessed via LDAP protocol.
Active Directory synchronization can be used together with auto blocking of accounts in Active Directory when the employees physically leave the permitted areas.
The options described above are not the only options of data synchronization in the PACS. Sigur supports other tools as well, including: