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

The supported NXP rfid cards and tags are listed below:

The following features are supported:

2.4 Known not supported features

The following features are NOT supported (yet):

2.5.1 MIFARE DESFire RFID

2.5.1.1 Standard OSS Application

2.5.2 Mobile device

Possible OSS events are described below:

2.7.1 OSS data on card - XML import/Export (A1/B1)

2.7.2 OSS data on card & Mobile access with RF-NetManager

2.7.2.1 Use of RF-NetManager

To use the DOM Service app, the configuration of the DOM controller must be synchronized with the DOM Service app.

The connection can be made via:

4.1.1 Add OSS manufacturer

• Browse to the menu: Installation | Hardware | OSS manufacturer

• Save

4.1.2 Add media element

Customer-specific elements supplied by TKH-Security.

• Browse to the menu: General | Settings | Media element

• Add three types of files:

• Save this record

• Save this record

• Save this record

• Save this record

4.2.1 Provisioner element

• Browse to the menu: Installation | Settings | Provisioner | Provisioner element

• Add provisioner elements

• Save this record

• Save this record

• Save this record

• Save this record

4.2.1 Add Provisioner group (DOM Controller) and select elements

• Browse to the menu: Installation | Settings | Provisioner | Provisioner group

• Add provisioner group DOM-IP-Bridge.xml

• After saving this record, open the treeview and go to Provisioner elementlist and select:

  • Element: OSS Enrollment

  • Element: Keyfile.ktl

  • Save this record

4.2.2 Add Provisioner group (OSS Enrollment) and select elements

• Browse to the menu: Installation | Settings | Provisioner | Provisioner group

• Add provisioner group OSS Enrollment

• After saving this record, open the treeview and go to Provisioner elementlist and select:

  • Element: OSS Enrollment.xml

  • Element: Keyfile.ktl

  • Element: Reader - LED settings, Led_act-red_acc-green_alt-blue.xml

  • Save this record

4.2.3 Add Provisioner group (OSS Update) and select elements

• Browse to the menu: Installation | Settings | Provisioner | Provisioner group

• Add provisioner group OSS Update

• After saving this record, open the treeview and go to Provisioner elementlist and select:

  • Element: OSS update.xml

  • Element: Keyfile.ktl

  • Element: Reader - LED settings, Led_act-red_acc-green_alt-blue.xml

  • Save this record

4.3.1 Add Card number presentation

• Browse to the menu: Access | Settings | Card coding | Card number presentation

• Add Default DesFire

• Save this record

4.1.2 Add Card data interpretation group

• Browse to the menu: Access | Settings | Card coding | Card data interpretation group

• Add a group

• Save this record

4.1.3 Add DESFire Card data interpretation

• Browse to the menu: Access | Settings | Card coding | Card data interpretation

• Add Default DESFire:

• Save this record

4.1.4 Add OSS Enrollment card data interpretation

• Browse to the menu: Access | Settings | Card coding | Card data interpretation

• Add OSS Enrollment

• Save this record

4.1.5 Add OSS Update card data interpretation

• Browse to the menu: Access | Settings | Card coding | Card data interpretation

• Add OSS Update

• Save this record

This chapter describes both DOM OSS data on card and mobile access. A physical controller line is created for using DOM OSS data on card that can also be used for normal access or mobile access The hardware which is used are:

• Pluto network device

• Orion door controller

• Sirius iX card reader which supports BLE

The on-line hardware is needed to profide the RFID card of a OSS application or to update these cards.

4.4.1 Add Network device for update- and enrollment function

Create a Pluto Network device. The readers connected to this line are used to write (add) an OSS application to the card and to update the cards when a card is presented on the reader before access is granted.

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

• Right click in the tree view and click on the icon “Add Line”:

• Save this record.

4.4.2 Add Orion door controller (Node)

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

• Select the Pluto line to which the Orion door controller is to be connected. Press right mouse-button: “Add Node”:

• Save this record.

4.4.3 Add online (Sirius) reader

4.4.3.1 Update reader

An update reader is required (per location) to read/write:

• the events (e.g. access granted, no access)

• the battery statuses of offline locks

• update access rights

• update the block list.

Browse to the menu: Installation | Hardware | Node.

• Select the Orion door controller Node and open this in the treeview (+).

• Select in the treeview Orion #1-4, prt 1 or prt2. Press right mouse-click, “Add Reader”

• Fill in a logical name for the reader

• Select the OSS update card data interpretation at the tab “general”.

• Select the correct provisioner group with the OSS update files.

• See for more settings and setting details chapter “Reader dialog details”

• Save this record

4.4.3.2 Enrollment reader

An enrollment reader is necessary to provide existing cards with an OSS application.

Browse to the menu: Installation | Hardware | Node.

• Select the Orion door controller Node and open this in the treeview (+).

• Select in the treeview Orion #1-4, prt 1 or prt2. Press right mouse-click, “add Reader”

• Select the correct OSS update card data interpretation at the tab “general”.

• Select the correct provisioner group with the OSS Enrollment files.

• See for more settings and setting details chapter “Reader dialog details”

• Save this record

4.5.1 Add Virtual line (DOM)

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

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

• Right click in the tree view and click on the icon “Add Line”:

• Save this record.

4.5.2 Add DOM controller (Node)

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”:

• Activate the check mark behind "Node online.

• Save this record.

4.5.2.1 Node tree-view items

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

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

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.

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.

• 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 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).

• 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 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.

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.

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 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:

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.

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.

• 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 displayed

• 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

  • 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.1.1 Access rights management

If you want to add or remove access rights to an offline lock, you can do this using the steps below.

Browse to the menu: Installation | Hardware | Reader.

1. Find the desired reader and unfold the reader with the + sign.

2. Click on the reader group list, here you can add or remove the desired reader groups.

3. after +- one minute the offline synchronization status of the lock will change to "the configuration is not in sync"

4. Get the configuration with the dom service app by syncing the app with the dom bridge.

5. Sync the offline device with the DOM service app.

6. Sync the DOM Bridge with the DOM service app.

7. after +- one minute the offline synchronization status of the lock will change to "the configuration is synchronized".

5.1.2 Remove a device

Browse to the menu: Installation | Hardware | Node

• Double click on the DOM controller node.

• Right-click on the reader to be deleted.

• Press on the button Delete.

• Open the Device unbound section below the DOM controller node.

• Select the device and change the state from “coupled” to “not coupled”.

• Sync the DOM service app with the DOM bridge.

• Sync the offline device with the DOM service app.

• Sync the DOM Bridge with the DOM service app.

• Remove the device from iProtect by using the delete button.

5.2.1 Access rights management

If you want to add or remove access rights to an offline lock, you can do this using the steps below.

Browse to the menu: Installation | Hardware | Reader.

1. Find the desired reader and unfold the reader with the + sign.

2. Click on the reader group list, here you can add or remove the desired reader groups.

3. The device and the RF-NetManager start communication and synchronize the changes automaticaly.

5.2.2 Remove a device

Browse to the menu: Installation | Hardware | Node

• Double click on the DOM controller node.

• Right-click on the reader to be deleted.

• Press on the button Delete.

• Open the Device unbound section below the DOM controller node.

• Select the device and change the state from “coupled” to “not coupled”.

• The device and the RF-NetManager will start communication and the device will be uncoupled automaticaly.

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.

It's important to note that switching from A1/B1 to the API is not mandatory.

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.

If you want to convert A1/B1 configuration to API, the system must meet the minimum requirements, see Chapter 2.1.

1. Browse to the menu: Installation | Hardware | Oss manufacturer

2. Select the used OSS element in the tree-view

3. Change the OSS Version from “A1” or “B1” to “Dom api implementation“

4. Browse to menu: Installation | Hardware | Node

5. Select the DOM OSS Node in the tree-view

6. Set the correct settings for the DOM bridge see Chapter 4.5.2

7. Discover the devices by using the wizard or manually see chapter 4.6.1.2

8. Set the correct unbound “device address/PHI” to the reader

9. 

10. Synchronize the locks by using the DOM service app see Chapter 3

Below is a detailed description of the reader settings:

The table below describes the other reader settings: