Auditing
Kaba Ilco Lodging Access Control System 183
03/20/2007 7:49A 1
PROGRAMMING
Auth 200 FDU No. 1
Sequence ID 8751-001
Creation 03/19/2007 3:54P
Most recent audit entry in memory,
showing that a programming keycard was
used (to download the audit), and the
sequence ID of the keycard (to identify
the staff).
03/20/2007 7:48A 2
GUEST
Auth 200 FDU No. 1
Sequence ID 9705-005
Creation 03/20/2007 7:48A
Second most recent audit entry showing
the usage of a guest keycard, time of
entry, and the user authorization level that
created the guest keycard.
03/20/2007 7:46A 3
OVERRIDE
Auth 200 FDU No. 1
Third most recent audit entry showing the
usage of the FDU to perform an override
on the lock, and the user.
Figure 7.1: Sample of printed lock audit, includes access and automation information.
The FDU can store the full audit trail from up to 10 locks at a time. Each audit may be
selected individually, scrolled on the screen, printed, saved on a PC or deleted from FDU
memory as required. If a lock is audited twice, the top audit in the Front Desk Unit will
always be the older one.
Auditing a RAC is done in the same manner as auditing a lock.
7.1.1 Auditing Locks Using the FDU
IMPORTANT: Do not attempt to read or encode any keycard (including
Authorization, Programming and Initialization keycards) while the
communication cable is connected between the FDU and the lock
or RAC. Connect the cable just before sending or reading the
information.
Purpose: To obtain the audit trail stored in the lock’s non-
volatile memory.
Minimum keycard required: Programming Authorization
Equipment Required: FDU
FDU to lock communication adapter
Programming keycard
To Next Page
Loading...
