*iProtect™ TrakaWeb
- Tom Polman
- Arnout van Wanrooij
- Lennert
- MB
Installation Manual | IM-20221223 iProtect Access / Security | Coupling |  | 
|
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 is the installation and operation manual of coupling between the iProtect system and the TrakaWEB key management system for Key Cabinets. TrakaWEB is the new web based management software for Traka Key Cabinets that replaces the old SQL server based Traka32 software. iProtect supports integrations with both software version.
2. Key Cabinets
A key cabinet is a lockable cabinet that can hold a large number of key fobs. These key fobs are locked in specific positions that are monitored and controlled by the management software.
By presenting an identification means (i.e. access card) to the reader that is connected to the key cabinet, the cabinet is unlocked. The management system has a database with persons and key authorizations and will unlock the key fobs that the person is authorized to. The person can take out one or more key fobs. This is registered by the management software. If, at a later moment the key fobs are replaces by the person, this again is registered.
2.1 Functionality of the coupling
The coupling between iProtect and the TrakaWEB system offers the following functionalities:
Share user credentials and provide access to the cabinet
Log events from the Traka system
Register key fobs that are taken out and returned
Prevent persons from leaving a certain area if (s)he still possesses key fobs
Generate reports on possession of key fobs
Generate alarm if key fob is not returned in time
iProtect can synchronize access cards to open the cabinet. The complete management of the key fobs must be done within the Traka application.
3. Configuration
3.1 License
To activate the iProtect TrakaWeb service a special license is required:
License number 15 – Traka Support
3.2 Service configuration
A new TrakaWEB service can be created in the Database Link form.
In iProtect, browse to menu: Installation | Settings | Database Link
Right click in the search field and choose “Add Database Link”
Select: Traka web
The details of this service appear:
Menu part | Label | Description |
|---|---|---|
Status | Activate | With the Active checkbox the service can be started and stopped. |
Remote server | The information necessary to connect to the TrakaWEB server can be provided in this panel. | |
Status | This is a read-only field that shows the communication status of the connection with the TrakaWEB service. | |
Login name and Password | These credentials will be used by the iProtect system to connect to the remote TrakaWEB service. This has to be an account with access rights on the Windows server on which the TrakaWEB service is installed. It should be an account of the type PC-NAME\USERNAME or DOMAINNAME\USERNAME. These credentials need to be the same in the Traka application, this configuration in Traka you can find it under the Traka monitor application -> Tab Web Service -> Authentication | |
Host name Traka server | is the hostname of the TrakaWEB server. In the Traka system this is defined as the service end point. This hostname must be resolved by the DNS server defined in the iProtect server or, if no DNS service is defined, it should be in the /etc/hosts file on the iProtect server. | |
Port | This is the port number that is used by the TrakaWEB Service. The default port number is 10700. | |
Time out | This is the duration in seconds that the iProtect waits for the TrakaWEB service to respond before deciding to close the connection and retry the communication. By default this time out is set to 45 seconds. | |
Logging | By entering a time and saving the record, logging will be enabled. The logging will be available in the User Interface log in the Maintenance page. The logging will be disabled automatically after x minutes to prevent filling up the filesystem, because this logging can be quite large. | |
Parameters | The parameters in this panel determine additional features of the TrakaWEB service. | |
Card group | The members of this card group will be synchronized with the TrakaWEB database. So if a person needs access to the Traka cabinet, the card should be a member of this card group. | |
IP address iProtect | This is the IP-address of the iProtect server. The TrakaWEB system will send its event to this IP-address. If the iProtect server has multiple IP-adresses, the IPaddress should be used here that the TrakaWEB can connect to. | |
Card data interpretation | This is the card coding the card reader on the TrakaWEB system will use. It can be required to define a different card number presentation under the card data interpretation for the TrakaWEB system. This system uses a different card reader then the access card readers in the iProtect system. For example, for Rijkspas the access card readers produce a 8-digit hexadecimal number while the reader on the Traka system produces a 10-digit decimal number. | |
Authorization | On the authorization panel you can determine the accessibility of the data that is entered in the iProtect database by the service. If you select an authorization group all data that is linked to the TrakaWEB service automatically also has this authorization group. Furthermore, you can determine which data can be read/written by this group. | |
3.3 Area
To decide whether a person is not allowed to leave the building if they still have a key fob, this can be enforced in the Area menu.
In iProtect, browse to menu: Access | Settings | Area
Select an existing area
Activate or deactivate Key cabinet area blocking
3.4 Person
The area blocking described above is a general feature of that Area and is effective for all persons / access cards. To exclude certain persons from this blocking, a checkbox is available at Person details.
In iProtect, browse to menu: General | Person
Select a person who needs to be exclude of the Area blocking functionality
Check by Key cabinet: Ignore area blocking. By checking this checkbox this person is excluded from the blocking and is allowed to leave the area while in possession of a key fob.
4. Operation
4.1 Synchronization
When the coupling with the TrakaWEB service is established, the follwing information is synchonized between the iProtect database and the TrakaWEB database for the cards that are a member of the card group defined in the service details form:
Person Name
Card number
Validity
Expiration date
4.2 Key fob handling
When a person takes a key fob from the Traka system, the key fob details will be displayed
in the treeview of the person.
In iProtect, browse to menu: General | Person
Select a person in the treeview
In the details screen of the key fob, additional information is presented:
Person: the person who has the product in possession
Description: description of the product. Usually, the name in the TrakaWEB
systemType: the type of product. In this case the key fob
Lost: with this checkbox the administrator can indicate that this person has lost this key fob. Now the person is allowed to leave the area and will not be blocked, even if this is activated.
4.3 Events
Incident description | iProtect Event |
|---|---|
When the card number is already present in the TrakaWEB database | Synchronization failure (48) => ACCESSKEY (86): 000003, PERSON (1557): John Doe, RCN card number (29): |
When a key fob is taken from the Traka cabinet iProtect will generate an Item removed event: | Item removed (118) => PERSON (1531): John Doe (25): IFob, Comment 1 (114): Key ring 10) 745576080000 |
When the key fob is replaced an Item returned event is generated: | Item returned (119) => PERSON (1530): John Doe (25): IFob, Comment 1 (114): Key ring 10) 745576080000 |
In the TrakaWEB system the maximum time that a key fob can be in someone’s possession can be configured. If it is not returned in time an Item overdue event is send to the iProtect system: | Item overdue alarm (105) => PERSON (1531): John Doe (25): IFob, Comment 1 (114): Key ring 10) 745576080000 |
If the key fob is returned after this an Item overdue resolved event is generated: | Item overdue alarm resolved (106) => PERSON (1530): John Doe (25): IFob, Comment 1 (114): Key ring 10) 745576080000 |
The Area blocking that is used to prevent that persons leave an area while in possession of keys relies on the up key update events from the TrakaWEB server. If, by some reason the connection between iProtect and TrakaWEB is not available, the Area blocking will be disabled automatically, to prevent the situation that people can not leave even afer returning the keys. |
|
4.4 Reporting
To get an overview of the keys that are in possession of persons, a number of reports are
available:
In iProtect, browse to menu: Access | Overview | Products in possession | Person
This shows which item was taken by which person.
By changing the search category, an overview per product type can be obtained or a list of all lost (or not lost) objects can be made
In iProtect, browse to menu: Access | Reports | Products in possession per person
This report shows which person has certain keys in possession.