WSE • 3/21/97 16720 — 10 SE 6000 Security Management System
11. Project Schedules:
a. Implement the capability to use project schedules to alter access to certain doors by activating
and de-activating “projects” in the SE 6000. This functionality shall work with access codes
and privilege levels to provide another level of clearance checking to the system.
b. Doors per project: 16 maximum. Doors included in an active project can be accessed only by
cardholders who are assigned a project that includes that door.
c. Projects: 128 maximum. The system shall provide the capability to define, modify, add and
delete projects.
d. Access Override:
1) Implementation of an Access Override feature shall enable one to quickly turn on and off
access, manually or by date, to particular sites of a facility.
2) This feature shall incorporate Access Override Codes (AOC), each of which may be given
a description, a range of dates, and whether access shall be allowed or denied during the
range of dates.
3) Subsequently, these codes may be assigned to one or more of the access privileges
assigned to each keyholder. Therefore, each cardholder's individual Access Code, or
Group Records may be assigned an Access Override Code. As a result, in addition to
controlling access by door, time of day, and day of week, access privileges may also be
controlled by date.
e. The system shall not only check access by door, time and day, it shall check to see if access
has been limited to a range of dates, and whether access should be allowed or denied through
that range of dates. This method of implementation shall, therefore contain several
properties, as follows:
1) Identical Access may be assigned to a group of cardholders, but restrictions may be
applied to a subset of cardholders.
2) Identical Access may be assigned to a group of cardholders, but restrictions may be
applied differently.
3) Different Access may be assigned, subject to the same date restrictions.
f. Keyholders whose Access Privilege Records have not been assigned an Access Override Code
shall be unaffected by this feature. This feature shall be functional for Host decisions.
E. System Management: The required system shall perform all of the following functions:
1. Simple System Administration:
a. To administer Host computer, the system shall provide control of all system administration
functions via menu accessed screens.
b. There shall be no need to memorize complicated commands or to learn the syntax of the
UNIX operating system.
c. System administrative functions shall include:
1) Adding and deleting system users.
2) Maintaining user passwords.
3) Checking database statistics.
4) Performing system and database backups.
5) Defining and maintaining program security levels.
6) Displaying current system activity.
7) Performing transaction archives.
8) Initiating data transfer to remote devices.
9) Defining and maintaining user-controlled fields.
10) Performing alarm transaction clean-up.
11) Displaying those users currently logged on the system.
12) Key holder loading.
(180 Seiten)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern