V9.7 01/05/20 UD0011 Page 136 of 177
This Document is uncontrolled when printed unless over stamped “CONTROLLED DOCUMENT"
17.12 ACCESS SCHEDULES
Access Schedules is a cost option that is used within TrakaWEB to impose time restrictions on iFobs/items or Users over
and above the normal access rights needed to access them.
Before it can be used, it will need to be enabled on your Traka Touch system by installing a configuration file. This is
usually carried out by Traka during production but if need be, you can add the configuration file to your own existing
system. Please contact Traka or your distributor for further details.
The functionality of Access Schedules is based on the following requirements:
To grant/restrict access, any users who are included in a schedule will only be allowed access to iFobs/items
when the schedule is active. Outside of this time, they will have access to no iFobs/items at all.
The access restrictions will not prevent a user from returning an item, only taking it.
Locking receptor strips on key cabinets and locker doors will physically restrict access to items however, Non-
Locking receptor strips are unable to enforce this.
If an Item is physically removed outside of the allowed access schedule (e.g. on a non-locking system) then
an ‘Item Removed outside Schedule’ event will be recorded.
A schedule restriction can be overridden on an Item (not a user) by a special role called ‘Item Access
Schedule Override’.
Software permissions will control who can administer the access schedules.
NOTE: A best practice would be to keep users and item/iFobs in separate Access Schedules to avoid
potential confusion.
NOTE: For a comprehensive guide to the functionality of the Access Schedules Feature Option, please refer
to UD0018 – TrakaWEB User Guide
17.13 REAL-TIME UPDATE SERVICE
The Real-Time Update Service is a cost option feature that will provide Real-Time State Change information from Traka
Touch to the Integration Engine v2 using a Message Broker on a system by system basis.
This in turn will provide events in real-time to a third party application based upon the current status of the items held
by the user which in turn can grant or revoke access rights to or from a user within a third party application when Item
State Changes are detected via RTUS. An example could be, preventing a user from leaving site if they have not returned
keys or assets.
The Comms status is monitored continually and email notifications can be sent if one or more components that make up
RTUS should fail. For example:
The Traka Touch System goes offline
The Message Broker goes offline
The Integrated Engine v2 goes offline
RTUS will work with the following products:
Traka Touch Key Cabinets (locking & non-locking strips)
Traka Touch Lockers with RFID
Traka Touch Lockers with RFID & FIFO
Other optional features such as Fault Logging, Fuel, Distance & Location, Item Booking
RTUS is not compatible with 16bit Systems or Traka Touch Lockers without RFID.
NOTE: For more information regarding the installation and configuration of RTUS, please refer to TD0165 –
Real time Update Service Installation Guide.
To Next Page
Loading...
