Академический Документы
Профессиональный Документы
Культура Документы
••••••••••••••••••••••••••••••••••••••••••••••••••••••
Version 10.3.0
Revised July 2012
Software House makes no representations or warranties with respect to the contents hereof and
specifically disclaims any implied warranties of merchantability or fitness for any particular
purpose. Furthermore, Software House reserves the right to revise this publication from time to time
in the content hereof without the obligation to notify any person of any such revision or changes.
NOTE:
The specifier should carefully select the
portions of this document that fit the intended
application. Feel free to consult w ith Softw are
H ouse regarding your particular application.
C• CURE and Softw are H ouse are registered trademarks of Tyco International Ltd. and its respective
companies.
The trademarks, logos, and service marks displayed on this document are registered in the United States
[or other countries]. A ny misuse of the trademarks is strictly prohibited and Tyco International Ltd. w ill
aggressively enforce its intellectual property rights to the fullest extent of the law , including pursuit of
criminal prosecution w herever necessary. A ll trademarks not ow ned by Tyco International Ltd. are the
property of their respective ow ners, and are used w ith permission or allow ed under applicable law s.
Product offerings and specifications are subject to change w ithout notice. A ctual products may vary from
photos. N ot all products include all features. A vailability varies by region; contact your regional sales
manager.
This manual is proprietary information of Softw are H ouse. Unauthorized reproduction of any portion of
this manual is prohibited. The material in this manual is for information purposes only. It is subject to
change w ithout notice. Softw are H ouse assumes no responsibility for incorrect information this manual
may contain.
A ll rights reserved.
Page ii
C•CURE 800/ 8000 Engineering Specifications V10.3.0
1. Introduction ................................................................................................................... 1
1.1 General Description _________________________________________________________ 1
1.2 Description of Work _________________________________________________________ 2
1.3 Submittals _________________________________________________________________ 2
1.3.1 Shop Drawings .......................................................................................................................................2
1.3.2 Product Data ..........................................................................................................................................2
1.3.3 Contract Close-Out Submittals...............................................................................................................3
1.3.4 Manuals .................................................................................................................................................3
1.3.5 As-Built Drawings ...................................................................................................................................4
1.4 Quality Assurance ___________________________________________________________ 4
1.5 Warranty __________________________________________________________________ 5
2. Products ........................................................................................................................ 5
2.1 Manufacturers _____________________________________________________________ 5
2.1.1 Security Management Control System Software ...................................................................................5
2.1.2 Security Management Control System Field Hardware .........................................................................5
2.2 Server Configuration _________________________________________________________ 5
2.2.1 Minimum CPU Capacities .......................................................................................................................5
2.2.2 High Resolution Graphics .......................................................................................................................6
2.2.3 Information Storage ...............................................................................................................................6
2.2.4 Information Backup/Retrieval................................................................................................................6
2.2.5 Communications Rates ..........................................................................................................................6
2.2.6 Printers...................................................................................................................................................7
2.2.7 Mouse ....................................................................................................................................................7
2.2.8 Communication Ports ............................................................................................................................7
2.2.9 Encryption ..............................................................................................................................................8
2.2.10 Redundant Array of Independent Disks (RAID) .................................................................................8
2.2.11 Symmetric Multiprocessor (SMP) Support ........................................................................................9
2.2.12 Redundancy ......................................................................................................................................9
2.3 Operator Workstations _______________________________________________________ 9
2.3.1 Minimum CPU Capacities .......................................................................................................................9
2.3.2 Local Area Network..............................................................................................................................10
2.4 Printers __________________________________________________________________ 10
2.4.1 Supported Printers ...............................................................................................................................10
2.4.2 Shared Printers ....................................................................................................................................10
2.4.3 Dot Matrix Printer ................................................................................................................................10
2.4.4 Ink jet Printer .......................................................................................................................................10
2.4.5 Laser Printer .........................................................................................................................................10
2.5 Software _________________________________________________________________ 11
2.5.1 Software Capacities .............................................................................................................................11
2.5.2 Software Operation .............................................................................................................................12
2.5.3 Millennium Compliance .......................................................................................................................13
2.5.4 Open Database Connectivity ...............................................................................................................13
2.5.5 Language Localization ..........................................................................................................................14
2.5.6 Card Formats........................................................................................................................................14
Page iii
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page iv
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page v
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page vi
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page vii
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page viii
C•CURE 800/ 8000 Engineering Specifications V10.3.0
1. Introduction
••••••••••••••••••••••••••••••••••••••••••••••••••••••••
This specification provides all information necessary to produce a complete proposal for a
sophisticated, easy-to-use, multi-tasking, multi-user Security M anagement Control System
(SM CS). The SM CS shall include all computer hardw are and softw are, intelligent field advanced
processing controller (apC/ L/ 8X and iSTA R), communication devices, card readers/ keypads,
access cards, I/ O boards, pow er supplies, conduit, racew ays, enclosures, mounting hardw are,
and all other equipment as indicated on the contract draw ings and as specified herein. A ll
material shall be the manufacturer’s standard catalog products.
The Server (H ost) PC, shall have a Pentium 600 to 1.5 GH z central processor. The Client
(Operator w orkstation) PC(s) shall have a Pentium 400 or greater central processor. The
exact hardw are configurations shall be described in a later section of this specification.
The Security M anagement Control System shall be designed to grow as project needs
grow . The system shall be simple and economical enough to support a single site, yet
pow erful enough to manage a multi-site netw ork.
The system shall have true multi-tasking and remote terminal capability; independent
activities and monitoring can occur simultaneously at different locations. The Operator
w orkstation (Client) shall be very easy to use. It shall employ icon-based menus and
provide a mouse-driven interface for system operation and the creation of color graphic
maps.
The Security M anagement Control System shall be designed to support Softw are H ouse’s
full line of distributed processing based controllers.
A ll objects w ithin the system, i.e., Doors, Readers, Time Intervals, etc., shall be addressed
by a unique name. The uses of point numbering or mnemonics shall not be accepted.
Field devices, such as card readers, alarm inputs, control points, etc., shall be connected
to fully distributed intelligent field controllers (apC/ 8X/ 8X and iSTA R) capable of
operating w ithout host computer intervention.
Page 1
C•CURE 800/ 8000 Engineering Specifications V10.3.0
1.3 Submittals
1.3.1 Shop Drawings
Provide complete shop draw ings w hich include the follow ing:
• Indicate all system device locations on architectural floor plans. N o other system(s)
shall be included on these plans.
• Include full schematic w iring information on these draw ings for all devices.
Wiring information shall include cable type, conductor routings, quantities, and
connection details at devices.
• Include a complete access control system one-line, block diagram.
• Include a statement of the system sequence of operation.
Page 2
C•CURE 800/ 8000 Engineering Specifications V10.3.0
• Protocol description
• Rigid disk system size and configuration
• Backup/ archive system size and configuration
• Start up operations
• System expansion capability and method of implementation
• System pow er requirements and UPS sizing
• A description of the operating system and application softw are.
1.3.4 M anuals
Final copies of the manuals shall be delivered w ithin thirty (30) days after completing
the installation test. Each manual’s contents shall be identified on the cover. The manual
shall include names, addresses, and telephone numbers of each security system
integrator installing equipment and systems and the nearest service representatives for
each item of equipment for each system. The manuals shall have a table of contents and
labeled sections. The final copies delivered after completion of the installation test shall
include all modifications made during installation, checkout, and acceptance. The
manuals shall contain the follow ing:
Page 3
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The security system integrator shall have been regularly engaged in the installation and
maintenance of integrated access control systems similar in size and scope to that
outlined herein for a period of no less than five (5) years.
The security system integrator shall supply information attesting to the fact that their
firm is an authorized product dealer for the system proposed.
The security system integrator shall supply information attesting to the fact that their
installation and service technicians are competent factory trained personnel capable of
maintaining the system and providing reasonable service time.
The security system integrator shall provide a minimum of three (3) references w hose
systems are of similar complexity and have been installed and maintained by the
security system integrator in the last five (5) years.
Page 4
C•CURE 800/ 8000 Engineering Specifications V10.3.0
There shall be a local representative and factory authorized local service organization
that shall carry a complete stock of parts and provide maintenance for these systems.
Local shall be defined as an area in a [ ] mile radius of installed location.
1.5 Warranty
The follow ing changes to the Warranty terms take effect M ay 11, 2000:
• The Warranty on C•CURE 800/ 8000 bundled system packages and softw are only
packages w ill be 14 months from the date of shipment, or 1 year from date of
registration, w hichever is shorter. Under the terms of the w arranty, version upgrades
are available “ at no extra charge” only if the customer is under a valid w arranty or
valid SSA . Bug fix releases w ill be made available to all customers under a valid
w arranty or SSA (critical bugs excluded). Refer to the SSA Entitlements in the price
book for specific details
• The softw are w arranty w ill now be activated at the time of installation assuming the
Softw are License Registration has been completed and is on file at Softw are H ouse.
• Before M ay 11, 2000, the previous terms of the Warranty shall apply, that is, the
w arranty for all unbundled (softw are only) packages w ill be 90 days from date of
installation, and the w arranty on bundled system packages w ill remain 14 months
from the date of shipment, or 1 year from date of registration, w hichever is shorter.
2. Products
•••••••••••••••••••••••••••••••••••••••••••••••••••
2.1 M anufacturers
2.1.1 Security M anagement Control System Software
Softw are H ouse C•CURE 800/ 8000 System
Page 5
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 6
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.2.6 Printers
The SM CS shall support report printers. The report printers may be connected to the
parallel port of the Server or Client computers.
2.2.7 M ouse
The SM CS shall only utilize a mouse as the man - machine interface. The mouse shall be
used throughout the application.
Page 7
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.2.8.5 On-line/Off-line
The system shall allow the operator to put a communications port
on-line or off-line. If the communications port is placed off-line, the
system shall not use the port to communicate to field devices
configured on that port. If the communications port is put on-line,
the system shall use the port to communicate to field devices
configured on that port.
2.2.8.7 I P address
For communications ports on a netw ork device, the system shall
allow the operator to define the IP address of the device, as w ell as
the local port address, to w hich the remote field devices are
connected.
2.2.9 Encryption
It shall be possible to configure a system such that the communications
betw een the H ost computer and the apC/ L/ 8X panel or iSTA R controller is
encrypted.
Page 8
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.2.10.1 RAI D 1
The system shall support the use of RA ID level 1. RA ID level 1
provides complete data redundancy.
2.2.10.2 RAI D 5
The system shall support the use of RA ID level 5. RA ID level 5
includes disk striping at the block level and parity.
2.2.12 Redundancy
Through the use of third-party softw are and associated hardw are, the system shall
support a second server for redundant capability. During normal operation, data shall
be w ritten to either server and shall be mirrored to its counterpart in a bi-directional
mirroring process.
If a failure is detected, it shall be verified across both the netw ork and the mirrored data
links. When the failure has been verified, the surviving server shall assume the functions
and identities of the failed server w ithout having to sacrifice its ow n identities or
functions. A pplications originally running on the failed server are restarted on the
surviving server.
Page 9
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.4 Printers
2.4.1 Supported Printers
The system shall support as a report printer(s) any printer for w hich a printer driver
exists w ithin the Window s XP, 2003, Vista, Window s 7, and Window s 2008 operating
systems. These printers may be dot matrix impact printers, ink jet printers or laser
printers.
Real time activity printers shall be form-based printers, i.e. dot matrix. Laser printers
shall not be used as real time event printers.
Page 10
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5 Software
2.5.1 Software Capacities
System softw are and language development softw are shall be existing, industry
accepted, and of a type w idely used in commercial systems. Operating system shall be
multi-user/ multi-tasking capable of operating in a non-proprietary CPU. The
application softw are, substantially as offered, shall be w ritten in a high level, industry
standard programming language. The system shall be modular in nature, allow ing the
system capacities to be easily expanded w ithout requiring major changes to the system
operation and maintaining all defined system data as w ell as historical information.
A ll System functions shall be accessible via point and click mouse control. Systems
requiring command string control or complex syntax are not acceptable.
The system softw are shall include the follow ing features and be configured for
minimum:
• thirty tw o (32) [32, 64,128, 256, 512, 1000, 2500*], 3000*] readers
• ten thousand (10,000) [10,000, 40,000,250,000,500,000*] active card holder records
• tw o (2) [4, 8, 12, 64, 128*] simultaneous programming locations
• nine hundred-ninety nine (999) client PC’s definable on Server
• supporting up to seventeen (17) simultaneous printers
• one hundred tw enty eight (128) time schedules
• tw o hundred and fifty six (256) programmable holidays for apC/ L/ 8X and
unlimited for iSTA R
• N umber of A ssets [800/ 1 N A ] [800/ 5, 800/ 10 40,000) [800/ 20 = 250,000, 800/ 30 =
250,000, 800/ 40 = 250,000, 8000 Enterprise System = 500,000]
• one hundred tw enty eight (128) [128, 256,512, 1024, 2500, 5,000, 10,000*] input
points
• one hundred tw enty eight (128) [128, 256,512, 1024, 2500, 5,000, 10,000*] output
control points
• 128 total configurable card formats for the entire system
• forty thousand (40,000) operator accounts w ith unlimited definable privilege levels
• audible alarm annunciation at Operator w orkstation
• unlimited graphic maps to be displayed on the Operator w orkstation monitor
• multi-user, multi-tasking operating system
• dial up remote diagnostics
• event scheduling
• an unlimited number of user defined card holder data fields
• an unlimited number of door groups
• an unlimited number of areas
• card holder access privilege activation date and time
• card holder access privilege expiration date and time
• clearance activation date and time
Page 11
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The configuration tools shall utilize intelligent configuration controls. The system shall
be structured such that the operator shall not be able to perform configuration functions
that are not valid based upon the configuration used. For example, if a tw o (2) door field
control panel is being configured, the system shall not allow the operator to configure
door number three (3) on that panel.
Where the operator may be presented w ith a choice of pre-defined objects, the system
shall provide a pop-up pick list. The operator may choose an object in the listing by
double clicking on the item. If the object has not been pre-defined, the operator may
define the new object from the pop-up pick list.
The user shall log into the system using a username and passw ord configured w ithin the
security management control system. A lternatively the security system shall be able to
utilize the user name and passw ord credentials of the operating system, thus allow ing
the use of added OS features such as; inactivity timer/ auto log-off, minimum passw ord
length, etc.
The system shall support the option to search using a ‘w ildcard’ character w ithin
brow ser lists. The system shall allow the user to do ‘w ildcard search’ for personnel
records in A dmin; w ildcard search for various object names in select and sub- select
screens of A dmin; as w ell as w ildcard’ search for object names in M onitor Station.
The system shall utilize dynamic icons. The dynamic icons shall change appearance, in
both color and icon display based upon the status of the associated object. This
appearance change shall occur in real time and shall not require the system operator to
perform a screen refresh or exit the current screen.
Page 12
C•CURE 800/ 8000 Engineering Specifications V10.3.0
For intelligent field panels hard w ired to the host computer, the dynamic icons shall
reflect the true state of the device represented by the icon. If an operator issues a
command to unlock a door, and the field panel w hich controls that door is not in
communication w ith the host computer, the icon shall not change state or appearance.
Where certain data fields w ithin data screens may contain the same information, the
system shall provide the ability to define default settings for these data entry fields. The
operator shall be able to change the default setting w ithout impacting objects that have
already been defined.
The softw are manuals for the Security M anagement Control System shall provide
complete documentation outlining the database schema used w ithin the system. This
documentation should be sufficient to allow a person, moderately skilled in databases,
to extract information from the Security M anagement Control System's databases. The
database schema information shall include information on the personnel tables, history
and configuration tables.
It shall be possible to use third party report tools, such as Crystal Reports, to generate
reports not already provided by the Security M anagement Control Systems, such as
statistical or graphical reports of system activity.
Page 13
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 14
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The system shall support the follow ing Government Card and reader formats:
Integrated Electronics (IE) formats:
• 01SM R-4011 200-bit Wiegand BCD M SB FA SC-N
• 01SM R-4012 200-bit Wiegand BCD M SB FA SC-N + 32-bit H M A C
• 01SM R-4015 54-bit Wiegand Binary
• 01SM R-4014 80-bit Wiegand binary + 32-bit H M A C
• 01SM R-4016 82-bit Wiegand binary + 32-bit H M A C
• 01SM R-4017 200-bit Wiegand BCD LSB FA SC-N
• 01SM R-4018 200-bit Wiegand BCD LSB FA SC-N + 32-bit H M A C
H ID formats:
• 64-bit M SB
• 64-bit M SB w ith H M A C
• 64-bit LSB
• 64-bit LSB w ith H M A C
• 64-bit M SB w ith Expiration Date
• 64-bit M SB w ith H M A C and Expiration Date
• 128-bit M SB or LSB w ith H M A C
• 128-bit M SB or LSB w ith H M A C and Expiration Date
• 128-bit M SB or LSB
• 160-bit FA SC-N
• 160-bit FA SC-N w ith Expiration Date
• 160-bit w ith H M A C and Expiration Date
• 200-bit FA SC-N
• 200-bit FA SC-N w ith H M A C
Page 15
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.7.2 M emory
The allocation of memory, betw een cardholder records and
historical event buffering, w ithin each apC/ L/ 8X and iSTA R shall
be dynamic. A ny memory not being used for the storage of
cardholder records shall be available for the buffering of historical
events.
Page 16
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.7.8 Expansion
System expansion must be modular. A dditional apC/ L/ 8Xs
required for incremental system expansion shall be available in tw o
(2) and eight (8) door configurations to allow for maximum
installation flexibility and optimum cost. iSTA R controllers shall be
available in 2, 4, 8 and 16 door configurations.
2.5.8.1 Addressing
Each time specification shall be addressed w ithin the system by a
unique fifty (50) character user defined name. The use of code
numbers or mnemonics shall not be accepted.
2.5.8.2 H olidays
The system softw are shall allow a maximum of tw o hundred and
fifty six (256) holidays (apC/ L/ 8X) and an unlimited amount of
holidays per iSTA R.
The SM S shall support tw o modes of operation for user-defined
holidays w hich shall be selectable by a system option. There shall
be a default mode and a distributed mode of operation.
In the default mode the user shall assign holidays to holiday lists,
and the holiday lists shall be dow nloaded to all system controllers
Page 17
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.8.3 Configuration
Each time specification shall be comprised of user defined time
segments. Each time segment shall be day(s) of the w eek, to include
holidays, and a starting time and an ending time. The system shall
provide grouping of days, i.e. M on. - Fri, for easy system
configuration.
2.5.8.4 Setup
The system softw are shall have the capacity for a minimum of one
hundred tw enty eight (128) user programmable time specifications.
Each time specification shall be comprised of allow a minimum of
eighteen (18) individual time segments.
2.5.8.5 Assignment
The system shall allow a time specification to be assigned to:
• A ccess Control Clearance
• Inputs
• Outputs
• Doors
• Scheduled functions
• A larm events
2.5.9.1 General
The system shall allow the end user to configure the host server,
operator w orkstations, and field hardw are devices, such as
apC/ L/ 8X and iSTA R controllers, clearances, elevators, some
groups and reports to be in different time zones. A time zone is a
Page 18
C•CURE 800/ 8000 Engineering Specifications V10.3.0
"time zone" such as Eastern Standard Time and does not indicate a
time specification.
2.5.9.6 I nterdependency
Objects w ithin the system shall have an associated time zone
allow ing the object to operate using the local time w here the object
is physically located. The objects to w hich time zones shall be
associated include operator w orkstations and apC/ L/ 8X and
iSTA R controllers.
A ll items associated w ith an object shall inherit the time zone of the
associated object. For instance, if an apC/ L/ 8X is assigned to a
time zone, all items controlled by that particular apC/ L/ 8X, such
as reader, doors, elevators, Intrusion Zones, inputs and outputs,
shall be in the same time zone as the apC/ L/ 8X. A n operator
w orkstation can be associated w ith a time zone so manual actions
performed by an operator at that w orkstation shall occur in the
time zone of the w orkstation.
If an operator attempts to configure the system and creates a time
zone mismatch, such as defining a clearance code that contains
door/ time combinations spanning multiple time zones, the system
shall provide an informational w arning message. The system shall
further provide a time zone exception report that shall list the
places w here the time zone mismatch occurs.
2.5.9.7 Assignment
The system shall allow time zones to be assigned to:
(a) apC/ L/ 8X and iSTA R controllers
Page 19
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 20
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.10 Events
2.5.10.4 Configuration
The system shall allow an event to be configured to:
• Require or not require operator acknow ledgment
• Require or not a message to be logged by the operator w hen the event is
acknow ledged and/ or cleared.
• N ot be cleared unless a log message is entered by the system
operator responding to the event
• Display or not display the event activation
Page 21
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 22
C•CURE 800/ 8000 Engineering Specifications V10.3.0
• start tour
• cancel tour
• suspend tour
• resume tour
• CCURE Watch flash dow nload
• CCURE Watch DSP filter dow nload
• CCURE Watch activate selected flash
• CCURE Watch request file upload
• CCURE Watch request file upload timed
• CCURE Watch cancel flash loading
• activate N etVue action
• arm N etVue alarm
• disarm N etVue alarm
• latch event
• unlatch event
• toggle event
• enable keypad commands
• activate BiD action
• toggle intr zone mode
• disable keypad commands
• show intr zone status
• show intr zone offnormal points
• clear violated intr zone
• arm local intr zone
• disarm local intr zone
• toggle local intr zone
• force arm local intr zone
• show local intr zone status
• show local intr zone offnormal points
• clear local violated intr zone
• shunt input
• activate event until overide
• deactivate event until overide
• set reader security level 1
• set reader security level 2
• set reader security level 3
• set reader security level 4
• enable counting only
• enable counting for events
• enable counting (access restrictions)
• set count
• set personnel group count
• set escorted visitors count
• set escort count
• set supervisee count
• set supervisor count
• lockout grace person
• enhanced reader flash
• enhanced reader cancel flash
• set reader security level 0
Page 23
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 24
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.11.3 Construction
Each door shall be comprised of one (1) or tw o (2) card readers, a
door position status alarm point, a request to exit alarm device, PIN
pad control, and door lock control output point designator. The use
of a second card reader and a request to exit device should be
Page 25
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 26
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 27
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.12.1 D efinitions
2.5.12.1.1 Lock Sensor I nput - The system shall allow the user to configure
multiple lock sensor inputs at the door. The system shall monitor the lock sensor
inputs and report lock unsecured or lock tamper w hen the input is in the incorrect
state based on the current state of the door and other associated inputs.
2.5.12.1.2 Lock Release I nput - The system shall allow the user to configure
multiple lock release devices at the door. The system shall monitor the lock release
devices, optionally annunciate changes in their state, and use their state as part of the
basis for deciding the lock unsecured, lock tamper, and door open alarms.
2.5.12.1.3 M ultiple D SM /RTE I nput - The system shall allow the user to configure
multiple door sw itch monitor inputs (DSM ) and Request to Exit (RTE) inputs at the
door.
2.5.12.1.4 D oor Forced Alarm Suppression – The system shall support the ability
for the user to configure a time based or manual suppression of door forced open
alarms on a per door basis.
2.5.12.1.5 D oor H eld Alarm Suppression - The system shall support the ability for
the user to configure a time based or manual suppression of door held open alarms
on a per door basis.
2.5.12.1.6 Time and M anual Control of RTE - The system shall support the ability
for the user to configure a time based or manual control of the operation of the RTE
function on a door.
Page 28
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.12.1.7 D oor Latch Relay Change - The system shall support the ability for the
user to configure the door latch/ strike relay (DLR) to be activated for the full door
unlock time regardless of DSM state. The door w ould remain shunted for this
period.
2.5.12.1.8 D oor Shunt Operation Change - The system shall support the ability for
the user to configure the door to remain shunted for the full shunt time regardless of
the state of the DSM .
2.5.12.1.9 D oor debounce Per D oor Basis/Alarm Grace - The user shall be able to
program a time interval for alarm grace after the unlock time interval expires or the
door closing to eliminate false alarms caused by bouncing doors.
2.5.12.2 Configuration
The general door screen shall allow the user to bring up a separate
screen named “ door monitoring” to configure the lock release
devices and other door monitoring settings for that door.
2.5.12.2.2 Selected I nputs – Shall display all inputs monitored by the door. Show s
the name and input type.
2.5.12.2.3 Edit I nputs – Button w idget that allow s users to edit inputs.
2.5.12.2.4 Add – Shall add the selected input in the A vailable Inputs list to the
selected list as the selected input type. Removes it from the available list. Enabled
w hile an input is highlighted in the available list.
2.5.12.2.5 I nput type column in Selected I nputs browser – Indicates the purpose
for w hich the door shall use the input. For most inputs, w hen an input is first added
to the list, the type w ill be N one and the correct type must be selected – the screen
cannot be exited if any input has type “ none” . A n input that has been previously
selected as a lock release input for another door shall have type ‘lock release’ w hen
added to a new door. These types of the ‘lock release’ inputs cannot be changed
unless the current door is the only door using that lock release input.
2.5.12.2.6 Remove – Removes the highlighted input in the Selected Inputs list from
the controlled list. Enabled w hile an input is highlighted in the Selected Inputs list.
2.5.12.2.7 Remove All – Removes all of the inputs in the Selected Inputs list from
the controlled list. Enabled w hile the controlled list is not empty.
2.5.12.2.8 Unlock grace time 1/10 seconds – This allow s the configuration of the
unlock grace time for the door. Units are 1/ 10 seconds.
2.5.12.2.9 D oor open grace time 1/10 seconds – This allow s the configuration of the
door open grace time for the door. Units are 1/ 10 seconds.
2.5.12.2.10 D oor close debounce time 1/10 seconds – This allow s the configuration
of the door close debounce time for the door. Units are 1/ 10 seconds.
Page 29
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.12.2.11 Change time 1/10 seconds – (Lock release, Bond sensor, Latch bolt, Cam
sensor, DSM side A , DSM side B, or RTE). These fields allow configuration of the
value of the time during w hich this type of input is expected to change after other
conditions have changed. Units are 1/ 10 seconds.
2.5.12.3 Events
Four access events associated w ith enhanced door monitoring shall
be available to the user w hen the ‘A ccess Events…’ button is
selected.
2.5.12.3.1 D oor Open Alarm causes event - The user shall be able to configure a
unique event that shall be activated w hen the door open alarm is active for this door.
Double-clicking brings up the Event Select Window .
2.5.12.3.2 Lock Unsecured causes event - The user shall be able to configure a
unique event that shall be activated w hen the lock unsecured alarm is active for this
door. Double-clicking brings up the Event Select Window .
2.5.12.3.3 Lock Tamper causes event - The user shall be able to configure a unique
event that shall be activated w hen the Lock Tamper alarm is active for this door.
Double-clicking brings up the Event Select Window .
2.5.12.3.4 D SM Tamper causes event - The user shall be able to configure a unique
event that shall be activated w hen the DSM Tamper alarm is active for this door.
Double-clicking brings up the Event Select Window .
2.5.12.3.5 Event Activation After Consecutive Rejects - The system shall allow the
user to configure the number of consecutive rejects, and the time that can lapse
betw een the consecutive rejects. Consecutive rejects can be cards, keypad commands,
or pin number rejects. If the number of consecutive rejects occurs before the timer
expires, a system activity message is displayed on the M onitoring Station.
2.5.12.4 M onitoring
Page 30
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.12.5 Journal
2.5.12.5.1 Lock Tamper Alarm – Shall report input name indicating w hich input
caused the lock tamper alarm condition.
2.5.12.5.2 Lock Unsecured Alarm – Shall report input name indicating w hich input
caused the lock unsecured alarm condition.
2.5.12.5.3 D oor Open Alarm – Shall report input name indicating w hich input
caused the door open alarm condition.
2.5.12.5.4 D SM Tamper Alarm – Shall report input name indicating w hich input
caused the DSM tamper alarm condition.
Page 31
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 32
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.15 Operators
2.5.15.1 Password
The system softw are shall be capable of identifying up to forty
thousand (40,000) system operators. Passw ords shall be up to
tw enty (20) characters.
Page 33
C•CURE 800/ 8000 Engineering Specifications V10.3.0
When building the privilege level, the system w ill provide the
administrator w ith a listing of all the commands in the system. By
default, all system commands w ill be assigned to the N o A ccess
access right classification. The administrator can then move the
command to the appropriate access rights classifications.
Page 34
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The system administrator shall then define the specific objects, i.e.
doors, alarm inputs, outputs, field panels, etc. w ithin the system an
operator can monitor.
If the operator is not authorized to monitor an object, by extension,
the operator shall be restricted from issuing manual commands
against the object.
Page 35
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 36
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The user shall be able to copy information from one personnel record to
another. A fter filling in the necessary fields, the user can click the OK button
to save or the Cancel button to discard. If the user selects the N ext button, the
current record is saved and the next record is created for editing. This method
utilizes the same behaviors as a regular addition into the cardholder database.
A utomated card number increment shall also be supported by the Copy
action. Unique fields such as Card N umber, Pin and Issue Code shall not be
copied over. N either shall the fields in the USERS table because
users.user_name is utilized as a unique index in the database table.
Page 37
C•CURE 800/ 8000 Engineering Specifications V10.3.0
(p) First and last name of operator that performed last edit of the card
holder information. This shall be defined by the system and shall be
view only to the operator.
(q) Date and time last edit w as performed on the card holder information.
This shall be defined by the system and shall be view only to the
operator.
(r) Stored image of the person
(s) Stored signature of the person
(t) Identification badge layout assigned to the person
(u) Date last image w as captured/ saved
(v) Date last identification badge w as printed
(w ) Supervision Status
• Supervisor
• Supervised
Page 38
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 39
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 40
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The system shall also provide the ability to generate the same
format file of existing card records, allow ing the information in the
system to be exported to other computers and applications. The
system shall allow the user to select the card records that shall be
included in the export file.
Page 41
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The system shall provide the ability in the personnel screen to allow
configuration of personnel as exempt from anti-passback testing.
This flag shall w ork w ith the A P Event flag on that screen so that if the A P
Event flag is set but the person is exempt from testing, they shall gain access
but shall still trigger anti-passback events if they violated anti-passback.
The user shall have the option to display all previous door activity by selecting
the “ Complete prev. doors” button. A fter the replay is finished, the user can
either save the result by selecting the “ Save” button, or print the result w ith
the “ Print” button. During the replay, the user can cancel it w ith the “ Stop”
button.
Page 42
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.19.1 Overview
The system shall allow for the segmentation of data in the systems
database such that different user groups can access only the data in
their ow n partitions or in partitions designated as shared. The
system shall also have the ability to assign any combination of
partitions to a particular user, w hile assigning one as the “ home”
partition. Partitioning in conjunction w ith administration
privileges shall support tw o customer models: a multi-tenant
facility or a campus facility.
2.5.19.3 Administrators
The system administrator is the person responsible for all system maintenance
as w ell as all common data. System administrators can use administration and
monitoring privileges to further restrict user access to both partitioned and
common data.
Page 43
C•CURE 800/ 8000 Engineering Specifications V10.3.0
(a) Personnel
(b) Clearances
(c) Time specifications
(d) Doors
(e) Door Groups
(f) Elevators
(g) Elevator groups
(h) N odes
For each of the customer models previously described, the
remaining object types in the system shall be considered common
data. Some examples of common data security objects include:
(a) Controllers
(b) Floors
(c) Floor groups
(d) Inputs
(e) Outputs
(f) Readers
(g) A reas
(h) Time Zones
(i) Personnel view s
Page 44
C•CURE 800/ 8000 Engineering Specifications V10.3.0
(b) Partition A dministrators w ill have the exact same privileges as they do in
normal partitioning mode (i.e. w hen the above option is not selected).
(c) A ll other users w ill have partitioning enforced the same as w ith normal
partitioning w ith the follow ing exceptions:
• A user may assign any clearance defined in their partition to
any personnel record in any other partition.
• A user may remove any clearance defined in their partition
from any personnel record in any other partition.
• A user may not remove a clearance defined in another partition
from a personnel record in their partition.
• A user may not edit or view the definition of a clearance defined
in another partition that is assigned to a personnel record in
their partition.
(d) A special user editable personnel view , called “ $Global Clearances” w ill
exist on all C•CURE 800 systems w here at least one partition has been
defined, and the “ A ll clearances to be assigned globally on partitioned
system” variable is true. This view defines for all non-partitioned
A dministrators w hat personnel fields a user w ill have read access to
w hen editing a personnel record from a partition other than their ow n.
(e) For a personnel brow se or query, the result list w ill include personnel
from all partitions that match the search criteria.
2.5.20.1 Overview
The system shall provide a means to import personnel information
from an external ODBC database other than import from a flat file.
A dditionally, the import shall execute in the background
periodically to avoid the need to run the A dministration
application each time personnel data is to be imported. The import
Page 45
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.20.5 I nterval
The system shall provide the ability to designate a time interval in
minutes and seconds before the next import query is run during
the designated time specification. The system shall allow the option
of keeping the automated import query option connected betw een
import queries.
Page 46
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.21.1 D efinition
The clearance codes shall be the definition w ithin the card holder
record w hich controls w hen and w here a person or vehicle is
authorized to move w ithin a protected area. The clearance code
shall be a function of combinations of reader locations and time
specifications.
Page 47
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.21.3 Activation/Expiration
The user shall be able to select w hether or not they w ould like a regular door or
elevator clearance to have a custom activation and/ or expiration date and time
assigned.
2.5.21.4 Construction
The system shall provide the operator w ith pick lists of previously
defined doors, door groups and time specifications. The system shall
allow the operator to create a combination of a door or door group
w ith a time specification. The system shall allow each clearance code
to contain a minimum tw enty four (24) door (group) and time
specification combinations.
2.5.22.1 D efinition
Custom Clearances shall allow the user to customize access control clearance
information for each person by adding sets of unique clearance information
including door or door group, time specification and expiration date & time
and/or activation date & time information to the personnel record for a person.
The date & time configuration for the activation and expiration fields on the
clearance screen shall be similar to that for the personnel activation / expiration
date fields, and shall support time zone handling in the same manner that those
fields support it. The date & time shall be configured and presented in the user
interface using the local time zone of the admin user, but shall be stored
internally in GMT.
2.5.22.2 Construction
The card holder record shall include a Custom A ccess tab including all
custom access clearances configured for this person. Clicking on a row
shall highlight and select the clearance to be operated on by the M odify
or Delete buttons. The Type column shall display the access object type:
door, door group, elevator or elevator group. The Name column shall
display the name of the configured access object. The Floor or Floor
group column shall be blank if type is door or door group, otherw ise it
shall display the name of the configured floor or floor group name. The
Time Specification column shall display name of the time specification
configured. The A ctivation and Expiration columns shall be blank if the
field is not configured, otherw ise they shall display the configured
Page 48
C•CURE 800/ 8000 Engineering Specifications V10.3.0
activation and/ or expiration date and time values. The w idth of the
columns shall be adjustable by the user.
2.5.23 Reports
2.5.23.4 M edia
Reports shall be generated from the hard disk and generated to the
operator’s screen, hard disk, or printer(s).
Page 49
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 50
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 51
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 52
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 53
C•CURE 800/ 8000 Engineering Specifications V10.3.0
• Visitor admit
• Visitor reject
• H eld open
• Forced open
• Duress
(4) Door sw itch monitor point
(5) Door request to exit monitor point
(6) Door latch relay
(7) Door alternate shunt (A DA ) relay
(8) Shunt expiration relay
(9) A lternate shunt time
(10) Shunt expiration relay time
(11) Reader 1
(12) Reader 2
(13) Unlock time
(14) Shunt time
(15) Pin entry required during time specification
2.5.23.10.7 Reader
(1) Reader name
(2) Reader description
(3) On-line
(4) Reader technology
(5) controller to w hich reader is connected
(6) Output control point linked to communication failure
(7) Tamper triggers output
(8) Tamper triggers event
(9) Board
(10) Board type
(11) Card format 1
(12) Card format 2
(13) Card format 3
(14) Card format 4
(15) Card format 5
(16) Card format 6
(17) Card format 7
(18) Card format 8 (max for apC/ L/ 8X is now 8 per reader/ per
apC/ 8X panel)
(19) Card format 9
(20) Card format 10 (max for iSTA R is 10 per reader/ 128 total
dow nloaded to an iSTA R. 128 total system-w ide.
(21) Pin required during time spec
(22) Related door/ elevator
(23) Slot index
(24) Time spec enabling pin
(25) Type
2.5.23.10.8 Communication port
(1) Port name
(2) Port description
(3) On-line
(4) Port type
(5) Port time-out delay
Page 54
C•CURE 800/ 8000 Engineering Specifications V10.3.0
(6) IP address
(7) Reconnection retry period
2.5.23.10.9 Real time event printer
(1) Workstation name
(2) Printer description
(3) Printer port identification
(4) Page length
(5) Page w idth
(6) Privilege level
(7) A bnormal status event
(8) Initialization string
(9) H eader (left, center, right)
(10) Footer (left, center, right)
2.5.23.10.10 CCTV matrix sw itcher
(1) Clock synchronization
(2) Communications fail delay
(3) Description
(4) On-line
(5) Poll period
(6) Port
(7) Protocol
(8) Sw itcher name
(9) Wait time
(10) Time zone
2.5.23.10.11 CCTV action
(1) A ction name
(2) A ction type
(3) Description
(4) Parameters
(5) Sw itcher
2.5.23.10.12 H ost modem
(1) Connect to host w ait time
(2) Description
(3) Direction
(4) DTR off timer
(5) Initialization string
(6) M odem answ er delay time
(7) M odem name
(8) M odem phone numbers
(9) M odem response w ait time
(10) M odem status check time
(11) On line
(12) Port
(13) Re-dial/ reconnect delay time
(14) Use DTR
2.5.23.10.13 A dministrative privilege report
(1) Privilege name
(2) Privilege is enabled
(3) Description
Page 55
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 56
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 57
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 58
C•CURE 800/ 8000 Engineering Specifications V10.3.0
(hh) lost
(ii) middle name
(jj) noticed
(kk)person ID
(ll) person type
(mm) PIN
(nn)carpool location used
(oo) driver
(pp)carpool group
2.5.28.4 Performance
Based upon a system, under normal load, containing one thousand
(1,000) card holder records, a duration period of forty eight (48)
hours and fifty five thousand transactions per day, the emergency
roll call report shall begin printing w ithin five (5) minutes of the
expiration of the duration timer. This five-minute requirement
presumes that only one emergency roll call report is being
generated and does not include the time required to print the
actual report.
2.5.28.6 M edia
Reports shall be generated from the hard disk and generated to the
M onitoring Station’s screen or printer(s).
Page 59
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 60
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 61
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 62
C•CURE 800/ 8000 Engineering Specifications V10.3.0
move up/ dow n among the event messages on the screen. The
system operator shall be able to scroll back through the previous
tw enty four (24) hours of system activity. To allow the system
operator to move quickly through the event display, the system
shall provide buttons w hich allow the system operator to move to:
(a) top of display list
(b) bottom of display list
(c) next page of display list
(d) previous page of display list
Page 63
C•CURE 800/ 8000 Engineering Specifications V10.3.0
(a) Duress
(b) N oticed
(c) Reject
(d) Door forced pen
(e) Door held open
(f) H ardw are Tamper
(g) Communications failure
(h) Pow er failure
The system shall allow the operator to select the event message
color based upon the follow ing event priorities:
(a) Critical
(b) H igh
(c) M edium
(d) Low
A detailed status display shall also list any notes that may have
been issued by the system operator w hen the manual command
w as issued.
Operators shall be able to issue a command to cancel active manual
commands.
Page 64
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The Status display / Operator action screens shall allow the system
operator to view the status of the selected device(s), based upon the
activation state and the physical state of the device. The operator
shall be able to individually select a device or device group and
issue a command for the particular device.
(1) The Events status display shall allow the operator to view events based
upon the state of the event. This shall include:
• A ctive events only
• Inactive events only
• Both A ctive and Inactive events
(2) The Events status display shall allow the operator to view events based
upon the armed state of the event. This shall include:
• A rmed only
• Disarmed only
• Both armed and disarmed events
(3) The Events status display shall allow the operator to select an event
from the display pick list and issue a command for that event. These
commands shall include:
• Show causes
• A ctivate selected
• Deactivate selected
• A rm selected
• Disarm selected
(4) The Inputs status display shall allow the operator to view inputs based
upon the state of the point. This shall include:
• A ctive inputs only
• Inactive inputs only
• Both active and inactive inputs
• Supervision errors only
(5) The Inputs status display shall allow the operator to view inputs based
upon the armed state of the input. This shall include:
• A rmed only
• Disarmed only
Page 65
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 66
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 67
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 68
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.5.33 Graphics
2.5.33.2 Programming
The system softw are shall, through the use of a mouse, allow for
placement of device icons on each graphic/ floor plan. The device
icons w hich may be placed on the graphic/ floor plan shall include:
(a) alarm inputs
(b) output control points
(c) doors
(d) other graphics
2.5.33.3 Operation
Upon activation of a selected event, the operator shall, by the use of
a single keystroke, view the associated graphic/ floor plan on the
monitor. The operator shall use the mouse to click on any of the
icons on the graphic and issue a command associated w ith the icon.
Systems requiring a separate monitor or PC for the display of
alarms or floor plan graphics are not acceptable.
2.5.33.4 Storage
The graphics feature shall take advantage of the Client/ Server
system configuration, w ith all graphics being created/ stored on a
shared disk in the netw ork. These graphics shall be available to all
authorized Operator w orkstations.
Real time activity printers shall be form-based printers, i.e. dot matrix. Laser
prints shall not be used as real time event printers.
Page 69
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 70
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 71
C•CURE 800/ 8000 Engineering Specifications V10.3.0
There shall be no limit to the number of privilege levels w hich may be defined in
the system.
Page 72
C•CURE 800/ 8000 Engineering Specifications V10.3.0
By use of the term embedded, it is the specifier’s intention that the paging and
email systems be completely encapsulated w ithin the Security M anagement
Control System. The user interface shall be constructed to be similar in look and
feel to the other modules of the Security M anagement Control System.
2.5.37.1 General
The system shall provide the follow ing tasks through an embedded
email and/ or paging function:
• The ability to access paging carriers via direct connect
communications port, modem, or internet
• The ability to define paging and email recipients
• The ability to associate “ send page” and “ send email” actions
to an event
• The ability to specify w hat data should be sent in each page or
e-mail
Page 73
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 74
C•CURE 800/ 8000 Engineering Specifications V10.3.0
passback, w here the system shall allow them to re-enter an area only after the
specified time has elapsed.
2.6.2 Definition
Page 75
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.6.3.1.2 Passback violation during exit causes event – This event shall be pulse-
activated personal anti-passback ‘passback’, ‘timed anti-passback’, or ‘tailgate’
violations during exit from this area.
2.6.3.1.3 Overdue Asset causes event – This event shall be activated w henever an
asset is overdue.
2.6.3.1.4 One Occupant causes event – This event shall be activated if one person
remains in the area. The event shall be deactivated w hen a second person enters the
area or w hen the one person leaves the area, leaving 0 personnel in the area.
2.6.3.1.5 Failure to enter additional card causes event – This event shall be pulse-
activated w henever an additional card is required (for minimum or supervised
occupancy) and the additional card is never presented.
2.6.3.1.6 M aximum occupancy causes event – This event shall be activated w hen
the area contains personnel numbering the same or more than the configured
maximum number of personnel. The event shall be deactivated w hen someone
leaves. M aximum occupancy number must be configured on the occupancy tab.
2.6.3.1.7 Each access over maximum occupancy causes event – This event shall be
pulsed activated for each access into the area over the maximum. This event is not
activated for the access that actually brings the count to the maximum. M aximum
occupancy must be configured on the occupancy tab. This event only applies to area
maximum, not personnel group maximum; it is not activated w hen the condition is
that the area is not over its configured maximum, even if the access is for a personnel
group that is at its maximum.
2.6.3.1.9 Each access under M inimum Occupancy causes event – This event shall
be pulse-activated for each access out of the area w hen less than the minimum
number of personnel are present. This event is not activated for the access that
actually brings the count to the minimum. M inimum occupancy must be configured
on the occupancy tab. This event only applies to area minimum, not personnel group
minimum; it is not activated w hen the condition is that the area is not under its
configured minimum, even if the access is for a personnel group that is at its
minimum.
Page 76
C•CURE 800/ 8000 Engineering Specifications V10.3.0
contains the maximum number or higher of personnel from any personnel group. If
the event is active because one personnel group reached its limit, and another
personnel group goes into its maximum, the event shall be re-activated. M aximum
personnel group occupancy number must be configured on the occupancy tab for
these personnel groups.
2.6.3.2.5 M inimum Occupancy – The minimum personnel that may be in the area.
N ote that system should validate that the maximum if used, is more than the
minimum, if used.
2.6.3.2.8 Escorted V isitor type personnel do not need escort to enter this area –
Indicates w hether escorted visitor type personnel need escort to enter this area. Used
for configuring exit areas for escorted visitors.
2.6.3.2.9 Last escort cannot exit this area if escorted visitors occupy this area –
Indicates w hether the last escort located in the area is allow ed to leave if any escorted
visitors are present. If checked then the last escort cannot leave if any escorted
Page 77
C•CURE 800/ 8000 Engineering Specifications V10.3.0
visitors are located in the area, unless the escorted visitors also present their cards at
the reader.
2.6.3.2.10 Last supervisor cannot exit this area if supervised personnel occupy
this area – Indicates w hether the last supervisor flagged cardholder located in the
area is allow ed to leave if any supervised flagged cardholders are present. If checked
then the last supervisor cannot leave if any supervised personnel are located in the
area, unless the supervised personnel also present their cards at the reader.
2.6.3.2.15 Add – allow s adding and configuring restrictions for a personnel group
by bringing up the personnel group selection and restriction screen.
2.6.3.2.17 Remove – deletes the highlighted personnel group and related fields.
Enabled w hen a personnel group is highlighted in the brow ser.
2.6.3.3.3 M inimum Occupancy – The minimum personnel from this group that
may be in the area. The maximum shall be 65535. N ote that system should validate
that the maximum if used, is more than the minimum, if used.
Page 78
C•CURE 800/ 8000 Engineering Specifications V10.3.0
the system functions. Please note that one person may belong to only one carpool
group.
2.6.3.3.5 Query Person – The user shall be able to query personnel from the
personnel group screen. If this button is selected then the standard personnel query
screen shall be displayed. Once the user closes the personnel query and results of the
query screen, the system shall try to add all of the personnel that appeared in the
result screen to the selected personnel brow se. If any personnel from the result could
not be added to the selected brow se w indow due to some conflict, a message dialog
box shall be displayed indicating the personnel name and the reason.
2.6.4.1.2 All Areas – contains buttons for actions that act on all areas.
2.6.4.1.3 Area List – show s status information for all areas. Includes area name,
last reported occupancy testing state, occupancy count, occupancy error state, and
comm. state of related controllers. The information on this screen shall be
dynamically updated as it changes.
2.6.4.1.4 Occupancy Testing – show s last reported area occupancy testing mode
as: N on-Occupancy (not tracking personnel presence in area); Counting only
(personnel in area are being counted but events are not triggered and access is not
restricted based on occupancy; Counting for Events (personnel in area are counted
and counts can trigger events; Events, A ccess (personnel in area are counted and
counts can trigger events and access is restricted by occupancy).
2.6.4.1.5 Count – show s last reported count of total personnel in this area. Show s
blank for non-occupancy areas. Show s Unknow n for any area w ith an unlocked door
leading in or out of the area. When the unlocked door becomes locked, the count w ill
go to 0.
2.6.4.1.7 Comm State – shall show N ormal if all controllers w here the area has
readers are communicating. Show s comm. fail if all controllers w here the area has
Page 79
C•CURE 800/ 8000 Engineering Specifications V10.3.0
readers are in comm. fail state. Show s partial if some but not all controllers w here
area has readers is in comm. fail.
2.6.4.1.8 Show D etails – shall pull up the single area status screen show ing
detailed status for this area.
2.6.4.1.9 M anual Actions for Selected – shall contain buttons for manual actions
that act on the highlighted area in the area list. These buttons shall be disabled if no
area is selected.
2.6.4.1.10 Set Count to V alue – shall set the personnel count of the selected area to
the value set in the Count Value field.
2.6.4.1.11 Count V alue – used by the Set Count to Value button. The value filled in
is used only w hen the Set Count to Value button is selected and is not otherw ise
stored. This means that every time this screen is displayed the value starts at the
default. Once a value is filled in that value should remain usable until this screen is
closed. Range 0 to 65535 (blank equals 0).
2.6.4.2.1 Area status I nformation – shall show the status information for this area.
The information shall be the same as that show n in the area list columns on the main
A rea Status screen.
2.6.4.2.2 M anual Actions for Area – shall contain buttons for manual actions
affecting this area.
2.6.4.2.3 Causes of Occupancy Testing state – shall contain a cause list for area
occupancy testing mode state and area manual actions.
2.6.4.2.5 Show Cause of selected – shall show a status w indow for causer of
selected cause line from brow ser, if any. Disabled if none selected.
2.6.4.2.6 Set Count to V alue – shall set this area’s personnel count to the value set
in the Count Value field.
2.6.4.2.7 Count V alue – shall be used by the M anual A ctions for A rea - Set Count
to Value button. The value filled in is used only w hen the appropriate Set Count to
Value button is selected and is not otherw ise stored. Once a value is filled in that
value should remain usable until this screen is closed. Range 0 to 65535 (blank equals
0).
2.6.4.2.8 Personnel Groups List (brow ser) – shall list every personnel group
configured for use w ith this area and any information that the area maintains on a
Page 80
C•CURE 800/ 8000 Engineering Specifications V10.3.0
per-group basis. This includes the count of personnel from that group w ho are in the
area, plus w hether that count is normal, over the maximum, or under the minimum.
This list shall be blank if this area has no personnel group restrictions configured.
2.6.4.2.9 M anual Actions for Group – shall contain buttons for manual actions
affecting this area’s personnel count for the selected personnel group. These buttons
shall be disabled if no group is selected.
2.6.4.2.10 Set Count to V alue – shall set this area’s personnel count of the selected
personnel group to the value set in the Count Value field.
2.6.4.2.11 Count V alue – shall be used by the M anual A ctions for Group - Set
Count to Value button. The value filled in is used only w hen the appropriate Set
Count to Value button is selected and is not otherw ise stored. Once a value is filled
in that value should remain usable until this screen is closed. Range 0 to 65535 (blank
equals 0)
2.6.4.2.12 Supervision Counts for area – shall list personnel by supervision type
(supervisor, supervised) and the count for each of how many are currently present in
the area.
2.6.4.2.13 M anual Actions for selected – shall contain buttons for manual actions
affecting count of selected supervision type. These buttons are disabled if no type is
selected.
2.6.4.2.14 Set Count to V alue – shall set this area’s personnel count of the selected
supervision type to the value set in the Count Value field.
2.6.4.2.15 Count V alue – shall be used by the M anual A ctions for selected
supervision type - Set Count to Value button. The value filled in is used only w hen
the appropriate Set Count to Value button is selected and is not otherw ise stored.
Once a value is filled in that value should remain usable until this screen is closed.
Range 0 to 65535 (blank equals 0).
2.6.5 Journal
Occupancy Restrictions shall report on access activity rejects reasons of:
• Reject no supervisor
Page 81
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.7.2 Definition
When a person w ho belongs to a carpool group accesses a carpool area door, w hile
carpool anti-passback is currently enabled for that area, the controller shall admit or
reject them based upon their carpool location and any carpool grace flags the controller
maintains. If admitted and not graced, and they open the door, all personnel in that
carpool group shall have their carpool location changed.
2.7.3.1.3 Carpool exit card can be different from the card that entered the area -
Indicates w hether a carpool exit card needs to be the same card that w as presented
w hen the area w as entered.
2.7.3.3.3 Timed pass-through –if selected, time defined here in hours and minutes
are applied to pass-through violation for this personnel group, not area-w ide pass-
through. If the value is 0, then no pass-through time w ill be enforced. M aximum
value is 999 hour 59 minute.
Page 82
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.7.3.4.3 Event to activate on passback violation during entry – The existing fill-
in box shall be used for carpool passback violation events. If the area is configured to
do personnel passback checking, then the event shall be activated as a personnel
passback violation. If the area is configured to do carpool passback checking, the
event shall be activated as a carpool passback violation.
2.7.4.3.2 Grace Carpool Group – Users shall be able to use this command button
to display a regular timed action dialog box allow ing users to select a start and end
time for the gracing of this carpool group.
2.7.4.4 Journal
A dmit and reject messages shall have an admit/ reject reason,
“ Group access” . Journal reject messages shall have a reject reason,
“ driver mismatch.”
Journal area activity messages shall report the follow ing message:
“ A rea name” : A rea pass-through is violated by “ person name.”
Page 83
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The user shall be able to exit and re-enter the lockout area as desired during the
lockout period (unless it’s one of the areas being locked), but every entrance or
exit extends the lockout time to the full period.
N ormal anti-passback testing may be performed on entry/ exit for the lockout
areas themselves, but anti-passback testing is not necessary for area lockout use.
When the lockout period has passed w ithout the user re-entering the initial area,
the user shall be able to enter any of the lockout areas.
The user shall be able to create multiple area lockout areas in the system, in a
cluster and in any particular controller. A n area group used for area lockout may
include areas in more than one controller as long as they are all in the same
cluster.
The system shall allow the ability to activate an event during an area lockout
violation. This event shall be configured in any area associated w ith area lockout
functionality. A ny cardholder system activity that produces an area lockout
violation shall be displayed in the activity log and monitor station as a lockout
violation.
A rea lockout rules can be enforced at any area w hether or not a cardholder is
admitted or rejected if configured to do so. A rejected card shall still represent the
cardholder being close enough to the area to prevent a cardholder from gaining
access to the area. Both access and denial of access shall be applied to area
lockout rules. A rea lockout for valid card rejection or admit unused is not
supported using apC panels.
Page 84
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.8.2 Definition
Page 85
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.8.5 Journal
The user shall be able to select ‘“ lockout” from a list of reject reasons that can be
used in access activity messages. The reject message shall show the time
remaining in the lockout as a variable in the message. There shall also be a journal
message for lockout grace, similar to the personal anti-passback grace journal
message.
The mode of the intrusion zone may be changed either from an event monitoring
w orkstation, or locally, w ithin the intrusion zone, by an authorized card holder.
Page 86
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 87
C•CURE 800/ 8000 Engineering Specifications V10.3.0
(d) Follow input state - the system shall allow for the arming of an intrusion
zone by input activation w here the status of the intrusion follow s the
state of the specified follow input. Used in connection w ith the “ Input
used to arm zone” field.
These doors w ill be locked/ unlocked according to the state of the intrusion zone.
These doors shall not be included in automatic door locking / unlocking
schedules.
Page 88
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.10.2 Configuration
The Intrusion Zone Configuration dialog box shall be accessed w hen the user
creates or edits an intrusion zone via the intrusion zone selection screen.
A fter a valid controller name has been entered it shall not be modifiable on the
configuration screens and shall become read-only. If the user w ishes to change
the controller of an existing intrusion zone, the intrusion zone must be deleted
and reconfigured w ith the new controller name.
Page 89
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The other general fields -- name, online checkbox, and description w ill have
standard behavior.
2.10.2.1 D isarming
2.10.2.1.1 Card M ethod used to disarm zone – selects from a list containing ‘N one’,
‘Valid Card Only’, and ‘A ctive Input and Valid Card’ to specify w hether the intrusion
zone may be disarmed by a method involving a card presentation. If the zone is only
to be disarmed by other methods including event activation via keypad command,
the user w ill select none.
2.10.2.1.2 Selecting ‘V alid Card Only’ means that w hen the zone is in secure mode
(armed) the first valid card access w ill disarm it.
2.10.2.1.3 I nput used with card to disarm zone – if ‘A ctive Input and Valid Card’
card method is selected, this field must be used to specify the input. This field is
disabled if that card method is not selected. This field is required to be filled in if that
method is selected. This is the unique name of an input on the same controller as the
intrusion zone. Double-clicking on this field w ill bring up the input select screen.
Standard object name verification is performed upon leave of field. Selecting ‘A ctive
Input and Valid Card’ means that the specified input must also be active for the card
access to disarm the zone
2.10.2.1.5 Personnel group – Enabled if the ‘w ith clearance and in personnel group’
radio button is selected. This is the unique name of a personnel group. Double-
clicking on this field shall bring up the personnel group select screen. Standard object
name verification is performed upon leave of field. N ote that each person record can
be in a maximum of four personnel groups.
2.10.2.1.6 Reader sounds during entrance delay of seconds – This shall be used
w hen the user must enter the zone area to disarm. This allow s input of the delay in
seconds betw een the time the zone area is entered to disarm and the time alarm
generation is reactivated. See the inputs tab screen to select w hich inputs shall trigger
the entrance delay and w hich shall be shunted during the delay. Integer, Valid
Range 0-999
2.10.2.1.7 Allow Zone disarm while violated – When checked, if the zone is
violated it can be changed to disarmed mode, and the mode change automatically
clears the violated state. If not checked, then the mode cannot be changed to
disarmed w hile the zone is in the violation state.
Page 90
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.10.2.2 Arming
2.10.2.2.1 Card M ethod used to arm zone – selects from a list containing ‘N one’,
‘Key-press and Valid Card’, and ‘A ctive Input and Valid Card’ to specify w hether the
intrusion zone may be armed by a method involving a card presentation. If the zone
is only to be armed by other methods, the user shall select none.
Selecting ‘Key-press and Valid Card’ means that the user must press the
CM D/ EN TER keypad key tw ice then present a valid card to arm the zone.
Selecting ‘A ctive Input and Valid Card’ means that the specified input must be active
for the card access to arm the zone.
2.10.2.2.2 I nput used with card to arm zone – if ‘A ctive Input and Valid Card’ card
method is selected, this field must be used to specify the input. This field is disabled
if that card method is not selected. This field is required to be filled in if that method
is selected. This is the unique name of an input on the same controller as the
intrusion zone. Double-clicking on this field w ill bring up the input select screen.
Standard object name verification is performed upon leave of field.
2.10.2.2.4 Personnel group – Enabled if the ‘w ith clearance and in personnel group’
radio button is selected. This is the unique name of a personnel group. Double-
clicking on this field shall bring up the personnel group select screen. Standard object
name verification is performed upon leave of field. N ote that each person record can
be in a maximum of four personnel groups.
2.10.2.2.5 Reader sounds during exit delay of (fill-in) seconds – This is used w hen
the user arms the zone w hile still w ithin the zone area. This allow s input of the delay
in seconds betw een the time the zone area arm command is issued and the time
alarm generation is reactivated . Integer, Valid Range 0-180.
2.10.2.2.7 Event to trigger if not armed – N ame of an event that the controller shall
activate if the zone is not in secure mode (armed) at the start of the time specification.
This field should be disabled if the arming check time specification is blank. Double-
clicking brings up the Event Select Window . Standard object name verification is
done on leave of the field.
2.10.2.3 D oors
2.10.2.3.1 Available D oors – Displays all doors on the controller that have at least
one access reader and are not currently controlled by an intrusion zone
Page 91
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.10.2.3.2 Selected D oors – Displays all doors controlled by the intrusion zone.
2.10.2.3.3 Edit D oors – A llow s the user to edit doors. When the user selects edit
doors, the system shall display the Doors Select Window.
2.10.2.3.4 Add – A llow s the user to add the selected door in the A vailable Doors
list to the selected list and remove it from the available list. Enabled w hile a door is
highlighted in the available list.
2.10.2.3.5 Remove – A llow s the user to remove the highlighted door in the Selected
Door list from the controlled list. Enabled w hile a door is highlighted in the Selected
Doors list.
2.10.2.3.6 Add All– A llow s the user to add all of the doors in the A vailable Doors
list to the controlled list. Empty the available list. Enabled w hile the available list is
not empty.
2.10.2.3.7 Remove All – A llow s the user to remove all of the doors in the Selected
Door list from the controlled list. Enabled w hile the controlled list is not empty.
2.10.2.3.8 D ouble Swipe – The SM S shall support the ability to designate doors at
w hich cardholders w ith double sw ipe event privileges may perform a manual
extended unlock function through the local card reader. Upon presentation of a valid
access credential to the reader, cardholders w ith double sw ipe privileges shall hear a
modified beep pattern and the door w ill unlock. These cardholders w ill now have the
option to proceed through the unlocked door or to activate the extended unlock
feature. Individuals w ishing to activate double sw ipe must present their credential to
the reader again before the expiration of the reader’s unlock time. Once activated, the
extended unlock condition triggered by the initiation of the double sw ipe feature
shall remain active until cancelled. Cardholders w ithout double sw ipe privileges
shall hear standard beep patterns and shall not have access to double sw ipe
functions.
1. Doors may be configured on an individual basis to tailor the use of the
double sw ipe feature. Double sw ipe permissions may be granted by
clearance, or may be further restricted to cardholders that have a valid
clearance and are assigned to a specific personnel group.
2. Cancellation of the double sw ipe extended unlock feature may be performed
either manually or automatically. M anual cancellation can be accomplished
by presenting a card w ith double sw ipe privileges to the active reader tw ice
in a row . The amount of time betw een card sw ipes for manual cancellation
may not exceed the time specified as a reader’s unlock time. A utomatic
cancellation of a double sw ipe extended unlock condition may be applied to
a single portal, or multiple portals through the definition and selection of
time specifications.
A ctivation of the double sw ipe extended unlock feature can be used to trigger events
such as operator notification, camera call-up, etc.
Page 92
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.10.2.4.1 Arm state – Selects the mode, ‘locked’, ‘unlocked’ or ‘secure’ that this
door should be set w hen this intrusion zone becomes armed.
2.10.2.4.2 D isarm state – Selects the mode, ‘locked’, ‘unlocked’ or ‘secure’ that this
door should be set w hen this intrusion zone becomes disarmed.
2.10.2.4.3 D irection – A llow s the user to toggle the ‘Direction’ flag for the
highlighted door in the Selected Door betw een in and out. If ‘in’ then this door leads
into the area of this intrusion zone, and it is assumed that the inbound reader on this
door is physically outside the zone area and the outbound readers on this door are
physically inside the zone area and vice-versa for ‘out’. The physical location of the
reader affects w hether card access arm/ disarm methods enable the door strike w hen
used.
2.10.2.4.4 Card Control – A llow s the user to toggle the ‘Card Control’ flag for the
highlighted door in the Selected Door from ‘yes’ to/ from ‘no’. If ‘yes’ then the
readers on this door may be used to arm or disarm the zone via card arm/ disarm
methods; if no, then these readers may not be used for this purpose.
2.10.2.4.5 D isplay – A llow s the user to toggle the ‘Display’ flag for the highlighted
door in the Selected Door from ‘blank’ to/ from ‘status’. If ‘blank’ then the LCD of the
readers on this door shall normally show time and date and the second line show n by
the door for normal access control. If ‘status’ then the LCD shall show time and date
w ith the second line show ing, in a cycle, the list of off-normal points in the zone, the
mode of the zone (armed or disarmed) and the state of the zone (off-normal, normal,
secure, violated).
2.10.2.5 I nputs
The follow ing are available inside the Intrusion Zone Configuration:
2.10.2.5.2 Selected I nputs – Displays all inputs controlled by the intrusion zone
(the controlled list).
2.10.2.5.3 Edit I nputs – A llow s the user to edit inputs. When the user selects edit
inputs, the system shall display the Inputs Select Window.
2.10.2.5.4 Add – A llow s the user to A dd the selected input in the A vailable Inputs
list to the selected list. Remove it from the available list. Enabled w hile an inputs is
highlighted in the available list.
2.10.2.5.5 Remove – A llow s the user to remove the highlighted input in the
Selected Inputs list from the controlled list. Enabled w hile an inputs is highlighted in
the Selected Inputs list.
2.10.2.5.6 Add All – A llow s the user to A dd all of the inputs in the A vailable
Inputs list to the controlled list. Empty the available list. Enabled w hile the available
list is not empty.
2.10.2.5.7 Remove All – A llow s the user to remove all of the inputs in the Selected
Inputs list from the controlled list. Enabled w hile the controlled list is not empty.
Page 93
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.10.2.6.2 Entrance delay shunt – A llow s the user to toggle the ‘Entrance Delay
Shunt’ flag for the highlighted input in the Selected Inputs list from ‘yes’ to/ from
‘no’. If ‘no’ then this activation of this input w hile the intrusion zone is secure
(armed) shall alw ays cause an immediate report and zone violation; if ‘yes’ then this
input shall be shunted during an entrance delay.
2.10.2.6.3 Protection I nput – A llow s the user to toggle the ‘Protection Input’ flag
for the highlighted input in the Selected Inputs list from ‘yes’ to/ from ‘no’. If ‘yes’
then this input shall be monitored by an intrusion zone w ithout being disarmed and
armed by the zone, making it a full-time monitored input. A ctivation of this input
w ill violate an armed intrusion zone.
2.10.2.7 Events
2.10.2.7.1 Event to activate while disarmed – N ame of an event (any system event)
that the controller shall activate w henever the zone changes to accessed (disarmed)
mode. Double-clicking brings up the Event Select Window . Standard object name
verification is done on leave of the field.
2.10.2.7.2 Event to activate while armed – N ame of an event (any system event)
that the controller shall activate w henever the zone changes to secure (armed) mode.
Double-clicking brings up the Event Select Window . Standard object name
verification is done on leave of the field.
2.10.2.7.3 Event to activate when not ready to arm – N ame of an event (any system
event) that the controller shall activate w henever the zone is not ready to be armed.
Double-clicking brings up the Event Select Window . Standard object name
verification is done on leave of the field.
2.10.2.7.4 Event to activate when zone violated– N ame of an event (any system
event) that the controller shall activate w henever the secured (armed) mode zone is
violated. Double-clicking brings up the Event Select Window . Standard object name
verification is done on leave of the field.
Page 94
C•CURE 800/ 8000 Engineering Specifications V10.3.0
• Display intrusion zone mode status on keypad’s reader (selects from configured
intrusion zones.)
Page 95
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.11.2 Configuration
• N ame - The unique name of the keypad command. Standard object name
verification is performed on leave of field.
Page 96
C•CURE 800/ 8000 Engineering Specifications V10.3.0
• “ Keypad Command causes event” – The user shall select the event that
shall be sent an activation request message w hen this keypad command is
issued. Users shall be able to double click on this field and brow se all of
the available configured events. Only events on iSTA Rs can be selected.
• “ Target Event causes H ome Cluster to be” - Displays the name of the
cluster that contains the panel the target Event resides on. Only doors in
this cluster can issue the command. This field is set by the selection of the
target Event and cannot be modified by the user.
• Priority – the priority of the activation sent to the event. Integer, Valid
Range 0-200.
• D oor group allowed to issue command – The user shall select a door
group. Doors in this group can issue this keypad command. Only doors in
the same cluster as the keypad command can activate the command.
Other doors in the group shall be ignored. N o validation w ill be
performed on the members of this group. If this field is empty, no doors
can issue this command (the command is effectively offline).
• Card validation required – If checked the RM shall ask for a card after the
command is entered. If checked the “ Limit permissions” radio set and the
“ PIN validation also required” checkbox shall also be enabled. Otherw ise
they w ill be dimmed.
Page 97
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.11.2.3 Reader
The reader keypad configuration screen shall have a radio button
set of options controlling the use of keypad commands at this
reader.
• Keypad command permissions – shall allow the selection of
w hether keypad commands are disallow ed by default at this
reader, allow ed by default, or allow ed during the specified
time specification.
• Keypad command time specification – this field shall be
enabled and required if the “ allow ed during time specification”
button is selected. Double-clicking brings up the time
specification selection w indow .
2.11.3 Privileges
• Administration privileges shall allow the control of keypad command and
keypad command report screens.
• D oor control privilege shall allow control of allow ing and disallow ing
keypad command manual actions: When a door is added to a monitor
privilege, tw o check boxes shall appear in the “ M anual actions for” box:
“ allow keypad commands” , “ disallow keypad commands” .
Page 98
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.11.4 M onitoring
The event status screen shall display “ A ctivate until override” for “ A ctivate
until override” actions in the “ A ction” column of the activation state cause list.
When an “ A ctivate until override” row is selected, the text of the “ Cancel
selected manual action…” button shall change to “ Cancel selected action…”
When the “ Cancel selected action…” button is pressed, the “ Overridable A ction
Detail” w indow shall be displayed:
The cause list shall show all the causes effecting keypad command allow ed
state. The panel shall keep track of these and report them to the host in activity
messages.
Each matrix sw itcher shall be configured, i.e. camera names, monitor names,
sequences, salvos, alarms and alarm actions, etc. utilizing the configuration
program and tools provided by the matrix manufacturer.
Page 99
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 100
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 101
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.12.3.4 On-line/Off-line
The system shall allow the operator to put a CCTV action on-line or
off-line. If the CCTV action is placed off-line, the system shall not
use the CCTV action in response to events and operators shall not
be able to manually activate the defined action.
2.12.4 Operation
2.12.4.3 Priority
CCTV actions shall become active or inactive according to the same
priority rules that apply to other objects under the control of the
Security M anagement Control System. A monitor related action
shall be sent to the monitor w henever it becomes the highest
priority action for that monitor. The system displays the CCTV
action based upon the assigned priority. The system shall not w ait
for operator interaction, other than clearing a higher priority alarm,
in order to activate the camera action.
2.12.4.4 Reports
The system shall allow the system administrator to generate reports
indicating configuration of the CCTV sw itcher, CCTV actions and
CCTV protocols.
Page 102
C•CURE 800/ 8000 Engineering Specifications V10.3.0
By use of the term embedded, it is the specifier's intention that the video imaging
system be completely encapsulated w ithin the Security M anagement Control
System. The video imaging subsystem shall share a common database w ith the
Security M anagement Control System, adding only the necessary data elements
such as stored image and assigned badge type. The user interface shall be
constructed to be similar in look and feel to the other modules of the Security
M anagement Control System.
The Server computer system may be the same server computer system utilized
by the Security M anagement Control System or a dedicated image server of
similar configuration.
The image view ing w orkstation shall be the same PC configuration utilized as the
client w orkstation in the Security M anagement Control System. N o additional
computer hardw are, i.e. video graphics cards, etc. shall be necessary in order to
retrieve and/ or view stored images.
In addition to the hardw are and softw are specified elsew here for the operator
w orkstations, the image capture w orkstation shall include an image
capture/ camera control board, camera, flash and imaging printer.
Page 103
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.13.2.2 Camera
The camera shall be an 1/ 3" inline transfer CCD color camera. The
camera shall connect to the image capture/ camera control board
through a single RS-232C connection. A ll camera control functions:
w hite balance, back-light, iris, brightness, hue, saturation, and
contrast shall be controlled through the operator w orkstation
keyboard. The camera shall be equipped w ith an auto-focus lens
w ith PC controlled zoom. The camera kit supplied w ith the Video
Imaging subsystem shall include the camera, professional grade
electronic flash w ith pow er supply, and camera stand.
Page 104
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Images shall be stored using a file naming scheme w hich links to the card holder
record. It should be readily apparent to someone w ith minimal know ledge of the
card holder record database to find the associated image in the directory w here
images are stored. This shall be used for importing and exporting of images for
use by the Security M anagement Control System and other systems needing
access to the store images.
JPEG is the preferred method of image compression and storage. When storing
images in JPEG format, the operator shall be able to set an image
quality/ compression threshold. The average image size using JPEG compression
shall be around 15KB per image.
Signatures captured w ith the Video Imaging subsystem shall be stored on the
centralized image server, allow ing all authorized operator w orkstations the
ability to retrieve and view the signatures. The image server shall have adequate
disk space to store signatures for the specified number of card holder records.
The image server shall be equipped w ith removable magnetic storage media for
backing up the stored signatures onto a single media unit, i.e. tape, Zip drive,
Jazz drive, etc.
Signatures shall be stored using a file naming scheme w hich links to the card
holder record. It should be readily apparent to someone w ith minimal
know ledge of the card holder record database to find the associated signature in
the directory w here signatures are stored. This shall be used for importing and
exporting of signatures for use by the Security M anagement Control System and
other systems needing access to the store signatures.
Page 105
C•CURE 800/ 8000 Engineering Specifications V10.3.0
JPEG is the preferred method of image compression and storage. When storing
signatures in JPEG format, the operator shall be able to set an image
quality/ compression threshold. The average image size using JPEG compression
shall be around 15KB per image.
The signature capture interface shall allow the operator to crop the signature,
removing excess w hite space. The operator shall also be allow ed to manipulate
the capture line thickness and scaling of the signature.
A t a minimum the badge design tool shall provide the follow ing feature:
(a) H orizontal or Vertical badge orientation
(b) Badge Rotation
(c) Layout grid, w ith user definable sizing, element alignment to grid and
snap to grid layout
(d) Layering of badge elements w ith M ove to Front and M ove to Back controls
(e) Proportional stretching
(f) Static Images
(g) Static Text
(h) Text controls -
• Font - any standard Window s text font
• Color - any standard Window s text color
• Format - standard Window s text formats, i.e. normal, bold, italic, bold
italic
• Size - standard Window s text sizes
• A utomatic Shrink-to-Fit w ithin defined text box
• Text justification, i.e. horizontal (left, center, right)
• Text alignment, i.e. vertical (top, center, bottom)
(i) Transparent or colored text background boxes
(j) Text angle and orientation
The badge design tool shall allow the operator to place a user defined
background image onto the card. This background image may be imported from
standard graphics formats, JPG, TIF, TGA , BM P. The operator can select w hether
the background image shall be printed onto the card, or displayed only, for use
w ith preprinted card stock.
The badge design tool shall be able to link to fields defined in the card record.
These fields and the associated data may be placed on the badge. The badge
design tool shall allow images and graphics to be placed onto the card,
correlating to data in the card holder record. For example a different logo
Page 106
C•CURE 800/ 8000 Engineering Specifications V10.3.0
depicting the department may be place the badge depending upon the
department name entered in the card holder record.
The system shall allow the system operator to place multiple objects, such as
stored photograph image, onto the identification badge. The system shall allow
the operator to vary the intensity of these objects as they displayed on the badge.
This shall allow a copy of the object to be placed onto the card in an intensity
similar to a w atermark.
2.13.7 Operation
A s previously stated, the imaging subsystem shall share a common database w ith
the Security M anagement Control System. In addition to producing an
identification badge, the Video Imaging subsystem shall capture and store an
image linking it to the personnel record maintained by the Security M anagement
Control System. The images shall be available for view ing by all authorized
Security M anagement Control System w orkstations.
Page 107
C•CURE 800/ 8000 Engineering Specifications V10.3.0
Page 108
C•CURE 800/ 8000 Engineering Specifications V10.3.0
command. The image display w indow size and location shall be set by
the system operator.
When the automatic image display is set, the operator shall be allow ed to
filter the images displayed to display the images on an access granted
event and/ or an access denied event. When images are automatically
displayed, the images shall remain on the operator's screen until the
image w indow is manually cleared by the system operator. The system
shall allow the operator to select w hether the latest image is displayed or
w hether all images are display in a cascading flow and each image
w indow manually closed by the system operator.
Each access event displayed on the operator w orkstation shall contain an
image recall icon. The operator shall be able to manually recall a card
holder's image by mouse clicking on the display image icon and choosing
the display image option. The system shall provide a different image
icon to indicate w hether or not an image of the card holder has been
captured and stored.
2.14.2 Configuration
Biometric Settings
Page 109
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.14.2.7 Setup
A dialogue box allow ing the user to verify the connection and to set
the baud rate for serial communication shall be available to the
user.
2.14.3 Capture/Verification
2.14.3.1 Enroll
Shall allow the user the ability to capture tw o individual
fingerprints. The Quality field shall show the percentage of the
captured fingerprint quality. The Content field shall show the
percentage of the captured fingerprint content.
2.14.3.2 V erify
A llow s the user to compare the captured fingerprint w ith the
presented fingerprint.
2.14.3.3 D elete
Shall allow the user to delete the captured fingerprint from the
biometric unit.
2.14.3.5 Accept
When selected the user is prompted to place their card into the
reader and the currently captured data is stored on the smart card.
Page 110
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.15.2 Configuration
2.15.2.3 Port
The system shall allow the user to specify the serial COM port used
to communicate w ith Security M anagement Control System.
2.15.2.5 D escription
The system shall allow the user to enter a description or additional
details regarding the device, 3000 characters max.
2.15.2.6 Online
The system shall serve the standard purpose of determining if the
device is to be ignored or not.
Page 111
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.15.3.1 N ame
The system shall allow the user to specify a unique name for the
Radionics device.
2.15.3.2 Receiver
The system shall allow the user to specify w hich device this
account belongs.
2.15.3.4 Online
The system shall serve the standard purpose of determining if the
Radionics account is to be ignored or not.
Page 112
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.16.2 Configuration
In the Security M anagement Control Systems administration screen, a new menu
item “ General Purpose Device” shall be added under the “ H ardw are” menu.
Under this menu, there shall be four new sub-menus “ General Purpose
Receiver” , “ M essage Protocol” , “ A ction Protocol” , and “ A ction.”
Receiver
2.16.2.1 N ame
The system shall allow the user to specify a unique name for a “ General
Purpose Receiver.” M aximum of fifty (50) characters.
2.16.2.3 Port
The system shall allow the user to specify serial COM port or N etw ork port
used to communicate w ith third party device.
2.16.2.4 V endor
The system shall allow the user to select a vendor type.
2.16.2.6 D escription
The system shall allow the user to enter a description or additional details
regarding this “ General Purpose Receiver.” M aximum 3000 characters.
2.16.2.7 Online
The system shall serve the standard purpose of determining if the “ General
Purpose Receiver” object is to be ignored or not.
Page 113
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.16.2.17 I nput
The system shall allow the user to configure an input in the “ General Purpose
Receiver.”
Page 114
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The system shall allow the user to specify a “ M essage Protocol” to trigger
the input to be activated.
The system shall allow the user to specify a “ M essage Protocol” to trigger
the input to be supervision error.
The system shall allow the user to specify a “ M essage Protocol” to trigger
the input to be supervision error restore.
2.16.3.1 N ame
The system shall allow the user to specify a unique name for a “ M essage
Protocol.” M aximum fifty (50) characters.
2.16.3.2 D escription
The system shall allow the user to enter a description or additional details
regarding the “ M essage Protocol.”
2.16.3.3 ASCI I H ex
The system shall allow the user to input key w ord in A SCII hex value format.
Otherw ise, user inputs key w ord in character format.
2.16.3.4 I nsert H ex
The system shall allow the user to select H ex value from a chart.
Page 115
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.16.3.7 Position
The system shall allow the user to enter a key w ord position. If this value is
greater than 0, the “ softw are device receiver” shall only search the key at this
position to map a message. If this value is 0, it means the key can be any
position in a message.
2.16.4.1 N ame
The system shall allow the user to specify a unique name for a “ General
Purpose Poll Command.” M aximum fifty (50) characters.
2.16.4.2 D escription
The system shall allow the user to enter a description or additional details
regarding this “ General Purpose Poll Command.” M aximum 3000 characters.
2.16.4.3 Protocol
The system shall allow the user to either fill in or double-click this field to
select the name of a pre-configured “ General Purpose A ction Protocol.”
2.16.4.4 Command
The system shall allow the user to select a command of the protocol specified
in the Protocol field.
2.16.5.1 N ame
The system shall allow the user to identify the protocol by entering a protocol
name in the N ame field.
2.16.5.2 Commands
The system shall allow the user to build a complete protocol command in the
“ construct action protocol commands” screen. This includes single-direction
protocol commands that merely send data to the General Purpose Receiver
device as w ell as more complex commands that require acknow ledgment.
2.16.6 Actions
2.16.6.1 N ame
The system shall allow the user to identify the action by entering an action
name in the N ame field.
Page 116
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.16.6.2 Protocol
The system shall allow the user to select an existing protocol from the list.
Once an A ction Protocol is selected, the user selects a command from the
‘Command’ drop-dow n list.
M onitoring Privileges are enforced on the monitoring station (object statuses and
M anual actions) and on the journal replay. This shall follow the standard method
of enforcing monitoring privileges as other objects in the system. Via this
privilege, users at the monitoring station shall see “ General Purpose Receiver”
journal messages.
2.16.9 M onitoring
The user shall be able to view the current state/ status of the device in the Guard
Station by looking in the “ Status/ A ction” menu for “ General Purpose Receiver.”
The user shall be able to view the current state/ status of the “ General Purpose
Input” in the “ Input” status screen.
2.17.2 Configuration
A ll server connections available to the monitoring station shall be
configured from the monitoring station via a new server connections
screen that shall be accessible through the monitoring station
“ Options” menu. For each server, the user shall specify:
a. N ame
The netw ork name of the server machine.
b. Port
Page 117
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.17.3 Login
The user shall enter a single username and passw ord to log on to the monitoring
station. This is similar to previous versions of the Security M anagement Control
System monitoring station. Each of the servers that the monitoring station w ill
connect to must have the same set of usernames and passw ords configured for
monitoring station access for all users w ho shall be performing central
monitoring functions.
When the user logs in to a monitoring station configured for central monitoring,
the activity log shall indicate the login status for each server that it w as logged
into. The activity log shall include only successful logins. If the user does not
successfully log into any server, then the user shall be re-prompted for another
username and passw ord. The Central M onitoring Station’s status line shall
display how many servers are connected to the Central M onitoring Station.
The Central M onitoring Station shall not display any indication of connection
retry attempts. A fter the Central M onitoring Station re-establishes a connection
w ith a server that w as retried, a login status line shall be displayed on the Central
M onitoring Station’s activity monitor display indicating either a login success or
login failure activity for that server. If the connection to a server is lost after the
user has already logged in to the server, attempts shall be made to re-establish
the connection.
2.17.4 Logout
When a user logs out of the central monitoring station, the CM S shall continue to
display activity from all connected monitoring stations. If the central monitoring
station looses connection w ith one or more servers that it w as logged in to and
then the user logs out, the central monitoring station shall continue to retry
connecting to these servers. If the central monitoring station w as unable to
connection and therefore w as unable to log in to one or more servers and then the
user logs out, the central monitoring station shall not continue to retry connecting
to these servers.
Page 118
C•CURE 800/ 8000 Engineering Specifications V10.3.0
station shall display a message box stating that the user is the last user
logging out of this server or servers.
2.17.7 Privileges
The System A dministrator shall configure M onitoring privileges and
Local by using the A dmin program. M onitoring privileges are
configured on a server-by-server basis. A user can have a different set
of monitoring privileges and local privileges for each server to w hich
they login.
2.17.9 Name
On any System, all object names are unique system-w ide. On a
monitoring station connected to multiple servers, it shall be possible
for the monitoring station to receive status messages on objects that
have the same name, but are different objects. This shall happen w hen
tw o objects on tw o different servers are configured w ith the same
name. It is strongly recommended that users establish an object
naming convention that avoids this sort of ambiguity.
Page 119
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.17.12 M aps
M aps shall be retrieved based on the map directory of the server on
w hich the map w as generated. A single map can contain icons from
only a single server. The map directory shall properly specify the
path, using the \ \ nodename\ sharename \ \ nodename\ sharename
UN C syntax. In order for M aps to be displayed on a Central
M onitoring station, that station must have M icrosoft Window s
netw ork access to all shared directories on local servers w here the
maps are actually stored.
2.17.14 Expiration
The monitoring station H elp A bout screen displays the SSA
expiration date. This may vary from one server to another. The
monitoring station shall display the SSA expiration information for
the first server to w hich it connects; the screen shall be modified to
display the name of the server for w hich it is show ing the SSA
expiration date.
Page 120
C•CURE 800/ 8000 Engineering Specifications V10.3.0
all connected servers shall use the primary server’s values. These
values are defined to reflect the monitor station event screen
privileges. A ll users must have monitor station privileges
established in the primary server. Failure to log on to the primary
server w ill produce a message notifying the user that all servers w ill
be disconnected from the Central M onitoring Station.
Routing by Time Of Day (RTOD) can be used in the C• CURE 800 configuration
in order to provide an automatic solution to adjusting guard privileges based on
the time of day, including in the more complex configuration of a Central
M onitoring Station (CM S) environment.
• A Last User Logout Event in the Options => System Variables…=> Personnel
tab.
• A Last User Logout checkbox in the Personnel => Edit Personnel Record =>
User tab.
The Security M anagement Control System application shall have a Last User
Logout Event in the A dministration program’s System Variables, Personnel tab
called Activate this event on last user logout. This new field allow s the System
Security A dministrator to specify a Last User Logout Event to trigger w hen the last
user logs out from a particular server.
Page 121
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The Security M anagement Control Systems personnel record shall include a Last
User Logout configurable checkbox. This User tab checkbox is called the Do not
trigger last user logout event checkbox.
When Do not trigger last user logout event is not checked for a user and that user
is the last user to logout from a Satellite site’s Guard Station that user’s logout
shall trigger the “ Activate this event on last user logout” event.
When Do not trigger last user logout event is checked for a user and that user is
the last user to logout from a Satellite site’s Guard Station, that user’s logout shall
not trigger the “ Activate this event on last user logout” event.
2.18.4 Reports
Routing by Time Of Day shall include the follow ing reports:
• Users Report shall include these fields added to the Users Tab.
2.19.2 Configuration
When the Guard Tour menu option is selected, the standard Select screen shall be
displayed w ith a list of Guard Tours that are currently configured. The Select
screen shall allow users to create a new Guard Tour by pressing the New button,
edit an existing Guard Tour by selecting the Guard Tour from the list of Guard
Tours and pressing the Edit button, delete an existing Guard Tour by selecting
the Guard Tour from the list control and pressing the Delete button, and edit a
default Guard Tour record by pressing the Edit Default button.
2.19.2.1 N ame
The system shall allow the user to specify a unique name for a Guard Tour.
Standard object name verification is performed on leave of field.
2.19.2.2 D escription
The system shall allow the user to enter a description or additional details
regarding this Guard Tour.
2.19.2.3 Online
This shall be used as a mechanism to control w hen changes in tour
configuration can be made. The online checkbox shall serve the standard
purpose of determining if the Guard Tour object is to be ignored or not. While
the Online checkbox is unchecked (tour is offline), users shall be able to make
changes to this tour’s configuration. A ll fields shall appear enabled, and
Page 122
C•CURE 800/ 8000 Engineering Specifications V10.3.0
available for configuration. While the Online checkbox is checked, user shall
not be able to change this tour’s configurations.
Page 123
C•CURE 800/ 8000 Engineering Specifications V10.3.0
tour, all tour stops must be visited (even if out of sequence) before the Guard
Tour can be completed unless the Guard Tour is canceled.
The system shall allow a new Tour Stop to be configured for any given
Guard Tour. Once configured, the tour stop shall be added to the end of
the Tour Stops brow ser and shall be configured as the last tour stop in this
Guard Tour.
The system shall allow the user to edit an existing tour stop by
highlighting its entry in the Tour Stop brow ser and either double-clicking
on it, or pressing this button. In either case, the Tour Stop Configuration
screen shall be displayed w ith the information about this tour stop.
The system shall allow the user to remove a Tour Stop from the Guard
Tour. If there is no tour stop selected in the brow ser, then the Delete
button shall be disabled.
When pressed, the selected tour stop in the Tour Stop brow ser shall be
moved up in list and its Stop # updated. If the selected tour stop is the
first item in the list or if no item is selected, then the M ove Up button
shall be disabled.
When pressed, the selected tour stop in the Tour Stop brow ser shall be
moved dow n in the list and its Stop # updated. If the selected tour stop
is the last item in the list or if no item is selected, then the M ove Dow n
button shall be disabled.
Page 124
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.19.2.10.7 Reader
Reader at stop#1 initiates Guard Tour (checkbox) – shall allow the user to
configure this reader as able to start a Guard Tour. This field becomes
enabled only if Tour Stop #1 has been configured and is monitored by a
reader.
The system shall allow the user to activate an event if tour stops are
completed out of Sequence. This field lets users define an event that
pulses w hen a tour stop is taken out of the defined order. The field shall
only be enabled and configurable for Sequential- type tours.
The system shall allow the user to specify the maximum time a guard should
take betw een any tw o random tour stops before a Guard Tour error occurs.
This field shall be disabled if the Sequence option is selected. The M ax Time
Between Random Stops fill-in shall be displayed in the time format, HH:M M .
M inimum value: 1 minute. M aximum value: 20 hours. If the value is 00:00,
then no maximum time shall be enforced. If M inimum time is greater than 0,
then M aximum time must be greater than M inimum time entered.
2.19.2.11.1 N ame
The system shall allow the user to provide a unique name for the tour
stop being configured. Tour stops shall be treated as security
items/ objects in the system; even if dependent on the Guard Tour it is
assigned to.
2.19.2.11.2 D escription
The system shall allow the user to enter a description or additional
details regarding for this tour stop.
Page 125
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The system shall allow the user to enter in the name of an input to be
used as the tour stop device. A user may enter the name of an input or
double-click on the fill-in field and select it from a list of configured
inputs on the system via the standard Select screen. Inputs configured as
tour stops shall be set as “ Guard Tour” type in the Input Configuration
screen by the system. They shall also be set as disarmed and online in the
Input configuration screen (shall appear as read-only). Once the tour is
started, the system shall automatically arm these inputs.
A n input may be part of multiple tour stops w ithin the same tour.
H ow ever it cannot be assigned to multiple Guard Tours. Tw o
concurrently running Guard Tours having the same input w ould cause a
conflict w hen determining for w hich tour the tour stop w as made.
2.19.3 Personnel
The Security M anagement Control System shall contain a Guard Tour checkbox
in General folder tab. This shall indicate w hether or not this person is allow ed to
perform Guard Tours. If the checkbox is checked, then this person can be
selected to perform a Guard Tour. This information shall be used as a filter to
preselect only Guard Tours personnel from all personnel records, and list only
these as selection criteria for journal replay of Guard Tour message, and at the
M onitoring station for Guard Tour manual actions.
• Guard Tour configuration report – A fixed report w hich lists all Guard
Tour configured in the system.
• Guard Tour and Tour Stop configuration report – A fixed report w hich
lists all Tour Stops configured for each of the Guard Tours in the system.
2.19.5 Journal
The journal replay shall include a Guard Tour selection item from the security
items screen. This shall allow users to filter on Guard Tour N ame, Person, and
Time frame. Standard journal report selection capabilities shall be available. This
shall allow the follow ing type of Guard Tour reports to be available via Journal
Replay:
Page 126
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The system shall the user to chose from three Guard Tour journal messages:
2.19.6 Privileges
There shall be A dministration privileges enforced on the Guard Tour
configuration screen. This shall follow the same standard method of enforcing
administrative privileges as other objects in the system.
M onitoring Privileges are enforced on the monitoring station (object statuses and
M anual actions) and on the journal replay. This shall follow the same standard
method of enforcing monitoring privileges as other objects in the system. Via this
privilege, users at the monitoring station shall be able to issue a Guard Tour
action such as to start, cancel, resume, and suspend a Guard Tour.
On monitoring privilege screen, there shall be radio buttons for the follow ing
actions: (1) Start tour, (2) Resume tour, (3) Suspend tour, (4) Cancel tour.
When a user starts a tour from the monitoring station, only guards configured as
allow ed to perform Guard Tours can be selected for w alking a tour.
2.19.7 M onitoring
The system shall include tw o items under Status/Actions menu for Guard Tours:
(1) Configured Guard Tours and (2) Active Guard Tours. The corresponding Guard
Tour Selection screen shall be displayed depending on the menu item selected.
N ew icons for Guard Tour object shall be included in the system. These shall
include Guard Tour in Progress, Guard Tour in progress w ith errors, Suspended,
and Canceled.
Page 127
C•CURE 800/ 8000 Engineering Specifications V10.3.0
“ Start Guard Tour” action, its priority shall be set via a user-selectable value in
the "Select Guard for Guard Tour" screen. For all other Guard Tour actions,
the user's “ M aximum priority,” as defined in the user’s M onitoring Privilege
shall be enforced. In other w ords, a user shall not be able to cancel, resume, or
suspend a Guard Tour that w as started w ith a priority higher than their
maximum priority.
When the Start button is pressed, a new Select Guard dialog shall be displayed.
This dialog shall show the user a list of guards allow ed to w alk a Guard Tour.
This dialog shall have a Start button, w hich shall be enabled after a guard
from the list has been selected. Only guards not currently w alking other tours
shall be displayed in the list. This dialog shall also have a Priority fill-in field,
w here users can select the priority that this Guard Tour action should be
assigned.
When the Start button is pressed, the Guard Tour shall begin. This dialog box
shall also have a Cancel button, to exit w ithout selecting a guard, and cancel
the Start Tour manual action.
For guards that are allow ed to start a tour, their cards should not be marked
as: Lost or Disabled or Expired (based on Expiration Date stored in Personnel
record). This shall generate a “ Cancel on error” message for the Guard Tour,
and a cancellation of the active Guard Tour in the system. The only card
sw ipe error condition that can qualify as a valid tour stop is “ Reject for
Clearance.”
Show tour details for selected tour allow s users to get Guard Tour status details
and its tour stops’ progress. This shall only be enabled for In
Progress/Suspended tours in the list because only these tours shall contain active
tour stop details.
List of configured tours allow s users to get a listing of all Guard Tours currently
configured and online in the system. (Same as Configured Guard Tour
Selection Screen.
Page 128
C•CURE 800/ 8000 Engineering Specifications V10.3.0
• The system shall allow the user to cancel the selected Guard Tour.
• The system shall allow the user to suspend the selected Guard
Tour. Button is only enabled for In Progress tours in the list.
For field changes at the Guard Tour level, audit trail messages shall be as
follow s: Guard Tour “ Guard Tour name” changed. For field changes at the tour
stop level, the audit trail messages shall be as follow s: Guard Tour Stop “ Tour
stop name” changed.
2.20.2 Description
The user shall be able to configure all objects required to support the DVRS
feature in the systems administration application. These include DVRS servers,
cameras and actions, and the M ap function shall be modified in order to support
the addition of DVRS Cameras to the M ap layout. The DVRS feature shall
provide a Journal replay function so that a user shall have the ability to view
recorded video segments that have been associated w ith an A ccess and Control
event.
2.20.3 Configuration
A DVRS menu item shall appear in the hardw are drop-dow n menu. When the
DVRS menu item is selected, another drop-dow n shall be presented w hich shall
contain Server, Camera, A ction Video Tour and Video View . When any menu
item is selected, the standard Select screen shall be opened to allow a user to
create, modify or delete the selected item.
Page 129
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.20.3.1 Server
When the Server item is selected, the standard Select screen shall be
displayed w ith a list of Servers that are currently configured. The
Select screen shall allow user to configure a new Server by pressing
the New button, edit an existing Server by selecting the Server from
the list of Servers and pressing the Edit button, delete an existing
Server by selecting the Server from the list and pressing the Delete
button, and edit a default Server record by pressing the Edit Default
button.
2.20.3.2 N ame
A llow s user to specify a unique name for the Server. 32 characters.
2.20.3.7 D escription
The system shall allow the user to enter a description or additional
details regarding this Server. 255 characters.
2.20.3.8 Online
This shall serve the standard purpose of determining if the Server
object is to be ignored or not (by Driver and M onitoring Station
applications).
While the Online checkbox is unchecked (DVRS Server is offline),
users shall be able to make changes to this Server’s configuration.
A ll fields w ill appear enabled, and available for configuration.
While the Online checkbox is checked, users shall not be able to
change this Server’s configurations. A ll fields/ buttons shall be
read-only, except for OK/ Cancel buttons and Online checkbox.
By default, every hour the current time at the CCURE800 Driver
w ill be sent to the DVRS Server (after the appropriate time offset
Page 130
C•CURE 800/ 8000 Engineering Specifications V10.3.0
has been determined based on the time zone of the DVRS Server) in
order to synchronize system clocks.
Page 131
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.20.3.18 Alarms
N etVue A larm M anagement shall allow users to associate C●CURE
800 events w ith video alarms and alarm groups to A rm and Disarm
N etVue alarms. When activated, events shall either disarm the
associated alarms, suppressing all journaling and M onitoring
Station notifications or re-arm the associated alarms. The video
alarms and alarm groups shall also support manual arming (the
default setting) and disarming.
Pressing this button shall display a standard object selection screen
for all alarms.
2.20.3.19 N ame
A llow s a user to specify a unique name for a ‘N etVue Server
A larm’. 50 characters.
2.20.3.20 Online
This shall serve the standard purpose of determining if the A larm
object is to be ignored or not (by Driver and M onitoring Station
applications).
2.20.3.21 D escription
A llow s the user to enter a description or additional details
regarding this ‘A larm’. 3000 characters.
2.20.3.22 Events
A llow s the user to specify an event to be activated if the associated alarm
notification is received from the DVM S.
2.20.3.24 Camera
When the Camera item is selected, the standard Select screen shall be
displayed w ith a list of cameras that are currently configured. The Select
screen shall allow users to configure a new camera by pressing the New
button, edit an existing Camera by selecting the Camera from the list of
Cameras and pressing the Edit button, delete an existing Camera by selecting
the Camera from the list and pressing the Delete button, and edit a default
DVRS Camera record by pressing the Edit Default button.
2.20.3.25 AD /PTZ
When selected the Server number and name and camera number from the
Camera Configuration Screen shall be displayed in the upper entry portion of
the screen. The w indow at the bottom of the screen shall list all previously
defined A D/ PTZ configuration entries.
Page 132
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The user shall define the port by selecting either TCP/ IP or COM .
The user shall define the A D Sw itcher protocol by selecting either M ake-Break
protocol (A D168) or 15H Z protocol (A D1024).
The user shall configure the Port N ame (the Port N ame w ill be grayed and not
available if the port type is TCP/ IP), Port A ddress (the Port A ddress w ill be
grayed and not available if the port type is COM ), Intellex server IP address
and Intellex Camera N umber. The A D/ PTZ# shall be listed in the w indow to
indicate w hich entry has been added.
2.20.3.27 D V RS Server
The system shall allow the user to specify the location of the camera. Users
shall be able to double click on this field and access all of the available
configured DVRS Servers. Selectable only, up to 32 characters.
a) Dome (selected):
The user shall see the A D/ PTZ’ button highlighted w hen a DOM E camera on
an Intellex Server is selected.
2.20.3.29 Presets
Camera objects shall support the inclusion of camera-based presets.
These presets are activated by user selection in the M onitoring
Station.
2.20.3.29.1 N etV ue Preset I ndex – This list control gets populated w ith all the
possible camera-based presets available in the Live Video Window (LVW).
2.20.3.29.2 Bi-directional Actions – This list control is populated w ith the current
list of Bi-directional actions. During actual operation, the selected action entry shall
trigger if the LVW user selects the associated preset button.
2.20.3.29.3 N ame – A llow s the user to specify a unique name for a ‘N etVue Server
A larm’. This name shall appear in the M onitoring Station w hen the user hovers the
mouse over the button. Up to 50 characters.
Page 133
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.20.3.29.5 V alid N ames for Preset I ndex – Provides the user w ith a list of valid
presets available for that camera.
2.20.3.31 Alarms
Pressing this button shall display a standard object selection screen
for all alarms.
2.20.3.31.1 N ame – A llow s the user to specify a unique name for a ‘N etVue Camera
A larm’. 50 characters.
2.20.3.31.3 Events – A llow s the user to specify event to be activated if the associated
alarm notification is received from the DVM S.
2.20.3.31.4 N etV ue Alarm I ndex – This list gets populated w ith all the possible
camera based alarms generated by the DVM S.
2.20.3.31.5 List of Alarm names – Shall list all alarms available w ithin this camera
for the user to choose from.
2.20.3.34 Online
This shall serve the standard purpose of determining if the Camera object is to
be ignored or not (by Driver and M onitoring Station applications).
Page 134
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.20.3.35 D escription
This shall allow the user to enter a description or additional details regarding
this Camera. 255 characters.
2.20.3.36 Action
The user shall be able to define a DVRS A ction. These DVRS actions are
treated as ‘momentary actions’ in the system. When the A ction item is
selected, the standard Select screen shall be displayed w ith a list of A ctions
that are currently configured. The Select screen shall allow users to configure
a new A ction by pressing the New button, edit an existing A ction by selecting
the A ction from the list of DVRS A ction and pressing the Edit button, delete an
existing A ction by selecting the DVRS A ction from the list and pressing the
Delete button, and edit a default DVRS A ction record by pressing the Edit
Default button.
2.20.3.38 Camera
The system shall allow the user to select a camera from the configured DVRS
cameras. 32 characters.
2.20.3.39 D V RS Server
Displays the DVRS Server that the selected Camera is associated w ith. filled in
after Camera selection is made. Display only. 32 characters.
2.20.3.41 D escription
The system shall allow the user to enter a detailed description about the DVRS
A ction. 255 characters.
Page 135
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The DVR action shall alw ays be annunciated at the M onitoring Station and
shall alw ays be listed in the Journal Replay. The disabling of the annunciation
is not an option.
Video
Protocol API DVR/NVR
Qualified By In Vendor
Software House Documentation
2.20.4 Events
DVRS action shall be added to the A ction drop-dow n list in the Event
Configuration. The user shall be able select the DVRS A ction in order to associate
the DVRS A ction to the A ccess Control Event.
Page 136
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.20.6 Journal
The journal replay shall include a DVRS A ctions selection item from the Select
M essage Types screen. This shall allow users to filter DVRS A ctions.
If the user selects the ‘export to avi’ button in order to save video segment on the
hard drive, the user w ould then be prompted to enter the location and file name
to store the segment.
2.20.8 Reports
The user shall be able to run the follow ing reports; DVRS Server Configuration,
DVRS Camera Configuration., DVRS A ction Configuration.
2.20.9 Privileges
There shall be A dministration privileges enforced for all DVRS functions. These
shall follow the same standard method of enforcing administrative privileges as
Page 137
C•CURE 800/ 8000 Engineering Specifications V10.3.0
other objects in the system. The DVRS feature is a system option that is available
throughout the licensing mechanisms. A ll DVRS icons and selections shall be
grayed and disabled if the appropriate DVRS license is not available on the
system.
A ny A ccess control events at the monitoring station, w hich have been defined to
have an associated video event, shall be listed in the General A ctivity M onitor
scrolling w indow . The user shall be able to playback video w hich has been
associated w ith an event.
The monitoring station shall also provide an option to toggle the Live Video
Window (LVW) display betw een standard and large sizes. Standard means the
size of the original N etVue Player.
N etVue shall provide a single-click function w ithin the Recorded Video Window
(RVW) to launch a LVW of the same camera and server type.
2.20.10.2 M enu/Toolbar
A menu item, “ Live DVRS,” shall be available to the user in the Status/ A ction
menu. A Live DVRS icon shall be available to the user from the General A ctivity
M onitor toolbar.
When the user selects DVRS Camera Selection, by clicking on the icon, the
standard Select screen shall be opened to allow a user to select a Camera. The
user may also Cancel the action as w ell by clicking on the Close button.
A DVRS camera icon shall be available from the General A ctivity M onitor
toolbar. Once the camera Selection dialog is displayed, the user shall have the
option of displaying live video, or displaying a previously recorded video
segment. In order to play live video, the user shall make the camera selection by
clicking on the appropriate camera name in the drop dow n list and then clicking
the “ Display Live Video” button. Live video for 1 to 4 cameras (configured on
the same DVRS Server) can be displayed at one time.
In order to play recorded video, the user shall make the camera selection by
clicking on the appropriate camera name in the drop dow n list, selecting the
Page 138
C•CURE 800/ 8000 Engineering Specifications V10.3.0
appropriate starting and ending dates and times, and then clicking the “ Display
Recorded Video” button.
The user shall be able to initiate an immediate manual record event by clicking on
the record button, from the live player. When Record button is selected, a
manual record event shall be activated w hich shall include a video segment,
w hich begins 10 seconds before the Record button w as pressed and terminates 10
seconds after the Record button, w as pressed. A manual record event shall occur
for each camera displayed in the current player. The event shall be journaled and
displayed as a manual event on the Guard Station Event w indow . The user shall
play the manually recorded video segment by selecting the video event from the
event w indow .
The user shall be able to launch the Intellex “ N etw ork Client” application from
the monitoring station tool bar.
Checking the automatic player display in the monitoring station means that the
N etVue Player shall automatically display if an associated ‘Display Live Video’
action is triggered by the security system. This Player represents an additional
player beyond the four-player limit indicated elsew here in this document.
V ideo Tour
A Video Tour icon shall be available from the General A ctivity M onitor toolbar.
A list of video cameras to be view ed in sequence for a user defined dw ell time in
a Live Video Window (LVW). When running a Tour, the user shall be able to
manually pause it to take manual control of the selected camera. Once the user is
finished w ith the manual control of the camera, they shall be able to restart the
Tour in either direction.
V ideo V iew
Page 139
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.20.10.4 M aps
M ap creation shall be performed in the A dministration A pplication. In the
M onitoring Station A pplication, the user can display configured maps by first
selecting the appropriate icon from the General A ctivity M onitor toolbar and
then selecting the desired map from the list of configured maps.
Once the user has displayed a map, the DVRS icon (camera or dome) shall
display any configured camera N ame at cursor proximity. The User shall have
the ability to launch live video from video icons placed on a map by left
clicking over the DVRS camera icon. Current camera states w ill be indicated by
the use of colored camera icons. The DVRS icon shall be presented in red if the
camera is in communications failure, green if the camera is currently recording
and yellow if the camera is monitoring and grey if the cameras is in standby
mode or idle.
2.21.2 Configuration
Escorted A ccess shall be configured using the A dministration Client. The user
shall use the personnel record editing screen to designate Visitor, Escorted Visitor,
or Escort.
Page 140
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.21.3 M onitoring
Escorted A ccess A ctivity messages shall be visible on the Guard Station either as
soon as a reject decision is made or w hen an admission is reported. M any visitors
admission/ rejection could be visible at once.
For the regular visitor type employee (not requiring escorts) the title shall be
[visitor]; this w ill be show n in both admit and reject reports.
For the escorted visitor type employee the title shall be [escorted visitor] and
this shall be follow ed by “ by <name>” w here <name> is the name of the
escort. N o escort name shall be show n if the escorted visitor is denied, or if
the area the escorted visitor is entering does not require an escort.
For escort type employees, the title [escorting] shall be show n only if the
employee is escorting someone during this access cycle. On an access cycle
w here the escort type employee is not escorting anyone, no special title shall
be show n.
Page 141
C•CURE 800/ 8000 Engineering Specifications V10.3.0
2.22.2 Configuration
The user shall be able to configure an area(s) for mustering/ de-mustering in the
area screen in the administration application.
2.22.3 M onitoring
2.22.3.1.1 D e-M uster Area - The user shall be able to select an area to de-muster.
When the button is pressed, personnel w ho are in the area selected shall have their
area set to the de-mustering area.
2.22.3.1.2 D e-M uster All Personnel – The user shall be able to set the location for
personnel in all mustering areas to the designated de-mustering area.
Page 142
C•CURE 800/ 8000 Engineering Specifications V10.3.0
The access control system shall have the ability to be configured w ith up to 6
threat levels. The follow ing features shall be included in the configuration of each
defined threat level:
3. Enable or disable color codes that are applied to maps and monitor station
displays
2.25 I ncident I D
2.25.1 General
The system shall provide an option to use Incident IDs. The ID can be associated
w ith event state change and event activity messages to track and report the
history of events.
Page 143
C•CURE 800/ 8000 Engineering Specifications V10.3.0
acknow ledgement, the incident w ill end w hen the event is deactivated,
acknow ledged and cleared.
When an event incident ends, the incident ID shall still be available under the
event status screen on the M onitoring Station. A dditional messages can be
assigned to this incident as long as the associated event does not become
activated w ith a new cause.
This shall apply to all three types of activation: activated, momentarily activated
and latching. During the activation period of an event, any other activity
messages related to this event w ill be assigned the same Incident ID. The
follow ing activity messages related to this event w ill be assigned to the same
Incident ID: event acknow ledgements, event clears, event acknow ledgement
overdue, event reset, event log messages, event re-activations and event
deactivations.
Image Capture Date Field – allow s the import of actual date or can be configured
to use the import time as the capture date. C• CURE Central image manager
requires the use of the import image capture date field.
• A llow s you to install, remove, modify and repair the SM CS silently (w ith no
user interface) or by using a graphical user interface.
• Can be accessed from any remote location for w hich client machines have
access permissions.
Page 144
C•CURE 800/ 8000 Engineering Specifications V10.3.0
3. Execution
3.1.2 I nstallation
A ll low voltage w iring outside the control console, cabinets, boxes, and similar
enclosures, shall be plenum rated w here required by code. Cable shall not be
pulled into conduits or placed in racew ays, compartments, outlet boxes, junction
boxes, or similar fittings w ith other building w iring.
Page 145
C•CURE 800/ 8000 Engineering Specifications V10.3.0
3.2 Training
3.2.1 General
The contractor shall conduct training courses for personnel designated by the
ow ner. Training shall cover the maintenance and operation of the SM CS. The
training shall be oriented to the specific system being installed under this contract
including central processor. Training manuals shall be delivered for each trainee
w ith tw o additional copies delivered for archiving at the project site. The
manuals shall include an agenda, defined objectives for each lesson, and a
detailed description of the subject matter for each lesson. The contractor shall
furnish audiovisual equipment and other training materials and supplies as
necessary. Where the contractor presents portions of the course by audiovisual
material, copies of the audiovisual material shall be delivered to the ow ner on the
same media as that used during the training session. Up to ____ hours of training
shall be provided for in the base contract.
3.3 Testing
3.3.1 General
The contractor shall perform pre-delivery testing, site testing, and adjustment of
the completed SM CS. The contractor shall provide all personnel, equipment,
instrumentation, and supplies necessary to perform all testing. Written
notification of planned testing shall be given to the ow ner at least fourteen (14)
days prior to the test, and in no case shall notice be given until after the
contractor has received w ritten approval of the specific test procedures. Test
procedures shall explain in detail, step-by-step actions and expected results
demonstrating compliance w ith the requirements of the specification. Test
reports shall be used to document results of the tests. Reports shall be delivered
to the ow ner w ithin seven (7) days after completion of each test.
Page 146
C•CURE 800/ 8000 Engineering Specifications V10.3.0
3.4.4 Personnel
Service personnel shall be qualified to accomplish all w ork promptly and
satisfactorily. Provide proof that Service personnel have successfully completed
the appropriate level of both hardw are and softw are training offered by the
system manufacturer. The ow ner shall be advised in w riting of the name of the
designated service representative and of any change in personnel.
3.4.5 I nspections
The contractor shall perform tw o inspections at six (6) month intervals or more
often if required by the manufacturers. This w ork shall be performed during
regular w orking hours, M onday through Friday, excluding Federal holidays.
These inspections shall include:
• Visual checks and operational tests of the central processor, local
processors, monitors, keyboards, system printers, peripheral equipment,
SM CS equipment, pow er supplies, and electrical and mechanical controls.
• Clean system equipment, including interior and exterior surfaces.
• Perform diagnostics on all equipment.
• Check and calibrate each SM CS device.
• Run system softw are and correct diagnosed problems.
• Resolve previous outstanding problems.
3.4.7 Software
The contractor shall provide free softw are updates for five (5) years and verify
operation in the system as required. These updates shall be accomplished in a
timely manner, fully coordinated w ith the SM CS operators, and shall be
incorporated into the operations and maintenance manuals and softw are
documentation.
Page 147
C•CURE 800/ 8000 Engineering Specifications V10.3.0
5. Automated Backup
This service creates a backup of the configuration database and the journal at user defined
intervals in such a w ay that a new backup is stored as a new file and does not overw rite any
previous backups. The DiagSystem utility shall display an additional section of the CCURE.IN I
file called A utoBackup. The user shall be able to set the values for the backup log location,
frequency, and time keys.
Page 148