*iProtect™ Multisite

Owned by Tom Polman
Last updated: Sept 14, 2022
7 min read

Installation Manual | IM-20210309-TP-14

iProtect Access / Security | Functionalities |

This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.

1 Introduction

This document describes the Multi Site functionality of the iProtect system. With this functionality an iProtect
operator can manage multiple iProtect systems through the user interface of one central coordinating iProtect server. All alarms, events and maps are received on the operator console of the central iProtect system. This system also can support multiple displays to increase the usability of the system and give the operator a better overview of the situation.

For the multi site iProtect functionality, it is important that all iProtect servers (the Multi site server and the
monitored local servers) are running the same iProtect version.

When it is necessary to also share the persons and access keys between multiple servers, the multi-site
functionality can be combined with the iProtect server synchronization feature to accomplish this. This
functionality is described in the manual: iProtect Server Synchronization.

2 Preparation

2.1 License

The Multi Site iProtect functionality becomes available with a special license on the central coordinating
iProtect server:

  • License number 5200: iProtect Multi-site enabled

The value of this license determines the number of associated iProtect server that this coordinating server can manage.

2.2 Add servers

Adding iProtect systems to the multi site management server is done via the menu:

Menu | Installation | Settings | Server

By default the settings of the local iProtect server (in this case the multi site iProtect management server) are
already present in the tree view. The name of this server can be modified. The other parameters, like IPaddress

and the checkbox to monitor notifications should not be modified.
An iProtect system that should be monitored by this multi site iProtect can be added via the right mouse button in the tree view, and selecting Add server. For this server the monitoring of the notifications/alarms and of events can be configured separately.

For this new server, the following parameters can be configured:

  • • Name: The name of the new monitored server

  • IP Address: The hostname or IP address of the new monitored server

  • Monitor notifications: A checkbox with which can be selected whether or not the notifications and
    alarms of this server are actively monitored. By unselecting this checkbox there is no active
    connection between the multi site server and the monitored server. When the checkbox is selected
    additional configuration parameters are shown:

  • Port: The port number on which the multi site server should connect with the monitored server.
    Usually this should be port 443 (HTTPS).

  • Secure connection: This checkbox determines whether the communication should be encrypted
    (https). Leaving this box unchecked is not recommended.

  • Login name: The name of the System user on the monitored system, that is used by the multi site
    system to synchronize the data from the monitored iProtect system. This System user should have
    sufficient (but not too many) authorizations and it is advised to define the External service user
    property for this System user, so that the Multi site iProtect server can always log into the monitored
    server.

  • Password: This is the password of the System user on the monitored system.

If (a selection) of events on the monitored system must also be stored on the multi site iProtect system, this can also be configured:

  • Store: This checkbox determines whether certain events from the monitored system should be stored
    on the multi site iProtect system.

  • Timezone: Here the time zone of the monitored system should be configured. When the iProtect
    systems are in different time zones, their timestamp of the events will be corrected to the local
    timezone of the multi site iProtect system.

  • Authorization group: If an Authorization group is selected here, the events that are stored from the
    monitored system will get this Authorization group.

  • Last processed event: This field displays the ID of the last event that was stored from the monitored
    server. It is used as the starting point for synchronization when the connection between the multi site
    server and the monitored server has been lost for a period of time. When this field is reset to zero all
    events that are still present in the database of the monitored system are re-transmitted.

Which events are transmitted to the multi site system must be configured on the monitored system. For each
event type individually, the user can decide if events of this type are transmitted to the multi site iProtect server.

2.3 Multi iProtect Manager

On the multi site iProtect server at least System user must be given the role of Multi iProtect Manager. This
can be done with the corresponding checkbox on the System user form. With this role the System user can
use the iProtect user interface of the monitored iProtect system through the user interface of the multi site
iProtect system.

It is important that the System user, with exactly the same username and password is defined on both the
multi site iProtect server as on the monitored iProtect server. On the monitored iProtect server this System
user does not need the Multi iProtect Manager setting.

To summarize: For this Multi iProtect service, on the monitored iProtect server, 2 System users must be
defined:

  1. External service user for the synchronization of data

  2. System user for the use of the iProtect GUI

2.3.1 Alarm handling

A System user that is a multi iProtect manager can have a modified behavior of the alarm handler. If a multi
iProtect manager has multiple displays on the workstation, it can be handy to split the alarm handler over 2
displays. Usually, if a Keymap is associated with an alarm, this Keymap can be opened in the Alarm handler
by pressing a button.

For the multi iProtect manager, a system setting is available via:

Installation | Authorization | System user | System settings | Alarm handler | Separate floor plan

By setting this value to yes (checking the checkbox) the alarm handler will open the floor plan/Keymap (right)
directly besides the alarm handling screen (left).

This setting must be made for this System user on both the monitored iProtect system and the multi site
iProtect system.

2.3.2 Keymap

The Keymap can also be split over 2 monitors for the multi iProtect manager. On the left side a default Keymap can be shown that contains the statusses of the monitored iProtect servers. If one iProtect server is selected, the defaulkt keymap of that iProtect server is shown on the right side.

For the multi iProtect manager, this setting is available via:

Installation | Authorization | System user | System settings | Keymap | Multi alarm split screen

By setting this value to yes (checking the checkbox) the default Keymap will be able to display the default
Keymap of the multi site iProtect server and a monitored iProtect server simultanuously.

2.4 Event storage

On the monitored iProtect server, it can be defined which event types will be transmitted and stored on the
multi site iProtect server. This is done via the menu:

Menu | General | Settings | Event settings | Event

For a selected event, under the sub-menu Event notification definition there is a check box Remote store.
By checking this checkbox, all events of this event type will be sent, and stored on the multi site iProtect server.

3 Operation

When a system user is a Multi iProtect manager a number of special forms are available to support the
monitoring and management of multiple iProtect systems.

3.1 Alarm handing

The alarm handler for a multi iProtect manager has a different appearance as usual.

In the list of pending alarms, on the left hand side of the screen, the alarms of the multi site iProtect server and of the monitored iProtect servers are combined in one list. The alarms from a monitored site are indicated with Remote site transaction or alarm and the name of the remote site concerned.

At the bottom of the left hand side panel, an icon is displayed that represents that communication status with the monitored iProtect systems.

If the split screen option is enabled (see paragraph 2.3.1), the right hand side of the alarm handler will display the associated keymap or video images.

3.2 Key maps

The multi site iProtect user can open the multisite floor plan (Keymap) by opening the default floor map
General | Keymap
or directly via the following URL:

http://<ip address of iprotect>/Webcontrols/multisitealarmmap.html

Depending on the system user settings, the keymap can consist of 2 panels suitable for 2 monitors. On the left panel the default Keymap of the multi site iProtect manager is displayed. On the left a Keymap of a monitored iProtect server can be displayed.

On the Keymap of the multi site iProtect manager icons can be placed that represent the status of the
monitored iProtect servers. (Table: SITE, Column: ALARMSTATE)
The status of a monitored iProtect server will be symbolized on the default floor map with certain default icons:

On the top left side of the Keymap, the “Home” icon is placed, that allows the system user to return to the
default Keymap.

3.3 Multi Site Viewer

With the multi-site viewer, it is possible to open a general iProtect form for all sites.

https:// <ip address of iprotect>/Webcontrols/multisiteviewer.html

This multi-site viewer has to be started from the main server. The displayed sites in the treeview are the
locations, defined under

Installation | Settings | Location

Also, other pages of iProtect™ on desired location can be opened via multi-site viewer.
For example:

https:// <ip address of iprotect>/Webcontrols/multisiteviewer.html?lasttransactions.html

 

Or https:// <ip address of iprotect>/Webcontrols/multisiteviewer.html?browseperson.html