Knowledge Articles

ThyssenKrupp(TKE) Enhancements

This feature allows the user to assign a default floor to a cardholder (along with a couple of attributes related to it) and have an elevator automatically dispatched for that floor when the cardholder badges at a Kiosk with the 'Register Call (Turnstile)' flag checked.  This will typically be a Turnstile in a lobby. Enabling this feature requires the following steps.

  1. Mark the Kiosk with the 'Register Call (Turnstile)' option.
  2. Modify the Elevator Flags for any cardholder that has a default floor.  In addition to the Default Floor, you can designate the Rear opening, the amount of time it takes to Walk to the Elevator in seconds, and preference as to what elevator(s) this user has.  For now, the Car Preference is a numerical value and clarification from ThyssenKrupp is needed before final implementation.  It will most likely change in subsequent releases to some sort of drop-down of available elevators. For now, don't use it unless you talk to the Open Options development team first.

When a card is badged at a Kiosk that supports the 'Register Call' option AND they have a default floor, a call request for the default floor will be sent to TKE controller with no further action necessary by the cardholder.  If the cardholder does not have a default floor it will just execute the standard 'Card Swipe' call where the user is expected to select a floor from the available floors.


Engage Credential Functions

Credential functions in the Engage reader allow a card to perform specialized functions.  In previous versions, we have supported the "Pass Thru" function with the standard 'Override' flag.  This allows a card to open a door that is in Lock Down mode.  However, Engage supports these additional credential modes

One Time- A onetime use credential opens a door only once with the normal function. Once a onetime use credential has been used on a door, it will no longer work on that door. It can still work on other doors, to which it has been assigned.

Supervised- Supervised credentials allow access only when a second supervised credential is presented.

Toggle- A toggle credential opens a door and leaves it open until it is closed again by a toggle credential. It toggles a door between locked and unlocked.

Freeze- A freeze credential disables the credential reader. After a freeze credential has been used on a lock, only a pass-through credential will operate the lock. Present a freeze credential to return the lock to an operational state.

Lock Down- A lock-down credential will always put the lock into the secured mode plus freeze credential functionality.

Dogged- Toggle credential functionality for a crash bar exit device (only when we add support for the RM/RU to the IP Gateway integration

These options are available via Global Access Levels.  If the site is licensed to Engage IP Gateway a new option will be available on the Global Access Level header.  It has no meaning if you don't select any Engage doors.  By using the Access Level approach, you can allow a credential to have different functionality on a door by door basis.

NOTE: If a credential, due to having multiple access levels assigned that use credential functions, ends up with multiple functions only one will be applied. The credential function with the highest priority will be used.  The priority is as follows.  Keep in mind that using the 'Override' flag on a credential applies to all doors globally and overrides any credential functions applied via an Access Level.

  1. Pass Thru
  2. Lock Down
  3. Freeze
  4. Toggle
  5. Supervised
  6. Dogged
  7. One Time

OnSSI Ocularis Integration

The DNA Fusion/OnSSI Ocularis integration requires the following support files. It is important to FIRST INSTALL THE ONSSI SDK RUNTIME, then install the DNA Fusion Integration Files.

Please note your version of Ocularis and download the appropriate support files below.

Important: If upgrading Ocularis from an earlier version, it is strongly recommended you uninstall previous integration files on the host computer prior to installing the new version's integration files.

The following files work with Ocularis v5.2:

(Requires minimum DNA Fusion v6.6.0.48)

Ocularis Integration 5.2
DNA Fusion Integration files--DNA Fusion Integration files

The following files work with Ocularis v5.1:

(Requires minimum DNA Fusion v6.4.0.5)

Ocularis Integration 5.1
OnSSI 4.1 SDK Runtime4.1Ocularis SDK Runtime
DNA Fusion Integration files--DNA Fusion Integration files

The following files work with Ocularis v3.8 – 4.1:

(Requires minimum DNA Fusion v6.2.3.12)

Ocularis Integration 4.1
OnSSI 4.1 SDK Runtime4.1Ocularis SDK Runtime
DNA Fusion Integration files--DNA Fusion Integration files

The following files work with Ocularis v3.7 and earlier:

Ocularis Integration 3.7.x and earlier
OnSSI SDK Runtime3.7.1.22Ocularis SDK Runtime
DNA Fusion Integration files--DNA Fusion Integration files

The following files work with Pre-Ocularis (NetDVMS):

Pre-Ocularis Integration
DNA Fusion Integration files--DNA Fusion Integration files

Suprema BioConnect Integration

The integration of the Suprema biometric solution uses the Fusion Flex API to sync the biometric database with the DNA Fusion database and to allow for the enrollment of biometric templates in a seamless manner through DNA Fusion.

NOTE: The Suprema Biometric integration with DNA Fusion requires the following support files. Please refer to BioConnect installation documentation within the support files below.

BioConnect Integration
FLEX API1.25Flex API Install
BioConnect Support Files4.7BioConnect Install Package

This integration will work with DNA Fusion version and higher.

  • The integration requires DNA Fusion, Flex API and the Entertech/Suprema BioConnect application.
  • The DNA Fusion application and the BioConnect application should reside on the same server computer.
  • There is a sync service from BioConnect application that ensures that their database is up to date with the DNA Fusion database and as records are added/removed to DNA Fusion they are replicated over to the BioConnect database.
  • The Suprema readers can be configured in the following ways.
    • Finger Only (1:N)
    • Card or Finger
    • Card & Finger (1:1)
  • The following Suprema readers are supported by the BioConnect integration
    • BioEntry Plus
    • BioEntry W
    • BioLite Net
    • BioStation
    • BioStation T2
  • The readers connect to a reader port on OO hardware and output Wiegand data.


Listed below are the steps to necessary to enroll a personnel record in DNA Fusion. These steps assume that the required setup instructions have been followed.

  1. Add a new personnel record
  2. Add a card number to the record and update the record (be sure to add an access level)
  3. Click the Enroll button
  4. This will launch the BioConnect Enrollment application with the card number in the search field and the personnel record listed below.
  5. Double click on the record to begin the enrollment process and select the Choose Finger box and select the desired finger to be enrolled.
  6. Then follow the instructions on the screen for the enrollment process.


  • Allows for the integration of the Suprema biometric reader product line.
  • Ability to support fingerprint only (1:N)
  • Simply passes DNA Fusion a card number via a reader port.
  • Eliminates double entry of cardholder data.
  • Auto update of cardholder info from DNA Fusion.