Dufferin-Peel Catholic District School Board
STANDARD TEXT GUIDELINE FOR
Security Systems – Card Access
for
SECONDARY AND ELEMENTARY SCHOOLS
Prepared by the Plant Department
With assistance from Vision Dynamics
Formatted by the Design Department
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROPRIETARY AND REMAINS THE PROPERTY OF
THE DUFFERIN-PEEL CATHOLIC DISTRICT SCHOOL BOARD. THIS DOCUMENT MAY NOT BE USED IN ANY
WAY, OTHER THAN AS AUTHORIZED BY THE DESIGN DEPARTMENT OF THE DUFFERIN-PEEL CATHOLIC
DISTRICT SCHOOL BOARD.
BY RECEIPT OF THIS DOCUMENT, THE RECIPIENT ACKNOWLEDGES AND
AGREES TO THIS CONDITION.
TABLE OF CONTENTS
SECURITY
SYSTEMS
Card Access
II.)
SECURITY
SYSTEMS
GUIDELINE
Card Access
1
CARD ACCESS SYSTEM............................................................................................................................... 1
1.1
2
3
4
PREAMBLE................................................................................................................................................ 1
GENERAL REQUIREMENTS ......................................................................................................................... 1
2.1
STANDARDS ............................................................................................................................................. 1
2.2
EXPERIENCE ............................................................................................................................................ 2
2.3
INSTALLATION.......................................................................................................................................... 2
2.4
SUPPORT SERVICES............................................................................................................................... 2
GENERAL DESCRIPTION.............................................................................................................................. 2
3.1
SYSTEM FUNCTIONS............................................................................................................................... 2
3.2
USER INTERFACE .................................................................................................................................... 3
3.3
SYSTEM ARCHITECTURE ....................................................................................................................... 4
FUNCTIONAL REQUIREMENTS ................................................................................................................... 5
4.1
PERSONNEL ACCESS CONTROL FUNCTIONS..................................................................................... 5
4.2
ALARM MONITORING FUNCTIONS......................................................................................................... 6
4.3
CONTROL OF READERS ......................................................................................................................... 7
4.4
EVENT MIDED CONTROL OF OUTPUT DEVICES.................................................................................. 8
4.5
SCHEDULED CONTROL OF READER CONTROLLED DOORS............................................................. 8
4.6
INHIBITING ALARMS ................................................................................................................................ 8
4.7
DATABASE STORAGE AND VERIFICATION........................................................................................... 8
4.8
COMMUNICATION FAILURES.................................................................................................................. 9
4.9
ALARM DISPLAY AND PROCESSING ..................................................................................................... 9
4.10 SYSTEM STATUS ..................................................................................................................................... 9
4.11 PRINTOUT OF SYSTEM ACTIVITY ........................................................................................................ 10
4.12 RECORDING AND RETRIEVING SYSTEM ACTIVITY FOR AUDIT....................................................... 10
4.13 INHIBIT PRINTING OR DISPLAYING OF CARD TRANSACTIONS ....................................................... 10
I.)
GUIDELINE
SECURITY
SYSTEMS
Card Access
4.14 PASSKEY PROTECTION OF COMMANDS ............................................................................................10
4.15 HELP SCREENS AND ONLINE OPERATOR AIDS.................................................................................11
4.16 TIME SCHEDULE AND HOLIDAYS .........................................................................................................11
4.17 DATABASE MAINTENANCE AND PRINTOUT........................................................................................11
4.18 AUTOMATIC SYSTEM STARTUP ...........................................................................................................11
5
6
7
8
EQUIPMENT ..................................................................................................................................................11
5.1
DOOR CONTROL UNITS.........................................................................................................................11
5.2
ELEVATOR CONTROL UNITS.................................................................................................................12
5.3
READERS.................................................................................................................................................13
5.4
CARDS......................................................................................................................................................13
5.5
COMPUTERS AND PERIPERALS...........................................................................................................14
GENERAL CONTRACT TERMS AND CONDITIONS...................................................................................14
6.1
MAINTENANCE AND REPAIR AGREEMENTS.......................................................................................14
6.2
GUARANTEE............................................................................................................................................15
6.3
APPROVALS ............................................................................................................................................15
6.4
DOCUMENTATION AND TRAINING........................................................................................................15
6.5
DRAWINGS ..............................................................................................................................................15
6.6
MISCELLANEOUS HARDWARE..............................................................................................................16
6.7
SUPERVISION..........................................................................................................................................16
6.8
COMMISSIONING OF THE SYSTEM ......................................................................................................16
INSTRUCTIONS TO BIDDERS .....................................................................................................................16
7.1
VENDOR QUALIFICATIONS....................................................................................................................16
7.2
RESPONSE TO SPECIFICATION............................................................................................................17
7.3
DESCRIPTION OF PROPOSED EQUIPMENT........................................................................................17
PHOTO BADGING & VERIFICATION...........................................................................................................17
8.1
II.)
SYSTEM FUNCTIONS AND FEATURES.................................................................................................17
SECURITY
SYSTEMS
GUIDELINE
Card Access
9
TYPICAL TENDER FORMAT FOR ACCESS CONTROL SYSTEM ............................................................ 18
10
TENDER REQUIREMENTS .......................................................................................................................... 18
10.2 WARRANTY/GUARANTEE INFORMATION ........................................................................................... 19
10.3 INSTALLATION........................................................................................................................................ 19
11
SYSTEM REQUIREMENTS .......................................................................................................................... 19
12
PROPOSAL EVALUATION CRITERIA ........................................................................................................ 20
13
APPLICABLE TAXES................................................................................................................................... 20
14
WORKER’S COMPENSATION..................................................................................................................... 20
15
BOARD’S RIGHT TO TERMINATE THE CONTRACT................................................................................. 20
16
CONSTRUCTION SAFETY ACT .................................................................................................................. 21
17
ASSIGNMENT OF CONTRACT.................................................................................................................... 21
18
LIENS AND DAMAGES ................................................................................................................................ 21
19
CONTRACTOR ON SITE.............................................................................................................................. 22
20
PROTECTION AND MAKING GOOD........................................................................................................... 22
III.)
SECURITY
SYSTEMS
GUIDELINE
Card Access
1
CARD ACCESS SYSTEM
1.1
PREAMBLE
1.1.1
The intent of this document is to provide a typical Guideline that will be used
for all JK-OAC educational and administrative facilities requiring a Card
Access System. This guideline provides the minimum performance criteria
for the components and sub-systems comprising a complete Card Access
System that shall accommodate The Dufferin-Peel Catholic District School
Board (the Board) current security system requirements.
1.1.2
It is edited for information and for the purposes of co-ordination between the
Electrical Sub-contractor under the General Contract Documents and the
Card Access Systems sub-contractor(s).
1.1.3
The Card Access System will be designed by a Board appointed Security
Systems Consultant. This Consultant shall fill in the appropriate blanks as
identified in shaded areas thus: XXX.
1.1.4
The card System shall be installed by a separate contractor, separately
tendered by the Board but paid directly by the Board from the General
Contract Allowance for Security Systems.
1.1.5
The Architect’s Consultants, in concert with the Board’s security personnel,
will indicate on the drawings which access points are to receive card
accesses and the Electrical Consultant shall indicate locations of required
power outlets.
1.1.6
The General Contractor shall provide 120 V power to the point of installation
of each system component required AC power.
2
GENERAL REQUIREMENTS
2.1
STANDARDS
2.1.1
Product specifications, general design considerations, and installation
guidelines are provided in this written document. Quantities of outlets, typical
installation details, and outlet types for the specific educational facility, or
facilities, are to be provided by the Card Access Consultant. If the bid
documents are in conflict, the written specification, based on this Guideline,
shall take precedence. The successful Vendor shall meet or exceed all
requirements of the system described in this Guideline.
2.1.2
All system components shall conform to the following standards where
appropriate:
2.1.2.1
UL STD 294:
Access Control
PAGE 1 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
2.2
2.1.2.2
CSA STD C22.2:
Bonding & Grounding of Electrical Equipment
2.1.2.3
CSA STD C22.2:
Signal Equipment
2.1.2.4
EMI emissions:
FCC Part 15
EXPERIENCE
2.2.1
All system components shall be manufactured by reliable firms with a least 15
years experience in the development and manufacture of access control and
point monitoring products.
2.2.2
The system shall be non-proprietary and or non exclusive to any installing
dealer. All components must be available through a minimum of 4 full service
security dealers located within the designated area.
2.3
INSTALLATION
2.3.1
The supplier shall supply and install all system components covered by this
specification, including all wiring for communications, monitoring and alarm
output, (if applicable).
2.3.2
The supplier shall provide one complete set of documentation covering
installation, operation and maintenance of all system components.
2.3.3
On-site training for a maximum of XX operators for XX days shall be provided
as a precondition to acceptance, if applicable.
2.3.4
The General Contractor shall provide 120 V power to the point of installation
of each system component required AC power.
2.4
SUPPORT SERVICES
2.4.1
3
The supplier shall be capable of providing on-going training and services for
all system components.
GENERAL DESCRIPTION
3.1
3.1.1
SYSTEM FUNCTIONS
The system shall integrate the following functions into a simple to use
package as described below;
3.1.1.1
Control of personnel access
3.1.1.2
Monitoring of detectors
3.1.1.3
Manual/automatic control and monitoring of doors
3.1.1.4
Reporting/auditing
3.1.1.5
Elevator control and access to floors
PAGE 2 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
3.1.2
3.2
The system software shall automatically identify all field devices and permit
the Board operator to customize each device’s configuration.
USER INTERFACE
3.2.1
Keyscan System VII software. It shall support a minimum of two primary
screens: one for event processing and direct programming of each ACU and
a second for administrative functions such as report generation and database
management. The main menu will have six (6) quick access hot buttons to
access ADD/DEL Cardholders, Time zones, Door Group Access,
Unlock/Lock Doors, Transaction Reports & Elevator Groups.
3.2.2
The operator shall be able to access either screen in an easy to manage
format.
3.2.3
The user interface shall be a windowed environment, capable of operating on
all platforms listed:
Windows™ Operating Systems 2000 Professional
XP Professional
Vista Business (32 bit)
complete with pull down menus suitable for operation on a personal computer
system with the following specifications:
3.2.4
3.2.3.1
Windows™ Operating Systems 2000 Professional (32 bit) Server
2003, XP Professional, Vista Business (32 bit)
3.2.3.2
Pentium D (or greater) processor 2.0 GHZ or higher
3.2.3.3
Minimum1 GB of Ram
3.2.3.4
Minimum 20 Gig hard drive
3.2.3.5
PS2 mouse
3.2.3.6
Colour SVGA monitor, capable of 1024 x 768 resolution
3.2.3.7
Dedicated Com Port 1 or 2 (Local site)
3.2.3.8
Local and remote site com port 1 and 2
3.2.3.9
Certain optional software features may require higher operating
specifications for optimum performance (Photo Badging and time
attendance modules)
USB Port
3.2.4.1
Internet Explorer 6 or higher installed, available service packs and
operating system patches installed.
3.2.4.2
Video card capable of 1024 x 768 resolution
PAGE 3 OF 22
GUIDELINE
SECURITY
SYSTEMS
Card Access
3.3
SYSTEM ARCHITECTURE
3.3.1
The system shall be based on independent intelligent devices which are
interconnected and communicating on a multi-drop communications network
(Both Star and Bus configurations must be supported) to an IBM PC or 100%
hardware and software compatible personal computer.
3.3.2
Event processing, system data entry, system management functions and
auditing of system activity shall be performed at the personal computer
connected to the network.
3.3.3
The system database information shall be distributed among the field devices
as well as stored in the personal computer.
3.3.4
The system shall be structured to provide a growth path from stand-alone
field devices to a completely integrated network that supports the capacities
and features specified within this document without necessitating exchanging
installed field devices.
3.3.5
A minimum 256 reader controlled portals shall be supported by the system.
3.3.6
The system shall be modular in design so that the failure of one device shall
have minimum effect on the functionality of another.
3.3.7
The system shall provide for user friendly on-line context sensitive help
instructions.
3.3.8
The system shall provide a user-definable database scrolling text window for
facility management purposes. This window shall provide the user with the
ability to enter, and modify at any time, site-specific information to be used in
managing the facility.
3.3.9
Support for a second user-definable window to be used for entering and
retrieving instructions pertaining to an emergency situation shall also be
provided. This information shall be accessible via function key.
3.3.10 The system shall have the capacity for a minimum of eight thousand (8,000)
cardholders complete with names stored in the access control units: or
16,000 cardholder numbers with the names, in this case names stored in
database.
3.3.11 The system shall record all field activity including event name/type, card ID,
cardholder name, location, time and date. This shall be in addition to all other
monitoring previously described.
3.3.12 To aid in simplifying the installation, it shall be possible to connect the
computer at any ACU on the communications network.
3.3.13 The system shall support dial-up modems, LAN/WAN connectivity and allow
for programming and monitoring of remote field systems.
PAGE 4 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
4
FUNCTIONAL REQUIREMENTS
4.1
PERSONNEL ACCESS CONTROL FUNCTIONS
4.1.1
Access into a controlled area shall be through reader controlled portals
(doors) using a token (card) in a sensing device (reader).
4.1.2
An access control unit (ACU) shall be used to control the reader(s) installed
at the door(s).
4.1.3
At least one token shall be supplied for each individual requiring access
through the controlled doors. Any person supplied with a token shall be
called a cardholder.
4.1.4
The system shall be capable of supporting all of the following token
technologies:
4.1.4.1
Proximity
4.1.4.2
Wiegand effect
4.1.4.3
Magnetic stripe
4.1.4.4
Personal Identification Number only (PIN)
4.1.4.5
Dallas Touch memory Disk
4.1.5
Each token shall be internally encoded with a Keyscan 36 Bit Wiegand
unique number. The system shall provide a central programming station to
enter these numbers into a database for transmission to each field device.
4.1.6
The sensing device (reader) shall be capable of reading the internal number
encoded in each token presented and passing this information to the ACU.
4.1.7
The ACU shall process this information and unlock the appropriate controlled
door only if the token is determined to be valid for access through that door.
4.1.8
For higher security, an additional facility shall be available for entry of a
Personal Identification Number (PIN) code on a number pad associated with
the reader. No additional Reader Port is required.
4.1.9
PIN code must be calculated from the encoded card number. All PIN codes
shall be changeable with a 5 digit key number controlling algorithm process.
4.1.10 Systems utilizing PIN codes which are derived by manipulating the encoded
numbers shall not be accepted.
4.1.11 Systems which require manual definition, entry and storage of the PIN codes
associated with the card number shall not be accepted
4.1.12 An access request at a reader shall be determined based on the following
conditions:
4.1.12.1 Is the card valid on this day of the week?
4.1.12.2 Is the card valid at this time of the day?
PAGE 5 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
4.1.12.3 Is today a holiday? If yes, is this card valid on this holiday?
4.1.12.4 Does the Personal Identification Number match with the card
sensed?
4.1.12.5 Is the card valid for this site?
4.1.12.6 Is the card valid for this door?
4.1.13 Should any of the above conditions not be met, access will not be granted.
This shall result in an “Invalid Access” event being audited and recorded.
4.1.14 Doors shall be unlocked for authorized personnel in less than one second
from entry requested regardless of all other system activity.
4.1.15 The time duration for which the door shall be unlocked shall be user definable
in one (1) second increments over the full range of 1-99 seconds.
4.1.16 Each ACU shall provide a dedicated request to exit input for each door (i.e.
an exit button) in order to prevent forced entry alarms for personnel wishing
to exit through the door. This facility shall be used to request egress from the
secure side of the door. Should a request to exit be made, the ACU shall
respond in the same manner as for access granted for a token.
4.1.17 If required, the ACU shall automatically re-lock the controlled portal whenever
the door is sensed as opened and closed regardless of the duration of the
momentary unlock period, or upon expiration of the unlock period, whichever
shall occur first. (Door contacts are not currently installed at card access
locations.
Installation of door contacts is requires for the specified
functionality.)
4.1.18 Each field device ACU shall have a capacity for at least eight thousand
(8,000) cards, c/w 16 character names or sixteen thousand (16,000) cards,
number only, depending upon the option selected for the location. This
capacity shall not be diminished by displacement from other memory storage,
e.g. event logging.
4.2
ALARM MONITORING FUNCTIONS
4.2.1
If required, each ACU shall be able to monitor the position of any properly
installed doors at all times. (I.e. door open or closed). The amount of time
that a door may remain open shall be a user definable variable. In order to
accommodate a high volume of traffic through controlled doors, the system
shall allow successive tokens to be read without requiring door closure
between reads.
4.2.2
If required, the system shall provide forced entry detection at user specified
door locations.
4.2.3
If required, a forced entry event shall be generated immediately whenever the
door is opened without authorization. Authorization shall be determined by
card or request to exit transaction at the door or by command from the host
system as described.
PAGE 6 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
4.2.4
It shall be possible to select specific events and locations that shall be printed
on hard copy without affecting card capacity.
4.2.5
Regardless of the event selections made, the computer shall record the
transaction in an audit trail on hard disk storage media such that it can be
later retrieved for audit reporting.
4.2.6
An “anti-pass-back” feature shall be available to prevent multiple use of a
card at the same door.
4.2.7
The system shall feature, in addition to the door position monitor for each
door, the provision to monitor a minimum of one thousand twenty four (1024)
supervised input points or detection zones. The system shall be capable of
detecting state changes between four distinct conditions for each of these
points:
4.2.7.1
Alarm
4.2.7.2
Secure
4.2.7.3
Trouble due to open circuit wiring
4.2.7.4
Trouble due to short circuit wiring
4.2.8
When an event is detected at any of these, the computer shall be notified and
shall generate a message stating the nature of the alarm, the location and the
time. The computer shall record the alarm such that it can be later retrieved
for an audit report.
4.2.9
It shall be possible to determine for the following specific conditions whether
the event shall be printed, displayed, both or neither.
4.2.10 The system shall support alarm maps with each input being identified on a
map alarm conditions/locations will be highlighted by a flashing icon.
4.3
CONTROL OF READERS
4.3.1
The system shall be able to manually control doors and readers from the
computer keyboard as detailed below. Doors and readers shall have plain
language descriptors of up to fifteen (15) characters.
4.3.2
The following door control commands shall be supported, at a minimum:
4.3.2.1
Unlock the door and leave it unlocked
4.3.2.2
Unlock the door momentarily such that it automatically locks after
the normal unlock interval
4.3.2.3
Lock the door
4.3.2.4
Unlock or lock all doors
4.3.3
The system shall be capable of allowing door selection for manual control by
means of drop-down lists for doors, or ACU’s.
4.3.4
The system shall also be able to control card and PIN processing as follows:
PAGE 7 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
4.4
4.3.4.1
Change the operation of number pads equipped reader such that it
requires entry of a PIN code in addition to a token.
4.3.4.2
Restore the number pad equipped reader to card only operation.
4.3.4.3
Time zone controlled number pad and reader modes.
EVENT MIDED CONTROL OF OUTPUT DEVICES
4.4.1
The ACU shall feature a means of actuating an alarm output for each door.
4.4.2
The conditions for each alarm output shall be user definable to include any
one or more of the following:
4.4.3
4.5
4.5.1
4.6
4.4.2.1
Access denied at a door for any reason.
4.4.2.2
Door position monitor detects illegal use of the door (such as door
held open too long or forced open).
4.4.2.3
An alarm event occurs at one or more of the auxiliary alarm points.
If the ACU cabinet is tampered with, an alarm output for each ACU shall
always be actuated.
SCHEDULED CONTROL OF READER CONTROLLED DOORS
The system shall provide a feature that will allow readers to be controlled on
a scheduled basis. Scheduled commands supported shall be the same as
those supported for manual keyboard commands from the computer (see
section 2.3). These schedules shall be user definable.
INHIBITING ALARMS
4.6.1
The system shall provide an alarm inhibit feature whereby changes of state
from alarm to secure or from secure to alarm for individual alarm points are
not printed, recorded or displayed by the computer. When this feature has
been invoked, trouble conditions shall continue to be reported. This feature
shall be available as both a manual keyboard command from the computer
and as a scheduled inhibit. When scheduled, the “inhibit” shall automatically
be applied to and removed from the alarm point at the scheduled times. The
schedules used for this feature are user definable on a weekly basis.
4.6.2
The system shall support the ability to completely disable an alarm point such
that no changes to or from any state shall be printed, recorded, or displayed
by the computer.
4.7
4.7.1
DATABASE STORAGE AND VERIFICATION
System information shall be stored in a database. Appropriate database
information required for full functioning of each reader shall be distributed to
reside in the non-volatile memory of the field devices. Systems-wide
PAGE 8 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
database information shall also be stored on a hard drive within the host
computer.
4.7.2
4.8
The system shall be able to ascertain if the field device or ACU has been
exchanged. Database verification checks shall be performed to ensure that
all devices operate according to the most current information. The system
shall provide the capability to perform database updates on demand.
COMMUNICATION FAILURES
4.8.1
In the event of a computer failure, all field devices installed on the system
shall remain fully functional.
4.8.2
Each field device shall be capable of retaining in memory at minimum the last
three thousand (3,000) events that occurred during the off line mode. When
communication with the computer is restored, these stored transactions shall
be transmitted to the computer for the appropriate treatment. (i. e. printout
and/or recording and/or display)
4.9
ALARM DISPLAY AND PROCESSING
4.9.1
System occurrences that are exception to the conditions shall be enunciated
as an alarm at the computer.
4.9.2
It shall be possible to assign a user definable fifteen (15) character name
from any reader or input point in order to distinguish its location to the
operator.
4.9.3
The operator shall be advised that an alarm is waiting to be processed. The
system shall display the event in a window or by audible tone waiting to be
processed at all times. Such window shall come to the foreground on any
window software program currently running, when the access control
program is running in the background.
4.9.4
Event information shall be presented on the display screen by operator
command via a dedicated function key. When the function key is pressed, an
event processing window shall open to display the event list. The user shall
be able to select from this list for viewing and acknowledging. Information
shown shall include time of occurrence, type of occurrence, and the user
defined description of the location of the initiating device.
4.9.5
When an operator “Acknowledges” an event, it shall be removed from the
screen.
4.9.6
The system shall allow the operator to examine information for all alarms
currently awaiting processing one at a time without acknowledging them.
4.10 SYSTEM STATUS
4.10.1 It shall be possible for an operator to review the current system status on a
list that shall include all current system status and exception conditions.
PAGE 9 OF 22
GUIDELINE
SECURITY
SYSTEMS
Card Access
4.11 PRINTOUT OF SYSTEM ACTIVITY
4.11.1 All messages directed to the printer shall be fully formatted complete with
headers, page number and information in clear text format. They shall also
contain the time and date of the event, name and location descriptors.
4.11.2 The system shall be capable (where the appropriate computer configuration
allows) of monitoring printer status. The operator shall be advised whenever
the printer becomes no longer available.
4.12 RECORDING AND RETRIEVING SYSTEM ACTIVITY FOR AUDIT
4.12.1 The system’s audit storage capacity shall be limited only by the hard disk
capacity. Each audit file shall provide for storage of a minimum of fifty
thousand (50,000) events on hard disk storage for recording all system
activity.
4.12.2 The storage shall be modular such that when an event file becomes full, that
file can be saved, or copied onto floppy disk and stored separately from the
computer while system events continue to be recorded in the next file without
interruption.
4.12.3 The system shall provide a means to obtain structured audit reports to be
generated from either the online storage facility or from portions of the events
record which have previously been removed onto floppy disk.
4.13 INHIBIT PRINTING OR DISPLAYING OF CARD TRANSACTIONS
4.13.1 The system shall allow printout and display of card access granted
transactions to be inhibited on a reader by reader and time zone basis.
4.14 PASSKEY PROTECTION OF COMMANDS
4.14.1 All commands are passkey protected. Each operator must log on to access
the workstation. The system shall confirm the validity of the passkey for that
operator before allowing access.
4.14.2 It shall be possible to give each operator individualized access for browsing,
changing, adding, editing and deleting database information, as well as to
interrogate and command field devices.
4.14.3 The system shall support at least fifty (50) passwords. Passwords shall not
be displayed or printed by the system at any time during usage. It shall be
possible for the system supervisor to enter, change, or modify passkeys at
any time.
4.14.4 The workstation screen shall time out after a preset number of seconds, in
case the operator must leave his station. In this event, a valid passkey must
be entered to access the workstation.
4.14.5 The
system shall provide a means of enabling/disabling password
processing. This shall include restrictions on access to protected commands.
PAGE 10 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
4.15 HELP SCREENS AND ONLINE OPERATOR AIDS
4.15.1 The system shall provide help information for various commands that require
operator input, in order to minimize the need to refer to manuals.
4.15.2 The system shall provide the operator with on-screen guidance on the type of
information to be entered.
4.16 TIME SCHEDULE AND HOLIDAYS
4.16.1 The system shall provide a minimum of two-hundred and fifty six (256) time
zones and five-hundred and twelve (512) user definable time schedules per
ACU for access control, alarm and output control inhibits etc. Each schedule
shall contain one start and stop time per day for a seven (7) day week, &
three (3) holiday types.
4.16.2 All time zones will have the ability to have First Person In (FPI) configuration.
4.16.3 The system shall support a minimum of 64 (64) dates that shall be used to
invoke holiday processing complete with date, type definition & holiday type.
4.16.4 Holiday processing shall automatically become effective when the system
clock matches any of the dates defined as Holidays. Personnel access shall
be determined by the authorizations given to each cardholder for each type of
holiday in their assigned time schedule.
4.17 DATABASE MAINTENANCE AND PRINTOUT
4.17.1 It shall be possible to specify the contents of database and/or activity reports
based upon selected criteria such as name, department, and access level.
4.17.2 It shall be possible to specify contents of database and/or activity reports
based on selection of any, or up to ten, (10) optional user defined fields.
4.17.3 Data printouts shall be fully formatted with clear text headings. Where space
requirements prohibit the use of full textual headings, a key explaining
abbreviated headings shall be included in the printout.
4.18 AUTOMATIC SYSTEM STARTUP
4.18.1 It shall be possible to provide automatic start-up such that no operator action
shall be required to start the system up after a power off condition.
5
EQUIPMENT
5.1
5.1.1
DOOR CONTROL UNITS
The system shall support a variety of intelligent door controllers. These shall
include the following packages:
5.1.1.1
Keyscan CA 200 2 reader/Door Access Control Unit
PAGE 11 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
5.1.1.2
Keyscan CA 4000 4 Reader/Door Access Control Unit
5.1.1.3
Keyscan CA 8000 8 Reader/Door Access Control Unit
5.1.2
Each of the controllers supplied shall meet the characteristics detailed in the
Guideline for the door controllers.
5.1.3
It shall be possible for an operator, if authorized to do so, to issue commands
to any of the reader controlled portals to cause the mode of operation to
change. These commands shall include the following functions:
5.1.4
5.2
5.2.1
5.1.3.1
Add a cardholder
5.1.3.2
Delete cardholder
5.1.3.3
Assign/change time zones
5.1.3.4
Print activity file
5.1.3.5
Change card processing mode to require a card and/or PIN before
an access request shall be processed
5.1.3.6
Unlock door momentarily
5.1.3.7
Unlock door until command is rescinded
5.1.3.8
Re-lock previously unlocked door
5.1.3.9
Reset anti-pass back conditions
For additional operational details refer to the detailed guide specifications for
the appropriate door controller.
ELEVATOR CONTROL UNITS
The system shall support a variety of intelligent elevator controllers. These
shall include at least the following packages:
Keyscan EC1000 Single Reader – Single cab elevator c/w control of
40 floors of elevator access
5.2.1.1
AND/OR
5.2.2
5.2.1.2
Keyscan EC2000 Dual reader dual cab elevators c/w control of 16
floors per elevator cab
5.2.1.3
Each of the controllers supplied shall meet the characteristics
detailed in the Guideline for the elevator controllers.
It shall be possible for an operator, if authorized to do so, to issue commands
to any of the reader controlled portals to cause the mode of operation to
change. These commands shall include the following functions:
5.2.2.1
Add a cardholder
5.2.2.2
Delete cardholder
PAGE 12 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
5.2.3
5.3
5.3.1
5.2.2.3
Assign/change time zones
5.2.2.4
Print activity file
5.2.2.5
Change card processing mode to require a card and/or PIN before
an access request shall be processed
5.2.2.6
Unlock floor momentarily
5.2.2.7
Unlock floor until command is rescinded
5.2.2.8
Re-lock previously unlocked floor
For additional operational details, refer to the detailed guide specifications for
the appropriate door controller.
READERS
The readers used for access control shall be available in the following types
and technologies:
5.3.1.1
Proximity readers with or without number pad, suitable for surface or
“concealed” mounting behind a wall or glass
5.3.1.2
Card insertion style Wiegand Effect readers, with or without number
pad, suitable for flush or door frame mounting.
5.3.1.3
Card swipe through style Wiegand Effect readers, with or without
number pad., suitable for surface or door frame mounting.
5.3.1.4
Insertion or swipe magnetic stripe readers, with or without number
pad suitable for flush or door frame mounting.
5.3.1.5
Key pad only reader suitable for flush or surface mounting
5.3.1.6
Dallas touch memory disk, with or without number pad, suitable for
flush or door frame mounting.
5.3.2
Readers shall be equipped with visual indication for access granted and door
unlocked.
5.3.3
The ACU shall be capable of receiving data transmitted from readers installed
up to five hundred (500) cable feet away, without additional signal conversion
equipment; or up to four thousand (4000) cable feet away, using additional
signal conversion equipment, supplied by the same equipment manufacturer.
5.4
5.4.1
CARDS
Cards shall be available in one or more of the following styles and
technologies:
5.4.1.1
Proximity credit card size and shape, Keyscan 36 bit format
5.4.1.2
Proximity key tag style
5.4.1.3
Wiegand Effect credit card size and shape, Keyscan 36 bit format
5.4.1.4
Magnetic stripe credit card size and shape
PAGE 13 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
5.4.1.5
Dallas touch memory disk
5.4.2
Each card shall bear a number hot stamped or printed number on its surface.
5.4.3
It shall be possible to laminate a user-supplied photo ID onto the surface of
the credit-card sized card.
5.4.4
The PIN number associated with each card shall not be obtainable by direct
manipulation of the internal encoded number.
5.4.5
Each card, in addition to the randomly encoded number specified above,
shall also contain a “facility” or “batch” code hot stamped or printed on its
surface. It shall be possible for the system to utilize this facility code in either
of two methods: general or site specific. When site specific processing is
enabled, this facility code shall be checked by the ACU and access will be
denied to any card that does not belong to this project.
5.4.6
The system shall be capable of accepting up to 255 different facility codes
simultaneously.
5.4.7
Cards that require predefined “issue levels” shall not be acceptable.
5.5
COMPUTERS AND PERIPERALS
5.5.1
6
The system shall be minimum Pentium D 2.0 Ghz equipped, running on
Windows™ Operating Systems 2000 Professional, Server 2003 XP
Professional (32 bit) or Vista Business (32 bit). It shall have minimum 1 GB
of RAM, and 20 Gig Hard Drive. At least one USB port and DVDR/W drive
shall be present for installation and back-up purposes. The PC shall not have
to be a dedicated PC. It shall be able to reside on end-users existing
network.
GENERAL CONTRACT TERMS AND CONDITIONS
6.1
MAINTENANCE AND REPAIR AGREEMENTS
6.1.1
If awarded the contract, the Supplier/Installer agrees to enter into an ongoing
agreement with the Board for the maintenance and repair of the system
equipment. The cost of maintenance for a period of XX months after system
installation shall be included in the tender price.
6.1.2
Requirements for maintenance schedules, documentation and tasks will be
listed in an attached addendum.
6.1.3
If awarded the contract, the Vendor agrees that he will arrange from his
supplier all software licenses as required by the supplier. The Vendor also
agrees that he will purchase appropriate software maintenance agreements
for full support and maintenance of all system software as available from the
supplier. The price of all software licenses and maintenance agreements
shall be included in the tender.
PAGE 14 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
6.1.4
Where the Vendor plans to sub-contract any portion of the maintenance
contract, the shall indicate the items affected and the names of the subcontractors.
6.1.5
The Vendor shall specify the number and location of trained service
personnel available to support the system.
6.2
GUARANTEE
6.2.1
The Vendor shall warrant all equipment furnished to be new, undamaged,
free from defects and in conformity with the requirements specified within this
document.
6.2.2
The Vendor’s obligation shall include removal, repair or replacement,
transportation, re-installation and testing, without charge to the Purchaser, for
all or any parts of the system found to be defective due to faulty materials or
workmanship for a period of XX months after system installation.
6.3
APPROVALS
6.3.1
All equipment supplied shall be approved for the purpose intended by the
authority having jurisdiction. Installation shall be in accordance with all
standards and practices dictated by this authority.
6.3.2
Installation, testing and commissioning shall be done by individuals fully
qualified to perform such work.
6.4
DOCUMENTATION AND TRAINING
6.4.1
Complete documentation shall be provided which covers all aspects of the
system operation. Excerpts from each available document shall be submitted
with the tender as proof of its current existence and acceptability.
6.4.2
Documentation which covers the following topics shall be provided at a
minimum:
6.4.3
6.5
6.5.1
6.4.2.1
An easy to use operation guide for non-technical and security staff
6.4.2.2
All planning assistance forms shall be provided, including a system
planning guide for collecting and preparing data.
The Vendor shall provide at least XX days of formal, hands-on training, using
the purchased and installed system. This training shall cover all aspects of
system operation, management, and troubleshooting. The cost of this
training shall be included in the tender price.
DRAWINGS
The Vendor shall furnish such shop drawings and diagrams as are
reasonably required to clarify the details of work included in this tender.
PAGE 15 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
6.5.2
6.6
At the conclusion of the project, the Vendor shall provide one (1) set of “as
built” drawings which indicate for example, the location of all supplied
equipment in the system, all electrical box locations and cable identification
as installed under the terms and conditions of the final contract.
MISCELLANEOUS HARDWARE
6.6.1
6.7
Any miscellaneous hardware items, such as connectors, cable plugs,
mounting brackets, not specified in this document but which are required to
make up a fully operational system shall be provided by the Vendor as part of
his tender.
SUPERVISION
6.7.1
6.8
The vendor shall be responsible for the following project supervision
functions:
6.7.1.1
Supervision of sub-trades (as required)
6.7.1.2
Attendance at site meetings (as required)
6.7.1.3
Attendance at project planning meetings
6.7.1.4
Co-ordinating his work with the Architect, Consulting Engineer,
General Contractor and others
COMMISSIONING OF THE SYSTEM
6.8.1
The Vendor shall be responsible for verifying that each component of the
system is fully operational and in conformity with the requirements specified
within this document. The Vendor shall also be responsible for ensuring that
all elements function together as a system.
6.8.2
Commissioning shall be done in a phased manner as the installation for
ACU’s proceeds. It shall not be necessary for the computer to be installed
and operational in order for commissioning of the system to begin. ACU’s
shall be capable of being installed and programmed to operate in a standalone mode prior to installation of the computer.
7
INSTRUCTIONS TO BIDDERS
7.1
VENDOR QUALIFICATIONS
7.1.1
The Vendor shall be fully qualified in the performance of the class of work
specified within this document and shall provide a list of similar installations
which have been completed and which may be inspected by the Purchaser or
his representative.
7.1.2
The Board reserves the right to reject any tender submitted by a party whose
financial standing is not considered to be such as to ensure the Vendor
PAGE 16 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
obtaining reasonable credit from the Vendor’s proposed suppliers for
materials.
7.2
RESPONSE TO SPECIFICATION
7.2.1
The Vendor shall submit a point by point statement of compliance with
Sections 2, 3, and 4. Each point shall be numbered as per the paragraphs in
Sections 2, 3, and 4. Any tender submission that does not include a point by
point statement of compliance with the requirements as specified in Section
2, 3, and 4 shall be disqualified.
7.2.2
Where a full description of a deviation is not provided, it shall be assumed
that the proposed system does not comply with the paragraph in question.
7.3
DESCRIPTION OF PROPOSED EQUIPMENT
7.3.1
The Vendor shall provide, as part of his proposal, a complete list and detailed
description of all equipment and software that is included in this tender.
7.3.2
Full specification sheets shall be provided for each hardware component in
order to allow the Board to make a comparison of the hardware proposed by
all Vendors.
8
PHOTO BADGING & VERIFICATION
8.1
8.1.1
SYSTEM FUNCTIONS AND FEATURES
The system shall integrate the following functions into a simple to use
package:
8.1.1.1
The Photo Badging & Verification feature shall be a separate
module integrated into the access control software at any given time.
8.1.1.2
The Photo Badging & Verification shall provide full integration into
the Access Control Software.
8.1.1.3
The photo capturing of a cardholder shall be done by any Twain
compatible device. (i.e.: Video capture card, scanner, digital camera
or other.) The card holder photo shall be displayed when viewing
that particular cardholder’s data.
8.1.1.4
End user will have the ability to view, edit, import, capture photo’s
live and print the card from the cardholder database at any given
time.
8.1.1.5
End user will be able to create, edit & import their own card
template(s) or use predefined templates for setting up their
cardholder’s background(s).
8.1.1.6
The system will allow photo verification when a token is read by the
reader, displaying the card holder photo in a separate transaction
PAGE 17 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
window.
The photo verification will also allow for up to 9 photo transaction
history windows to be displayed.
8.1.1.7
9
TYPICAL TENDER FORMAT FOR ACCESS CONTROL SYSTEM
The Dufferin-Peel Catholic District School Board (the Board) invites
proposal bids for the supply and installation of a “KEYSCAN ACCESS
CONTROL SYSTEM BY KEYSCAN” to integrate the Board’s existing
Keyscan network for the following school named herein:
9.1.1
10
The Board at the present time uses Motorola Keyscan Cards to activate the
readers. No substitution to this system is permitted.
TENDER REQUIREMENTS
10.1.1 Provide company profile with Bidder’s response.
10.1.2 Submit 3 references naming the company, contact person, and phone
number.
10.1.3 Include in your bid complete information on the following:
10.1.3.1 A detailed list of hardware being proposed for the project
10.1.3.2 A detailed list of access control hardware and its application for the
project.
10.1.3.3 Software
applications to
control
the
access control
where
applicable.
10.1.3.4 Expandability of the card access system
10.1.3.5 Compatibility of the access system, with the Motorola Keyscan
Proximity Readers
10.1.4 All products quoted relating to the access control installations on the network
of the Board, must be of Keyscan origin and must comply to the following
requirements:
10.1.4.1 All bidders must be a certified Keyscan System VII for Networks
dealer (Proof of certificate must be available) and have training and
or experience in the installation of the MSS-COMMP and MSSCOMM products from Keyscan to be eligible for consideration.
10.1.4.2 Dealer must have proven work-related experience in the area of
LAN/WAN’s utilizing the protocol of TCP/IP. (References an asset)
10.1.4.3 MSS-COMM & MSSCOMMP must be ordered from Keyscan and
pre-programmed by them. No Alternatives allowed.
PAGE 18 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
10.2 WARRANTY/GUARANTEE INFORMATION
10.2.1 Vendor presentation/demonstration may be required, and vendors must be
prepared to demonstrate the system being proposed, - at no cost to the
Board.
10.3 INSTALLATION
10.3.1 The bidder who is awarded any contract for this project must adhere to the
following procedures:
10.3.1.1 Work on the project to be conducted between the hours of xx:xx and
xx:xx during the weekdays.
10.3.1.2 Work must be done on existing doors.
10.3.1.3 Security and control of the doors must be intact during installation.
10.3.1.4 All electrical hardware must have the appropriate approvals.
10.3.1.5 All open wiring installed in the ceiling spaces shall be plenum rated.
Surface wiring shall be installed in ether EMT conduit or wiremould
minimum size conductor 22 gauge AWG. All wiring shall be tagged
or marked clearly to provide ease of reference and any cable to that
is used in any way for the Ethernet connections should be white in
colour.
10.3.1.6 Patch cables that are used at both ends of the Ethernet run are to
be ordered through the Board’s Technical Services Department.
10.3.1.7 Contact name, title
of the
Board’s IT Department at 905-890-0708 ext. XXXX.
10.3.1.8 Request Netcom 2 with the appropriate IP address for that site pre-
programmed.
10.3.1.9 Arrange in advance to have IT personal at each school site at the
end of the install (dealer must be flexible with the times IT personal
are available) in order to be shown HUB locations and connections
of same.
10.3.1.10 All work must be open for inspection at any time.
10.3.1.11 Project must be completed and invoiced by XX XXX 20XX
11 SYSTEM REQUIREMENTS
11.1.1 The Floor Plans, as prepared by the Architect’s Consultant, showing power
characteristics and conduits as necessary to integrate the Card Access
System will be attached to the specification, and will become an integral part
of the Card Access Tender.
11.1.2 The complete system shall include equipment and methodology as described
in an attachment with the card Access Tender.
PAGE 19 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
12 PROPOSAL EVALUATION CRITERIA
12.1.1 This RFP includes standards and specifications that the Board believes are
the most appropriate to its needs.
12.1.2 All proposals received shall be subject to evaluation by a committee of
qualified personnel for the purpose of selecting the proposal, which most
closely meets the requirements of the RFP. The following areas of
consideration will be used in making selections:
12.1.2.1 Experience and background of the bidding individual or firm
(Please submit references, including contact names and telephone
numbers.)
12.1.2.2 Ability of vendor to perform the required service competently and
expeditiously
13 APPLICABLE TAXES
13.1.1 With the exception of the GST, the Contractor shall include all applicable
taxes in force, during the progress of this project. GST shall be shown and
invoiced separately.
13.1.2 Any taxes announced prior to date of quotation and scheduled to come into
effect subsequent to it shall be taken to be included. Any changes to taxes
announced subsequent to date of quotation shall be added or deducted from
the contract sum on evidence submitted by the Contractor.
14 WORKER’S COMPENSATION
14.1.1 The Contractor shall provide Worker’s Compensation coverage for all
employees who are employed under the contract.
14.1.2 The successful Contractor, prior to having a purchase order issued to him,
and prior to commencing any work on the site, shall present proof of this
coverage to the Board.
14.1.3 Proof of this coverage shall also be submitted to the Board with each invoice
when requesting payment.
15 BOARD’S RIGHT TO TERMINATE THE CONTRACT
15.1.1 In the event that the Board’s Consultant deems that sufficient cause exists,
the Board may notify the Contractor, in writing, that he is in default of his
contractual obligations. The default may apply if the Contractor:
15.1.1.1 Refuses or fails to supply sufficient properly skilled workmen, or
proper workmanship, products or construction machinery and
equipment for the scheduled performance of the work or,
PAGE 20 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
15.1.1.2 Fails to make payments due to his Subcontractors, his suppliers, or
his workmen; or,
15.1.1.3 Persistently
disregards laws or ordinances, or the owners
instructions, or,
15.1.1.4 Otherwise violates the provisions of the contract to a substantial
degree.
15.1.2 In the event of a Health and Safety violation, such written notice by the Board
shall instruct the Contractor to correct the default immediately.
15.1.3
Violations other than Health and Safety must be corrected by the Contractor,
within five (5) working days from the receipt of the written notice.
15.1.4 If the Contractor fails to correct the default within the time specified, or
subsequently agreed upon, the Board may, without prejudice to any other
right or remedy it may have, terminate the Contract.
15.1.5 If the Board terminates the contract under the conditions set out above, it is
entitled to:
15.1.5.1 Take possession of the premises and products and utilise the
construction machinery and equipment the whole subject to the
rights of third parties, and to finish the work by whatever methods he
may deem expedient but without undue delay or expense;
15.1.5.2 Withhold any further payments to the Contractor until the work is
finished.
16 CONSTRUCTION SAFETY ACT
16.1.1 The work of this contract shall be executed in strict accordance with the
current Occupational Health and Safety Act of the Province of Ontario.
16.1.2 The Contractor shall be responsible for ensuring that his workmen abide by
the rules and requirements set forth under the Act and a copy of the Act is to
be available on the site at all times when work is being performed.
17 ASSIGNMENT OF CONTRACT
17.1.1 The Contractor acknowledges that neither the contract nor any part of the
proceeds thereof may be assigned or sublet to any other Contractor or Subcontractor without the written consent of the Board.
18 LIENS AND DAMAGES
18.1.1 The successful Contractor agrees to protect and save harmless the Board
from all liens, damages, etc., arising from or caused by his work.
PAGE 21 OF 22
SECURITY
SYSTEMS
GUIDELINE
Card Access
19 CONTRACTOR ON SITE
19.1.1 The Contractor shall ensure the procurement of all required materials for the
project, prior to the commencement of work on the project.
19.1.2 All furniture must be placed back into position and the room left clean and
tidy.
19.1.3 The contractor shall clean up and remove debris on a daily basis. Under NO
circumstances shall the Contractor use the school's garbage dispose
containers.
19.1.4 Smoking is NOT permitted in any of the Board’s buildings or on any of the
Board’s properties. All smoking must be done off premises.
20 PROTECTION AND MAKING GOOD
20.1.1 Provide proper and adequate protection for all school property and
equipment. Ensure that dust is contained within the area of work.
20.1.2 The contractor shall be responsible for moving all furniture and equipment
and replacing same at the completion of the work all as directed by the
custodian.
20.1.3 Make good, at no additional cost to the Board, all surfaces disturbed by the
execution of this contract whether such surfaces are located within the area
of work or not. Make good to new condition matching surrounding surface.
END OF CARD ACCESS SYSTEM GUIDELINE
LATEST REVISION IN GREEN FONT
DATE ISSUED:
REVISION 1:
MARCH 2001
APRIL 2002
REVISED:
JUNE 2009
E:\Data\Word\INSTRUCTIONS\DPCDSB SECURITY SYSTEMS - Card Access.doc
PAGE 22 OF 22