Other aspects of the LOCKSHOP module are listed and linked
in the column to the left.
Bulk Key Transfer
allows a range of keys to be moved in a single operation.
The function is accessed from Key Operations, in the
OPTIONS menu when a key record is being displayed. Clicking on the link takes
the operator to the Bulk Key Transfer screen. This screen allows a group
of keys to be moved together. It works as follows:
1. The operator goes to the Key Operations screen for
the blindcode of the key to be moved, and chooses BULK KEY TRANSFER. The
locksmith privilege is required to see and/or use this link. The operator is
taken to the Bulk Key Transfer screen.
2. The operator specifies the starting and ending ISSUE
SEQUENCE NUMBER of the keys to be moved. "KEY ISSUE NUMBERS" (which may include
non-sequential tags and/or alphanumeric characters) may NOT be used on this
screen. ONLY the FULLY NUMERIC Issue SEQUENCE numbers may be specified here.
These numbers will almost always match the Key Issue Numbers. In cases where
legacy AltIDs or iKeyIDs are in use, the sequence numbers can be determined from
the Key Inventory screen.
3. The operator specifies the OLD STATUS of the keys he
is moving. Only keys within the range which MATCH the OLD STATUS specified will
be affected. [If the OLD STATUS is "ON HOOK" (i.e. the locksmith is moving the
keys out of a key issue point) then the appropriate key issue point must be
specified on the Key Issue Point field.] This allow for such operations as
moving all keys out of a key issue point - only the keys on hook will be
affected, while issued/lost/stolen/destroyed keys will NOT be affected by the
move.
4. The operator specifies the NEW STATUS of the keys he
is moving. All the keys which match the specified old status will be changed to
the specified new status. Again, if the NEW STATUS is "ON HOOK" (i.e. the
locksmith is moving keys onto a hook) the issue point must be specified.
5. The operator types a COMMENT for the log, and clicks
SAVE. While it is highly advisable to put a comment in the Comment
field, it is not necessary when performing the transfer. If you do not put
a comment in the field, KeyNET will place a default comment of "Bulk Transfer"
in the field.
6. All the matching keys are moved, and history records
are created for each key as well showing the move.
This screen allows for many
maintenance operations, such as:
1. Delivery of a new batch of keys to a key issue
point.
2. Transfer of a batch of keys from a key issue point to
a locksmith, or from a locksmith to a key issue point.
3. Marking all keys at a key issue point as DESTROYED.
4. Marking all lost keys as BACK ON HOOK...etc. etc.
As you will note, the OLD and NEW status settings can be
one of any of the five following choices: DESTROYED, ON HOOK (at specified key
issue point), ISSUED TO ME (issued to the operator/locksmith), STOLEN, LOST.
This allows for many combinations of operations.
NOTES:
1. To ensure accountability, it is NOT possible to
BULK-ISSUE a group of keys to "somebody else." A user may only bulk issue keys
to THEMSELVES, for the purposes of transport.
2. It is not possible to direct-transfer keys from one
key issue point to another, because this is not possible in real life. In real
life, the locksmith takes keys out of one issue point (Transfer from On Hook to
Me), physically carries them to wherever they're going (while Issued to Me),
then puts them on the hook at another key issue point (Transfer from Me to On
Hook.) Therefore, the system REQUIRES two operations for this scenario.
|