|
Other aspects of the LOCKSHOP module are listed and linked
in the left hand column.
Before starting, insure that your Systems Administrator has licensed and CONFIGURED your
privileges to allow you all of the features you will need from the Multiple Key
Issue
Module.
MULTIPLE KEY ISSUE (MKI) is a powerful tool for controlling keys. This
feature allows Lockshop and Key Issue functions to be used together in harmony.
Lockshop functions can now administer to remote Key Issue sites as if they were
in the same room.
Key Issue location operate independently; but, in concert with each other.
Personnel may work at a number of sites and have keys issued from multiple
sites. They may also transfer between sites quickly and easily.
-
Personnel only need to be entered into the system once.
-
Issue records are a composite of all sites (you may turn in keys at any
MKI site) (individual records are complete with all keys issued).
-
Rapid look-up of Key Identification
-
Rapid look-up of Hook to Key
-
Rapid look-up of Key to Hook.
-
Each MKI site can control Key Issue Authorizations.
-
Each MKI site can electronically order keys.
-
Each MKI site can produce reports specific to their MKI site.
-
Each MKI site can issue and return keys with ease.
-
Each MKI site can print, and have signed, an individuals key record.
-
Each MKI site can utilize e-signature, for a paperless system.
-
Each MKI site can track DELINQUENT KEYS.
-
Each MKI site can track Lost or Stolen Keys
-
MKI allows sites to reduce the number of keys in their inventory.
-
MKI sites can create and administer KEY RINGS.
-
MKI sites can update Photo IDs and Pin Numbers.
-
MKI aids in the enforcement of site Policies and Procedures.
-
Complete control of ACCESS to YOUR MKI site.
Lockshop personnel service each MKI site as an independent location, with
hook assignments at each site being independent of each other.
-
Lockshop can preview and advise MKI sites of potential problems.
-
Lockshop can insure that keys are returned to their proper MKI site.
-
Lockshop can respond quicker and more efficiently, knowing the number of
keys issued and in inventory.
-
Lockshop can review lost and stolen keys to advise of rekeying issues and
problems.
-
Lockshop can interface with Card Access databases, for card issue and
system updates.
Now there is a quick and effective way of MANAGING KEYS at Multiple Key Issue
locations. Imagine, other MKI site administrators being able to assist at
critical issue times, or fill-in while you are on sick leave or vacation.
MKI provides it's sites with valuable resources, while maintaining the highest
of Security Industry standards and practices.
How it works:
eKeyRequest is specifically different
than the normal Authorizations used in a paper trail authorization path.
With the "regular" authorizations (that existed already) are just people who may
sign paper orders for keys. They have nothing to do with electronic
authorizations. Conversely, the field added in the Department
section of Code Management is the single electronic authorizer for the
department, which has nothing to do with paper authorizations.
The reasons for this are many -
primarily because it just would work any other
way - but other reasons include such
things as: There may be 30 people in a
department "allowed" to sign
authorizations for keys... but those 30 people
would NOT want to be notified every
time an electronic authorization came
through. Additionally,
because there is no "paper" trail, it's important to
severely limit the people in a
department who can electronically authorize.
This should be a single point of
contact (point of responsibility) in each
department who can, of course, check
with others in their department to
confirm authorizations, but who is
the sole person responsible to ENTER that
into the system.
Moreover, because Key Authorizations and "eKeyRequests" are
two entirely separate systems, and
work differently, they are necessarily set
up differently (Eventually we
may allow the two types of integrate ).
The "normal" (paper) authorizers
(unlimited numbers and types) go into the authorization system.
eKeyRequests use a department-level authorization only, allow a single person
per department only, and that person is coded in at the department code screen.
|
