...

Expand

title	How to setup the online hardware...

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

Field	Content
Name	Logical name for the Line
Features
Type	Network device.
Host type	Pluto
Communication
Active	Activated
Active (with Nodes)	Activated
Status
Function of the line	Physical line
Address
IP Address	IP address of the relevant pluto

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

Field	Content
Name	Logical name of the Node
Status
Node online	Active	When activating the Node, the Orion will be detected automatically.

Info
When the line is active and the Orion is already connected to the Pluto, Press the button “Discover”. The Orion (with connected card readers) are created automatically.

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.

Info
When using multiple locations, each location should get there own site code. Select the corresponding Card data interpretation with the correct site code.

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

Info
The reader is also created automatically by pressing the discover button on the pluto line

Note
For both the update reader and the enrollment reader, the update card data interpretation must be selected, the provisioner files determine whether a reader is an update or enrollment reader.

...

Expand

title	How to setup the DOM controller...

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

Field		Content
Name		Logical name for the Line
Features	Type	Server
Features	Host type	Server
Status		Virtual

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

Field

Content

Description

Name

Logical name of the Node

Features

Node type

OSS

Network

HTTP port

443

Port number of the connection to the DOM bridge

IP address

e.g. 192.168.1.120

Unique IP address of the DOM bridge

Password

Password of the DOM Controller (only visible for system users with Installer rights)

Set keys (SC)

Once the connection is established, you can modify the password to a unique one by clicking on the "Set Keys (SC)" button.

General

Provisioner group

Customer specific

Customer specific, supplied by TKH-Security B.V.

Other

Offline

OSS manufacturer

DOM API-implementation, see chapter 4.1.1

Bluetooth

Default TX power (iBeacon)

Transmit power 0 dBm

Logging

Log minutes

Installation option

Link to existing reader
Link to new reader

Chapter 4.6.1.2 and 4.6.1.3

Temparary login (root or installer only)

Button

Fetch

Retrieve the temporary users from the DOM controller.

Info
After updating iProtect or a restart of the system, the temporally users will be deleted.

Button

Add

You can utilize this button to create a temporary user, such as a user for the mobile app or a system user requiring temporary access to the DOMPloy application.

Info
After updating iProtect or a restart of the system, the temporally users will be deleted.

Select user

Delete button

Delete selected user

Edit button

Edit selected user

Global settings (root or installer only)

Button

Fetch

Mobile
Card

Get detailed system information

Field

Description

Discover

When a new device is added to the system (e.g. NetManager, lock or door handle), it can be discoverd discovered in iProtect by pressing this button.

Backup

Pressing the button will back up the configuration of the DOM controller. The backup is saved with the date/time of the moment of creation.

Activate the check mark behind "Node online.
Save this record.

Info
When the connection is successful, the status check mark behind "connected" will turn black.

Note
Temporary users will be automatically deleted when the OSS service restarts.

4.5.2.1 Node

treeview

tree-view items Image Modified

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

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.

...

Expand

title	How to add offline devices to the system...

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.

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.

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

Info
If the status is different, you should check this within the DOM service app by first synchronizing the DOM service app with the DOM bridge and then synchronizing the locks.

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.

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

Info
By using this way of configuration, only one synchronization with the device is needed

Info
If you change access rights or other reader settings after this step, synchronization must take place again for the device in question.

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.

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

...

Expand

title	How to update or remove online devices...

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.

Find the desired reader and unfold the reader with the + sign.
Click on the reader group list, here you can add or remove the desired reader groups.
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.

6.

...

6.1 Reader dialog details

...

title	Detailed reader dialog information...

...

Migrate the OSS configuration from A1/B1 to API

This section describe how to convert an existing dom configuration (A1/B1) to the API config

Expand

title	How to convert A1/B1 config to API

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

6.1 Steps to convert A1/B1 to API configuration

Browse to the menu: Installation | Hardware | Oss manufacturer
Select the used OSS element in the tree-view
Change the OSS Version from “A1” or “B1” to “Dom api implementation“
Browse to menu: Installation | Hardware | Node
Select the DOM OSS Node in the tree-view
Set the correct settings for the DOM bridge see Chapter 4.5.2

Note

It is essential to configure the correct provisioner group at the DOM OSS node, as this will transmit the configuration and keys to the Bridge.

If an incorrect provisioner is selected, the locks may be programmed with the wrong keys, rendering them incompatible with the existing cards.

Discover the devices by using the wizard or manually see chapter 4.6.1.2
Set the correct unbound “device address/PHI” to the reader
Image Added
Synchronize the locks by using the DOM service app see Chapter 3

Info
When migrating a system from A1/B1 to API, all locks must be re-synchronized

7. Extensive information

7.1 Reader dialog details

Expand

title	Detailed reader dialog information...

Below is a detailed description of the reader settings:

Field	State/Status	DOM ONLY or DOM & ORION	ORION ONLY
Name		Logical name for the Reader or same as DOM Device name
Hardware			ORION ONLY
Offline reader	Unique DOM reader ID	Automatically generated unique readerID which can be changed manually.	not available
Sub number	Unique IPROTECT sub number	Automatically generated unique Sub number which can be changed manually.	Read only field when the on-line card reader is connected the Pluto.
Status			ORION ONLY
Offline synchronization status	Not coupled	Not coupled
	The coupling has been started	The coupling has been started
	The configuration is not in sync	The configuration is not in sync.
	The configuration is being synchronized	The configuration is being synchronized
	The configuration is synchronized	The configuration is synchronized
	Connection is lost	Connection is lost
	Decoupling process has been started	Decoupling process has been started
Device address / PHI		Select the correct DOM Device	not available
Cosmos Access			ORION ONLY
Enable Cosmos Access		By enabling Cosmos Access on a reader, a new type of identification is activated.	By enabling Cosmos Access on a reader, a new type of identification is activated. Only available when using SIRIUS IX card readers
Force remove button		When reader cannot be unassigned (broken), it will remove the reader from the Token Autority. Be aware! When doing this action and the reader will be re-used again for Cosmos Access, the reader must be sent back to TKH-Security.
Synchronization status	Undefined	No status
	Reader sent	Reader is signed up with the TokenAuthority
	Reader assigned and tokens sent	Intermediate stage in assigning a reader
	Reader assigned	Reader is assigned and can be used with Cosmos access
Interaction	All - In background	The mobile device does not need to be unlocked before it is presented to the reader. When opening the app nearby readers can be selected and opened in the app at the touch of a button
	Scan & Go - Device unlocked	The mobile device does not need to be unlocked before it is presented to the reader
	Scan & Go - In background	Nearby readers can be selected and opened in the app at the touch of a button
	Scan & Go - and Select & Go	not available	Mobile device needs to be unlocked before presenting it to the reader. Select & Go can also be used for this reader. Select & Go only supported when using SIRIUS IX card readers
	Select & Go	not available	Nearby readers can be selected and opened in the app at the touch of a button Select & Go only supported when using SIRIUS IX card readers
Entity state	Unknown	Unknown
	To be assigned	Reader needs to be assigned
	To be unassigned	Reader needs to be unassigned
	Assigned	Reader is assigned

The table below describes the other reader settings:

Field	State/Status	DOM ONLY or DOM & ORION	ORION ONLY
General / General
Card data interpretation		Select the correct Card data interpretation (Card data interpretation: update)	Per reader: 1x OSS update per location 1x OSS enroll
Provisioner group		NA for DOM	Per reader: 1x OSS update 1x OSS enroll
Reader mode (only available when reader is in connected to Device manager, when reader is on-line)	Locked	The door is closed. Access not granted.
	Normal	Access granted.
	Open	The door is open.
Door behavior / Door control			ORION ONLY
Unlock time (1/10 sec)		Default unlock time (3 sec - Default)
Alternate Unlock time (1/10 sec)		Default unlock time (3 sec - Default)
Device info			ORION ONLY
Public key for Cosmos		Public key is shown when the DOM controller and Mobile access are configured correctly	not available
Bluetooth / TX power (iBeacon)	Transmit power 0 dBm	Strength of the bluetooth signal can be adjusted. Do not adjust this at random! (0 dBm - Default)	not available
Fetch		Show all data from the device (registered at the DOM controller)	not available
IPROTECT ACCESS			ORION
Person		The person to check if it has a Mobile key (token) for the specific door/reader
Fetch		Shows which person(s) has a Mobile key (token) for the reader

...

7.2 DOMConnect Manual

View file

name	DOMConnect Manual.pdf

Versions Compared

Old Version 2

New Version 3

Key