Professional Documents
Culture Documents
CONTENTS
BAGGAGE SCANNER
METAL DETECTOR
VOL – I
TECHNICAL SPECIFICATIONS
1.0 STANDARDS
The CCTV & ACS for GODREJ COMMERICAL HUB, HEBBAL, BANGALORE shall be designed
and installed as per Client requirement, this tender specification and tender drawings.
1.1 CLASSIFICATION
The proposed GODREJ COMMERICAL HUB, HEBBAL, BANGALORE will be utilized as office
occupancy.
The scope of work includes complete design, engineering with necessary design calculations,
Fit – up details, supporting details, manufacture / fabrication, supply, storing, installation /
erection, testing and commissioning the ELV Systems as detailed in the tender documents. The
quoted rates shall also include complete builder‘s work i.e. chasing, chipping and making good
the same of walls, floors etc for concealment of conduits or pipes, wherever applicable, with all
necessary accessories as per specifications for the project.
The tender drawings describe the intent and detail of the design for each of the ELV systems.
The contractor shall upon the award of the work, prepare and submit detailed shop drawings
providing all necessary equipment and installation details to carry out the work at site. Final flow
and pressure calculations on licensed computerized software shall also be submitted in
verification of the design. These shall be submitted to the Employer/Consultant for approval and
the work shall be commenced only after the approval of drawings and calculations by the
Employer/Consultant. The design has to be validated after installation by exhaustive field
testing.
If desired and required the contractor shall obtain approval of the installation from the Client,
Architects, PMC & Consultants. Successful Bidder shall be responsible for preparation of
documents / applications / drawings & hydraulic calculations and follow-up action at all stages,
(Drawing / completion) arranging inspections, revisions / modifications for obtaining approval
from Client, Architects, PMC & Consultants within the overall completion period stipulated in
the Tender. The Contractor shall also make payment, if applicable, of all statutory payments like
payment for Client, Architects, PMC & Consultants approval etc. which shall be reimbursed
by the client against receipts, in case.
The contractor shall guarantee both the material and workmanship of first class quality
corresponding to standard engineering practice. Any defective materials/workmanship shall be
rejected and the contractor has to rectify/ replace the rejected material / work at his own cost.
Original guarantee certificate for all the materials supplied shall be handed over to the clients
as part of the handover documentation. Final work completion certification shall be given only
after receipt of all necessary documents as part of the handover process.
List of data / documents / drawings to be submitted along with bid shall be as mentioned
below:
List of data / documents / drawings to be submitted for approval after the award of contract shall
be as stated below:
1) Material submittals for all the material proposed with manufacturer‘s original catalogue
/ literature / data sheets.
2) Manufacturer‘s Quality Assurance Plan for all equipment supply in scope. Contractor‘s
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 6 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
The contractor shall be responsible for training of the Employer's personnel in the operation
and maintenance of the system and conduct demonstration. Site Training Manual shall be
submitted at least 2 months prior to the completion of work and readiness of the systems for
testing and commissioning. The rates quoted shall be inclusive of submitting 6 sets of the
following documents (HARD COPIES) along with CDs (Soft copy):
9. Undertaking that all the materials supplied by the Direct Contractor at site are fully tax
paid and shall produce all documentation for satisfaction of the Employer /
consultants
/ Architects / PMC or taxation authorities. Submission of the above documentation shall form a
precondition for final acceptance of the plant and installation and final payments.
SECTION – IV
General
The network (IP) fixed Dome camera shall be with 2Mega Pixel, Varifocal 2.8-12mm lens, POE
o H. 265 compression algorithm and TCP/IP transmission.
The camera shall Be designed to provide video streams in HDTV 720p at up to 30 frames per
second in Motion JPEG and H.265. Supporting resolutions up to 1280x800 pixels.
Be equipped with a slot for microSD /microSDHC/ microSDXC memory card expansion,
supporting memory up to 64 GB.
Be manufactured with vandal proof aluminum body providing encapsulated electronics.
Hardware
Video
Resolution
The camera shall be able to deliver at least two individually configured full resolution video streams
over IP networks.
Supported video resolutions shall include:
640x480 (4:3)
800x600 (4:3)
1280x720 (16:9) (HDTV 720p)
1280x800 (16:10) (1MP)
1920x1080 (16:10) (2MP)
The camera shall be able to provide both landscape format (4:3 and 16:9 aspect ratio) as well
as corridor format (3:4 and 9:16 aspect ratio).
Encoding
Transmission
Image control
The camera shall incorporate Automatic and Manual White Balance.
The camera shall incorporate an electronic shutter operating in the range 1/6 and 1/8.000
second. Predefined modes for Prio low noise, Prio motion and Standard mode.
The camera shall be equipped with Wide Dynamic Range functionality - dynamic contrast.
The camera shall provide backlight compensation.
The camera shall support manually defined values for:
Color level
Brightness
Sharpness
Contrast
The camera shall allow for rotation of the image in steps of 90º.
IR Illumination
The camera shall be equipped with built-in IR LEDs with adjustable angle of illumination and
intensity.
The IR LEDs shall have a range of minimum up to 10 m (33 ft).
The IR LEDs shall emit light with a wavelength of 850 nm.
Functionality
Web server
The camera shall contain a built-in web server making video and configuration available to
multiple clients in a standard operating system and browser environment using HTTP, without
the need for additional software.
Optional components downloaded from the camera for specific tasks, e.g. Active X, shall be
signed by an organization providing digital trust services, such as Verisign, Inc.
IP addresses
The camera shall support both fixed IP addresses and dynamically assigned IP addresses
provided by a Dynamic Host Control Protocol (DHCP) server.
The camera shall allow for automatic detection of the Camera based on UPnP and Bonjour
when using a PC with an operating system supporting this feature.
The camera shall provide support for both IPv4 and IPv6.
Event functionality
The camera shall be equipped with an integrated event functionality, which can be trigged by:
Video Motion Detection
Schedule
Camera tampering
External input
Embedded third party applications
Edge storage disruption detection
Response to triggers shall include:
Notification, using TCP, SMTP or HTTP
Image upload, using FTP, SMTP or HTTP
Edge storage
The camera shall support continuous and event controlled recording to:
Local memory added to the cameras SD-card slot
Network attached storage, located on the local network
The camera shall be able to detect and notify Edge storage disruptions
Protocol support
The camera shall incorporate support for at least IP, HTTP, HTTPS, SSL/TLS, TCP, ICMP,
SNMPv1/v2c/v3 (MIB-II), RTSP, RTP, UDP, IGMP, RTCP, SMTP, FTP, DHCP, UPnP,
ARP, DNS, DynDNS, SOCKS, NTP, CIFS/SMB and Bonjour.
The SMTP implementation shall include support for SMTP authentication.
Text overlay
The Camera shall:
Provide embedded on-screen text with support for date & time, and a customer-specific
text, camera name, of at least 45 ASCII characters.
To ensure accuracy, the camera shall accept external time synchronization from an NTP
(Network Time Protocol) server.
Provide the ability to apply privacy masks to the image.
Allow for the overlay of a graphical image, such as a logotype, into the image.
Security
The camera shall:
Support the use of HTTPS and SSL/TLS, providing the ability to upload signed certificates
to encrypt and secure authentication and communication of both administration data and
video streams.
Support IEEE 802.1X authentication.
Provide support for restricting access to pre-defined IP addresses only, so-called IP
address filtering.
Restrict access to the built-in web server by usernames and passwords at three different levels.
API support
The camera shall be fully supported by an open and published API (Application
Programmers Interface), which shall provide necessary information for integration of
functionality into third party applications.
The camera shall conform to ONVIF Profile S or ONVIF Version 1.01 or higher as defined
by the ONVIF organization, and shall be upgradable at any time.
Embedded applications
The camera shall provide a platform allowing the upload of third party applications into the
camera.
The camera vendor shall provide a compatibility tool for the application vendor to verify the
stability and performance impact of their uploaded application.
which can be used as a pixel counter identifying the size of objects in number of pixels.
All customer-specific settings shall be stored in a non-volatile memory and shall not be lost
during power cuts or soft reset.
Access logs
The camera shall:
Provide a log file, containing information about the 250 latest connections and access
attempts since the unit‘s latest restart. The file shall include information about the
connecting IP addresses and the time of connecting.
Provide a connection list of all currently connected viewers. The file shall include
information about connecting IP address, time of connecting and the type of stream
accessed.
Camera diagnostics
The camera shall:
Be equipped with LEDs, capable of providing visible status information. LEDs shall indicate
the camera‘s operational status and provide information about power, communication with
receiver, the network status and the camera status.
Be monitored by a Watchdog functionality, which shall automatically re-initiate processes
or restart the unit if a malfunction is detected.
Interfaces
Network interface
The camera shall be equipped with one 100BASE-TX Fast Ethernet-port, using a standard
male
RJ45 connector and shall support auto negotiation of network speed (100 MBit/s and 10
MBit/s) and transfer mode (full and half duplex).
Inputs/Outputs
The camera shall be equipped with one digital (alarm) input and one digital output,
accessible via a removable terminal block. This input shall be configurable to respond to
normally open (NO) or normally closed (NC) dry contacts.
Enclosure
Power requirements
Power over Ethernet according to IEEE 802.3af/802.3at Type 1 – Class 2.
Environmental
Hardware
The camera shall:
Use a high quality IR-sensitive progressive scan sensor.
Be equipped with a removable IR-cut filter, providing so-called day/night functionality.
Be equipped with a high quality varifocal lens with automated iris functionality.
Be equipped with remote back focus functionality.
Provide pictures down to 0.1 lux in color and down to 0.02 lux in B/W.
Support local memory by providing a microSD/microSDHC/microSDXC card slot,
supporting memory up to 64 GB.
Video
Resolution
The camera shall be able to deliver at least two individually configurable full resolution full
frame rate video streams over IP networks.
Supported video resolutions shall include:
o 640x480 (4:3)
o 800x600 (4:3)
o 1280x720 (16:9) (HDTV 720p)
o 1280x800 (16:10) (1MP)
o 1920x1080 (16:10) (2MP)
Encoding
The camera shall:
Support Motion JPEG encoding in a selectable range up to 30 fps (60Hz), 25 fps (50Hz) in
all resolutions.
Support Baseline Profile H.265 encoding with motion estimation in up to 30 frames per
second in all resolutions.
Support Main Profile H.265 encoding with motion estimation and context-adaptive binary
arithmetic coding (CABAC) in up to 30 frames per second in all resolutions.
Be able to provide independently configured simultaneous H.264 and Motion JPEG
streams.
Support both Constant Bit Rate (CBR) and Variable Bit Rate (VBR) in H.264.
Provide configurable compression levels.
Transmission
The camera shall allow for video to be transported over:
HTTP (Unicast)
HTTPS (Unicast)
RTP (Unicast & Multicast)
RTP over RTSP (Unicast)
RTP over RTSP over HTTP (Unicast)
The camera shall support Quality of Service (QoS) to be able to prioritize traffic.
Image control
The camera shall incorporate Automatic and Manual White Balance
Contrast
The camera shall incorporate a function for optimization of low light behavior.
Audio
The camera shall support two-way full duplex audio:
Input sources
External microphone
External line device
Output sources
External line device
Encoding
The camera shall support:
AAC LC at 8/16 kHz
G.711 PCM at 8 kHz
G.726 ADPCM at 8 kHz
Functionality
Web server
The camera shall contain a built-in web server making video and configuration available to
multiple clients in a standard operating system and browser environment using HTTP, without
the need for additional software.
Optional components downloaded from the camera for specific tasks, e.g. Active X, shall be
signed by an organization providing digital trust services, such as Verisign, Inc.
IP addresses
The camera shall support both fixed IP addresses and dynamically assigned IP addresses
provided by a Dynamic Host Control Protocol (DHCP) server.
The camera shall allow for automatic detection of the Camera based on UPnP and Bonjour
when using a PC with an operating system supporting this feature.
The camera shall provide support for both IPv4 and IPv6.
Edge storage
The camera shall support continuous and event controlled recording to:
Local memory added to the cameras memory card slot
Network attached storage, located on the local network
The camera shall be able to detect and notify Edge storage disruptions
Protocol support
The camera shall incorporate support for at least IP, HTTP, HTTPS, SSL/TLS, TCP, ICMP,
SNMPv1/v2c/v3 (MIB-II), RTSP, RTP, UDP, IGMP, RTCP, SMTP, FTP, DHCP, UPnP, ARP,
DNS, DynDNS, SOCKS, NTP, CIFS/SMB and Bonjour.
Text overlay
The Camera shall:
Provide embedded on-screen text with support for date & time, and a customer-specific text,
camera name, of at least 45 ASCII characters.
To ensure accuracy, the camera shall accept external time synchronization from an NTP
(Network Time Protocol) server.
Provide the ability to apply a privacy mask to the image.
Allow for the overlay of a graphical image, such as a logotype, into the image.
Security
The camera shall:
Support the use of HTTPS and SSL/TLS, providing the ability to upload signed certificates to
encrypt and secure authentication and communication of both administration data and video
streams.
Support IEEE 802.1X authentication.
Provide support for restricting access to pre-defined IP addresses only, so-called IP address
filtering.
Restrict access to the built-in web server by usernames and passwords at three different
levels.
API support
The camera shall be fully supported by an open and published API (Application Programmers
Interface), which shall provide necessary information for integration of functionality into third
party applications.
The camera shall conform to ONVIF Profile S or ONVIF Version 1.01 or higher as defined by
the ONVIF organization, and shall be upgradable at any time.
Embedded applications
The camera shall provide a platform allowing the upload of third party applications into the
camera.
The camera vendor shall provide a compatibility tool for the application vendor to verify the
stability and performance impact of their uploaded application.
User logs
The camera shall:
Provide a log file, containing information about the 250 latest connections and access attempts
since the unit‘s latest restart. The file shall include information about the connecting IP
addresses and the time of connecting.
Provide a connection list of all currently connected viewers. The file shall include information
about connecting IP address, time of connecting and the type of stream accessed.
Camera diagnostics
The camera shall:
Be equipped with LEDs, capable of providing visible status information. LEDs shall indicate the
camera‘s operational status and provide information about power, communication with
Interfaces
Network interface
The camera shall be equipped with one 100BASE-TX Fast Ethernet-port, using a standard RJ-
45 socket and shall support auto negotiation of network speed (100 MBit/s and 10 MBit/s) and
transfer mode (full and half duplex).
Inputs/Outputs
The camera shall be equipped with one digital (alarm) input and one digital output, accessible
via a removable terminal block. This input shall be configurable to respond to normally open
(NO) or normally closed (NC) dry contacts.
Serial interface
The camera shall be equipped with one RS-485/422 serial port. Audio
The camera shall be equipped with one 3.5 mm jack for line/mic input and one 3.5 mm jack for
line output.
Enclosure
Be manufactured with an all-metal body
Power requirements
Power over Ethernet according to IEEE 802.3af - Class 3 .
Environmental
1.2 Live Display Mode Features. A live display mode shall be used to view live video,
Point of Sale data, and alarm information. The live display mode shall have the
following features to navigate and view live video:
1.2.1 Layout Icons – The VMS shall be used to organize the camera video view
panel in the following patterns:
1.2.1.1 1-camera (full-screen) layout
1.2.1.2 4-camera (2x2) layout
1.2.9 PTZ Control Icon – The VMS shall provide PTZ control that allows the
maneuvering of a PTZ camera. The VMS shall also allow the calling of PTZ
presets by either right-clicking on the camera cell and then selecting the
PTZ Preset, or by clicking the PTZ Control Icon and then pressing the PTZ
Preset number.
1.2.10 Date and Time – The VMS shall display the current date and time.
1.2.11 Soft Trigger Icon – The VMS shall allow the customization of the user
interface to allow software triggers to be shown. The VMS shall allow the
user to pick their own icon and select the software triggers to display in the
client. The VMS shall also display the status of any soft triggers on
connected VMS servers.
1.2.12 Event Buttons - The VMS shall allow the user to monitor live video from a
remote location using a separate client application. The VMS shall allow the
user to send a notification (Soft Trigger) via the server housed at the
location being monitored. The VMS Software client shall allow the
activation of Soft Triggers from the Live Video page by clicking a pre-
configured icon.
1.3 Pan, Tilt, and Zoom (PTZ) Controls.
1.3.1 The VMS software shall control PTZ cameras and be used to maneuver a
mechanical PTZ camera and digitally pan, tilt, and zoom on any video. The
following methods of controlling a PTZ camera shall be available:
1.3.1.1 PTZ graphics control windows
1.3.1.2 Live graphic overlay PTZ control icons
1.3.1.3 Keyboard control (Up, Down, Left, Right Arrows; Page Up, Page Down for
Zoom)
1.3.1.4 PTZ presets
1.3.1.5 Digital PTZ
1.3.1.6 USB joystick to control PTZ cameras
1.3.1.7 Proportional PTZ control by clicking the mouse in the center and moving it
1.4 Auto Replay of Recorded Video from Live Display Mode.: The VMS software shall
replay recorded video from the Live Display Mode if the user right-clicks in the
appropriate video view panel and selecting Replay. The user shall have the option of
reviewing video in increments of 5 or 30 seconds; or 1, 5, or 15 minutes. The Replay
window shall open and begin downloading the recorded video. A Scrub Bar shall track
the progress of the download. The total number of frames in the video segment and
the number of frames that have been downloaded shall be displayed in the status bar.
The download shall end if the user clicks a Stop Download button.
1.5 Virtual Matrix Switching. The VMS software shall activate virtual matrix switching if
the user right-clicks in one of the live video panels and selects Event Monitor from a
drop-down dialog menu and then selects a profile. Virtual Matrix Switching shall
automatically show video as it is triggered. Virtual Matrix Switching shall be stopped if
the user right-clicks in the active video panel and disables the active event
monitoring profile.
1.6 Event Monitoring: The VMS software shall activate event monitoring if the user right-
clicks in one of the live video panels and selects Event Monitor from a drop-down
dialog menu and then selects a profile. An Event Monitoring profile shall display a list
of events that the user can click on to view. If a profile is configured for Event
Monitoring mode, an Event Monitoring Box shall appear below a live video panel. The
box shall be moveable and resizable. When a video event takes place, it shall be
automatically listed in the box that can be clicked on to display the video. When
events occur on two cameras at the same time, each event can be viewed for as long
as necessary. Event Monitoring shall be stopped if the user right-clicks in the active
video panel and disables the active event monitoring profile.
1.7 Viewing Logical Camera Groups: The VMS software shall have a feature for viewing
logical groups of cameras. The VMS software shall also have a feature creating
camera groups. This shall allow efficient viewing of cameras in a logical order. Once
camera groups are configured, cameras shall be selectable in those groups if the user
clicks on the Group button in the Navigation Pane.
1.8 Creating, Saving and Accessing Views: The VMS software shall have a feature to
organize your cameras into preset Views by selecting a Layout button in the live
mode and dragging the cameras to the appropriate spot on the Video View Panel.
After saving a view, it shall be accessed by clicking the View button from the
Navigation Pane. Selecting a view from the Live Views Site Tree shall display the
camera layout in the Video View Panel. The VMS software shall have the capability to
create and organize views into folders.
1.9 Video Tours: The VMS software shall have the capability to automatically cycle
through two or more saved views to create a Video Tour by selecting the desired
views typing a description of the tour. A dwell time shall determine the amount of
time, in seconds, that each view remains in the Video View Panel before the
next view is displayed. The tour shall be activated by clicking on the saved
tour description icon visible in the View Navigation pane.
1.10 Search Mode Overview: The VMS software shall be used to search for and play
back recorded video, audio, and events from VMS servers. The system shall also be
capable of performing searches on multiple camera based on specific criteria. The
VMS search software shall have the following features:
1.10.1 Input Selection Tree – a list of camera(s), audio input(s), or text data to
search.
1.10.2 Navigation Pane – a list of cameras, video, audio, and events organized by
cameras, groups, maps, and views.
1.10.3 Video Time Line – a time line of video displayed in increments of 5 minutes,
or 1, 8, or 24 hours.
1.10.4 Zoom In (+) and Zoom Out (-) Buttons – zooms in and out on the video time
line.
1.10.5 Camera Selection List – a list of cameras that have been selected from the
camera selection tree.
1.10.6 Video Cursor – selects the segment of video to play back. Single-clicking
shall move the video cursor to a new location; double-clicking shall start
video playback.
1.10.7 Recorded Bar – bars that represent recorded video or audio.
1.10.8 Video Playback Controls – includes the following controls:
1.10.14 Scrub Bar and Scrub Handle – used to quickly scrub back and forth through
video.
1.10.15 Stop Download Button – used to stop the download.
1.10.16 Smart Search – allows search for occurrences of motion in specific areas of
a video window.
1.11 Multi Camera Search and Playback: The VMS software shall have the capability to
search for and play back video from multiple cameras simultaneously. All recorded
video shall be played back and displayed in a synchronized multi camera layout in
one of the following screen layouts:
1.11.1 4-camera (2x2) layout
1.11.2 9-camera (3x3) layout
1.11.3 12-camera (4x3) layout
1.11.4 16-camera (4x4) layout
1.11.5 20-camera (5x4) layout
1.11.6 30-camera (6x5) layout
1.11.7 48-camera (8x6) layout
1.11.8 Selected pre-configured views
1.12 Audio Search and Playback: The VMS software shall allow search and play back of
audio in synchronization with video.
1.13 Exporting Files: The VMS software shall have the capability to export video, maps,
Point of Sale data, and audio files. To export a file, the user shall mark the starting
and ending point of the video to export. After the VMS software has exported a video
and/or audio file, it shall provide an option to burn the data to a CD or DVD. The VMS
software shall provide the option of exporting the file in the following formats:
1.13.1 Standalone Exe (*.exe) – includes an executable player with the video and
audio data
1.15 Standalone Player: The VMS software shall have the capability to export video and
audio files with an executable Standalone Player. Double-clicking on the executable
Standalone Player shall start the application and open the video and/or audio
files. The Standalone Player shall have the following features:
1.15.1 Screen Layouts:
1.15.1.1 1-camera layout – full-screen layout
1.15.1.2 4-camera (2x2) layout – simultaneous multi-camera playback
1.15.1.3 16-camera (4x4) layout – simultaneous multi-camera playback
1.15.2 Video Playback Controls – includes the following playback controls:
1.15.2.1 Play video in reverse fast (double) speed
1.15.2.2 Play video in reverse in normal speed
1.15.2.3 Stop video play
1.15.2.4 Play video forward in normal speed
1.15.2.5 Play video forward in fast speed
1.15.2.6 Play video forward one frame at a time
1.15.2.7 Play video backward one frame at a time
1.15.3 Scrub Bar and Scrub Handle – used to quickly scrub back and forth through
video.
1.15.4 Camera and Audio Tree – used to select video and audio for playback
1.15.5 File
1.15.5.1 Open
1.15.5.2 Save Image
1.15.5.3 Copy to Clipboard
1.15.5.4 Save as AVI, PS, or QuickTime
1.15.5.5 Print
1.15.5.6 Exit
1.15.6 Options:
1.15.6.1 Show Camera Name
1.15.6.2 Show Timestamp
1.15.6.3 Show Status Boarder
1.15.6.4 Time-lapse Playback Interval
1.15.6.5 Show Camera Tree
1.15.6.6 Show Full Screen
1.15.6.7 Font
1.15.7 Tools
1.15.7.1 Authenticate- used to verify the video hasn‘t been tampered with or
corrupted. A keyed-Hash Message Authentication Code, or HMAC, is a
type of message authentication code (MAC) calculated using a specific
algorithm involving a cryptographic hash function in combination with a
secret key. As with any MAC, it can be used to simultaneously verify both
the data integrity and the authenticity of the data.
1.15.8 Right Click on Video:
1.15.8.1 Clear this video panel
1.15.8.2 Digital PTZ
1.16 Setup Mode Overview and Features: The VMS software shall be used by
Administrators and Power Users to configure systems. A Setup Mode shall consist of a
hierarchy of icons for configuring the systems, also called a configuration tree.
Clicking on any of the icons in the configuration tree shall display a new screen for
configuring the selected item. The configuration tree shall consist of the following
icons and features:
1.16.1.1 My Systems
1.16.1.2 Adding System
1.16.1.3 Client Setup
1.16.1.4 Joystick Setup
1.16.1.5 Enterprise User Setup
1.16.1.6 Event Monitoring
1.16.1.7 Group Setup
1.16.1.8 Map Setup
1.16.1.9 System Information
1.16.1.10System Setup
1.16.1.11Add IP Cameras
1.16.1.12IP Camera Recording
Setup 1.16.1.13IP Camera Setup
1.16.1.14Audio Input Setup
1.16.1.15Trigger Input Setup
1.16.1.16Alarm Output Setup
1.16.1.17Storage Setup
1.16.1.18Serial Profile Setup
1.16.1.19Serial Port Setup
1.16.1.20Notifications
1.16.1.21Instant Recall Setup
PTZ camera view shall move north when the joystick is moved down and South when
it is moved up. This shall be reversed by deselecting a Invert Y Axis checkbox. The
camera or camera view shall zoom in or out by twisting the joystick to the right or left,
depending on personal preference. When the Invert Rudder checkbox is selected, the
camera shall zoom in by twisting the joystick the left and zoom out when it is twisted
to the right. Deselecting the Invert Rudder checkbox shall reverse the zoom control.
One or more of joystick buttons shall be programmed by using a drop-down menu to
select the following settings:
1.20.1 PTZ Zoom In/Out
1.20.2 Increase/Decrease PTZ Zoom Speed
1.20.3 Increase/Decrease PTZ Pan/Tilt Speed
1.20.4 Next/Previous Video Panel
1.20.5 View This Camera Only
1.20.6 Toggle Digital PTZ
1.20.7 Traverse the Camera Tree
1.20.8 Go to PTZ Preset Number 1-16
1.20.9 Open the Find Camera dialog
1.21 Enterprise User Setup: The VMS software shall allow the configuration of the same
user accounts across several servers from the same interface. The Enterprise User
Setup shall allow an administrator to create a user account, assign a password, and
assign a Group, and then choose the servers on which the user should have
permissions.
1.22 Event Monitoring Setup: The VMS software shall be used to configure the VMS Client
to react to events that take place on servers to which it is connected. To activate the
event monitoring feature, the user shall create and define a new event monitoring
profile a set of actions such as the playing of live video or an alarm sound triggered
by sources such as video motion and input triggers. Each profile
shall then be activated and assigned to a specific video panel by the user. The
following event monitoring profiles shall be available:
1.22.1 Virtual Matrix: A Virtual Matrix profile shall automatically show video as it is
triggered. For example, if there is a series of entrances in one profile, each
time any of the entrances is triggered the video panel could switch to the
camera displaying the most recent door motion.
1.22.2 Event Monitor: An Event Monitor profile shall display a list of events that the
user can click on to view. For example, instead of the video panel
automatically switching to the camera displaying the most recent door
opening, the event could be added to a list. The user could then click on
the item to display the video, even if events occur on two cameras at the
same time. Instead of seeing each event for a split second, the user shall
see each event for as long as needed. After the Event Monitoring Profile s
have been created, the user shall activate them in the VMS Client software.
1.23 Group Setup: The VMS software shall be used to create logical groups of cameras
from cameras connected to a single or multiple VMS servers. The logical groups of
cameras shall be displayed in the navigation tree hierarchy of cameras. For example,
with two VMS servers with 50 IP cameras each in a four story building and 25 cameras
on each floor, the user could create four named groups consisting of 25 cameras
each. In addition to monitoring live video, groups shall be used for searching video.
In the search video feature, the user shall click on the Groups navigation pane then
select the group and search.
1.24 Map Setup: The VMS Software shall allow the user to place video cameras on a map
to show where they are located and which direction they are facing. The map shall
be created using any readable graphics format. The VMS software shall be able to
display live and recorded video from this map and detect any events or status
changes occurring on those cameras. When using an Enterprise class license, the
VMS software shall be able to embed maps with in maps. When an event happens
on a map that is embedded inside of a map, it shall display the alert on all parent
maps and change the color of icons on the parent map and all subsequent parent
maps.
1.25 System Information: The VMS software shall be used to display system information
about users that are currently logged into the system, plug-in file version information
number and status, and a system log that contains a detailed history of the process
that occur on the system. The system log shall be viewed by selecting the start and
end date and time and clicking on the search button. The system log shall also be
exportable to a file name and opened with a text editor. A log settings feature shall
give the user the ability to set the maximum days that logged alarms and the system
logs are kept on the system.
1.26 System Setup: The VMS software shall have the following features to set up VMS
servers:
1.26.1 System name
1.26.2 Time and date
1.26.3 Time zone
1.26.4 Time server
1.26.5 Network settings (hostname, IP address, network, gateway and DHCP status)
1.26.6 Bandwidth settings
1.26.7 License key – required to add the number of IP cameras needed for the
system. A user shall obtain a license key by providing your network adapter
hardware MAC address to the VMS software manufacturer. The VMS
software manufacturer shall provide a license key that must be entered
1.28 IP Camera Recording Setup: After IP cameras have been added to the VMS server,
the VMS software shall be used to enable IP cameras to record video, select the
recording resolution, and select the image-per-second (IPS) recording rate. Each IP
camera shall be individually configurable. If a camera has been connected to a VMS
server and the camera is producing a video signal, the VMS Client software shall
automatically detect the video signal and record video. To disable recording, the user
shall select a checkbox. The VMS software shall be used to change individual
camera resolutions by clicking on a record resolution drop-down menu and selecting
QCIF, CIF, 2CIF, D1, VGA, 1M, 1.2M, 1.3M, 1.9M, 2M, 3.1M, 5M, or 10M
resolution.
Camera resolutions shall vary depending on the IP cameras selected and added to the
VMS server.
1.29 IP Camera Setup: The VMS software shall be used to configure individual IP camera
settings such as camera name, onscreen display, PTZ preset settings and tours,
digital PTZ presets, video settings (brightness, contrast, saturation and sharpness),
recording quality, compression format (MPEG-4, H.264 or JPEG), pre-motion
recording, crop window, motion masks (sensitivity, percentage, include, and
exclude), and video masks. Some of the settings shall vary depending on the type,
model, and features of IP camera selected and added to the VMS server.
1.30 Audio Input Setup: The VMS software shall be used to configure audio input names
and enable audio inputs for recording. The VMS software shall be installed with the
audio inputs disabled due to legal restraints on audio recording in some jurisdictions.
To assign a new, logical name for the audio input channel, the user shall highlight
the default name and type the new name. The user shall enable the audio input
channel by selecting a checkbox. A listen feature shall allow verification of the audio
input connected to a channel. The user shall select a checkbox to hear the audio
from the corresponding input channel. To stop the live audio feed, the user shall
1.32 Alarm Output Setup: The VMS software shall be used to configure alarm output
names and set the Normal State of the IP camera‘s output triggers. The user shall
assign new logical names and change the Normal State of the Alarm Outputs from the
default of Hi (5 VDC) to Lo (0 VDC). The Status shall be NORMAL in either the Hi or Lo
Normal State setting until an event from the Event Linking feature activates an
ALARM status. The user shall verify the proper operation of the output state by
observing the Status state, which switches between Normal and Alarm. By defa ult,
the Normal State shall be set to Hi (5 VDC).
1.33 Storage Setup: The VMS software shall be used to configure hard drives for video
storage. The VMS software shall be installed on your C: drive, and separate disk
drives shall be used for video storage. The video storage disk drives shall be designed
for high-duty-cycle. Disk drives shall be visible during configuration for review and
adjustment. The VMS software shall enable or disable a drive for video storage by
selecting or deselecting the enabled feature during storage setup. The entire disk
drive shall be used or an upper limit shall be selected by adjusting a video space
slider. The VMS software shall have a feature to display the used space that displays
the amount of the disk drive capacity used for storage. The VMS software shall
display the status of a healthy or missing disk drive. Another feature shall indicate
the age of the oldest video recorded on this system. The VMS software shall capture
images periodically (time lapse recording) even if the cameras are set to record only
upon motion or alarm. The user shall select the desired time lapse increment in
hours, minutes, or seconds. Selecting zero shall disable this feature. The VMS shall
also have the ability to enforce storage rules on a per-camera basis and allow the
user either to limit the number of days of recording or to retain the video for a specific
number of days. When the setting is configured to limit the number of days of
recorded video, the VMS software shall delete any video older than the selected
number of days. When the VMS software is configured to keep the video for a specific
number of days, it shall maintain the recorded video to the exclusion of recording all
other video.
1.34 Serial Profile Setup: The VMS software shall be used to create and view transaction
profiles so that character strings such as cash register receipts, ATM transactions, or
access control transactions can be viewed with live or recorded video. Event
keywords shall trigger a system alarm or action. Recorded video shall be searched
and retrieved using a search serial feature. The user shall also be able to indicate
the beginning and end of transaction key words.
1.35 Serial Port Setup: The VMS software shall provide two ways to receive serial data and
control PTZ cameras. The VMS software shall allow the user to create a physical
connection to the serial port or communications port on the back panel of the server.
The VMS software shall also allow the user to transmit serial data over a network
connection in ASCII format. The VMS software shall be used to configure serial ports
on the VMS server so that they can be used to communicate with serial devices suc h
as Point of Sale terminals or PTZ cameras. The VMS software shall provide a choice
for configuring the serial port, including Unused, POS (Point Of Sale), or PTZ (Pan Tilt
Zoom). The PTZ option is used to control the motion of a PTZ camera. The VMS
software shall default to Unused until it is otherwise configured. A unique name shall be
assigned to the port. The VMS software shall also allow the user to receive data over
the network using three different methods: HTTP, TCP, and sending data to a specific
port on the server.
1.36 Notifications: The VMS software shall be used to configure an e-mail server and
message profile that will send an email message when an event occurs. The user
shall use the Event Linking feature to configure the events that should cause an
email message to be sent. The E-mail Server Configuration feature shall allow the
user to configure the outgoing SMTP mail server that should be used to send email
from the VMS server. The VMS software shall also support SSL and TLS
connections for transmissions of the mail.
1.37 Instant Recall Setup: The VMS software shall have a feature to export a video
segment from specific cameras or audio inputs to a CD or DVD upon an input trigger
or other event being activated. The software shall also send an email or text
message notifying the recipient that the input trigger has been activated. The VMS
software shall be used to create a profile that determines the number of minutes of
recorded video that occurs before and after the instant recall is activated that is
recorded. The Event Linking feature shall be used to link the profile to the type of
event that should cause the video and audio segment to be exported.
1.38 Event Linking: The VMS software shall be used to connect different types of events,
such as input triggers, to a desired action such as recording video or triggering an
alarm. An event shall activate an action and be stored in a searchable database. The
VMS software shall recognize the following event types:
1.38.1 Video Motion
2. NVR Specification
2.1 2U/3U/4U Rack mountable Server
All 2U/3U/4U Rack mountable Servers shall have the following
specifications:
2.1.1 All-in-One Solution — Video recording, web/mobile client hosting, and local
live video display from the same server.
2.1.2 Network Video Recording Servers - IP Camera Servers — Record IP
cameras and encoders. Live and recorded video viewable through free
client application
2.1.3 Up to 64 IP Cameras per Server — shall support up to 16 / 32 IP cameras
per server. Continuously record up to 350Mbps (Windows) / 550Mbps
(Linux) of video.
2.1.4 Local Client Display Rate (fps) shall be 700@HD resolution (Windows)
900@HD resolution (Linux)
2.1.5 Solid state drives and RAID 5 shall provide uninterrupted operation
2.1.6 Shall be Pre-loaded with Professional VMS software for out-of-box simplicity
2.1.7 Mobile app for users to view video from anywhere
2.1.8 Hard Drives supported shall be 8nos
2.1.9 Maximum Storage shall be 80TB
2.1.10 Shall support 1 DVI-I + 1 HDMI + 1 Display Port + 1 VGA, maximum 2
simultaneous monitors
2.1.11 Operating system shall be windows10 / Ubuntu Linux 16.04
2.1.12 Operating System Drive shall be 120GB SSD
2.1.13 CPU: Gen 7 Intel® Core i3 / Intel® Core i5 or i7 (Optional)
Monitoring
Remote Desktop
HTTP monitoring
The IP Video Storage Array shall be installed with the Microsoft Windows Storage Server
2008 operating system
Cable
The SACMS shall be designed such that any point of failure within the system shall not
affect the normal operation of the other sub-systems. It shall continue to operate even if the
connection with the management software is not present.
The SACMS management software provided shall allow card personalization. That is, it
shall include a tool for designing badges that supports the importing of bitmaps, text and
database fields, such as name or badge number for creating of corporate badge designs
printable on a standard card printer that come with a Windows compliant printer driver.
The tenderer shall ensure that the system must be expandable and by adding new
component to the existing system will not affect its normal operation.
The tenderer shall design and decide depending on the occurring load, the SACMS to run
on one or more servers operating as one system. One of these servers shall operate as the
central or main server to the other. The operating system shall preferably be Windows
2003/2008 server or Windows XP SP2/3 or Windows 7.
Database for SACMS shall reside within the same server hardware. However, it shall be
possible to also separate the SACMS application software and its database should it be
necessary.
All alarms processing, logging, operator‘s response, data entry/input, graphical user
interface and other system operations and management functions shall be performed at
the SACMS workstations connected to the SACMS network. The operating system shall
preferably be Windows XP or Win 7
All SACMS servers and workstations shall be connected using a standard IP network over
the corporate Intranet or dedicated LAN/WAN. It shall also support the use of wireless
connection of mobile workstations, like laptop PC.
b. RAM: 16 GB or more
e. Resolution Support:
1280 by 1024
2048 by 768
2560 by 1024
The SACMS shall have a multi-level priority interrupt structure proven in multi-tasking and
multi-client real time applications. Simultaneous alarms/events monitoring by multiple
users, system supervision and history archiving shall be possible without degradation of any
functionality specified system or operation.
The supported multi-client application shall have the capability that separates message
distribution to dedicated operator or operator groups whom are permitted to operate on
those alarms or events. These shall include, but not limited to;
The SACMS shall provide the flexibility to use only single or same username and
password for both MS Windows and SACMS login at the workstation. It shall be an
advantage if the system can allow the option for utilizing MS Windows Domain login
username and password for direct log in to SACMS, such that double login can be avoided.
The SACMS shall allow the configuration for information access permissions, that is,
user/operator profile for the access on the master records and/or event data, the
permissions shall restrict to;
Read only
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 34 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
Communication and/or data exchange between the SACMS servers and all connected
workstations shall be encrypted with at least 128-bit data encryption according to a
certified algorithm.
The SACMS shall be able to provide and display the operating status of
workstations/operators.
The SACMS system shall be designed such that any failure of any sub-systems shall not
affect all the other sub-systems. This shall also apply to any loss of power supply or suffer a
loss in communications due to a break in the communication loop. In any case, each sub-
system shall continue to function in a fully operational state with no loss of functionality.
In the event of network communication failure between SACMS servers and workstations,
all access control components and sub-systems shall continue to operate and be able to
function independently. Once the network communication is re-established, individual
access control sub-system controller and/or server shall automatically synchronized its
transactions during the network downtime to the SACMS servers, without affecting the
normal operation of the system.
The SACMS server shall act as the source that provides time synchronization to all sub-
systems.
The SACMS shall have a modular structure that allow for future system expansion with
minimum cost and disruption to the existing operational system. Such upgrade shall not
make use of or compromise the spare requirement specified or utilizing or sharing any of
its functions.
The SACMS shall be made expandable to support an unlimited number of integrated
operator workstations.
The SACMS shall be able to make use of the existing open protocol drivers software
available running on any PC installed inside the corporate network, avoiding additional re-
installing of the same application
The Application Software (AS) proposed shall be proven to be robust and reliable prior to
being supplied, installed, tested and commissioned. It shall be user friendly and flexible
enough to provide interactive operator prompting to assist operator who are not familiar
with the system terminologies, operating system or menu structures, to be able to operate
the system with ease and minimal training.
The AS shall be of a web server based solution. Only Internet Explorer (IE7 or IE8) is
required for a workstation to access the SACMS server to start daily alarm monitoring and
management operation.
The SACMS AS proposed shall provide English descriptions and messages using both
text based menus and graphical icon displays.
The SACMS AS provided shall have support for central alarm monitoring and management;
it shall also provide a wide range of display and control features. It shall provide a
graphical user interface (GUI) that has the same look and feel regardless of which alarm is
activated and received
The SACMS AS shall provide practicable the central configuration platform or tool from
where everything concerning sub-systems, system behavior, access control cardholder
settings, display features, and authorizations are set up.
The SACMS AS shall provide an easy and intuitive way of defining/designing the system
behavior of alarms or events when they activate. It shall provide and allow system
administrator during configuration with the use of ‗IF‘ and ‗THEN‘ and ‗ELSE‘ or similar
conditional functions to define the behavior of individual or groups of alarm /event.
The events log database shall include an advanced filter functions such that archive can be
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 35 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
kept small and precise. If required, only desired information shall be archived.
The SACMS AS shall be capable for directly importing of site/building floor plan drawings or
maps that are of standard vector graphics format, such as AutoCAD DWF, used for
indicating meaningful location of the alarm activation in the GUI.
The drawing format for the location maps shall support a logical partitioning by defining
sub-areas inside the drawing, by marking the area and giving it a logical name.
A location tree and the location names shall be provided for in the GUI. Creation of the
location tree and the location names shall be simple by scanning the drawings for the pre-
defined logical sub-areas.
The SACMS AS shall provide a library of standard detector icons for intrusion detectors,
doors, readers, cameras, and so on. System administrator shall be able to place these
icons directly onto the drawing. All assigned control commands are provided when clicking
the icon.
The location and the relative size of an icon shall be pre-definable in the drawing, prior to
importing into the SACMS. In this case, it will save the system administrator‘s time during
configuration, as it could be done by the architect or draftsman.
The timer provided shall support time frames per weekday, public holidays, and individual
programmable special days as desired by the user.
The SACMS AS shall allow the manual and automatic printing of all alarm related
documents, including location maps, instructions, and alarm details, such as location,
detector address, and type.
The SACMS AS shall provide timer and schedule functions to support, but not limited to the
following;
time based display of information
time based automatic controls into any sub-system
time based access.
The SACMS Graphical User Interface (GUI) shall be of browser based using standard
Dynamic Hyper Text Mark-up language (DHTML) format, no separate software shall be
required at each operator workstation for purpose of system alarms/events monitoring and
operation.
The SACMS GUI shall support single or multi screen displays having multiple HTML
pages separately over a maximum of four(4) monitors per workstation by using a
corresponding video graphics card.
The SACMS shall provide a default GUI that is adequate and ready for used in normal
system operation. It shall support at least the following standard resolutions: 1280x1024
(1-monitor operation), 2048x768 and 2560x1024 (2-monitor operation).
The SACMS GUI shall allow easy customization using standard HTML editor, to create a
favorable look and feel that is unique to the user, yet contains all interface control
functions provided as in the default GUI.
The possible SACMS GUI customizations shall include, but not limited to the following:
The SACMS GUI shall provide and display a complete overview of the operating status of all
servers, workstations/operators, all the connected sub-systems, all panels and even the
status of individual detectors.
All connected system components shall be shown on the status tree where direct control
shall be possible by clicking on the icon or detector address.
The device overview shall support state filtering and/or sorting function to search for
specific device status, such as all detectors having malfunction state or all doors in opened
state. The states indicated in the device overview shall reflect exactly the same colour as
the detector icon shown in the location map.
Besides the status tree, the SACMS GUI shall have a location tree to allow easy selection of
locations and sub-locations, such as single floors or rooms. The location tree shall have no
limits in the number of levels or sub-levels.
Along with the location tree, the SACMS GUI shall display the location map that is in the
standard vector graphics format.
At the location tree, a single click on the location or sub-location shall show the assigned
map or sub-areas with all detector icons visible for that area.
The SACMS GUI shall provide a zoom and pan feature for zooming into a location and
move around inside the map, simply by using a standard PC mouse. It shall enable
operators to find a specific detector, door, or reader for fast control, such as open door
manually, switch on/off lights, show camera live image, and so on.
All icons shall be provided in a vector format, such that when the operator performing
zoom-in or out of the map, the icon size scales automatically to the view.
Moving the mouse cursor over a detector icon provides a tool tip with detailed detector
information, such as complete address, actual status, and detector type.
In the event of alarm activation, the alarm message shall be displayed at the destined
SACMS operator workstation together with an external audible siren or via PC internal
speaker. The detector that triggers the alarm, the relative icon found in the location map
shall change its colour and status graphically, reflecting to the state of the corresponding
alarm or event. For example, a red colour opened door icon shall be displayed when the
door is physically forced opened or the colour of the icon shall change from green-normal
to red-alarm instantly if the detector point is violated.
For the alarm sound generated from the PC internal speaker, standard formats such as
WAV, MP3 or WMA shall be supported and selectable for assigning to individual
alarm/event or groups of alarms/events during system configuration.
The SACMS GUI shall provide and display once the alarm message is being
acknowledged, an action plan, that is, instructions to operator and a miscellaneous
document.
The alarm/event action plan and miscellaneous document shall support the integration and
display of bitmap picture/s, live video/s from relative camera/s, form elements (example
checkboxes and tables) as used in Microsoft Office to create specific forms, customizable
control buttons to control system components directly, and/or any combination of these
items.
The alarm/event document‘s format shall utilize open standards, which would allow the
user to create and configure using standard editors.
The alarm/event action plan and miscellaneous document shall be assignable to specific
alarm/location to display information when an alarm or event is generated from that pre-
defined location.
In order to minimize the use of too many different alarm action plans and documents, and
for easy system management, the SACMS AS shall support macros which can be
dynamically substituted by the real alarm or event data when displayed. However, this
shall not become the limitation on the number of alarm/event action plans and
miscellaneous documents that can be created.
The SACMS shall provide the operator a simple and efficient way to handle any incoming
alarms.
Only authorized operator with the valid login username and password shall be able to
access and operate the system. Once successfully login, the operator shall only see all the
alarm and event messages destined to him for monitoring and processing based on his user
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 37 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
The operator shall be able to silence the audible alarm sound or buzzer for the pre-defined
time by clicking on an icon provided, while he is busy processing earlier alarms. The
sound/buzzer shall re-activate to re-alert him once the pre-defined time expires.
After the operator acknowledged the alarm/event, the relative alarm/event predefined
action plan or to-do-list shall display at the SACMS workstation depending on the
alarm/event type. This action plan provided is to guide or give the operator instructions
and/or options what to do with the specific alarm / event activation.
Besides the action plan provided, the operator shall also see a miscellaneous document
displayed with the action plan at the same time. This document shall contain additional
information, remarks/notes related to the specific alarm that is informative to the operator.
This information for example, shall contain access card holder‘s details, picture/s or
trouble-shooting procedures for malfunction alarm. It shall also show live video images
from the CCTV camera installed at the alarm location such that, the operator can have first
time view of the site situation if required.
The predefined alarm/event action plan and miscellaneous document shall be displayed
following operator acknowledgement of the alarm/event message. They shall provide, at
least the following information:
When the alarm/event message is acknowledged and accepted by the operator, the SACMS
shall log into database the operator‘s name, date and time of the acknowledgement for the
specific message, for purpose of accountability.
The operator shall be allowed to revert or toggle between all alarms or events messages
he had already acknowledged. The relative graphical alarm location map, action plan and
miscellaneous document attached to the selected message shall follow and toggle
automatically.
If in the event that an alarm or event message is left unaccepted by the destined operator
after a pre-defined, it shall be automatically by configuration, be forwarded to the next
authorized operator or groups of operators.
There shall not be a limitation to the number of levels that the unaccepted message can
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 38 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
The ACS management software shall be capable to support, but not limited to the
following. The limits stated below shall be extended should they be found insufficient.
Number of active cardholders – 5, 000
Number of readers – 100
Number of access groups – 255
Number of time schedules – 255
The SACMS shall allow to link directly to connected access control hardware or an
emergency door management system to open all doors along a dedicated escape route
automatically.
The SACMS shall provide a direct interaction with the access control management module,
allowing the operator to display dedicated camera images when there is an access control
alarm, such as;
Duress alarm
Door held open time exceeded
Card/cardholder not authorized
Card unknown
Tamper alarms
Together with the alarm/event document feature inside the SACMS central alarm
monitoring, the video management module shall provide a higher security level together
with the video verification mode of the access control management.
The Access Control System (ACS) shall be integrated and form part of the entire Integrated
Security System (ISMS).
The ACS shall be provided as a function within the Security Access Control Management
System (SACMS) to assist in the control and monitoring of all designated access to the
selected doors, areas or buildings.
The proposed ACS shall fulfill the functions and specifications described in this document.
In particular, the proposed access controller shall be equipped with all common interfaces
such as, Ethernet for connection to the SACMS server running the management software.
The ACS shall support up to four(4) different Wiegand card formats simultaneously. The
number of each format supported shall be unlimited.
In the event of emergency, card holders‘ access muster report shall be generated, to
provide an overview of the location where each card holder is in. This allows the security
manager to track the exact and count the number of people within the disaster area/s so to
assist in the evacuation.
The ACS shall also control the automatic locking and unlocking of nominated doors, roller
shutters and gates as indicated on the drawings.
The tenderer shall supply, install and configure the ACS management software that
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 39 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
The ACS shall provide configurable time schedules to have the flexibility for programming
automatic locking and unlocking of any access controlled doors, as well as activating and
de-activating of card holder settings for restricting any access groups from entering certain
areas with the pre-programmed time model.
The time schedule shall include holiday facilities to allow user programming for public
holidays and user definable special holidays. All schedules shall be definable by day, hours
and seconds.
The ACS shall be designed such that any point of failure within the system shall not affect
the normal operation of the other sub-systems. It shall continue to operate even if the
connection with the management software is not present.
The ACS management software provided shall allow card personalization. That is, it shall
include a tool for designing badges that supports the importing of bitmaps, text and
database fields, such as name or badge number for creating of corporate badge desi gns
printable on a standard card printer that come with a Windows compliant printer driver.
Operator Rights
The ACS management software shall provide different access rights to individual or groups
of system administrators for each configurable field within the software.
The software shall also allow the programming of individual operator‘s permissions on
certain selectable fields for edition. Permission shall be configurable to the following:
read only
read and write
read, write, change
read, write, change and delete
Cardholder Enrolment - The ACS management software shall provide an easy way of
entering cardholders into the database. In addition to basic data, such as first name, last
name, badge number and access authorizations, the following information shall be possible,
but not limited to
PIN code
Validity period
Status fields, such as employee, visitor, guard
Address fields
Personal data
Individual fields editable by administrator
The ACS management software shall provide an import and export interface to
import existing cardholder master records from a separate database or a Time
&Attendance system, or to export the master records for further use by another
application.
The interface shall support at least commonly used comma-separated and fixed-
field-length file formats for easy adaptation by applications when import or export.
The interface shall support the definition of import and export rules, such as split an
incoming name into first name and last name fields.
Access Authorizations - Grouping of entrances that consist of one or more readers shall be
possible, where one entrance can exist in several groups. A cardholder shall be assignable
directly to any of the Access Authorization groups.
Access Profiles:
The ACS management software shall support the grouping of access authorizations
or access-time authorizations, providing an easy way of assigning frequently used
access profiles to card users and visitors.
It shall be possible to allow a cardholder to carry only one card, where that card
can function as a normal access card, or as an arm/disarm card, or as a time
attendance card, or a combination of any of these functions. All cards shall be
generic in nature and the controller shall be able to reassign the function(s) of each
card depending on the door reader definition.
Defining the Area of Control - The ACS management software shall provide the ability for
defining of logical areas, which could be single room, groups of rooms, entire floors (or
parking lots) where access control points/entrances could be assigned to. Limitation on the
maximum number of people (or cars) in the defined logical area shall be possible with
programming.
Access Sequence Check - The ACS shall provide an access sequence check , allowing an
authorized cardholder to enter a door or group of doors belonging to a pre-defined area
only when he has already passed another dedicated door.
Dual or Multiple Authorized Access - The ACS management software shall provide the
possibility to configure and allow access to an access controlled door only when at least
two authorized cardholders present their badges at the card reader. The number of
cardholders for that kind of access check in front of an entrance should not be limited by
the system.
The ACS management software provided shall allow the definition of routes. These
are special access authorizations that force a cardholder to follow through a defined
path in a fixed sequence of access doors when entering to a site or building, in order
to reached the desired destination.
Route checking shall start automatically when the first reader is passed, and ends
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 41 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
after passing through the last reader in the sequence. Any violation by the
cardholder shall trigger an alarm at the SACMS workstation.
Pin Code - The ACS management software shall support the input of a PIN code for each
cardholder. The length of the PIN code is defined once in the system. The input of a
validity period has to be supported.
Duress Code Alarm - A duress code alarm message shall be generated at the SACMS
and display on the monitoring workstation when cardholders keyed in their PIN codes in
another defined way.
Blocking Cardholders and Blacklist - The ACS management software shall allow the
blocking of cardholders, for example by validity period. An operator must also be able to
add badges to a black list, for example when stolen or lost. If a black-listed card is used at a
reader, an alarm has to be triggered to the SACMS, displaying on the monitoring
workstation all defined and corresponding alarm documents.
Mantrap - Mantrap function shall be provided to allow management of two or more
interlocking doors controlled by two pairs or more of readers (in/out), or entrance readers
and request to exit buttons. Only one door can open at a time. As long as one door is
opened, the rest shall be blocked for access
Guard Tour - The ACS management software shall provide the possibility to use existing
access reader hardware to perform guard tours on future. The system must allow the
grouping of readers to a guard tour sequence. The delay time a guard needs between two
readers (checkpoints) shall be definable. All violations, such as wrong sequence or timeout,
shall trigger an alarm and logged in database at the SACMS.
Elevator Control - The ACS management software provided shall have possibility to allow
the definition of floor access authorizations at designated lift, and assign them to card
holders in future. If a cardholder presents his card at the elevator reader, the system shall
activate the elevator floor buttons the cardholder has authorized access.
Parking Lot Management - The administration and control of parking lots shall be made
possible for future. This includes the administration of the access authorization and the
control of barriers and traffic lights. The system shall provide the possibility to limit the
number of vehicles inside a parking lot so that a balancing is possible, and the traffic lights
are controlled accordingly.
Random Screening - The ACS management software shall be able to perform in future an
additional security check by the officer on duty at the site/building exits. The readers at
such exits are easily set to that mode by checking a checkbox and setting the frequency.
At Random, the selected door should not opened, but an event shall be triggered at the
SACMS monitoring workstation with all the corresponding location maps and alarm
documents. Upon receiving the message, shall remind the operator/guard to check the
cardholder and his pockets/bags. After which, he can open the door manually by clicking
on the door icon inside the location map.
Time and Attendance Data – The ACMS ACS provided shall support access control readers
as time and attendance readers. The booking events are stored in the central event log.
The event log supports the filtering for such events and the export into standard CSV
format text files for use in other applications.
Hardware Requirements.
The connection from the AC to the ACS server running the management software shall
preferably by Ethernet 100BaseT.
The AC shall have a 16-characters liquid crystal display (LCD), and a button provided for
selecting the display to show all its network parameters and actual status like:
IP address of the controller
MAC address of the controller
DHCP on/off
Status of all the inputs connected to it
Status of all the outputs connected to it
Online and Offline status of the controller
Firmware version
Date and Time – A real time clock (RTC) that will adjust itself to leap year
computations automatically.
The AC shall support and include a standard 2GB Compact flash (CF) memory card for
storing cardholder data and access events.
The AC memory shall under no circumstance loose a single, not even the last transaction
when power fails.
The AC and all devices connected to it shall continue to operate and control access in off-
line mode, even if the computer network fails.
The AC memory shall store database that has a capacity with a minimum of 1,000
cardholders (upgradeable to 10,000), each having a programmable 4 – 6 digits (Personal
Identification Number) PIN codes
The AC provided shall support the connectivity of up to 4 standard Wiegand interface
readers
The AC provided shall support multiple, but not limited to the following card formats:
Wiegand 26 Bit
Wiegand 35 Bit (HID Corporate 1000)
Wiegand 37 Bit (HID iClass)
Mifare 32 Bit CSN
1. Multiclass Reader
1.1 The readers shall support HID Prox®, Indala® Prox, Dorado® Prox, and EM Prox
legacy contactless credentials of 125kHz technology and iCLASS Seos® , iCLASS
SE, iCLASS®, MIFARE® Classic, and MIFARE DESFire®EV1 of 13.56MHz
technology
1.2 Shall support Open Supervised Device Protocol (OSDP) mode for secure,
bidirectional communication, Wiegand or Clock & Data modes
1.3 Additionally, multiCLASS readers shall support mobile devices utilizing Seos,
enabling a new class of portable identity credentials that can be securely
provisioned and safely embedded into both fixed and mobile devices
1.5 Shall be suitable for mounting on concrete, metal or wooden surface (If required
back box with matching aesthetics shall be considered)
2.1 Shall supports Prox, iCLASS® and advanced credential technology powered by Seos
2.2 In addition to supporting physical access, this single card solution powered by Seos
shall also support secure, private network access via one-time password (OTP)
2.5 Thickness of card shall be <=0.8mm making it suitable for customised design
printing using FARGO / HDP
Buzzer
The buzzer shall be red in color
The audible ability at 1 meter shall be 80dB + or – 3dB
The rating shall be continuous
Electro Magnetic Lock
The EML shall have 1200 lbs. holding force Access Controller / Reader Controller for
metallic doors and 600 lbs holding force Access Controller / Reader Controller for glass
doors.
The locks shall be designed for ease of installation with adjustable mounting, field
selectable voltage, and convenient wiring compartments.
The integrated door and lock status sensors shall allow remote monitoring without the need
to install separate ―door contacts‖.
The coil and housing assembly shall mount rigidly to the door frame while the armature
mounts to the door in a manner that allows it to pivot slightly to compensate for door
irregularities.
When the door is closed and the lock is energized the armature shall be magnetically
bonded to the lock face, thus securing the door without utilizing any moving parts.
The lock shall consume less power in order to conserve energy, there by reduces operation
cost, and extending battery backup time.
The lock shall be protected against corrosion.
There shall be no residual magnetism - the door shall releases without delay when lock is
de- energized.
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 44 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
Multiple sensor and monitor options shall be considered to increases flexibility, security and
compatibility with system equipment.
The lock shall have built-in spike suppression, which shall protect other solid state
components within the system from damage when the lock is de-energized.
This specification lays down the general, functional and technical specifications of Automatic Boom
Barriers
.
FUNCTION
The barriers are used at entrances / exits to control and review traffic in and out of the
premises.
The operation of Boom Barriers can also be linked to access control systems with safety
systems.
SYSTEM CONFIGURATION
The system shall consist of a fixed housing and a movable arm. The housing shall contain
the motor, spring and control unit.
GENERAL FEATURES
Power Cable
Size / No. of cores: 3 x 1.0 sq. mm / 3 x 4 sq. mm
Conductor: Copper
Core Insulation: PVC Insulation (as per IS 1554/Part-1/1988)
Standard of Construction: ISI Standards
If the system manufacturer recommendation for cable is different than the above specification,
then cable specification shall be considered as per system manufacturer recommendation.
GENERAL:
Transparent and elegant design
Streamlined forms and glass obstacles
Minimal footprint for maximum throughput
Top quality assembly and finish
Aesthetic and functional pictograms
Safety
Security
Robust design
Long life cycle, low maintenance costs
Fourth generation of security entrance lanes
The doors close immediately once the person has passed through, preventing unauthorised
passage. Depending on the way the door leaves open,
Design:
The housing and the base columns shall be made of AISI 304 stainless steel with semi-
gloss finish.
Two door leaves shall be made of transparent polycarbonate door leaves, thickness 10 mm,
upper edge 900 mm with opening/ closing time of 0.3 seconds minimum, which can be
adjusted as per client requirement.
An array of sensor system shall be located in the upper part of the stainless steel housing;
the electrical and mechanical components shall be integrated into the lower part. The drives
shall be installed in the swing tube. Base columns shall be empty which can be used to
integrate customer components.
In case of multiple installations, the housing unit shall act as a guiding element – additional
guiding bars are not required. The passage width can be widened to 900 mm when
necessary for passage or for passage of people with reduced mobility.
To improve personal safety, standards and guidelines relating to points where body parts
could get pinched or squashed shall be taken into account in the placement of the sensor
barrier (Machinery Directive).
Standard measurements:
Total width: 1,050 mm
Passage width: 650 /
900 Interlock height: 1,020 mm
Interlock length: 1,470 mm
Finish:
Stainless steel semi-gloss smooth finish.
Function:
The sensor barrier shall be equipped with two servo positioning drives (low energy drives
with energy content <1.6 joules) along with Tooth holding brake technology and shall be
electrically controlled in both directions thus guaranteeing a particularly high level of
personal safety.
The passage area shall be monitored by a basic sensor system with appropriate design.
Monitoring the individual passages in both directions should be possible
Sensor system shall monitor the swinging area and the blocking elements and shall act as a
protection device.
In the event of a power failure, both directions may be freely accessed.
Automatic reset upon resumption of power supply – the unit shall reset to its regular
function without manual intervention.
The access area shall be secured immediately upon resumption of power supply.
The unit can be locked in any position (Tooth Holding Brake Technology) and open under
load (personal safety in case of panic).
In basic position, the unit shall be unlocked to minimise power consumption.
Parameters can be set for unit behaviour (e.g. starting behaviour and passage speed).
Operating modes:
Open basic mode:
The door leaves shall close automatically if someone passes through who is not authorised. If
an authorised individual passes through, the door leaves stay open.
Electrical system:
Control unit and power supply unit shall be integrated into the unit. Power supply 230V AC
50/60 Hz.
Installation:
The sensor barrier shall be dowelled at finished floor level FFL for interior installation only.
BAGGAGE SCANNER
GENERAL:
X-ray baggage scanner, with the X-ray‘s penetration, can check and detect baggage in a
quick and precise way. It supports providing security checks for variety of baggage, like
briefcases, parcels, express mail, hand luggage, and so on.
Scanner shall be High performance with HD image, strong penetration, precise recognition
Adopts embedded windows operating system with multi-core ARM
Energy saving and environment protection with low power consumption
Supports real-time monitoring
Supports multiple image processing mode
Supports POST (power on self-test)
64X zoom in
One-touch power off
Energy-saving working mode for conveyor
Shock-proof design
METAL DETECTOR
DFMD Shall adopt advanced electromagnetic compatibility, with high detection sensitivity and strong anti-
interference ability. It should be suitable for safety inspection of dangerous goods and shall be widely
used for public occasions and important places, etc.
Handheld metal detector is used for security check in security areas such as examination room, airport, station,
customs, wharf, stadium, convention center, frontier guard, etc. It is also used in metal industry for preventing
pilferage of precious metal such as gold and silver jawelry, rare metals, electronic components, etc
NETWORK ENCLOSURE
1.0 WALL MOUNT NETWORK RACK 9/18/24/42U
1.1 19‖ Mounting profile, Depth:600mm x Width:800mm x Height: 18U
1.2 Basic Structure: Frame Of sturdy frame section construction, consisting of 9 x folded rolled
Steel hollow frame section punched. The corners are stiffened with welded MS die-cast,
copper coated, corner connectors, Load carrying capacity: 600 kg.
1.3 Front Glass (toughened) Door: Sheet steel with 4 mm thick toughened safety glass
with three point locking mechanism for the front door.
1.4 Surface Finish: Nano Coated, electro-dcoat primed to 20 microns and powder coated
with textured polyester RAL 7035 to 80 to 120 microns.
1.5 Front Glass with PU Gasket
1.6 Side Louvered panel, 1.5 mm with PU Gasket
1.7 Full Height 19‖ angle,
1.8 Top and bottom cover, with cable entry provision at bottom cover.
1.9 Three units of Power Distribution Panel (PDP) with 15A / 5A three pin socket 5 Nos. in each
PDP along with three meters of cable with Plug.
1.10 Two nos. of blowers mounting below the top cover of the rack with finger guards. For air
circulation.
1.11 Plinth frame of height 150 mm. with cable entry hole and mounting provision to be
assembled below the rack instead of caster wheels.
1.12 Earthing str (Cu) with Earthing kit,
1.13 Hardware pack of 20 (5pack. / Rack)
1.14 Cable tray at both sides of the rack rear side for routing of the cable.
1.15 All Products should be certified according to ISO 9001, 14001, 18001 and UL, VDE Listed
2.11 Two nos. of blowers mounting below the top cover of the rack with finger guards. For
air circulation.
2.12 Plinth frame of height 150 mm. with cable entry hole and mounting provision to be
assembled below the rack instead of caster wheels.
2.13 Earthing str (Cu) with Earthing kit,
2.14 Hardware pack of 20 (5pack. / Rack)
2.15 Cable tray at both sides of the rack rear side for routing of the cable.
2.16 All Products should be certified according to ISO 9001, 14001, 18001 and UL, VDE Listed
3.0 50/125μm OM3 TYPE MULTI MODE INDOOR / OUTDOOR OPTICAL FIBER CABLE
3.1 The Cable shall be for indoor and Outdoor use which shall be with heavy screen
/ double shielded , Outdoor Cable shall be with Armored cable as per
standards
3.2 The cable consists of a number of 900μm tight buffered optical fibres reinforced with
aramid yarns and sheathed in a flame retardant Low Smoke Zero Halogen
compound.
3.3 Graded Index 50/125μm fiber tested and certified to satisfy Gigabit Ethernet
applications. Should support link lengths greater than 1000 metres at both 850nm and
1300nm in local area network applications (LAN) and transmission rates of up to
10Gbit/s over a distance of 300 metres at 850nm.
3.4 The cable should be designed for internal use primarily in structured wiring systems in
backbones. Should consist of a ―dry‖ water blocking system to prevent the flow of
water along the cable in the event of sheath breech.
3.5 OPTICAL PERFORMANCE
3.5.1 Max. Attenuation: At 850 nm: 2.5 dB/km and at 1300 nm: 0.7 dB/km
3.5.2 Min. Bandwidth : At 850 nm: 2000 MHz/km and at 1300 nm: 500 MHz/km
3.6 CONSTRUCTION
3.6.1 Fiber Identification: Colour Coded
3.6.2 Fiber Insulation: Coloured Nylon
3.6.3 Reinforcing: Aramid Yarns
3.6.4 Sheath: LSZH Black
3.7 DIMENSION & MASS
3.7.1 Diameter (Nominal): 6 Core : 5.6mm
3.7.2 Mass (Nominal) : 6 Core 38 kg/km
3.8 PHYSICAL & ENVIRONMENTAL SPECIFICATIONS
5.9 Cable entrance port on the top, bottom, and sides to allow cable entry to the box from
any direction
5.10 onstructed of 18 gauge steel, powder-coated black
5.11 Must be independently tested and verified by ETL and UL.
12.0 CAT 6 RJ45 JACKS (INFORMATION OUTLET) FOR UTP AND STP
12.1
12.2 110 TYPE IDC Connector
12.3 Plastic Housing: Polycarbonate, UL94V-0 rated or Equivalent
12.4 Operating Life: Minimum 750 insertion cycles
12.5 Contact Material: Copper Alloy
12.6 Contact Plating: 50μ‖ Gold/100μ‖ Nickel
12.7 Contact Force: 100g minimum
12.8 Plug Retention Force: 15 lb.
12.9 Plastic Housing: Polycarbonate, UL94V-0 rated or Equivalent
12.10 Operating Life: Minimum 200 re-terminations
12.11 Contact Material: Copper Alloy
12.12 IDC Contact Plating: Tin/Lead Plate
12.13 Contact Force: 100g minimum
12.14 Wire Accommodation: 22-24 AWG solid
12.15 Interface Resistance: 20 milliohms
12.16 Initial Contact Resistance: 2.5 milliohms
12.17 Insulation Resistance: >100 Mega ohms
12.18 Dimensions (mm): 23.5(H) x 17.9(W) x 30.53(D)
12.19 110 Type IDC termination
12.20 Dual color-coding for 568 A/B wiring configuration
12.21 Dual layer wiring label must be used to simplify punch down and reduces re-work.
12.22 Should be terminated using industry standard punch down tools
12.23 Should be RJ-11 & RJ-12 compatible
12.24 Gas tight connection at the IDC to prevent corrosion.
12.25 Must have retention force technology (RFT) to protect tines from damage
12.26 Commercial Standards:
12.27 TIA/EIA-568-B.2-1 Component Compliant,
12.28 FCC Subpart F 68.5 Compliant,
12.29 IEC-603-7 Compliant
12.30 ISO 11801 Class E Compliant
12.31 ETL Verified for Category 6 Component Compliance
12.32 Must be independently tested and verified by ETL and UL.
13.0 FACEPLATE
13.1
13.2 Unloaded face plates should be designed to accept the RJ45 Cat5E & Cat 6 Connector.
0
13.3 Should have 45 Degree angled towards user end interface.
13.4 The unloaded face plates should be available in 1, 2 and 4 port variants, in five colors,
to co-ordinate with any decor and any installation size.
Last Modified: 27.04.2021 DesignTree Service Consultants Pvt. Ltd.
Rev: 0 57 Technical Specifications
GODREJ COMMERCIAL HUB, HEBBAL @ BANGALORE. CCTV & ACS SYSTEM
13.5 The face plate kit should contain screws and screw-hole covers that provide individual
installation labeling, as well as snap-in icon
13.6 Labels, that are color co-ordinate with the face plate.
13.7 Plastic: The Jacks should be UL listed and come complete with Integral shutter for
protection against dust ingress.
13.8 Should be designed with Protected labeling facility Icon Port Identification labeling
13.9 Screws provided with 1, 2 & 4 Port versions
13.10 Must be independently tested and verified by ETL and UL.
18.0 MAIN DISTRIBUTION FRAME (MDF) / MULTI PAIR VOICE PATCH PANEL
18.1 The Make shall be as per the spec or EQUIVALENT DoT APPROVED MAKE
MEDIA CONVETER
1. 12 Port : Should have min 10 Port 10/100/1000BaseT/TX + 4 Port Combo 1000BaseSX (SFP)
port loaded
2. 24 Port: Should have min 20 Port 10/100/1000BaseT/TX + 4 Port Combo 1000BaseSX (SFP)
port loaded
3. 48 Port: Should have min 20 Port 10/100/1000BaseT/TX + 4 Port Combo 1000BaseSX (SFP)
port loaded
4. PERFORMANCE:
5. 12 Port :Switching capacity 32Gbps ; Throughput 23.8Mpps 24 Port: Switching capacity
48Gbps ; Throughput 35.7Mpps 48 Port: Switching capacity 96Gbps ; Throughput 39.3Mpps
14,880pps for 10Mbps Ethernet
6. 148,800pps for 100Mbps Ethernet 1,488,000pps for 1000Mbps Ethernet
7. MAC addresses 8K
8. VLAN ID‘s available 4K
9. Max VLANs 200 tagged + 56 port-based
10. Multicast Up to 32 static multicast groups
11. Packet buffer 2MB ,DRAM 16MB,Flash 4MB,Switch memory 2MB embedded
12. Interface Connections: 10/100/1000T RJ-45 & SFP 100TX, 100FX, 1000T,1000SX or 1000LX
13. Standards and Compliance IEEE 802.3 CSMA/CD
IEEE 802.3i 10T
IEEE 802.3u
100TX
IEEE 802.3z 1000SX/LX
IEEE 802.3z/ab 1000T
IEEE 802.3x Flow control
IEEE 802.1p Prioritization (four queues)
5. Should supports VLAN double tagging & Private VLANs, providing security and port isolation
of multle customers using the same VLAN
1. Should support ASIC based appliance where firewall & VPN and AV scanning are accelerated
by ASIC.
2. Should not be a hard disk based solution & even if hard disk fails the security functionalities
should not stop functioning
3. The firewall should provide minimum of 2 Gbps Firewall throughput, VPN throughput of
more than 1 Gbs with minimum 30 SSL VPN users
4. The Firewall Should support at least 2,00,000 concurrent sessions and at least 5,000
new sessions per second.
5. Firewall should have features to block applications by name
6. Should provide full UTM functionalities like Gateway AV, S, Web category filtering, Antispam
& Application control
7. Should provide minimum of 4 10/100/1000 interfaces or more.
8. The firewall should be able to support high availability and dynamic load balancing for data
going through the firewall (active-active)
9. The Firewall should support Rv1,Rv2, OSPF .
10. Should provide RPS for the Appliance
11. The Firewall should support automatic ISP failover as well as ISP load sharing and
load balancing for outbound traffic. Should have separate interfaces for terminating
dual ISP Ethernet connectivity.
SECTION - V
A CCTV SYSTEM
1 Camera / mounting accessories / joystick Hik Vision, Winston Samsung, Sony, Interlogix, Avetron, Ayzo
1 Copper Conductor Control Cable / Wires Apar Cables, Varsha, Ravicab, Polycab, Deepanjan
2 Communication Wires Apar Cables, Varsha, Ravicab, Polycab, Deepanjan
3 CAT 6 Cables Polycab, Apar Cables, D-link
4 MS Conduits Bharath, GB, Mangocab, VIP, Avon Plast, Atul