Section Cover Page
Section 28 13 00
Electronic Access Control
2014-02-06
Use this Section to describe electronic access control system. This section is based on current IP control
panel technology.
This Master Specification Section contains:
.1
.2
.3
This Cover Sheet
Data Sheet - Sample Schedule
Specification Section Text:
1
General
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
Summary
Performance Requirements
References
Reference Documents
Reference Standards
Submittals
Delivery, Storage and Handling
[Warranty]
2
Products
2.1
2.2
2.3
2.4
2.5
2.6
Open Architecture
System
Access Control System
Operation
Equipment
Materials
3
Execution
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
Installation
Training
Testing
Installation: Burglar Alarm System
Installation: Security Access
Verification
[System Startup]
Cleaning
Protection
Maintenance
2014-02-06 BMS Version
Data Sheet - Sample Schedule
Section 28 13 00
Electronic Access Control
2
Following is a sample schedule indicating the format and typical content of the "Card Reader Schedule"
to be included at the end of this Section:
3.X
EXAMPLE CARD READER SCHEDULE
Examples:
Intelligent System Controller
(ISC)
EDM-B0192Sx-004-00423-E001-ISC001
Input Interface Module (IIM)
EDM-B0192Sx-004-00423-E005-IIM001
Output Interface Module (OIM)
EDM-B0192Sx-004-00423-E005-OIM001
Reader (RDR)
EDM-B0192Sx-004-INT-Sx-DATA RM 423xxxxxxxxx-RDR0001
Intrusion Keypad (IKP)
EDM-B0192Sx-004-Sx-ZONE 1xxxxxxxxxxxxxx-IKP0001
Intrusion Alarm Input (IAI)
EDM-B0192Sx-004-00423-SE WINDOW GLASS BRxx-IAI0001
ISC, IIM, OIM
[3 CHAR CITY ABBREVIATION][7 CHAR BUILDING CODE]-[3 DIGIT FLOOR#]-[5 DIGIT ROOM#]-[4
DIGIT ENCLOSURE#]-[3 CHAR DEVICE ABBREVIATION][3 DIGIT LOGICAL#]
RDR
[3 CHAR CITY ABBREVIATION][7 CHAR BUILDING CODE]-[3 DIGIT FLOOR#]-[2 CHAR DIRECTION
CODE]-[3 CHAR INT/EXT]-[20 CHAR LOC DESCRIPTOR]-[3 CHAR DEVICE ABBREVIATION][4 DIGIT
LOGICAL#]
IKP
[3 CHAR CITY ABBREVIATION][7 CHAR BUILDING CODE]-[3 DIGIT FLOOR#]-[2 CHAR DIRECTION
CODE]- [20 CHAR LOC DESCRIPTOR]-[3 CHAR DEVICE ABBREVIATION][3 DIGIT LOGICAL#]
IAI
[3 CHAR CITY ABBREVIATION][7 CHAR BUILDING CODE]-[3 DIGIT FLOOR#]-[5 DIGIT ROOM#]-[20
CHAR LOC DESCRIPTOR]-[3 CHAR DEVICE ABBREVIATION][3 DIGIT LOGICAL#]
END OF DATA SHEETS
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 1
Project ID.:
1
General
1.1
SUMMARY
.1
Section Includes:
.1
.2
Section including complete and working access control system including:
.1
Redundant Server hot standby configuration c/w system software
& data base.
.2
System operator workstation(s) to show status & alarms and
perform administrative functions.
.3
Wiring infrastructure
.4
Remote field panels c/w input/output boards for controlled door
operation
.5
Battery backup surge protected power supplies for field panels,
Human Machine Interface (HMI), and control CPU.
.6
Reader stations
.7
Credentials (Access Cards)
.8
Request to exit.
.9
Door position switches.
Products Supplied but not installed under this section
.1
Credentials (Access Cards)
.2
[
]
SPEC NOTE: Address communication or integration requirements between Access Control
and Video Surveillance system 28 23 00.
.3
Connection of work supplied and installed under other sections
.1
.4
Connect via relays or otherwise, the following auxiliary equipment
supplied and installed under other Sections:
.1
Door hardware
Section 08 71 00
.2
Elevator control
.3
Magnetic door holders
Section 08 71 00
.4
Products-of-combustion detection
Section 28 31 00
.5
[
Division 14
]
Related Requirements
.1
Elevators
Section 14 20 00.
.2
Electrical General Requirements
Section 26 00 10.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 2
Project ID.:
.3
Electrical Operation and Maintenance Data
Section 01 78 23.
.4
Spare Parts and Maintenance Materials
Section 01 78 43.
.5
Wire and Cable
Section 26 05 13.
.6
Electrical Identification
Section 26 05 53.
.7
Electrical Systems
Section 26 08 00.
.8
Commissioning of Demonstration and Training
Section 01 79 00.
.9
Structured Cabling
Section 27 10 00.
.10
Door Hardware
Section 08 70 00.
SPEC NOTE: Where access control system is sole source to match existing system expansion,
an allowance for a pre negotiated scope & cost could be included.
1.2
PERFORMANCE REQUIREMENTS
.1
Access control and security access systems using only [ULC/UL Listed] [non
listed] products.
.2
Security access system using [ULC/UL Listed Alarm Service Company],
company [specializing in security access systems].
.3
Security access system for [ULC/UL Listed Central Station] an alarm monitoring
facility having capability to provide specified service.
.4
Security access system as a [ULC/UL Certified Alarm System] [non certified
alarm system].
.5
System as type: [Central] [Mercantile] [Proprietary].
.6
Central Station Burglar Alarm (CPVX): To [CAN/ULC [___]] [ORD-C [___]]
[UL [___]]. Design operation of electrical protection circuits and devices for
signalling automatically to, recorded in, maintained and supervised from central
station with arming and disarming supervised by central station.
.1
.2
2014-02-06 BMS Version
System description:
.1
Type of system: [premise] [stockroom] [___].
.2
Extent of protection: defined by UL 681, Level [1] [2] [3] [4],
[complete] [partial].
.3
Area covered: [___].
.4
Alarm sounding Device: [none] [inside] [outside] [inside and
outside].
Remote monitoring:
.1
Monitoring location: [___].
.2
System with no investigator response.
Project No.:
Section 28 13 00
Electronic Access Control
Page 3
Project ID.:
.3
.3
[Primary] [Secondary] signal transmission method.
.4
UL Listed alarm transport company: [___].
.5
[Standard line security] [No line security] employed.
.6
Monitor for fault or alarm.
.7
Identify fault location.
.8
Monitor all power
Alarm investigator: Design system to accommodate the following
response time and investigator team requirements.
.1
.2
Investigator response time:
.1
Line security systems [standard] [encryption]: [5] [10] [15]
[___] minutes.
.2
No line security systems: [5] [10] [15] [___] minutes.
Investigator team:
.1
[One] [Two] runner[s]; [with] [without] keys; [no] [plus]
local law enforcement.
.2
None, alarm retransmitted only.
.7
Design access control systems to meet safety requirements specified in
accordance with UL 294.
.8
Design system to provide door manual and automatic control functions from
locations indicated to central monitoring system.
.9
Design system to allow for addition of future Door release switch (DRS) controls
and activation units by adding appropriate transmission lines and equipment at
each location.
.10
Design system to consist of homed run control to activation unit connections.
.11
Each activation unit must have door panel control function/equipment item
located as indicated.
.12
Design system to provide ease of operation, servicing, maintenance, testing and
expansion of additional services.
.13
Door activation units
.1
Fully complement and function and match door manufacturer’s magnetic
controls and hardware.
.2
Fully function with Original Equipment Manufacturer (OEM) supplied
door controls and hardware to activate system in routine and emergency
conditions.
.3
Fully function within supplied electrical supervision circuits as specified.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 4
Project ID.:
.14
.15
Control Panel
.1
Fully compatible, compliment and operate door magnets provided by door
manufacturer of system or OEM supplied door operating hardware.
.2
Complete with push button or electronic key pad to release and secure
each door.
.3
Identify each door control function with lamp electronically identified on
panel or associated display unit.
.4
Permanently label (paper labels are not acceptable) or electronically
identify each door location on panel or associated display unit.
.5
Fully function within supplied electrical supervision circuits as specified.
Control Signal Standards
.1
Input and Output Signal: 0.0 dBmV + 1.0 dBmV Level.
.2
Input and Output Signals: Terminated on each Control Unit.
.3
Input and Output Impedance: 120 Ohms, BAL.
.4
Channel Bandwidth:
.5
.16
1.3
.1
Data: 300 Hz to 3.5 kHz (9.6 kilobits per second rate).
.2
DC: 0.5 Hz to 100 Hz, + 5.0%, MIN.
S/N Ratio: 60 dBmV + 1.0 dBmV.
Intercom System
.1
Design door answering system with door and interior stations including
door release where indicated.
.2
System to be complete with system calls, [with privacy handsets,] audio
and video, and mounting requirements as specified,
REFERENCES
.1
1.4
Abbreviations and Acronyms
.1
Request to exit Sensor
REX
.2
Door Position Switch
DPS
.3
Security Access Control
SAC
.4
Security Management System
SMS
.5
Personal Identification Number
REFERENCE DOCUMENTS
.1
National Fire Protection Association (NFPA)
.1
2014-02-06 BMS Version
NFPA 70, Article 517, National Electric Code
PIN
Project No.:
Section 28 13 00
Electronic Access Control
Page 5
Project ID.:
.2
.2
.3
Electronic Industries Association (EIA)
.1
REC 12749, Power Supplies.
.2
RS 16051, Sound Systems
ANSI/BICSI
.1
1.5
NFPA 101, Life Safety Code
005-2013: Electronic Safety and Security Systems Design and
Implementation Best Practices
REFERENCE STANDARDS
.1
.2
Underwriters Laboratories of Canada (ULC)
.1
CAN/ULC-S301- [1988], Central and Monitoring Station Burglar Alarm
Systems.
.2
CAN/ULC-S302- [1991], Installation and Classification of Burglar Alarm
Systems for Financial and Commercial Premises, Safes and Vaults.
.3
CAN/ULC-S303- [1991], Local Burglar Alarm Units and Systems.
.4
CAN/ULC-S304- [1988], Central and Monitoring Station Burglar Alarm
Units.
.5
CAN/ULC-S310- [1991], Installation and Classification of Residential
Burglar Alarm Systems.
.6
CAN/ULC-S319-05. Electronic Access Control Systems.
.7
ORD-C827- [1973], Central Stations for Watchman, Fire alarm and
Supervisory Services.
.8
ORD-C1023- [1974], Household Burglar Alarm System Units.
.9
ORG-C1076- [1986], Proprietary Burglar Alarm Units and Systems.
.10
ORD-C488- [1995], Remote Burglar Alarm Signaling Centres
Underwriters' Laboratories (UL)
.1
UL 294-[1999], Standard for Safety for Access Control System Units.
.2
UL 365- [1997], The Standard for Police Station Connected Burglar alarm
Units and Systems.
.3
UL 609- [1996], the Standard for Local Burglar Alarm Units and Systems.
.4
UL 636- [1996], the Standard for Holdup Alarm Units and Systems.
.5
UL 681- [1999], Installation and Classification of Burglar and Holdup
Alarm Systems.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 6
Project ID.:
.6
UL 827- [1996], Standard for Central Station Alarm Services or (the
Standard for Central Station for Watchman, Fire Alarm and Supervisory
Services).
.7
UL 1076- [1995], Standard for Safety for Proprietary Burglar Alarm Units
and Systems.
.8
UL 1610- [1998], The Standard for Central Station Burglar Alarm Units.
.9
UL 1635- [1996], the Standard for Digital Alarm Communicator System
Units.
.10
UL 1641- [1999], Standard for Safety for Installation and Classification of
Residential Burglar Alarm Systems.
.11
UL 1981- [1994], Standard for Central Station Automation Systems.
SPEC NOTE: in occupied facilities careful coordination with the users is required for the
minimum disruption installation or modification of the Access Control System.
1.6
SUBMITTALS
.1
Provide submittals in accordance with [Section 01 33 00 – Submittal Procedures].
.2
As-built Records and Drawings:
.1
Confirm format with the Minister prior to preparation of submittals.
.2
Provide electronic drawings in [AutoCAD 2009] format depicting all as
built conditions.
.3
Provide two [2] sets of as-built records to the Minister.
.1
1.7
Include a floor plan showing the location of all equipment.
DELIVERY, STORAGE, AND HANDLING
.1
Waste Management and Disposal: separate waste materials for reuse and
recycling in accordance with Section [01 74 19 - Waste Management and
Disposal].
.2
Stored and handle materials to ensure that their performance requirements are not
affected by abrasions, dust or extreme temperatures.
.3
Follow manufacturer recommendations for handling and storage to ensure that
their performance requirements are not affected by abrasions, dust or extreme
temperatures.
.4
Do not bring equipment to site until required for use and a suitable storage space
has been identified.
1.8
[WARRANTY]
.1
[Manufacturer Warranty]
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 7
Project ID.:
2
Products
SPEC NOTE: Confirm at outset compatibility requirements to existing on or off site systems
confirm card compatibility requirements (e.g. HID Corporate 1000 format)
2.1
OPEN ARCITECTURE
.1
The system shall have an open architecture design. It shall be a true open
architecture design and support industry standards for database, networks, ID and
card printers, and video cameras. No customized or proprietary PC or ID badge
creation software or hardware shall be required to operate the system.
.2
The system shall be Open Database Connectivity (ODBC) compliant. The system
shall support relational database management system with the proper 32-bit
ODBC drivers. Examples of these databases include, but are not limited to,
Microsoft SQL Server and Oracle Server.
2.2
SYSTEM
.1
The System shall be an integrated system that utilizes a single, industry-standard
relational database management system for the storage and manipulation of
related data. The system shall include a server with operating system and
applications software, operator and administrator terminals with appropriate
software, hard copy printers and fixed magnetic storage media. The security
devices shall communicate with the field panels via a dedicated cable network.
The field panels shall communicate to the server via a Fast Ethernet 10/100,
TCP/IP network or a serial (RS-232, RS-485) connection
.2
The Access Control System shall allow for growth and scalability from a low-end
or entry level system to a high end or enterprise system by increasing CPU power,
memory and database. The system shall be modular in nature, allowing system
capacities to be easily expanded without requiring major changes to system
operation. All defined system data as well as historical information shall be
maintained. Customizable user interfaces shall allow management of system
information and activity for administrators and operators. The System shall
include an intuitive .NET based badging solution with a WYSIWYG badge layout
editor and GUI for badge design
SPEC NOTE: Confirm compatibility requirements to any existing access control equipment.
2.3
ACCESS CONTROL SYSTEM
.1
Partitioning - The System shall allow system administrators to separate the
creation and viewing of objects into partitions. System operators shall be
associated with partitions and this shall determine which objects operators have
the ability to create, edit and or view. The System shall support an unlimited
number of partitions.
.1
2014-02-06 BMS Version
The System partitions shall include but not be limited to the following
objects:
Project No.:
Section 28 13 00
Electronic Access Control
Page 8
Project ID.:
.2
.1
Personnel
.2
Controllers with all associated hardware (readers, inputs, outputs, etc.)
.3
Video servers with all associated objects (cameras, tours, views, etc.)
.4
Application layouts
.5
Events
.6
Maps
.7
Reports, forms, results
.8
Holidays
.9
Badge layouts
.10
Queries
.2
Through the use of privileges, the System Administrator shall be able to
determine which objects are associated with a particular partition. These
objects shall then be assigned to System Operators with the appropriate
privilege.
.3
The System shall support a super-user (Admin) assigned the ‘System All’
privilege who shall have full access to all objects in all partitions.
.4
Any operator shall have the ability to be assigned access rights to any
partition. Individual Access rights shall be created and have the ability to
be assigned to any users of the system.
.5
The System shall allow objects to be created in any partition.
.6
The System shall provide the ability to move objects from one partition to
another partition without the requirement of deleting and recreating.
.7
The System shall support the display of all associated objects contained
within a partition.
Graphical User Interface (GUI)
The System shall employ a standard Windows™ graphical user interface (GUI).
A mouse and keyboard shall be the primary operator interface with the system.
Operator screens shall utilize all standard Windows-style functions such as dropdown menus, context menus, radio buttons, and lists, as appropriate. The
interface shall utilize a ‘tree structure’ similar to Windows Explorer.
.1
Administration Operator Interface
.1
The System shall employ an Administration Operator Interface to control
the following:
.1
2014-02-06 BMS Version
Hardware (readers, inputs, outputs, video systems, door controls,
Video Surveillance, and other systems).
Project No.:
Section 28 13 00
Electronic Access Control
Page 9
Project ID.:
.2
.2
.2
Configuration of personnel records, operators and operator
privileges.
.3
Graphical Maps.
.4
Queries.
.5
Import/Export of objects, including images.
.6
System Variables.
.7
Reports (either periodic or one-time).
.8
System functions (event command and control, actions, schedules).
.9
Display of a list of objects in a grid that can have their values
modified and respond to real-time status changes.
.10
Scheduling of backups.
.11
Monitoring of system settings and performance.
.12
Designing of and printing of badges.
The GUI shall be configurable by the system administrator to control the
views and access of each Monitoring Station operator.
Monitoring Operator Interface / Activity Monitoring
.1
The System shall contain a monitoring component that is capable of,
among other things, displaying the current state of any object in the
system. Additionally the monitoring station shall be capable of displaying
a log of all activity that occurs in the system, from object state changes, to
access control information.
.2
The Monitoring Station shall be capable of showing all changes occurring
to an object without requiring the associated activity messages for that
object to be routed to that monitoring station. The System shall require the
operator to have appropriate permissions to view and/or control any
object.
.3
The System shall provide the Monitoring Operator with following
functional capabilities:
2014-02-06 BMS Version
.1
Shall provide a scrolling list of lines or tiles showing current
activity on the system.
.2
Shall display activity in real-time as data is being transmitted by
field hardware.
.3
A series of menus, driven by drop-down or trees, shall allow the
Monitoring Station operator to perform manual actions, such as
“momentary door unlock” for a given door.
.4
As part of the manual action capability, the system shall provide
screens or boxes that query the operator on specifics, such as start
Project No.:
Section 28 13 00
Electronic Access Control
Page 10
Project ID.:
and end time, and offer guidance on performing the manual
actions.
.4
2014-02-06 BMS Version
.5
A GUI that displays the images of personnel as they enter, as well
as the stored images of personnel available in the system.
.6
Ability to view a sort able list of active alarms or events and
recently active alarms or activity.
.7
Ability to view video from VMSS systems within the same GUI.
The video screen GUI shall be able to display multiple panes of
live or recorded video and have on-screen camera controls for each
live window, providing Pan-Tilt-Zoom (PTZ) control of individual
cameras.
.8
A GUI that minimizes the number of operator mouse clicks or
keyboard strokes.
.9
Mouse controls include “right-click” pop-ups and highlighted
default selections.
.10
Objects shall be displayed to the operator based on his/her assigned
operator privilege. The operator shall only be able to
monitor/command those objects for which he or she has been
assigned privilege.
.11
When an operator logs out of a workstation and a new operator
logs on, the objects displayed on the workstation screen shall by
dynamically updated to display only those objects for which the
new operator has privilege.
.12
Allow the customization of columns as defined by the operator
privilege, including:
.1
Adjusting width (on the fly or pre-programmed).
.2
Not displaying Columns (on the fly or pre-programmed).
.3
Sorting on selected columns (to follow standard Windows
conventions).
.13
Allow for a “freeze” function. This includes a configurable “freeze
time-out” that permits an activity to be selected and temporarily
prevents the display of subsequent activities which push the
selected activity off the screen. A break-through event disables the
freeze function.
.14
Support multiple panes for the display of events, activities, video,
personnel images, and maps.
The System shall support audible alarm annunciation at operator
workstations (operator configurable audio files associated with alarms).
Project No.:
Section 28 13 00
Electronic Access Control
Page 11
Project ID.:
.5
.3
The activity monitoring screen shall be capable of displaying the
following features:
.1
System clock.
.2
Date/time when the activity actually occurred and the date/time
when the activity was received by the server shall be displayed
(when they are different).
.3
Real time event counters.
.4
Count of the active events.
.5
Count of the events requiring operator acknowledgment.
.6
Name of operator logged on at the workstation.
.7
Real-time display of the current activity on the system in
chronological order.
.8
Right-click actions for each event based on event type.
.9
Pre-defined and configurable acknowledgement messages.
.10
Log message.
.11
Clear event.
.12
Clear group of events.
Graphic Maps
.1
The System shall support unlimited graphic maps and icons to be
displayed on the operator workstation monitor.
.2
The system shall support an operator-programmable, color graphic map
display that:
.3
2014-02-06 BMS Version
.1
Shall be capable of showing the floor plan, the location of alarm
devices, and alarm instructions for a facility.
.2
Shall be centralized in the system configuration and displayed on
the operators’ workstations.
.3
Shall allow various maps to be associated with different areas to
create a hierarchy of maps.
.4
Shall support graphic maps having a resolution of 1024x768 Pixels
or greater.
Operators shall be able to use [drag-and-drop mouse technique] [touch
screen] to place dynamic system level object icons of all objects such as:
cameras, video servers, inputs/outputs, events, maps, reports, dynamic
views, and door/elevator icons. These dynamic object icons shall allow a
system operator to perform tasks and issue commands related to the object
by double-clicking on the icon. The icons shall employ animation and
color changes to indicate alarm or off normal conditions.
Project No.:
Section 28 13 00
Electronic Access Control
Page 12
Project ID.:
.4
The operator shall be able to create a line object that can be used to denote
a fence line. The line object shall allow the operator to click on a starting
point and continue left-click operations to draw fence sections
interconnected at various angles until the fence line has be accurately
depicted. The operator shall end the fence line by right-clicking the
mouse. The fence line shall change colors and flash when denoting an
alarm event, and shall return to normal after being acknowledged by the
operator.
.5
The System shall allow the addition of sub-maps to be assigned to a map
creating a hierarchical map navigation system.
.6
The System shall be able to directly import the following file formats for
the map:
.1
.7
.4
[JPEG (.JPG)] [Bitmap (.BMP)] [AutoCAD (.DWG)] [Other]
The Maps feature shall include two operational modes: an administrative
mode to allow configuring of the facility floor plans or site plans that
show exterior features and a runtime mode to allow monitoring and
interacting with the configured facility layouts or site plans. The Maps
feature shall also include a tracking window, a magnification window, and
a coordinates window.
Information Storage, Backup and Transfer
.1
All programmed information, as well as transactional history, shall be
automatically stored in the database for later retrieval and backup. The
System shall support configurations where the System database(s) may be
installed on a hard drive on the System server, on an independent database
server, or in an existing corporate database server.
.2
The System shall be capable of backing up and restoring all system data
and transactional history. The server shall be capable of transferring all
programmed data and transactional history to CD-ROM, DVD, or Hard
Drive (including networked drives).
.3
The System shall allow activity history to be written to a database. The
system shall have the capacity to store a minimum of 50 million
transactions. There shall be a method of backing up the activity history on
external media and then restoring and replaying it.
.4
The System shall support AES 256-bit encrypted communications
between server and user client.
.5
The System shall support AES 256-bit encrypted communications
between server and controller. The encryption shall support both local and
third-party digital certificates.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 13
Project ID.:
.5
.6
Communication Ports
.1
The System shall be able to support multiple serial devices. In addition to
COM1 and COM2, up to [8, 16, 32, to 256] additional ports may be
configured through the use of a port expander or its equivalent. These
serial ports may be used for connection to Video Surveillance matrix
switchers, or other controllers.
.2
The System shall support the use of Ethernet networks as the
communications path between the host computer and field devices such as
the Mercury controllers, iTDC controllers, and Video Surveillance matrix
switchers. This communications path shall be the same network used for
communications between the host server and the operator workstations.
The communications between the host computer and the field devices
shall be encapsulated in a TCP/IP network/transport layer.
Software Configuration
.1
The System configuration tools shall utilize intelligent configuration
controls. The system shall be structured so an operator is unable to
perform configuration functions that are invalid based on the configuration
used. The system shall support the ability to search within browser lists
using filtering operators such as “begins with”, “ends with”, “contains”,
etc. The system shall also allow an operator to do searches using filtering
operators on any class of object in the system, both in the Administration
application and the Monitoring Station application.
.2
The System shall allow text description of all configured objects. The
System shall allow the renaming of an existing title description without
removing the sub-components of that configuration object. The System
shall automatically remove from the system all configuration references to
an object being deleted. The System shall automatically provide default
names for all inputs, outputs, readers, and extension boards. The System
shall clearly display which hardware objects (inputs, outputs, readers) on a
controller are configured, and which are not.
.3
The System shall when adding hardware, automatically add all associated
inputs, outputs, readers, etc. with associated addressing and unique
identification provided.
.4
The System shall allow automatic disabling of objects that are not
typically used thereby limiting the objects displayed in lists and trees to
only the active objects within the system. The operator shall have the
option of selecting disabled objects for display, and the ability to enable
objects and to place them into uses.
.5
The System shall support an unlimited number of groups for any object
type. The System shall support unlimited object group definitions. In
general, a group shall be usable wherever an individual object is
referenced in the System. For example, a group may be used instead of an
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 14
Project ID.:
object when configuring a schedule/object pair in a clearance, and a group
may be used instead of an object when performing a manual action to
unlock a door.
.7
.6
The System shall generally allow any object in the system to be grouped
including personnel, doors, inputs, and outputs. The System shall restrict
the viewing and controlling of objects in the administration and
monitoring stations via operator privileges. The System shall support the
configuration of operator restrictions on an object class basis, and on an
object-by-object basis. The System shall maintain a distinction between
objects that are being monitored and objects that are being controlled,
preventing operators from issuing object manual actions to objects for
which the operator does not have manual action privileges. There shall be
different levels of controls within the system for administration privileges
versus monitoring privileges
.7
The System shall support unlimited operator accounts with unlimited
definable privilege levels.
.8
The System shall allow configuration of controllers and other objects such
as inputs, outputs, readers, maps, and personnel using lists or hierarchical
tree-based navigation and context menus.
.9
The System shall support the ability to download firmware updates to the
controllers.
.10
The System shall provide an automatic client update process for quick
distribution of application updates.
.11
The System shall have online help capability for each module and for the
complete application available at any point requiring operator input.
Personnel Records
.1
The System Personnel records shall provide multiple tabbed pages of
personnel data containing default system and user-defined fields. The
System shall support a tab for user defined information with a minimum of
10 additional fields. Labels for user-defined field tabs shall be
customizable by the System Administrator with the appropriate privileges.
Each user-defined field shall allow a name, description and label.
.2
User-defined fields shall support the following field types:
2014-02-06 BMS Version
•
Character
•
Integer
•
Logical
•
Date/Time
•
Date
Project No.:
Section 28 13 00
Electronic Access Control
Page 15
Project ID.:
.8
.9
.10
.11
•
Time
•
Decimal
Language Localization
.1
The System shall be configured so the information presented to system
operators is displayed in a language native to the system operator provided
that the proper translation files exist.
.2
It shall be possible to translate the System into any left-to-right or right-toleft language supported by Unicode and by the Microsoft Windows
operating system.
Inputs
.1
The System shall monitor both supervised and unsupervised hardware
inputs as well as virtual inputs such as predefined system messages. These
inputs include door / elevator inputs and monitor points. The System shall
also monitor controller inputs such as tamper, AC fail, and low battery.
.2
The System shall have the ability to name and allow for user-defined
descriptions for individual inputs, outputs, and readers as well as input and
output modules.
.3
There shall be two separate and distinct states for inputs which can be
defined on the input configuration screen: Disabled/ Enabled.
.4
The System shall allow configuration to link the state of an input to an
output. The system shall allow multiple inputs to activate a single output
or group of outputs.
Outputs
.1
The System shall have outputs, also known as Control points that associate
an input or event action with a relay. These output uses include doors /
elevators, alarms and industrial control.
.2
There shall be two types of outputs available: dry contact / Form C relays
and digital outputs (depending on the hardware platform used). Outputs
shall be configured such that they can be activated, deactivated or pulsed
by system actions.
Card and Reader Support
The System shall be designed to support multiple card formats and card reader
types
The System shall support the following features for directly connected readers:
.1
User defined card formats up to 256 bits.
.2
Unlimited number of System card formats.
.3
The ability to assign up to 8 card formats per reader.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 16
Project ID.:
.12
.13
.4
Support Wiegand and 3x4 matrix keypads.
.5
The enrollment of biometric templates to smartcards.
.6
Custom CHUID FIPS201-compliant supporting full 256-bit data.
.7
The System shall support readers that provide Wiegand signaling and
magnetic signaling to include:
.1
Wiegand swipe/insert readers.
.2
Proximity readers.
.1
Thin Profile
.2
Standard
.3
Long Range (vehicle entrance).
.4
c/w PIN Pad
.5
Weatherproof
.6
Vandal Resistant
.3
Biometric readers.
.4
Smart card readers.
.5
Wireless readers.
.6
Magnetic readers.
Keypad Commands
.1
The System shall support keypad commands. Keypad commands shall be
up to 15 digits in length. Keypad commands shall be entered at a keypad
connected to a Mercury controller and shall be used to activate system
events. The event shall be configurable to activate any allowable event
action.
.2
The System shall support the assignment of certain users as Keypad
Command Administrators. These users shall be able to issue all Keypad
Commands and shall not be required to be part of a Personnel Group
assigned to a Keypad Command.
.3
Keypad commands shall have the ability to be limited to specific doors as
part of a Door Group within a defined Cluster.
Door Configurations / Elevator Control
.1
2014-02-06 BMS Version
The System shall allow doors to be configured to operate in any of the
following access control modes:
.1
Unlocked
.2
No Access (Secure mode)
Project No.:
Section 28 13 00
Electronic Access Control
Page 17
Project ID.:
.3
.2
.14
Any combination of the following, as defined by schedule, event:
card only, PIN only, Card + PIN, Card or PIN
The System shall allow a door to be configured to operate using the
following functions:
.1
Readers shall read cards while the door is in the open position.
.2
Door lock relay shall automatically lock upon the door being
opened.
.3
Allow for a user-defined delay relock time period.
.4
Allow for a user-defined door unlock time and door held open
time.
.5
A separate (alternate) shunt timer for ADA flagged cardholders
.6
The operator shall be able to specify a shunt expiration output to be
triggered for a configurable time (in hh:mm:ss) before the
expiration of the door open or alternate shunt. Can be enabled for
ADA only, or all the time.
.7
Allow for a user-defined door unlock and door held time, in
seconds.
.8
PIN-only access (keypad).
.9
PIN-entry on the reader keypad shall be required during a specified
schedule after a card access (unless a manual action or event has
disabled PIN).
.10
Card entry through keypad.
.3
The System shall allow each door to be configured to cause a variety of
events such as alarms to occur based on activity at that door.
.4
The System shall support configuration of unlimited elevators.
Area Control and Anti-pass back
.1
The System shall support the ability to define Area configurations. Areas
are defined as physical regions bounded by doors. An area shall consist of
a room, a specific location(s) within a building, or an entire building.
.2
All configured areas shall have in/out access doors providing the ability to
run reports showing all present cardholders in each area. [There shall be
no way to leave an area without presenting a credential to a reader/door.]
.3
The System shall provide the ability to run a Roll Call report. The host
shall maintain a current area for each personnel record, and the time at
which the area was entered (AreaAccessTime).The current area shall
represent the last area entered by the cardholder based on a valid admit.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 18
Project ID.:
.4
The System shall support Area control to provide the ability for tracking
personnel. With this function, an operator shall obtain the current location
of cardholders. Dynamic views and or reports can be generated to show
specific cardholders who are present in each defined area.
.5
Each cardholder’s record shall provide easy access to view and maintain
their current area location. This card record property will be updated as a
person moves from one area to another using a valid credential.
.6
The local controller shall provide the ability to manage and control the
Area configuration in the event that it loses communication with the
system server.
.7
The System Area configuration shall have three modes of operations:
None, Anti-pass back, and Timed Anti-pass back.
.8
Anti-pass back shall control access based on the cardholder’s location.
The System shall deny access to cardholders who are in violation of antipass back rules. In the event that a cardholder leaves an area without
presenting their credential to the out access reader/door and then tries to
enter back into the area by swiping the In access reader/door, a denial of
access will occur. The System shall provide the ability to grace individual
cardholders who have violated anti-pass back rules. The Grace option
shall also provide the ability to grace all cardholders.
.9
Anti-pass back shall continue to be enforced during communications
failure. System controllers shall have the ability to be clusters in a group.
The master controller in the group and all other controllers within that
group shall have full access to the existing anti-pass back information. The
cluster can be configured for ‘No Access’ Communications Failure mode
or for ‘Local’ Communications Failure mode.
.10
The System shall support Timed Anti-pass back. Areas configured for
Timed Anti-pass back shall require a cardholder use an exit reader to exit
an area. Cardholders who do not exit properly shall be required to wait for
a predetermined period of time before re-entering the area.
.11
The System shall provide occupancy restrictions for areas. Restrictions
shall be applied to individual cardholders (personnel) or user defined
groups of cardholders. Areas shall be configurable to provide limits for the
maximum and minimum number of personnel who can access an area at
one time. It shall be possible to trigger an event based upon a violation of
either of these rules. Events shall be configurable based upon the
following criteria:
2014-02-06 BMS Version
.1
Maximum occupancy status
.2
Minimum occupancy status
.3
Personnel Count (user-defined)
.4
Violation status (Anti-pass back entry/exit violation etc.)
Project No.:
Section 28 13 00
Electronic Access Control
Page 19
Project ID.:
.15
.16
.17
.18
Schedules
.1
The System shall support unlimited operator configurable schedules. Each
schedule shall allow individual time intervals.
.2
Each system controller shall support a minimum of 128 schedules and a
minimum of 12 time intervals per schedule.
.3
Each schedule shall consist of operator-defined time segments. Each time
segment shall be day(s) of the week and include holidays and starting and
ending times. The system shall provide grouping of days.
Holidays
.1
The System shall support unlimited holidays.
.2
The System shall support holiday type designations.
.3
Holiday groups can be assigned to a Schedule.
Time Zones
.1
The System shall maintain time zones to be used when configuring certain
system objects. A time zone shall adhere to standard international Time
Zone behaviour, and the system shall support all time zones supported by
the Windows OS.
.2
The System shall allow time zones to be assigned to IP devices,
controllers
Events
.1
The System shall support unlimited operator configurable events,
including the scheduling of events, and action-based trigger of events.
.2
The system shall allow an event to be configured to:
.1
Be sortable by event name, date/time, priority, state, and any other
displayable information.
.2
Require or not require operator acknowledgment.
.3
Require or not require a log message to be entered by the system operator
responding to the event.
.4
Display the event activation.
.5
Display an operator-defined text message upon event activation.
.6
Display an operator-defined text message when the event is deactivated.
.7
Be associated with a map so the map automatically displays on the
monitoring station when the event activates.
.8
Allow the operator to associate an audio wave file with the event.
.9
Run reports.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 20
Project ID.:
.19
Integrated E-mail
.1
.20
Import / Export
.1
.21
.22
The e-mail system shall have the ability to interface directly to an SMTPcompliant e-mail system supplied and configured by the user.
The system shall also support importing from Comma Separate Values
(.CSV) files.
Objects
.1
Each object within the System shall be addressed by a unique operatordefined name. Object names shall be unique within object types.
.2
The System shall provide the ability to add description text to each object
definition.
Reports
.1
The System shall provide configurable data reports for database
configuration, historical activity (Journal) and audit tracking. Pre-defined
reports shall be available for download and import into the system.
.2
The System report function shall perform the following:
2014-02-06 BMS Version
.1
Create reports about any object.
.2
Create report templates to simplify report design.
.3
Run reports on demand.
.4
Save report results for sharing between different users of the
application.
.5
Export reports into formats such as PDF, RTF, TXT, and Excel
(XLS).
.6
Specify a query to select and filter the records on which to report.
.7
Specify the data fields to be included in a report.
.8
Specify a design for the report layout.
.9
Design a report form to be used as a layout for headers / footers for
multiple reports.
.10
Access and use system pre-defined report forms.
.11
Select tabular, multi-line, or free form report layouts.
.12
Report on objects linked together with parent / child relations.
.13
Schedule reports to run automatically on a customized schedule.
.14
Send exported report files to the printer or to external recipients via
e-mail.
Project No.:
Section 28 13 00
Electronic Access Control
Page 21
Project ID.:
.23
.24
.25
Dynamic Views
.1
The system shall support a grid format displayable report that will be
usable to display homogeneous lists of objects within the system. This
display shall be configurable both at configuration time and also at run
time.
.2
The Dynamic views shall have the following features:
.1
Real-time updating and display of property values.
.2
The display shall be sortable.
.3
Groupable by any number of columns.
.4
Filterable based on user selectable criteria.
.5
Printable.
.6
Exportable in CSV file formats.
.7
The export file shall be viewable in Excel (Excel must be installed
separately).
.8
The export file shall be able to be emailed.
.9
The user shall be able to add and remove columns from the grid at
runtime to enhance the user experience even if displaying a
preconfigured view.
.10
The view shall be capable of pre-configuration so that repeatable
displays of objects are possible.
.11
The view shall support in-place editing of properties of the object.
.12
Bulk operations shall be performed via multi-selection. The
operations shall consist of (but are not limited to) setting a property
to a value and deletion.
Query
.1
The System shall provide a Query engine to be useful for users with
knowledge of SQL or any other specific query language. It shall allow
users to make requests against data sets with preconfigured relations
between tables. The relations shall reflect the actual relations between
database objects and the user shall be able to put conditions on any
available field in the selected object type and its subordinate objects.
.2
The users shall be able to construct a proper query expression selecting all
available operations, column names, and table names from prompted lists.
The Query feature also shall support complex logic, such as AND/OR.
Video Surveillance Integration / Digital Video
.1
2014-02-06 BMS Version
The System shall provide extensive integration with video recorders/NVR
solutions.
Project No.:
Section 28 13 00
Electronic Access Control
Page 22
Project ID.:
.26
.2
The System server shall be connected to the DVR/NVR during the
configuration process enabling the System to query the DVR/NVR for
setup information.
.3
The System shall use tree controls to drag and drop video servers or
cameras directly into the interface for intuitive and instantly active video
integration.
.4
The System shall provide live camera display during configuration.
.5
The System shall provide the ability to drag cameras into tours.
.6
The System shall provide the ability to identify and automatically
configure all cameras on a controller.
.7
The System shall provide the ability to interface with IP cameras.
ID Badging Subsystem
The System shall include an embedded ID Badging Subsystem. The ID Badging
subsystem shall utilize a common database with and be an integral part of the
System. The ID Badging Subsystem shall provide the ability to capture cardholder
images and design and print user-defined badge layouts. The Badging Subsystem
shall support the following capabilities:
.1
Unlimited number of badge design layouts.
.2
WYSIWYG badge designer.
.3
User-defined selection of background color.
.4
User-defined selection of replacement color or transparency setting.
.5
Edge-detection setting, to aid in replacing only the selected background
and not any matching color within the portrait image.
.6
Capture, import, and display portraits.
.7
Insert, import, and display foreground and background images.
.8
Print two-sided badges.
.9
Encode magnetic data onto personnel badges.
.10
Insert 1D or 2D bar codes.
.11
Insert or replace color and transparent effects for image and background
display.
.12
Support a variety of image formats including .bmp, .jpg, .tiff, and .wmf.
.13
Proper Case (first letter in string is set to uppercase, all other characters set
to lowercase).
.14
Year display (four- or two-digit).
.15
Month display (full or abbreviated name, or numeric).
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 23
Project ID.:
.27
.16
Day display (full or abbreviated name, or week/month numeric).
.17
Hour display (12 or 24 hour format).
.18
Minute display.
System Parameters
.1
.2
.3
.28

16 online readers

64 online inputs

64 online outputs

7,000 credentials

6 simultaneous Clients

1 badging Client
The System shall have a maximum capacity of:
.1
2,500+ online readers
.2
10,000+ online inputs
.3
10,000+ online outputs
.4
500,000 credentials
.5
256 simultaneous Clients
.6
10+ Badging Clients
The System shall support application client connections. The system shall
allow the user to define the number of administration/monitor client
connections.
Watch Tour System
.1
2.4
The Access Control System shall have a minimum capacity of:
Access Control to have capacity to operate a watch tour where the watch
person is recorded badging at any station with alarms triggered in event of
a fail to badge situation.
OPERATION
The SMS shall provide the following operational functionality:
.1
The system shall control access to a designated area.
.2
The system shall validate cardholder credentials by use of downloaded personnel
records, card formats, PINs, biometric enrollment and multiple active cards. The
system shall compare the time, location, and unique credential number of an
attempted entry with information stored in memory.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 24
Project ID.:
.3
Access to a designated area will be validated only when a user’s credential has a
valid number for its facility and the number is valid for the current time and for
the reader where it is used.
.4
The system shall access the hardware that validates the person and monitor the
security of a building by use of controllers, doors, readers, elevators, inputs and
outputs. When access has been validated, a signal to the door locking device shall
be activated to enable alarm-free access at that location.
.5
The system shall configure itself as required by use of an Administrative
application, and shall provide Configuration templates.
.6
The system shall monitor access control activities by use of Monitor Station,
Alarm configuration, and dynamic Graphical Maps display of alarm, door, and
event activity.
.7
The system shall restrict administrative and Monitoring Station activity by use of
Privileges and Authentication (User Password).
.8
The system shall report on various aspects of the system by use of Reports
(canned and configurable). Reports shall be able to export to a printer.
.9
The system shall have the capability to report off-normal security device
conditions both audibly and visually.
.10
The system shall control hardware from the monitoring station by use of Manual
actions, Events, and cause lists.
.11
The system shall provide Record and Data Management by use of Historical
Journal (archive and replay), Full Audit Trail and automated and manual import
and export (data and images.
2.5
EQUIPMENT
.1
[Database] [Alarm Monitoring] [Credential Management] Server
The server shall meet the following minimum requirements:
.1
The server shall have a Processor of:
Quad-Core Intel Xeon [2.2GHz], [32-bit] [64-bit] Processor, [8MB]
Cache, [1066MHz] FSB.
.2
The server shall have Hard Disk Drives of:
Operating System = [160GB].
Database = [160GB].
Drive Speed = [7200] RPM.
.3
The server shall have memory of [4GB RAM (2x2GB) Dual Ranked].
.4
The server shall [dual] Network Adapter Cards: 10/100/1000 MB/sec.
.5
The server shall have a 24x CD-RW/DVD ROM Drive.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 25
Project ID.:
.6
The server shall have an Operating System of:
[Windows 2003 Standard SP2 or Enterprise SP2 32 bit]
[Windows 2008 Standard or Enterprise, 32 bit]
[Windows 2008 R2 Standard or Enterprise, 64 bit]
[Windows 7 Professional or Enterprise 32/64 bit]
.2
.7
The server shall have a dedicated [256 MB] SVGA accelerated video card.
.8
The server shall have a [17”] SVGA (1024 x 768) flat LCD monitor with
true color support.
.9
The server shall have a [PS/2] [USB] style keyboard and mouse.
.10
The server shall have [four] USB [2.0] [3.0] ports.
.11
The server shall have [one] serial port.
.12
[The server shall have an appropriate backup device].
Client Workstation Requirements
The client workstations shall meet the following minimum requirements:
.1
The client workstation shall have an Intel Pentium 4 Dual Core [2.5GHz],
[32-bit] [64-bit] Processor.
.2
The client workstation shall have a Hard Disk Drive of:
Operating System = [160GB]
Drive Speed = [7200] RPM.
.3
The client workstation shall have memory of [4GB RAM].
.4
The client workstation shall have a Network Adapter Card: 10/100/1000
MB/sec.
.5
The client workstation shall have a CD/DVD Combo Drive.
.6
The client workstation shall have an Operating System of:
[Windows 7 Professional or Enterprise 32 bit]
.7
The client workstation shall have a [17”] flat LCD monitor with true color
support.
.8
Stereo Speakers.
.9
The client workstation shall have [six] USB [2.0] [3.0] ports.
.10
The client workstation shall have [one] serial port.
.11
The client workstation shall have [one] parallel port.
.12
The client workstation shall have a [onboard] [dedicated] [128MB]
accelerated video card.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 26
Project ID.:
.13
.3
The client workstation shall have a [PS/2] [USB] style keyboard and
mouse.
Badging Station Requirements
The SMS badging stations shall meet the following minimum requirements:
.4
.1
The same as client workstation.
.2
The badging station shall have a USB camera that supports TWAIN
protocol for photos.
.3
The badging station shall have a PVC printer.
Controllers
The SMS shall support the following controller hardware:
2.6
.1
MAZE FDC Versions 1 and 3
.2
Mercury Controller EP2500
.3
Mercury Controller EP1502
.4
Mercury Controller EP1501
.5
iTDC 2 Door Controller
.6
iTDC 4 Door Controller
MATERIALS
SPEC NOTE: Careful coordinates between control panels & proposed or existing door
hardware is required to ensure electrical & operational compatibility.
.1
Door controls Items and panels
.1
Provide standard "off the shelf" equipment items to form a complete and
operating Access Control system.
.2
Provide as required: Equipment cabinet[s], equipment panels, AC power
strips, power line conditioner, system power supply, junction box, door
control panels, door activation units, electronic supervising master panel,
electronic supervising remote panel[s], system connectors, and system
cables.
.2
Provide system cables including coaxial cable, multiconductor control cable,
audio and AC power cable required.
.3
Number of stations: [___]; [audio only] [audio/video]; [selectable call] [all page];
[door release]; [hardwired] [dial-up (telephone entry)]; vandal proof.
.4
Power supplies: to CAN/ULC-S318 or UL 603.
.5
Connectors and switches: to ORD-C634.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 27
Project ID.:
.6
.7
Intercom
.1
Door stations: durable construction, to suit application, number [___],
[surface] [flush] mount, colour [___].
.2
Interior stations: durable construction, to suit application, number [___]
[surface] [flush] mount colour [___].
.3
[Audio only] [Audio and video].
.4
Video: [Black and white] [colour].
.5
Call type: [all call] [selective call] [with privacy handsets].
Basic System Criteria
.1
.2
Card readers:
.1
Type: [Weigand] [proximity] [multi-class].
.2
Quantity of card readers required: [___].
.3
[MIFARE] [MIFARE DESFire EV1] [iClass SE] technology.
.4
Fitted with tri-state LED indicator light.
.5
Reading distance 50 - 200 mm.
.6
[Optical tamper switch.]
.7
[Near Field Communication (NFC) compatible.]
.8
[PIN number access: [4] [8] [6] [___] user codes.]
.9
[Biometric identification.]
.1
Fingerprint: With false acceptance rate less than [0.005]
[___] % and false rejection rate less than [3] [___] %.
.2
Hand geometry: [[Front] [Side] [All] hand views] [Hand
blood vessel analysis pattern system].
.3
Face recognition.
.4
Retinal scan: False acceptance rate [0] [___] %, False reject
rate [0] [___] %, template record comparison time [___]
seconds.
.5
Voice recognition
Keypads:
.1
Quantity of keypads required: [___].
.2
Fitted with tri-state LED indicator light.
.3
Combination card readers and keypad:
.1
2014-02-06 BMS Version
Quantity of units required: [___].
Project No.:
Section 28 13 00
Electronic Access Control
Page 28
Project ID.:
.4
.3
.2
[MIFARE] [MIFARE DESFire EV1] [iClass SE]
technology.
.3
Fitted with tri-state LED indicator light.
.4
Reading range: [50 mm (2")] [75 mm (3")] [___].
Cards: [ISO Style] credit card size, sealed and highly resistant to
normal handling and weather, [fitted with vertical slot punched
hole].
.1
Quantity of cards required: [___].
.2
Guaranteed for [5] years against all defects and protected
against:
.1
Magnetic encoded cards.
.2
Metal objects including coins and keys.
.3
Retail shoplifting detection equipment.
.4
Communication equipment
Coding:
.1
Designed with highly secure codification of card
information.
.2
Card life: minimum period of [10] [___] years for cards in
same family.
.3
Use [one] series of cards for all areas protected by access
control system
.5
Quantity of alarm monitoring points required: [___].
.6
Quantity of outputs required: [___].
.7
Number of access levels (assigned to cardholders): [___].
.8
Schedules:
.9
.1
Number of date schedules required: [100] [___].
.2
Number of holiday schedules required: [180] [___].
.3
Allow full schedule description label of [30] alphanumeric
characters.
.4
Include [4] time intervals/day.
Groups:
.1
Design system to include possibility of group association in
following categories:
.1
2014-02-06 BMS Version
Controller groups: [100] [___].
Project No.:
Section 28 13 00
Electronic Access Control
Page 29
Project ID.:
.2
.8
.2
Door groups: [100] [___].
.3
Relay groups: [100] [___].
.4
Input groups: [100] [___].
.5
Access groups: [100] [___].
Design groups with fully customizable field of [30]
alphanumeric characters for easy renaming of associated
group.
.10
Operating system: Windows [7] or Windows Server [2008] or
[Linux].
.11
Connection: [local] [remote dial up [multisite]] [networked] [___].
.12
Language: [English] [French] [Bilingual].
.13
Off Site Monitoring of alarm conditions.
System Accessories:
.1
Door strike: [surface mounted,] [latch] [monitor] [current], UL approved
complete with mounting hardware
.2
Magnetic lock: holding force [350] [700] [1200] [1500] [___] lbs.,
[surface mounted], UL approved complete with mounting hardware.
.3
Request to exit motion detector device.
.4
2014-02-06 BMS Version
.1
Infrared detection.
.2
Continuous low-voltage operation.
.3
Fitted with indicator light.
.4
Integrated with local audio alarm (electronic buzzer).
.5
Adjustable coverage.
Request to exit motion push button device:
.1
Heavy duty assembly.
.2
Size: [square, [50 x 50] mm] [___].
.3
Sturdy and attractive finishing plate with security screws
.5
Pull Station Power interrupt.
.6
Power Supplies:
.1
Continuous low-voltage operation output.
.2
Equipped with secondary protection for each output.
.3
Individual outputs for connection of devices.
.4
AC power failure output.
Project No.:
Section 28 13 00
Electronic Access Control
Page 30
Project ID.:
.7
.9
.5
DC power failure output and low battery output.
.6
Fitted with tamper contact.
.7
Wall mounted cabinet with locked door complete with [2]
keys.
Voltage: [12] [24] volt DC.
Burglar alarm systems: to ORD-C1023.
SPEC NOTE: Access Control processor should be served from TVSS protected UPS power
supply.
SPEC NOTE: Access Control field door panels to provide power supply for door locks.
3
Execution
3.1
INSTALLATION
.1
Install system and components in accordance with manufacturer's written
installation instructions to locations, heights and surfaces shown on reviewed
shop drawings.
.2
Install panels, system and components secure to walls, ceilings or other substrates.
.3
Install required boxes in inconspicuous accessible locations.
.4
Conceal conduit and wiring.
3.2
TRAINING
.1
3.3
The Contractor shall provide a competent trainer who has extensive experience on
the installed systems and in delivering training to provide the instruction. As an
alternative, the Contractor may propose the use of factory training personnel and
coordinate the number of personnel to be trained.
TESTING
.1
The software shall be entered into the SMS computer systems and debugged. The
Contractor shall be responsible for documenting and entering the initial database
into the system. The Contractor shall provide the necessary blank forms with
instructions to fill in all the required data information that will make up the
database. The database shall then be reviewed by the Contractor and entered into
the system. Prior to full operation, a complete demonstration of the computer
real-time functions shall be performed. A printed validation log shall be provided
as proof of operation for each software application package. In addition, a point
utilization report shall be furnished listing each point, the associated programs
utilizing that point as an input or output and the programs which that point
initiates.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 31
Project ID.:
.2
Upon satisfactory on-line operation of the system software, the entire installation
including all subsystems shall be inspected. The Contractor shall perform all tests,
furnish all test equipment and consumable supplies necessary and perform any
work as required to establish performance levels for the system in accordance
with the specifications. Each device shall be tested as a working component of the
completed system. All system controls shall be inspected for proper operation and
response.
.3
Tests shall demonstrate the response time and display format of each different
type of input sensor and output control device. Response time shall be measured
with the system functioning at full capacity. Computer operation shall be tested
with the complete data file.
.4
The Contractor shall maintain a complete log of all inspections and tests. Upon
final completion of system tests, a copy of the log records shall be submitted as
part of the as-built documentation.
3.4
INSTALLATION: BURGLAR ALARM SYSTEM
.1
Install burglar alarm system units and components in accordance with
CAN/ULC-S310 or UL 1641.
.2
Provide tamperproof unobtrusive dual gang receptacle back box with stainless
steel cover plate where door release items installed in areas with suspended
ceiling, fixed tile, plaster, or concrete walls, and/or metal door frames.
.3
Fully enclose external cables in conduit or flexible protective armor, from
activating unit location's enclosure receptacle back box to and above ceiling wall
mounted junction box[es].
.4
Provide tamperproof attachments for each activation unit cover plate to receptacle
back box.
.5
Enclose in conduit or flexible protective armor external cables for associated
junction box to remaining system locations, from junction box to above ceiling
mounted cable duct[s] or master conduit route[s].
.6
Securely fasten all components to wall, ceiling, or other substrate or structure.
3.5
INSTALLATION: SECURITY ACCESS
.1
Install security access systems and components in accordance with
[CAN/ULC-S302] [CAN/ULC-S310] [UL 681] [UL 1641] [UL 681].
.2
Install components in accordance with manufacturer's written installation
instructions to locations, heights and surfaces shown on reviewed shop drawings.
.3
Install components secure to walls, ceilings or other substrates.
.4
Install required boxes in inconspicuous accessible locations.
.5
Conceal conduit and wiring.
2014-02-06 BMS Version
Project No.:
Section 28 13 00
Electronic Access Control
Page 32
Project ID.:
3.6
VERIFICATION
.1
.2
.3
Perform verification inspections and test in the presence of [Engineer]
[Consultant].
.1
Provide all necessary tools, ladders and equipment.
.2
Ensure appropriate subcontractors [, and] manufacturer's representatives
[and security specialists] are present for verification.
Measure and record, control (and/or voice) carrier levels of every System channel
at each of following points in the system:
.1
Door located actuating devices.
.2
Door control panel functions.
.3
Electronic supervisory control units inputs and outputs.
.4
Distribution system input and output.
.5
Telephone system interface input and output.
Performance testing.
.1
.2
.3
Test procedure: perform test on a "go-no-go" basis.
.1
Make only operator adjustments required to show proof of
performance.
.2
Test to demonstrate and verify that installed System complies with
installation and technical requirements of this specification under
operating conditions.
.3
Test results to be evaluated by [Engineer] [Consultant] as either
acceptable or unacceptable using following procedures
Documentation review
.1
This review will determine if information provided is sufficient to
meet requirements of this specification.
.2
Provide for review all System manuals, as installed drawings, pretest form[s], antenna radiation pattern[s], equipment cabinet
pictorial[s], antenna pictorial, antenna mount pictorial, video and
audio equipment details.
Mechanical inspection
.1
2014-02-06 BMS Version
[Engineer] [Consultant] Owner’s representatives and Contractor to
tour all areas to insure that all Systems and Subsystems are
installed in place for proof of performance testing.
Project No.:
Section 28 13 00
Electronic Access Control
Page 33
Project ID.:
.2
Take system inventory at this time. Verify following items before
beginning proof of performance test[s]:
.1
All electrical power circuits designated for system
equipment are properly labeled, wired, phased, protected
and grounded.
.2
Conductor ends are protected by heat shrink wrap; audio
spade lugs, barrier strips and punch blocks are used.
.3
Dust, debris, solder splatter, etc. are cleaned and removed
from site.
.4
All equipment is properly labelled.
.5
All equipment identified in System's equipment list[s] are
in place and properly installed.
.6
Each lightning and System ground method are installed in
accordance with manufacturer's instructions and this
specification.
3.7
[SYSTEM STARTUP]
3.8
CLEANING
.1
3.9
Waste Management
PROTECTION
.1
3.10
Provide physical protection for detection devices & controls from construction dust &
damage to ensure complete new working systems at final acceptance.
MAINTENANCE
.1
The Contractor shall offer a Support Agreement in order for Technical Support
Specialists to reactively troubleshoot system problems.
.2
As part of the agreement, access to patches and software release updates shall be
provided.
END OF SECTION
2014-02-06 BMS Version