Synchronization with the third-party database

Ask a question

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.

Why is it important?

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.

Synchronization mechanism

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

Synchronization via a standard ODBC interface

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:

  • Synchronization of main fields of employee files, such as full name, department, employee ID, position; it also enables transfer of the nested hierarchy by departments from a third-party system
  • Synchronization of any custom fields created by the user
  • Synchronization of work schedules and justification documents if presented in a specific but simple format
  • Synchronization of photos
  • Synchronization of ID numbers (cards, key fobs, fingerprints and other identifiers); synchronization of more than one identifier for each employee is supported
  • Sending PACS events to a third-party database (including an option of syncing employees’ access events only with the source from which the list of employees was obtained)

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.

Supported photo formats

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.

Optimization of photo synchronization

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.

LDAP synchronization

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.

Integration with Active Directory

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.

Other employee data synchronization options in Sigur

The options described above are not the only options of data synchronization in the PACS. Sigur supports other tools as well, including:

  • Employee information import from an XLS file integrated in any Sigur software
  • Synchronization with Intellect (ITV) database available if integrated with Sigur
  • Personnel synchronization with a partner website, uploading access events to the website. This option is optimal for a PACS deployed in a number of similar organizations, such as schools, and enables centralized management and control
  • Designing your own tools based on open integration interfaces supported by Sigur.