...

When using DOM ENIQ hardware, the system is already prepared as standard for the use of "data on card", but also for mobile access. Using a mobile key makes it very flexible and easy. This applies not only to the use, but also to the creation and assignment of rights to locks and persons.

...

...

1.

...

2

...

Below is an overview of support for both the hardware and the software, including the necessary license:

...

Support

...

Hardware

Features and Benefits DOMBox API-integration

The iProtect - DOM REST API is a new way to connect that greatly improves the A1/B1 setup. It brings new features to help both users and administrators.

The A1/B1 setup will still work as it always has. However, the API setup provides many extra benefits and features that can make the overall experience better.

Below are the key benefits of the iProtect - DOM REST API:

• Support for multiple DOM controllers: Users can manage several DOM controllers at the same time, making security management more flexible and scalable.

• IPROTECT ACCESS (mobile access): Users can conveniently access the offline devices from their mobile phones, enabling them to utilize a single mobile identifier for both online and offline locks.

• Compatibility with DOM RF Netmanager: The API works well with the DOM RF Netmanager, making it easy to update lock configurations and send door commands, which improves efficiency.

• Real-time synchronization of OSS configuration data: Configuration data changes are instantly updated across all systems, minimizing errors and ensuring that everyone has the most current configuration status of the locks.

• Real-time synchronization of OSS device status: Users can continuously monitor the status of their devices, allowing for quick responses to any problems.

• Ability to add temporary DOM controller users (APP USERS): Administrators can easily add or remove users who need temporary access, like contractors who need to implement a new lock, improving security without losing convenience.

• Automation of DOM controller backup and restore processes: Automating these processes helps prevent configuration data loss and ensures backups are regularly maintained.

• Provisioning of AES DESFire keys to the Bridge: This feature allows for secure sharing of encryption keys. It sends the encryption keys and configurations from the iProtect system to the bridge, with the key encrypted in a KTL file (keystore).

• Installation of discovery function processes: The API can automatically find new devices from the bridge and link those devices to the correct readers, making the setup process easier and faster.

In summary, the A1/B1 setup remains unchanged, but the iProtect - DOM REST API introduces key enhancements that improve functionality, security, and user experience.

2. Support

2.1 Hardware and licence

...

...

Supporting OSS does not mean that every lock can be integrated effortless since this part is not standardized. This manual only describes the DOM OSS manufacturer.

4.1 Presets

To begin the installation, you must first have the correct key and configuration files.

...

4.2 Provisioner

A provisioner group consists of one or more elements. These elements can be configurations, key files or firmware.
The sections below describe the required combinations.

4.3 Card coding

...

...

• Save this record.

Create a Virtual line. This line is needed to connect DOM controllers.

In iProtect, browse to menu: Installation | Hardware | Line.

• Select the virtual line to which the DOM Controller is to be connected. Press right mouse-button: “Add Node”: Image Removed

• Activate the check mark behind "Node online.

• Save this record.

4.5.2.1 Node tree-view items Image Removed

After creating a DOM controller (Node), multiple items are displayed under the Node in the treeview.

Tree-view item

Description

Node backup

Whenever something is changed in the configuration of the DOM controller, iProtect backs it up. The backup is kept for a maximum of 3 months.

Device manager: No

All offline devices associated with a door/reader.

Device manager: Yes

Devices which are associated to a RF-NetManager (on-line)

Device manager

Connected RF-NetManager, interfaced with the DOM Controller

Devices unbound

All offline devices, not linked to a door/reader.

4.6 Add offline device

Using DOM OSS, the device is always linked to a door (a card reader in iProtect). Access rights are then associated with the card reader.

DOM devices such as ENIQPro or ENIQGuard, for example, are added to the system using the DOM Service app.

...

4.6.1 Add device

Although there are several methods to create the hardware, two methods will be described in this chapter.

• The readers with access rights are prepared in iProtect and linked to the device in the Service app.

  • Method 1: Link to existing reader <Prefered>

• The reader and device are created in the DOM service app.

  • Method 2: Link to a new reader

4.6.1.2 Link to existing reader Image Removed

Start by adding manually readers within iProtect.

Browse to the menu: Installation | Hardware | Node.

• Add a reader by clicking with the right-mouse button on the DOM node.

• Click on the icon “add reader”

• Fill in the logical name of the reader and select the correct card data interpretation.

• If desired, you can adjust the door open time in the "door behavior" tab.

• Once everything has been filled in, you can press the save button.

• You can grant access rights to the reader by adding the reader to the desired reader groups, you can do this in the reader group list under the created reader.

...

4.6 Add offline device

Using DOM OSS, the device is always linked to a door (a card reader in iProtect). Access rights are then associated with the card reader.

DOM devices such as ENIQPro or ENIQGuard, for example, are added to the system using the DOM Service app.

• Add a reader by clicking with the right-mouse button on the DOM node.

• Click on the icon “add reader”.

• Fill in the logical name of the reader and select the correct card data interpretation.

• If desired, you can adjust the door open time in the "door behavior" tab.

• Once everything has been filled in, you can press the save button.

• You can grant access rights to the reader by adding the reader to the desired reader groups, you can do this in the reader group list under the created reader.

Browse back to the menu: Installation | Hardware | Node.

• Select the DOM Controller Node.

• Open the tab: Other and enable by Installation option the checkbox “Add automatically”.

• Select “Link to existing reader' at the New device (app) option. Image Added

• All newly added devices with the dom service app are automatically added to iProtect and linked to the correct reader.

  • After about a minute the device should been enrolled and linked to the reader, and you can also see this on the detail page of the readers.

• The offline sync status will be visible and if everything is correct the status should be changed in a minute to the status “The configuration is synchronized”.

4.6.1.2.1 DOM Service app

Use the DOM service app to add the devices. During this process you can directly link the newly created readers to the correct devices in the DOM service app.

• Synchronize the DOM service app with the DOM controller.

• Add a device by clicking the Devices button and then clicking the + sign in the DOM service app.

• Apply the mobile phone (Android) to the device or present de RF Wake-up card to the device (IOS).

• Click on the OSS-SO-configuration button to link the device to the door (iProtect reader).

• Press on the couple button.

• Follow the instructions in the DOM service app.

Once the new devices have been assigned from the DOM Service app and the app has been synchronized with the DOM controller, the devices will be enrolled and automatically linked to the correct reader in iProtect. After it has been linked automatically, when using mobile access, enable the checkbox “IPROTECT Access”.

4.6.1.3

Link to a new

• Synchornize the DOM service app with the DOM Bridge

• Add a device by clicking the Devices button and then clicking the + sign in the DOM service app

• Apply the mobile phone (Android) to the device or present de RF Wake-up card to the device (IOS).

• Change the name of the device (this will be the reader name in iProtect).

• Press on the couple button

• Follow the instructions in the DOM service app (sometimes multiple synchronizations are necessary).

When the reader is synchronized, the following is displayed:

Image Removed

4.7 Lock sensor

...

After connecting a DOM device to a card reader, after synchronizing the device, a sensor will automatically be created containing the battery status of the device.

...

Battery status

...

Discovery

...

No status available

...

No status available

...

Replace battery

...

Battery is almost empty

...

Battery replaced

...

Battery is replaced

...

Full

...

Battery is full

4.8 Add online device

To change the offline device into an online device, a RF-NetManager is required.

The RF-NetManager needs to be configured using the DOMPloy software, please consult the DOMConnect manual and go to next chapter "Configure and deploy a RFNM".

...

4.8.1 Discover a new RF-NetManager

Ones the RF-NetManager is configured in DOMPloy, follow the steps below.

Browse to the menu: Installation | Hardware | Node.

• Open the tab: Other

• Press on the Discover button. Image Removed

• Add the RF-NetManager by selecting the checkbox and press the button Add.

• In the treeview, below the DOM Node, go to RF-NetManager, the device will be displayedImage Removed

• In the treeview, below the DOM Node, go to RF-NetManager: No, open this tree

  • A list of devices are shown. Select the offline device which must be connected to the RF-NetManager.

  • Enter by Network-manager the RF-NetManager Image Removed

  • Save this record

• In the treeview, the device will be moved to RF-NetManager: Yes

• Now the RF Wake-up card needs to be presented to the device (lock). After presenting, the leds of the device should blink blue.

• After the device is synchronized, the paired reader is given the following options:

  • Reader | General

    • Reader mode: Open, Close and Normal

  • Reader | Door behavior

    • Button option, Open ones

5. Configuration management

5.1 Offline devices

The following section uses the DOM Service App

Expand
title How to update or remove offline devices...
5.1.1 Access rights management If you want to add or remove access rights to an offline lock, you can do this using reader This setup can be done automatically by the system by enabling the auto discovery function. When a new device is assigned from the DOM Service app, and the app is synchronized with the DOM controller, iProtect will automatically recognize it and assign the preset settings to the device. Info By using this way of configuration, multiple synchronizations with the device are needed! Note The mobile phone used to program the locks must have a stable and direct online connection with the DOM controller. If this is not possible, we recommend using the manual method. Browse to the menu: Installation | Hardware | Node. Select the DOM Controller Node. Open the tab: Other and enable by Installation option the checkbox “Add automatically”. Select “Link to new reader' at the New device (app) option. Select the correct Card data interpretation. When using mobile access, enable the checkbox “IPROTECT Access”. Select a Reader group which can be used during testing the system. Start the auto discovery process by pressing on the start button. Info When the auto-discovery process is started, assigning of new device and readers will be activated for 4 hours. After this time this process will stop automatically. 4.6.1.3.1 DOM Service app Use the DOM service app to add a new device. Synchornize the DOM service app with the DOM controller. Add a device by clicking the Devices button and then clicking the + sign in the DOM service app. Apply the mobile phone (Android) to the device or present de RF Wake-up card to the device (IOS). Change the name of the device (this will be the reader name in iProtect). Press on the couple button. Follow the instructions in the DOM service app (sometimes multiple synchronizations are necessary). When the reader is synchronized, the following is displayed: Image Added

4.7 Lock sensor

4.8 Add online device

To change the offline device into an online device, a RF-NetManager is required.

The RF-NetManager needs to be configured using the DOMPloy software, please consult the DOMConnect manual and go to next chapter "Configure and deploy a RFNM".

5.2 Online devices

...

5. Configuration management

5.1 Offline devices

The following section uses the DOM Service App

6. Migrate the DOM OSS configuration from A1/B1 to API

This section describes the benefits of using the DOM OSS API and gives a simple step-by-step guide on how to convert your current DOM OSS setup (A1/B1) to the API setup.

6.1 iProtect - DOM REST API Enhancements for A1/B1 Installation: Features and Benefits

...

5.2 Online devices

The following section uses the RF-NetManager. The DOM service app is not needed.

6. Using the DOM API-implementation

To take advantage of the new API-implementation and hereby the benefits (see Chapter 1.2), the setting in IPROTECT must be changed.

7. Extensive information

7.1 Reader dialog details

...