Your Free Consultant

HIRSCH SECURITY ACCESS SYSTEM – VELOCITY SYSTEM OVERVIEW

November 15, 2010

Here is a good overview of Hirsch Electronics Security System…

 

SECTION 13705

 

SECURITY ACCESS SYSTEM – VELOCITY SYSTEM

 

 

 

Display hidden notes to specifier by using “Tools”/”Options”/”View”/”Hidden Text”.

** NOTE TO SPECIFIER ** Hirsch Electronics; door control, alarm monitoring, video, photo badging, graphics and database management.

This section is based on the products of Hirsch Electronics, which is located at:

1900-B Carnegie Ave.
Santa Ana, CA 92705
Toll Free Tel: (888) 809-8880
Tel: (949) 250-8888
Fax: (949) 250-7372
Email: marketing@hirschelectronics.com
Web: www.hirschelectronics.com

[ Click Here ] for additional information.

Hirsch products include Velocity™ Security Management System, high security controllers, and a line of intelligent keypads and readers: ScramblePad®, ScrambleProx®, ScrambleSmart™ and BioSmart™.

Hirsch has earned numerous industry awards for their integration of door control, alarm monitoring, video, photo badging, graphics and database management. From a single door application to an enterprise-class system connecting hundreds of doors for thousands of users, Hirsch is the preferred choice for applications requiring high security, reliability and interoperability.

Security Management Software: Velocity™ Hirsch Management Software for Access Control, Graphical Guard Stations, and Photo Badging.

Access Control Systems: DIGI*TRAC® High Security Access Control & Management.

  1. GENERAL

    1. SECTION INCLUDES

** NOTE TO SPECIFIER ** Delete items below not required for project.

      1. Security access system, Velocity by Hirsh Electronics, including the following:

        1. Server hardware and software.

        2. Application software.

        3. Intrusion detection devices.

        4. Security access devices.

        5. Access control, relay control, and alarm monitoring controllers.

    2. RELATED SECTIONS

** NOTE TO SPECIFIER ** Delete any sections below not relevant to this project; add others as required.

      1. Section 16050 – Basic Electrical Materials and Methods.

    2. REFERENCES

** NOTE TO SPECIFIER ** Delete references from the list below that are not actually required by the text of the edited section.

      1. NFPA 70 – National Electrical Code.

      2. UL294 – Standard for Access Control Systems.

      3. NFPA 72 – National Fire Alarm Code.

      4. NFPA 101 – Life Safety Code.

    2. REGULATORY REQUIREMENTS

      1. System shall be UL-Listed.

    3. SYSTEM DESCRIPTION

      1. The Hirsch Electronics “VELOCITY Version 3.0 Security Management System shall be a modular and network capable access control and intrusion detection system. The Security Management System shall have the ability of handling corporations with multiple remote sites, controlled access with various reader technologies supported simultaneously, alarm monitoring with text and graphics based annunciation, Photo Call-Up, Photo ID Badging, DVR and CCTV switcher control that allows for easy expansion or modification of readers, inputs, and outputs. The system control at the central computer location shall be under a single software program control, shall provide full integration of all components, and shall be alterable at any time, depending upon the facility requirements. Reconfiguration shall be accomplished on-line through system programming, without hardware changes.

      2. The system shall support both manual and automatic responses to alarms entering the system. Each alarm shall be capable of initiating a number of different actions, such as camera switching, activation of remote devices, email of alarm/event, text page of alarm/event, Threat Level change, and door control.

      3. Access control functions shall include, validation based on time of day, day of week, holiday scheduling, automatic or manual retrieval of cardholder photographs, and access validation based on positive verification of card, card/PIN, and PIN.

      4. The VELOCITY System shall interface to the CCTV matrix control system through a serial software interface, simulating alarm inputs. The CCTV system shall be programmed to respond to the alarm input, switching the appropriate camera(s) to the appropriate monitor/s and/or recording devices. All control of camera selection, position, zoom, focus, iris, pre-position, etc. shall be controlled by the CCTV system’s keyboard/joystick controls or the Velocity computer keyboard and mouse. Advanced switcher programming shall be performed through the switcher and associated keyboard or software programming interface.

      5. The VELOCITY System shall interface to the DVR system through an API software interface. The DVR system shall be programmed to respond to the alarm inputs through Velocity’s Triggers/Actions Manager. In response to an alarm, the DVR shall record video as programmed, including: Pre-Alarm, Alarm Duration, Post Alarm, and Frames per second as defined for that camera. All control of position, zoom, focus, and iris shall be controlled by the DVR system’s keyboard/joystick controls or the Velocity on-screen PTZ controls. Initial DVR setup and Advanced programming shall be performed through the DVR’s configuration software programming interface.

      6. Utilizing assigned passwords, it shall be possible to define the levels of system operation for each individual Operator. Operator Actions range from basic monitoring to full control of the system databases.

      7. The system programming shall be user-friendly Windows environment (use conventional “Title Bar”, “Menu Bar”, “Tool Bar” and “Status Bar”) and allow mouse control of key functions. The programming shall be MENU driven and include on-line “Documentation”, “Help” or “Tutorial” information. The software shall utilize combo boxes for previously entered system-required data where applicable.

      8. system shall provide supervised alarm point monitoring. Upon recognition of an alarm, the system shall be capable of displaying alarm information in text format in a dedicated Alarm Viewer, real-time status in a Status Viewer, on a graphic floor plan, initiate alarm recording on a DVR, switching CCTV cameras, email an alarm notification to one or more people, and send a text page to a cell phone or display pager that are associated with the alarm point. The system shall be capable of arming or disarming alarm points both manually and automatically, by time of day, and day of week.

      9. The method of communication from remote locations to the central components shall be transparent to the user.

      10. After installation, the Owner shall be able to perform hardware configuration changes as desired without the services of the manufacturer.

      11. Equipment repair shall be able to be accomplished on site, by module replacement, utilizing spare components.

      12. All controller components shall utilize “Distributed-Processing” concepts. The distributed processing shall include the ability to down-load operating parameters to any field panel, thus allowing the field panel to provide full operating functions independent of any other system component.

      13. The system shall be capable of utilizing the existing LAN / WAN connecting the buildings or a dedicated security Ethernet network for Hirsch DIGI*TRAC Controller and Velocity Client communications. Install Hirsch SNIB2 communications interface in each controller to communicate to the controllers via 10/100 Mbps, 128 bit AES encrypted Ethernet.

      14. The Controllers shall utilize Version 7.4 or later Flash downloadable CCM (Command and Control Modules) firmware.

      15. Upgrade CCM Firmware in existing controllers as required.

** NOTE TO SPECIFIER ** Delete if not required.

    1. ALTERNATES:

      1. Alternate Item #1: Provide a complete photo ID Badging system, including: Pan/Tilt/Zoom camera with Synchronized Flash, Tripod, and backdrop (Hirsch Model IDCAMKIT; Ultra Magic Card RIO Printer (Hirsch IDP-MLR); Printer Rolls (Hirsch Model IDP-ML5-PR).

      2. Alternate Item #2: Provide a Dual Monitor PC Card (Hirsch Model DMC) and an additional 17 inches (423 mm) Flat Panel Monitor (Hirsch Model HMS-M17FP).

      3. Alternate Item #3: Provide as an option a Fault-Tolerant Server Computer, Windows Server 2003 R2 operating system, SQL Server 2005 database, 17″ Flat Panel Monitor (Hirsch Model HMS-L2D-3-17FP).

    2. SUBMITTALS

      1. Submit under provisions of Section 01300.

      2. Manufacturer’s Data:

        1. Submit three (3) copies of:

          1. Product Data Sheets.

          2. Installation Instructions.

        2. Authorized Dealer Certificate and Certified Training Certificates of installers who will be working on this project.

      3. Shop Drawings:

        1. Submit three (3) copies and digitally in AutoCAD 14 or later format on a CD (3 copies), shop drawings, including:

          1. Layout of equipment on supplied AutoCAD drawings.

          2. Security Console elevation drawings.

          3. Field Controller equipment location wall layouts, including size requirements.

          4. Detailed wiring diagrams of Field Controllers, Door Details, and head-end devices.

          5. Load calculations of all security equipment for proper sizing of electrical provided by the customer and standby emergency generator circuits.

** NOTE TO SPECIFIER ** Delete selection samples if colors have already been selected.

      1. Selection Samples: For each finish product specified, two complete sets of color chips representing manufacturer’s full range of available colors and patterns.

      2. Verification Samples: For each finish product specified, two samples, minimum size 6 inches (150 mm) square, representing actual product, color, and patterns.

      3. As-Built Drawings: Update Shop Drawings to create final As-Built Drawings. Submit 3 copies and digitally in AutoCAD 14 or later format on a CD (3 copies).

      4. Operation Data: Include three (3) copies of the software Administrator and Operator Manuals.

      5. Maintenance Data: Include maintenance and repair procedures.

    2. QUALITY ASSURANCE

      1. Manufacturer: The access control system shall be from a single-source manufacturer that specializes in intrusion detection and access control systems with a minimum of 5 years experience.

      2. Installer: Company specializing in intrusion detection and access control systems with a minimum of three years experience on systems of similar size and scope. Technicians working on project must have been certified on the hardware and software used for this project.

** NOTE TO SPECIFIER ** Include a mock-up if the project size and/or quality warrant taking such a precaution. The following is one example of how a mock-up on a large project might be specified. When deciding on the extent of the mock-up, consider all the major different types of work on the project.

      1. Mock-Up: Provide a mock-up for evaluation of surface preparation techniques and application workmanship.

        1. Finish areas designated by Architect.

        2. Do not proceed with remaining work until workmanship, color, and sheen are approved by Architect.

        3. Refinish mock-up area as required to produce acceptable work.

    2. DELIVERY, STORAGE, AND HANDLING

      1. Owner will provide, on-site, a secure, dry, locked storage area for all equipment delivered under this scope of work.

      2. Store products in manufacturer’s unopened packaging until ready for installation.

      3. Store and dispose of solvent-based materials, and materials used with solvent-based materials, in accordance with requirements of local authorities having jurisdiction.

    3. PROJECT CONDITIONS

      1. Maintain environmental conditions (temperature, humidity, and ventilation) within limits recommended by manufacturer for optimum results. Do not install products under environmental conditions outside manufacturer’s absolute limits.

    4. WARRANTY AND SERVICE AGREEMENT

      1. All equipment, materials, and labor shall be guaranteed for a period of 24 months from the date of final acceptance by the Owner.

      2. Provide any software maintenance updates or upgrades at no additional cost to the Owner for this period.

      3. Perform two (2) scheduled preventative maintenance site visits per year during the warranty period.

      4. Response Times – Normal business hours shall be 7 AM to 5 PM Monday through Friday. Calls for service before noon shall be responded to on-site before the end of the day. Calls after noon shall be responded to on-site by noon the following business day.

      5. Provide extra costs for time outside of normal business hours if the Owner requires emergency service.

      6. Submit an all-inclusive Annual Maintenance Agreement cost for years 3 and 4, including two (2) preventative maintenance sites visits per year.

      7. Submit normal and after hours labor costs and typical costs for equipment for items not covered under the Warranty, like: Acts of God, vandalism, misuse.

    5. EXTRA MATERIALS

      1. Provide one (1) each of the following Hirsch Electronics components to serve as system spares:

        1. SNIB2 – Secure Network Interface Board (as required).

        2. MRIB – MATCH Reader Interface Board (as required).

        3. DS47L (as required)

        4. DS47L-SPX (as required)

        5. Card Reader (as required)

  2. PRODUCTS

    1. MANUFACTURERS

      1. Acceptable Manufacturer: Hirsch Electronics, which is located at: 1900-B Carnegie Ave. ; Santa Ana, CA 92705; Toll Free Tel: 888-809-8880; Tel: 949-250-8888; Email: request info (marketing@hirschelectronics.com); Web: www.hirschelectronics.com

** NOTE TO SPECIFIER ** Delete one of the following two paragraphs; coordinate with requirements of Division 1 section on product options and substitutions.

      1. Substitutions: Not permitted.

      2. Requests for substitutions will be considered in accordance with provisions of Section 01600.

    2. BASIC CENTRAL SYSTEM COMPONENTS

** NOTE TO SPECIFIER ** The computer specifications are the minimum standards for a basic system. If the server will be running the full version of SQL Server, used as a Client, running badging and graphics, and/or be interfacing to other systems, additional processing power, memory, hard disk size, speed and type should be used. In addition, if the system includes a large number of Client computers, a large number of controllers, and/or a large number of users, additional server power is recommended. It is recommended that as much computer power be purchased as possible above the minimum specifications to ensure long term compatibility with enhancements to the Operating System, Velocity Application, and additional functionality required of the server. Contact Hirsch for recommendations for your specific application.

      1. Security Management System: Hirsch Electronics Corporation, Velocity Security Management System, model VEL (Velocity Server plus unlimited remote clients).

      2. Central Processing Unit Computer Specifications:

        1. The software shall operate on a Dell or equal personal computer. The requirements for the computer, rated to the size of the system, are as follows:

      3. Central Processing Unit (CPU):

        1. The computer CPU shall be type Pentium 4, 2GHz/533MHz or greater.

      4. Random Access Memory (RAM):

        1. The computer shall have a minimum of 1GB RAM for the Server (plus 40MB per active client) and 512 MB RAM for Clients and Single User Workstation running on Windows XP Professional SP2.

      5. Disk Drives:

        1. The computer shall have a 40 GB IDE, SATA or SCSI hard disk drive minimum, a 3.5″ floppy disk drive, and CD-ROM (CD-R on the Server recommended).

      6. Monitor:

        1. The computer shall have a 17″ Flat Panel Monitor, XGA color.

      7. Mouse:

        1. 2 button bus type.

      8. Keyboard:

        1. The computer shall have a standard 101-keyboard layout and IBM-compatible.

      9. Modem:

        1. The modem shall be a 56K internal modem with PCAnywhere 12 Remote Control Software for the server computer. The owner will provide a dedicated voice-grade phone line at the Head-End Server location.

      10. Serial Ports:

** NOTE TO SPECIFIER ** Increase the number of serial ports as required to meet the specific requirements of the application.

        1. Provide 2 serial ports.

      2. Parallel Ports:

** NOTE TO SPECIFIER ** Increase the number of parallel ports as required to meet the specific requirements of the application.

        1. Provide 1 parallel port.

      2. L. Ethernet Port:

        1. Provide 1 10/100/1000 Cat5 Ethernet port (onboard or separate card)

      3. Sound Card and Speakers:

        1. 1. Provide audio output (onboard or separate sound card) and speakers.

      4. Operating System:

        1. The VELOCITY Server computer shall operate under Windows Server 2003 SP1 or R2 and the Single User Server or Client shall operate under Windows XP Professional SP2.

      5. Database:

        1. The VELOCITY Server shall have Microsoft SQL Server 2005 Express Database included and loaded with the application. The system shall optionally run on MS SQL Server 2005.

      6. Printers: (as required for each workstation)

        1. Report Printer – The computer shall have one parallel or USB printer port, and corresponding printer, Hirsch Model HMS-PLBW Laser Printer, and printer drivers for Windows XP Pro SP2.

        2. Badging Printer – The computer shall have one parallel or USB printer port, and corresponding printer Hirsch ID Badge Printer, Hirsch Model IDP-MLR, and printer drivers for Windows XP Pro SP2.

        3. Alarm and Event Printer – The computer shall have one parallel or USB printer port, and corresponding printer, Hirsch Model PR-1 Dot Matrix Printer, and printer drivers for Windows XP Pro SP2.

      7. UPS:

        1. The UPS (Uninterruptible Power Supply) for the Server, Hirsch Model UPS-HMS, and Client, Hirsch Model UPS-HMS, shall provide for 20 minutes of continued operation in the event of an AC Power Failure.

      8. Tape Drive – Internal on Server:

        1. The tape drive shall be a 20/40 GB Travan, Model Hirsch HMS-TBI. Provide 12 Blank Tapes.

      9. Tape Drive Software

        1. The tape drive software shall be Symantec Backup Executive.

      10. Communications Interface To Field Controllers Supported:

        1. RS-232.

        2. RS-485.

        3. TCP/IP.

        4. Dial Up.

      11. Control Panel Specifications:

        1. The control panel shall incorporate microprocessor-based, digital technology, using high speed processing for maximum reliability.

      12. tributed Intelligence:

        1. The system shall use distributed intelligence architecture, with controllers operating independently of one another.

        2. Regionalized functions for all controllers connected to an XBox communications loop shall include: Use Count, Absentee Limit, Temporary Days, Passback, and Input/Output linking and shall not require the host to be online for processing and control.

      13. Stand Alone Operation:

        1. All database information required for stand-alone operation shall be stored at the control panel level. All decision-making shall be performed at the control panel, eliminating the need for degraded mode operation.

        2. Proprietary software programs and control logic information used to coordinate and drive system hardware shall be stored in Flash Downloadable Read Only Memory.

      14. XML Writer Application:

        1. The system shall support as standard sending any or all event and alarm transaction events out of a selected port in a standard XML format.

        2. A Time Zone may be defined to limit when this data is exported.

        3. Multiple XML Writers may be defined and run concurrently for different applications.

      15. MS Message Queue Application:

        1. The system shall support as standard sending any or all event and alarm transaction events in a standard XML format to a Microsoft Message Queue.

        2. A Time Zone may be defined to limit when this data is sent to the queue.

        3. Multiple MS Message Queues may be defined and run concurrently for different applications.

    2. SYSTEM CONFIGURATION

      1. The head-end shall support one (1) Server Computer that may optionally be used as a full functioning Client. The system shall support unlimited remote Client computers will full system functionality. The unlimited client capability will be inherent to the software and will not require additional licensing by the manufacturer.

      2. The server software shall support Cold Redundant, Warm Redundant, Hot Redundant, and Clustered server environments.

      3. During installation, support for a split SQL Server Database server and Application/Communications server shall be available.

      4. Computer to Controller Communication Protocols:

        1. Communications between the computer and the controller shall be accomplished by Scramble*Net Communications and shall be encrypted using a 64-bit cipher feedback method (HES – Hirsch Encryption Standard). The encryption shall be full time and not require any programming or key setting to operate.

        2. The system shall utilize RS232 up to 50′ for hardwired applications.

        3. The system shall utilize RS485 up to 4000′ (4-wire hardwired). Longer distances are allowed with a communications multiplexer / amplifier (Hirsch Model NET*MUX4), if applicable.

        4. The system shall utilize TCP/IP for communicating over dedicated or shared Ethernet networks. For 10/100 Ethernet communications to the controller, install SNIB2 128 Bit AES Encrypted communications interface board in each controller.

        5. All of the communications protocols shall be supported simultaneously on the system.

      5. Host Computer to Controller Communication Transmission Methods/Hardware:

        1. Communications between the computer and the controller shall be able to use any or all of the following methods:

          1. Hardwired.

          2. Leased line modem.

          3. Fiber Optic.

          4. Microwave.

          5. RF.

          6. Ethernet 10/100.

          7. Dial-Up modem.

      6. Proprietary Network Interface Hardware:

        1. The controller shall be interfaced to an industry standard personal computer running proprietary software with the addition of an opto-isolated network communications interface board (Hirsch Model: SNIB). The Scramble Net Interface Board will accept RS232 or RS485 communications interface. Each board is uniquely addressable through on-board dipswitch settings and has an adjustable baud rate from 1200 – 19,200. The board shall be mounted in the controller cabinet and connect to the controller board via an expansion bus cable.

** NOTE TO SPECIFIER ** Delete if not required.

        1. Optionally, the enhanced SNIB2 communications interface board may be installed for 10/100 Ethernet, 128 Bit AES encrypted communications input to the controller. Downstream RS485 hardwired communications to controllers daisy chained off the “master” controller on any communications port can communicate up to 115 K Baud. The SNIB2 board firmware will be Flash Downloadable to accommodate any future communication enhancements.

      2. Maximum System Wide Capacities:

        1. The following shall be the maximum system wide capacities. These capacities will be inherent to the software and do not require additional licensing by the manufacturer. The actual number shall be dependent upon the mix of controllers that make up the system:

          1. Doors: Unlimited.

          2. Supervised Alarm Inputs: Unlimited.

          3. Control Relays: Unlimited.

          4. Controllers: Unlimited.

          5. Users: Unlimited.

    2. SYSTEM SOFTWARE

      1. General layout of the software “Windows” will include but not be limited to:

        1. Main Menu Bar shall be used to access all Velocity Functions from a standard pull down menu method.

        2. Tool Bar ICONS shall be used to access all common Velocity Functions with a single mouse click.

        3. Customizable Graphical User Interface shall allow for configuring the screens in a variety of layouts. Layouts for each window include: Docked to the Top, Bottom, Left, and Right; Floating; Child – Minimized, Maximized, Restored. Each Operator shall have their own unique layout for available options. If dual-monitors are used, the Customizable GUI shall apply to both monitors. It shall be possible to restore factory defaults for each user with a single action.

        4. Tool Tips describing the feature(s) that the selected item represent, will be displayed in small “bubbles” underneath the selected item, field caption or other component. These tool tips shall be user definable.

        5. The Administration Console shall use the familiar Microsoft Explorer metaphor with a tree of folders in the left pane and details of selected folders in the right pane. The left pane shall include the following main components: Main Administration Console, Velocity Configuration, DIGI*TRAC Configuration, and Interface Configuration.

          1. The Main Administration Console shall include:

            1. Alarm Viewer.

            2. Badge and Graphics Designer.

            3. Customization Manager.

            4. Enrollment Manager.

            5. Event Viewer.

            6. Graphics.

            7. Report Manager.

            8. Status Viewer.

            9. SQL Manager.

            10. Velocity Scheduling Agent

            11. Video Explorer.

            12. Who’s Inside

            13. CCTV Camera Viewer.

          2. The Velocity Configuration Module shall include:

            1. Person Templates

            2. Credential Templates.

            3. Time Zones.

            4. Holidays.

            5. Door Groups.

            6. Function Groups.

            7. Operators.

            8. Roles

            9. Command Sets.

            10. Workstations.

            11. Alarm Responses.

          3. The DIGI*TRAC Configuration Module shall contain:

            1. Add either an S*NET, X*NET, or Dial-Up communications port, either serial or TCP/IP.

            2. Add XBOX

            3. Add DIGI*TRAC Controller.

            4. Import New Controller

            5. Add Dial-Up Location and Modem Pool Settings.

            6. Doors, Readers, Inputs, Outputs, Expansion Inputs, Expansion Outputs.

          4. The Interface Configuration Module shall define the parameters for communicating to a CCTV switcher, Serial Port Redirector, E-mail Notification of Alarms, Message Queue writers, Central Station Interfaces (optional and sold separately) and DVR integration.

        6. Dialog Boxes will provide a means for entering information into fields and displaying information from the System Software database.

      2. Workstation Customization:

        1. Each Operator may customize the Graphical User Interface display location and size of the software components. After Logging Off and then Logging In again, the User Interface will display the software components exactly as the Operator left them when they Logged Off.

        2. Alarm Viewer will bring the “Alarm Viewer Window” forward on new alarm(s) while you are in other Velocity windows.

      3. Time Zones:

        1. Time Zones define periods during which readers, cards, codes, alarm inputs, doors or other system features are active or inactive. Basic configuration parameters shall “ask” the Operator to define “when” the user is enabling (or disabling) a specific feature. In addition to Monday-Sunday, there shall be one day of the week called Holiday. When selected, there will be 4 Holiday Schedules that determine if the Holiday is to be followed for this Time Zone. There shall be 64 Standard Time Zones, 64 Master Time Zones, and 20 Grand Master Time Zones.

      4. Holidays:

        1. Holidays are used within the system for the purpose of defining if a Time Zone is to be followed on a defined Holiday. Each Time Zone has up to 4 Holiday schedules. There are 366 user definable Holidays this year and 366 days next year. It shall be possible for the Operator to “Make the rest of Today a Holiday”.

      5. Door Groups:

        1. Door Groups shall allow the user to establish groups of readers, each with its own unique Time Zone, at a facility for the purpose of granting or denying access to Credentials. Door Groups are assigned to Credential Templates, and people being added to the system take on the Door Group of the Credential Template selected during the enrollment process. A new Door Group may be defined when adding a Credential or Credential Template without having to exit and re-enter the Credential function for that Person.

        2. The Door Group application shall allow the user to view any existing Door Group listed in the dialog box. A user, with proper authority, shall be able to modify, add, or delete a Door Group from the System Software.

        3. More than one Door Group may be added to a Credential as long as there is no overlap of a controller in a door group already added to the Credential.

        4. Door Groups may be combined into Master Door Groups, which can then be added to a Credential.

      6. Function Groups:

        1. Credentials can be assigned to perform a single User Function, like Momentary Access, or multiple functions like Momentary Access in one controller and Control Trigger Function in a relay controller for Elevator Access. When multiple User Functions are required by a Person, a Function Group may be defined and associated with one or more credentials. The Function Group requires a ScramblePad keypad to be used, where the Person’s base Credential PIN number is entered, followed by an * (Asterisk), followed by a one or two digit Extension digit, which defines which User Function will be issued for which Control Zone. This allows for a single person to perform multiple User Functions like: Unlock Door, Relock Door, Change Threat Level, Mask Alarm Inputs, Lock Down Doors.

      7. Credential Templates:

        1. A Credential Template can be used when adding Credentials to people. The Credential will take on the properties of the Credential Template selected. This will minimize the number of keystrokes and time required to add a Credential to a person. The Credential Template properties include: Credential Name; Badge Template; Activation and Expiration Date and Time; ID Format; Card Type; Code Length; Duress Digit; Credential Function and Category; Door Group, Multiple Door Groups, or Function Group; Threat Authority; 2 Person Rule options; Use Count, Day Limit, and Absentee Limits; Apply Credential Management Globally; Tag, Alert, Disable Credential; Issue Number; Status; Executive Override for Passback; Special Needs Access Extension. Credential Templates may be linked, whereby any User Credentials that are added with a Linked Credential Template can be group edited by editing the definition of the Linked Credential Template. A User’s credential may be unlinked and customized or it can be linked to another Credential Template.

      8. Command Sets:

        1. A Command Set defines an action or actions to be sent to a controller or controllers. Command Sets can include: Unlock and Relock a Door; Lock Down and Release a Lock Down on one or more doors; make the rest of today a Holiday; Mask all Interior Alarm Points; change the facility Threat Level; Forgive All Passback. Once defined, a Command Set can be executed from the Command Set Window, or from a Graphic Floor plan ICON, if defined. There shall be an unlimited number of Command Sets available to be defined. Command sets shall be defined with pick lists and shall be restrictable by Operator Group and Workstation.

      9. Roles

        1. Each Operator is assigned one or more Roles that defines at each authorized workstation, what that Operator is allowed to see and do, including:

          1. Add-Ins

          2. Application Permissions

          3. Cameras

          4. Command Sets

          5. Credential Templates

          6. DIGI*TRAC Hardware

          7. Door Groups

          8. Event Viewer Filters

          9. Function Groups

          10. Graphics

          11. Person Groups

          12. Person Templates

          13. Reports

          14. Status Viewer Groups

          15. Video Explorer Groups

        2. Alarm and Event Routing can be defined by Operator Role. Specific alarms and events can be routed by Time Zone to Operators to allow for only those Operators needing to see certain alarms and events can see them.

      10. Operator:

        1. Operators entered into the system shall take on the properties of the Role/s to which they are assigned. If the Operator is already defined in the Operating System, the “Find” feature can be used to select this Operator for use in Velocity.

      11. Velocity Scheduling Agent

        1. There shall be a Velocity Scheduling Agent that allows functions to be performed on an as needed basis, like activating and deactivating credentials. It can also schedule Tasks like: Synchronize Controller Clocks; Run Historical Log Archiver; Print Reports; E-mail Reports; Import/Export User Data; Execute third party applications; Dial-Up remote sites; Perform Database Maintenance (backups), and Run Command Sets on a Daily, Weekly, Monthly basis.

      12. SQL Database Manager:

        1. The SQL Database Manager shall launch SQL Server Management Studio Express for manual backups and restoration of backups when running SQL Server 2005 Express.

      13. Diagnostic Window:

        1. There shall be a Diagnostic Window available to aid in system diagnostics / troubleshooting. Once a Controller is selected, the Standard Setup and Status diagnostic commands may be selected from a drop down list and sent to the selected controller. The response from the controller is displayed in the Diagnostic Window, and may be viewed, copied to the clipboard, a Report created and printed or saved to a file.

        2. In addition, any supported DIGI*TRAC Command can be sent to the selected controller.

      14. Status Viewer:

        1. There shall be a Status Viewer which displays in a spreadsheets type format, the real-time status of all or selected Doors, Readers, Inputs, Relays, Expansion Inputs, Expansion Relays, and Controllers. Devices may be grouped in to “Status Groups”, which are selectable from a drop down list. Devices may have selected information displayed. The available list includes the following:

          1. Name and Address.

          2. Status.

          3. Alarm and Acknowledged Status.

          4. Masking Status.

          5. Line Module Input Status and Type.

          6. Relay Status.

          7. Detailed relay status

          8. Controller Threat Level status

          9. Revision Number.

          10. Enabled Status.

          11. Controller Alarm Relay, Tamper, and Battery Status.

      15. Alarm Viewer:

        1. The Alarm Viewer shall have 4 panes: Alarm, Acknowledged Alarms, Instructions, and Comments. At the bottom of the Main Console display are counters to indicate Active Alarms, Acknowledged Alarms, and Off Normal Conditions. Double clicking the Counter will launch the Alarm Viewer. The Alarm Viewer may also be manually launched, or automatically in the event of a new alarm occurrence. Alarm Viewer properties that may be configured include:

          1. Require Acknowledgement Before Clearing.

          2. Auto Acknowledge on RTN (Return to Normal).

          3. Require Entry of Note on Acknowledgement.

          4. Force New Note on Multiple Acknowledgements.

          5. Require Entry of Note on Clear.

          6. Force New Note on Multiple Clear.

          7. Restore Alarm Viewer on New Alarm.

          8. Specify the number of Cached Alarms to Load at Launch of Alarm Viewer.

        2. Foreground, Background, Alarm, and Secure colors may be changed. In addition, the Columns of data viewed in the Alarm and Acknowledged windows may be selected and the sequence in which they will appear. The available columns include:

          1. ICON.

          2. DVR Video.

          3. Count.

          4. Controller Time.

          5. Host Time.

          6. Description.

          7. Address.

          8. Level.

          9. Alarm ID.

          10. Acknowledge Time and Acknowledged By (available for the Acknowledged Pane).

        3. Tool bar ICONS shall include:

          1. Acknowledge Selected.

          2. Clear Selected.

          3. Acknowledge All.

          4. Clear All.

          5. Add Note.

        4. Right Clicking an Alarm Event shall display a list of available options, including:

          1. Acknowledge.

          2. Clear.

          3. Acknowledge All.

          4. Clear All.

          5. Record Note.

          6. Go To Graphic.

          7. Display User Photo.

          8. Replay WAV file.

          9. DVR Alarm Video: Show Viewer and Get Recorded Alarm Video.

      16. Event Viewer:

        1. The Event Viewer can display all or Filtered Transactions. Custom filers may be defined and selected, or Standard selections can be made for main categories of Event types. Column width, order, selection, and scrolling direction are user definable, as well as text and background color.

        2. The number of cached events to load when launched, up to 10,000, may be defined. The Operator shall be able to scroll back in time to view events no longer seen on the screen, without the need for running a report.

      17. Velocity Learning Center – An Internet Explorer like “Velocity Learning Center” page shall be available for accessing on-line help, tutorials, manuals, Known Issues, and Product Registration information.

      18. Create Defect Report

        1. There shall be a wizard to create a system defect report to aid in reporting issues to factory technical services personnel.

      19. Customization Manager:

        1. There shall be a Customization Manager that allows the Operator to define an alternate language or change the English name or label for each element of the software.

        2. Audio WAV files may be defined for playback when a particular Alarm Type is active.

        3. Priority Levels may be defined (1-99) for each Alarm Type.

        4. Operator Instructions per Alarm Type shall be user definable.

        5. Individual Alarm Points may be customized on an individual point level, where each alarm point can have a unique priority, wav file, and operator response instructions.

        6. Alarm points that are customized can have an assigned “escalation” where if an operator doesn’t respond in a user defined period of time, the alarm event can be escalated to another Operator with the selected Role.

      20. Report Manager:

        1. The Report Manager shall allow the Operator to select from a number of pre-defined Reports. Custom Reports can be created outside the software, and added to a Custom folder, making the Custom Reports available from within the Report Manager application.

        2. Once a Report is selected, the default Criteria and Sorting options may be used, or custom Criteria and Sorting options may be selected.

        3. Once the report is run, it may be viewed, printed, or saved in various standard file formats.

        4. Standard Reports included as standard shall include:

          1. Customization Reports:

            1. Component Resources.

            2. Customizations Report.

          2. DIGI*TRAC Configuration

            1. Controllers.

            2. Doors.

            3. Expansion Inputs.

            4. Expansion Relays.

            5. Inputs.

            6. Network Layout.

            7. Printers.

            8. Readers.

            9. Relays.

          3. History Logs:

            1. Active Alarms by Date.

            2. Alarm Log by Date.

            3. Alarm Log by Date with Comments.

            4. All Events Log.

            5. External Events Log.

            6. Internal Events Log.

            7. Operator Log.

            8. User Activity Log.

          4. Person Information:

            1. Credential Status.

            2. Door Access by Person.

            3. Dossier Style by Person.

            4. Expired and To-Be-Expired Person Access.

            5. Expired Credentials.

            6. Last Access by Person.

            7. Person Access and Function Group Summary.

            8. Person Access and Function Group Summary with Codes and Cards.

            9. Person Access by Door.

            10. Person Access Summary.

            11. Person Access Summary with Codes and Cards.

            12. Person FG Summary with Codes and Cards.

            13. Person Function Group Summary.

            14. Who Is Inside Where.

          5. Velocity Configuration:

            1. Command Sets.

            2. Door Groups.

            3. Function Group Extensions.

            4. Functions Groups with Users.

            5. Functions with Users.

            6. Holiday Schedules.

            7. Holidays.

            8. Master Door Groups.

            9. Master Door Groups with Persons.

            10. Operator Groups.

            11. Operators.

            12. Time Zones – Grand Master Time Zone.

            13. Time Zones – Master Time Zone.

            14. Time Zones – Standard Time Zone.

            15. Time Zones – Standard Time Zones in Use.

      21. CCTV Interface:

        1. System Software shall allow the ability to define, view, monitor, and control the CCTV Matrix Control System. Simulated Alarms can be sent to the switcher, as well as Tours, Presets, select a specific camera, Grab and Store a CCTV image, and pan/tilt/zoom/iris controls for the selected camera. In addition, one or more Triggers and Actions can be defined for each camera.

      22. DVR Interface:

        1. The DVR interface configuration allows a qualified Operator to add a new DVR to Velocity. Properties defined when adding a DVR include:

          1. DVR Name.

          2. DVR Description.

          3. DVR Vendor (American Dynamics: DV8000, DV16000, Intellex IP, and Ultra; and Integral Technologies DVX series currently supported).

          4. DVR I.P.

          5. I.P Port (Control).

          6. I.P. Port (Live Video).

          7. DVR Server Name.

          8. Port (Listen).

          9. Time Zone.

          10. DVR Enabled.

        2. From the DVR Interface Configuration, the Operator shall be able to Search and Retrieve video from one or more cameras for a specified period of time. In addition, the Event Viewer History enables a qualified Operator to track and report events that are specific to the DVR subsystem history logs. These logs include:

          1. Active Alarms by Date.

          2. Active Alarms by Date with Comments.

          3. Alarm Log by Date.

          4. Alarm Log by Date with Comments.

          5. All Events Log by Category.

          6. All Events Log by Date.

        3. The DVR interface shall allow a qualified Operator to:

          1. View Cameras.

          2. Generate a Host Alarm.

          3. Stop a Host Alarm.

          4. Get Alarm List from DVR.

          5. Search and Retrieve Recorded Video.

          6. Play Local Video.

          7. Time Synchronization.

          8. Diagnostics.

          9. View DVR Properties.

        4. When Viewing cameras, the Operator may select Small, Medium, or Large display size, and select for viewing 1, 4, 9, or 16 cameras to display in the View Window. Cameras may be selected then dragged to the window the Operator wishes to view the camera in. If the camera has Pan/Tilt/Zoom/Focus/Iris control, the Operator can open the control functions and operate the on-screen controls for the selected camera.

        5. An Operator shall be able to define Triggers and Actions that allows Alarms and Events in Velocity to cause Alarm recording in the DVR through an API interface.

        6. In Graphics, DVR Cameras and DVR recorder ICONS can be placed on floorplans and used to view the associated video from the selected camera.

        7. Video can be exported from a DVR and store it on the Velocity PC, then transfer the video to other media like CD-R and CD-RW.

        8. There shall be a Velocity Video Explorer application that lets a qualified Operator to view multiple cameras from multiple DVRs in a single window. Cameras can be displayed in 1, 4, 9, or 16 display views and these views can be saved as View Groups for fast and easy selection by the Operator.

      23. Console Preferences:

        1. The Console Preferences shall define specific settings or devices for use with Velocity. These shall include: Show Splash Screen on Startup; Access and Enable Customized Values for Components in Customization Manager; Use 24-Hour Time Format; Automatically start Velocity when computer starts; PIN and Code reuse options; Display Credential template and time to display; SQL Server and Network Connections settings; Alarm Options for Stacking, Make Note requirements, repeat Multimedia until Acknowledged, and Alarm Queuing options; Report, Badging, and Alarm/Event Printer properties; CCTV Properties.

      24. DIGI*TRAC Configuration:

        1. This function shall contain the required definition of the hardware components of the system. The database files shall be based on the hierarchy of the system hardware as it is physically installed in the field.

          1. The system shall have the ability to export controller configurations in an XML format for later use on this or other systems.

          2. The system shall have the ability to import a previously exported controller configuration for ease of adding a new system.

          3. The system shall have the ability to drag and drop and duplicate controllers in the hardware tree. No reprogramming of Door Groups shall be required when dragging and dropping one or more controllers in the hardware tree.

      25. Controller Properties:

        1. Controller Properties shall define all General settings for the Controller. These setting will include: Name, Type, Address, Local Time Zone, Enabled Status, Firmware Revision Number and Date, Expansion Option Boards Installed and available Hardware. All additional Controller Setup Options can be defined here and are detailed in the Firmware Features section below.

      26. Controller Device Properties:

        1. The Controller Device Properties shall define all connected field devices, including: Doors, Readers, Inputs, Relays, Expansion Inputs, and Expansion Relays. Device names and all operating parameters shall be definable if operation other than the included defaults is required.

      27. Graphics:

        1. The Graphics application shall allow the Operator to add, delete or modify graphic floor plans and add indicator ICONs to graphic floor plans that represent Controllers, input/output points, readers, or cameras located in the facility. Formats for Graphics supported include: jpg; bmp; dxf; wmf; emf.

        2. There shall be two Modes, Live and Design. The Live mode shall be used for real time monitoring. In addition, right clicking an ICON presents the Operator with a list of available Access or Control Functions that can be issued to the device. The Design mode allows the Operator to Define which Graphics are to be used, place ICONs on the Graphics, and define properties for each ICON.

        3. There shall be a Pan and Zoom Viewer that provides a key plan that can be panned and scrolled by moving the red box, which indicates the current viewing area.

        4. There shall be a Directory of available Graphics to easily select the desired Graphic to display.

        5. The Graphics application shall display the real-time state and condition of Alarm Points and Doors. The Door ICONs shall change from a closed door ICON to an Open door ICON, representing that the door is open. When the door is closed, a closed ICON will appear again. The Alarm ICONs shall change from a closed contact ICON to an Open contact ICON, representing that the alarm device is active. When the Alarm Device is restored to it’s normal condition, a closed contact ICON will appear again. The ICON will also display the Device Name and Alarm Condition that caused it to go into an Alarm condition. The Color of the ICON will also change based on whether it is in alarm or secure.

        6. User definable ICONs can be created and used. Link ICONs can added to quickly link to other graphics. Command Set ICONs can be used to issue a Command Set with a single mouse click.

        7. Custom Links shall be available to provide additional functionality. These links include:

          1. AXIS Camera Link – This link shall enable the Operator to launch an AXIS IP camera from any graphics page. A dedicated viewer window will open for each camera link by double clicking the link.

          2. Quick Link – This link shall enable an Operator to launch an HTML page from any graphics page. A dedicated window will display the defined HTML page when the link is double clicked.

      28. Badge and Graphics Designer:

        1. The Badge and Graphics Designer shall allow the Operator to create and customize an unlimited number of Badge Templates that may be assigned to a Person in the Enrollment Manager and create Backdrops to be used in the Graphics module.

        2. An Object Toolbar shall be available for selecting Objects to appear on the Badge Template or Backdrop, including: Bit Map Logos, Photos, Fixed Text, and Database Fields. Each Object shall have a Properties box where the specific Properties of that Object are defined, including: File, database field, Font Color, Font Style, Font Size.

      29. Enrollment Manager:

        1. The Enrollment Manager application shall maintain information related to a Person, and Credentials assigned to that person. Multiple Credentials per person shall be supported. New people can be added with the assistance of a Person Template to automatically enter User Defined field data and select Person Groups for this person.

        2. The Personal Information pane shall include the General, 10 Additional Tabs, and a Person Group tab. The system shall be capable of defining 999 user definable fields and place them on any of the 10 Tabs. The captions of the Tabs are customizable and can be restricted by Operator. There shall be an “Additional Images” tab that can be used to store additional photos of the person, photos of relatives, and/or photos of Assets assigned to the person. These field names can be either a “Text Box”, “Dropdown” where the Operator can enter text, or select from a Dropdown List, a “Dropdown List” where selecting from the List is required, Date, Number, Unique number, Auto-unique, Auto-sequential, unique text, and the Dropdown and Dropdown Lists can sort in Ascending or Descending order. Fields can be made “Required”, where the Person’s record cannot be saved unless data is entered in that field. Field captions can have their color changed. A Photo field shall be available for acquiring a live video image, acquire an image from a TWAIN device, or acquiring a photo from an existing file. A Record Last Updated field shall be available, as well as Preview and Print a Badge. A signature field shall also be available.

        3. A Person can be placed in one or more Person Groups. An Operator’s Role/s determines which Users an Operator can view.

        4. Once a person is added, one or more Credentials may be added to that Person. Credentials may be added using a Credential Template, or directly without a Credential Template. The Credential will take on the properties of the Credential Template if used. There shall be a Card Enrollment Station used for entering card data into the system. PIN Numbers can either be randomly selected, or Operator/User selected. Multiple card formats shall be supported, including: multiple bit length Wiegand, ABA (magnetic stripe), and custom. Each credential can have assigned one or multiple Door Groups, Master Door Groups, or Function Groups for access and control authorization. If a new Door Group is required and not currently defined, the Operator can create a new one from within the credential management application. Additional credential properties that may be assigned include:

          1. Badge Template.

          2. Card Data.

          3. Hot Stamp Card Number.

          4. Activation Date/Time.

          5. Expiration Date/Time.

          6. PIN Length.

          7. PIN Number.

          8. Duress Digit.

          9. Day/Use/Absentee Limits.

          10. 2 Person Rule.

          11. Threat Authority.

          12. Tag.

          13. Alert.

          14. Disable.

          15. Passback Executive Override.

          16. Special Needs Access.

          17. Issue Number.

        5. Devices may be configured to allow for scanning and automatic field data entry from a Business Card scanner, Drivers License Scanner, Passport Scanner, and PIV Smart Card Reader. Fields can be mapped to allow for proper placement of the scanned data in the correct field. There shall be the ability in the credential management program to provide Print and Issue control for badging, where the maximum number of times a badge can be issued and printed can be set, as well the current count listed. The reason for a badge reissue shall be logged for auditing purposes.

        6. Once a Person is selected from the List, the Credential Status and information is displayed for the assigned Credentials. The information includes: IDF, ID, Function, Description, Status, Expires On, Last Access, Last Door, Tag, and Alert. An Operator may right click on a Credential, and will be presented with the following options: Tag, Alert, Disable, Forgive Passback, Override Code Tamper, Reset Limit Count, Force Download, Unassign, Delete, and Properties.

        7. The bottom of the Enrollment Manager window shall display counters for: People, Assigned Credentials, Unassigned Credentials, and Guest Credentials.

        8. Multiple User search options shall be available, including: “Find Person” query search builder; form based quick search, and Quick Find.

        9. There shall be the capability to group edit multiple User’s user defined fields and Person Groups.

      30. Download Monitor:

        1. The system shall display the status of all data downloads to the field controllers.

      31. Switch Operator:

        1. There shall be the capability to change Operators without the need for the current Operator to Log Off the computer. The new Operator’s Velocity permissions are then used during the session to control access to Velocity functionality.

      32. Velocity Data Import/Export:

        1. There shall be the capability to Import user related data into the database. This data can be in either a text file, Comma Separated Value format, or XML format. The imported data can be mapped to any of the user definable fields available within the Velocity Enrollment Manager. In addition, a User’s photo, signature, and credential info, including PIN, card number, hot stamp card number, and the Credential and Person Templates to use when importing are available for importing.

        2. There shall be the capability to Export user related data from the Velocity database. This exported data can be formatted in a text file, Comma Separated Value, or XML format. This data can be selected from any of the fields available in the Velocity Enrollment Manager.

      33. Add-Ins: The following “Add-Ins” are available to be added to Velocity by an authorized Operator.

        1. Velocity Remote Desktop – The Operator shall be able to launch a terminal services session from within the Velocity shell.

        2. Launchpad – The Operator shall be able to launch standard Windows applications within Velocity.

      34. Software Developers Kit (SDK): The Security Management Application shall support an SDK to allow for external third party applications to interact with the Enrollment Manager Application. It shall also provide for external event and alarm monitoring and control back into the application in an XML format.

        1. API – There shall be available as an option, an Application Programming Interface to allow third party applications to manage Users and Credentials in the Security Management application, including add, edit, and delete functions.

        2. XML – There shall be available as an option, an XML interface to allow for the Security Management application to receive commands in an XML format, as defined by the SDK, to perform commands like: List Alarms, Acknowledge Alarms, Unlock Doors, issue Command Sets, and others, and to provide command responses in an XML format.

        3. The Vendor shall have available a Professional Services Group to assist and/or provide solutions using the SDK.

    3. HARDWARE REQUIREMENTS

      1. Controllers:

        1. There shall be three primary types of controllers:

          1. Access control (1 Door [Hirsch Model M1N], 2 door [Hirsch Model M2N] and 8 door – [Hirsch Model M8N].

          2. Alarm monitoring (16 supervised inputs – [Hirsch Model M16N]), expandable to 32 inputs.

          3. Relay control (8-32 relay [Hirsch Model MSPN-8R] with the addition of REB8 relay expansion boards and (64 relay – [Hirsch Model M64N]).

      2. Each controller shall have the following common features.

        1. Controller Board: The controller board shall be microprocessor based, incorporating Flash ROM (firmware) downloadable from the Host Computer, RAM (User Information, System Setups, Event Transaction Buffer) and a Clock/Calendar. The ROM shall be modularly upgradeable in the field for enhancements to system features. All powered connections to the controller board shall be protected by fuses. All wiring connections to the controller board shall be to “Phoenix” type screw terminals. Each door connection shall consist of terminals for two readers, one 10 Amp rated Form C dry output relay for lock control, and one input for monitoring a status switch, a request-to-exit device, and a tamper switch. There shall be status indicator lights for active relays, as well as diagnostic indicator lights to aid in system troubleshooting. There shall be dedicated alarm output relay/s for external reporting of the following conditions: Alarm; Duress; Tamper; and Trouble.

        2. Enclosure: The controller enclosure shall be a NEMA style metal cabinet designed for surface mounting. It shall have a tampered, removable hinged door with a high security key lock. It shall have conduit knockouts to allow from 1/2″ to 1″ EMT conduit to be used for wire entry into the cabinet.

        3. Internal Power Supply: The controller shall have an internal power supply that will accept 50 Hz/ 200 – 240 VAC, or 60 Hz/100 – 120 VAC. The primary side of the power supply shall be protected with a fuse. The power supply shall provide 28 VDC power to the controller board, internal battery charger, selected card readers, and reader interface boards.

        4. Standby Battery: The controller shall have an internal standby battery that is capable of running the system during AC power interruptions. It shall be recharged by a charging circuit incorporated into the controller board.

        5. Expansion Options: A maximum of five (5) expansion boards can be installed in each controller, with the exception of four (4) in the Model M64N and none in the Model 1N. A SNIB (SCRAMBLE*NET Interface Board) is included with each controller with the “N” designation in the part number and takes up one of the available expansion slots. A SNIB2 is included with each controller with the “N2” designation in the part number.

        6. Alarm Inputs: The controller shall be capable of accepting up to 32 additional supervised alarm inputs, in increments of eight (8). The sensitivity of the line supervision shall be 2% AA Standard. The alarm expansion boards shall be mounted in the controller cabinet and connect to the controller board via an expansion bus cable. This option shall be limited to 16 additional supervised alarm inputs for the 16 zone alarm input controller (Model M16N) and none for the Model M1N. The alarm expansion board shall be Hirsch Model AEB8.

        7. Relay Output: The two (2) access control (Model M2N and Model M8N) and one (1) alarm monitoring (Model M16N) controllers shall be capable of accepting up to 32 additional Form C, 2 Amp rated relay outputs in increments of 8. The 1 – 32 relay controller (Model MSPN-8R) shall accept up to a maximum of 24 additional Form C, 2 Amp rated relay outputs in increments of 8. The 1 – 64 relay controller (Model M64N) and the Model M1N shall not accept any additional relay outputs. These outputs shall be used for control applications other than standard door access, such as elevator floor control, local door annunciators, HVAC interface, etc. The relay expansion boards shall be mounted in the controller cabinet and connect to the controller board via an expansion bus cable. The relay expansion board shall be Hirsch Model REB8.

        8. CODE/Buffer: The controller shall be capable of expanding the CODE database up to a maximum of 132,000 Users with the addition of a memory expansion board. The board shall be mounted in the controller cabinet and connect to the controller board via an expansion bus cable. The CODE/Buffer ewxpansion board shall be Hirsch Model MEBCB64 (64,000 Users) or the MEBCB128 (128,000 Users). Both Expansion Boards shall expand the Buffer capacity as well as the Code record capacity. The Model M1N shall not accept any CODE/Buffer Expansion board.

        9. Event Transaction Buffer: The controller shall be capable of expanding the event transaction buffer up to a maximum of 20,000 events and 2,000 alarms with the addition of a memory expansion board. The board shall be mounted in the controller cabinet and connect to the controller board via an expansion bus cable. The event transaction buffer expansion board shall be Hirsch Model MEBBE. The Model M1N shall not accept a Buffer Expansion board.

        10. Intelligent Reader Interface: The control panels shall utilize an intelligent reader interface (Hirsch MRIA or MRIB) to communicate with card readers of various types. The interface shall be microprocessor based and allow data formats including ABA magnetic stripe, Wiegand (26 to 55 bit), Proximity, Bar Code, Touch Memory, RF and Biometric. The interface shall utilize a digitizing algorithm, which will convert the card data to a unique number, thus, eliminating the need for facility codes. A single interface shall support both entrance and exit readers with keypads associated with each door. The interface shall be U.L. Listed to U.L.294. The reader interface shall be included as standard in all Scramble Pads.

    4. CONTROLLER FIRMWARE

      1. General Features:

        1. The software for the controller shall reside in Flash ROM (firmware) and be located on a plug removable module on the controller board to facilitate easy field upgradeability of the features. All of the necessary software for a fully functional System is located in the controller. The controller firmware shall include the following general features at a minimum and be fully supported by the VELOCITY head-end.

          1. 3 – 15 digit keypad Code’s.

          2. Duress digit for keypad Code’s.

          3. 150 Time Zones for access restriction and automatic event control.

          4. 128 Access Zones for access management.

          5. 256 Control Zones for alarm and relay management.

          6. 366 programmable holidays this year, 366 days next year. Each Holiday may be assigned to 1 – 4 Holiday Schedules.

          7. Automatic daylight savings time clock adjustment.

          8. 27 different functions for Code’s and cards, e.g. access, unlock, re-lock, alarm mask, relay control.

          9. Add user records.

          10. Tag users for annunciation at host computer.

          11. 4,000 Users.

          12. 1500 event, 1500 alarm transaction buffer.

      2. Access Control Features

        1. The controller shall include the following access control features at a minimum:

          1. Restrict access by: time of day; day of week; door; holiday.

          2. Momentary Access of door up to 8100 seconds.

          3. Extended Access for User Definable Momentary Access duration (requires ScramblePad). ScramblePad will display time remaining on the minute, and annunciate at the defined “Warning Time”.

          4. Special Needs Time Extension to provide additional time for Momentary Access and Door Open Too Long for selected people.

          5. Unlock/Re-lock of door by CODE, card or Time Zone.

          6. Door status monitoring shall allow for: door forced monitoring; door-open-too-long monitoring; door-open-too-long while door is unlocked; auto-re-lock of door when opened or closed.

          7. Request-to-exit masks alarm and/or unlocks door.

          8. 2 person requirement by door. A user can be defined as Normal, A/B Rule A, A/B Rule B, Executive Override. Can be disabled by Time Zone.

          9. 63 Passback Zones. Can be disabled by Time Zone. A User can designated with Passback Executive Override.

          10. Use Count limits on users

          11. Absentee Rule limits on users.

          12. Temporary Day limits on users.

          13. Occupancy Counting / Minimum & Maximum limits per Passback Zone.

          14. Deadman CODE / Timer.

          15. Threat Levels – 99 Levels may be defined. Based on the Level in effect for the facility, selected readers may be disabled, dual readers in Card/Code Only During Time Zone can require dual, and selected User’s Credentials can be disabled.

      3. Alarm Management Features:

        1. The controller shall include the following alarm management features at a minimum:

          1. Momentarily mask alarm by CODE and/or card.

          2. Mask/unmask alarm by CODE and/or card or by Time Zone.

          3. Alarm device supervised while masked.

          4. Tamper switch on alarm device monitored while masked.

          5. Tamper Input may be configured to operate as a “Latch Monitor” with the appropriate door lock hardware.

          6. Entry/Exit delay per alarm input.

          7. Alarm input triggers relays.

      4. Relay Control Features:

        1. The controller shall include the following relay control features at a minimum:

          1. CODE and/or card, input, or other relay triggers relays.

          2. Trigger relay/s by time zone.

          3. Relay may be normally de-energized or energized.

          4. Disable relay/s during time zone.

          5. Clear relay at end of time zone.

    5. CARD READER/KEYPAD SPECIFICATIONS

      1. Readers:

        1. The controllers shall accept all of the following reader technologies concurrently: Scrambling Keypad; Mag Stripe; Wiegand; Proximity; Smart Card; Bar Code; Biometrics – Retinal Scan, Hand Geometry, Fingerprint; Radio Frequency. The readers can be used for access control, alarm management, and/or relay control and shall be capable of being used alone (keypad only, card only) or a scrambling keypad and any other reader technology may be combined to operate as a dual technology reader where two valid IDs (PIN and card) are required.

      2. ScramblePad:

        1. The controller shall be capable of using scrambling keypad readers. The keypad shall incorporate the following features: Scrambling display of numbers 0 – 9 (numbers appear in different location every time it is used); +/- 4 degree horizontal and +/- 26 degree vertical viewing restriction; accept 3 – 15 digit CODEs simultaneously; be disabled for 1 minute and report CODE Tamper violation (guessing CODEs); be disabled and report Physical Tamper violation (attempt to remove keypad from mounting box); silent CODE duress; status LEDs for reporting granted, denied, and overridden transactions, AC Fail, Programming Mode active, responses to Status Request of Alarm Inputs and Relay Outputs; weather resistant; supervised by controller; and built-in diagnostics. The ScramblePad shall include the MATCH Reader Interface functionality for connection of up to two (2) card readers. The scrambling keypad shall be the Hirsch ScramblePad Model DS47L.

** NOTE TO SPECIFIER ** Delete if not required.

        1. A version of the scrambling keypad shall be available for use in high ambient lighting conditions or where the front is subject to direct sunlight. This version shall have a +/- 26 degree horizontal and +/- 4 degree vertical viewing restriction. The high intensity display scrambling keypad shall be the Hirsch ScramblePad Model DS47L-HI.

** NOTE TO SPECIFIER ** Delete if not required.

        1. A version of the scrambling keypad shall be available with an integrated proximity card reader. Presentation of the card shall automatically auto-start the scrambling display. The scrambling keypad with integrated proximity card reader shall be the Hirsch ScrambleProx Model DS47L-SPX.

** NOTE TO SPECIFIER ** Delete if not required.

        1. A version of the scrambling keypad with high intensity display shall be available with an integrated proximity card reader. Presentation of the card shall automatically auto-start the scrambling display. The scrambling keypad with integrated proximity card reader shall be the Hirsch ScrambleProx Model DS47L-SPX-HI.

        2. A version of the scrambling keypad shall be available with an integrated smart card reader. Presentation of the card shall automatically auto-start the scrambling display. The scrambling keypad with integrated smart card reader shall be the Hirsch ScrambleProx Model DS47L-SS-IE.

** NOTE TO SPECIFIER ** Delete if not required.

        1. A version of the scrambling keypad with high intensity display shall be available with an integrated smart card reader. Presentation of the card shall automatically auto-start the scrambling display. The scrambling keypad with integrated smart card reader shall be the Hirsch ScrambleProx Model DS47L-SS-IE-HI.

      2. Mag Stripe Card Readers:

        1. The controller shall be capable of using standard ABA/ISO high and low energy track 2 cards and readers. The reader shall have a wide throat to accept laminated photo ID cards. For indoor and outdoor use, the mag stripe reader requires the addition of a MRIB (MATCH Reader Interface Board) or a MRIA (MATCH Reader Interface Assembly).

      3. Wiegand Card Readers:

        1. The controller shall be capable of using standard Wiegand readers and cards with 26-55 Bit standard Wiegand data formats. The readers can be swipe, insert, turnstile, or key.

      4. Proximity Card Readers:

        1. The controller shall be capable of using proximity readers that output a standard 26-55 Bit Wiegand data format. The readers can have a short or long read range and be unidirectional or bi-directional.

      5. Bar Code Reader:

        1. The controller shall be capable of using Bar Code readers and cards with standard Wiegand data format output. The reader shall be swipe, black, weather resistant, and capable of reading multiple symbologies, including concealed bar codes.

      6. Miscellaneous Readers:

        1. The controller shall be capable of using any reader technology that outputs a standard ABA/ISO data format or a standard 26-55 Bit Wiegand data format. Readers that meet this requirement include: Radio Frequency; Biometrics – Hand Geometry, Retinal Scan, Finger Print, Voice Recognition; Smart Card, including Mifare, DESFire, and FIPS-201 compliant readers.

  2. EXECUTION

    1. EXAMINATION

      1. Do not begin installation until substrates have been properly prepared.

      2. If substrate preparation is the responsibility of another installer, notify Architect of unsatisfactory preparation before proceeding.

    2. INSTALLATION

      1. Install system in accordance with manufacturer’s instructions.

      2. Install wiring for detection and signal circuit conductors in conduit. Use 22 AWG minimum size conductors.

      3. Make conduit and wiring connections to existing door hardware devices as required.

    3. FIELD QUALITY CONTROL

      1. Test in accordance with NFPA 72 – National Fire Alarm Code

      2. Test in accordance with Hirsch Electronics testing procedures for “Velocity Security Management System”.

    4. TRAINING

      1. The two designated System Administrators shall attend the 4 Day Factory Velocity Class.

      2. The Dealer shall coordinate with the System Administrators for two 8 hour Operator training sessions on the Operational System to be conducted on-site on the actual running system.

    5. MANUFACTURER’S FIELD SERVICES

      1. Provide manufacturer’s field services for final system checkout and acceptance testing as required.

    6. PROTECTION

      1. Protect installed products until completion of project.

      2. Touch-up, repair or replace damaged products before Substantial Completion.

 

END OF SECTION

 

This good article was extracted from: http://www.arcat.com/sdspecs/htm/13705hei.htm

Category:

CCTV & Security System

Leave a comment

Tagged with:

Leave a comment