IDenticard PremiSys

This document is intended for the user to be able to gain a greater understanding of the IDenticard integration within SureView. This document will cover the following:

• Features
• Prereqs
• Alarm Configuration 
• Installation
• Alarm Configuration on SureView

Features

Cloud

Prerequisites

1. The PremiSys server requires the following PremiSys API components to be installed and licensed:
   1. QueryAPI (default port 9002)
   2. ActionAPI (default port 9002)
2. The Identicard system must contain a user that Sureview can use for authentication (note, no permissions are needed for the user). 

Note: to change the ports of the PremiSys API components, edit the 'ConfigValues' database table in the PremiSys database, changing the ports then resetting 'IDenticard Windows Service' in services.

Alarm Configuration

Overview

The Diagram below shows an overview of the architecture of the IDenticard integration. The boxes in green represent the components specific to this integration. The IDenticard Alarm Receiver windows service connects to the IDenticard Router service using the device host and port details as described below. It receives transactions from the IDenticard Router and converts them to SureView alarms. The device integration uses the IDenticard Router service to control relays/doors etc.

Service Configuration

SVidenticardPremiRouter service on PremiSys Server:

This service resides on the PremiSys server and connects to the PremiSys API and Database running on the same server.

Settings include:

• Connection information for the following PremiSys components (this is usually all installed on the same server as PremiSys).
  • PremiSys database
  • PremiSys cardholder database
  • Query API
  • Action API

Installation of IDenticard

This section will walk you through how to install the IDenticard integration from the release repository. There will be screenshots showing you how to do each step to ensure you have a smooth installation.

To start the installation process you first need to open the setup exe found within the setup immix setup folder. Once you have opened setup.exe as admin you will be presented with the below screen. This screen below is where you will select the installation location of your immix cloud file. 

once you have gone through and added your database details and verified the connection you can then go ahead and search for the IDenticard integration. As seen below please search for IDenticard and select both options.

For reference please install IDendticard version 1.0.0.2 and SVDenticardTransactionReceiver version 1.0.0.3.

Once installation has finished, head over to windows services on the server and check the following service is running:

• SVIDenticardReceiver

This service is required for this integration to work.

Now that you have finished the installation of IDenticard you can now go ahead and read on to the next section which walks you through how to configure the alarms within the SureView dashboard.

Alarm Configuration within SureView

The alarm configuration for IDendticard resided directly within the SureView application. You will configure the alarm to meet your specific needs.

To create an alarm for IDendticard you first need to create a Device. To do this you need to go into 'Device Setup' within SureView and then configure the device to meet your needs, ensuring that you set the device type to 'iDenticard'. This has been highlighted below for you as a visual aid.

Once the device has been set up, you can then create an alarm that is associated with the newly setup device. To do this you will need to go into 'setup alarms' and then create a new alarm. In here you will be able to select the area of the alarm, the device to asociate the alarm with and then you can set the iDenticard type. The types have multiple options in the drop down menu. You can see this in the screenshot below.

Once you have created your alarm, you can go ahead and test it by running a test trigger. If all looks as you would expect then you have successfully created your alarm and device using the iDenticard integration. Below I have triggered my 'Access denied' Alarm that was created using this integration. Once the alarm has been triggered you can close it off or if you have added actions to the alarm complete them before closing it off.

Input values

The Input1 and Input2 values determine how alarms are matched

• Input1 = the identifier of the item sending the alarm.
• Input2 = the type of item sending the alarm from the table below.

For example: If you create an alarm in Immix with Input1=3 and Input2=7 that will be an alarm from Monitor Point number 3 (7 being the type for "Monitor Point" from the table below).

Item types:

• 0 = Controller Diagnostics
• 2 = Monitor Points on Controller
• 3 = I/O Diagnostics
• 4 = I/O Communications
• 5 = I/O Enclosure Tamper
• 6 = I/O Power Monitor
• 7 = Monitor Point
• 8 = Control Point
• 9 = Door/Elevator/Rack
• 10 = Door/Elevator: Reader Tamper Monitor
• 11 = Door: Door Position Sensor
• 12 = Rack
• 13 = Door: REX Input
• 14 = Door: Alt. REX Input
• 15 = Time Zone
• 16 = Procedure (Action List)
• 17 = Trigger
• 18 = Trigger Variable
• 19 = Alarm Point Group
• 20 = Access Area
• 21 = Door/Elevator: Alt. Reader Tamper Monitor