Suggestions For Access Control System Requirements

Please share software model and hardware that matches below requirements.

Components of an access control system:

Software: Used to adjust all parameters of the system, control hardware, display events related to movement of users, alarms, and operation of hardware devices. The software is also used for storing all events in the database and generating reports based on requirements defined by an operator.

Electromechanical hardware:

  • Electric locks

  • Parking barriers and garage gates

  • Turnstiles

Electronic hardware:

  • Controllers: receive settings from software and control the electromechanical hardware of the system.

  • Contactless readers: read unique numbers of identification cards/tags and forwards the numbers to controllers.

  • Fingerprint readers: scan fingerprint images, compare them with the templates stored in the internal reader database (or on a smart card) and send the verification results to controllers.

System users:

  • Operators: responsible for administrating the system, creating new users, issuing cards and performing other regular daily tasks.

  • Installers: responsible for installing, programming, maintaining and troubleshooting the system.

  • Users: regular staff of the company, with permanent or long-term ID cards (or PINs), who use the system to gain access to certain building areas as configured by operators.

  • Visitors: people that are not employed by the end-user company, but still have rights to access certain areas (contractors, visitors, delivery people, etc.).

  • Vehicles (or other equipment): are accounted for and their in/out movements are controlled and tracked by the system, in order to prevent unauthorized vehicles from entering parking areas, or valuable equipment from being taken without authorization.

Technical requirements

  1. Software

    1. The software will operate in MS Server 2012, MS server 2016, MS Windows 8 and MS Windows 10

    2. The number of cards/users shall be limited only by memory available in hardware.

    3. At least 3 active cards per user shall be supported.

    4. At least 8 access levels per user shall be supported.

    5. Access levels should be assigned to a user, not to a card, in order to help issue a new card in a fast and easy manner, without reassigning access levels.

    6. The software shall have automatic holiday rescheduling feature.

    7. The software shall have the ability to perform scheduled automatic database maintenance and backup tasks at user selected intervals and ability to configure the amount of history stored in the active database.

    8. The software shall have the ability to produce the following report types: system and alarm event reports, user reports, hardware configuration settings, access level reports, employee time & attendance reports.

    9. The reports shall be available in Adobe PDF and MS Excel formats.

    10. Report filters must be convenient and user friendly: allow operator preview user photos, content of access levels, hardware settings and time zone configuration.

    11. The software shall support an unlimited number of building floor plans.

    12. Floor plan viewing interface shall have convenient zoom in/out controls by mouse wheel.

    13. The software shall allow operator to conveniently edit floor plans by “dragging and dropping” hardware devices to selected plan areas.

    14. The software shall allow assigning custom icons to each floor plan in order to help operators identify floor plans quickly. The software shall have a wide selection of default icons as well.

    15. The software shall support “full-screen” mode that would take up 100% of the monitor area and prevent operators from starting or accessing any other programs.

    16. All configuration and user changes shall be sent to controller immediately. The software shall display the progress in percent as the changes are being downloaded. The downloading shall be done in background and not affect the normal use of the software in any way.

    17. The floor plans shall display real-time status of system hardware and allow operators to immediately see the effects caused by configuration changes.

    18. Dynamic search function shall be present in all windows of the program: search results shall be narrowed automatically as a key phrase is being entered. I.e. after entering characters “xy” the program shall locate and display all records containing these characters, and after typing in more characters shall refresh the results automatically.

    19. The software shall use an industry standard database engine released not earlier than 2005 and currently supported by the manufacturer.

    20. The software shall have the ability to automatically display photos and additional information about users as they enter/exit through doors.

    21. The software shall be available in English

    22. The software shall have a modern interface, attractively designed and convenient to use.

    23. The software shall be adapted for operators who have not received any special training related to management of integrated security systems. Graphical user interface shall be intuitive. Introducing the system to a new operator shall not take more than 1 hour.

    24. In order to reduce the amount of work done by an operator, the software shall incorporate an option to copy objects: users, doors, floor plans, time schedules, access levels and holidays.

    25. The software shall facilitate integration with other systems of the building.

    26. The software shall have the ability to transfer entry and exit events to HR systems with the purpose of work time calculation.

    27. The software shall store information and provide reports about visitors and appointments.

  1. Hardware

  1. The hardware shall support open architecture. Communication protocols shall be available to system integrators and software development companies in order to protect end-users from being constrained to a single brand of hardware or software.

  2. The hardware shall support all industry standard readers that output information in Wiegand or Clock/Data formats (up to 128 bits).

  3. There shall be at least 2 types of controllers: (a) for one door with an entry reader and an exit button and (b) for one door with two readers (entry and exit) or for two separate doors with entry readers and exit button.

  4. There shall be an IP-reader available. The IP-reader shall integrate a contactless card reader and controller in a single body, designed for surface mounting on a wall or a door frame eliminating the need for enclosures.

  5. Each controller and IP-reader shall have a standard RJ-45 network port for communication with software and other controllers.

  6. Controller and IP-reader shall support standard Ethernet 10/100BaseT network and TCP/IP communication protocol.

  7. Systems using Ethernet converters, adapters, or terminal servers that enable network connectivity for legacy controllers by tunneling RS-232/485 serial data over Ethernet shall not be acceptable.

  8. Single-door controller and IP-reader shall have at least 32Mb SDRAM operating memory and 8 MB Flash memory for database and events. Two-door controller shall have an option for expanding Flash memory to 32MB.

  9. All controllers and IP-readers shall use a 32Bit 100Mhz RISC processor (or better) in order to enable fast execution of advanced functions.

  10. Controllers and IP-readers shall accept firmware upgrades via network.

  11. In case communication with the host PC is interrupted, the controller and IP-reader must have enough memory to store at least 5000 latest events (FIFO buffer).

  12. Operation of controller and IP-reader shall be completely independent of the PC or “Master controller”. Should the PC or the communication link fail, the users should not be affected in any way and all functions should continue working.

  13. IP-reader shall have the following inputs and outputs:

      1. Exit button input

      2. Door contact input

      3. Auxiliary alarm input

      4. Tamper sensor and tamper input

      5. Inputs for monitoring AC power and backup battery state. There should be an option to reconfigure these inputs to function as general purpose inputs.

      6. Relay for controlling an electric lock.

      7. General purpose auxiliary output relay.

  1. One-door controller shall have the following inputs and outputs:

  1. Power output for the reader

  2. Outputs for controlling LEDs and beeper of the reader

  3. Wiegand or Clock/Data input

  4. Exit button input

  5. Door contact input

  6. Auxiliary alarm input

  7. Tamper input

  8. Inputs for monitoring AC power and backup battery state. There should be an option to reconfigure these inputs to function as general purpose inputs.

  9. Relay for controlling an electric lock.

  10. General purpose auxiliary output relay.

  1. Two-door controller shall have the following inputs and outputs:

  1. Power output for two readers

  2. Outputs for controlling LEDs and beepers of the readers

  3. Two Wiegand or Clock/Data inputs

  4. Two exit button inputs

  5. Two door contact inputs

  6. Two auxiliary alarm inputs

  7. Tamper input

  8. Inputs for monitoring AC power and backup battery state. There should be an option to reconfigure these inputs to function as general purpose inputs.

  9. Two relays for controlling an electric lock.

  10. Two general purpose auxiliary output relays.

  1. Relays of controllers and IP-readers should support two modes of operation: (a) dry contact and (b) powered mode, whereas power to the lock is provided via relay contacts this way simplifying wiring and eliminating the need for an additional power supply.

  2. Controllers and IP-readers shall have a built-in PoE capability, in order to reduce wiring and provide backup power effectively. PoE feature must comply with the 802.3af standard.

  3. Controllers and IP-readers shall be capable of supplying up to 600mA @ 12VDC to peripheral devices: readers, electric locks, sirens, detectors, etc.

  4. Controllers and IP-readers shall accept the standard 12VDC power input in case an existing network infrastructure does not support PoE.

  5. In case the main PC of the system fails, controllers and IP-readers shall accept a connection from a laptop in order to diagnose the problem, change settings or control peripheral devices.

  6. In case of an alarm controllers and IP-readers shall initiate communication and provide timely notifications to operators. Hardware that does not initiate communication and needs to be polled frequently will not be acceptable due producing needless traffic on the network and processing load on the PC.

  7. The system shall support biometric IP-readers with the following or better specifications:

  1. 25,000 fingerprint template storage capacity

  2. 1-to-many verification in less than 1 second (with the database of 3000 users)

  3. 1-to-many verification with the database of 9000 users.

  4. 500,000 event storage

  5. Built-in USB, RS-232/485, LAN and WLAN communication ports

  6. Selectable operation modes: fingerprint, fingerprint + card, fingerprint + PIN.

  7. Door-phone function

  8. Microphone, speaker and 2.5“ QVGA color LCD

  9. 72MB flash memory

  10. Door contact and exit button inputs

  11. Lock control relay

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

***** *** ******** ******* **** **** ***** ************.

**** ****:

"*.***** ***** ** ** **-****** *********. *** **-****** ***** ********* a *********** **** ****** *** ********** ** * ****** ****, designed *** ******* ******** ** * **** ** * **** frame *********** *** **** *** **********."

******* ****:

"*. *** ******** ***** ******* **** ************. ************* ********* ***** be ********* ** ****** *********** *** ******** *********** ********* ** order ** ******* ***-***** **** ***** *********** ** * ****** brand ** ******** ** ********."

****** *** ************ ** ******* **** ********** ********* ***********. *** * **** ** *** ****** ********* **** support ****, ***:**** ** *** ** ******* ****** ***********