Westinghouse SE 6000 Product Manual
  1. Manuals
  2. Brands
  3. Westinghouse Manuals
  4. Security System
  5. SE 6000
  6. Product manual
Westinghouse SE 6000 Product Manual

Westinghouse SE 6000 Product Manual

Westinghouse se 6000 security management system standard product manual
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
SE 6000
SE 6000
STANDARD
PRODUCT
MANUAL
Westinghouse
Security Electronics
an ISO 9001 certified company
P/N 66107919001, Rev. F
S
ECURITY
M
ANAGEMENT
S
YSTEM

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SE 6000 and is the answer not in the manual?

Questions and answers

Related Manuals for Westinghouse SE 6000

Summary of Contents for Westinghouse SE 6000

  • Page 1 SE 6000 SE 6000 STANDARD PRODUCT MANUAL Westinghouse Security Electronics an ISO 9001 certified company P/N 66107919001, Rev. F ECURITY ANAGEMENT YSTEM...

  • Page 2: Limited Warranty

    LIMITED WARRANTY IMPORTANT...

  • Page 3: Table Of Contents

    ABLE OF SECTION 1: INTRODUCTION ... 1-1 MANUAL ORGANIZATION ... 1-1 System Main Menu ... 1-1 Documentation Methods ... 1-2 DEFINITIONS ... 1-2 General ... 1-2 System Hardware — Devices ... 1-3 System Software ... 1-5 Principal System Functions ... 1-6 SAMPLE SYSTEM ...
  • Page 4 Doors ... 2-6 Select Zone ... 2-6 REVIEW TRANSACTIONS (FULL SCREEN) ... 2-7 ALARM SERVICING ... 2-8 REAL TIME CONTROL MAPS ... 2-8 CONTROL PROJECTS ... 2-9 ABORT TIMERS ... 2-9 OTHER FUNCTIONS ... 2-9 Printer Control ... 2-9 Forgive Passback ... 2-10 Manual Access Granted ...
  • Page 5 Keyholder Access Entry [empgentr] ... 4-5 Project Assignment [epj_entr] ... 4-6 COPY KEYHOLDERS ... 4-7 Copy Keyholder Information ... 4-7 ACCESS ASSIGNMENT ... 4-8 Keyholder Access Assignment [egrpentr] ... 4-8 COPY KEYHOLDER ACCESS [ERGCOPY] ... 4-8 ACCESS DEFINITION ... 4-9 Access Code Entry [acdsentr] ...
  • Page 6 Reader Access Assignment ... 5-5 Reader Assignment — Sample Report ... 5-5 ACCESS DEFINITION ... 5-6 Access Code Master ... 5-6 Access Group Master ... 5-6 Access Override ... 5-7 Intelligent Fail Soft Report ... 5-7 Project Report ... 5-8 Keyholder Project Report ...
  • Page 7 SECTION 6: SYSTEM ADMINISTRATION ... 6-1 INTRODUCTION ... 6-1 SECTION ORGANIZATION ... 6-1 ADDITIONAL INFORMATION ... 6-2 ADD USERS [ADDUSERS] ... 6-2 MODIFY PASSWORDS [MOD_PASS] ... 6-4 PROGRAM SECURITY [SEC_MENU] ... 6-5 Program Security Level Entry [pgacentr] ... 6-5 Program Security Entry Definition [pg1_entr] ... 6-5 Copy Security [mnaccopy] ...

  • Page 8: Section 1 Introduction

    ECTION INTRODUCTION MANUAL ORGANIZATION This manual follows the order of the seven standard product items in the system main menu, with the Key Inventory and Parking Stickers items merged into the System Administration section: • Section 2: Monitor Security Activity •...

  • Page 9: Documentation Methods

    Documentation Methods To avoid repetition and to reduce document size, detailed explanations for the system's principal data items are given only in Section 4: Master File Entry, which is used when creating the system database. For introductory information concerning the data items, see Definitions below. Further, with the exception of the screens presented in Basic System Usage in this section, and the introductory menu screens for Sections 2 through Section 5, all other screens throughout this manual are limited to the particular screen area being discussed (i.e., full screens are not shown).

  • Page 10: System Hardware - Devices

    Keyholder ID. Keyholder's ID number. The unique ID number is used by the computer to keep track of all activity for that person. Once entered, the keyholder ID cannot be changed. Location. Location of the office or branch of the company to which a keyholder is assigned. Tenant.
  • Page 11 Readers Digital Key Reader. Reads the unique number of 1 to 5 digital command keys simultaneously at a range of up to 36 inches. Keypad Controllers. The keypad controllers, normally used in conjunction with an ACU, provide additional security by requiring a personal identification number (PIN) entry. Magnetic Card Readers.

  • Page 12: System Software

    The system can be programmed to control data flow between central and remote computers to create a large-size security system controlled from a central point. Integrated Software Support. The SE 6000 communicates with a variety of access control and alarm monitoring devices. Currently, the system interfaces with WSE ACUs and their peripheral...

  • Page 13: Principal System Functions

    Response Time. The SE 6000 is capable of fast response times in both single and multiple site configurations. Fast response times are important for security personnel who monitor alarms and are always appreciated by keyholders wishing to enter locked doors.

  • Page 14: File Maintenance

    File Maintenance To perform its access control functions, the system must know the unique ID numbers of all keyholders and the doors and times they can enter. Further, the SE 6000 maintains other keyholder data to facilitate scheduling and reporting.

  • Page 15: Creating The Database

    Because all system activity is based on four-digit ID numbers, you need to decide before data entry how these numbers are to be assigned to the system hardware elements. Although the numbering system is entirely the choice of the SE 6000 owner, we recommend one of the two following methods:...

  • Page 16: Data Entry Sequence

    If the login incorrect message continues, consult the system administrator. When logged in correctly, the system displays the SE 6000 title page, sets the terminal environment, then displays the main menu. Call WSE Customer Service if you have a login problem.

  • Page 17: System Screens

    System Screens There are two basic screen types: Menu and Application: Menu Screens Menu screens list application selections by group according to function (exception Monitor Security Activity — see Section 2). All menu screen IDs end in menu (example: [fmntmenu] — Master File Entry).

  • Page 18: Screen Examples

    Storing Data in this section). SCREEN EXAMPLES SE 6000 screen displays show the path used to access the screen. For example, the final screen used when setting up keyholders, [epj_entr], is accessed via three preceding keyholder setup screens: [key_entr], [key1entr], [empgentr]. This useful feature considerably assists the new SE...

  • Page 19: Using Screens And Fields

    USING SCREENS AND FIELDS Selecting Screens There are three screen selection methods: Use the arrow keys to select the menu choice. Press Enter to place it in the Enter Selection field, and press Enter again to display the selection. Use the arrow keys to select the menu choice, and press F2 to display the selection. Press Enter anywhere in the list of choices to move the highlight bar to the Enter Selection field.

  • Page 20: Moving To Prior Screens

    Moving to Prior Screens Press F1 to return to the previous screen displayed. If required, continue to press F1 to return to the system main menu. FINDING, ADDING, AND STORING DATA Finding Data Use the find mode to locate and select data. A specific record (a single keyholder ID, for example) or a group of records (all keyholders in a particular job category, for example) can be found.

  • Page 21: Adding / Changing Data

    The computer automatically changes to the update mode when a search completes, and the records selected can be updated if required. To start another search, press F4 to clear the screen and begin again. Adding / Changing Data The add mode is used to input new records. Once a record is found using the search mode, update is automatically selected which allows the user to change the existing data.

  • Page 22: Zoom Feature

    • To save time when moving around the SE 6000 system, it pays to learn the screen titles of the most commonly used application screens (see the screen location trees and the table at the end of this section).

  • Page 23: Shutting Down

    MPORTANT Log off the SE 6000 system formally before you leave the terminal. If you do not log off, any action taken by the next person at the terminal will appear under your name. SHUTTING DOWN Always use the following procedures, in the order given, when powering off the SE 6000: Go to the main system terminal (system console).

  • Page 24: System Screen Trees

    If any other message displays apart from those noted here, just press Enter. SYSTEM SCREEN TREES The SE 6000 screens are arranged in tree structures, with hierarchies established from the primary screen to the lowest level screens in each tree. Each screen has a unique title which displays in the upper-left.
  • Page 25 SE 6000. Keyholder information and photo IDs created on the Polaroid system are transferred via a LAN or serial connection to the SE 6000. Badges can be printed on film or on PVC. Keyholder maintenance may be initiated on either system; all data is stored in a single database resident on...

  • Page 26: Section 2 Monitor Security Activity

    2: M ECTION ECTION ONITOR ECURITY CTIVITY MONITOR SECURITY ACTIVITY INTRODUCTION System monitoring and control is performed via the monitor menu, the first selection in the system main menu. The monitor menu screen is shown below. Notice this is a split screen, with the lower half constantly updated as transactions (any system event) occur.

  • Page 27: Control Pollers Function Keys

    FUNCTION KEYS Beneath the transactions display are the applicable function keys for each screen, with the key actions shown next to the key numbers. For most function key actions, the system displays messages confirming that the action has been completed, e.g., POLLER STOPPED. In general, F1 is used to exit from the current screen, and F7 and F8 are used respectively to display the previous screen and the next screen within the set of screens that apply to the particular data item being controlled or when there are more items then will fit into a single screen.

  • Page 28: Devices

    2: M ECTION ONITOR ECURITY CTIVITY When F4 is pressed, a second screen displays showing the connections between the host and the devices of the particular poller selected: Poller-device communication should be one of the first items checked whenever there is an apparent problem with the system.

  • Page 29: Locks

    F4 KEY RSET. Key Reset—Used when setting up new ACUs or reestablishing repaired ACUs, or when the integrity of the data currently resident in the ACU is suspected. Downloads all host key data to the ACU. F5 SHUNT. Shunt a device. F6 UNSHUNT.

  • Page 30: Input Points

    2: M ECTION ONITOR ECURITY CTIVITY F6 UNSHUNT. Unshunt a door previously shunted. Input Points The Control Inputs screen displays point ID, description, point status, tamper, shunt. Control Inputs Function Keys F5 SHUNT. Shunt a selected input point. If no input point is selected, F5 shunts all input points in the zone.

  • Page 31: Doors

    F6 UNSHUNT. Unshunt a selected output point previously shunted. If no output point is selected, F6 unshunts all output points in the zone. Doors The Control Doors screen displays point ID, description, status, and shunt of the door switches. Control Doors Function Keys F5 SHUNT.

  • Page 32: Review Transactions (Full Screen)

    2: M ECTION ONITOR ECURITY CTIVITY — Number of keyholders currently in the zone. Count — Passback zone type—personal, vehicle, none. PBarea — Passback type —hard, soft, none. PBtype PBlevel — Passback control—global (host), local (ACU), none. Note that zone count is automatically reset whenever a zone is selected. Multi-user systems employ record locking techniques for keyholder file maintenance, and locked records are not updated by the passback routine that maintains keyholder location.

  • Page 33: Review Transactions Function Keys

    Review Transactions Function Keys F2 BACKWARD. Page backward through the transactions. F3 FORWARD. Page forward through the transactions. F4 OLDEST. Go to first transaction. F5 LATEST. Go to last transaction. ALARM SERVICING The system emits beeps when an alarm occurs, and displays the number of pending and active alarm data in the upper-right corner of the monitor menu screen: Pending—alarm condition no longer occurring but not yet formally resolved.

  • Page 34: Control Projects Function Keys

    2: M ECTION ONITOR ECURITY CTIVITY CONTROL PROJECTS The Control Projects screen (not controllable on LC systems—host only) displays project, status, description, start, end. The control projects screen permits operator override of doors assigned to projects which directly affects keyholder access. Control Projects Function Keys F2 ACTIVATE.

  • Page 35: Forgive Passback

    2-10 F5 PRNT ON. Switch printer #1 on or off depending on current state (used to control log printer only). F6 PRNT ON. Switch printer #2 on or off depending on current state. Forgive Passback A passback violation occurs when a keyholder uses their key to reenter a door without first using their key to exit the same door.

  • Page 36: Remote Devices

    2: M ECTION ONITOR ECURITY CTIVITY When requested, enter the number of the table to be downloaded and press Enter. The system requests confirmation — press F1. REPACK OK displays when transfer completes. Remote Devices This function is used to establish a telephone connection to a remote device to perform certain actions, for example, unlock a door to a remote ATM for Service.

  • Page 37: Full Screen Monitoring

    2-12 F3 LIMITED. Change current building mode to limited. F4 CLOSED. Change current building mode to closed (takes approximately one minute to complete). If a device input point configured to prevent building closure is active, the building will remain in the limited mode until the point is cleared. Full Screen Monitoring Displays system logs in a manner similar to the review transactions feature (see Review Transactions—Full Screen in this section) except that new transactions display as they occur.

  • Page 38: Status Screen Function Timeout

    2: M ECTION ONITOR ECURITY CTIVITY Status Screen Function Timeout Some system functions temporarily disable the realtime display until the sub-menu is exited. The status screen function Timeout feature provides a user-defined method for controlling the length of time that the realtime display is disabled. If the system does not detect any keyboard or mouse activity for the number of seconds defined by the TIMEOUT parameter, the monitor program returns to the previous menu and resumes realtime display.

  • Page 39: Additional Information

    2-14 Monitoring Security - Passwords With enhanced monitor security function and the addition of password logic, any or all portions of the monitor functions can be set up to require a valid ID and password combination before the function can be initiated. In place of the factory-supplied status login, the user may create a similar login ID, with or without password, and control access to monitor capabilities.

  • Page 40: Modified Usage Of Invalid Facility Code Log

    2: M 2-15 ECTION ONITOR ECURITY CTIVITY Status Screen Function Timeout Feature Modified Usage of Invalid Facility Code Log This feature suppresses a keyholder's name from the monitoring screen and various reports when an INVALID FACILITY CODE message is logged. In some cases, this resulted in a log message erroneously associating a valid keyholder with an invalid facility.
  • Page 41 2-16 2: M ECTION ONITOR ECURITY CTIVITY...

  • Page 42: Section 3 Security Reports

    ECTION SECURITY REPORTS INTRODUCTION Security management reports provide a permanent record of transactions, and are also used to examine specific events. The reports are accessed through the security management reports menu screen, [accsmenu], via the main menu. In this section, the reports are documented following the security management reports menu sequence (see section table of contents).

  • Page 43: Point History Report

    Some reports are over-wide (132 characters instead of the standard 80 characters), and have been formatted to use a smaller print size not available with some terminals (HP printers can handle the smaller print). These reports can be displayed but will 'wrap'; that is, some lines continue to the next display line .

  • Page 44: Section 3: Security Management

    ECTION ECURITY ANAGEMENT Keyholder History — Sample Report 06/27/96 14:36 Point Point Description _____ ____________________ Keyholder 2771 Dale, Deborah 0225 RDI-8082-SEN2 0221 RDI-8082-SEN1 0215 RDI-8081-SEN1-READER 0220 T&A READER 3 N/A 0210 T&A READER 2 OUT 0200 T&A READER 1 IN 0120 ELEVATOR FREIGHT CAR TRANSACTION HISTORY REPORT...

  • Page 45: Transaction History - Sample Report

    Transaction History — Sample Report 11/15/96 10:34 Point Point Description Zone _____ _______________________ ____ HOST HOST HOST HOST HOST HOST ACCESS CONTROL ARCHIVE REPORT The access control archive report, [acrtrprt], is identical to the transaction history report (previous report) except that it reads data from an archive tape rather than from the system database. ALARM SERVICING REPORT The alarm servicing report, [almarprt], details actions taken by operators in response to alarms.

  • Page 46: Alarm Servicing - Sample Report

    ECTION ECURITY ANAGEMENT Alarm Servicing — Sample Report 06/27/96 15:01 Alarm No Alrmtime Alrmdate Point Zone ________ ________ ________ _____ ____ Point Descrip = CHEMICALS GPS 3 2851 09:18:00 06/26/96 Operator Response: CALLED FIRE DEPT. CLEARED BUILDING OPENED VENTS LEFT BUILDING REENTERED WHEN ALL CLEAR PASSBACK ZONE REPORT The passback zone report, [whowhere], lists keyholders currently present in passback zones.

  • Page 47: Passback Zone - Sample Report

    Passback Zone — Sample Report 04/05/96 Easthaven Manufacturing 14:43 Passback Zone Report Keyholder Key No Keyholder Name _________ _____ __________________________ ______ 1055699 83383 MAITLING, JACK 1061128 84128 LYONS, CINDY 1086201 83361 DENEUVE, DENISE 1099004 86660 SMITH, PAULA 1100015 87083 MACKLING, JACKIE 1116345 88883 FLYNN, SEAN...

  • Page 48: Download Status - Sample Report

    3: S ECTION ECURITY ANAGEMENT Download Status — Sample Report 06/27/96 15:03 Serial # Key Value File Descrip Typ Date _________ _________ ____ _______ ___ ____ 21729 Points 21730 Points 21731 Points 21723 21463 Events 21724 21463 Events 21725 21463 Events 21726 21463...

  • Page 49: Keyholder Zone Report

    KEYHOLDER ZONE REPORT The report lists the most recent zone information for all keyholders that meet the search criteria; however, information is not necessarily current. A sample [kyznrprt] screen follows: Keyholder Zone — Sample Report 05/12/96 14:41 Keyholder Keyholder Name _________ ___________________ ______ 10556...

  • Page 50: Event / Point - Sample Report

    3: S ECTION ECURITY ANAGEMENT Event / Point — Sample Report 03/17/96 09:15 Point Point Description ______________________________________________________________ HOST HOST DATA BASE POLLER DATA BASE POLLER 808/422 POLLER 808/422 POLLER REALTIME PASSBACK ZONE REPORT The realtime passback zone report, [rpasrprt], is essentially the same report as the passback zone report (described earlier in this section), with one important difference.

  • Page 51: Realtime Passback Detail - Sample Report

    REALTIME PASSBACK DETAIL — SAMPLE REPORT 03/14/96 15:18 Keyholder Key No Keyholder Name _________ ________ _________________________ 223141 188954 McDaniels, Jeff 237473 140226 Wellington, Lambert 233974 195226 Du Pont, Michael 239965 200026 Senter, Carol 248366 180463 Pons, Antonia 249037 143511 Segwick, G.J. ECTION McPowell-Angus Aviation Realtime Passback Detail Report...

  • Page 52: Section 4 Master File Entry

    4: M ECTION ASTER NTRY ECTION MASTER FILE ENTRY INTRODUCTION The master file entry procedures are used to create and maintain the database. All initial system data is entered following the methods detailed in this section. The data item menu screens are accessed via the master file entry menu [fmntmenu], displayed via the main menu.

  • Page 53: Keyholders

    KEYHOLDERS Four data entry screens are used to add new keyholders to the system, and to change or delete existing keyholder information: Keyholder Entry - Page 1, [key_entr]. Used to enter primary keyholder information. Keyholder Entry - Page 2, [key1entr]. Used to enter optional keyholder information. Keyholder Access Entry, [empgentr].
  • Page 54 4: M ECTION ASTER NTRY Keyholder ID. Required in the Add mode (the system denies further screen access until this field is entered). Enter a unique nine-digit maximum keyholder ID number (alphabetical letters are not supported). Last Name. Optional. Enter the keyholder’s last name. First Name.

  • Page 55: Keyholder Entry-Page 2 [Key1Entr]

    Issue Date. Optional. Enter the date that the access control card for the keyholder will become valid. Default is current system date. Note that a future date will not permit access until that date is reached. Issue Time. Optional. Enter the time that the access control card for the keyholder will become valid.

  • Page 56: Keyholder Access Entry [Empgentr]

    4: M ECTION ASTER NTRY Keyholder Access Entry [empgentr] Access Code. Optional. Enter an access code number that applies to this keyholder (the system automatically enters the access code description). Default is 0—No access code. There is no limit to the number of access codes that can be assigned, with the following two exceptions: Do not assign a keyholder more than one access code for a single NexSentry, 8xx series, or 422 ACU.

  • Page 57: Project Assignment [Epj_Entr]

    Y if the downloaded access code is to be sent to the ACU as a smart failsoft access code. Default is N. Note that this is used only in conjunction with the host access codes. The smart failsoft option is not supported with any keys used in conjunction with 708P and 718P ACUs, but a function is built in to the units which does provide some measure of failsoft protection in the event of a communications failure with the host.

  • Page 58: Copy Keyholders

    4: M ECTION ASTER NTRY A sample [epj_entr] screen follows. Enter the project number (zoom available) then press Enter; the project description displays automatically. If multiple projects are to be assigned, enter and store each one separately. COPY KEYHOLDERS Copy Keyholder Information Used when creating new keyholders who share data with existing keyholders, the [key_copy] screen is an important timesaving feature.

  • Page 59: Access Assignment

    ACCESS ASSIGNMENT Keyholder Access Assignment [egrpentr] The [egrpentr] and [egrpentr1] screens, accessed from Access Assignment (third item in the [fmntmenu] menu), are used as a fast way to make access assignments without using the keyholder data entry screens. Data entry is the same as for the keyholder access entry screen [empgentr].

  • Page 60: Access Definition

    ACCESS DEFINITION The access definition selection in the master file entry menu displays the access definition menu: • Access Code Entry, Access Code Definition, Elevator Definition • Access Group Entry, Access Group Definition • Access Override Entry • Fail Soft Entry •...
  • Page 61 Access Code ID. Required. Enter a four-digit maximum access code number. Tenant. Required (zoom available). Enter a four-digit maximum tenant code number. Default is tenant 0. Download Device ID. Optional (zoom available). This field must be used if the access code being created is to be downloaded to an ACU—enter the ACU ID number.

  • Page 62: Access Group Entry [Agdsentr], [Agrpentr]

    Reader ID. Required. Enter the reader number to be linked to this access code (the reader description is automatically displayed). The reader numbers can be entered in any order. Time Code. Optional. Enter up to four time codes, in any order, that apply to this access code (the time code parameters are displayed automatically).
  • Page 63 Group Description. Required. Enter a 30-character maximum description of the access group. When screen entry is completed press F6 to store the data, at which point the Access Group Definition screen displays automatically. This screen permits you to enter the access codes that will apply to this access group.

  • Page 64: Access Override Entry

    CCESS VERRIDE NTRY Access override codes are typically used for visitors to restrict or allow access to specific locations for specific time periods. This is a host function that must be used only if normal access is through host access codes: Override Code.

  • Page 65: Failsoft Entry

    AILSOFT NTRY 708P ACUs can be programmed to recognize up to 25 keyholders (based on key numbers) for use when communication with the host computer is temporarily unavailable. Known as failsoft, the feature becomes active (access is granted) for these keyholders after 15 seconds following the occurrence of the communications interruption (response is not available for specific time periods, however).
  • Page 66 Project ID. Required. Enter a four-character maximum project ID code. Description. Optional. Enter a 40-character maximum description of the project. Starting Date and Time. Enter the project's starting date and time in the formats MM/DD/ YY and HH:MM. Ending Date and Time. Enter the project's ending date and time in the formats MM/DD/YY and HH:MM.

  • Page 67: Time Codes [Tmcdentr]

    TIME CODES [tmcdentr] Time codes are normally used to define when points and readers are active. The codes are also used to automatically lock / unlock doors, activate / deactivate output relays, and to initiate recurring tasks. When combined with readers into access codes, the time codes define when access is valid for particular readers.

  • Page 68: Tenants [Tententr]

    TENANTS [tententr] INSTRUCTIONS [instentr]...

  • Page 69: Hardware Configuration [Confmenu]

    HARDWARE CONFIGURATION The hardware configuration item in the master file entry menu displays the hardware configuration menu [confmenu]: • Zones • Areas • Pollers • Devices • Readers • Points • Auto Opens/Activates ONES ZONEENTR zoom [confmenu] • Device Report Definition •...

  • Page 70: Areas [Areaentr], [Areaentr1]

    [areaentr], [areaentr1] REAS For reporting purposes only, passback zones may be grouped into areas. Reporting (keyholder zone report) may be by zone or area, with the area report listing the zones contained in each area. Assign a number and optional description for the area using [areaentr]; enter the applicable zone numbers in [areaentr1].
  • Page 71 The SE 6000 can run different pollers or multiple copies of the same poller concurrently but, with the exception of the NexSentry, 8xx-series, and 422 ACUs, the pollers can be run with one device type only. Poller parameter files are read when the poller programs start. The parameters define the poller type, the physical port assignment, and other required control information.

  • Page 72: Devices

    EVICES IMPLE NTELLIGENT EVICE simple Simple Devices Intelligent Devices zoom Poller Entry YPES intelligent...

  • Page 73: Device Types

    local mode EVICE NTRY CREENS [dev_entr] EVICE NTRY Device ID. Required. Enter a unique, four-digit maximum device ID number in the range 1—9999. Device Description. Optional. Enter a 20-character maximum description of the device. If omitted, the system enters the device ID number in this field. Tenant.
  • Page 74 Address. Required. Enter the address of the device. Since each poller can poll a number of devices, the Address field is necessary to tell the host which device to poll. The address ranges are included in the Device Type table (see following field). Note that the system will not allow duplicate device addresses on the same poller.
  • Page 75 SE 8 ERIES EVICE ONFIGURATION The [d808entr] screen must be completed for all 8xx-series ACUs (use F2 to display the screen after the previous screen has been stored). A sample screen follows: Level, Name, Password. Required. These first three fields are entered to identify up to eight operators who will be permitted to set/change system parameters for a particular ACU from the ACU terminal port.
  • Page 76 Power Fail. Optional. Enter the power fail report number if a report has been created (see applicable ACU manual). The report states the actions that will be taken by the ACU should a power failure occur. Default is 0. Override. Optional. Enter the operator override report number if a report has been created (see applicable ACU manual).

  • Page 77: Se Nexsentry Device Configuration Entry [Nexsentr]

    SE N ENTRY EVICE Complete the [nexsentr] screen for the NexSentry ACU and then press F2 Next Form to display the [d818entr] screen. Enter all appropriate information and press F6 Store to complete the NexSentry device configuration. A sample [nexsentr] screen follows: Level, Name, Password.
  • Page 78 The Level, Name and Password fields are specific to the NexSentry and applies only to operators logging in directly via the ACU's terminal port. The fields are not part of the SE 6000 control parameters. Tamper. Optional. Enter the tamper report number if a report has been created (see applicable ACU manual).
  • Page 79 SE 818 D EVICE ONFIGURATION SE 422 Pin Definition PIN Timeout. Optional. Enter the maximum number of seconds allowed between key presentation and PIN entry. Default is 10. Max PIN Retries. Optional. Enter the allowed number of PIN entry retries. Default is 4. VIP Only Digits.
  • Page 80 The security codes A through F control the degree to which the operator may add/change/ delete the system parameters. Code A has the most privileges, code F has the least. For detailed information concerning operator privilege levels, refer to the applicable ACU manual.
  • Page 81 VIPs Digits. Optional. The number of digits in the PIN number for doors using keypads only. The range is 4 to 8. Default is 4. Modem Definition. Not used when the SE 6000 is connected directly or in a dial-up configuration.

  • Page 82: Readers

    EADERS Readers are usually assigned to ACUs, but they may be used as standalone devices or linked to other security monitoring devices. Twelve reader types (1 — 12) are currently defined: Access Control. Controls power to a door lock allowing or denying entry. Time and Attendance (optional feature).

  • Page 83: Reader Entry [Rdr_Entr]

    [rdr_entr] EADER NTRY zoom zoom zoom...
  • Page 84 Reader Type. Required. Enter the reader type number in the ranges 1 through 12 as described above. Assoc Reader ID (Associated Reader). Required if the reader is used in conjunction with a keypad. Enter the ID number of the Reader used with the keypad. Default is 0. Door Switch ID.
  • Page 85 active. For Mod, enter a transaction modifier code (A, B, etc.) to customize log messages and system actions (see Section 6: System Administration for details). The default for Mod is 0 (zero); use the standard log message. NTRY AND EADER The Auto Key Entry feature allows you to capture the key number from a key card and assign the number as well as enter the card number automatically in the Key Number field of the keyholder Entry [key_entr] screen.
  • Page 86 In addition, the MOR and the SE 6000 keep track of the people that are in a specified zone. NTERING A ULTIPLE CCUPANCY When a multiple occupancy zone is vacant, two keyholders are required to present their keys to the reader to unlock the door;...
  • Page 87 in response to various events occurring within the system. (The field titles indicate the event types.) See Device Report Definition in the section and the applicable ACU manual for detailed information. SE 422 R EADER EPORT EFINITION Mag Stripe Type. Enter the magnetic stripe type: 0 = MSR, 1 = MSR5, 2 = MSRK5. Mag Stripe Code.
  • Page 88 — The following ten fields, Forced Open through Exit Granted, require the entry of a report number. The word report in this context identifies a user-defined action or series of actions that the ACU is to take in response to various events occurring within the system. (The field titles indicate the event types.) See Device Report Definition in the section and the applicable ACU manual for detailed information.
  • Page 89 Proximity Type. Enter the proximity type: 0 = Sensor interface, 1 = DigiKey reader. The following thirteen fields, DKR/SCR Fail through VIP tamper, require the entry of a report number. The word report in this context identifies a user-defined action or series of actions that the ACU is to take in response to various events occurring within the system.

  • Page 90: Points [Pnt_Entr]

    The following eleven fields, DKR/SCR Fail through Device Tamper, require the entry of a report number. The report in this context identifies a user-defined action or series of actions that the ACU is to take in response to various events occurring within the system. (The field titles indicate the event types.) See Device Report Definition in this section and the applicable ACU manual for detailed information.

  • Page 91: Section 4: Master File Entry

    4-40 Section 4: Master File Entry zoom zoom zoom...
  • Page 92 Section 4: Master File Entry 4-41 zoom Enable Point...

  • Page 93: Auto Opens / Activates

    PENS CTIVATES The auto open / activate feature is used to instruct the system to lock / unlock doors, or activate / deactivate output points, for a predefined amount of time. Examples: • A regular business door is configured to automatically unlock at a prescribed time each morning.

  • Page 94: Device Report Definition [Rdefentr]

    EVICE EPORT EFINITION Use this feature to create action reports for the SE 8xx-series and SE 422 ACUs. An action report is a set of user-defined tasks performed by the ACU when specified conditions occur. The actions are defined using the device report definition screen (sample screen shown below); the reports are assigned using screens described in the device entry subsection.

  • Page 95: Se 422 Hardware Definition

    4-44 Section 4: Master File Entry Section 3 SE 422 PIN Master Report Device Entry SE 422 H ARDWARE EFINITION zoom...

  • Page 96: Dialer Entry

    Section 4: Master File Entry 4-45 IALER NTRY zoom zoom...

  • Page 97: Site Entry Definition

    4-46 Section 4: Master File Entry Not currently implemented. NTRY EFINITION...

  • Page 98: Aba Configuration Entry

    Section 4: Master File Entry 4-47 ABA C ONFIGURATION NTRY...

  • Page 99: Dkr Configuration Entry

    4-48 Section 4: Master File Entry DKR C ONFIGURATION NTRY In all cases, however, do not attempt these procedures without first contacting your dealer and/or WSE customer support.

  • Page 100: User-Defined Information

    Section 4: Master File Entry 4-49 USER-DEFINED INFORMATION The field titles are changed with the control file maintenance feature accessed from the System Administration menu (see Section 6: System Administration):...

  • Page 101: Maps

    4-50 Section 4: Master File Entry MAPS RAWING OMMANDS AND ESCRIPTIONS...
  • Page 102 Section 4: Master File Entry 4-51 close exactly nearly exactly...
  • Page 103 SE 422 Input Table ACU (2-state) 0: M16 /RO1 (4-state input) 2: RO4 (4-state) VIP (2-state) SI (4-state) MSR (2-state) 17: SE 422 Output Table Acu (2-state) M16/RO1 (4-state input) 2: Input points are always on sensor 1, contact 1-75 Output points are always on sensor 2, contact 1-51...

  • Page 104: Section 5: Master File Reports

    ECTION MASTER FILE REPORTS INTRODUCTION The master file reports list comprehensive database information. The report menu screens are accessed via the master file reports menu [rprtmenu], displayed via the main menu. In this section, the reports are documented following the reports menu sequence (see section table of contents). A sample [rprtmenu] screen follows: All screens in this section show the system default values, with most screen fields requiring a numeric range entry.

  • Page 105: Additional Information

    ADDITIONAL INFORMATION An additional report feature not accessed via the reports menu, 132-xx Column Report Display, is detailed at the end of this section. KEYS MASTER Two versions of the keyholder master report are available — Keyholder Quick List and Keyholder Master List (extended).

  • Page 106: Keyholder Quick List - Sample Report

    5: M ECTION ASTER EPORTS — S EYHOLDER UICK 06/02/96 14:45 KeyholderKey No Keyholder Name ___________________________________________________________________________________________________________ 220774 409 JENSEN STEVE 221922 811 KREBS SCOTT 222172 512 DUNN JEFF 233132 588 NEWMAN TERESA 239445 277 CLEMENT KAREN 245165 338 KIRK KATHY 246763 445 FERRELL STUART 247666 176...

  • Page 107: Access Assignments

    ACCESS ASSIGNMENTS EYHOLDER CCESS SSIGNMENT This report prints the access codes and access groups assigned to keyholders. Regular and extended versions of the report are available. The regular report lists keyholder numbers and names, access code / group numbers and descriptions, and access override codes where applicable.

  • Page 108: Keyholder Access Assignment: Extended - Sample Report

    EYHOLDER CCESS 06/09/96 12:30 Access Code 1 = Host 422, 808, 818 Keyholder 331 Name Key No 1038 Addr1 S.S. No987-65-4321 Addr2 Tenant 1 Addr3 P.I.N. 2198 Privledge YES Remarks Phone 224-8089 Trace NO Visitor NO EADER CCESS This report prints keyholder access permissions at a specific reader and applicable time codes. A sample screen follows: EADER SSIGNMENT...

  • Page 109: Access Code Master

    ACCESS DEFINITION CCESS ASTER This report details all access codes defined in the system (the report can be limited to a single code or a range of codes, as required). A sample screen follows: CCESS ASTER 05/02/96 11:26 Code Code Description Reader ____ ________________ ______...

  • Page 110: Access Override

    5: M ECTION ASTER EPORTS — S CCESS ROUP ASTER AMPLE 06/10/96 10:03 Group Group Description _____ ______________________________ ____ 1 DWNLD 801/802/8100/4222 1 DWNLD 801/802/8100/4222 2 SFS/708/801/802/8100/4222 2 SFS/708/801/802/8100/4222 2 SFS/708/801/802/8100/4222 CCESS VERRIDE The report lists access override codes in the database, with descriptions, start / end dates, and permissions (allow / deny access).

  • Page 111: Intelligent Fail Soft Report

    — S NTELLIGENT AMPLE 03/25/96 08:24 Keyholder Keyholder Name _________ ______________________ 67100 708P PARKING CNTR 63455 DIGI FI-GI 61096 GUARD NEW 61099 1030 ALT+D+P ROJECT EPORT The Project Report includes number, description, start / stop times and dates, and current status. This report gives project status based on start / stop dates defined by the project entry function compared to the current system date and time.

  • Page 112: Keyholder Project Report

    — S ROJECT EPORT AMPLE EPORT 03/25/96 08:29 Project Project Description _______ ___________________________ ________ TEST PROJECT #1 TEST PROJECT #2 EMERGENCY CIRCUITBOARD REV. 12/17/96 NEW TEST PROJECT LAUNCH TEST PROJECT #3 EYHOLDER ROJECT EPORT The Keyholder Project Report includes keyholder ID, name, project ID and description, and current status.

  • Page 113: Reader Project Report

    EADER ROJECT EPORT The Reader Project Report lists project number, description, readers assigned, current status. This report gives reader project status based on start / stop dates defined by the project entry function compared to the current system date and time. Since the selection criteria and reported status do not consider operator overrides, actual and reported project status may differ.

  • Page 114: Holidays

    — S ODES AMPLE EPORT 03/25/96 08:36 Tmcd Description ____ ________________________ _____ _____ NEVER ACTIVE 7-DAYS, 24-HOURS & HOLS OFFICE HOURS 7 am - 6 pm 07:00 18:00 WEEKENDS & HOLIDAYS HOLIDAYS This report lists all holidays that have been entered into the system. A sample screen follows: —...

  • Page 115: Tenants - Sample Report

    — S ENANTS AMPLE EPORT 05/04/96 09:07 Number Description ______ ___________ 1 WESTWOOD SECURITY SYSTEMS 2 SOS PUBLISHING (CALIFORNIA) 3 BETA SOFTWARE 4 WALKINS PRODUCTS, INC COMPANY, DEPT, LOCATION, JOB CAT These reports list user-defined company, department, location and job category information. The report screens are identical for all four —...

  • Page 116: Sample Instructions

    AMPLE NSTRUCTIONS 03/25/96 08:45 Point Point Description _____ ______________________________ ____ ________________________________________ 7114 PRIORITY 10 ALARM 9011 RDI 808 #1 1.1 FIRE MAPS The map report lists all points incorporated into user-defined system maps. The report screen prompts only for the desired sequence: point ID, point type, or map name. —...

  • Page 117: Zones - Sample Report

    — S ONES AMPLE EPORT 03/25/96 08:47 Zone Description ____ _______________________________ ALPHA LAB ZONE HARD PASSBACK ZONE 2 HARD PASSBACK ZONE 3 HARD ANTI PASSBACK OLLERS The report lists all defined pollers in the system. A sample screen follows: — S OLLERS AMPLE EPORT...

  • Page 118: Readers

    5: M ECTION ASTER — S EVICES AMPLE 03/25/96 08:50 Device Device Desc Comp #Poll # Address Prim Device Type Desc ___________________________________________________________________________________________________ 1 HOST 10 LC #1 100 DIAL-UP 422 #1 801 BETA 808 SX# 2 802 BETA 804S #1 EADERS This report lists all readers defined in the system.

  • Page 119: Points

    — S EADERS AMPLE EPORT 06/03/96 12:57 Reader Reader Description Comp # ______ __________________ ______ RM-A EAST ENTRY RM-A WEST ENTRY OINTS This report lists all points defined in the system. A sample screen follows: — S OINTS AMPLE EPORT 07/16/96 11:51 Point Point Description...

  • Page 120: Auto Opens / Activates

    PENS CTIVATES This report lists system points and readers which have auto-open or auto-activate times. A sample screen follows: CTIVATE 03/25/96 08:54 Point Point Description _____ ___________________________ 1830 818 #7 DOOR #3 +VIP 1850 818 #7 DOOR #5 1870 818 #7 DOOR #7 8240 TIM’S 804S DOOR 4 808 R...

  • Page 121: Device Configuration

    808 D EVICE ONFIGURATION This report lists configuration information for the system 800-series ACUs. A sample screen follows: 808 D EVICE ONFIGURATION 06/05/96 15:25 DIAL-UP 808 #1 Level Name Password OPERATOR MGR NEW G. SAYLES SAYLSG LYNN VAUGHAN LYNSID TIM JONES TJO123 IALERS The two dialer report types detail the remote dialup interface (RDI) devices defined for the system...

  • Page 122: Site Definition - Sample Report

    — S EFINITION AMPLE 03/25/96 09:02 Group Code _____ ____ 0000 1000 1001 6016 7279 ABA C ONFIGURATION This report lists all the ABA configurations defined for the system, and gives the configuration parameters. A sample screen follows: ABA C —...

  • Page 123: Dkr Configuration

    DKR C ONFIGURATION The reports lists the system default DKR parameters. A sample screen follows: DKR C — S ONFIGURATION 06/12/96 15:21 Config. ID Send Once Read Range Number of Reads Read Time SE 422 PIN M ASTER EPORT This report lists keyholders having system-calculated SE 422 PIN numbers. A sample screen follows: AMPLE EPORT...

  • Page 124: 132-Column Report Display

    5: M ECTION ASTER SE 422 PIN M ASTER 03/25/96 09:22 Keyholder Key No Keyholder Name ___________ ______ _______________________ 6109 1895573 Duane Eddie 6110 1784422 Juarez Sandi 6112 1901112 De Witt Charles 6113 1788122 Ames Linda 132-COLUMN REPORT DISPLAY The local print program was originally written to accommodate an 80-character terminal display. Some terminals now use up to 132 characters, and the new 132-Column Report Display feature allows for this.

  • Page 125: Section 6: System Administration

    ECTION SYSTEM ADMINISTRATION INTRODUCTION The administration functions are used to control and maintain the system. These functions are accessed from the system administration menu, [sys_menu], via the main menu. (Depending on the operator's program security level, some or all of these functions may not be available.) A sample screen follows: SECTION ORGANIZATION The procedures in this section are in the order shown in the system administration menu (above).

  • Page 126: Additional Information

    ADDITIONAL INFORMATION Additional system administration-related information is provided at the conclusion of this section. ADD USERS [addusers] The add users screen, [addusers], is entered to add, change, or delete system users / operators. MPORTANT The administration log-on and password must be used to access this screen. If you are already logged on with your regular password, first log off in the normal way, then log on again using the administration log-on and password.
  • Page 127 ECTION YSTEM DMINISTRATION Program Security Level. Optional (range 1—9999). Code number indicating the specific screens the user can access. Default is 1 (complete access). Tenant. Optional. Enter tenant number (if applicable). Default is tenant 0. " Monitoring Group. Optional. System code indicating transaction types available to this user.

  • Page 128: Modify Passwords [Mod_Pass]

    Jump Timer Servicing. Y / N field indicating if the user has the authority to automatically jump to timer servicing from monitor when an timer event occurs. Language. The code number entered will determine what language the system will use for this user.

  • Page 129: Program Security [Sec_Menu]

    ECTION YSTEM DMINISTRATION PROGRAM SECURITY [sec_menu] ROGRAM ECURITY EVEL NTRY Begin creating program security level types by first displaying the program security level entry screen [pgacentr]: Enter the security level number (four digits maximum). Enter a description (30 characters maximum). Press F6 Store, then press F2 for the program security level definition screen ROGRAM ECURITY...

  • Page 130: Copy Security [Mnaccopy]

    Enter Y or N in the add/update/delete fields to give or deny access to these functions on the selected screen. If you do not make any Y/N selection in the Add, Update, and delete fields, the keyholder will not have access to the screen. Press F6 Store and then, before any other action is taken, press F5 to return to the add mode for the next entry.

  • Page 131: Display All Valid Logins [Showuser]

    ECTION YSTEM DMINISTRATION DISPLAY ALL VALID LOGINS Use the [showuser] screen to identify — by hard copy printout or report display at the system terminal — all operators who have access to the system (use the [showwho] (Display All Valid Logins) screen to display operators currently logged on.

  • Page 132: Purge A Pending Report [Purgrprt]

    [key_entr] and [key1entr] can be changed to suit the individual user. Since keyholder records may be considered the primary data items for an access control system, many SE 6000 owners use the field title change feature to tailor the system to their precise requirements. Change fields A through F and 1 through 7 as required.

  • Page 133: Events [Evenentr]

    ECTION YSTEM DMINISTRATION [evenentr] VENTS The task / event subsystem is used to program one or more tasks to be automatically performed in response to the occurrence of a user-defined event. Tasks and events are linked, and the task must be entered and stored before the system allows the creation of a related event. Events can initiate the same task, or a single event can initiate multiple tasks.

  • Page 134: Tasks [Taskentr]

    6-10 Modifier. Optional. If applicable, the transaction modifier which defines the event if the message is user-defined. Event Date. Optional. If the task referenced by this event is to be system-initiated, enter the applicable date. Event Time. Optional. If the task referenced by this event is to be system-initiated, enter the applicable time.

  • Page 135: Activate Output

    ECTION YSTEM DMINISTRATION Activate Code, Extension. Required. System code number for the type of action to be performed. The extension applies to camera presets for pan and tilt, or image verification when used with a Polaroid ID-4000 system. See table following this field description list. Deactivate Code, Extension.

  • Page 136: Task Event / Master Report [Taskrprt]

    ACTIVATE PROJECT DEACTIVATE PROJECT NORMALIZE or CLEAR PROJECT VENT ASTER EPORT This report shows all tasks / events established in the system: 04/14/96 13:02 Task Task Description ____ _ _______________________ 42 UNLOCK DOOR EVENTS [tranentr] RANSACTIONS Customized versions of any system transaction (log message) can be created. The custom transactions are created using the transaction entry screen, where they are linked to the point or reader screens by a transaction modifier code.
  • Page 137 ECTION YSTEM DMINISTRATION Transaction Type (ID). The unique ID number of a transaction. The system is pre- programmed to use specific transaction types for certain events at certain types of points. (See Appendix C: System Transactions for a complete list of standard transactions.) Transaction Modifier.

  • Page 138: Database Maintenance [Db_Menu]

    Green Cyan (light blue) Blue Display Icon. For future use. Printer Group. Each log printer must include the selected printer group in its list of available printer groups. If the selected printer group is not included, the transaction will not be printed on the log printer.
  • Page 139 ECTION YSTEM DMINISTRATION . A database backup copies all information in the database (exceptions user and map ATABASE ACKUP information). If you make a number of changes to keyholder, hardware, and / or access information in a single day, then the database backup should be performed each day. For these purposes, use two alternating tapes (one for odd days, one for even) to guarantee that no information will be lost in the event of a hardware malfunction.

  • Page 140: Alarm Transaction Clean Up [Alrmcln]

    LARM RANSACTION LEAN Each time an alarm is triggered, a record is created and stored in a separate file along with the operator's alarm servicing response. This table is then available for reporting using the alarm servicing report. Over time, the size of this table grows and takes up excessive space on the hard disk.

  • Page 141: Keyholder Loading [Loadmenu]

    Keyholder ID 1 to 9 digits; both name fields 15 characters maximum ID SECURITY MAINTENANCE The ID Security Maintenance function controls access to the information shared by the SE 6000 and the Polaroid ID-4000 Identification System. It also controls access to selected fields in the keyholder record.

  • Page 142: Id Security Group Entry [Id2_ Entr]

    ID S [ID2_ entr] ECURITY ROUP NTRY This function is used to create ID security groups. A sample screen follows: Required. Enter a unique security group number in the range 1—999. Optional. Enter a group description (30 characters maximum). ID S [ID1_ rprt] ECURITY EPORT...

  • Page 143: Miscellaneous Information

    Multiple baud rates are supported for the diverse mix of communications equipment available for the SE 6000 system. The baud rate is set by changing the HOSTBAUD parameter in the $DATAPATH/NPOLLER.x file where x is the associated poller number. The baud rate is entered during installation or changed as needed by the system administrator;...

  • Page 144: Key Inventory [Invtmenu]

    This feature is enabled / disabled using the REXEXTEND parameter in the $DATAPATH/ NPOLLER.x file where x is the associated 708P poller number. The feature is enabled / disabled during installation, or may be changed as needed by the system administrator. If changed, the poller must be halted and restarted for the parameters to take effect.

  • Page 145: Key Inventory Entry [Cdinentr]

    ECTION YSTEM DMINISTRATION 03/25/96 15:52 Code Code Description ____ ________________ AVAILABLE ASSIGNED LOST UNUSABLE DAMAGED TERMINATED REISSUED RECOVERED PREVIOUS OWNER RESERVED [cdinentr] NVENTORY NTRY This function is used to add/change key inventory information (to delete a key record, use the system delete record feature —...

  • Page 146: Parking Stickers [Stkrmenu]

    03/25/96 15:55 Keyholder Keyholder Name _________ ____________________ 29205 THORPE JAMES 31408 ROSS MICHAEL 33244 DESJARDINS ROBERT 36427 JERRY TIMOTHY 37441 JUDD AL PARKING STICKERS [stkrmenu] This feature is used to control parking stickers issued to keyholders. The initial screen is accessed from the main menu: [stkrentr] ARKING...

  • Page 147: Parking Sticker Master Report [Stkrprt]

    ECTION YSTEM DMINISTRATION ARKING TICKER ASTER EPORT The report lists assigned parking stickers. A sample screen and report follow: 06/25/96 16:00 Keyholder Keyholder Name _________ _______________________________ 28870 TERRY VALE 28977 JESS WHITTINGTON 28993 CHERYL ROBERTS 29001 PETER VAUGHAN [stkrprt] Security Electronics Parking Sticker Report Sticker _______...

  • Page 148: Appendix A: System Screen Trees

    A: S PPENDIX YSTEM CREEN REES (Full Screen)
  • Page 149 A: S PPENDIX YSTEM CREEN REES...
  • Page 150 A: S PPENDIX YSTEM CREEN REES...
  • Page 151 A: S PPENDIX YSTEM CREEN REES...
  • Page 152 A: S PPENDIX YSTEM CREEN REES...
  • Page 153 A: S PPENDIX YSTEM CREEN REES "...

  • Page 154: Appendix B: System Screen Hierarchies B

    B: S PPENDIX YSTEM CREEN ONITOR ECURITY CTIVITY CREEN ITLE UNCTION monitor Watch events and activities as they occur; menu to other monitoring and control screens. ctrlmenu Menu to control functions. Zone selection stays in effect until this screen is exited. ctrlpoll Select pollers to halt or restart, and to check device communication.
  • Page 155 key_copy Create new keyholder record by copying from an existing keyholder record. egrpentr Select a keyholder for access privilege assignment. Can also be reached from key1entr. egrpentr1 Assign access privileges to a keyholder. egrpcopy Copy one keyholder's information to another keyholder. acc_menu Menu to reach the access definition functions.
  • Page 156 B: S PPENDIX YSTEM CREEN ASTER EPORTS CREEN ITLE UNCTION rprtmenu Menu to database reporting functions. key_rprt Report keyholder information. aassmenu Menu to the access assignment reporting functions. egrprprt Report access codes / access groups assigned to keyholders. emrdrprt Report specific readers assigned to keyholders. accrmenu Menu to the access definition reporting functions.
  • Page 157 ARKING TICKERS CREEN ITLE UNCTION stkrmenu Menu to parking sticker and license plate management functions. stkrentr Select keyholder for parking sticker and / or license plate information entry. stk1entr Enter parking sticker or license plate information for keyholder. stkrrprt Locate keyholder by license plate or parking sticker. stkrrprt1 Display keyholder location information by license plate or parking sticker number.

  • Page 158: Appendix C: Systemt

    C: S — N PPENDIX YSTEM RANSACTIONS UMERICAL EQUENCE...
  • Page 159 C: S — N PPENDIX YSTEM RANSACTIONS UMERICAL EQUENCE...
  • Page 160 C: S — N PPENDIX YSTEM RANSACTIONS UMERICAL EQUENCE...
  • Page 161 C: S — N PPENDIX YSTEM RANSACTIONS UMERICAL EQUENCE Archive immediately.
  • Page 162 C: S — N PPENDIX YSTEM RANSACTIONS UMERICAL EQUENCE...
  • Page 163 C: S — N PPENDIX YSTEM RANSACTIONS UMERICAL EQUENCE through...
  • Page 164 C: S — N PPENDIX YSTEM RANSACTIONS UMERICAL EQUENCE...
  • Page 165 C: S — N PPENDIX YSTEM RANSACTIONS UMERICAL EQUENCE...
  • Page 166 C: S — A PPENDIX YSTEM RANSACTIONS LPHABETICAL EQUENCE Message Message...
  • Page 167 C: S — A PPENDIX YSTEM RANSACTIONS LPHABETICAL EQUENCE C-10 Message Message...

  • Page 168: Appendix D: Program Security Master List

    PPENDIX ROGRAM ECURITY Level 1 = COMPLETE SYSTEM ACCESS ID1_entr ID Security User Entry ID1_rprt ID Security Report ID2_entr ID Security Group Entry ID_menu ID Security Report aassmenu Access Assignments abacentr ABA Configuration Entry abacrprt ABA Configuration acc_menu Access Definition accrmenu Access Definition accsarch...
  • Page 169 outsrprt Outstanding Tickets overrprt Tenant Overage p422rprt SE/422 PIN Report padmmenu Parking Administration parkmenu Parking Control pgacentr Security Entry pgacrprt Security Master List phstrprt Point History plotentr Point/Lot Association pndfentr SE422 PIN Definition pnt_entr Points pnt_rprt Points pol_entr Pollers pol_rprt Pollers prd_rprt Project Reader Report...
  • Page 170 NDEX Access Assignment, 4-8, 5-4 Keyholder Access, 5-4 Keyholder Access Assignment, 4-8 Readers, 5-5 Access Code, 1-2 Access Code Entry, 4-9 Distributed Access codes, 4-9 Host, 4-9 Smart Failsoft, 4-9 Access Control Archive Report, 3-4 Access Control Transaction Archiving [accsarch], 6-15 Access Control Units (ACUs), 1-3 Access Definition, 4-9, 5-6 Access Code Master, 5-6...
  • Page 171 Auto Opens/Activates, 4-42 Automatic Access Control, 1-6 Automatic Activate / Deactivate, 1-6 Automatic Restart, 1-16 Automatic Unlock/Lock, 1-6 Basic System Usage, 1-16 Logging Off, 1-15 Biometric Identifiers, 1-3 Building Modes, 2-11 CCTV, 1-17 Clearing a Field, 1-14 Communications Monitor, 1-6 Company, 1-2 Complete Portability, 1-5 Contact Alarms, 1-4...
  • Page 172 Data Entry Sequence, 1-9 Data Item Selection, 2-2 Database Changes, 1-7 Database Maintenance [db_menu], 6-14 Definition, General Trace, 1-3 Transactions, 1-3 Definition, Inputs Fire Alarms/Heat Sensors, 1-4 Definition, Principal System Functions Auto Unlock/Lock, 1-6 Definitions Access Control, 1-6 Definitions, Basic System Usage, 1-9 Applications Screens, 1-10 Logging On, 1-9 System Screens, 1-10...
  • Page 173 Definitions, Principal System Functions, 1-6 Auto Activate/Deactivate, 1-6 Automatic Access Control, 1-6 Communications Monitor, 1-6 Flexible Event Handling, 1-6 Independent PIN Entry, 1-6 Manual Access Control, 1-6 Two-Man Rule, 1-6 Definitions, Readers, 1-4 Digital Key Reader, 1-4 Magnetic Card Reader, 1-4 Readers, Sensors, 1-4 Definitions, Reporting, 1-7 Alarms and Responses, 1-7...
  • Page 174 NexSentry Reader Report Defined, 4-38 Reader Entry, 4-32 Reader Report, 4-35 Readers, 4-31 Devices Configuration Reports Devices, 5-14 Readers, 5-15 Digital Key Reader, 1-4 Disk Almost Full Warning, 2-12 Display All Users Logged In [showwho], 6-7 Display All Valid Logins [showuser], 6-7 Display Current Date and Time [showdate], 6-7 Display Database Statistics [dbstats], 6-14 Distributed Access Codes, 4-9...
  • Page 175 Forgive Passback, 2-10 Full Screen Monitoring, 2-12 Function Keys, 2-2 General Definitions Keyholder, 1-2 Guard Tour, 1-18 Hardware Configuation 422 Hardware Definition, 4-44 Hardware Configuration 422, 4-28 422 Pin Definition, 4-43 818, 4-28 8xx Series, 4-24 ABA Configuration, 4-47 Areas, 4-19 Device Report, 4-43 Devices, 4-21 Dialer Entry, 4-45...
  • Page 176 Job Category, 1-2 Journal Archive [jourarch], 6-16 Journal Reporting [jourrprt], 6-16 Key Inventory [invtmenu], 6-20 Key Inventory Entry [cdinentr], 6-21 Key Inventory Report [cdinrprt], 6-21 Key Inventory Status Code Report [statrprt], 6-20 Key Number, 1-2 Keyholder, 1-2 Access Assignment, 4-8 Keyholder Access Entry, 4-5 Keyholder Entry, Page 1, 4-2 Keyholder Entry, Page 2, 4-4...
  • Page 177 Microprocessor Access Control Units, 1-3 Biometric Hand Reader, 1-3 Miscellaneous Information, 1-15, 2-12 Modified Usage of Invalid Facility Code Log, 2-15 Modify Passwords [mod_pass], 6-4 Monitor Security Activity, 2-1 Monitoring Security - Passwords, 2-14 Motion Sensors, 1-4 Moving Backwards in a Field, 1-14 Moving Between Data Fields, 1-12 Moving to Prior Screens, 1-13 MSMs, 1-5...
  • Page 178 Program Security Entry Definition [pg1_entr], 6-5 Purge a Pending Report [purgrprt], 6-8 Reader Entry, 4-32 Reader Report, 4-35 818, 4-37 NexSentry, 4-38 Reader Report, 422, 4-36 Readers, 1-4 Real Time Control Maps, 2-8 Realtime Passback Zone Report, 3-9 Remote Alarms, 1-5 Remote Devices, 2-11 Remote Dial-Up Interface, 1-18 Reporting, 1-7...

  • Page 179: Security Master List [Pgacrprt]

    Review Transactions Full Screen, 2-7 Review Transactions Function Keys, 2-8 REX, 1-5 Sample System, 1-7 Screen Access, 4-1 Screen Examples, 1-11 Searching With Partial Information, 1-13 Section Organization, 2-1 Security Master List [pgacrprt], 6-6 Security Reports, 3-1 Select Zone, 2-6 Select Zone Function Keys, 2-6 Selecting Screens, 1-12 Shutting Down, 1-16...
  • Page 180 Tenant, 1-3 Tenants, 4-17, 5-11 Time and Attendance, 1-18 Time Code, 1-3 Time Codes, 4-16, 5-10 Trace, 1-3 Transaction History Report, 3-3 Sample Report, 3-4 Transactions, 1-3 Transactions [tranentr], 6-12 Two-Man Rule, 1-6 User Defined Information, 4-49 Using Screens and Fields, 1-12 Moving Between Data Fields, 1-12 Moving to Prior Screens, 1-13 Selecting Screens, 1-12...

Table of Contents