Access Control and Systems Integration Solutions.
DN1607-0411 Page ii
Access Control and Systems Integration Solutions.
1. Overview
1.1. Introduction
The local and remote Intrusion Detection and Video surveillance systems will be fully integrated with the access control system to:
1) Centralize building security in a single supervisor to provide the operator with an easier to operate system using fewer hardware resources.
2) Allow manual or automatic interactions between the 3 applications (access control/video surveillance/intrusion).
3) Allow the creation of common graphical floor plans
The convergence of these various applications must be implemented over the ETHERNET network.
All of the applications must work perfectly in standalone mode if the communication network fails.
1.2. Requirements
The proposed system must include proven software for this type of application, i.e. HONEYWELL WIN-PAK or equivalent. It must be easy to use and be designed to maximise all of the tools provided by the Windows platform. All of the commands will be easily accessible via a mouse and the use of the computer keyboard will be limited merely to completing fields requiring numeric or alphanumeric input.
The system and development software used must be existing, widely available, industry-approved software. The operating software must support multiple users and multitasking and be able to run on a non-proprietary CPU. The application software will be written in a standard, high-level programming language. The system must be modular for easy enhancements without major modifications to its operation or defined system data and data logs.
System modularity will also allow easier installation and reduce installation costs to a minimum.
The Supervision system will include the following accessories (not limited to below list):
- Computer(s) and printer(s);
- Licenses for the management software
- RS-232/RS-485 connections between the various system components;
- TCP/IP connections;
- Server(s);
- Workstation(s);
- Gateway(s);
The following sections describe the main functional requirements. The proposed system must meet the minimum following requirements (list is not exclusive).
1.3. Minimum system capacity
The system must operate in one of the below 64 bit and 32 bit environments:
- Windows® 7 Professional
- Windows 7 Ultimate
- Windows Server 2008 R2
And must be compatible with a TCP/IP computer network
The system must also support:
- The integration of Network and Digital Video Recorders (NVR and DVR);
- The integration of CCTV matrix switchers
- The integration of intrusion panels
2. Description of the IT hardware
2.1.1. Minimal workstation requirements
- Intel® Core™ i5 2400 / 3.1 GHz
- 4 GB RAM
- 80 GB SATA Hard Drive with minimum 5 GB free
- NVIDIA Quadro NVS 300 - 1x512MB PCIe x16 or similar Video card
- One 10/100 Base-T network card
- 17’’ LCD color screen
- Ergonomic mouse with two buttons and wheel
- Keyboard
- External backup
- 1 DVD DL RW drive
- Operating system: Windows® 7 Professional or Windows 7 Ultimate
- Database engine : Microsoft SQL 2008 R2 Express
2.1.2. Minimal server requirements
- Intel® Quad Core Xeon® / 2.4 GHz
- 16 GB RAM
- 1 TB 15000 RPM drives configured as: OS on RAID1; DB RAID 1+0 (4-disk)
- NVIDIA Quadro NVS 300 - 1x512MB PCIe x16 or similar Video card
- One 10/100 Base-T network card
- 17’’ LCD color screen
- Ergonomic mouse with two buttons and wheel
- Keyboard
- External backup
- 1 DVD DL RW drive
- Operating system: Windows Server 2008 R2 SP1
- Database engine : Microsoft SQL Server 2008 R2 with processor license
2.1.3. Uninterruptible power supply
To avoid any risk of interruption to the IT hardware's power supply, it is recommended to design in an uninterruptible power supply to maintain power whilst the generator starts up.
The server application must be installed in service mode so that human intervention is not required during a re-start.
On re-start, the server must perform the following actions automatically:
- Verify the integrity of the database
- Verify the indices
- Verify the peripheral connections
- Open the database
3. Applications
3.1. Workstation
The workstation will be the main human interface. It must be intuitive and easy to understand. It will have two main functions. The first is the supervisor/monitoring and control function. All events occurring on the system must be displayed in text format. Also, it must be possible to display video images from a video recorder in real time and receive all of the events from the intrusion detection unit. Its second function is to operate in programming mode. This mode will be used to access the security system data to create, modify and delete management data.
Each workstation will be configured in accordance with its physical location and with the security level of the (surveillance) operator.
Workstation commands will be password protected.
Each system operator will be assigned a security level allowing access to certain commands on the system in their own selectable language.
Minimal supported user interface languages should include English, French, Spanish, Dutch, Italian, Czech, Russian, Polish, Arabic, Portuguese, and Simplified Chinese.
The operator's security level will determine their access to certain commands on the system. Only the commands authorized for a given security level will be visible on the screen.
4. Software description
4.1. General ergonomy
It must be possible to determine if the screens are floating or fixed on the desktop. If they are floating, they can be positioned anywhere on the screen. Moreover, if the workstation is fitted with a double video card or with twin monitors, it must be possible to split the screens across both monitors to maximize the display and optimize the use of the work surface. However, it must be possible to display each of these screens individually or together, depending on the surveillance operator's requirements.
List of the main display screens required;
- Floor plans;
- Floor plans associated with one or more alarms from the access control, intrusion detection or video surveillance systems
- Video surveillance display (Multiple camera interface).
- Diagnostics of equipment operation.
4.2. Access control management
Hardware support and access control design
The HONEYWELL WIN-PAK supervisor software, or equivalent, must be able to accept various types of controller so that it can be tailored to the site and developed as the site evolves. This requires the supervisor to be capable of managing single door, 2-door, 3-door, 4-door and 16-door modular controllers.
The software must also support the various badge reader technologies (proximity/smartcard/magnetic stripe etc.) and card formats (26 bit wiegand, 34 bit Wiegand, clock and data, etc). It must be possible to allocate several badge technologies to a single card holder..
To connect the software to the peripheral hardware, several cable topologies can be used (e.g. TCP/IP, RS232/RS485/modem)
The system must provide the access control security using time zones, access areas, access levels and card/card holder information.
For especially sensitive access areas, the system must support higher access functionality, such as an escorted “double badging” and supervisor mode, where only badges with higher clearance have access.
Software Licensing and architecture
The software is open-ended, modular and has no license restrictions on the number of doors, controllers, readers or badges.
The software may run on a single workstation or on multiple workstations in a client/server architecture.
Graphical user interface
The Graphical User Interface must be user-friendly and handle animated, interactive graphical floor plans. A file structure identical to that of Windows Explorer is an advantage.
At a minimum the operator will have available in the graphical user interface (per operator rights):
- Time zone creation, editing and deletion.
- Access areas creation, editing and deletion.
- Access levels creation, editing and deletion.
- Card and card holder information creation, editing and deletion.
- Card holder data record creation, editing and deletion.
- Monitoring access events and alarms
- Design and monitor / control access control elements/items on graphical floor plan
- Design and monitor / control access control elements/items on control map (explorer tree representation of the access control system)
- Design and monitor / control tracking and mustering functionality to check personnel attendance or to use in evacuation scenarios
- Card holder pop-Up view
- Locate card holder or card
- Set up and create reports
- Operator rights and levels creation, editing and deletion.
Card holder pop–up view on card actions
Option of displaying the card holder's photo and access permissions live on the operator’s monitor when his/her credential/card is read. It must be possible to pop-up a video screen in the software from the relevant camera to allow the operator to compare the information.
Additional Card holder data records
Additional Card holder data records must be fully configurable. The minimal number of card holder data records is 40. These data records can be presented in card holder field tabs. The card holder data fields can be used as additional information for card holders, card holder pop–up view used in automated badging design and used for report filtering.
Card personalization
Badges can be personalized and printed directly from the software using a badge printer with a windows driver. For the automation of designing the badge layout per card holder the below data can be user:
- At least 40 personalized card holder data records.
- Imported or captured card holder photos and signatures.
- Imported logos and pictures
In addition the badging interface must allow:
- Single and double-sided printing
- Magnetic stripe encoding
- Barcode printing
Automation / integration
To limit the wiring required, when an alarm is triggered or an event appears on an access controller the supervision software must be able to generate an action on another access controller, intrusion unit or Network /Digital video recorder.
4.3. Video surveillance management
It must be possible to extend the supervision system with Network Video Recorders (NVR), Digital Video Recorders (DVR) and matrix switches.
Supervision system and Video hardware requirements
The supervision system must be able to control and monitor 4, 8, 16 and 32-channel NVR / DVRs and display 16 cameras simultaneously in real time and recorded video.
The supervision system must be capable of controlling and monitoring cameras and directing the motorized domes (PTZ camera) manually and automatically to presets.
The PTZ cameras can be connected via the TCP/IP, RS485 or RS232 network depending on the type of NVR or DVR.
Video interface operation and links in the supervision system
The Video interface is part of the supervision system and must be designed to:
- Display up to 16 cameras simultaneously in real time (live) and recorded video (play back), where all cameras must be connected to a NVR or DVR
- Display playback video images using the time indicators in the video interface and in the camera display menu.
- Select a camera in real time (live) from a graphic floor plan, and control map or an alarm screen.
- Display a PTZ dome camera with a fixed preset for that camera, set up by clicking on the camera icon in the floor plan. Multiple presets are available per PTZ camera in the graphical floor plan.
- Control a PTZ camera from the video interface using dragging the mouse pointer in the video image and zooming via scroll wheel. Buttons for pan, tilt and zoom are available for the PTZ video image.
- Define a home preset position and home preset time per PTZ camera after inactivity from the operator, allowing the supervisor system to keep the camera images in the best and desired possible position.
- Digitally zoom in and out in live and play back images for both stationary and PTZ cameras
- Allow the operator to display multiple video live and recorded images in 1x1, 2x2, 3x3, 4x4, 6, 10 and 13 image format.
- Select full screen or tile view to watch a video. At any time, the operator must be able to point at a specific video image and bring it up in full screen format. In addition, when using full screen view, the operator must be able to interrupt and select another image display mode.
- Allow access to the surveillance operator to all camera commands (PTZ function). Command icons can be used to rotate the camera, zoom in and out and focus (focus, iris).
- Allow the operator to store video clips and snapshots on the Workstation / Server. It must be possible to export the video clip in authentic format, to prevent tampering of the video footage.
- Allow the operator to mirror, flip and enhance the live and recorded video images on the fly.
Events / alarms with video recording/live display
All alarms and events from access, intrusion and the Video surveillance system in the supervision system must be allowed to be associated with up to 4 cameras for recording and display purposes. Depending on the type of DVR / NVR the recording is either continuous or can be set up for every camera independently with start/stop recording with specified frame rate and resolution, with defined pre recording times and clip lengths.
On incoming alarm, up to 4 cameras will be displayed live in the video interface.
For the live display of PTZ cameras, a preset position can be defined per type of alarm / event. On incoming alarm, the camera will be displayed live in the video interface with the defined preset position. Home preset return and home preset time can be set up per alarm type. Manual operator PTZ control override must be possible.
Per priority of alarm/event the recording speed and PTZ preset position can be prioritized.
From the alarm view or event log (access authorized, refused, door still open, door forced etc.) it must be possible to select the associated camera(s) for playback of recorded video or live view.
Operator reporting /log with video footage
The operator must have access to the full list of the events that have triggered a video recording. To facilitate the operator's task, all the events related to a video recording will appear in the log in blue, accompanied by a camera icon. It must be possible to specify the time range and the desired event type(s). Once all the information has been completed, the system will run a search and display all of the events associated with the query. It will then be possible to display the video images for each of the events shown.
DVR and camera status
DVR and camera system information (on-off line, video loss) shall be displayed in the supervision system as event / alarm.
Depending on the NVR / DVR type and camera type motion detection should be an additional event / alarm
Automation / integration
- It will be possible to display the video images for each of the video events shown
To limit the wiring required, when an alarm is triggered or an event appears on a Network/Digital video recorder or camera the supervision software must be able to generate an action on another access controller, intrusion unit or Network /Digital video recorder.