Embed Size (px)
Citation preview
1
Request for Proposal- Volume 2
Designing, Development, Implementation, Testing , Training,
Commissioning and Operation & Maintenance of Intelligent Traffic
Management and Monitoring Systems (ITMS) with Advertisement
Panels under Smart City Mission (SCM) in Jammu – Volume -2
2
Table of Contents
1 PROJECT CONCEPT ................................................................................................................................................. 12
1.1 CHALLENGES AND OBJECTIVES ...................................................................................................................................... 12
1.2 TMMC CONCEPT ...................................................................................................................................................... 14
1.3 PROJECT OUTCOMES & BENEFITS .................................................................................................................................. 15
2 DETAILED SCOPE OF WORK FOR SYSTEM INTEGRATOR FOR TMMC ....................................................................... 17
2.1. Detailed Project Plan and System Design Document ........................................................................................ 21
2.2. Site Clearance obligations & other general provisions ..................................................................................... 22 2.2.1. Survey and Commencement of Works ........................................................................................................................... 22 2.2.2. Existing Traffic Signal system .......................................................................................................................................... 22 2.2.3. Road signs ....................................................................................................................................................................... 22 2.2.4. Electrical works and power supply ................................................................................................................................. 23 2.2.5. Earthing System .............................................................................................................................................................. 23 2.2.6. Junction Box, Gantries and Cantilever ............................................................................................................................ 23 2.2.7. Cabling Infrastructure ..................................................................................................................................................... 23 2.2.8. Road Marking (Zebra / Stop line) ................................................................................................................................... 23 2.2.9. RoW (Right of Way) ........................................................................................................................................................ 24
2.3. Design, Supply, Installation, Testing & Operation of Field Equipment.............................................................. 24 2.3.1. Traffic Junction Surveillance System .............................................................................................................................. 24 2.3.2. Public Address (PA) System ............................................................................................................................................ 24 2.3.3. Red Light Violation Detection (RLVD) System ................................................................................................................ 25 2.3.4. Automatic Number Plate Recognition (ANPR) System ................................................................................................... 25 2.3.5. E-Challan System ............................................................................................................................................................ 26 2.3.6. Variable Message Sign (VaMS) System/Advertisement Panels ...................................................................................... 26 2.3.7. Network Connectivity between Field Locations to TMMC ............................................................................................. 26
2.4. Traffic Control Center and Data Center ............................................................................................................ 27 2.4.1. Traffic Control Centre (ITMS)/Traffic Management and Monitoring Centre (TMMC) .................................................... 28 2.4.2. Data Centre (DC)............................................................................................................................................................. 28
2.5. Smart DR Solution – Hosted on GCC/MEITY certified Cloud ............................................................................. 34
2.6. Lying & Commissioning of Backbone Fiber Network ........................................................................................ 35
2.7. Implementation of the Information security policy .......................................................................................... 40
2.8. Capacity Building and Training ......................................................................................................................... 40
2.9. Integration with ICCC and other external systems ............................................................................................ 40
2.10. Acceptance Testing ........................................................................................................................................... 40
2.11. Final Acceptance Testing .................................................................................................................................. 41
2.12. System Documents and User Manuals ............................................................................................................. 42
2.13. Operations and Maintenance during Contract Period ...................................................................................... 42 2.13.1. Project Management Team ....................................................................................................................................... 43 2.13.2. Provision of the Operational Manpower to support Operations at Traffic Control Center ....................................... 45 2.13.3. Physical Infrastructure Management and Maintenance Services ............................................................................. 45 2.13.4. Project Handover ....................................................................................................................................................... 46 2.13.5. Other ......................................................................................................................................................................... 46
3 SYSTEM ARCHITECTURE ......................................................................................................................................... 48
3.1 GUIDING PRINCIPLE .................................................................................................................................................... 48
3.2 DESIGN CONSIDERATIONS ............................................................................................................................................ 56
3.2.1 Identification of all stakeholders....................................................................................................................... 56
3.2.2 Jammu Municipal Corporation (JMC) and departments: .................................................................................. 57
3.2.3 Smart City SPV .................................................................................................................................................. 57
3
3.2.4 Implementation Partner ................................................................................................................................... 58
3.3 CHARACTERISTICS OF DESIGN ........................................................................................................................................ 58
3.4 DESIGN PARAMETERS ................................................................................................................................................. 58
3.5 NETWORK BACKBONE ................................................................................................................................................. 59
4 TRAFFIC MANAGEMENT AND MONITORING CENTRE ............................................................................................. 61
4.1 TMMC COMPONENTS................................................................................................................................................ 61
4.2 FUNCTIONAL ARCHITECTURE ........................................................................................................................................ 63
4.2.1 Architecture Flow .............................................................................................................................................. 63
4.3 TMMC APPLICATIONS ................................................................................................................................................ 65
4.3.1 Traffic Management ......................................................................................................................................... 65 4.3.1.1 Red Light Violation Detection System ....................................................................................................................... 65 4.3.1.2 Entry Restriction Violation using Video Analytics and ANPR ..................................................................................... 65 4.3.1.3 Handheld Device application ..................................................................................................................................... 66 4.3.1.4 Operational and Data Integration with Existing Adaptive Traffic Control System (ATCS) ......................................... 66
4.3.2 Traffic Monitoring ............................................................................................................................................. 66 4.3.2.1 CCTV Surveillance of Traffic Junctions ....................................................................................................................... 66 4.3.2.2 Video Analytics .......................................................................................................................................................... 67 4.3.2.3 Integration with Bus and Intermediate Public Transport Operations (In Future) ...................................................... 68
4.3.3 Incident Management ...................................................................................................................................... 68
4.3.4 Information Dissemination ............................................................................................................................... 70
5 MINIMUM TECHNICAL SPECIFICATIONS ................................................................................................................. 71
5.1 DC SCOPE OF WORK .................................................................................................................................................. 74
5.2 DC COMPONENTS ...................................................................................................................................................... 80
5.2.1 Unified Command & Control Center for TMMC ................................................................................................ 80
5.2.2 Firewall with Anti-APT solution. ........................................................................................................................ 83 5.2.2.1 Next Generation Firewall: .......................................................................................................................................... 83 5.2.2.2 Anti-APT ..................................................................................................................................................................... 85
5.2.3 Core and Internet Router .................................................................................................................................. 85
5.2.4 Core Switch ....................................................................................................................................................... 86
5.2.5 TOR Distribution Switch .................................................................................................................................... 89
5.2.6 Access Switch 48 Port POE ................................................................................................................................ 91
5.2.7 Access Switch 24 Port Non-POE ........................................................................................................................ 93
5.2.8 Server Load Balancer ........................................................................................................................................ 94
5.2.9 EMS (Enterprise Management System ............................................................................................................. 95
5.2.10 End Point Security .......................................................................................................................................101
5.2.11 Servers ........................................................................................................................................................110 5.2.11.1 Rack GPU Server ................................................................................................................................................. 110 5.2.11.2 Rack Servers ........................................................................................................................................................ 112
5.2.12 Storage and Backup ....................................................................................................................................114
5.2.13 Backup Software .........................................................................................................................................117
5.2.14 Unified Management .................................................................................................................................119
5.2.15 Server Virtualization ...................................................................................................................................122
5.2.16 Video Wall, Video wall Management software and Controller ..................................................................125 5.2.16.1 Video Display Wall .............................................................................................................................................. 125 5.2.16.2 Push / Pull Type Video Wall Mounting Kit .......................................................................................................... 126 5.2.16.3 High-performance Video wall controller ............................................................................................................ 126
5.2.17 Video Management System and Video Analytics .......................................................................................127
5.3 INTEGRATED DATA CENTRE INFRASTRUCTURE ................................................................................................................132
4
5.3.1 Uninterrupted Power Supply (UPS) System .....................................................................................................133
5.3.2 Rack & Accessories ..........................................................................................................................................135
5.3.3 Biometric Access Control and Fire alarm system ............................................................................................136
5.3.4 DC CCTV Surveillance with Camera, storage and Switch ................................................................................137
5.3.5 DC wireless access point with controller .........................................................................................................140
5.3.6 Ruggedized Hand held devices ........................................................................................................................143
6 NON-IT REQUIREMENTS, SPECIFICATIONS & OFFICE INTERIOR ............................................................................ 145
6.1 GENERAL STANDARDS: ..............................................................................................................................................145
6.2 CIVIL AND ARCHITECTURAL WORK ...............................................................................................................................145
6.2.1 False Ceiling ....................................................................................................................................................145
6.2.2 Furniture and Fixture ......................................................................................................................................146
6.2.3 Partitions (wherever required as per approved drawing) ...............................................................................146
6.2.4 Flooring (wherever required as per approved drawing) .................................................................................147
6.2.5 Air Conditioning and Natural Convection for Data Centre ..............................................................................147
6.2.6 Painting ...........................................................................................................................................................148
6.2.7 PVC conduit .....................................................................................................................................................148
6.2.8 Wiring .............................................................................................................................................................148
6.2.9 Cable Work......................................................................................................................................................149
6.2.10 Fire Detection and Control Mechanism ......................................................................................................150
6.2.11 Rodent Repellent System ............................................................................................................................151
6.2.12 Access Control System ................................................................................................................................151
6.2.13 Monitoring Workstations ...........................................................................................................................152
6.2.14 Desktops for Helpdesk ................................................................................................................................153
6.2.15 Multifunctional Device ...............................................................................................................................154
6.2.16 DG Set .........................................................................................................................................................154
6.2.17 Field Equipment ..........................................................................................................................................155 6.2.17.1 Specification of Field Junction Box .......................................................................................................................... 155 6.2.17.2 Camera Poles ........................................................................................................................................................... 156 6.2.17.3 Industrial Grade Outdoor PoE switches ................................................................................................................... 157 6.2.17.4 Specification of Field UPS. ....................................................................................................................................... 159 6.2.17.5 Networking Cost (Passive Components including Patch Panel, LIU, Cat6 Cable, Patch Cords) ................................ 160 6.2.17.6 Fiber Cable 12 cores Type & Construction:.............................................................................................................. 160 6.2.17.7 ANPR software with required no. of Licenses ......................................................................................................... 164 6.2.17.8 ANPR and RLVD cameras Hardware specification for covering all the arms & lanes .............................................. 171 6.2.17.9 Local Processing unit/industrial grade Server for ANPR & RLVD ............................................................................. 173
6.2.18 AD Panels ....................................................................................................................................................174 6.2.18.1 Rack Frame Power Distribution Unit ....................................................................................................................... 176 6.2.18.2 LED Processor .......................................................................................................................................................... 177 6.2.18.3 Item 4: Mechanical Structure For Mounting Of LED Walls ...................................................................................... 177 6.2.18.4 Content Management Server with Software ........................................................................................................... 178 6.2.18.5 Auto Brightness Sensor............................................................................................................................................ 178
6.2.19 IP based Public Address System – Functional .............................................................................................178 6.2.19.1 Desktop Intercom Paging Microphone with touch screen ...................................................................................... 180 6.2.19.2 Outdoor IP Based smart speakers ........................................................................................................................... 181
6.2.20 Emergency Call Box – Functional ................................................................................................................182
6.2.21 City Surveillance..........................................................................................................................................183 6.2.21.1 BOX Camera ............................................................................................................................................................. 183 6.2.21.2 Surveillance PTZ Camera ......................................................................................................................................... 185
6.2.22 Smart Sensors .............................................................................................................................................188
5
6.2.22.1 Technical Specifications – Pollution / Environmental Sensors ................................................................................ 188 6.2.22.2 Technical Specifications – Rain Gauges Sensor........................................................................................................ 189
6.3 HAND HELD BASED E-CHALLANS .................................................................................................................................189
9.3.1 Functional Requirements ................................................................................................................................189
6.4 AUTOMATIC E CHALLAN & CENTRALIZED MONITORING ...................................................................................................191
6.4.1 Security Provisions ..........................................................................................................................................192
6.5 MANPOWER ...........................................................................................................................................................193
7 PROJECT TIMELINES ............................................................................................................................................. 195
7.1 IMPLEMENTATION PLAN ............................................................................................................................................195
7.1.1 Implementation Phase ....................................................................................................................................195
7.1.2 Operation & Maintenance (O&M) Phase ........................................................................................................195
7.2 PROJECT TIMELINES ..................................................................................................................................................196
7.3 ANNEXURE 10 - PROPOSED BILL OF MATERIAL (TECHNICAL BID).......................................................................................197
8 ANNEXURE 11 – FORMATS FOR SUBMISSION OF THE COMMERCIAL BID (WILL BE GIVEN IN ONLINE PORTAL) .... 200
8.1 CAPITAL EXPENDITURE (CAPEX (A)) .............................................................................................................................201
8.2 OPERATIONAL EXPENDITURE (OPEX (B)) ......................................................................................................................204
8.3 SUB-TOTAL .............................................................................................................................................................205
9 ANNEXURES: ........................................................................................................................................................ 206
9.1 PTZ, FIXED, ANPR AND RLVD CAMERA, AD PANEL AND ENVIRONMENT SENSOR LOCATIONS: ..............................................206
9.2 CITY EXIT POINTS: ....................................................................................................................................................219
9.3 PUBLIC ADDRESS SYSTEM ..........................................................................................................................................221
6
Glossary
S. No Terms Meaning
1 ACL Access Control List
2 AAC Advanced Audio Coding
3 AES Advanced Encryption Standard
4 APT Advanced Persistent Threat
5 AVC Advanced Video Coding
6 AWFS Advanced Wide Field Sensor
7 AC Air Conditioner
8 ACR Annual Confidential Reports
9 AV Anti Virus
10 API Application Programming Interface
11 ABD Area Based Development
12 AI Artificial Intelligence
13 AMWI Audio Message-Waiting Indicator
14 AVI Audio Video Interleave
15 ACD Automatic Call Distribution
16 BIOS Basic Input Output System
17 BSNL Bharat Sanchar Nigam Limited
18 BFCP Binary Floor Control Protocol
19 BGP Border Gateway Protocol
20 BIFMA Business And Institutional Furniture Manufacturer's Association
21 BI Business Intelligence
22 BPR Business Process Reengineering
23 CO2 Carbon Dioxide
24 CO Carbon Monoxide
25 CAS Central Authentication Service
26 CPU Central Processing Unit
27 CSV Comma-Separated Values
28 COTS Commercial Off-The-Shelf
29 CEOS Committee On Earth Observing Sensors
30 CIF Common Intermediate Format
31 CAD Computer Aided Design
32 CBT Computer Based Training
33 CTI Computer-Telephony Integration
34 CFM Connectivity Fault Management
35 CMS Content Management Software
36 CRM Customer Relationship Management
37 DB Database
38 DBMS Database Management System
39 DOS Denial Of Service
7
40 DG Diesel Generator
41 DEM Digital Elevation Model
42 DTED Digital Terrain Elevation Data
43 DDoS Distributed Denial of Service.
44 DND Do Not Disturb
45 DNS Domain Name Server
46 DHCP Dynamic Host Configuration Protocol
47 ERDAS Earth Resources Data Analysis System
48 EROS Earth Resources Observation And Science
49 EMS Enterprise Management System
50 ESB Enterprise Service Bus
51 ER Entity Relationship
52 EPROM Erasable Programmable Read-Only Memory
53 EVPN Ethernet Virtual Private Network
54 XGA Extended Graphics Array
55 XML Extensible Markup Language
56 ETL Extract,Transform And Load
57 FFT Fast Fourier Transform
58 FR Fast Reroute
59 FCIP Fibre Channel Over Internet Protocol
60 FTP File Transfer Protocol
61 FIFO First In First Out
62 FSC Forest Stewardship Council
63 FIB Forwarding Information Base
64 FRS Functional Requirement Specification
65 GPRS General Packet Radio Services
66 GIS Geographic Information System
67 GEOTIFF Georeferenced Tagged Image File Format
68 GPS Global Positioning System
69 GSM Global System For Mobile Communication
70 GST Goods And Services Tax
71 GUI Graphical User Interface
72 GLSR Ground Level Storage Reservoir
73 HD High Definition
74 HLD High Level Design
75 HTTPS Hyper Text Transfer Protocol Secure
76 HTML Hypertext Markup Language
77 IDM Identity Management
78 IDP Identity Provider
79 ICT Information And Communications Technology
80 I/O Input/Output
81 IM Instant Messaging
8
82 IEEE Institute Of Electrical And Electronics Engineers
83 ITL Instructor-Led Training
84 IVR Interactive Voice Response
85 IPT Intermediate Public Transport
86 ITU International Telecommunication Union
87 IGMP Internet Group Management Protocol
88 IOT Internet Of Things
89 IP Internet Protocol
90 IPFR Internet Protocol Fast Reroute
91 IPS Internet Protocol Security
92 ISP Internet Service Provider
93 INSPIRE Interstate Network Of Science Programs Integrating Research And Education
94 IDW Inverse Distance Weighting
95 JSON Javascript Object Notation
96 JPEG Joint Photographic Experts Group
97 KPI Key Performance Indicators
98 KML Keyhole Markup Language
99 LDR Light Detection And Ranging
100 LDAP Lightweight Directory Access Protocol
101 LISSS Linear Imaging Self Scanning Sensor
102 LPU Local Proceesing Unit
103 LAN Local-Area Network
104 LC Low Complexity
105 LD Low Delay
106 LLD Low Level Design
107 MIS Management Information System
108 MITM Man-In-The-Middle
109 MAC Media Access Control
110 MDF Medium Density Fiberboard
111 MQTT Message Queuing Telemetry Transport
112 MDM Mobile Device Management
113 MLPP Multi-Level Precedence And Preemption
114 MCU Multipoint Control Unit
115 MPLS Multi-Protocol Label Switching
116 NEMA National Electrical Manufacturers Association
117 NFPA National Fire Protection Association
118 NIC National Informatics Centre
119 NIR Near-Infrared Reflectance
120 NAC Network Access Control
121 NAT Network Address Translation
122 NMS Network Management System
123 NTP Network Time Protocol
9
124 NAS Network-Attached Storage
125 NO2 Nitrogen Dioxide
126 NOC No Objection Certificate
127 NOSQL Not Only SQL
128 ORDBMS Object-Relational Database Management System
129 OHSAS Occupational Health And Safety Assessment Series
130 OSC One Stop Centre
131 Oauth Open Authorization
132 OGC Open Geospatial Consortium
133 ONVIF Open Network Video Interface Forum
134 OSPF Open Shortest Path First
135 OS Operating System
136 O&M Operations & Maintenance
137 OAM Operations Administration Maintenance
138 OCR Optical Character Recognition
139 OFC Optical Fiber Cable
140 OEM Original Equipment Manufacturer
141 O2 Oxygen
142 PCT Patent Cooperation Treaty
143 PC Personal Computer
144 PM Picometre
145 POP Point Of Presence
146 PU Polyurethane Paint
147 PVC Polyvinyl Chloride
148 PDF Portable Document Format
149 PNG Portable Network Graphics
150 PIMER Postgraduate Institute Of Medical Education And Research
151 PABE Private Automatic Branch Exchange
152 PBE Private Branch Exchange
153 PIE Private Internet Exchange
154 PLAR Private Line AutomatIC Ringdown
155 PIM-DM Protocol-Independent Multicast- Dense Mode
156 PIM-SM Protocol-Independent Multicast- Sparse Mode
157 PA Public Address
158 PBS Public Bike Sharing
159 PKI Public Key Infrastructure
160 PSTN Public Switched Telephone Network
161 PEC Punjab Engineering College
162 QSFFP Quad Small Form-Factor Pluggable
163 QA Quality Assurance
164 QC Quality Control
165 QoS Quality Of Services
10
166 QCIF Quarter Common Intermediate Format
167 QR Quick Response
168 RIS Radar Imaging Satellite
169 RTMT Real Time Monitor Tool
170 RTO Recovery Time Objective
171 RHEL Red Hat Enterprise Linux
172 RAID Redundant Array Of Independent Disks
173 RPSU Redundant Power Supply Unit
174 RTO Regional Transport Office
175 RGI Registrar General Of India
176 RC Registration Certificate
177 RDBMS Relational Database Management System
178 RADIUS Remote Authentication Dial-In User Service
179 RMON Remote Monitoring Network
180 RTU Remote Terminal Unit
181 REST Representational State Transfer
182 RRP Resource Reservation Protocol
183 RHS Restriction Of Hazardous Substances
184 SFN Sampled Flow Netflow
185 SVC Scalable Video Coding
186 SCP Secure Copy Protocol
187 SRTP Secure Real-Time Transport Protocol
188 SSH Secure Shell
189 SSL Secure Sockets Layer
190 SAML Security Assertion Markup Language
191 SDP Session Description Protocol
192 SIP Session Initiation Protocol
193 SMS Short Message Service
194 SNMP Simple Network Management Protocol
195 SNMPv3 Simple Network Management Protocol Version 3
196 SOAP Simple Object Access Protocol
197 SSO Single Sign On
198 SFFP Small Form-Factor Pluggable
199 SDK Software Development Kit
200 SDLC Software Development Life Cycle
201 SRS Software Requirements Specification
202 SFTP Ssh File Transfer Protocol
203 SD Standard Definition
204 STQC Standardisation Testing And Quality Certification
205 SAN Storage Area Network
206 SQL Structured Query Language
207 SO2 Sulfur Dioxide
11
208 SXGA Super Extended Graphics Array
209 SVGA Super Video Graphics Array
210 SCADA Supervisory Control And Data Acquisition
211 SOC System On A Chip
212 TSV Tab Separated Values
213 Tbps Terabit-Per-Second
214 TACACS Terminal Access Controller Access-Control System
215 ITMS/TMMC Traffic Command Center/Traffic Management and Monitoring Center
216 TLS Transport Layer Security
217 TFTP Trivial File Transfer Protocol
218 TAT Turn Around Time
219 UV Ultraviolet
220 UC Unified Communication
221 URL Uniform Resource Locator
222 UPS Uninterruptible Power Supply
223 USB Universal Serial Bus
224 UAT User Acceptance Testing
225 UDP User Datagram Protocol
226 UX User Experience
227 UI User Interface
228 VIP Very Important Person
229 VA Video Analytics
230 VC Video Conference
231 VESA Video Electronics Standards Association
232 VGA Video Graphics Array
233 VMS Video Management System
234 VXLAN Virtual Extensible Lan
235 VPN Virtual Private Network
236 VRF Virtual Routing Forwarding
237 VOIP Voice Over Internet Protocol
238 WMS Warehouse Management System
239 WCS Web Coverage Service
240 WFS Web Feature Service
241 WEBRTC Web Real-Time Communication
242 WAN Wide Area Network
243 WEGA Wide Extended Graphics Array
244 WORM Write Once Read Many
12
1 Project concept
1.1 Challenges and Objectives
Jammu Smart City Envisages to set up TMMC/ITMS to overcome following challenges:
• Traffic Enforcement: The city has a high number of traffic violations and/or an upward trend
towards number of traffic violations indicating issues with traffic enforcement.
• Road Network Congestion: City is experiencing congestion on its road network evidenced by
higher travel time, very low speed and growing trip rates. It is due to available transport capacities
being sub-optimally utilized and issues with traffic management approaches.
• Population Growth: The city is registering rapid growth in city population and travelling population
leading to higher number of trips being observed on its road network causing congestion.
• Growth in number of registered vehicles: The city is observing a high rate of growth in number of
vehicles registered which is deteriorating the traffic conditions on its road network.
• Traffic Accidents: The city has a high number of accidents and an upward trend towards number of
traffic accidents and related injuries.
• Pollution Level: The city has high level of vehicle related pollution in the form of suspended
particulate matter (PM2.5) and other pollutants (such as NOx, CO) as compared to the permitted
levels.
• Lack of Traffic Data: The city does not have traffic related data (historical or current) that it can use
for planning transport related interventions and share with public to enable them to plan their
trips using such information.
• Physical Constraints: The city is experiencing growth in number of transport trips but it cannot
augment transport capacity owing to physical and geographical constraints.
TMMC will be scalable to host more applications and services in future for managing city more
effectively. Later, TMCC can be extended as ICCC, which will manage utilities of the entire city,
eventually. Following are the intangibles that should be addressed by this intervention:
• Efficient traffic and Transport management
• Utility Integrations
• Disaster Management and Emergency Response System
• Enhanced safety and security
• Asset Management
• Organized workflow management
• Coordinated decision making
13
• Implementation with following services in the city (existing/Current and future planned
infrastructure with provision for future scalability)
Integrated Command and Control Centre
Data Centre and Disaster Recovery
City Safety, Security & Surveillance
Transit Management System
Intelligent Traffic Management System
Environmental Sensors
GIS asset Mapping
Public Address System
Governance and Citizen Services
The other objectives that can be achieved by proposed ICT interventions in the city are:
• Effective detection and monitoring of traffic violations thus real time traffic enforcement
(reduces offences of Red-Light violations)
• Effective surveillance helps in enforcing law and order and crime prevention (reduction in
number of criminal and unlawful activities)
• Reduces number of traffic rule violations such as illegal parking, Riding without Helmet,
Triple Riding etc. with the help of continuous surveillance
• Prompt emergency response by Police and City Administration in cases of accidents, fires,
disasters, epidemics, etc. due to availability of real time data and response mechanisms
• Delivering effective governance by aggregating various data feeds from sensors and systems
• Reduction in waiting period at intersection by optimizing traffic cycles to regulate and
maintain smooth flow of traffic to enhance the efficiency of the transport infrastructure and
reduce travel time.
• Ensuring safety and crowd surveillance. The central command and control will also ensure
efficient continued working of the field equipment
• Public Address System (voice) will enable civic bodies to respond / communicate effectively
while dealing with emergencies
• Variable messaging displays (Advertisement Panels) will be used to display the useful
information related to Traffic congestion, accidents, incidents, ongoing roadwork zones,
speed limits, key notices or messages from city administration. These Ad Panels can also
used to generate Revenue using general Advertisement.
14
1.2 TMMC Concept
High Level Architecture of TMMC
To Operate, Control, Manage and monitor the aforementioned systems a dedicated Traffic Monitoring
and Management Centre (TMMC) is envisaged. TMMC including other Information Systems Such as
Video wall, Server Farm, networking equipment with required software platform capability to
aggregate incoming data streams onto a single platform, provide detailed traffic information on a real-
time basis and assist in analysing impact of alternate traffic management strategies. It is expected that
TMMC/ITMS
Command Center
Traffic Management
RLVD+ANPR+PAS
Traffic Monitoring
Surveillance
Environment Monitoring
Sensors
Advertisement Panels
VaMSl
Existing ATCS
Integration
External Agencies
Integration
15
JSCL or JMC will provide sufficient space at Police headquarter or other building for setting up of
TMMC (around 4000 sq feet including 1000 sqft area where ATCS is implemented)
A Traffic Monitoring and Management Centre shall provide seamless integration to multi-vendor
devices and disparate systems across the enterprise platform to provide a holistic traffic view. Some of
the design consideration for the TMMC includes the following:
• The system shall be designed to provide complete situational awareness to ensure that incident
response policies are implemented without technical restrictions.
• It will address the need to rapidly change and adapt these security process and policies,
especially when managing disparate security systems, sensors and devices.
• Seamless integration to multi-vendor devices
• Single view of incidents and events (via dashboards and role-specific graphical user interfaces).
• Pre-plan process event management (via customized alarm, GUI workflow tools and response
plans).
• Analytics, Correlation and information management
Thus, the TMMC shall be able to provide complete situational awareness on ground, covering a set
percentage of the overall traffic violation, surveillance cameras, readiness status, vehicle movements,
open incidents (incidents which are still open for action) etc.
Decision Making
The system shall be designed to enable decision making, planning, allocation of resources and post
action review.
Command Control
The system shall monitor, manage and disseminate alerts (sound based, email based etc.) and
information from all of the disparate video and security systems. The operations centre shall also
conduct intelligent video analytics processing and third party data mining analysis
1.3 Project Outcomes & Benefits
The project once implemented shall benefit all the stakeholders. The envisaged key benefits to the City
Administration and Citizen are as under:
16
City Administration • The implementation of Pan City interventions will ensure
efficient traffic management, as well as safety and crowd
surveillance.
• The central command and control will ensure efficient
continued working of the field equipment
• Continuous surveillance would help in reduction in
number of criminal and unlawful activities, number of
traffic rule violations, illegal parking etc.
• Prompt emergency response in cases of accidents, fires,
disasters, epidemics, etc. due to availability of real time
data and response mechanisms
• To lower the costs by adopting a centralized architecture,
enabling the platform to be administered and supported
from one location
• Instant MIS reports for planning, budgeting, monitoring
& evaluation
• Instant identification of delay points enabling prompt
administrative action
• Facilitate cross-department collaboration with the help
of online systems in compliance with various standard
operating procedures will bring transparency in city
administration
Citizens • Better city planning and development
• Services delivered to citizens, faster, and at a lower
operating expense
• Local economic development
• Citizens will also be able to have access to efficient, safe
& reliable Urban Transport System
• Improve communication between government
administrators and citizens by building an interactive
Web portal to disseminate information and submit
grievances
17
Setting up of Traffic Management and Monitoring Centre shall have the following additional benefits:
• Improvement in overall traffic flow by efficient traffic management thereby improving the
efficiency of transportation network
• Improved flow of traffic resulting in savings in time for commuters
• Increased road user satisfaction driven by access to real-time information of traffic
• Reduction in traffic congestion
• Capital expenditure on physical infrastructure build-up to cater to traffic requirements can be
avoided or postponed
• Reduction in energy consumption for transportation
• Reduction in pollution and Green House Gas (GHG) emissions
• Improvement in coordination amongst various agencies and enabling faster responses to
incidents
• Improved planning for traffic management both, for short term measures as well as long term
interventions based on data mining and analysis
• Useful for accident data collection and analysis
• Collected data can be used for framing the traffic policy for the city
2 Detailed Scope of Work for System Integrator for TMMC
The System Integrator (SI), shall have the overall responsibility to design, build, implement,
commission, operate and maintain the project for a period of five years from the date of successful
commissioning/Go-live.
The snapshot of scope is as below:
• The Agency / Bidder will conduct a detailed assessment and design a comprehensive technical
architecture and project plan including:
a. Assessment of the business requirements and information technology (IT) Solution
requirements for the TMMC
b. Design and build the solution for TMMC as per the Design and functional
Considerations
c. Facelift of the building to house the TMMC
d. Plan for development, configuration and customization of software products
e. Design and build the cyber security infrastructure
f. Conduct Integration test cases to achieve seamless integration with envisaged smart
city systems and applications
18
g. Conduct Testing, training and commissioning of the complete system
• Agency / Bidder will have to ensure the compatibility of scope mentioned in this document with
Integrated Command and Control Centre (ICCC) of Jammu Smart City (to be implemented
separately in future)
• Agency / Bidder will design, supply, install and maintain for 3 years from the date of go live, all
solutions mentioned in the document and Traffic Management and Monitoring Centre (TMMC)
comprising but not limited to:
a. IT Infrastructure / Data Center
b. Video Wall & controller system
c. GIS Application.
d. Operator Workstation and accessories
e. Contact Center
• Agency / Bidder will be required to conduct the survey of the existing systems and accordingly
define the implementation roadmap for field devices and network backbone
a. Assessment of the business requirements and IT Solution requirements
b. Design and build the solution as per the Design and Functional Considerations
c. Design and build the minimum Cyber Security infrastructure
d. Plan for development, configuration and customization of software products
e. Conduct Integration test cases to achieve seamless integration with envisaged existing,
planned, upcoming and ongoing smart city systems and applications
f. Conduct Testing, training and commissioning of the complete system
• Agency / Bidder will be required to provide Help Desk and Call Centre (with operators 24X7) in
TMMC for following activities:
a. To receive call from citizens, forwarding the same to the respective officials, updating
the status to the citizens on 24X7X365.
b. Technical and Operational support of the system.
c. Maintenance of the IT and Non-IT Infrastructure
d. Technical & Operational Manpower for smooth running of the system
e. This help desk will also act as a functional call center to send instructions to various
field agencies to do the needful.
Following table provides Feature, Objective and the high-level scope for implementation of the project:
19
Feature Objective High Level Scope
Traffic Management and Monitoring Center
Key Objectives of the TMMC:
1) Traffic Enforcement
On-road checks Red light violations detection Handheld Device Based e-Challan System
Entry restriction violations
2) Monitoring and management of Traffic
Management and Monitoring of Traffic: - Signal Timing and Operations (using
existing ATCS) - Active Traffic and Demand
management - Road Network Surveillance
Monitoring the functional status of various traffic equipment and taking steps towards restoration of defective equipment, including, - Traffic Signals - Sensors - Cameras - Advertisement Boards - Speakers
Interfacing with various agencies to obtain information impacting traffic flows - Transit Operations - Parking Management and Operations - Weather Information - Disaster Information
Support traffic management activities
related to planned events and emergencies in coordination and collaboration with other city agencies
Detecting traffic incidents and supporting authorities in responding to these by way of coordination, information sharing and dissemination
Sharing of traffic data and information with various agencies such as transit, road construction and maintenance, Traffic Police etc. to help such agencies to monitor and control their respective
Design , Supply , Installation , Testing, Training, Commissioning and Maintenance of TMMC comprising of Decision Support System, Integration, Visualization and the BI & Analytics tool hosted on a premise data center and cloud based disaster recovery centre, Control room for Maximum 10 operators , Contact center for 3-5 Operators.
TMMC Solution should have central infrastructure and Services management platform to centrally monitor and manage all the services.
TMMC shall host Implemented and Integrated Services as detailed in this document.
20
operations more efficiently
3) Dissemination of Traffic Information to
Public
Dissemination of traffic information to
public through various channels like Variable message signs/advertisement boards
Dissemination to existing website, helplines, mobile applications, social media etc.
4) Data Repository and Analysis
Storage of traffic data and sharing the
same with planning and enforcement agencies in order to support transport planning measures in the city
Analysis of traffic related data and data mining to support infrastructure planning and design.
Traffic flow analysis
Providing inputs to road agencies in junction planning and layout design
Secure Data Center and Cloud based Disaster Recovery
• To provide IT infrastructure for Hosting of Application
• To provide cyber security layer for protecting the data from cyber threats
Design, Supply Installation, Testing, Commissioning and Maintenance of On Premise Data Center and Cloud based Disaster recovery center as defined in this RFP
Implementation of On Field Equipment/ Smart Solutions and leased line network backbone – Surveillance Cameras, Advertisement boards, Environment Sensors and Intelligent Traffic Management System
• Decision Support system for City Administration for city operations
• Pro-active 24x7 monitoring of city assets and public interest areas
• Provision of secure and safe environment for the citizen
• Monitoring Environment Pollution and integrate it with disaster management
• Assisting Awareness of government initiatives and public guidelines through Advertisement Boards
• Improve Journey Time - Improve reliability in journey times between
Design, Supply, Installation, Testing and Commissioning and Maintenance of Traffic Surveillance , Intelligent Traffic Management System ( ANPR , RLVD , E-Challaning, Public addressing system), Environmental Sensors, Advertisement Boards
Implementation of Leased line network for connectivity and
Integration with existing
21
various locations, so that citizens can experience an enhanced quality of road-based transportation, through improving sustainability and efficiency in operation of the road network
• Increase Signal Efficiency - Reduction in traffic delays, optimized cycle times at intersection to regulate and maintain free flow of traffic to enhance the efficiency of the transport infrastructure.
• Increase Operational Efficiency- Use of Information technology solutions should help in reducing the repetitive paperwork/records and making the back-office functions more efficient
• Improve Customer Services - The traffic services to the public can be improved through the user-friendly presentation of the various traffic information in real time through sharing of all relevant data feeds for public consumption.
Adaptive Traffic control system for Traffic Signals (ATCS on 64 Locations) and other external agencies
These field equipment shall be real time monitored in TMCC and shall be connected through Leased line network.
System Integrator shall design and implement the solution to meet the objectives detailed in this RFP.
2.1. Detailed Project Plan and System Design Document
The ITMS System Integrator should provide as part of System Design Document, the details as specifying the
following:
i. The ITMS system integrator shall prepare and submit document which shall include a
comprehensive survey and study of traffic junction location as per the list defined in RFP
ii. High Level Design (including but not limited to) Junction Lay Out Drawing, System
Architecture, Junction Network topology and physical infrastructure design for devices on the
field
iii. Placement of Gantry / System/ Equipment as per the Junction layout geometry for all the all
the proposed systems
iv. Software Requirement Specifications (SRS) for the ITMS component applications
v. Low Level Design- LLD (including but not limited to) Application flows and logic including flow
chart, GUI design (screen shorts and flows etc.), Database architecture, including defining data
structure, data dictionary as per standards.
vi. Location of all field systems and components proposed at the junctions, (KML / KMZ file
plotted on GIS platform like Google Earth etc.)
vii. Detailed BOQ of all the equipment required to be installed in the field as well as in the Traffic
Control Center for the ITMS. The ITMS System Integrator shall optimize the quantity of the
22
equipment (such as cameras, gantries, junction boxes, UPSs etc.) required for different sub-
systems of ITMS without compromising on the desired functionalities
viii. All the data sheets of field equipment / devices such as Junction Boxes, Traffic Signals, PA
system, RLVD, ANPR and other sub-systems of ITMS shall be provided
ix. Details of gantry design drawing with foundation design and other mounting structure shall be
provided
x. Details of ground clearance height and foundation of cantilevers, gantry and other mounting
structures for other field devices shall be provided.
xi. Location of Network Provider’s Point of Presence (PoP) shall be provided.
xii. Design of Cables, Ducts routing, digging and trenching shall be provided.
xiii. Electrical power infrastructure provisioning and back provision details shall be provided.
xiv. Names of the Project Team members, their roles and responsibilities
xv. Approach and methodology to be adopted to implement the Project (which should be in line
with what has been proposed during bidding stage but may have value additions / learning in
the interest of the project).
xvi. Responsibility matrix for all stakeholders
xvii. Risks the ITMS System Integrator anticipates and the plans they have towards their mitigation
xviii. Activity and work plan specifying dependencies between various project activities / sub-
activities and their timelines
xix. Project Plan with all the micro activities with timeline
xx. The detailed solution document for end to end e-Challan process
2.2. Site Clearance obligations & other general provisions
2.2.1. Survey and Commencement of Works
Prior to starting the site clearance, the ITMS System Integrator shall carry out survey of field
locations as specified in Annexure (List of Indicative Locations, for buildings, structures, fences,
drains, trees, existing installations, etc.) The JMC/JSCL shall be fully informed of the results of
the survey and the amount and extent of the demolition and site clearance shall then be agreed
with the JMC/JSCL.
2.2.2. Existing Traffic Signal system
The infrastructure of existing traffic signal shall be used wherever these signals are installed and
in operational condition
2.2.3. Road signs
All existing road signs which are likely to be affected by the works are to be carefully taken
down and stored. Signs to be re-commissioned shall be cleaned, provided with new fixings
where necessary and the posts re-painted in accordance with JMC guidelines. Road signs, street
name plate, traffic signals, controllers or any other public property etc. damaged by the ITMS
System Integrator during their operation shall be repaired or replaced by ITMS System
Integrator at no additional cost.
23
2.2.4. Electrical works and power supply
Responsibility on provision of mains power supply at all project locations shall be provided by
JSCL. The charges for obtaining electricity connections shall be paid by JSCL. The JSCL shall be
responsible to pay the electricity charges to the electricity board directly. The ITMS System
Integrator shall have responsibility to distribute the Power form the Junction to further Field
Equipment. Utilities like petrol, diesel, telephone lines, etc. used for ITMS/TMMC infrastructure
will be paid by bidder upfront and then JSCL will reimburse the bills based on the monthly
invoices from bidder as per actuals.
The ITMS System Integrator shall comply with lightning-protection for all the structures (Gantry)
as per IS 2309 standard.
2.2.5. Earthing System
i. The ITMS System Integrator shall comply with earthing-protection for all electric
equipment at the junction including Gantry as per IS 3043 standards.
ii. At ITMS/TMMC, earthing should be done for the entire power system including but not
limited to UPS systems, Power distribution units, Server racks, AC units, etc. to avoid a
ground differential. JMC shall provide the necessary space required to prepare the
earthing pits. Preparation of earthing pits shall be the responsibility of System Integrator
2.2.6. Junction Box, Gantries and Cantilever
i. The ITMS System Integrator shall provide the junction boxes, gantries and cantilever to
mount the field devices like the cameras, traffic sensors, traffic light aspects, active
network components, controller and UPS at all field locations, as per the specifications
given in the RFP
ii. The Junction Box needs to be appropriately sized in-order to accommodate the systems
envisaged at the Junctions. The SI should design the Junction box for 1.5 times the
actual size the ITMS System Integrator requires for utilization under the ITMS project
iii. The junction box should be designed in a way that it shall have lock & key facility to
secure the equipment housed in it
iv. The junction boxes, gantries, and cantilevers shall be aesthetically designed
2.2.7. Cabling Infrastructure
i. The ITMS System Integrator shall provide standardized cabling for all devices and
subsystems in the field and Traffic Control Center
ii. All cables shall be clearly labelled with indelible indications that can clearly be identified
by maintenance personnel. The proposed cables shall meet the valid directives and
standards
iii. Cabling must be carried out per relevant BIS standards. All cabling shall be documented
in a cable layout plan by the ITMS System Integrator.
2.2.8. Road Marking (Zebra / Stop line)
i. The ITMS System Integrator shall be required to undertake the Junction markings
including edge lines, centre line, pedestrian markings for Zebra crossing and stop line,
lane markings, directional arrow markings etc. at all junctions as per Ministry of Road
Transport and Highways (MoRTH) and Indian Roads Congress (IRC) guidelines
24
ii. The ITMS System Integrator shall submit as part of the system design report, the
detailed plan of undertaking this task including prior approvals for timings of road
closure/ junction closure if required from the JMC/JSCL
iii. The task of junction marking shall be carried out with minimum disruption of traffic,
with appropriate signage informing the road users of any diversions/ road closures being
undertaken.
2.2.9. RoW (Right of Way)
JMC will provide the RoW (Right of Way) for the installation of all ITMS components from the
respective Authority
2.3. Design, Supply, Installation, Testing & Operation of Field Equipment
All field equipment for enforcement system and Advertisement Boards will be installed on Gantry
only, if the gantry installation is not feasible at particular location /junction the ITMS System
Integrator will have to inform the JMC and take prior permission to install the required Pole
2.3.1. Traffic Junction Surveillance System
The broad scope of work to be covered under this module will include the following, but is not
limited to:
i. The ITMS System Integrator shall install Traffic Surveillance cameras at identified
junctions for traffic monitoring and management at identified junctions in this RFP
document
ii. The ITMS System Integrator shall undertake due diligence for selection and placement
of traffic surveillance cameras to ensure the full coverage of the traffic junction along
with all associated junction arms, accuracy of the information captured on the field and
for rugged operations.
iii. The ITMS System Integrator shall design, supply, and install the traffic surveillance
cameras as defined in the RFP, all wiring connections for the system shall be installed by
the ITMS System Integrator. The ITMS System Integrator shall supply all the necessary
equipment for the camera operations including camera housings and mountings,
camera poles, switches, cabling, and shall make the final connections to the junction
box.
iv. The ITMS System Integrator shall be responsible for providing all the necessary IT
infrastructure for monitoring, recording, storage & retrieval of the infraction
information at ITMS/TMMC or any other location as specified in the RFP
2.3.2. Public Address (PA) System
The broad scope of work to be covered under this module shall include the following, but is not
limited to:
i. The ITMS System Integrator shall supply and install PA system at the locations as
provided in this RFP document. PA systems shall be controlled from the ITMS/TMMC.
The purpose of the PA system shall be to provide pre-recorded and real time
announcements in case of emergencies, disasters etc.at identified traffic junctions
ii. Details on technical and functional specifications of PA system, have been provided in
this RFP document.
25
2.3.3. Red Light Violation Detection (RLVD) System
The broad scope of work to be covered under this module shall include, but not limited to, the
following:
i. The ITMS System Integrator shall install the RLVD Systems at the identified traffic
junctions as provided in this RFP document. This system shall capture the following
infractions, at the minimum, at these junctions:
a. Red light violation
b. Stop line violation
ii. The ITMS System Integrator shall design, supply, and install the RLVD system as defined
in the RFP, all wiring connections to the traffic signal controllers and to the camera
platforms shall be installed by the ITMS System Integrator. The ITMS System Integrator
shall supply all of the necessary equipment for the camera and detection system,
including but not limited to computers/processors, ancillary camera equipment, camera
housings, gantry, warning signs and shall make the final connections to the camera.
a. The ITMS System Integrator shall be responsible for providing all the necessary
IT infrastructure for analysis, storage & retrieval of the infraction information
at ITMS/TMMC or any other location as specified in the RFP.
b. The solution proposed by the ITMS System Integrator shall have the capability
to seamlessly integrate with the E-Challan system as proposed as a part of this
project.
c. Details on technical and functional specifications of Red Light Violation
Detection (RLVD) system have been provided in this RFP document.
2.3.4. Automatic Number Plate Recognition (ANPR) System
The broad scope of work to be covered under this module shall include the following, but not
limited to:
i. The ITMS System Integrator shall install the ANPR Cameras at specified location as
provided in this RFP document. This system shall automatically capture the license
number plate of the vehicle at these locations
ii. The ITMS System Integrator shall design, supply, and install the ANPR camera system as
defined in the RFP, all camera accessories such as IR Illuminators, camera housing and
mounting shall be installed by the SI. The ITMS System Integrator shall supply all of the
necessary equipment for the camera and local processing system, including but not
limited to computers/processors, local storage and ancillary camera equipment, gantry,
warning signs and shall make the final connections to the camera.
iii. The ITMS System Integrator shall be responsible for providing all the necessary IT
infrastructure for analysis, storage & retrieval of the data capture through ANPR system
at ITMS/TMMC
iv. The Automatic Number Plate Recognition (ANPR) System will give count of vehicles as
well as classification of vehicles passing through the location
v. Details on technical and functional specifications of ANPR Cameras have been provided
in this RFP document
26
2.3.5. E-Challan System
The ITMS System Integrator shall be responsible to undertake following activities, but not
limited to:
i. Design, development and implementation of e-Challan Software Solution for end-to-end e-
challan management
ii. The E-Challan system shall be configured to automatically generate traffic challans based on
infractions received from the installed field equipment including RLVD and ANPR systems.
iii. The ITMS System Integrator shall ensure that the proposed system has the capability for
complete automation of the challan processing/ printing process with minimal manual
intervention. This shall involve automatic capturing of relevant information from the evidence
generated by the traffic enforcement system and integrating it with the state wide vehicle
database, national Vahan database or any other database
iv. The ITMS System Integrator shall ensure the printing of challans at TMMC. Physical delivery of
the challan to the respective violator through Speed Post/ Courier/ by other means to ensure
physical delivery shall be the responsibility of JMC/JSCL/Traffic Police.
v. Undelivered / wrong address / incomplete address challan shall be reported to the authorities
for taking required corrective action.
vi. The ITMS System Integrator shall formulate suitable procedure for payment collection for
challan and deposit it to the respective authorities.
vii. The detailed functional and technical specification details of the E-Challan system are provided
in Section 5 of this RFP document.
2.3.6. Variable Message Sign (VaMS) System/Advertisement Panels
The broad scope of work to be covered under this module shall include the following, but not
limited to:
i. The ITMS System Integrator shall supply, install and commission the VaMS Systems at the
identified traffic junctions/locations, as decided by JMC
ii. The VaMS System shall be used to inform, warn, and guide the motorists by displaying
information such as traffic congestions, accidents, road closure, road maintenance activities,
events (rallies, demonstrations) affecting road conditions and other relevant information.
iii. One of the major use for these panels shall be for Advertisements. While the SI shall deploy the
hardware and software to display and manage the advertisements, JSCL / JMC shall have the
right to tender out advertisement rights on these ad panels.
iv. VaMS System shall also be used for public information system by running the social messages
and commercials advertisements, special events etc.
v. The VaMS shall be seamlessly integrated with ITMS for displaying messages and controlling
VaMS from ITMS.
2.3.7. Network Connectivity between Field Locations to TMMC
i. The ITMS System Integrator shall provide a detailed network architecture of the overall ITMS
solution, incorporating findings of detailed site survey. The network so envisaged should be able
to provide real time data streams to the ITMS/TMMC. All the components of the technical
network architecture should be of industry best standard and assist in ensuring that all the
connectivity SLAs are adhered to during the O&M phase.
27
ii. A Dedicated leased line/fiber network should be available between all main junctions and DC.
The network should be available with 99.5% SLA
iii. Connectivity to Data Center and ITMS/TMMC shall be provided with scalable capacities to allow
for expansion in the future
iv. ITMS System Integrator shall provide a firm quote from any bandwidth provider in the region
clearly showing the costing of proposed bandwidth. JSCL / JMC and SI shall enter into a tripartite
agreement with ISP for providing bandwidth for the project. The cost of proposed bandwidth
shall NOT be added in Proposed Commercial Bid.
v. The ITMS System Integrator is required to provide connectivity for all the components of ITMS
including the following:
a) Connectivity for locations with Jn surveillance, ANPR, Ad Panels, PA and RLVD
system
b) Internet Leased line connectivity for Data Center & ITMS
The minimum bandwidth for each component/location shall be as below:
Sl. # ITMS Solution/Module Approximation for consideration
1.
Junctions with the following systems:
• Jn surveillance
• PA system
• RLVD System
• ANPR System
• VaMS //Advertisement Panels
Minimum 24 Mbps per junction and as
per solution requirement. SI should make
sure enough Bandwidth to be provided
for 5MP @25 FPS Video stream along
with PA system and Vams Bandwidth
requirement.
2. Connectivity at DC and ITMS/TMMC Minimum 1.5 Gbps and up to as per
solution requirement.
Note:
The actual bandwidth requirement to meet the desired functionality, performance, quality and
security of ITMS solutions and to meet SLAs shall be calculated by the ITMS System Integrator and
provided at respective locations. JMC reserves the right to ask the ITMS System Integrator to
increase the bandwidth if the provided bandwidth is not sufficient to give the functionality of the
system mentioned in the RFP and adhere to the SLAs.
2.4. Traffic Control Center and Data Center
Proposed location of Traffic Control Center and Data Center:
Police lines, Gulshan Ground,
Jammu-
Or
any Building as finalized by the JMC.
28
2.4.1. Traffic Control Centre (ITMS)/Traffic Management and Monitoring Centre (TMMC)
The ITMS System Integrator shall set up a state of the art Traffic Management and Monitoring
Centre (TMMC) for the ITMS project, at the building provided by JMC. The Traffic Control Center
is planned to be set up in the Jammu city. JMC shall make available approximate 2000 square
feet built-up space for setting up of ITMS and DC. Additional 1000 sqft will need to be built by
the SI. This is over and above the ATCS Centre, which is approx. 1000 Sqft. The key components
of the ITMS shall be as follows:
i. Video wall
ii. Operators workstations
iii. Connectivity Wired and Wireless with controller
iv. Network printers, Online UPS etc.
v. Security cameras for DC
vi. Servers and Storage
vii. Other ICT infrastructure
viii. Meeting Room / Conference Room Infrastructure
ix. OS and all supported software
x. Desktop Workstations, Multifunction printer, Color Printer etc.
2.4.2. Data Centre (DC)
The ITMS System Integrator shall supply and install hosting infrastructure for ITMS (including
but not limited to servers, storage, operating systems, database, security, networking,
connectivity, rack, etc.) at Traffic Control Center (ITMS). JSCL shall provide adequate space for
servers and other IT infrastructure. The ITMS System Integrator shall also maintain and manage
the Data Center during the Contract Period.
Detailed requirement and the Bill of Materials for ITMS and DC are provided in this RFP
The Planning, Design and Implementation Services for Data Centre transformation combine the
people, processes and technology, with the program and project management necessary to
transform an existing data centres into one that provides business agility at a lower cost, a wide
range of services for discovery, analysis, optimization, automation, virtualization and migration
of data centres that can complement client efforts and fill gaps in client skills and capacities.
Various aspects of the data centers include:
• Facilities: layout, power/cooling, physical security, manpower
• System infrastructure: servers, networking (with LAN), storage, and security;
• Applications, infrastructure mapping & dependencies;
• Design Standard: Tier-III or above (ISO 27000, ISO 20000 certification to be done within 9 months of go-live)
• The availability of data must be guaranteeing to 99.5% availability.
• UPS: UPS system in active-active redundancy
• Generator: Gen-set: 1 with redundancy
• Power Provision: Dual power feed, PDU sources to each rack, Power supply to a rack as per requirement
29
Key Functional Requirements
1. Provide Unified visibility, operations & portability across clouds
• Create a common operating environment and foundational elements with abstracted compute, network & security across DC, DR (MeITY empanelled CSP (GCC/VPC (AWS/AZURE))) to have unified visibility, operations and portability across clouds.
2. Provide Unified View of health, performance & security across multiple clouds
• Building Unified view of the health, performance and security of workloads across DC • Centralized visibility of all the cloud environments • Deliver highly efficient and automated IT operations across multi cloud environment.
3. Delivery of IT services across multiple clouds
• Delivery of IT services through automation and pre-defined policies with Self-service capability and Standardized infrastructure offerings
• Defining explicit automation and policy
4. Consistent Security and Networking across multiple clouds
• The network & security policies in the virtualization layer must be tied to the application so as to ensure that there is no manual intervention in redefining Network & Security policies, in case of migration across DC. Also, when the application is deleted, all the security policies related to the application should also be removed.
5. Fully Automated DR and Business Continuity
• The DR should be fully automated including automation of networking and security policies for the workloads. The solution should offer Layer-2 extension which allows virtual machines to retain network connectivity across geographical boundaries. There should be minimal manual intervention and the RTO should be calculated considering the networking and security policies.
6. End to End Network Visibility across clouds
• The Solution should provide real time operational visibility for network and security across clouds. The solution should be able to give comprehensive Network visibility including East west, North South traffic, VM to VM traffic etc.
7. Security across Clouds/ Datacentres
• The solution should offer comprehensive visibility and analytics that tie together compute, network, storage and security and provide Physical to Virtual Correlation and troubleshooting.
• The Network & Security solution should offer virtualized workload at the virtual NIC level to be protected with a full stateful firewall engine at a very granular level based on constructs such as MAC, IP, ports, tags, active directory groups, Security Groups, etc.
30
The solution should offer comprehensive flow assessment and analytics and security groups and
firewall rules suggestion for the purpose of implementing a zero-trust security within the datacentre
8. Civil and Architectural Work
The proposed building requires a facelift in general. The bidder may be required to extend the
existing building to cover additional 1000 Sqft area.
False Ceiling
Metal false ceiling with powder coated 0.5mm thick hot dipped galvanized steel tiles 595 x 595
mm with regular edge (10mm) suitable for 25mm grid supported on suitable powder coated
galvanized steel grid as per manufacturer specification. The same shall be inclusive of cut outs
for lighting, AC grills, Fire detectors, nozzles, etc.
Minimum 12 mm thick fire line Gypsum false ceiling and lighting troughs 300 mm as per
design including 100 mm high cornices as lighting pelmets on G.I. framework, in G.I. vertical
supports at every 450mm c/c and horizontal runners at every 900mm c/c self-taping metal
screws to proper line and level. The same shall be inclusive of making holes and required
framing for fixing electrical fixtures, A.C. grills etc. GI vertical supports to be anchored to slab
by means of anchor fasteners.
Furniture and Fixture
Workstation size of min. 18” depth made with 1.5mm thick laminate of standard make over
18mm thick commercial board complete with wooden beading including cutting holes & fixing
of cable manager etc. complete with polish. Edges shall be factory post-formed. The desk shall
have the necessary drawers, keyboard trays, cabinets etc. along with sliding / opening as per
approved design with quality drawer slides, hinges, locks etc. All workstations, cabins should
be as per industry best practices and standards.
Providing & making of storage unit with 18 mm thick MDF board along with 1.5 mm approved
laminate colour outside and 2 coat of enamel paint inside the storage of size 1'6"x1'6"x2'4".
The same should be provided with all the required accessories including the handle, lock,
sliding channel and necessary hardware, etc. complete with polish
An enclosure for gas cylinder of Shutters and Partitions along with wooden support and 18
mm thick MDF board along with 1.5 mm approved laminate colour outside and 2 coat of
enamel paint inside the shutter. The same should be provided with all the required
accessories including the handle, lock, loaded hinges, tower bolt and necessary hardware etc.
complete with French polish.
Partitions (wherever required as per approved drawing)
Full height partition wall of 125 mm thick fire line gyp-board partition using 12.5 mm thick
double fire line gyp-board on both sides with GI steel metal vertical stud frame of size min. 75
mm fixed in the floor and ceiling channels of 75 mm wide to provide a strong partition. Glass
wool insulation inside shall be provided as required. Fixing is by self-tapping screw with
vertical studs being at 610 mm intervals.
31
The same should be inclusive of making cut-outs for switch board, sockets, grill etc. It shall
also include preparing the surface smoothly and all as per manufacture’s specification etc.
finally finishing with one coat of approved brand of fire resistant coating. Glazing including the
framework of 4" x 2" powder coated aluminium section complete (in areas like partition
between server room & other auxiliary areas).
Fire Rated Wire Glass minimum 6 mm thick for all glazing in the partition wall complete.
(External windows not included in this). All doors should be minimum 1200 mm (4 ft.) wide.
Flooring (wherever required as per approved drawing)
SI shall procure and install a raised floor to match the floor height and room aesthetic in
accordance with the approved final layout and design. SI shall consider standard parameters
for developing the final height, width, point of load, and uniform distribution load of the
raised floor for the rooms based on type of furniture and overall load.
SI shall ensure the following features and parameters are considered while designing and
commissioning the raised floor:
1. Point of Load (PoL) shall be considered 20% more than the actual load
2. Uniform Distribution Load shall be calculated according to the final Point of Load
3. Noise-proof, Fireproof
4. Maintenance window for easy access to under the raised floor
5. Separate electrical and data cable tray under the raised floor
6. Face of floor tiles shall conform to the aesthetic part of the approved design
7. SI shall perform load test and noise test of the constructed raised floor.
The SI shall complete the following requirements for the raised flooring panels:
• Floor shall be designed for standard load conforming to BIS 875-1987.
• Panels shall be made up of 18-gauge steel of 600 mm × 600 mm size treated for
corrosion and coated with epoxy conductive paint (minimum thickness 50 Micron).
• Raised flooring covering shall be antistatic, high- pressure laminate, two (2) mm thick
in approved shade and color with PVC trim edge. It shall not make any noise while
walking on it or moving equipment. Load and stress tests on floor panels shall be
performed as part of acceptance testing.
Air Conditioning and Natural Convection
For Data Centre, Precision remote control and manual operated air conditioning system shall
be exclusively installed to maintain the required temperature in the data center server farm
area. The A/C shall be capable of providing sensible cooling capacities at ambient temperature
and humidity with adequate air flow. Air conditioner shall be linked to secondary power
supply as well to prevent them from shutting down in case of power outage
Painting
Provide and apply Fire retardant paint of pre-approved make and shade to give an even shade
over a primer coat as per manufacturers’ recommendations after applying painting putty to
32
level and plumb and finishing with 2 coats of fire retardant paint. Base coating shall be as per
manufacturer’s recommendation for coverage of paint, For all vertical Plain surface and fire
line gyp-board ceiling.
Use approved fire retardant coating on all vertical surfaces, furniture etc. as per
manufacturer's specification.
PVC conduit
The conduits for all systems shall be high impact rigid PVC heavy-duty type and shall comply
with I.E.E regulations for non- metallic conduit 1.6 mm thick as per IS 9537/1983. All sections
of conduit and relevant boxes shall be properly cleaned and glued using appropriate epoxy
resin glue and the proper connecting pieces, like conduit fittings such as Mild Steel and should
be so installed that they can remain accessible for existing cable or the installing of the
additional cables.
No conduit less than 20mm external diameter shall be used. Conduit runs shall be so arranged
that the cables connected to separate main circuits shall be enclosed in separate conduits, and
that all lead and return wire of each circuit shall be run to the same circuit.
All conduits shall be smooth in bore, true in size and all ends where conduits are cut shall be
carefully made true and all sharp edges trimmed. All joints between lengths of conduit or
between conduit and fittings boxes shall be pushed firmly together and glued properly.
Wiring
PVC insulated copper conductor cable shall be used for sub circuit runs from the distribution
boards to the points and shall be pulled into conduits. Looping system of wring shall be used,
wires shall not be jointed. No reduction of strands is permitted at terminations.
Wherever wiring is run through trunking or raceways, the wires emerging from individual
distributions shall be bunched together with cable straps at required regular intervals.
Identification ferrules indication the circuit and D.B. number shall be where required
Where, single phase circuits are supplied from a three phase and a neutral distribution board,
no conduit shall contain wiring fed from more than one phase in any one room in the
premises, where all or part of the electrical load consists of lights, fans and/or other single
phase current consuming devices, all shall be connected to the same phase of the supply.
Circuits fed from distinct sources of supply or from different distribution boards or M.C.B.s
shall not be bunched in one conduit. In large areas and other situations where the load is
divided between two or three phases, no two single-phase switches connected to difference
phase shall be mounted within two meters of each other.
All splicing shall be done by means of terminal blocks or connectors and no twisting
connection between conductors shall be allowed. Metal clad sockets shall be of die cast non-
corroding zinc alloy and deeply recessed contact tubes. Visible scraping type earth terminal
shall be provided. Socket shall have push on protective cap.
Balancing of circuits in three phases installed shall be arranged before installation is taken up.
Unless otherwise specified not more than ten light points shall be grouped on one circuit and
the load per circuit shall not exceed 1000 watts.
33
Cable Work
Cable ducts should be of such dimension that the cables laid in it do not touch one another. If
found necessary, the cable shall be fixed with clamps on the walls of the duct. Cables shall be
laid on the walls/on the trays as required using suitable clamping/ fixing arrangement as
required. Cables shall be neatly arranged on the trays in such manner that a crisscrossing is
avoided, and final take off to switch gear is easily facilitated. Cable shall be laid as per the IS
standard
All cables will be identified close to their termination point by cable number as per circuit
schedule. Cable numbers should be properly punched. For trip circuit identification additional
red ferrules are to be used only in the switch gear / control panels, cables shall be supported
to prevent appreciable sagging. In general distance between supports shall not be greater
than 600mm for horizontal run and 750mm for vertical run.
Each section of the rising mains shall be provided with suitable wall straps so that same can be
mounted on the wall.
Whenever the rising mains pass through the floor, they shall be provided with a built-in fire
proof barrier so that this barrier restricts the spread of fire through the rising mains from one
section to the other adjacent section.
Neoprene rubber gaskets shall be provided between the covers and channel to satisfy the
operating conditions imposed by temperature weathering, durability etc.
Necessary earthling arrangement shall be made alongside the rising mains enclosure by Mean
of a GI strip of adequate size bolted to each section and shall be earthed at both ends. The
rising mains enclosure shall be bolted type.
The space between data and power cabling should be as per standards and there should not
be any crisscross wiring of the two, in order to avoid any interference, or corruption of data.
Fire Detection and Control Mechanism
Fire can have disastrous consequences and affect operations of a Control Room. It is required
that there is early-detection of fire for effective functioning of the Control Room. The facility
shall be equipped with adequate and advanced Fire Detection and Suppression system. The
system shall raise an alarm in the event of smoke detection. The system shall have proper
signage, response indicators and hooters in case of an emergency. The system shall be based
as per NFPA standards.
• Should proactively alert in case there is a possibility of an electrical fire (short circuit
or over current)
• The system should have the capability to integrate with different makes of fire alarm
systems in the DCs and provide the alarms generated by the system on the
centralized Dashboard.
• The system should be able to plan and process a proper evacuation plan in case of
fire
• Trigger Audio and Visual alarm
• Co-relate with the nearest camera in the site with the zone of the FAS.
34
• Switching ON of lights on the evacuation pathway.
Rodent Repellent System
The entry of Rodents and other unwanted pests shall be controlled using non-chemical,
nontoxic devices. Ultrasonic pest repellents shall be provided in the false flooring and ceiling
to repel the pests without killing them. However, SI shall conduct periodic pest control using
chemical spray once in a quarter as a contingency measure to effectively fight pests.
Access Control System
The Access Control System shall be deployed with the objective of allowing entry and exit to
and from the premises to authorized personnel only. The system deployed shall be based on
Biometric Technology. An access control system consisting of a central PC, intelligent
controllers, power supplies and all associated accessories is required to make a fully
operational on line access control system. Access control shall be provided for doors. These
doors shall be provided with electric locks, and shall operate on fail-safe principle.
The lock shall remain unlocked in the event of a fire alarm or in the event of a power failure.
The fire alarm supplier shall make potential free contacts available for releasing the locks in a
fire condition especially for staircase and main doors. Entry to the restricted area shall be by
showing a proximity card near the reader and exit shall be using a push button installed in the
secure area. The system shall monitor the status of the doors through magnetic reed contacts.
The system should be designed and implemented to provide following functionality:
S.No Description
1. 1 Controlled Entries to defined access points
2. 2 Controlled exits from defined access points
3. 3 Controlled entries and exits for visitors
4. 4 Configurable system for user defined access policy for each access point
5. 5 Record, report and archive each activity (permission granted and / or rejected) for each access point.
6. 6 User defined reporting and log formats
7. 7 Fail safe operation in case of no-power condition and abnormal condition such as fire, theft, intrusion, loss of access control, etc.
8. 8 Day, Date, Time and duration-based access rights should be user configurable for each access point and for each user.
9
One user can have different policy / access rights for different access points.
2.5. Smart DR Solution – Hosted on GCC/MEITY certified Cloud
DR design should be 25% of DC (compute and RAM), 10% of Video storage
Various ICT equipment to be provisioned and maintained by SI at the Data Centre is given below.
The backup storage should be active-active. All equipment in DC should be in HA. DR should be on
cloud as a service and 99.5 % uptime.
35
The proposed Cloud Service Provider (CSP) must be an empanelled cloud service provider by MEITY
(Ministry of Electronics and Information Technology) for Public cloud, Virtual Private Cloud and
Government Community Cloud.
• The Cloud Data Centre Facility for DR must be within India and must be Tier III or above. The
DR site should be in a different seismic zone
• DC/DR would operate in an active passive state with 25% data should be replicated from
primary to DR site.
• DR automation solution for automated failover, failback and recovery of application VMs in
proper sequence to other data center with single click from the virtualization console.
• Solution to perform non-disruptive DR drill/testing of recovery plan for full and selected
applications every six months without impacting production applications running in primary
environment.
• Cloud-orchestration and self-service portal should be either from single OEM or should have
Out-of-the box integration to avoid the integration challenges. Said Integration may need to
be demonstrated during the bid evaluation phase.
• Shall have the capability to provide adequate bandwidth between Primary Data Centre and
Disaster Recovery Centre for data replication purpose and should provide extension of layer 2
network across data centre for smooth failover of movement of VMs across DCs and DR.
• DR should be on dedicated hosts within the cloud, and hypervisor should be same across DC
and DR for consistence failover and failback of operations.
• Network and security should be integrated with cloud so automated and on-demand creation
of network, Security and load balancing policies is done as soon as VM is created
• Security policies should follow the Virtual Machines as it moves within the cloud within and
across data centres.
Functional Requirements
• SI is required to provision for a Disaster Recovery (DR) as a service on cloud with 25% capacity
of DC as standard for JSCL Solution. The DR site should not be in the same seismic zone
• The SI shall establish dedicated connectivity between the DC and DR Site for replication &
failover and they should offer Layer-2 VPN to allow you to extend your data centre by allowing
virtual machines to retain network connectivity across DC and DR (CSP Cloud).
• The SI shall submit the detailed solution document for the DR Site solution
• SI shall also be responsible for providing Cloud service for storing all applications at DR
[minimum 25% production capacity, RTO – 60 mins, RPO – 240 mins] which will be
implemented under JSCL project for the project duration. All H/W and S/W on cloud should
meet the specification in RFP
• Cloud services should be accessible via internet and MPLS.
2.6. Lying & Commissioning of Backbone Fiber Network
The fiber optic network is hybrid topology comprising of a backbone / Core design along with the
access layers in ring topology. Core layer will connect each PoP with TMMC / NoC / DC / DR in ring
topology. Access layer will facilitate connectivity of all last mile locations with PoP. Each last mile
location will be connected to access layer with ring connectivity. The network described in this RFP is
36
illustrative in nature as far as active component is concerned and bidders are free to suggest their
network design.
Estimated pop locations will be 64 in total, remaining lanes/poles shall be connected through fiber
network. Estimated Fiber distance will be 30,000 Meters along with digging, refilling and marking as
per tender scope.
Bidders will implement passive fibre network as per the design site/Project and are free to provide
suggestions for discussion as per the scope defined in this RFP.
Core Layer
The Core backbone topology shall meet the following minimum requirements:
• The Core backbone ring topology shall be constructed using 12 Core armoured Single
mode Optical Fiber Cables (OFC).
• The Core layer shall have including TMMC / DC / DR connecting to each other as
backbone of the network for providing bandwidth to the entire network components.
• The Core shall utilize a 10/40 Gigabit Ethernet / optical technology and shall support 40
Gigabit Ethernet / optical technologies.
• The Core layer shall have 2 numbers of 40mm High Density Polyethylene (HDPE) pipes.
• The maximum fiber distance between two Core / PoP routers in a ring/Mesh/Star based
on project requirement
• Core Layer will be from Service provider pop to TMMC / DC / DR
• The proposed Core layer shall consider 25 % more fibre length than surface length as
spare length, 15% for looping in chambers, 5% for modulation, 1% for splice joint
preparation & remaining 4% for wastage.
• The Core architecture shall to formed in full ring topology to handle single point of
failures.
• The proposed Ring architecture shall support resiliency of sub 50ms ensuring high
availability and faster convergence for service continuity.
Access Layer
• The access layer comprising of ring topology will be connected to different POP locations.
• Each POP location will have one end of multiple access rings/Mesh getting terminated
from both directions which will connect locations i.e. traffic Junctions to provide
connectivity.
• The Access ring shall be constructed using a 12 Core armored Single mode Optical Fiber
Cables (OFC). It shall utilize a 1 Gigabit / 10 Gigabit Ethernet / optical technology.
• It shall have 2 numbers of 40mm High Density Polyethylene (HDPE) pipes.
• The access architecture shall be formed using ring topology.
• The maximum length of one access ring shall not exceed 20 kilometers.
• Maximum 8 Nos. of switches should be considered within a single logical ring on a pair of
fiber.
• The proposed Access ring length considered is 25 % more fibre length than surface length
as spare length, 15% for looping in chambers, 5% for modulation, 1% for splice joint
preparation & remaining 4% for wastage.
37
• The detailed specifications for each components (Active + Passive) are provided in
Annexure I of this RFP.
Detailed Scope
(a) Laying of Cable. The following specifications on laying the UG cable will be strictly adhered to by the
supplier:
Digging of Trench: - The trench for laying the UG cable will be one foot wide and depth will be as
under:
i. 3.5 ft in plains
ii. 2 ft in rocky, mountainous and high altitude terrain
(b) Filling of Sand and Laying. First, six inches of sand will be filled in the trench before laying of cable
begins. After cable is laid, six inches of sand will be put over the cable. Thereafter bricks will be
placed on top of the sand on the cable and trench closed. The method of placing bricks will be as
under: -
i. 5 x standard per meter placed lengthwise in case of single UG cable
ii. 9 x standard per meter placed breadth wise in case of more than one UG cable.
Road and runway / taxi track crossing.
• Proper ducts will be used to enclose the UG cable.
• HDPE/ rigid PVC pipes/ GI Pipes will be used for protection.
• The depth of trenching must ensure rodent protection.
• The responsibility for ensuring this would be that of vendor. Width at top should be
minimum should be minimum 450 mm but can be more as per soil condition and actual
depth from road surface as to meet the working condition.
• Minimum five bricks will be laid per meter length of HDPE. Brick size will be minimum 200
mm each. The HDPE pipe will be of 40 mm outer diameter with minimum wall thickness of
3.5 mm. The following specifications will be met:
(i) Co- efficient of friction - < 0.1
(ii) Blowing pressure - upto 10 bar
(iii) Environmental stress crack - As per ATSM D-1693
(iv) Crush resistance Test - As per IEC standard
(v) Internal Pressure Cre - 48 hrs at 800 C as per IS 4984-1995 Rupture Test
(vi) Impact Resistance Te - No crack or split as per IS-12295 (Part 9) -1986
38
(vii) Reversion Test- Less than 3 % as per IS 4984-1995
• The laying of the cable will be at least 1.65 m depth as per DOT standard and specifications
inside HDPE pipe (schematic diagram given below). Wherever required for turns, bridges,
culverts etc.
(c) Cable Route Markers.
• A minimum of 10 cable markers per km of cable route will be put.
• The cable route markers will be five feet long with a six inch diameter metal so that it is 1.5 ft
above ground after the trench is filled.
• Route markers to be fixed on a concrete block to prevent unintentional shifting.
• The cable markers must be placed at all bends roads / bridge / culvert crossing, cable joints and
sewage / electrical UG cable crossings.
• The disc will have following marking:
(i) Type of cable pair and gauge
(ii) Route
(iii) Date of installation
(d) Testing Points (TPs).
The TPs will be fixed at a height of five ft above ground. It will have a metal housing with locking
arrangement to provide protection from rain, dust and security of the line. The TPs will be erected
on cement plinth above ground so that maintenance is easy and it is protected from water logging
etc.
(e) Fixing of DPs.
The external DPs will be fixed on the buildings at a convenient place, and inside, as far as possible,
for ease of maintenance without any disturbance to the occupants. The DPs will be protected from
39
rain and dust and will have proper locking arrangements. The DPs will not be fixed near windows
and doors in the building.
(f) Cable Joints.
All joints in the UG cable will be proper and soldered so that there is no loss / deterioration in
specifications after laying of the cable.
(g) Pillar Boxes.
Pillar boxes are to be mounted on RCC Construction. It should have opening facility both from rear
as well as front. Adequate slope should be given on the top so as to allow rain water to flow. Locking
facility is to be provided and termination is to be done on Krone.
(h) Jointing Kits. As per Standard specifications
(i) Joint testing before commencement of laying.
A joint team consisting of JSCL reps and the reps of vendor will carry out joint testing of the cable
and ensure that the test results conform to the specifications. If any pair in the cable is faulty, the
whole cable will be rejected and the vendor will replace the cable drum with 100% serviceable UG
cable. Test equipment will be provided by the firm. The following tests will be carried out on all the
pairs of UG cable in each cable drum and signed by both the reps of Station Commander and rep of
the vendor:
(i) Conductor resistance
(ii) Insulation resistance
(iii) Cross Talk level
(iv) Attenuation/ Transmission Equivalent
General instructions
• The SI shall provide standardized cabling for all devices and subsystems in the field.
• SI shall ensure the installation of all necessary cables and connectors between the field sensors
/devices assembly, outstation junction box, for pole mounted field sensors /devices the cables
shall be routed down the inside of the pole and through underground duct to the outstation
cabinet.
• All cables shall be clearly labeled with indelible indications that can clearly be identified by
maintenance personnel. The proposed cables shall meet the valid directives and standards.
• All Ethernet components which are to be connected with copper cable need to be connected with
Toolless Field Termination Plug and this Field termination plug should be upgradable to IP54 rating
and must be UL Listed. The plug should have option for colour coding for different services.
• All outside plant copper patch cords should be double jacketed and must be treated with anti-
rodent chemical.
• All fiber patch cords should be armoured and of industrial type.
• Cat 6 Cable should be double jacket with outer jacket HDPE and inner Jacket LSZH and should be
mixed with anti-rodent chemical.
40
• Fiber to be laid from ISP rack to service racks and fiber must be Armored Single Mode 12 core
Fiber.
• Service racks to be installed with DIN rail mountable LIU
• All fiber connectors should be LC type only .
2.7. Implementation of the Information security policy
The ITMS System Integrator shall adhere to the Information Security Policy for the overall Project
and the same would be reviewed and then finalized by JMC & its authorized committees. Cyber
security solution shall be designed in compliance with MoUD Circular K-15016/61/2016-SC-I dated
20th May, 2016. The Security policy needs to be submitted by the ITMS System Integrator within 1st
quarter of the successful Final Acceptance Tests
2.8. Capacity Building and Training
The ITMS System Integrator is required to conduct a proper training need analysis of all the
concerned staff and draw up a systematic training plan in line with the overall Project Plan. For all
these training programs the ITMS System Integrator has to provide necessary training material and
reference manuals (user/maintenance/ administration) along with training schedules for all phases.
The training shall be held at various office/department locations as finalized by JMC.
Trainings would be of two types for different phases of the Project:
1) Functional Training
This training would focus on the use of the software of the various ITMS components at
Traffic Control Center, so that the users are aware of all the operations of Traffic
Enforcement solutions. The training shall be provided to the staff nominated by
JMC/Jammu Traffic Police.
2) Administrative Training
This training would focus on the administration of Traffic Enforcement solutions and would
be imparted to the staff nominated by JMC/JMC/ Jammu Traffic Police.
2.9. Integration with ICCC and other external systems
The ITMS System Integrator shall provide open APIs / SDKs / web services and extend all necessary
technical support for integration with city level Integrated Control and Command Center (ICCC) and
other external systems
2.10. Acceptance Testing
JMC shall review and finalize the detailed acceptance test plan proposed by the ITMS System
Integrator. JMC would also conduct audit of the process, plan and results of the Acceptance Test
carried out by the ITMS System Integrator for both IT & non-IT components.
41
All acceptance testing, project review and monitoring shall be enabled through an agency
nominated by JMC.
Commissioning shall involve the completion of the site preparation, supply and installation of the
required components and making the Project available to the JMC and Jammu Traffic Police for
carrying out live Operations and getting the acceptance of the same from the JMC.
Testing and Commissioning shall be carried out before the commencement of Operations
2.11. Final Acceptance Testing
The final acceptance shall cover 100% of the ITMS Project scope.
After successful testing by the JMC / Jammu Traffic Police or nominated agency, a Final Acceptance
Test (FAT) Certificate shall be issued by JMC to the ITMS System Integrator.
Prerequisite for Carrying out Final Acceptance Test Certificate (FAT) activity:
1) Detailed test plan (component wise) shall be developed by the ITMS System Integrator
with Pass / Fail criteria and approved by JMC. This shall be submitted by ITMS System
Integrator before FAT activity to be carried out.
2) The process flow document for all component related to ITMS Project and relevant
acceptance test document (including IT Components, Non-IT Components etc.) should be
completed & submitted before the 15 days of starting of final acceptance test to the
JMC/Jammu Traffic Police.
3) The training requirements of JMC/Jammu Traffic Police / JMC should be completed before
the final acceptance test
4) All the components and its application software and MIS Software should be hosted at
ITMS and fully functional before the FAT
5) All IT & Non-IT equipment’s / software manuals / brochures / Data Sheets / CD / DVD /
media for all project components shall be duly submitted in original to JMC
6) The ITMS System Integrator shall arrange the necessary test equipment / support
software for performance of FAT and provide documented test results.
The Final Acceptance Test Certificate (FAT) shall include the following:
1) All hardware and software items installed at respective sites as per the required
specification and project plan shall be verified
2) Availability of all the defined services shall be verified
3) The ITMS System Integrator shall be required to demonstrate all the features / facilities /
functionalities as mentioned in the RFP, technical and functional requirements
4) The ITMS System Integrator shall arrange the test equipment required for performance
verification and shall also provide documented test results
42
5) The ITMS System Integrator shall document all the test results as per the test plan and
submit it in Hard and Soft copies to JSCL
Note:
Any delay by the ITMS System Integrator in the Final Acceptance Testing shall render him liable to
the imposition of appropriate Penalties. However, delays identified beyond the control of ITMS
System Integrator shall be considered appropriately and as per mutual agreement between JMC and
ITMS System Integrator.
2.12. System Documents and User Manuals
The ITMS System Integrator shall provide following documentation:
1) Project Commencement: Detailed Project Plan should provide micro level activities with
milestones, deadlines and deliverables and other documents as defined earlier in this
chapter
2) Delivery of Material: Original Manuals from OEMs (Soft and Hard copies). Manufacturer
Authorization Forms
3) Training: Training Material shall be provided which shall include the presentations used
for trainings and also the required relevant documents for the topics being covered.
4) Process Flow Documentation: The ITMS System Integrator shall be responsible for
preparing process flow documentation related to the operation and maintenance of each
and every component of the ITMS Project. The prepared process flow document shall be
formally signed off by JMC before completion of final acceptance test.
a) The ITMS System Integrator shall document all the installation and test
procedure and provide the same to the JMC before handover to JMC.
b) The ITMS System Integrator shall submit a complete set of Line diagram,
complete cabling system layout (as installed), including cable routing, and
connector terminations. The layout shall detail locations of all components and
indicate all wiring pathways.
c) Manuals for configuring of switches, routers etc. shall be provided by ITMS
System Integrator.
d) The ITMS System Integrator shall be responsible for documenting configuration
of all devices and keeping back up of all configuration files, so as to enable quick
recovery in case of failure of devices.
2.13. Operations and Maintenance during Contract Period
The ITMS System Integrator is required to depute a dedicated team of professionals to manage the
Project and ensure adherence to the required SLAs. ITMS System Integrator shall provide operations
and maintenance services for the software, hardware and other IT and Non-IT infrastructure
43
installed as part of ITMS project during the Contract Period, including one (1) year of warranty
period after “Go-Live”.
The activities to be carried out by the ITMS System Integrator during the Contract Period shall
include, but not limited, to the following:
1) Monitor the operation of ITMS components installed at the locations.
2) Periodic cleaning of all system equipment, Camera Lenses installed the Junction / Locations.
3) Periodic / as and when required upgradations of system configuration and software updates.
4) Monitor health of equipment and initiate immediate corrective action in any of any fault.
5) Process e-challans for the violation captured by ITMS, including generation, verification,
printing. Dispatch and tracking of e-challans.
6) Management and Tracking the record of payment received against e-challans and print &
dispatch reminder for pending challans.
7) Assist the traffic Police to track specified vehicles (stolen vehicles or vehicles involved in
crimes) based on ANPR data.
8) Undertake configuration management for all systems.
9) Undertake analytics of traffic data and generate various MIS and analytics reports.
10) Undertake system admin, database admin, back up, archival, network admin activities.
11) Comprehensive maintenance of all equipment/sub-system during Contract period.
12) Set up a Helpline / Call center for verification of addresses, pending challans, reminders,
public help regarding challan etc. The Helpline /Call center shall be one-seater and shall work
in 2 shifts 7 days a week.
13) Restore the system at the location if damaged by accidents and other factors as per the SLA.
14) The repainting of equipment, gantry and street furniture to protect them from rust and
environment.
2.13.1. Project Management Team
The ITMS System Integrator shall be required to provide Project management team to support
the JMC and Jammu Traffic Police in performing their day-to-day functions related to this
system.
ITMS System Integrator is required to depute a dedicated, centralized project management and
technical staff for the overall Project management and interaction with JMC, JMC and Jammu
Traffic Police. An indicative resource requirement for this centralized administration of the
Project is as follows.
Sl. # Name of Position/Role Total No. of
Resources
Deployment Period
(Implementation
Phase)
Deployment Period
(O&M Phase)
1. Project Manager 1 100%
(Full time On-site)
100%
(Full time On-site)
44
Sl. # Name of Position/Role Total No. of
Resources
Deployment Period
(Implementation
Phase)
Deployment Period
(O&M Phase)
2. Technical expert- ITMS/ICT 1 • 70% (On-site)
• 30% (Off-site)
As per project
requirement.
3. Technical Expert –
Network & Security 1
• 70% (On-site)
• 30% (Off-site)
As per project
requirement.
4.
Technical Expert – Server,
Storage, EMS &
Application
1 • 70% (On-site)
• 30% (Off-site)
As per project
requirement.
5. Technicians and Field Staff 3 100%
(Full time On-site)
100%
(Full time On-site)
6.
ITMS Operators including
e-Challan Processing Staff
(O&M Phase) in 2 Shifts
6x3 NA 100%
(Full time On-site)
Note: The above-mentioned manpower effort estimation/requirement is indicative and if the
Bidder / ITMS System Integrator believes that to meet the SLAs, additional manpower is
required, the same may be provided as scope of the project.
The minimum qualification criteria are provided as below:
Sl.
# Name of Position/Role Minimum Qualification & Experience
1. Project Manager
• BE / B. Tech
• 10+ Years of Experience
• 5+ Years of experience in large ICT project
experience
• Minimum 1 large similar (similar to Intelligent
Traffic Management Project) project experience
2. Technical expert-
ITMS/ICT
• BE / B. Tech
• Minimum 5 years of experience, Min.3 years of
experience in traffic domain
• Should have experience of at least one project in
design implementation of Intelligent (preferably
Intelligent) Traffic Management System
• Experience in setting up Command and Control
Centre would be added advantage
3. Technical Expert –
Network & Security
• BE / B.Tech. with CCNA/CCNP
• Minimum 5 years of experience, Min. 3 years of
experience in IT Networks
• Should have experience of at least one project in
design implementation of large IT Network for
similar project
• Certification in Networking would be added
advantage
4. Technical Expert –
Server, Storage, EMS &
• BE / B.Tech. with CCNA/CCNP/MCSA
• Minimum 5 years of experience, Min. 3 years of
45
Sl.
# Name of Position/Role Minimum Qualification & Experience
Application experience in Server, Storage, EMS & Application
• Should have experience of at least one large
project of Server, Storage, EMS & Application
5. Technicians and Field
Staff
• ITI/ Diploma / Senior Secondary Examination with
technical experience
6. ITMS Operators (O&M
Phase)
• ITI/ Diploma / Graduate with computer Training
• Minimum 2 years of relevant experience with
proper trainings on ITMS
2.13.2. Provision of the Operational Manpower to support Operations at Traffic Control Center
The ITMS System Integrator is required to provide suitable manpower to monitor the data feeds
at Traffic Control Centre and support JMC/ Jammu Traffic Police in operationalization of the
ITMS project.
The exact role of these personnel and their responsibilities would be defined and monitored by
JMC/Jammu Traffic Police. The ITMS System Integrator shall be required to provide such
manpower meeting following requirements:
1) All such manpower shall be minimum graduate pass/ ITI/ Diploma holders.
2) All such manpower shall be without any criminal background / record.
3) JMC reserves the right to carry out background check of the personnel proposed on the
Project for verification of criminal record, at the beginning of deployment or during
deployment.
4) ITMS System Integrator shall have to replace any person, if not found suitable for the
job.
5) All the manpower shall be adequately trained on the working of ITMS project and ITMS.
The ITMS operation support staff shall work from the ITMS or any other locations as identified
by JMC/Jammu Traffic Police from where the back-office operations for ITMS can be
undertaken. An indicative list of activities to be performed by the ITMS operation staff are
provided in this RFP
2.13.3. Physical Infrastructure Management and Maintenance Services
All the devices that shall be installed in the ITMS Project as part of the physical infrastructure
should be SNMP enabled and shall be centrally and remotely monitored and managed on a
24x7x365 basis. Industry leading infrastructure management solution should be deployed to
facilitate monitoring and management of the ITMS Infrastructure on one integrated console.
The physical infrastructure management and maintenance services shall include:
1) Proactive and reactive maintenance, repair and replacement of defective components
(IT and Non-IT/ Hardware and Software). The cost for repair and replacement shall be
borne by the ITMS System Integrator during O&M period.
46
2) The ITMS System Integrator shall have to stock and provide adequate onsite and offsite
spare parts and spare component to ensure that the uptime commitment as per SLA is
met. To provide this service it is important for the ITMS System Integrator to have 5 % of
the spares in the inventory.
3) Component that is reported to be down on a given date should be either fully repaired
or replaced by temporary substitute (of equivalent configuration) within the time frame
indicated in the Service Level Agreement (SLA). In case the selected ITMS System
Integrator fails to meet the above standards of maintenance, there shall be a penalty as
specified in the SLA.
4) The ITMS System Integrator shall also maintain records of all maintenance of the system
and shall maintain a logbook on-site that may be inspected by the Jammu Traffic
Police/JMC on a regular basis.
2.13.4. Project Handover
The ITMS System Integrator shall provide knowledge transfer to JMC/Jammu Traffic Police for
upkeep of ITMS components post contract period. The ITMS System Integrator shall carry out
project hand-over of the system at the end of contractual period along with all documentation
required to operate and maintain the system ITMS System Integrator shall supply to the JMC/
Jammu Traffic Police the following before the expiry of the contract:
1) Information relating to the current services rendered and data relating to the
performance of the services; Entire documentation relating to various components of
the Project, any other data and confidential information related to the Project;
2) All other information (including but not limited to documents, records and agreements)
relating to the products & services related to the project to enable Police Department
and its nominated agencies, or its replacing Successful ITMS System Integrator to carry
out due diligence in order to transition the provision of the Project Services to Police
Department or its nominated agencies, or its replacing Successful ITMS System
Integrator (as the case may be).
2.13.5. Other
1) ITMS System Integrator to ensure that for operation and maintenance team take the
safety precautions
2) ITMS System Integrator shall have to arrange vehicles and other requisite such as ladder
etc. for carry out implementation and maintenance work (including transportation of
items required for Project) during the Contract Period.
3) ITMS System Integrator shall pay all the recurring charges for Connectivity etc.
47
4) ITMS System Integrator shall implement the attendance system for the attendance of
Project team proposed in this document. The ITMS System Integrator shall share the
attendance report with the JMC at the end of the month.
5) The JMC shall be responsible to secure and safeguard all field equipment after
Implementation period. In case of any loss or damage due to theft / accident/
vandalism. JMC has to do all the legal formalities with the Police Authorities. System
Integrator shall only be responsible for repair and restoration of all equipment at its
own cost during the operation and maintenance period.
48
3 System Architecture
3.1 Guiding Principle
System Integrator (SI) shall identify the customizations/ workaround that would be required for
successful implementation and operation of the project. The report should take into consideration
following guiding principles:
a. Transformational Nature of Smart City applications Applications should look to fully embrace mobile adoption, online authentication, etc. to transform
the processes completely and offer wider choice and no/low touch point for residents to interact
directly. It is critical that project designs are aligned to larger trends and designed for next decade
rather than past.
b. Use of Open Standard for evolving Technology
The entire system would be built to be open (standards, open API, plug-n-play capabilities like virtual
environments, creating sandbox), components coupled loosely to allow changes in sub- system level
without affecting other parts, architected to work completely within a heterogeneous compute,
storage, and multi-vendor environment. Use of the latest & best available standards to avoid locking
in obsolescent technologies simulated services environment can help agencies to save cost,
Infrastructure and time in testing multiple application integrations.
Large integrated systems of Smart City operations should be designed to get best cost and
performance advantages of natural technology curve (constant increase of speed and decrease of
cost), architecture should be open and vendor neutral, and designed for horizontal scale.
c. Virtualization
Consolidate with Virtualization, Build Software Defined Infrastructure: - For digital transformation,
compute virtualization is the basic unit and a must to have start point. Parallelly steps can be taken
towards unified management including network virtualization.
Build a Unified layer Introduce unified management layer to bring self-service, zero manual touch delivery of virtualized
resources seamlessly to requesting department. At the same time maintaining the governance and
security standards defined by J&K.
Hybrid Cloud Ready Extend the infrastructure to MEITY certified cloud service provider for use cases like infrastructure
bursting or disaster recovery. The management and governance layer can also be extended to
manage public cloud interfaces. The recommended approach is to have same set of infrastructure
virtualization on both sides.
49
d. Distributed, PKI based Authentication and Authorization
The solution shall support PKI based Authentication and Authorization, in accordance with IT Act
2000, using the Digital Certificates issued by the Certifying Authorities (CA). In particular, 3 factor
authentications (login id & password, biometric and digital signature) shall be implemented by the SI
for officials/employees involved in processing citizen services.
e. Security and privacy of data
The security services will cover the user profile management, authentication and authorization
aspects of security control. This service run across all the layers since service components from
different layers will interact with the security components. All public contents should be made
available to all users without authentication. The service will authenticate users and allows access to
other features of the envisaged application for which the user is entitled to.
The system should be designed to provide the appropriate security levels commiserate with the
domain of operation. Also, the system will ensure data confidentiality and data integrity. The
architecture must adopt an end-to-end security model that protects data and the infrastructure from
malicious attacks, theft, natural disasters etc.
SI must make provisions for security of field equipment as well as protection of the software system
from hackers and other threats. Using Firewalls and Intrusion Prevention Systems such attacks and
theft should be controlled and well supported (and implemented) with the security policy.
The virus and worm attacks should be well defended with gateway level Anti-virus system, along
with workstation level Anti-virus mechanism. There should also be an endeavor to make use of the
SSL/VPN technologies to have secured communication between Applications and its end users.
Furthermore, all the system logs should be properly stored & archived for future analysis and
forensics whenever desired. The authority would carry out the security audit of the entire system
upon handover and at regular interval during O&M period. Proposed solution shall adhere to the
model framework of cyber security requirements set for Smart City (K-15016/61/2016-SC-1,
Government of India, and Ministry of Urban Development).
Field equipment installed through this Project would become an important public asset. During the
contract period of the Project the SI shall be required to repair / replace any equipment if stolen /
damaged/faulty. Appropriate insurance cover must be provided to all the equipment’s supplied
under this project.
50
• The systems implemented for project should be highly secure, considering that it is intended
to handle sensitive data relating to the city and residents of the city. The overarching security
considerations are described below.
• The security services used to protect the solution shall include: Identification, Authentication,
Access Control, Administration and Audit and support for industry standard protocols.
• Micro-segmentation and granular security delivered to the individual workload i.e. IT teams
can define policies for each workload based on application and user context, which ensures
immediate responses to threats inside the data centre and enforcement down to the
application
• Reduced network provisioning time from days to seconds and improved operational
efficiency through automation i.e. Virtualizes all networking and security functions to enable
faster deployment and complete lifecycle automation of traditional and new applications
consistently across DC and DR
• Workload mobility independent of physical network topology within and across data centers
• Enhanced security and advanced networking services through an ecosystem of leading third-
party vendors
• Solution provide traffic visibility, end point monitoring for visibility up to layer 7 for network
monitoring and automating application security rules, firewall planning & management,
network virtualization operations & troubleshooting tools.
• The solution shall support advanced user authentication mechanisms including digital
certificates and biometric authentication.
• Security design should provide for a well-designed identity management system, security of
physical and digital assets, data and network security, backup and recovery and disaster
recovery system.
• The solution should provide for maintaining an audit trail of all the transactions and should
also ensure the non-repudiation of audit trail without impacting the overall performance of
the system.
• The overarching requirement is the need to comply with ISO 27001 standards of security.
• The application design and development should comply with Open Web Application Security
Project (OWASP) top 10 principles
• A secure solution should be provided at the hardware infrastructure level, software level,
and access level.
• Authentication, Authorization & Access Control: 3 factors (User ID & Password, Biometric,
and Digital Signature) security mechanisms should be implemented to enable secure login
and authorized access to portal information and services.
51
• Encryption Confidentiality of sensitive information and data of users and portal information
should be ensured.
• Appropriate mechanisms, protocols, and algorithms necessary to protect sensitive and
confirmation data and information both during communication and storage should be
implemented.
• Data security policies and standards to be used as per government of India guideline.
• In order to adequately provide access to secured information, security needs must be
identified and developed at the data level. Database design must consider and incorporate
data integrity requirements.
• Role based access for all the stake holders to be implemented to access and use the system
• Ability to adopt other authentication mechanism such as Electronic Signature Certificates
• Authorization validity to be ensured for the users providing the Data to the system. Data
should be accepted only from the entity authorized
• Audit trails and Audit logging mechanism to be built in the system to ensure that user action
can be established and can investigated if any can be aided (e.g. Logging of IP Address etc.)
• Data alterations etc. through unauthorized channel should be prevented.
• Industry good practice for coding of application so as to ensure sustenance to the Application
Vulnerability Assessment
• Build a complete audit trail of all activities and operations using log reports, so that errors in
system – intentional or otherwise – can be traced and corrected.
• Access controls must be provided to ensure that the system is not tampered or modified by
the system operators.
• The security of the field devices must be ensured with system architecture designed in a way
to secure the field devices in terms of physical damage & unauthorized access.
• The message exchange between various applications in the smart city should be fully
encrypted and authenticated. Any application outside the Data Centre (DC) should talk to the
applications hosted in the data center through predefined APIs only.
• APIs should be published, and the IT systems be running on standard protocols like JSON /
XML or REST etc.
• From a network security perspective all information that flows on the network should be
encrypted to ensure safety and privacy of confidential data. The devices at each endpoint of
the network should be authenticated (using mechanisms based on attributes one of which
could use passwords). The authentication system so used on these endpoint devices should
ensure that only authorized users are sending data over the network, and there is no rogue
data that is sent to the control systems to generate false alarms or sabotage the systems.
52
• All IoT sensors deployed as part of Smart cities system should talk only to the authorized
wireless network, and do not hook on to the rogue networks. The guidelines to secure Wi-Fi
networks as published by Department of Telecom must be followed.
• Wireless layer of the Smart City Network should be segmented for public and utility networks
by using Virtual Private Networks (VPNS), preferably separate virtual networks in the wired
core, so that any traffic from the internet users is not routed into the sensor networks and
vice-versa.
• All traffic from the sensors in the Smart city to the application servers should be encrypted
Secure Socket Layer (SSL) and authenticated prior to sending any information. The data at
rest and in transit must be encrypted
• Authentication of sensors in the Smart city should happen at the time of provisioning the
sensors, and adding them into the system, and should be based on physical characteristics of
the sensors like MAC lD, Device lD etc.
• Sensors deployed in solutions to set up Smart city should be hardened devices with the
ability to be upgraded remotely for firmware through encrypted image files.
• The Sensors or edge device deployed in Smart city should not have any physical interface for
administration. Monitoring of systems and networks should be undertaken remotely.
• All the sensors in the Smart city should connect to a completely separate virtual network.
• As various sensors use multiple protocols to communicate with the underlying network with
varied security capability, the system should allow provisioning necessary authentication and
encryption at the gateway or the nearest data aggregation level if the sensor is not able to do
the same.
• Secured Information and Event Management system monitoring all Smart City networks,
devices and sensors to identify malicious traffic.
• Data should be encrypted at database and application level. Hardware based encryption
which has the capacity of working in layer 3 and It should be doing the encryption key mgt as
well. The proposed solution should be able to encrypt everything at a min 1024 bit.
Activities such as anti-spoofing (no one should be able to masquerade for inappropriate access),
anti-sniffing (no one should be able get data and interpret it), anti-tampering (no one should be able
to put/change data which was not meant to be put/changed) should be taken care for data in
transit, as well as data at rest, from internal and external threats.
f. Sustainable & Scalable Solution
Important technical components of the architecture must support scalability to provide continuous
growth to meet the growing demand of the city. The system should also support vertical and
53
horizontal scalability so that depending on changing requirements from time to time, the system
should scale upwards. There must not be any system-imposed restrictions on the upward scalability
in number of cameras, data center equipment’s or other smart city components. Main technology
components requiring scalability are storage, bandwidth, computing performance (IT Infrastructure)
The architecture should be scalable (cater to increasing load of internal and external users and their
transactions) and capable of delivering high performance till the system is operational. In this
context, it is required that the application and deployment architecture should provide for Scale-Up
and Scale out on the Application and Web Servers, Database Servers and all other solution
components. The data center infrastructure shall be capable of serving at least 10,000 concurrent
users. The expectation is that the system should sustain at least 10 years from GO-Live. There must
not be any system-imposed restrictions on the upward scalability in number of field devices.
g. Manageability
Ease of configuration, ongoing health monitoring, and failure detection are vital to the goals of
scalability, availability, and security and must be able to match the scalability of the system
h. Interoperability
Keeping in view the evolving needs of interoperability, especially the possibility that the solution
shall become the focal point of delivery of services and may also involve cross-functionality with the
e-Government projects of other departments / businesses in future, the solution should be built on
Open Standards.
The SI shall ensure that the application developed is easily integrated with the existing applications.
The code does not build a dependency on any proprietary software, particularly, using proprietary
‘stored procedures’ belonging to a specific database product. The standards should:
a. at least comply with the published eGovernance standards, frameworks, policies and
guidelines available on http://egovstandards.gov.in (updated from time-to-time); and
b. be of leading industry standards
All the personnel working on the Project and having access to the Servers / Data Center should be
on direct payroll of the SI/OEM/Consortium partner. The SI would not be allowed to sub-contract
work, except for following:
• Passive networking & civil work during implementation and O&M period,
54
• Viewing manpower at Command/ viewing centers & Mobile Vans during post-
implementation
• FMS staff for non- IT support during post-implementation
However, even if the work is sub-contracted, the sole responsibility of the work shall lie with the SI.
The SI shall be held responsible for any delay/error/non-compliance/penalties etc. of its sub-
contracted vendor. The details of the sub-contracting agreements (if any) between both the parties
would be required to be submitted to city and approved by the Authority before resource
mobilization.
i. Convergence
The ITMS Infrastructure should be made scalable for future convergence needs. Under the smart
city program JSCL, has envisaged to create a state-of-the-art infrastructure and services for the
residents of Jammu, hence it is imperative that all infrastructure created under the project shall be
leveraged for maximum utilization.
SI is required to ensure that such infrastructure will allow for accommodation of equipment’s being
procured under other smart city projects. Equipment like Junction Boxes and poles deployed under
the ITMS project at the field locations will be utilized to accommodate field equipment’s created
under the other projects of JSCL. The procedure for utilization of the infrastructure will be mutually
agreed between JSCL and SI
j. GIS Integration
SI shall undertake detail assessment for integration of the Smart Governance, Surveillance System
and all other components with the Geographical Information System (GIS). SI is required to carry out
the seamless integration to ensure ease of use of GIS in the Dashboards in Command Control
Centers. If this requires field survey, it needs to be done by SI. If such a data is already available with
city, it shall facilitate to provide the same. SI is to check the availability of such data and its suitability
for the project.SI is required to update GIS maps from time to time.
k. SMS Gateway Integration
SI shall carry out SMS Integration with the Smart City System and develop necessary applications to
send mass SMS to groups/individuals. Any external/third party SMS gateway can be used, but this
needs to be specified in the Technical Bid and approved during Bid evaluation.
55
l. Application Architecture I. The applications designed and developed for the departments concerned must follow best
practice and industry standards. In order to achieve the high level of stability and robustness of
the application, the system development life cycle must be carried out using the industry
standard best practices and adopting the security constraints for access and control rights.
The various modules / application should have a common Exception Manager to handle any
kind of exception arising due to internal/ external factors. The standards should (a) at least
comply with the published eGovernance standards, frameworks, policies and guidelines
available on http://egovstandards.gov.in (updated from time-to-time); and (b) be of leading
industry standards and as per standards mentioned at Annexure.
II. The modules of the application are to be supported by the Session and Transaction Manager
for the completeness of the request and response of the client request. The system should
have a module exclusively to record the activities/ create the log of activities happening within
the system/ application to avoid any kind of irregularities within the system by any User /
Application.
SI shall design and develop the Smart City System as per the Functional and System
requirement specifications finalized.
III. The Modules specified will be developed afresh based on approved requirement.
IV. Apart from this, if some services are already developed/under development phase by the
specific department, such services will be integrated with the Smart City System. These
services will be processed through department specific Application in backend.
V. Application should have a generic workflow engine for citizen centric services. This generic
workflow engine will allow easy creation of workflow for new services. At the minimum, the
workflow engine should have the following features:
• Feature to use the master data for the auto-populating the forms and dropdowns
• Creation of application form, by “drag & drop” feature using meta data standards
a) Defining the workflow for the approval of the form
b) First in First out
c) Defining a citizen charter/ delivery of service in a time bound manner
• Creation of the “output” of the service, i.e. Certificate, Order etc.
• Automatic reports
i. Of compliance to citizen charter on delivery of services
ii. Delay reports
56
VI. The standards should: at least comply with the published eGovernance standards, frameworks,
policies and guidelines available on http://egovstandards.gov.in (updated from time-to-time);
and
VII. The application should have a module for management of digital signature including issuance,
renewal and suspension of digital signatures based on the administrative decisions taken by
the State.
VIII. SI shall ensure using Digital signatures/eAuthentication (Aadhar Based) to authenticate
approvals of service requests etc.
IX. e-Transaction & SLA Monitoring Tools
a) The SI should be able to measure and monitor the performance of the deployed
Infrastructure. More importantly, it should be possible to monitor in REALTIME, the
number of citizens touched through e-Services each day, month and year, through
appropriate tools and MIS reports.
b) The Infrastructure management and Monitoring System shall be used by SI to
monitor the infrastructure (Both IT and Non-IT) hosted at the Data center and DR
site.
c) for monitoring of uptime and performance of IT and non-IT infrastructure deployed,
the SI shall have to provision for monitoring and measurement tools, licenses, etc.
required for this purpose.
X. The Smart City Application should have roadmap to integrate with key initiatives of State
namely Portal Services, Citizen Contact Centre, Certifying Authority etc.
XI. Complete mobile enablement of the Smart City System
3.2 Design Considerations
3.2.1 Identification of all stakeholders
The project requires collaboration between multiple stakeholders for its successful execution. It is
therefore important to understand the various stakeholders envisioned to be part of this project and the
role that they are expected to play. Following are the critical stakeholders whose involvement will drive
the project and enable the establishment of a strong project governance:
57
3.2.2 Jammu Municipal Corporation (JMC) and departments:
The Jammu Municipal Corporation will be responsible for the driving the project along with the SPV.
would also be responsible for driving maximum usage and adoption of the ICT functions across the city
departments. departments are critical for driving adoption and will be the end users of this project. The
direct benefit of the project will be felt at each of the department. The project will be a support to the
functioning of departments given below. The reach and users of these projects will be at offices of
various department.
3.2.3 Smart City SPV
As per the GoI guidelines, a separate Special Purpose Vehicle (SPV) has been created for execution of
projects under the smart city mission for the city of Jammu. This SPV shall carry end to end responsibility
for implementation, operationalization and utilization of the proposed project along with efforts and
assistance of the PMC. PMC will support the SPV for executing the tendering process for the selection of
the implementation partner. Thereafter, during the implementation phase and SPV be responsible for
carrying out the review of detailed design, deployment, acceptance testing and providing support during
the final acceptance tests. During the O&M phase, the SPV will engage the PMC with the responsibility to
review the maintenance and operations and driving the adoption of the projects.
Jammu Smart City Limited
City Municipal Corporation
Police & Traffic Police
Residents/ CitizensInternet Service
providersRegional Transport
Office
Housing & Urban Development Department
Project Management Consultant
System Integrator
58
3.2.4 Implementation Partner
An implementation partner for the project shall be selected by the SPV through an open competitive
bidding process. This may be a single agency or a consortium of multiple agencies that would come
together for project execution on commercial terms. The implementation partner would be the primary
owner for detailed project design and the execution of the project on ground. It will be responsible for
providing the necessary guidelines and support during the acceptance testing. Thereafter, in the O&M
phase of the project, the implementation partner will act as the primary owner for maintenance and
operations. Technical Evaluation Criteria of selecting implementation partner shall be evaluated as per
the point’s weightage of PQ Specified in RFP.
3.3 Characteristics of design
While designing the PAN city ICT projects the key aspects to be considered are:
Real time integration with other systems within the TMMC and inter-operability
KPI monitoring and real time reporting dashboard
Interface with systems of other agencies
Handling cross agency scenarios and SOP’s including police, traffic and utilities
City Management Activities in routine day to day as well as emergency scenarios
Configure single centralized manager to control and manage the virtual infrastructure as well as
for real time monitoring of virtual components. Design should provide automation and
operations layer so as to bring self-service, zero manual touch delivery of virtualized resources
seamlessly
Automation, virtualization and orchestration should be tightly integrated, as to any alerts, info
regarding infrastructure performance, capacity planning etc. can trigger automated
provisioning and de-provisioning tasks including compute, network and security in the
automation and virtualization layer in private cloud deployment.
Extend the infrastructure to MEITY certified cloud service provider (GCC/VPC (AWS/AZURE)) for
use cases like disaster recovery, the management and governance layer can also be extended
to manage public cloud interfaces. The recommended approach is to have same set of
infrastructure virtualization on both sides
3.4 Design Parameters
The PAN city smart solution has been designed taking into consideration the following key functional
parameters:
59
The ICT solutions shall provide effective collaborative monitoring and management of city
operations across various agencies.
Systems should be designed as per the local site conditions of Jammu
Open Standards based interfaces so that additional requirements that might emerge in the
future can be easily accommodated without requiring for a major change in the solution
architecture
Cater to the common data requirements of other applications. For e.g. the TMMC shall
provide for common GIS layer that would be used by all applications needing GIS
functionality
Act as single point of contact for citizen interface by attending to voice calls as well as
attending to their complaints registered through other channels including web, smart mobile
applications.
All the applications should be deployed on servers and required integration with external 3rd
party SAN/NAS storage into the Server cluster for capacity expansion.
ICT solutions and their Standard Operating Procedures (SOPs) that would be followed for
managing and tracking the incidents.
Deployment Architecture with no single point of failure and in line with the industry best
practices. Integration between various components offered in the overall solution needs to
be done.
Provide business continuity services in case the primary site becomes unavailable.
Configure and deployment DR automation solution for one click DR and enable DR drill. DR
should not require manual creation of network and security policies and IP addresses should
be retained if required
Configure micro segmentation and zero trust security in DC, DR.
Provides centralized automated disaster recovery, site migration and non-disruptive testing
capabilities to the customers.
3.5 Network Backbone
With technology being a key driver for implementation of Jammu Smart City initiatives across the Jammu
City, a robust network is one of the key foundational requirements on which future ICT based ‘Smart’
initiatives shall be designed and built. Accordingly, establishing a Jammu wide network backbone
infrastructure that shall act as the backbone for effective implementation of smart Jammu initiatives
across the Jammu City becomes mandatory.
60
The provisioned network backbone infrastructure shall be designed in a manner which shall be capable
of carrying out all the key services that shall be implemented in due course under smart Jammu
initiatives. The Authority wishes to use existing OFC network of existing service providers by entering into
lease agreements with them. The bidder is encouraged to propose alternate solutions.
The expected benefits to be derived from Jammu city network backbone are:
o Connectivity – Network that interconnects citizens, government, business houses and other
communities.
o Smartness – Network would allow better management and control to offer richer and smooth
application usage experiences.
o Secure, private and resilient – Network built considering security standards and best practices
with stability in bandwidth provisioning and resilient
o Efficient – Network that is capable to deliver the envisaged bandwidth and related services
o Scalable – A network that can scale up to cater all the bandwidth requirements for
deployment of future smart Jammu City initiatives
Multiprotocol Label Switching (MPLS) based network or better is expected to be provisioned for the
backbone network wherever required : The network backbone is expected to help the Jammu city to build
a converged network, bringing together different departments’ vertical solutions on a single foundational
network infrastructure. The converged network shall facilitate information exchange between various
resources and applications across different domains. It is proposed to be an end-to-end platform enabling
delivery of varied services for citizens. Key objectives envisaged are to provide:
o IP connectivity that shall enable the citizens to avail varied services under smart Jammu
initiatives
o Wired and wireless, scalable, and highly secure network platform
o Data management framework to help enable data collection, organization, and sharing
o Adoption and usage of distributed computing and storage services, location-based services
and security services
61
4 Traffic Management and Monitoring Centre
The TMMC shall serve as a shared space to host backend systems of various Pan City ICT components
listed in this RFP. It will be a common facility from where various smart components shall be operated,
managed and monitored
The key objectives of establishing the TMMC are as below:
• Integrated Platform for control monitored managing traffic flows on the roads in the city
and various other systems related to traffic management.
• Platform for monitoring operational and performance aspects related to public transport
(future), parking (future), information dissemination, citizen service delivery, etc.
• Aggregation of various data feeds received from sensors/systems and further process
information out of these data feeds to provide interface /dashboards for generating alerts
and notifications in real time.
• Equip city administration to respond quickly and effectively to any incidents/ crisis
situations in city in collaborative and coordinated manner in response to incidents /
emergencies / crisis situations.
• TMMC shall house various smart components feed and information, which shall use the
data and intelligence gathered from operations of other to enable the data and analytics
platform for batter decision management system.
4.1 TMMC Components
TMMC should have system components that would be driven by its design and operational needs. TMMC
will house all the necessary equipment for the monitoring, operation, control and archiving of data for
the purpose of traffic and surveillance system infrastructure. TMMC would require Data Center (DC)
facility to host backend system comprising hardware, software, storage and associated facilities. SI shall
set up a dedicated DC for TMMC. The typical major equipment and systems in TMMC will include, but
not limited to, the equipment and systems listed in following table
62
Table: TMMC Components: Backend Centre
BACKEND CENTRE COMPONENTS
Centre Application Software
• Traffic Management Software
• Road Network Surveillance Software
• Emergency and Incident Management Application- Help desk
• Interfaces with Transit, Traffic Enforcement Systems and other Specialized Applications
Centre Hardware
• Computers/ Operators consoles
• Hosting, Compute and Management IT infrastructure (application, communication, information dissemination, signals, CCTV, enforcement system etc.)
• Video Wall
• Storage Area Network (SAN)
• Network and Communication Routers, Switches
• Cyber Security devices • Printers
Backend Standard Software
• Operating system
• Cyber Security Applications
• Database
• BI/Data analytics Tools
Utilities
• Fire suppression
• Air conditioning
• Access control
• Power and its backup
63
4.2 Functional Architecture
The functional (logical) architecture defines the more detailed layers of the architecture in terms of
setting out the physical sub-systems. The logical architecture aims to define and illustrate the
configuration of services. The logical architecture starts with the functions specifications and takes the
form of a series of data flow diagrams that depict the logical processes, the data flows and the definitions
of the data requirements, or Data Dictionaries. It is a graphical tool to organize complex entities and
relationships. It focuses on the functional processes and the information (data) flows of sub-systems and
the system as a whole. A logical architecture helps to identify the system function and guides the
development of the overall requirements of the system and/or upgrades. A logical architecture is
independent of institutional framework and technology, but is supported by the institutional
arrangements and goals.
Following figure representative TMMC Functional Architecture envisaged to be implemented in phases
in Jammu. It depicts those services that are anticipated to be integrated with TMMC Jammu. However,
in current scope Transit Management, CCTV Surveillance and Enforcement systems are covered.
4.2.1 Architecture Flow
Information that is exchanged between sub-systems and terminus in the physical architecture are the
architecture flows. Architecture flows and their communication requirements define the interfaces
64
which form the basis for much of the standards that need to be defined. Data flows described earlier in
the Logical Architecture are aggregated together to form architecture flows
65
4.3 TMMC Applications
Following Table provides an overview of the TMMC related applications in the area of Traffic
Enforcement, Traffic Monitoring and Integration. These have been detailed in subsequent sub-sections
Area TMMC Applications
Traffic Management
• Red light and over speed violations with Automatic Number Plate Recognition
• Entry restriction violations using ANPR at the Entry and Exit of Jammu
• Handheld Device Application
• Integration with Existing Adaptive Traffic Control System
Traffic Monitoring • CCTV surveillance of Traffic Junctions
• Video Analytics (Minimum 900 Channels)
• Integration with Bus and IPT operations (In future)
Incident Management • Analysis and Action from TMMC for Incident Management
Information Dissemination • Advertisement Boards, Web Portal of JSCL
4.3.1 Traffic Management
4.3.1.1 Red Light Violation Detection System
Red Light Violation Detection System (RLVD): The RLVD would be hosted in the Data Center
(as detailed in the later part of this document). All of the red light violations shall be listed
with image/video proofs for the validation of internal team and then processed for challan
issuance. However, information of violations should also be used by the TMMC
system/operators for analyses (e.g. correlation with accidents, vehicle category wise
violations etc.) and planning corrective actions, if any.
The central application shall receive the violation details from the field devices and then shall
be processed same as RLVD.
4.3.1.2 Entry Restriction Violation using Video Analytics and ANPR
Vehicle restricted on class and number can be detected by Video analytics field devices and
an alarm shall be triggered in TMMC dashboard for a violation. This alarm can be shared with
respective agencies for further action.
66
4.3.1.3 Handheld Device application
These systems are used by Traffic Police for traffic and transport related enforcement. Data
from the e-Challan system should interface with TMMC and can be used for analysis
4.3.1.4 Operational and Data Integration with Existing Adaptive Traffic Control System (ATCS)
As part of signal timing and operations activity undertaken by the TMMC, inputs from a
variety of sources are received and processed at the TMMC. The activities that the TMMC
performs as part of this are listed below:
• Controlling signals from TMMC that are connected to it through communication links
• Signal control plans creation based on surveillance and other inputs and its implementation. The plan could be based on fixed time, adaptive or local operations.
• Coordinate with other signalized junctions while creating, modifying and implementing the signal control plans
• Configure signal controllers to operate in various modes such as adaptive, fixed time based etc.
• Collect signal LOS (level of service) or similar congestion data
• Collect and monitor status update from signal controller such as fault data
• Clock synchronization of signal controllers
4.3.2 Traffic Monitoring
4.3.2.1 CCTV Surveillance of Traffic Junctions
CCTV Surveillance would be carried out through surveillance cameras (Fixed Box and PTZ)
that monitor the traffic conditions on the road network, capture visuals and traffic
characteristics from the field and transmit data to the TMMC for review and analysis.
TMMC transmits command and configuration details to these equipment and they send the
captured data, operational and functional status of the equipment to the TMMC. Signal
timing can be adjusted based on the data feed for the surveillance equipment.
67
4.3.2.2 Video Analytics
The need to protect physical security of important facilities and infrastructure is more critical
than ever before. Conventional surveillance solutions depend on round-the-clock monitoring
of the camera feeds by trained professionals. This is neither scalable nor fool proof, given the
scarcity of trained manpower. For Governments to truly benefit with the exponential
investment in CCTV Cameras for security and surveillance, the only option is to harness the
emerging innovations in technology. While specialized technology solutions like Face
Recognition are used in law enforcement and anti-terrorism domains, they are very unique,
purpose built and quite expensive to the general security needs of large businesses or for
effective monitoring of public facilities and infrastructure. Advances in camera capabilities
coupled with Image Recognition technologies make it feasible to leverage technology to
detect intrusions in designated locations. This significantly lowers the dependence on skilled
manpower, the need for human monitoring 24x7 and enhances overall security efficiency
Platform combines deep image recognition capabilities with ultra-quick image processing to
power its Smart Surveillance solutions portfolio. Security features available to businesses
include:
68
• Face Detection
• Crowd detection
• Intrusion detection
• Trip wire detection
• Missing object detection
• Object counting
• Tampering detection
• Helmet detection
• Triple riding detection
• Loitering detection
• Wrong way detection
• Left baggage /abandon baggage
SI to provide minimum 900 channels for Video analytics, provisioning for minimum 4
analytics per camera.
4.3.2.3 Integration with Bus and Intermediate Public Transport Operations (In Future)
The bus operations are managed by the bus operators manually in Jammu. Bus operations
utilize road network and infrastructure and they are, therefore, affected by the signal plans
at signalized junctions, incidents/events affecting traffic, road closures/diversions,
construction/maintenance work on the roads, congestion levels on the road, current and
predicted traffic. They may need signal priority on certain predetermined corridors, to ensure
schedule adherence or signal pre-emption while supporting emergencies
IPT operations cover modes such as auto rickshaws, taxis, radio taxis and other similar modes.
In case of unorganized IPT operations, the regulatory authority may coordinate for
information exchange with the TMMC
4.3.3 Incident Management
Emergency response and its management is the responsibility of designated agencies and
authorities through the emergency center. Incident response requires several city agencies
to come together, participate and discharge their respective roles. The need for information
sharing and dissemination becomes very critical in such situations. TMMC typically have a
supporting role in emergency management as listed below:
69
Issues Analysis Action
Fore
seen
Eve
nts
Climate/
Weather/
Vagaries
• Information regarding this would be provided by meteorological department to TMMC
• TMMC will analyse the potential impact of the predicted weather condition on the traffic.
• TMMC would disseminate this information to the public through various channels
• TMMC would take necessary steps regarding traffic diversion and issue advisory based on its assessment of the impact on traffic.
Ambulance
Detection (In
Future)
• The signalling system would be able to detect when the ambulance approaches the junction.
• Signal priority would be given to the ambulance based on the policy followed by TMMC
Festivals/Rallies/
Events
• Information regarding this would be provided by respective department concerned to the TMMC
• TMMC will analyse the potential impact of the planned event on the traffic.
• TMMC with the help of Traffic Police would make the traffic circulation plans for the events
• TMMC would disseminate this information to the public through various channels
Un
fore
seen
Eve
nts
1u
Un
fore
see
n
Eve
nts
Breakdown of
street furniture
such as signal
not working or
any other issues
• TMMC would detect the breakdown
• TMMC would also analyse the street furniture through its systems like cameras and other mechanism
• TMMC would take necessary steps regarding traffic diversion and issue advisory based on its assessment of the impact on traffic.
Accident • TMMC would analyse the traffic data and detect the accidents based on the traffic pattern.
• Concerned authorities may also provide accident related information to TMICC.
• TMMC would disseminate this information to the public through various channels
• TMMC would help in diverting the traffic
• TMMC would inform the agencies for action on road
• Coordination for emergency vehicle dispatch.
• Support to authorities concerned during evacuation.
Vehicle
breakdown
on roads
• TMMC would analyse the traffic data and detect the vehicle breakdown based on the traffic pattern.
• TMMC would disseminate this information to the public through various channels
• TMMC would help in diverting the traffic
• TMMC would inform the agencies for action on road
• Coordination for emergency / towing vehicle dispatch.
• Concerned authorities may also provide vehicle breakdown related information to TMMC
70
• Support to authorities concerned during traffic restoration.
Landslide • TMMC would analyse the situation with the system
• cameras.
• TMMC would disseminate this information to the public through various channels
• Concerned authorities may also provide information to TMMC
• TMMC would divert the traffic.
• TMMC would inform the agencies for required action on the road.
Dis
aste
r
Disasters such as
fire/ flood/
earthquakes
• Management of disasters and other calamities are dealt with by the disaster management authorities.
• TMMC would analyse the situation in consultation with authorities in case of disaster and would recommend the necessary steps to be taken by authorities to regulate traffic flows.
• TMMC would disseminate this information to the public through various channels
• Disaster Management authorities would communicate with TMMC through interface about the disaster.
• Disaster Management authorities would guide the TMMC for the action to be taken.
• TMMC would also make traffic plans in coordination with the Traffic Police.
4.3.4 Information Dissemination
The objective of information dissemination is to provide the citizen and tourists with comprehensive,
relevant, reliable, accurate and updated traffic information which is useful for them to plan their travel.
The idea is not to flood them with a barrage of information but to provide only that information which could
affect travel choices. Such information includes the factors that affect road network capacity, lead to
congestion, affect travel times, require road closure or diversions. It is, therefore, necessary that information
about such factors is captured promptly and disseminated through suitable channels so that travelers can
accordingly make/change their travel plans.
The information could be disseminated through various channels: web, mobile apps, social network,
Advertisement Boards, radio channels and/or TV channels.
Advertisement Boards provide real time, contextual, useful traffic, congestion, re-routing related
information to motorists in an automated fashion without the need for control centre monitoring or human
intervention. The data captured by TMMC may also be shared in open data format with public. This would
enable third party software developers and/or Value Added Service (VAS) providers to develop mobile
applications and other tools to disseminate useful
71
5 Minimum Technical Specifications
The Planning, Design and Implementation Services for Data Centre transformation combine
the people, processes and technology, with the program and project management necessary
to transform a client’s existing data centres into ones that provide business agility at a lower
cost, a wide range of services for discovery, analysis, optimization, automation, virtualization
and migration of data centres that can complement client efforts and fill gaps in client skills
and capacities.
Various aspects of the data centers include:
• Facilities: layout, power/cooling, physical security, manpower
• System infrastructure: servers, networking (with LAN), storage, and security;
• Applications, infrastructure mapping & dependencies;
• Design Standard: Tier-III or above (ISO 27000, ISO 20000 certification to be done)
• The availability of data must be guaranteeing to 99.982% availability.
• UPS: UPS system with 1+1 redundancy
• Generator: Gen-set with 1+1 redundancy
• Power Provision: Dual power feed, PDU sources to each rack, Power supply to a rack as
per requirement
Key Functional Requirements
1. Provide Unified visibility, operations & portability across clouds • Create a common operating environment and foundational elements with
abstracted compute, network & security across DC, DR (MeITY
empanelled CSP) to have unified visibility, operations and portability
across clouds.
2. Provide Unified View of health, performance & security across multiple clouds • Building Unified view of the health, performance and security of
workloads across DC, DR (MeITY empanelled CSP)
• Centralized visibility of all the cloud environments
• Deliver highly efficient and automated IT operations across multi cloud
environment.
3. Delivery of IT services across multiple clouds • Delivery of IT services through automation and pre-defined policies with
Self-service capability and Standardized infrastructure offerings
• Defining explicit automation and policy
72
4. Consistent Security and Networking across multiple clouds • The network & security policies in the virtualization layer must be tied to
the application to ensure that there is no manual intervention in
redefining Network & Security policies, in case of migration across DC, DR
(MEITY empanelled CSP). Also, when the application is deleted, all the
security policies related to the application should also be removed.
5. Fully Automated DR and Business Continuity • The DR should be fully automated including automation of networking
and security policies for the workloads. The solution should offer Layer-2
extension which allows virtual machines to retain network connectivity
across geographical boundaries. There should be minimal manual
intervention and the RTO should be calculated considering the
networking and security policies.
6. End to End Network Visibility across clouds • The Solution should provide real time operational visibility for network
and security across clouds. The solution should be able to give
comprehensive Network visibility including East west, North South traffic,
VM to VM traffic etc.
7. Security across Clouds/ Datacentres • The solution should offer comprehensive visibility and analytics that tie
together compute, network, storage and security and provide Physical to
Virtual Correlation and troubleshooting.
• The Network & Security solution should offer virtualized workload at the
virtual NIC level to be protected with a full stateful firewall engine at a
very granular level based on constructs such as MAC, IP, ports, tags, active
directory groups, Security Groups, etc.
• The solution should offer comprehensive flow assessment and analytics
and security groups and firewall rules suggestion for the purpose of
implementing a zero-trust security within the datacentre.
Storage:
Total Surveillance Storage would be 1PB at least with 40 TB for OS and application
as Raw Storage
DR:
73
The DR for the data centre shall be on cloud on empanelled service providers by
MeITY. The cloud provider should be MEITY empanelled as well as STQC certified
Govt community cloud.
DR design should be 25% of DC (compute and RAM), 10% of Video storage (Only
critical and Flagged data)
Various ICT equipment to be provisioned and maintained by SI at the Data Centre is
given below. The backup storage should be active-active. All equipment in DC
should be in HA. DR should be on cloud as a service and 99.5 % uptime.
• The proposed Cloud Service Provider (CSP) must be an empanelled cloud
service provider by MEITY (Ministry of Electronics and Information
Technology) for Public cloud, Virtual Private Cloud and Community
Government Cloud.
• The Cloud Data Centre Facility for DR must be within India and must be
Tier III or above. The DR site should be in a different seismic zone
• DC/DR would operate in an active passive state with 25% data should be
replicated from primary to DR site.
• DR automation solution for automated failover, failback and recovery of
application VMs in proper sequence to other data center with single click
from the virtualization console.
• Solution to perform non-disruptive DR drill/testing of recovery plan for
full and selected applications every six months without impacting
production applications running in primary environment.
• CSP should use technologies which are in the leader’s quadrant of
Gartner’s Magic Quadrant or within top 3 vendors in the latest IDC report
• Hypervisor, cloud-orchestration and self-service portal should be either
from single OEM or should have Out-of-the box integration to avoid the
integration challenges.
• Shall have the capability to provide adequate bandwidth between Primary
Data Centre and Disaster Recovery Centre for data replication purpose
and should provide extension of layer 2 network across data centre for
smooth failover of movement of VMs across DCs and DR.
• DR should be on dedicated hosts within the cloud, and hypervisor should
be same across DC and DR for consistence failover and failback of
operations.
74
• Network and security should be integrated with cloud so automated and
on-demand creation of network, Security and load balancing policies is
done as soon as VM is created
• Security policies should follow the Virtual Machines as it moves within the
cloud within and across data centres.
5.1 DC Scope of Work
The bidder shall supply Hardware, Software, field equipment as per Schedule of
Requirements and in accordance with minimum functional & technical
specifications as provided. Higher version /additional specifications shall be
accepted. However, deviation from minimum specifications if any, shall be clearly
indicated along with the explanation in the technical deviation section.
• All the supplied equipment, licenses and ATS certificates should be in the
name of the JSCL for TMMC but could be in the name of CSP for DR
• The bidder shall be responsible for providing all equipment, software and
services, specified or otherwise, which are required to fulfil the intent of
ensuring operability, maintainability and reliability of complete solution
covered under the functional requirements and technical specifications
within the quoted/contract price
• For management overheads (including CMP, Virtualization Manager, SDS,
Backup, Antivirus, etc.) the bidder shall consider extra servers over and
above the requirement specified for application servers
• Bidders shall have back to back tie-up with OEMs of supplied product so
as to provide support from the respective OEMs for deployment
architecture, installation, configuration, performance tuning, security,
acceptance testing and commissioning of the supplied products like
Surveillance equipment’s, ITMS, Network Equipment’s, Virtualization,
Storage, Servers etc implementation of functional requirements and carry
out required integration of various components offered in overall solution
• The bidder along with the OEM/s will work out and finalize the
Deployment Architecture with no single point of failure and in line with
the industry best practices. Integration between various components
offered in the overall solution needs to be done.
75
• The bidder along with OEM/s shall deploy, configure, fine-tune & optimize
the supplied infrastructure including hardware, software, network &
security components, as per industry best practices.
• Bidder should deploy Servers with SDS infrastructure and configure
storage policies to automate provisioning and balancing of storage
resources to ensure that each application gets the specified storage
resources and services.
• Bidder solution should be built using software defined infrastructure
components which should be independent of underlying hardware
components.
• Bidder solution should provide automation and orchestration solution for
automated delivery of IaaS, PaaS, XaaS/SaaS services for JSCL applications
so that when VM is created it should automatically get the required
virtualized compute, storage, switching, routing, firewall, load balancing
services without any manual intervention. All compute, network, storage,
security, load balancing policies must follow the life cycle of VM and
movement within and across DC.
• Bidder solution must provide cloud operations layer integration with
automation layer which provides proactive monitoring, alerts,
management, resources availability (like CPU, memory, storage, etc.),
capacity planning, performance management etc.
• The proposed backup solution should provide policy-based backup
scheduling for the solution offered to JSCL.
• Bidder solution should provide pre-defined workflows with policy-based
governance on wide array of attributes that allows administrator to
personalized services based on end user requirement.
• Bidder solution should monitor resource utilization of running VMs and
should reclaim resources from idle VMs and allocate to other VMs in
automated fashion.
• Bidder solution should be deployed in High Availability mode and there
should be no single point of failure.
• The self-service portal shall provide feature to request of services which
becomes available after due approval process.
• Bidder solution shall also automate delivery of virtual networking &
virtual security services such as switching, routing, load balancing and
76
micro-segmentation using state-full firewall, defining of policies etc. thus
enabling end to end provisioning of infrastructure. The solution should
support automatic on-demand network creation and should be able to
define routed, NAT or Private Network profiles based on application
topology.
• Bidder solution should be able to create a VM with different pre-defined
sizes, storage with configurable capacity & performance parameters and
also a Multi-tier infrastructure as part of a standard template.
• Bidder solution should be able to design & build ready / custom workflow
to create VM from custom template as a service to provision a VM with
custom machine name prefixed with initial four letters of project group.
• The resources compute, storage, network and security should be pooled
to serve multiple users using a multi-tenant model, with different physical
and virtual resources dynamically assigned and reassigned according to
user demand.
• Bidder solution should be able to host multiple tenant applications on
same physical infrastructure resources such as compute, storage,
networking, security, and backup with complete isolation among tenant
applications
• Bidder solution shall allow administrators to manage and reserve (allocate
a share of the memory, CPU and storage) resources for a project group to
use and also offer any cost control measures such as quotas (limits on
what a user can provision).
• Bidder solution should enable CPU and memory over commit which helps
in resource optimization.
• Capabilities can be elastically provisioned and released, automatically, to
scale rapidly outward and inward commensurate with demand.
• Bidder Solution should support both horizontal & vertical scalability of
infrastructure as per user demand without downtime.
• Cloud systems automatically control and optimize resource used by
leveraging a metering capability at some level of abstraction appropriate
to the type of service (e.g., storage, processing, bandwidth, and active
user accounts). Resource usage can be monitored, controlled, and
reported, providing transparency for both the provider and consumer of
the utilized service.
77
• Bidder Solution should provide metering of consumed resources for each
user/tenant. User should get detailed information of resources used by
them.
• Bidder solution should provide agile Service Costing and Modeling by
using a deterministic engine and powerful modeler to allocate or translate
IT costs (physical, virtual, vendor, overhead, facilities, software, support,
cloud, etc.) to each project group.
• Dedicated compute, memory and storage will be provisioned for
management layer. This is over and above the requirement mentioned for
application servers and is to be provisioned separately as per the solution
requirement.
The management servers (same configuration as application servers)
should be part of the same cluster.
• Bidder solution should be able to provide ready/custom workflow
solution to create a user for project group as a service using a LDAP and
sets password for the user. Password length and mix of character should
be provisioned according to organization’s standard password policy.
• The solution should be able to provide ready/custom workflow solution to
destroy a project group from an LDAP instance.
• The solution should be able to provide solution for business group user
list as a service with ready/custom workflow which will help support user
to list available users and associated VMs of particular business group.
• The solution should be able to Send Email to Cloud Admin Support as self-
service for cloud admin assistance with ready / custom workflow.
• Bidder shall provision the necessary Structured LAN cabling components
for physical network connectivity of the new infrastructure as well as
integration of Cloud layer. The bidder shall prepare a detailed plan to
perform these activities.
• Bidder shall implement and configure Directory Services as part of Overall
solution so that all authentication, authorization of cloud Infrastructure is
done by Directory Services
• Bidder should Integrate backup solution with CMP to provide self- service
configuration of data backup & restore facility.
78
• Respective OEMs of Switches, Firewalls and Backup shall also provide
technical support for integration with Cloud Management Platform (CMP)
being procured in this Tender
• Bidder should implement replication and DR automation solution
Scope of Work for DR (Disaster Recovery as a service)
• SI is required to provision for a Disaster Recovery (DR) as a service on
cloud with 25% capacity of DC as standard for JSCL Solution. The DR site
should not be in the same seismic zone
• The SI shall establish dedicated connectivity between the DC and DR Site
for replication & failover and they should offer Layer-2 VPN to allow
extending the datacentre by allowing virtual machines to retain network
connectivity across DC and DR (CSP Cloud).
• The SI shall submit the detailed solution document for the DR Site
solution
• SI shall also be responsible for providing Cloud service for storing all
applications at DR [minimum 25% production capacity, RTO – 60 mins,
RPO – 240 mins] which will be implemented under JSCL project for the
project duration. All hardware and software on cloud should meet the
specification in RFP
• Cloud services should be accessible via internet.
Scope of Work – Field Equipment
• Bidder should configure separate virtual networks for different
functionality (Surveillance feed, RLVD, AD Panels etc)
• Required QOS to be configured for proper optimization of links
• The Bidder would be responsible to design the network solution with
adequate capacity and redundancy to meet the Service level
requirements
• Bidder to ensure that Public Address system must be used at
intersections, public places, marketplaces or those critical locations to
make important announcements for the public.
• PA System shall be able to broadcast messages across all PA systems or
specific announcement could be made to a particular location supporting
single zone / multi zone operations.
• The PA system shall also deliver pre-recorded messages to the
loudspeakers attached to them from CD/DVD Players & Pen drives for
public announcements. All the PA Systems must be IP Based and Cloud
based control from TMMC.
• Bidder to ensure that emergency box shall will enable citizens to establish
a two way audio (microphone and speaker) & camera communication link
to TMMC
79
• Emergency/ Panic buttons to be strategically located, suitably sized and
identified/clearly labelled for “Emergency”.
• The proposed video surveillance system will involve setting up of IP based
outdoor security cameras across various locations in the Jammu City.
• The video surveillance data from various cameras deployed will be stored
and monitored at TMMC and Viewing centers.
• The Surveillance system will also have video analytics with edge level
analytics system, etc.
• The Surveillance system should have centralized Storage up to 30 days
with High availability mode. The Surveillance system must have an edge
level storage inside the camera which can accommodate up to 5 days
24/7 continuous recording. In case of network loss event the cameras
should store the video at edge level and once connection resume the
video should synchronize with central storage at DC. The video footage
should be available 100%.
• The Surveillance system shall be configured with 5MP@25FPS for real-
time video footage recording, video compression shall be configured with
H.265 to optimise bandwidth and storage.
• All the Surveillance system must record at high resolution as specified in
camera specifications including RLVD and ANPR cameras can be
configured as per the solution required to get high accuracy of violation
detection.
• Bidder to ensure that the entire outdoor IP66 Junction box must have
proper earthing done as per industry standards to ensure the safety of
field equipment’s from surge and electrical attacks.
• Bidder should ensure that all field equipment’s must be protected from
disasters like lightning and high surge, required protectors and arrests
must be installed on each Pole where Field equipment is installed
80
5.2 DC Components
5.2.1 Unified Command & Control Center for TMMC
S.No Specifications Compliance (Y/N)
Offered Specification with Document Proof
1 Solution should have the capability to integrate with GIS
2 Solution shall integrate with GIS and map information and be able to dynamically update information on the GIS maps to show status of resources.
3 Solution should allow defining key performance indicators and visualize the indicators on a configurable dashboard infrastructure
4 Solution should allow configuration and monitoring of service levels for key performance indicators and triggering of actions towards the incident management system when those service levels are breached.
5 Solution should provide current business status (snapshot) of City’s facilities, departments and a holistic perspective of incidents and situations. Including incident handling time, number of false alerts, number of active and closed incident.
6 Solution should provide operators and managers with a management dashboard that provides a real-time status and is automatically updated when certain actions, incidents and resources have been assigned, pending, acknowledged, dispatched, implemented, and completed. The above attributes shall be colour coded.
7 Solution shall provide the “day to day operation”, “Common Operating Picture” and situational awareness to the Centre and participating agencies during these modes of operation
8 Shall provide complete view of sensors, facilities, e-governance/ERP, video streams and alarms in an easy-to-use and intuitive GIS-enabled graphical interface with a powerful workflow and business logic engine
9 Shall provide a uniform, coherent, user-friendly and standardized interface
10 Shall provide possibility to connect to workstations and visualization layer shall be accessible.
11 Dashboard content and layout shall be configurable, and information displayed on these dashboards shall be filtered by the role of the person viewing dashboard
12 Solution should allow creation of hierarchy of incidents and be able to present the same in the form of a tree structure for analysis purposes
13 Shall be possible to combine the different views onto a single screen or a multi-monitor workstation
14 Solution should maintain a comprehensive and easy to understand audit trail of read and write actions performed on the system
15 Solution should provide ability to extract data in desired formats for publishing and interfacing purposes
81
16 Solution should provide ability to attach documents and other artefacts to incidents and other entities
17 Platform shall also be able to integrate, connect, and correlate information from IoT Platform and other IT & non-IT systems, providing rule-based information drawn from various sub-systems for an alert. Platform shall have the ability to add / remove sensors including new vendor types as per future business requirements. It should support SDK/API based integration with the Smart system elements.
18 All system messages (notifications, alerts and alarms) should always be visible from the Notifications view, which provides controls that operator can use to sort and filter the messages that it displays.
19 Systems should deliver message to a set of subscribers. The Notification service should support min two types of notification methods – Email notification and Short Messaging Service (SMS) notification.
20 Platform should allow different roles to be created and assign those roles to different access control policies. Platform should allow single or multiple users to view and manage alarms in defined areas/Locations. User can be part of Single or multiple Areas/Locations.
21 Reports - Platform should have capability to provide access to real time data and historical data from various connected devices for reporting and analytics. System should have ability to generate reports and have provision to add reports in favorites list.
a. Incident Reports
b. Detailed incident reports shall include an incident summary, all the tasks associated with the incident, sensor related activities, relevant snapshots, and maps.
c. Periodic Reports
d. Maintenance Reports
e. Statistical Reports
f. Ability to display report on monitor and print report.
g. Ability to capture Operators response in Text
h. Ability to select information to be included in report at time of report generation.
i. Details of alarm including severity, time / date, description, and location.
j. Capture the operator response by text
k. Allow operator to transfer the incident report to Mobile Device/another operator’s Console
Standard Operating Procedure
22 SOP is a standard operating procedure which provides the step-by- step instruction in the shape of drop-down menu to Command and Control Centre operator on how to handle a particular incident in an organized manner.
82
23 Software shall provide SOP’s in text, pdf, image, word formats.
24 SOP tasks should serve as an instructional resource that allows operator to act without asking for guidance.
25 There shall be the provision to define various SOPs in Command and Control System such as alert category specific SOPs, Location Specific SOPs
26 It shall have facility to define more than one SOP for the selected alert category or location
27 There shall be a provision to define multiple tasks under single SOP
28 The system shall select & present the appropriate SOP automatically based on predefined policies
29 Actions taken as part of SOP should be logged in audit trail with date time stamp and operator comments
30 SOP shall contain the lists of tasks to be performed by operator categorized under following headings
a. Task: Task to be performed by the operator in the sequential order.
b. Description: Task description.
c. Comments: Space for operator to enter the comments.
d. Action: Actions (like email, sms escalation) to be initiated by operator.
e. Done: Indication by operator that the task is completed.
f. User: User name of the operator for audit trail.
g. Date & Time: date time of the action.
Field Responder Mobile
31 Provide Integrated Mobile Application for capturing real-time information from the field response team using Mobile- Standard Operating Procedure. Overall Integrated Operations Platform should account for below solution components, City Tenant activation license with one lakh device connection
a. Operator Client License min 25 with one city activation license
b. Field Responder should be able to acknowledge the incident and provide real time updates from the incident site.
c. Field Responder should be able to view the live stream and image of the event
d. Field Responder should be able to send ATR or action taken for the event to the command and Control application
83
5.2.2 Firewall with Anti-APT solution.
5.2.2.1 Next Generation Firewall:
S.No Firewall Specifications Compliance (Y/N)
Offered Specification with Document Proof
1
The Virtual Firewall shall be entirely Software based for private/Public cloud environment and shall support cloud virtualization platforms like VMware ESXi, Microsoft Hyper-V, KVM, Amazon AWS, Microsoft Azure etc and should have 16 vCPU and 24 GB license from day-1.
2
Firewall shall have feature of application visibility and application control. And should have inbuilt SDWAN feature.
3
Firewall shall perform 'Statefull' and 'Deep' inspection of traffic from layer-2 to layer-7, in both incoming and outgoing direction.
4
Intrusion Prevention System: IPS capability shall minimally attain NSS Certification, ICSA labs certification. Should able to inspect SSL based traffic. Should have at least 7,000 Signature.
5
Web Content Filtering: The proposed system should have integrated Web Content Filtering solution without external solution, devices or hardware modules. Should be able to enable or disable Web Filtering per firewall policy or based on firewall authenticated user groups for both HTTP and HTTPS traffic. System shall be able to queries a real time database of over 110 million + rated websites categorized into 70+ unique content categories. Antivirus capability shall be ICSA labs certified.
6
Data Leakage Prevention: The proposed system shall allow administrator to prevent sensitive data from leaving the network. Administrator shall be able to define sensitive data patterns, and data matching these patterns that will be blocked and/or logged when passing through the unit.
7 Firewall shall support at least 100 VLANs.
8
Firewall shall provide all necessary features for IPV4, IPV6 and dual stack (IPV4 & IPV6) operations from day one. The performance of the firewall shall not degrade for IPV4 and IPV6 individually as well as for dual stack operations (IPV4 & IPV6).
9 Firewall shall support operating in routed & transparent mode.
10 In transparent mode firewall shall support arp-inspection to prevent spoofing at Layer-2.
11 It shall provide mobility without need of any additional licenses and shall use existing license only.
12 The solution shall allow to orchestrate security policy using self- service rule provisioning.
84
13 Firewall shall support static NAT, pat, dynamic NAT, pat & destination based nat.
14 Firewall shall support static routing, RIP, OSPF and BGP.
15
The Device shall provide static as well as dynamic policy-based Network Address Translation (NAT) and Port Address Translation (PAT) functionality.
16 The number of access policies / rule set configurable on Device shall be more than 10000.
17
The Device shall perform packet filtering based on following parameters:
a. Source Address b. Destination Address c. Protocol Type d. Port number e. User f. FQDN based policy
18
The proposed solution must support Policy Based forwarding based on:
- Zone - Source or Destination Address - Source or destination port - AD/LDAP user or User Group - Services or ports
19
The Device shall provide the following features/functions: a. Device shall support NTP (Network Time
Protocol) for date & time synchronization from NTP Server
b. DHCP Client/Server
20 The Device shall provide bandwidth management & rate limiting features etc.
21
The Device shall provide authentication through following: a. LDAP b. Active Directory c. Radius/ TACACS+
22 The Device shall provide authorization and accounting through RADIUS / TACACS+ .
23 The Device shall provide packet filtering based on Time Schedules (one time / recurring).
24 The proposed solution must provide different actions in the policy such as Permit & Deny/Drop.
25
Solution must support SNMP counters for logical interfaces e.g. L2/L3 sub interfaces
26
The proposed solution must provide the ability to lock configuration while modifying it, avoiding administrator collision when there are multiple people configuring the appliance
27 Supports Hub and Spoke architecture
28 The Firewall firmware/operating system shall confirm the FIPS- 140-level-II security standard.
85
29
Should have in house development and subscriptions for all UTM Modules including IPS, App Control, Antivirus, Web content filtering.
30
The Firewall Operating System shall be tested and certified for EAL 4 / NDPP / STQC or equivalent under Common Criteria Program for security related functions or under Indian Common Criteria Certification Scheme by regulations of Govt. of India.
5.2.2.2 Anti-APT
Sr No. Anti-APT Specs Compliance (Y/N)
Offered Specification with Document Proof
1 The APT appliance should be a purpose built on premise appliance/Virtual appliance based solution with integrated support for sandboxing.
2 The solution should provide protection for all incoming and outgoing web and email traffic from /to Internet.
3 Ability to do breach detection system methodology 2.0 and should have block rate of at least 95%
4 Ability to handle min 1 Gbps incoming /outgoing traffic (throughput)
5 Ability to support at least 8 virtual machines running simultaneously
6 Min 6 ports should be provided in APT appliances for achieving functionalities mentioned
7 The solution must be able to detect and report malware by using multiple images OS; No requirement of additional licenses purchase for sandboxing solution
8
Ability to support scanning links inside emails/documents for zero days and ability to remove all the active content, harmful links in email message/documents and macros sending only a clean document to the end user
9
Ability to inspect the web sessions (HTTP and HTTPS both) to detect and notify the malicious web activity including malicious file downloads through the internet.
5.2.3 Core and Internet Router
The proposal should adhere to the following minimum eligibility criteria of Storage OEM:
• OEM of Storage have its own service centre in India and should have a toll free number
• OEM or Manufacturer should be ISO 9001, ISO 14001 and ISO 27001 certified.
• OEM or Manufacturer of the offered goods/ equipment’s should be a company registered under the companies Act since last 5 years in India. Valid company registration certificate should be submitted
86
S.No Parameters Minimum Specifications Compliance (Y/N)
Offered Specification with Document Proof
1 General The Core Router should be chassis based, Should have redundant processor, redundant controller card and redundant power supply
2 The back‐plane capacity of Router
should be minimum 160 Gbps & forwarding performance of 120 Mpps packets per sec of 64 bytes packet. The performance is considered with IPv4 & IPv6.
3 Interface All the Interfaces should be provided in line cards and no interface should be on CPU card. All interface should have wire speed performance.
4 Interface Requirement: 8 x 1Gig base copper, 8 X 1 Gig Base SFP interface and 4 X 10Gig interface (The optics should be populated from day one)
5 Chassis should have at least 3 free main slots (not daughter slots) to scale in future to support
6 Should be scalable to 8 X 10 Gig interface or 60 X 1 Gig interface, should be capable to support minimum 4 X 40Gig interface in future.
7 High Availability
Non-Stop Routing, Graceful Restart, BFD for IPv4 and IPv6, VRRP
8 Protocol Support
DHCP, IP Multicast, PIM SM, PIM SSM, IGMP, MLD, RP, Next generation Multicast using MPLS LSP, IS-IS, HQOS, LDP, MPLS, MPLS FRR, L2 VPN, L3 VPN, VPLS, Diff Serv TE, RIP V 2, OSPF, BGP, NAT, should support three level HQOS with minimum 32K queues
9 QOS Router should have IPv4, IPv6 and QoS Classification. Should have 1M IPv4 and 1M IPv6 routing entries per system. Should have support for 15 logical routers.
10 Management
Network Management: SNMP v2 and upgradable to SNMP V3, Console management access, NTP or SNTP
5.2.4 Core Switch
The proposal should adhere to the following minimum eligibility criteria of Storage OEM:
87
• OEM of Core Switch have its own service centre in India and should have a Toll-free number
• OEM or Manufacturer should be ISO 9001, ISO 14001 and ISO 27001 certified.
• OEM or Manufacturer of the offered goods/ equipment’s should be a company registered under the companies Act since last 5 years in India. Valid company registration certificate should be submitted
S No. Parameter Tender Specifications Compliance (Y/N)
Offered Specification with Document Proof
1 Switching ports
Should support 9 or more business blade slots, 4 or more switching fabric blade slots, 2 management engine slots, 8 power module slots and 4 Fan Module slots, Support 10G Base-T copper ports Should be loaded with following modules/ports from day one 2* Management card with redundancy 2* Switch fabric card with redundancy and bandwidth of 1.2 Tbps or more 4* 40GE QSFP ports (4# of QSFP Modules Loaded support up to 300 Meters or more) 98*10GE(SFP+) ports (48# of SFP+ Modules Loaded support up to 300 Meters or more), 4*10GE Base-T Copper ports required 24*1G SFP Ports 24* 1G Copper ports For scalability core switch should support following Modules/ports below: 150*40GE(QSFP) or more 450*10GE(SFP+) or more 210 * 1G Copper / Fiber ports or more
2 Management Ports
RJ45 Console port, USB Port
3 Power Supply Module
Redundant Power Supply AC Should support 1+1 & N+N form Day1, less than 1600W 4# of Power supply to be loaded form Day 1
4 Switching Capacity
10Tbps or better Per Physical Switch
5 Throughput 7600 Mpps Per Physical Switch
6 Jumbo Frame 10K
7 IPv4/IPv6 Routing Table
8K or more
8 Mac Address 400K or better
9 L3 Interface 4K or better
10 Vlan 802.1Q, 4K VLAN, MAC VLAN, Voice VLAN, PVLAN, Protocol VLAN, Multicast VLAN
11 Spanning Tree STP, RSTP, MSTP
12 Qos 8 Queues Per Port and should support SWRR,
88
SP, WRR and WRED
13 ACL IP ACL, MAC ACL, MAC-IP ACL
14 IPv6 Features
"Should support ICMPv6, DNSv6, IPv6 PBR, IPv6 VRRPv3, OSPFv3 and BGP4+ Should support IPv6 Multicast VLAN, PIM-SM/DM for IPv6, IPv6 ACL and IPv6 QOS DHCP Server/Client for IPv6 Should support IPv6 Management Features"
15 L1/L2 Features
Shall Support 802.3ad LACP, support up to 128 group trunks with 8 ports for each trunk, LACP Load balance / Failover, N:1 Port Mirroring, LLDP, LLDP-MED, RSPAN, ERSPAN
16 IPv4 and IPv6 L3 Routing Features
Static Routing, RIPv2, OSPFv3, OSPF Multiple process, BGP4+, PBR, LPM Routing, ECMP, VRRPv3, Classless Inter Domain Routing (CIDR), Variable Length Subnet Mask (VLSM) (All Routing Features should be available form Day1)
17 Network security
ARP deep inspection, DOS Attack shield, ARP Close shield, Pink DOS attack protection, ICMP unreached attack protection, Protect DDOS Attack, CPU engine guard, IP address clone protection, illegal DHCP server search protection Key message protection, etc
18
Multicast Routing Support for IPv4 and IPv6
Multicast routing, PIM-SM, PIM-DM, PIM-SSM, IGMP v1/v2/v3, DVMRP, RP Address, Any cast RP, Static Multicast routing, Multicast receive control, illegal source multicast detect, MSDP
19 DHCP Features DHCP Client, DHCP Relay, DHCP Snooping, Option-82 and DHCP Server
20 Management Features
Web, CLI, Telnet and Console access, TFTP/FTP and SSH v1/v2 SNMPv1/v2c/v3 snooping RMON 1,2,3,9 and Radius Authentication Syslog (Internal & External) and SNTP/NTP sFlow, RSPAN
21 OAM Support 802.3ah and 802.1ag
22 MPLS More than 255 VRF
24 SDN Should support SDN Network
Datacenter Features
Support Virtual switch Framework, Virtual Ethernet Port Aggregator, Data Center Bridging Open flow 1.0 and 1.3 802.1Qbb: Priority-based Flow Control (PFC) 802.1Qaz: Enhanced Transmission Selection (ETS and DCBX) 802.1Qau: Congestion Notification (CN/QCN)
89
23 Environment
Operating Temperature: 0°C~50°C Storage Temperature: -40°C~75°C Relative Humidity: 10%~90% non-condensing Green Should be rack mountable, which shall not below 14U or above 20U in size (can be/between 14U~20U rack mountable).
24 General All types of switches and SFP modules should be from Same Manufacturer/OEM
5.2.5 TOR Distribution Switch
Sl. No. Parameter Tender Specifications Compliance (Y/N)
Offered Specification with Document Proof
1
Physical Ports 48# 10G SFP+ Slots (24# of SFP+ Modules to be loaded and support up to 300 Meters or more) 6# 40GE QSFP Slots (4# of QSFP Modules to be loaded and support up to 300 Meters or more)
2 RAM Switch should have minimum 1G RAM
3
Power Supply Module
2# Hot swappable Power Supply Modules support Should support 1+1 Power Supply Redundancy, Dual AC Power Supply modules Should be loaded form Day1, Support Hot swappable power supply
4 Fan Module Should support 3# of Hot swappable Fan
Modules supplied form Day1 FAN air flow form front to back
5 Management Port
1# RJ45 Console Port 1# RJ45 Ethernet Management port
6 Switching Capacity
1440 Gbps Per Physical Switch
7 Throughput 1070 Mpps Per Physical Switch
8 Jumbo Frame 10K
9 IPv4/IPv6 Routing Table
16K
10 Mac Address 96K
11 L3 Table 16K
12 Standards Support
Should support IEEE 802.3ak, IEEE 802.3ae, IEEE 802.3ba, IEEE 802.3ab, IEEE 802.3z, IEEE 802.3u, IEEE 802.3, IEEE802.3x
13 Vlan Management
Should support IEEE802.1Q, Private VLAN, Protocol VLAN, Voice VLAN, MAC VLAN and Multicast VLAN
90
Should support QinQ, Selective QinQ and Flexible QinQ
14
Layer 2 Features
802.1D STP, 802.1W RSTP, 802.1S MSTP, Root Guard, BPDU Guard and BPDU Tunnel 802.3ad LACP, max 128 group trunks with max 8 ports for each trunk Should support LLDP, LLDP-MED, UDLD and GVRP QoS - 8 Queues Per Port and should support SWRR, SP, WRR and WRED IP ACL, MAC ACL, MAC-IP ACL and Time Range ACL, IPv6 ACL DHCP Client, DHCP Relay, DHCP Snooping, Option-82 and DHCP Server Should support Virtual Stacking so that could virtualize multiple switches into one logical device DHCP Server/Client for IPv6 Should support RRPP ring topology and instance
15
Security Features
L2 Ring Protection, Loopback Detection and Fast Link Port Security, MAC Limit based on VLAN and Port Anti-ARP-Spoofing , Anti-ARP-Scan, ARP Binding, ARP Guard and Proxy ARP DAI, IEEE 802.1x, AAA, Radius and TACACS+
16
Multicast Routing Support for IPv4 and IPv6 on all protocols
IGMP v1/v2/v3 snooping and MLD v1/v2 snooping IGMP v1/v2/v3, IGMP Proxy, DVMRP, PIM-DM, PIM-SM, PIM-SSM, any cast RP and MSDP
17
Layer 3 Features Support for IPv4 & V6 ( All Routing Features should be available form Day1)
Support Static Route, RIPv1/v2, RIPng, OSPF, OSPFv3, BGP4, BGP4+, LPM, PBR, IPv6 PBR, ECMP, BFD, ISIS4 Should support IPv4 and IPv6 URPF Should support IPv6 LPM Routing Policy based routing for IPv4 and IPv6 Should support MPLS, VRF and LDP Should support IPv6 6to4 Tunnel, Configured Tunnel, ISATAP Tunnel and GRE Tunnel Should support ICMPv6, DNSv6, IPv6 PBR, IPv6 VRRPv3, RIPng, OSPFv3 and BGP4+ Should support IPv6 Multicast VLAN, PIM-SM/DM for IPv6
18
Reliability Should support EAPS and GERP with Less than 50ms ring protection recovery time for industrial high reliable application Should support RSTP and MSTP with
91
recovery time less than 1s Should support LACP with recovery time less than 10ms Should support VRRP Host Backup Should support Dual IOS image for fault redundant operating system and dual configuration file
19 MPLS Should support MPLS L3 VPN
Should support MPLS L2 VPN Support minimum 250 VRF interfaces
20
Management Features
Should support IPv6 Management Features Web/SSL (IPv4/IPv6), CLI, Telnet and Console access TFTP/FTP and SSH (IPv4/IPv6) SNMPv1/v2c/v3 (IPv4/IPv6) and SNMP Trap RMON 1,2,3,9 and Radius Authentication Syslog (IPv4/IPv6) and SNTP/NTP (IPv4/IPv6) Dual Firmware Images and Configuration Files sFlow, RSPAN and OAM (802.3ah and 802.1ag) Switch should be modular design Support Ethernet Multi-layer Ring Protection Protocol
21
Datacenter Features
Support Virtual switch Framework, Virtual Ethernet Port Aggregator, TRILL, VXLAN, Data Center Bridging 802.1Qbb: Priority-based Flow Control (PFC) 802.1Qaz: Enhanced Transmission Selection (ETS and DCBX) 802.1Qau: Congestion Notification (CN/QCN)
22 Operating Temperature
Working 0°C~50°C, Storage -40°C~70°C
23 General All types of switches and SFP modules should
be form Same Manufacturer/OEM
5.2.6 Access Switch 48 Port POE
S.No Tender Specification
Description Compliance (Y/N)
Offered Specification with Document Proof
1 Switching ports
Shall support 48# 10/100/1000 Mbps Base-T POE ports, 4# SFP+ 10G Fiber Ports, along with Additional stacking ports
2 Management Ports
RJ45 Console port, USB/SD Card Port, dedicated Ethernet Management port
3 Switching Capacity
256Gbps Per Physical Switch form day1
92
4 Throughput 190Mpps Per Physical Switch form day1
5 Jumbo Frame 10K
6 IPv4/IPv6 Routing Table
16K or more
7 Vlan 802.1Q, 4K VLAN, MAC VLAN, Voice VLAN, PVLAN, Protocol VLAN, Multicast VLAN.
8 Spanning Tree STP, RSTP, MSTP, RSPAN, ERSPAN
9 Qos 8 Queues Per Port and should support SWRR, SP, WRR and WRED
10 ACL IP ACL, MAC ACL, MAC-IP ACL
11 IPv6 Features
Should support ICMPv6, DNSv6, IPv6 PBR, IPv6 VRRPv3, OSPFv3 and BGP4+
Should support IPv6 Multicast VLAN, PIM-SM/DM for IPv6, IPv6 ACL and IPv6 QOS
DHCP Server/Client for IPv6
Should support IPv6 Management Features
12 IPv4 L3 Routing Features
Static Routing, RIPv1/v2, OSPFv2, OSPFv3, BGP4, BGP4+, PBR, LPM Routing, ECMP, VRRP (All Routing Features should be available form Day1)
13 IPv6 L3 Routing Features
6 to 4 Tunnel / Dual stack , VRRPv3, OSPFv3, BGP4+, IPv6, PBR(All Routing Features should be available form Day1)
14 Multicast Routing
Multicast routing, PIM-SM, PIM-DM, IGMP v1/v2/v3.
15 DHCP Features DHCP Client, DHCP Relay, DHCP Snooping, Option-82 and DHCP Server
16 Power Supply Support build in Dual AC Power Supply Should be loaded form Day1 power supply
17 Management Features
Web, CLI, Telnet and Console access TFTP/FTP and SSH v1/v2
SNMPv1/v2c/v3
RMON 1,2,3,9 and Radius Authentication
Syslog (Internal & External) and SNTP/NTP
Dual Firmware Images and Configuration Files, sFlow, RSPAN
18 OAM Support 802.3ah and 802.1ag
19 POE Budget 700 Watts or above
20 POE Protocols IEEE802.3af(15.4W), IEEE802.3at(30W), IEEE802.3bt(60W)
21 Power supply Dual redundant Hot swappable power supply loaded form day1
22 Environment
Operating Temperature: 0°C~50°C
Storage Temperature: -40°C~75°C
Relative Humidity: 10%~90% non-condensing
93
Green Energy: IEEE 802.3az (Energy Efficient Ethernet)
23 General All types of switches and SFP modules should be form Same Manufacturer/OEM
5.2.7 Access Switch 24 Port Non-POE
S.No Tender Specification
Description Compliance (Yes/No)
Offered Specification with Document Proof
1 Switching ports Shall support 24# 10/100/1000 Mbps Base-T ports, 4# SFP+ 10G Fiber Ports
2 Management Ports
RJ45 Console port, USB/SD Card Port, dedicated Ethernet Management port
3 Switching Capacity
128Gbps Per Physical Switch
4 Throughput 95Mpps Per Physical Switch
5 Jumbo Frame 10K
6 IPv4/IPv6 Routing Table
16K or more
7 Vlan 802.1Q, 4K VLAN, MAC VLAN, Voice VLAN, PVLAN, Protocol VLAN, Multicast VLAN.
8 Spanning Tree STP, RSTP, MSTP
9 Qos 8 Queues Per Port and should support SWRR, SP, WRR and WRED
10 ACL IP ACL, MAC ACL, MAC-IP ACL
11 IPv6 Features
Should support ICMPv6, DNSv6, IPv6 PBR, IPv6 VRRPv3, OSPFv3 and BGP4+
Should support IPv6 Multicast VLAN, PIM-SM/DM for IPv6, IPv6 ACL and IPv6 QOS
DHCP Server/Client for IPv6
Should support IPv6 Management Features
12 IPv4 L3 Routing Features
Static Routing, RIPv1/v2, OSPFv2, OSPFv3, BGP4, BGP4+, PBR, LPM Routing, ECMP, VRRP (All Routing Features should be available form Day1)
13 IPv6 L3 Routing Features
6 to 4 Tunnel / Dual stack , VRRPv3, OSPFv3, BGP4+, IPv6, PBR(All Routing Features should be available form Day1)
14 Multicast Routing
Multicast routing, PIM-SM, PIM-DM, IGMP v1/v2/v3.
15 DHCP Features DHCP Client, DHCP Relay, DHCP Snooping, Option-82 and DHCP Server
16 Power Supply Support build in Dual AC Power Supply Should be loaded form Day1 power supply
17 Management Web, CLI, Telnet and Console access
94
Features TFTP/FTP and SSH v1/v2
SNMPv1/v2c/v3
RMON 1,2,3,9 and Radius Authentication
Syslog (Internal & External) and SNTP/NTP
Dual Firmware Images and Configuration Files, sFlow, RSPAN
18 OAM Support 802.3ah and 802.1ag
19 Power supply Dual redundant power supply loaded from day1
20 Environment
Operating Temperature: 0°C~50°C
Storage Temperature: -40°C~75°C
Relative Humidity: 10%~90% non-condensing
Green Energy: IEEE 802.3az (Energy Efficient Ethernet)
21 General All types of switches and SFP modules should be from Same Manufacturer/OEM
5.2.8 Server Load Balancer
S.No Tender Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 Server Load Balancing Mechanism - Cyclic, Hash, Least numbers of users - Weighted Cyclic, Least Amount of Traffic - NT Algorithm / Private Algorithm / Customizable Algorithm / Response Time
2 Redundancy Features - Routing protocols RIPv1/RIPv2/OSPF - Static Routing policy support
3 Server Load Balancing Features - Server and Client process coexist - UDP Stateless - Service Failover - Backup/Overflow - Direct Server Return - Client NAT - Port Multiplexing -Virtual Ports to Real Ports Mapping - DNS Load Balancing
4 Load Balancing Applications - Application/ Web Server, MMS, RTSP, Streaming Media - DNS, FTP, ACTIVE & PASSIVE, REXEC, RSH, - LDAP, RADIUS
5 Browser Type Farm - Global Server Load Balancing - Load Balancing Algorithms - HTTP Redirection, -HTTP - DNS Redirection, RTSP Redirection - DNS Fall-back Redirection, HTTP Layer 7 Redirection
95
6 Management Features - Secure Web Based Management - SSH - TELNET - SNMP v1, 2, 3 Based GUI - Command Line
7 The solution must provide Out of the box reporting templates for performance, availability, operation, virtualization and capacity and audit
8 The solution should provide reports that can prove IT service quality levels, such as application response times and server resource consumption
9 The system reports should be accessible via web browser and Reports can be published in PDF and csv format
10 The solution must provide Reports that can be scheduled to publish automatically, or they can be produced on demand
11 The solution should be able to report in the context of the business services that the infrastructure elements support—clearly showing how the infrastructure impacts business service levels
12 The solution should provide Business Service Management functionality to track Service quality by logically grouping Network, Server and Application components. The solution should provide correlation between Network, Server and Application to identify the business impact from the specific event or alarm
13 The solution must provide way to define key performance indicators (KPIs) within the Service Quality report.
14 The solution must provide SLA measurement to track service quality from both Availability and Performance perspective
5.2.9 EMS (Enterprise Management System
S.No. Tender Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 For effective operations and management of IT Operations, there is a need for an industry-standard Enterprise Management System (EMS). Given the expanse and scope of the project, EMS becomes very critical for IT Operations and SLA Measurement. Some of the critical aspects that need to be considered for operations of IT setup of are:
• Network Fault and SNMP Management
• Network Health Management
• Application Performance Management
• Server Performance Monitoring
• Centralized Log Management
• Centralized and Unified Dashboard
• Centralized and Customizable Service Level Reporting
• Help Desk for Incident Management
2 The Monitoring Solution should provide Unified
96
Architectural design offering seamless common functions including but not limited to:
• Event and Alarm management,
• Auto-discovery of the IT environment,
• Performance and availability management
• Correlation and root cause analysis
• Service Level Management, notifications
• Reporting and analytics
• Automation and Customization
3 There should be a tight integration between infrastructure metrics and logs to have the single consolidated console of Infrastructure & security events.
4
Consolidate IT event management activities into a single operations bridge that allows operator quickly identify the cause of the IT incident, reduces duplication of effort and decreases the time it takes to rectify IT issues.
5
The Operator should be able to get consolidated system/network event details and security events (current and historical) from the same console and save time in troubleshooting / isolating the issue.
6 The operator should be able to build correlation rules in a simple GUI based environment where the Operator should be able to correlate cross domain events
7
Scalability – The system should be capable of supporting at least 100 thousand network flow per second on single server with capability to capture each unique traffic conversations
8
Scalability – The solution must be scalable, it should be able to support upto 25000 log events per second and be able to support beyond 25000 EPS by Linearly adding more servers of either reference system type, depending on the size of the expected load
9 The solution shall provide future scalability of the whole system without major architectural changes.
10
The Solution shall be distributed, scalable, and multi-platform and open to third party integration such as Cloud, Virtualization, Database, Web Server, Application Server platforms etc.
11 All the required modules should be from same OEM and should be tightly integrated for single pane of glass view of enterprise monitoring
12
The solution must provide single integrated dashboard to provide line of business views and drill down capabilities to navigate technical operators right from services to last infrastructure components
13
Consolidated dashboards of the proposed EMS solution must be able to do dynamic service modelling of all business-critical production services & use near-real time Service Model for efficient cross domain topology-based event correlation.
a. Consolidated Dashboard
97
1 The platform must provide complete cross-domain visibility of IT infrastructure issues
2 The platform must consolidate monitoring events from across layers such as Network, Server, Application, Database etc.
3 The solution should support dynamic discovery to maintains Run-time Service Model accuracy e.g. virtualization and cloud
4 The solution must support custom dashboards for different role users such as Management, admin and report users
5 The solution must allow creating custom data widget to visualize data with user preferences
6 The proposed solution must support capacity views to find most consumed resources.
7
The solution should provide superior view of infrastructure health across system, networks, application and other IT Infrastructure components into a consolidated, central console
8 The solution should allow for customizable operator perspectives
b. System and Application Monitoring:
1
The solution should offer service driven operations management of the IT environment to manage distributed, heterogeneous systems - Windows, UNIX & LINUX from a single management station.
2
The solution should carry out automated probable cause analysis by picking up feeds from every infrastructure component being monitored and automating the correlation of these alarms or events to point out the probable cause using remedy actions - E.g. pull the top 5 processes consuming most of the CPU when CPU alarm triggers
3
The solution should provide a centralized point of control with out-of-the-box policy-based management intelligence for easy deployment for the servers, operating systems, applications and services for correlating and managing all the IT infrastructure components of a business service
4 The solution shall be able to monitor Hypervisor host hardware status e.g. fans, disk, memory, CPU etc.
5 The solution must support SNMP v1-3, PowerShell, SSH, JDBC, HTTP, JMX, collected agents for monitoring various type of devices and systems
6 It should also be able to monitor various operating system parameters depending on the operating system being monitored and setting thresholds.
7
The solution should support Virtual platforms - VMware and Microsoft Hyper-V, Citrix Xen, AWS, Azure and provide capability to monitor both Microsoft .NET and J2EE applications from the same platform
8 The solution should provide support for maintenance window and scheduled downtimes
98
9 The solution should measure the end users' experiences based on transactions without the need to install agents on user desktops.
10
The solution must be able to provide user usage analysis and show how user's success rate, average time and transaction count has changed over a specific period such as current week versus previous week.
11 The solution must be able to provide the ability to detect and alert when users experience HTTP error codes such as 404 errors or errors coming from the web application.
C. Fault Management
1
The proposed solution must should provide out of the box root cause analysis with multiple root cause algorithms inbuilt for root cause analysis. It should also have a strong event correlation engine which can correlate the events based on event pairing, event sequencing etc.
2
The Platform must include an event correlation automatically fed with events originating from managed elements, monitoring tools or data sources external to the platform. This correlation must perform:
• Event filtering
• Event aggregation
• Event masking
3
The proposed solution must support creating and monitoring of rising or falling thresholds with respect to basic key performance indicators for network, system and application infrastructures.
4
The solution should have predictive analytics and intelligence in-built into it to detect any anomaly before it could potentially hit the threshold thereby giving enough lead time to users to resolve the issues before the threshold is breached.
5
The proposed solution should provide out of the box root cause analysis with multiple root cause algorithms inbuilt for root cause analysis. It should also have a strong event correlation engine which can correlate the events based on event pairing, event sequencing etc.
6 Powerful correlation capabilities to reduce number of actionable events. Topology based and event stream-based correlation should be made available.
7 The solution must offer relevant remedy tools, graphs in context of a selected fault alarm/event
8 The proposed monitoring solution should have capability to configure actions-based rules for set of pre-defined alarms/alerts enabling automation of set tasks.
9 The Platform must support Event or Alarm Correlation integrations with service desk to trigger automated creation of incidents, problems management
10 The solution should classify events based on business impact
11 The solution should allow creation of correlation or
99
analytics rules for administrators
12 The proposed solution must provide default event dashboard to identify, accept and assign generated alarms.
d. Log Management:
1 The proposed solution must provide a common classification of event irrespective of the log format
2 The proposed solution must provide the ability to store/ retain both normalized and the original raw format of the event log as for forensic purposes.
3 The log data generated should be stored in a centralized server. The period upto which the data must be available should be customizable.
4
The proposed solution must support logs collected from commercial and proprietary applications i.e. Microsoft, Cisco, Brocade, HP, Security System, Firewall, Access Points etc.
5 The proposed solution must support log collection for Directories (i.e. AD, LDAP), hosted applications such as database, web server etc. using agents
6 The proposed solution must support log collection from Network infrastructure (i.e. switches, routers, etc.). Please describe the level of support for this type of product.
7
The system shall support the following log formats for log collection:
• Windows Event Log
• Syslog
• Access Log Data
• Application Log data
• Any Custom Log data
• Text Log (flat file)
8
The solution should be able to collect raw logs in real-time to a Central log database from any IP device including:
• Networking devices (router/switches/ Cameras/ storage)
• Security devices (IDS/IPS, AV, Firewall/DB Security solutions)
• Operating systems (Windows 2003/2008, Unix, linux, AIX)
• Virtualization Platforms (Microsoft HyperV, VMware Vcenter / VSphere 4.X, vDirector, Citrix)
• Databases (Oracle/SQL/MYSQL/DB2)
9 The collection devices should support collection of logs through Syslog and provide native Windows Agents as well as Agentless (PowerShell) connectors
10 The proposed solution must provide alerting based upon established policy
11 The proposed solution must provide SDK/API to write custom connectors and collectors to pull log and monitoring data from third party system
100
12 The proposed solution must provide UI based wizard and capabilities to minimize false positives and deliver accurate results.
13 The proposed solution must collect, index the log messages and support full text searching for forensic investigation
14
The proposed solution must support the ability to act upon receiving an alert. For example, the solution should support the ability to initiate a script or send an email message.
15 The solution must provide pre-defined log correlation rules to detect suspicious behaviour
16 The solution must support real-time and scheduled alerting timeline while creating a log policy to catch specific log pattern
17 The solution should support applying regex pattern in real-time to extract vendor specific log data for reporting and alerting purpose
18 The system shall have the capability to drag and drop building of custom queries & reports.
19
The system shall be capable of operating at a sustained 10000 EPS per collection device. The system shall provide the ability to scale to higher event rates by adding multiple collection devices.
e Service Level Reporting:
1 The solution must provide Out of the box reporting templates for performance, availability, operation, virtualization and capacity and audit
2 The solution should provide reports that can prove IT service quality levels, such as application response times and server resource consumption
3 The system reports should be accessible via web browser and Reports can be published in PDF and csv format
4 The solution must provide Reports that can be scheduled to publish automatically, or they can be produced on demand
5
The solution should be able to report in the context of the business services that the infrastructure elements support—clearly showing how the infrastructure impacts business service levels
6
The solution should provide Business Service Management functionality to track Service quality by logically grouping Network, Server and Application components. The solution should provide correlation between Network, Server and Application to identify the business impact from the specific event or alarm
7 The solution must provide way to define key performance indicators (KPIs) within the Service Quality report.
8 The solution must provide SLA measurement to track service quality from both Availability and Performance perspective.
101
5.2.10 End Point Security
S.No Tender Specification Compliance
(Yes/No)
Offered
Specification with Document Proof
1 Antivirus Protection 1. Must offer comprehensive client/server security by protecting enterprise
networks from viruses, Trojans, worms, hackers, network viruses, mixed threat attack from multiple entry points, and spyware.
2. Have the capability to detect all in-the-wild viruses and Antivirus Engine should be certified with reputed ICSA Labs, AV Test, AV Comparatives
3. Must have the capability to detect and block files with malicious executable content and embedded/compressed executable that use real-time compression algorithms
4. Must have the capability to detect and remove rootkits 5. Must have the capability to detect and quarantine suspicious files. 6. Must have the capability to detect malware by behavioral detection
techniques. 7. Must have the capability to detect and remove rogue wares 8. Must have the capability to detect and block ransom ware attacks. 9. Must have the capability to backup and restore data so that in case of ransom
ware attack data can be easily retrieved. 10. Must have the capability to identify source of infection i.e. from where the
infection has originated in the network. 11. Must have the capability to restore a file from quarantine if the file is
deemed safe. 12. Must provide Virus Outbreak Prevention mechanism, which should be
activated based on threshold of detected malware. 13. Should have anti malware protection and cleanup capability. 14. Ordinary Users should not be able to modify AV settings except for those in
special groups as deemed necessary by the Administrators. 15. Update Managers: Should have the capability to create multiple update
servers to distribute updates load in large network environment that reduce bandwidth consumed during definition updates.
16. Must have the capability to scan compressed, archived, and packed files. 17. Must have the capability to scan and disinfect infections from mobile
phones. 18. Must have the capability to scan plug and play USB storage drives as soon as
they are connected. 19. Must have the capability to terminate virus program threads in memory,
repair registry, remove any malicious OS processes created by trojans. 20. Must have the capability to disconnect infected endpoints from the network. 21. Must have the capability to scan and repair OLE (Object Linking and
Embedded) files.
102
22. Must have capability to disconnect endpoint from the network in case if virus/suspicious file is active in memory.
23. Must have the capability to exclude file types/extensions and folders from real-time scanning.
24. Must have provision to send Email Notification with list of unprotected systems in the network.
25. Must have the capability to specify file type to take critical data backup in case of ransom ware attack.
2 Vulnerability Scan 1. Must have capability to scan and report vulnerabilities present in installed
applications. 2. Must provide summarized view of vulnerabilities as per severity. i.e. High,
Medium and Low. 3. Must have capability to schedule vulnerability scan periodically in order to get
latest reports of vulnerabilities present in the network.
3 Patch Management 1. Must have capability to scan missing patches for Microsoft applications. For
example: Windows, Office, Internet Explorer. 2. Must have capability to scan missing patches for Non-Microsoft applications.
ex: Adobe Reader, Adobe Acrobat, Adobe Flash Player, VLC, Java, Putty, Notepad++, 7-Zip, Mozilla Firefox and Mozilla Thunderbird.
3. Must have the capability to patch applications on air-gapped endpoints, which don't have(or may have limited) connectivity with the central EPS server.
4. Must have capability to generate reports of missing patches as per client. 5. Must have capability to generate reports of missing patches as per missing
update. 6. Must have capability to generate status reports such as number of scanned
patches, downloaded patches, installed patches and number of failed installations for each endpoint.
7. Must provide summarized view of critical, moderate and important updates missing on endpoints.
8. Must have capability to schedule scanning and installation of missing patches.
4 Device Control 1. Must have the capability to grant allow, block, read-only access to various
devices. 2. Must have the capability to grant access rights for storage devices such as
USB, CD/DVD, Card Reader, Floppy Drive etc. 3. Must have the capability to regulate the use of Wi-Fi and Bluetooth
connections. 4. Must have the capability to retain control over interfaces such as Firewire
Bus, Serial Port, SATA Controller, Thunderbolt, etc 5. Must have the capability to control and regulate PCMCIA devices, MTD/SCSCI
Card reader devices etc. 6. Must have the capability to control and regulate the use of printers,
scanners, web cameras, and network shares. 7. Must have the capability to allow or block the attachment of Windows
Portable devices like Digicams, Smartphones etc. 8. Must have the capability to allow or block the attachment of Mobile Phones
i.e. Android Phone, IPhone, iPad, & iPod, Blackberry etc. to the endpoints.
103
9. Must have the capability to allow or block Teensy Board devices. 10. Must have the capability to exclude any particular device from device control
policies. 11. Must have the capability to exclude any particular devices based on Model
Name. 12. Must have the capability to encrypt USB Pen Drive contents and make it
accessible only on endpoints where EPS client is installed. 13. Must have the capability to allow access of USB Pen drives temporarilty to
some authorized users. 14. Must have the capability to completely block USB Interfaces to deny access
to all USB devices(except Keyboard and Mouse and mass storage devices) 15. Must have the capability to support NTFS & FAT formatted devices for
authorization. 16. Provision to add whitelisted Wi-Fi SSID in Device Control Wi-Fi configuration.
Endpoints will only able to connect to whitelisted Wi-Fi SSID 17. Must have the capability to exclude USB devices based on serial number
5 Data Loss Prevention 1. Must have the capability to report the activity on various data transfer channels such as removable devices, network share, clipboard 2. Must have capability to monitor printing activity on each endpoint. 3. Must have capability to block printing activity on each endpoint. 4. Must have the capability to monitor and control print screen operation. 5. Must have the capability to monitor data transfer via various applications
such as web browsers, messaging software's, etc. on windows as well as mac platforms.
6. Must have the capability to monitor data transfer via file sharing applications, cloud services and social media.
7. Must have the capability to monitor data transfer via Email clients. 8. Must have the capability to monitor and control the flow of confidential
information in files. 9. Must have the capability to add custom defined words/phrases to search for
in different file types. 10. Must have the capability to block files based on file extensions and file types. 11. Must have the capability to provide exemption to domains. 12. Must have the capability to provide exemption to application.
13. Must have the capability to provide exemption to network share location. 14. Must have the capability to scan and detect confidential data residing on
storage drive. 15. Must have the capability to add custom applications for DLP monitoring. 16. Must have the capability to support Optical Character Recognition for data
monitoring. 17. Must have the capbility to classify file manually as confidential or public. File
Activity Monitoring
6 File Activity Monitoring 1. Must have the capability to monitor activities related to file handling such as
copy, delete, move on local drives, removable drives and network drives 2. Must have the capability to monitor certain file types. 3. Must have the capability to exclude certain files/folders/paths from
monitoring procedures.
7 Asset Management
104
1. Must have the capability to collect system and hardware information related to remote endpoints.
2. Must have the capability to obtain a summary report of various software's/updates installed on endpoints
3. Must have the capability to track software changes happening on endpoints i.e. applications installed/uninstalled.
4. Must have the capability to track hardware changes happening on endpoints. E.g. RAM Changed, Processor changed, etc.
5. Must have the capability to display Software license key for Windows OS and MS Office (last 4 digits)
6. Must provide comprehensive asset management reports based on following parameters: Operating System, Application Name, System Manufacturer, Installed Physical RAM, Processor and Last Shutdown time.
8 IDS/IPS 1. Must have the capability to detect, and prevent network based and host based
intruder attempts on the home networks. 2. Must have the capability to prevent port scanning attacks. 3. Must have the capability to prevent DDOS attacks. 4 Must have the capability
to generate reports for potential security breaches, policy violations, and suspicious traffic flow.
9 Web Security and Web Filtering 1. Must have the capability to block user access to malicious and phishing
websites from configured endpoints. 2. Must have the capability to block user access to websites based on their
categories e.g. Social Networking, News, etc. 3. Must have the capability to block entire domain or a particular website/URL 4. Must have provision to exclude certain websites or entire domains. 5. Must have the capability to block https sites. 6. Must support safe banking feature to perform banking transactions. 7. Must support sandbox browsing for safe and secure browsing. 8. Must have the capability to schedule internet access time. 9. Must have the capability exclude certain internal URL's from the internet
restriction hours.
10 Application Control 1. Must be able to block applications based on application categories. E.g.
Download Managers, File sharing applications, Games, etc. 2. Must have ability to add custom applications to the blocked application list. 3. Must have capability to collect list of all installed applications in the network. 4. Provision to block applications based on application name.
11 Firewall 1. Must provide the flexibility to create firewall rules to filter connections by IP
address, port number, or protocol, and then apply the rules to different groups of users.
2. Must have the capability to examine and control all incoming and outgoing traffic per configured settings for ports, source, or origin or destination address.
3. Must have the capability to monitor Wi-Fi Networks and send alerts when a client connects to unsecured Wi-Fi Network.
4. Provision to Allow/Disallow applications.
12 Email Protection 1. Must have the capability to block infected and spam mails.
105
2. Must have the capability to allow only trusted email clients to send mails. 3. Must have the capability to scan incoming emails encrypted over SSL/TLS
protocol. 4. Must have the capability to block attachments in incoming emails having
multiple extensions (ex -doc.exe). 5. Must have the capability to block emails which try to exploit vulnerabilities in
the email client. 6. Must have the capability to block all or user specified attachments in
incoming emails. 7. Must have provision for trusted email client configuration on Server
13 Groups and Policies 1. Must have the capability to create multiple user groups as per organizational
structure. 2. Must have the capability to assign different policy configuration to each
group. 3. Must have the capability to import group structure from Active Directory. 4. Must have the capability to import/export groups and policies.
14 Client Deployment 1. Must have the capability to deploy the Client software using the following
mechanisms: 1.1 Client Packager (Executable & Microsoft Installer (MSI) Package Format) 1.2 Web install page 1.3 Login Script Setup 1.4 Remote installation on single endpoint or on entire IP range. 1.5 From a client disk image 1.6 Through Active Directory and by creating group policy object
2. Client uninstallation should only be done by administrator. 3. Must have capability to create password protected client packager. 4. Must have provision to send Email Notification when any new eps client is
installed/uninstalled.
15 Server Deployment 1. Must have the facility to deploy the EPS Server on cloud based servers on
Microsoft Azure and AWS Platform. 2. Must support installation of EPS server on dynamic (DHCP) IP address. 3. Must have the facility to deploy the EPS Server on Public IP/FQDN 4. Must have the facility to support multi-tier master-slave deployment
16 Management Features 1. Must provide a secure GUI or Web-based management console to give
administrators access to all clients and servers on the network for client administration.
2. Must have the flexibility to roll back updates if required via the management console.
3. Should have role based administration capability. 4. Must support plug-in modules designed to add new security features without
having to redeploy the entire solution, thereby reducing effort and time needed to deploy new security capability to clients and servers across the network
5. Must have provision for Self/Tamper Protection for Seqrite EPS files/folders. 6. Group Administrator to manage certain groups and policies associated with
the group.
17 Notification, Reporting and Logging
106
1. Must provide email and sms notification for various critical events such as virus outbreak, ransomware incidents, license getting expired.etc.
2. Must have the capability to generate a graphical as well as tabular reports. 3. Must have capability to export reports in multiple formats such as PDF and
CSV. 4. Must have capability to automatically send the report to administrators email
address as per configured schedule. 5. Must have capability to automatically purge old reports after a preconfigured
duration. 6. Must have provision to send-Email Notification for status of update
downloaded by Update Manager. 7. Must have capability to log all activities of management server.
18 Roaming Client Management 1. Must have capability to configure policies for roaming clients even if it is out
of network through cloud based management platform. 2. Must have capability to get status, reports from roaming clients even if it is
out of network through cloud based management platform. 3. Must have capability to install/uninstall EPS Clients on endpoints which are
outside the corporate network.
19 Management through Cloud Platform 1. Must have capability to view consolidated status of organizational security of
various EPS products installed at different offices. 2. Must have capability to backup and restore EPS server configuration files from
cloud platform. 3. Must have capability to promote an effective local policy to global policy and
apply it globally to all offices at different locations. 4. Must have capability to create multiple access levels or hierarchy to allow
access to cloud platform as per the assigned groups/products. E.g. Administrators, Group Administrators and Product Administrators. These users should able log on to cloud platform from anywhere and get a consolidated view of their own product(s), group(s) or entire organization as applicable.
5. Must have capability to access local EPS console from anywhere and take required action in case of emergency.
6. Must have capability to view summary reports for all activities happening at various local offices.
7. Must have capability to get reports and notifications through email.
20 Update Manager 1. Should have the capability to create multiple update servers to distribute
updates load in large network environment that reduce bandwidth consumed during definition updates.
2. Must have the capability to schedule the frequency of downloading the updates.
3. Must have capability to allocate user-specified bandwidth to the Update Manager from the total available bandwidth.
21 Other Features 1. Must have the capability to prevent a user from accessing the operating
system in safe mode. 2. Must have the capability to improve performance of endpoints by cleaning
junk files and deleting invalid registry/disk entries. 3. Must have the capability to manage mobile workforce when they moves out
107
of the corporate network. 4. Should have the ability to facilitate removal of 3rd party Antivirus solutions
at the time of installation
22 MAC Features 1. Must offer comprehensive client security by protecting enterprise networks
from viruses, Trojans, worms, hackers, network viruses, mixed threat attack from multiple entry points, and spyware.
2. Must have the capability to scan compressed, archived, and packed files. 3. Must have the capability to scan files with malicious executable content 4. Must have the capability to prevent a user from accessing the operating
system in safe mode. 5. sData Loss Prevention
5.1 Must have the capability to scan and detect confidential data residing on storage drive 5.2 Must have the capability to report the activity of copying confidential data to a clipboard. 5.3 Must have the capability to monitor data transfer via file sharing applications, cloud services and social media. 5.4 Must have the capability to monitor and control the flow of confidential information in files. 5.5 Must have the capability to add custom defined words/phrases to search for in different file types.
6. Asset Management 6.1 Must have the capability to detect hardware changes on the clients and display the number of changes. 6.2 Must have the capability to detect software changes on the clients and display the number of changes. 6.3 Must have the capability to track software changes happening on endpoints i.e. applications installed/uninstalled. 6.4 Must have the capability to track hardware changes happening on endpoints. E.g. RAM Changed, Processor changed, etc. Must provide comprehensive asset management reports based on following parameters: Operating System, Application Name, System Manufacturer, Installed Physical RAM, Processor and Last Shutdown time.
7. Advanced Device Control 7.1 Must have the capability to grant allow, block, read-only access to various devices. 7.2 Must have the capability to allow access of USB Pen drives temporarilty to some authorized users.
8. Client Deployment: Must have the capability to deploy the Client software using the following mechanisms: 8.1 Client Packager (DMG file format in a self-extracting TAR file) 8.2 Web install page 8.3 Remote installation on single endpoint or on entire IP range.
9. Email Protection 9.1 Must have the capability to block infected and spam mails.
10. Web Security & Filtering 10.1 Must have the capability to block user access to malicious and phishing
websites from configured endpoints. 10.2 Must have the capability to block user access to websites based on
108
their categories e.g. Social Networking, News, etc. 10.3 Must have the capability to block entire domain or a particular
website/URL 11. File Activity Monitor
11.1 Must have the capability to monitor activities related to file handling such as copy, delete, move on local drives, removable drives and network drives.
11.2 Must have the capability to monitor certain file types. 12. Roaming Client Management
12.1 Must have capability to configure policies for roaming clients even if it is out of network through cloud based management platform. 12.2 Must have capability to get status, reports from roaming clients even if it is out of network through cloud based management platform.
13. Update Manager 13.1 Should have the capability to create multiple update servers to distribute updates load in large network environment that reduce bandwidth consumed during definition updates. 13.2 Must have the capability to schedule the frequency of downloading the updates.
23 Linux Features 1. Must offer comprehensive client/server security by protecting enterprise
networks from viruses, Trojans, worms, hackers, network viruses, mixed threat attack from multiple entry points, and spyware.
2. Must have the capability to scan external drives such as USB Storage, CD/DVD's
3. Must have the capability to define scan schedules for the clients. 4. Must have the capability to initiate scan remotely on clients. 5. Must have the capability to monitor and protected shared folders on Samba
Server. 6. Asset Management
6.1 Must have the capability to detect hardware changes on the clients and display the number of changes.
6.2 Must have the capability to detect software changes on the clients and display the number of changes.
6.3 Must have the capability to track software changes happening on endpoints i.e. applications installed/uninstalled.
6.4 Must have the capability to track hardware changes happening on endpoints. E.g. RAM Changed, Processor changed, etc.
6.5 Must provide comprehensive asset management reports based on following parameters: Operating System, Application Name, System Manufacturer, Installed Physical RAM, Processor and Last Shutdown time.
7. Advanced Device Control 7.1 Must have the capability to grant allow, block, access to various devices.
8. Client Deployment: Must have the capability to deploy the Client software using the following mechanisms: 8.1 Client Packager
9. Web Security and Web Filtering 9.1 Must have the capability to block user access to malicious and phishing websites from configured endpoints. 9.2 Must have the capability to block user access to websites based on their
109
categories e.g. Social Networking, News, etc. 9.3 Must have the capability to block entire domain or a particular website/URL.
24 Windows Platform Support 1. Microsoft Windows XP Home (32-bit) / Professional Edition (32-bit / 64-bit) 2. Microsoft Windows Server 2003 Web / Standard / Enterprise (32-bit/64-bit) 3. Microsoft Windows Server 2003 R2 Web / Standard / Enterprise
/Datacenter 4. Microsoft Windows Vista Home Basic / Home Premium / Business /
Enterprise / Ultimate (32-bit/64-bit) 5. Microsoft Windows 2008 Server Web / Standard / Enterprise (32-bit/64-bit)
/ Datacenter (64-bit) 6. Microsoft Windows 2008 Server R2 Web / Standard / Enterprise /
Datacenter (64-bit) 7. Microsoft Windows 2016 Server Edition 8. Microsoft Windows 7 Home Basic / Home Premium / Professional /
Enterprise / Ultimate (32-bit/64-bit) 9. Microsoft Windows 8 Professional / Enterprise (32-bit/64-bit) 10. Microsoft Windows 8.1 Professional / Enterprise (32-bit/64-bit) 11. Microsoft Windows SBS 2011 Standard / Essentials 12. Microsoft Windows Server 2012 Standard / Essentials / Foundation /
Storage Server / Datacenter (64-bit) 13. Microsoft Windows MultiPoint Server 2012 Standard (64-bit) 14. Microsoft Windows Server 2012 R2 Standard / Datacenter (64-bit) 15
Microsoft Windows 10 Home / Pro / Enterprise / Education (32-Bit/64-Bit)
25 MAC Platform Support 1 Mac OS X 10.7 2 Mac OS X 10.8 3 Mac OS X 10.9 4 Mac OS X 10.10 5 MAC OS X 10.11 6 MAC OS X 10.12 7 MAC OS X 10.13
26 Linux Platform Support 32-Bit: BOSS 6 Fedora 14, 18, 19, 20, 21, 22, 23, 24, 25 Open SUSE 11.4, 12.2, 12.3, 13.2, 42.2 Linux Mint 13, 14, 15, 16, 17.3, 18 Ubuntu 10.10, 11.4, 12.04 LTS, 12.04.3 LTS, 13.04, 13.10, 14.04, 14.10, 15.04, 16.04 LTS, 16.10, 17.04 Cent OS 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9 RHEL 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8,6.9 64-Bit: Fedora 14, 18, 19, 20, 21, 22, 23, 24, 25 Open SUSE 11.4, 12.2, 12.3, 42.3 Linux Mint 13, 14, 15, 16, 17.3, 18 Ubuntu 10.10, 11.4, 12.04.2 LTS, 13.04, 13.10, 14.04, 14.10, 15.04, 16.04 LTS, 16.10, 17.04 Cent OS 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 7.0 RHEL 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3 SUSE 11.0, 12.0, 12.2
27 Distributed Environment Support (Centralized and Decentralized Control) EPS has support for Master, Slave configuration. This is helpful for the customers who has distributed environment of Assets with one HO but multiple branch offices in multiple regions. Support Centralized defragmentation and Tuning of all End Points
110
28 Ransom ware Protection Critical Data Backup option for Ransom ware protection
5.2.11 Servers
5.2.11.1 Rack GPU Server
S.No Item Parameter and Minimum Specification
Compliance (Yes/No)
Offered Specification with Document Proof
1 Chipset
Lewisburg PCH Intel C621 or equivalent
2 Form Factor
Max. 2U rack mounted with sliding rails
3 Configured CPU
Should be populated with 2nos. Of latest series Intel Gold CPU each should be min. 20core & min. 2.0Ghz or better
4
Memory slots
24 DDR4 DIMM slots RDIMMS& LR DIMMS supporting speeds up to 2666MT/s. Optionally support up to 12 DIMM & 12 NVDIMM
5 Memory configured
Server should be configured with 256Gb memory & scalable to 1.5TB
6 Disks supported
Front drive bays: Up to 16 x 2.5” SAS/SATA/SSD, Up to 8 x 3.5” SAS/SATA,
7 RAID Controller
12Gbps PCIe 3.0 with RAID 1, 5, 6,10, 50
8 Disks configured
2nos. Of 1TB SSD
9 DVD writer DVD RW
10 I/O slots Up to 8x PCIe Gen3 Slots
11
GPU
Server should be configured with 1no. Of Nvidia V100, 32 GB GPU & should support Upto 3 DW and 6 SW GPU cards
12 Ethernet ports
4 x 1G RJ45 LOM
13 Certification and compliances
Microsoft Windows Server, Hyper-V, VMWare, Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES)
14 Power Supply
Platinum rated redundant Power Supply
15 SD Modules slots
Dual SD Module slots supporting redundant configuration
16 Management integration
Support for integration with Microsoft System Center, VMware vCenter, BMC Software
17 Power & temperature
Real-time power meter, graphing, thresholds, alerts & capping with historical power counters.
111
18 Power & temperature
Temperature monitoring & graphing
19
Pre-failure alert
Should provide predictive failure monitoring & proactive alerts of actual or impending component failure for fan, power supply, memory, CPU, RAID, NIC, HDD
20
Configuration & management
• Real-time out-of-band hardware performance monitoring & alerting • Agent-free monitoring, driver updates & configuration, power monitoring & capping, RAID management, external storage management, monitoring of FC, HBA & CNA & system health • Out-of-band hardware & firmware inventory • Zero-touch auto configuration to auto deploy a baseline server configuration profile • Automated hardware configuration and Operating System deployment to multiple servers • Zero-touch repository manager and self-updating firmware system • Virtual IO management / stateless computing • Support for Redfish API for simple and secure management of scalable platform hardware
21
LCD panel
Should display system ID, status information and system error error code followed by descriptive text. LCD background should light up in different colours during normal system operation & error conditions.
22 HTML5 support
HTML5 support for virtual console & virtual media without using Java or ActiveX plugins
23
Server security
Should have a cyber resilient architecture for a hardened server design for protection, detection & recovery from cyber attacks Should protect against firmware which executes before the OS boots Should provide effective protection, reliable detection & rapid recovery using: - Silicon-based Hardware Root of Trust - Signed firmware updates - Secure default passwords
112
- Configuration and firmware drift detection - Persistent event logging including user activity - Secure alerting - Automatic BIOS recovery - Rapid OS recovery - System erase Configuration upgrades should be only with cryptographically signed firmware and software Should provide system lockdown feature to prevent change (or “drift”) in system firmware image(s) & prevent malicious modification of server firmware
24 Intrusion alert
Intrusion alert in case chassis cover being opened
25 Warranty
3 years On-site comprehensive warranty with 24x7x365 remote hardware support.
5.2.11.2 Rack Servers
S.No Item Parameter and Minimum Specification
Compliance (Yes/No)
Offered Specification with Document Proof
1 Chipset Lewisburg PCH Intel C621 or Equivalent
2 Form Factor Max. 2U rack mounted with sliding rails
3 Configured CPU
Dual Intel® Xeon® Scalable processors, (To be populated with min Gold 6152 to Gold 6252 --- (2* intel 6252 2* Intel® Xeon® Gold 6252 2.1G, 24C/48T, 3UPI, 35.75M Cache))
4 Memory slots 16 DDR4 DIMM slots, speed up to 2666MT/s
5 Memory configured
512 GB upgradable to 1 TB
6 Disks supported
Front drive bays: Up to 12 x 3.5” SAS/SATA HDD Rear drive bays: Up to 2 x 3.5 SAS/SATA HDD
7 RAID Controller
12Gbps PCIe 3.0 with RAID 1, 5, 6,10, 50 with 8 GB Cache on a single controller
8 Disks configured
Hot pluggable SAS HDD 2x600 GB, 10K RPM or higher
9 DVD writer DVD RW
113
10 I/O slots Up to 5 Gen 3 PCIe Slots
11 Ethernet ports Min 2 x 10G SFP+ Ports and 2 x 1 G Ethernet Ports
12 Certification and compliances
Windows Server 2016, VMWare, Red Hat Enterprise Linux, SUSE Linux Enterprise Server
13 Power Supply Upto 1100W Platinum rated redundant Power Supply
14 Management integration
Support for integration with Microsoft System Center, VMware vCenter, BMC Software
15 Power & temperature
Real-time power meter, graphing, thresholds, alerts & capping with historical power counters. Temperature monitoring & graphing
16 Pre-failure alert
Should provide predictive failure monitoring & proactive alerts of actual or impending component failure for fan, power supply, memory, CPU, RAID, NIC, HDD
17 Configuration & management
• Real-time out-of-band hardware performance monitoring & alerting
• Agent-free monitoring, driver updates & configuration, power monitoring & capping, RAID management, external storage management, monitoring of FC, HBA & CNA & system health
• Out-of-band hardware & firmware inventory
• Zero-touch auto configuration to auto deploy a baseline server configuration profile
• Automated hardware configuration and Operating System deployment to multiple servers
• Zero-touch repository manager and self-updating firmware system
• Virtual IO management / stateless computing
• Support for Redfish API for simple and secure management of scalable platform hardware
18 LCD panel Should display system ID, status information and system error error code followed by descriptive text. LCD
114
background should light up in different colours during normal system operation & error conditions.
19 HTML5 support
HTML5 support for virtual console & virtual media without using Java or ActiveX plugins
20 Server security Should have a cyber resilient architecture for a hardened server design for protection, detection & recovery from cyber attacks Should protect against firmware which executes before the OS boots Should provide effective protection, reliable detection & rapid recovery using:
• Silicon-based Hardware Root of Trust
• Signed firmware updates
• Secure default passwords
• Persistent event logging including user activity
• Secure alerting
• Automatic BIOS recovery
• Rapid OS recovery
• System erase
• Dynamically enabled USB Ports,
• Chassis Intrusion Detection
• System Lockdown
• System Drift Detection Configuration upgrades should be only with cryptographically signed firmware and software
21 IPV 6 compliance
The Hardware should be IPV 6 Compliant ready
22 OS Windows server Standard Edition (latest version)
23 Certification CE, FCC, UL, RoHs
5.2.12 Storage and Backup
The minimum Storage requirement for the TMMC project is as below:
S. No Minimum Storage Requirement TB 1 Surveillance Storage (RAW Space) 1000 2 Application Storage (RAW Space) 40 Total 1040 The proposal should adhere to the following minimum eligibility criteria of Storage OEM:
• OEM of Storage have its own service centre in India and should have a Toll free number
115
• OEM or Manufacturer should be ISO 9001, ISO 14001 and ISO 27001 certified.
• OEM or Manufacturer of the offered goods/ equipment’s should be a company
registered under the companies Act since last 5 years in India. Valid company registration
certificate should be submitted
• Proposed Storage device model should be supplied and working in minimum 10 locations
at any government department in India
S.No Feature Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 Data storage
Data storage Configurable 19” rack mountable each 3U chassis 6Gb SAS NAS and iSCSI target device Network attached storage/FC ISCSI solution for a flexible and expandable solution Storage device should not be more than 16 bays and Raid 6 should to be configured within 16 bays including one hot spare Only one additional Enclosure can be added with each Storage device with maximum of 16 Bays, Same Raid 6 to be configured and together Raid 60 Need to be configured in 32 Bays max including 2 Hot spares
2 Hard disk Through put
Supports 6Gbps & 3Gbps SAS & NLSAS Hard drives simultaneously
3 System Log Supports SNMP/email notification and auto system log information from USB port
4 ISCSI management
Overall storage system should support minimum 300 TB via single ISCSI
5 Power Supply
The Primary device and additional enclosures also should be with dual controller cards and N+1 Redundant power supply (minimum 3 Power supply to be loaded on each physical hardware)
6 Fan Module 1 or more rear redundant hot swappable Fans, Internal environmental status monitoring"
7 RAID support System can support Hardware RAID levels 0,1,10,3,5,6,30,50,60.
8 Battery Backup
Battery Backup Unit Support for power shortage
9 Storage Parameter
Smart Bad Sector Remapping during Raid Storage (during inactive periods
116
and automatically remaps bad sectors), S.M.A.R.T Hard disk Error Handling
10 Hard disk Power
Support NVRAM Check and log errors, Hard Disk Power input Control, Write-hole Table Protection for video footage and Read/write check
11 Controller cards
Loaded Dual controller cards, The controller cards should work as Active/Active mode and Active/ Passive mode.
12 CPU and Data Cache
Support 64 bit 4 core or better CPU support. DDR3/DDR4 64G data cache Loaded on Each System.
13 Virtualization Virtualization features support like VMware, Citrix, Hyper-V and Data Core
14 Network interface
Should have minimum of 4x10 Gbe or 4 x 10 G SFP+ or 4x16Gb FC Host ports.
15 Network Features
Networking support for NIC Trunking/load balance/fail over/802.3ad, DHCP server/DHCP client, WINS server and Internet gateway.
16 Network Protocol
Protocol support for TCP/IP, SMB/CIFS, NFS, SNMP v1/v2c/v3, FTP, HTTP, HTTPS, Telnet, SSH, AFP, WebDAV. Support OS for 2003 / Vista /2008, Unix / Linux and Mac
17 User Accounts
User accounts Microsoft Active Directory Authentication, Network Information Service, Batch creation of users/group, user quota management, share level and file level security with access control list setting.
18 Session Support
Up to 100K domain account support, up to 1K concurrent sessions support
19 Security
Security and data protection Support like online Raid level migration/reconfiguration, online volume copy, Advance Battery Flash Backup
20 Web Management
Device Management through Web-based Management, Web client support: IE 7 or above, Mozilla Firefox, safari, Google Chrome
21 Notification Support Buzzer, LED, Mute Button, Power Button
22 File System File system and backup Supports User database and Configuration Backup.
117
23 Backup/ Restore
Backup Server, Share Disk Clone, Remote Replication, Online Recovery, File Backup/Restore
24 Surveillance Management
Application Mode like Surveillance Buffer Management support and benefit for more cameras supported, Less Frame Drop and Sequential Design Recording
25 Operating temperature
0 ~ 50 or better
26 Certifications CE, FCC, UL, ROHS
5.2.13 Backup Software
S.No Features Compliance (Yes/No)
Offered Specification with Document Proof
1
Proposed backup software should be available on various OS platforms like Windows, Linux, HP-UX, IBM AIX, Solaris etc. The backup server should be compatible to run on both Windows and Linux OS platforms
2
The backup software should be able to encrypt the backed up data using 256-bit AES encryption on the backup client and should not demand for additional license, any such license if needed should be quoted for the total number of backup clients asked for.
3
The backup solution should also support online LAN Free SAN based backups of databases through appropriate agents; Important Applications being Oracle, Microsoft SQL Server, Exchange, SharePoint, IBM DB2 UDB, Informix, Lotus Notes/Domino, MySQL, SAP, SAP HANA & Sybase etc.
4
Should able to dynamically break up large savesets into smaller savesets to be backed up in parallel to allow backups to complete faster for Windows, Unix and Linux clients.
5
Should have in-built calendar based scheduling system and also support check-point restart able backups for file systems. It should support various level of backups including full, incremental, differential, synthetic and virtual synthetic backups
118
6
The proposed backup software should have the capability to enable WORM on the backup sets from the backup software console on proposed disk backup appliance
7
The solution must support client-direct backup feature for file system, applications and databases to reduce extra hop for backup data at backup/media server to cater stringent backup window.
8
Should integrate with third party VTL which has data deduplication capabilities. Backup software must support Robotic/automated Tape library, the licensing of such library should be on the unlimited number of slots and not on the drive counts as additional drives are added to improve performance. Must support OST, VTL, Disk, NFS. CIFS for proposed backup disk appliance
9 Must support source capacity based licensing and host based licensing as well.
10 System should provide Socket based license for VM Ware ESXi or MS Hyper V or Host for RHEV/KVM or Fronet end capacity based licenses
11
Must have Agent/Modules for online backup of applications and databases such as MS SQL, Oracle, Exchange, Lotus, DB2, Informix, Sybase, Sharepoint, Meditech and SAP. Must support NAS and storage array based snapshot backup for off host zero downtime and zero load on the primary backup client with wizard based configuration.
12
Backup Solution must support multi tenancy feature for creation of distinct data zones where the end users have access without being able to view data, backups, recoveries, or modify in other data zones.
13
Backup Solution should also have configurable ReST API support for management, administration and reporting on backup infrastructure via custom applications and out of box integration with Automation Solution for complete orchestration
14
The proposed backup software should support restore a single VM, single file from a VM, a VMDK restore from the same management console for ease of use.
15
Proposed backup software should not need a physical proxy server for backups and should have a minimum of 16 concurrent sessions capability for the VMs image based backups with single virtual proxy. It should support instant access of a VM.
119
16
The proposed solution should have inbuilt feature for extensive alerting and reporting with pre-configured and customizable formats. The proposed solution must have capability to do trend analysis for capacity planning of backup environment not limiting to Backup Application/Clients, Virtual Environment, Replication etc.
17
The proposed backup software should be able to recreate backed up data from existing volumes from metadata backups. The solution should offer recovery of specific volumes for recovery from metadata in case of a disaster recovery.
18
The proposed Backup software should have the capability for Block based backups with granular recovery capability for Windows, Linux, Hyper-V, VMWARE and Exchange for faster backups on supported Disk platforms.
19
The proposed backup solution should provide search capability from a web portal to allow search for a single file from complete backup store
20
The solution should be capable of integration with active directory infrastructure for ease of user rights management along with role based access control to regulate the level of management
21
The solution should have the capability to manage and monitor backups at remote locations from a single backup server, where clients can backup data to a local disk backup device without the need of local media server or sending primary backup copy over the WAN
22
The solution should have the capabilities to backup as well as archive data to cloud with cloud service providers like Azure / Amazon etc. In addition to this if data has to be moved from Cloud A to Cloud B the solution should be capable of cloud portability.
5.2.14 Unified Management
S.No Feature Specification Compliance (Yes/No)
Offered Specification with Document Proof
1. Automation Solution should provide automation and orchestration solution for automated delivery of IaaS, PaaS, XaaS/ SaaS services for Smart City applications so that when VM/app is created it should automatically
120
get the required virtualized compute, storage, switching, routing, firewall, load balancing services without any manual intervention. All compute, network, storage, security, load balancing policies must follow the life cycle of VM and movement within and across DC & DR.
Unified management solution should be provisioned for complete applications and database layer in the datacenter (including surveillance, analytics solutions etc ).
2. Policy defined Infrastructure
Solution should be built using programmable & policy defined infrastructure components which should be independent of underlying hardware components and use standard x86 servers, storage, switches from any OEM make and model, Solution should provide for creation of complete application blueprint along with required virtual networking (such as routing, load Balancing) and security services for the application using a user-friendly graphical interface by using a drag and drop functionality.
3. Auto-scale Solution must provide auto scale so that in case of increase in load/connections/users. additional VMs should be automatically created with all network, security and load balancing policies. Integration required from cloud portal, orchestration, virtualization, virtual network, security and load balancing should be done to achieve this functionality.
4. Operations & Management
Solution must provide cloud operations layer integrated with automation layer which provides proactive monitoring, alerts, management, capacity planning, performance management and predictive analytics capabilities for automatically initiate corrective measures.
Solution should learn the environment behavior and based on usage patterns, pre-emptively rebalances workloads in advance of upcoming demands and spikes and it should provide integrated smart alerts for health, performance and capacity degradation to identify building performance problems before they affect
121
end users
5. Monitoring Solution should monitor utilization of running VMs and should reclaim resources from idle VMs and allocate to other VMs in automated fashion. The solution capacity analytics should provide "What If" scenarios to eliminate the need for spreadsheets, scripts and rules of thumb to eliminate time-consuming problem resolution processes through automated root cause analysis Solution should provide automated workflow triggers which would let admins associate workflows created in Orchestrator layer with Operations alerts. For example, these workflows can automatically delete old VM snapshots when available capacity falls below a critical threshold or add resources when workload demands are rising above normal. Automated workflows help reduce Mean time to incident (MTTI) and mean time to resolution (MTTR)
Solution shall support management of the machine life cycle from a user request and administrative approval through decommissioning and resource reclamation with dynamic capacity management and it should collect and analyze all types of machine-generated log data, for example, application logs, network traces, configuration files, messages, performance data and system state dumps.
6. Dashboard & Reporting
Solution should provide monitoring and management of complete virtualized infrastructure with prebuilt and configurable operations dashboards to provide real-time insight into infrastructure behavior, upcoming problems, and opportunities for efficiency improvements.
Solution should provide comprehensive flow assessment and analytics and security groups and firewall rules suggestion for the purpose of implementing a zero-trust security within the data-center also should be able to report the amount of East-West, North-South, Internet, virtual machine to virtual machine, virtual machine to physical
122
traffic within the datacenter
5.2.15 Server Virtualization
S.No Feature Specification Compliance (Yes/No)
Offered Specification with Document Proof
1. Bare Metal Solution
Sits directly on the bare metal server hardware with no dependence on a general-purpose OS for greater reliability & security
2. Guest OS Support
Heterogeneous Guest OS support and certification for namely Windows, Red hat & SUSE Linux Enterprise (SLES). This support and certification should be from OS as well as hypervisor vendor public listed.
3. VM Live Migration
Live Virtual Machine migration between different generations of CPUs in the same cluster and without the need for shared storage option and long distances from one site to another (up to 150 milliseconds round trip time) with no disruption to users or loss of services, eliminating the need to schedule application downtime or business downtime.
4. Storage Live Migration
Live migration of VM disk from one storage array to another without any VM downtime. Support this migration from one storage protocol to another eg: FC, NFS, iSCSI, DAS.
5. High Availability
• Proactive High availability capability that utilizes server health information and migrates VMs from degraded hosts before problem occurs Migration of VMs in case one server fails all the Virtual machines running on that server shall be able to migrate to another physical server running same virtualization software.
• It should support affinity and anti-affinity rules to set constraints that restrict placement of a virtual machine to a subset of hosts in a cluster and to keep virtual machines paired or separated. The solution should have single reboot to dramatically reduce the upgrade times by
123
skipping a host reset and also help to reduce patching and upgrade times by rebooting the hypervisor without rebooting the physical host, skipping time-consuming hardware initialization
6. Always Available
• Zero downtime, Zero data loss and continuous availability for the applications running in virtual machines in the event of physical host failure, without the cost and complexity of traditional hardware or software clustering solutions.
7. Resource Addition
• Add CPU, Memory & devices to virtual machines on the fly when needed, without disruption or downtime of working VMs for both windows and Linux based VMs.
8. Resource Scheduler
• Create a cluster out of multiple storage datastores and automate load balancing by using storage characteristics to determine the best place for a virtual machine’s data to reside, both when it is created and when it is used over time.
9. Security • VM-level encryption with no modifications in guest OS to protects unauthorized data access both at-rest and in-motion and also provides secure boot for protection for both the hypervisor and guest operating system by ensuring images have not been tampered with and preventing loading of unauthorized components.
• Integration of 3rd party endpoint security to secure the virtual machines with offloaded antivirus, antimalware, firewall and hips solutions without the need for agents inside the virtual machines.
10. Storage support
• Support boot from iSCSI, FCoE, and Fibre Channel SAN. Integration with Storage API's providing integration with supported third-party data protection, multi-pathing and disk array solutions.
11. Virtual Switch
• Span across a virtual datacenter and multiple hosts should be able to connect to it. This will simplify and enhance virtual-machine networking in virtualized environments and enables those environments to use third-party distributed virtual switches.
• In-built enhanced host-level packet capture tool which will provide
124
functionalities like SPAN, RSPAN, ERSPAN and will capture traffic at uplink, virtual switch port and virtual NIC level. It should also be able to capture dropped packets and trace the path of a packet with time stamp details.
12. VM based Replication
• Efficient array-agnostic replication of virtual machine data over the LAN or WAN. This Replication should simplify management enabling replication at the virtual machine level and enabling RPOs as low as 240 minutes.
13 Performance
Support for persistent memory, exposing it as block storage or as memory, to enhance performance for new as well as existing apps Should be able to dynamically allocate and balance computing capacity across collections of hardware resources aggregated into one unified resource pool with optional control over movement of virtual machines like restricting VMs to run on selected physical hosts.
• Should support network and storage QoS to ensure performance on per VM basis
14 Quick reboot
Should provide quick reboot and reduce patching and upgrade time by rebooting the hypervisor without rebooting the physical host, skipping time- consuming hardware initialization.
15 Disaster Recovery Automation
• Solution should provide DR automation solution delivered from virtualization manager console for automated failover, failback and recovery of application VMs in proper sequence to other data center with single click Solution should provide solution to perform non-disruptive DR drill/testing of recovery plan for full and selected applications every six months without impacting production applications running in primary environment.
16. Operations Management
• It should include proactive smart alerts with self-learning performance analytics Capabilities with Prebuilt and configurable operations, customized dashboards to provide real-time insight into infrastructure behavior, upcoming problems, and opportunities for efficiency improvements.
125
• Capacity analytics which can identify over-provisioned resources so they can be right-sized and "What If" scenarios to eliminate the need for spreadsheets, scripts and rules of thumb, as well as Real-time, integrated dashboards of performance and capacity to enable a proactive management approach and help ensure SLAs are met
• Automated workflow triggers which would let admins associate workflows created in Orchestrator layer with Operations alerts. For example, these workflows can automatically delete old VM snapshots when available capacity falls below a critical threshold or add resources when workload demands are rising above normal.
• Solution should provide monitoring of OS level resources (CPU, Disk, Memory, Network) for windows and Linux OS and physical hardware resources of the host.
5.2.16 Video Wall, Video wall Management software and Controller
5.2.16.1 Video Display Wall
S. No Feature Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 Screen Size (Diagonal)
Video wall in a 4x3 arrangement, Screen Size – 50” Diagonal Laser DLP ” Each screen (Total 12 Screens)
2 Aspect Ratio 16:9
3 Viewing Angle Half Gain
(H) +- 34 (V) +_31
4 Resolution (H X V)
1920 X 1080 or better per cube
5 Brightness & Contrast
2200 Lumens & 1800:1
7 Response time 8 ms
8 Panel Surface Treatment
Anti-Glare
9 HDMI In HDMI X 1
10 DVI-D In DVI-D 24-Pin X 1
11 DVI-D Out DVI-D 24-Pin X 1
12 Control IR remote Control
13 Cube Depth Less than 460 mm
14 Power Supply Dual Redundant Hot swappable power supply built inside the cube. External redundant power supplies
126
not acceptable
15 Bezel Width 0.2 mm or better
16 Access Rear Access
17 Light source type
Laser
18 Power Requirement
100V ~ 240V, 50-60 Hz
19 Power Consumption
350W or Lower per cube
20 Stand-by Condition
≤0.5 W or better
21 Bezel Width (Bezel to Bezel)
0.2 mm or lesser
22 Operation 24/7 Continuous working Life time - 50,000 hrs (min.)
23 Casing Full Metal Rear Cover
24 Orientation Landscape
25 Operating Temperature
5ᵒC ~ 35ᵒC
26 Operating Humidity
20% ~ 85% RH Non-Condensing
27 Accessories Equipped with all accessories including base stand
5.2.16.2 Push / Pull Type Video Wall Mounting Kit
S.No Feature Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 General Specification • Base Stand with front cover
2 Height • As per site requirement
3 Curve • As per site requirement
4 Finish • Black powder coated
5 Height adjustment • +/- 50mm
5.2.16.3 High-performance Video wall controller
S.No Feature Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 General Specification
Should have 16 HDMI input ports and 16 HDMI output ports Connects any of 16 video sources to any 16 displays in any combination Support 4 K resolution on each 16 HDMI input and 16 HDMI output ports Should able to customize video wall
127
matrix/layouts from GUI, Support HDCP 2.2 High-performance matrix switcher for HDMI signals. It reclocks and Equalizes the signal and can route any input to any or all outputs simultaneously. 16 X 16. Data Rate — 6.75Gbps (2.25Gbps per graphic Channel). 4K 3840 x 2160 @30Hz (4:4:4) Configuration of the complete system via a graphical Interface, Administrative Control, Deliver the screen wall Management software as described before including all required licenses and install it ready for Operation on the server of the large screen wall, Control of the windows on the large screen wall from Control and observation computers Should have internal scalar for seam less real-time switching
• Video wall controller quantity to be added based on site or solution requirements
5.2.17 Video Management System and Video Analytics
S.No Video Management System for recording and viewing of all types of proposed cameras
Compliance (Yes/No)
Offered Specification with Document Proof
1 License for all cameras should be provided. provision to upgrade the license of unlimited cameras in future
2 Requirement.
Add camera, delete camera, View, record, playback, fast forward, rewind, time based recording, manual recording, user group creation, time stamp watermarking in the video, camera labeling in the video footages, snapshot in live and recorded videos, camera bookmarking, export video clips in to a playable video format in VLC, export video clips to pendrive and DVD writer, Microsoft video players and other popular video players, system status, alarms, alarm log, support of third party analytics, remote clients (25 numbers) through laptop, desktop, tablet etc.,, mobile clients ( 25 numbers)
3 Should have high level of network security. Hacking of the video footages through VMS should not be happened at any cost. The tenderer will take adequate measures by installing antivirus and
128
periodic security audit of the video management system to protect the system against hacking and all possible best practices must be adopted.
4 The VMS should be an enterprise class (or higher) open platform IP- enabled software solution. It shall support the seamless unification of remote IP video management systems & Third Party Systems like Video Analytics and Video / Voice Communication from control room
5 The VMS should support industry standard for the interface of IP-based physical security products, ONVIF profile- S and should be based on a server/client model. The Software must be able to adopt on any COTS based Server / machine
6 The VMS Should offer a complete and scalable video surveillance solution which allows cameras to be added on a unit-by-unit basis. The database shall support more than 25000 cameras / IP end points in a single Hardware machine
7 To minimize network traffic, the VMS must have the ability to manage multi-cast directly from the camera. VMS Shall supports dynamically switch the video resolution according to the size on Monitoring Screen. High Resolution Video feed while watching single camera on screen and Low Resolution Video feed while watching Cameras in Multiple views depending on the number of viewing size
8 The client applications should support any form of IP network connectivity including: LAN, WAN, VPN, Internet, Wi-max and Wireless. The client applications shall support IP Multicast and Unicast, UDP video and audio streaming. However the preferred video streaming is Multicasting. The proposed VMS solution should have open standard IGMP, PIM-SM, PIM-DM for both IPv4 & IPv6
9 The VMS should allow configuring – discovery on IP network and set IP Address, Frame Rate, Resolution, Motion detection within camera or server based, Bit Rate, Key frame interval, Digital I/O, Audio Inputs/Outputs, Ability to update firmware of IP camera or encoder. Any of these configuration changes do not require the server services to be Restarted.
10 Each camera’s will be set independently from other cameras in the system, and altering above settings of one camera will not affect the recording and display settings of other cameras.
11 The VMS must have built-in Failover / Redundancy Feature with hot stand-by for the management & recording servers (including geographical redundancy if required in the future).
12 The Fail over Server should be on hot standby, ready to take over during the primary server fails. The failover and retrieval should occur without any disruption to the monitoring client and recording. No manual action from the user shall be required
13 It should be a fully distributed solution with centralized management, requiring 24/7 surveillance with support and unification for devices from different vendors
129
14 Software shall also provide the ability to monitor system centrally, events, alarms, systems status and health issues of devices and servers from single console.
15 VMS should support multicast and multi- streaming
16 The VMS installed in the server should be able to intelligently scan and detect new cameras and other IP enabled devices automatically when connected to the network.
17 The VMS shall incorporate Matrix functionality for distributed viewing of Cameras
18 VMS should have PTZ camera controls, ROI, Motion detection and other edge analytics supported by the camera, play, pause, stop, Video crop and export, play back for all cameras. Video search by date, time, Channel,
19 The VMS system administrator shall have privileges to add/delete/configure users with rights. It should be possible to view the privileges of each client or the cameras which can be viewed / controlled by each client. It should also be possible to add/delete cameras and other IP devices, configure cameras, assign priorities to users, configure alarm etc
20 The VMS should be compatible to single and multiple processor servers and should support virtual servers.
21 The VMS should support H.265, H.264 and MJPEG compression formats for the video stream from all IP cameras connected to the system.
22 All the recorded video footages should have time and date water marking. The System shall ensure that time and date for once recorded video cannot be tampered.
23 In case of Network Failover and if the camera have the capability to store the video locally (in a memory card) the stored video in the camera memory card should be archived to fill the gap in the control room Recorder
24 The VMS should provide a documented Software Development Kit (SDK) to allow integration with other application software/ in-house custom development of the Police Department.
25 The system should maintain a alarm stack (Audit trial) for the complete system, which should include events detected in network loss, video loss etc.
26 The VMS should allow the clients for seamless operation of all cameras. Software should allow the client applications to interact with all the camera and other IP enable devices simultaneously and allow simultaneous display of live video/recorded video
27 VMS/ Client should support manual recording, time based recording, motion detection based recording etc. VMS should allow bookmarking of video footages for analysis.
28 VMS should pull the video from camera SD card, incase of any link failure and restored at TMMC/field location then the missing video files should be retrieved form SD card and copied
130
to storage device.
29 Should support keyboard, mouse and joystick operations Should support integration of third party video analytics.
30 Should support remote view in a web client through Computer, laptop and Mobile phones (android, IOS etc)
31 The VMS should be capable of supporting the attachment of external storage devices like NAS as per the scope of the project. The VMS should be capable of supporting SAS, iSCSI or Fibre Channel interfaces.
32 Cyber Security:
i) The proposed software should support end to end encryption Server to Server and Server to Client, additionally the recorded video at the storage can be in encrypted form to avoid any cyber attack.
ii) The Proposed software shall be an IP enabled solution. All communication should be based on standard TCP/IP protocol and shall use TLS encryption with digital certificates to secure the communication channel.
iii) The proposed application should support end to end encrypted streams with cameras supporting Secure RTP (SRTP) both in unicast and multicast from the camera
33 The VMS should have a GIS map (online) of Jammu City.
i. The GIS map consists of important spots like all Police Stations, hospitals, important Government offices, public places, Educational institutions, defence areas, beaches/rivers, religious places, shopping areas and other important locations as demanded by tenderer on time-to-time.
ii. The VMS OEM should be ISO 9001, 14001 and 27001 Certified, The OEM should have minimum 3 direct offices in India The OEM should have Toll Free in India
iii. The VMS OEM and IP Camera OEM should be of Same Make, incase the VMS OEM is different from IP camera OEM then the VMS OEM should submit an complete test report of all the specification of VMS software integrated with Quoted camera model and tested by an UL or EAL LAB at the time of Bidding.
Video Analytics
S.No Required Parameter Compliance (Y/N)
Offered Specification with Document Proof
1 The video analytics (VA) shall be of repute and can be an integrated with VMS OEM.
2
The Video Analytics (VA) shall be designed to provide Intelligent Video Analysis for 24/7 surveillance with support for 3rd party devices. It shall be capable of Learning scenes automatically
3 The Video Analytics (VA) shall be designed to provide Intelligent Video Analysis for 24/7 surveillance with support for 3rd party devices. It shall be capable of Learning scenes
131
automatically
4
The VA shall allow each camera to have 40 detection zones that are polygonal with a variable number of vertices so that any shape can be supported. Detection zone can also be a line, which can have one or many segments. The VA shall be flexible to use Rule based Analytics in any fixed camera in the project and shall provide with floating license for the particular server.
5 The VA configurator shall have easy to use graphical user interface with live alarms list for easy parameter fine tuning and feedback.
6 The VA alarms shall be recorded in the VMS similarly like other alarms, for example motion detection, audio detection and digital input alarms.
7 The VMS shall store the VA alarm video and image files for export
8 The VA shall support video from any camera supported by the VMS.
9 The VA shall support cameras using any of the video compression formats H.265/H.264/MPEG4/MJPEG.
10
The VMS shall support scheduling so that that VA alarms can be enabled or disabled for a certain period of time. The VA software shall be able to run at least 4 different types of analytics in one single camera.
11 The VA shall support ONVIF enabled cameras, The VA Shall support RTSP/RTMP
12 Analytics proffered on the edge
• Face Detection
• Crowd detection
• Intrusion detection
• Trip wire detection
• Missing object detection
• Object counting
• Tampering detection
13 Analytics preferred on the Command center
• Helmet detection
• Triple riding detection
• Loitering detection
• Wrong way detection
• Left baggage /abandon baggage
132
5.3 Integrated Data Centre infrastructure
S.No Specifications Compliance
(Yes/No)
Offered
Specification with
Document Proof
1 This specification covers intelligent integrated/inbuilt
infrastructure, standalone system design, engineering,
manufacture, assembly, testing at manufacturer’s
works, supply, delivery at site, unloading, handling,
proper storage at site, erection, testing and
commissioning at site of complete infrastructure for the
proposed Data Centre to be installed by SI as per
detailed specification, complete with all accessories
required for efficient and trouble free operations.
2 The detail specifications of the intelligent
integrated/inbuilt infrastructure, standalone system
shall be in adherence to data center guidelines thus
shall be composed of dual active power and cooling
distribution paths, but only one path active. Shall have
redundant components
3 The Intelligent Integrated Infrastructure essentially
includes internal redundant or backup power supplies,
environmental controls (e.g., precision air conditioning,
fire suppression, smoke detection, Water leak
detection, humidity sensor etc), security devices etc.
Critical systems like UPS and Precision Air-conditioning
system will have N+N topology respectively.
4 The Intelligent integrated infrastructure shall be having
foot print approximately 17 Sq. Mtr which shall have
min 117 U usable space (min 6 racks), to accommodate
IT and network equipment & devices. This footprint
should include separate panel housing fire suppression
and power distribution preferably.
5 The Intelligent integrated infrastructure would provide
many functionalities and some of the key functionalities
are Cold Contained Front Aisle & Rear Contained Hot
Aisle, insulation, remote management and single point
of service.
The Intelligent integrated Infrastructure shall have following components: -
133
1 Precision Air conditioner with variable capacity cooling,
heater and humidifier to cater IT load approximately 40
KVA and in N+N topology for total 6 racks.
2 2x 30 KVA – 2 Sets rack mount UPS with P.F. up to 0.9 &
efficiency more than 92% ~94% - 2 numbers. There should
be 20 min battery back-up. UPS & Battery should be
mounted inside the cabinet only. Novec 1230 Gas based
fire suppression system as per NFPA guidelines
Smoke detectors, water leaks detection system,
temperature & humidity sensor, door sensor, and alarm
beacon. 42 U racks
Monitoring system – capable for Email alerts
1 Biometric access control system which should be control
by access control panel.
2 32A Vertical Rack mount PDU of type IEC C13 & IEC C19
combination, each rack shall have two such PDU’s.
Electrical system with essential MCB/MCCB.
3 Intelligent integrated infrastructure would have provision
to add an extra rack in future. It should be flexible,
adaptable, controllable infrastructure.
5.3.1 Uninterrupted Power Supply (UPS) System
S.No Parameter Minimum Specifications
Bidder Compliance (Yes/No)
Product Documentation Reference
1
System Configuration
Each 30 KVA Online UPS shall have Modular design & feature of Hot Swap ability with 15 or 20kva module (no small rating module acceptable). THDi less than 3%. The UPS Rack shall also be Scalable to min. 80kva in complete capacity at site. Module shall be with full rated rectifier, inverter & charger.
2 Technology
True On-line, double conversion type. Inbuilt Isolation Transformer is required in the UPS Cabinet itself
3 Input Source Mains/Local DG Set Compatibility
4 Input Voltage 415 VAC 3 phase, 4 wires
5 Input Voltage Tolerance
315 to 475 VAC
6 Input Frequency 50 Hz
7 Input Frequency 45 HZ TO 55 HZ
134
Tolerance
8 Input Power Factor
>0.99 (at nominal voltage and full load)
9 Total Harmonic Distortion at 100%
< 3% for linear load
10 Output Voltage 415 VAC 3 phase, 4 wires
11 Output Voltage Regulation
± 1% for 100% static load, ± 1% for 100% balanced load, ± 1% for 100% un-balanced load. THDU < 3% between Phase to Neutral for 100% non-linear load
12 Output Power Factor
0.8 or higher ( for 0 to 40 deg C operation)
13 Over Load Rating
125% for 10 minutes; 150% for 60 seconds (or better)
14 Inverter Efficiency
> 92%
15 Overall efficiency(without transformer in ckt)
> 93% (Eco mode efficiency shall be 97%)
16
Static Bypass switch
A Built-in static transfer switch shall be provided as an integral part of the UPS. The Static switch shall be a bi-directional naturally committed high-speed static (SCR type) device rated to carry full load current continuously.
17
Manual Bypass switch
The UPS should have a Built-in Maintenance Bypass Isolator to directly connect the load to the input AC power source, bypassing the rectifier, inverter and static transfer switch.
18 Battery type
Sealed Maintenance Free with a separate Battery Rack
19 Battery make Exide / Rocket / Quanta / Leoch / Amaron
20 Backup
30 minutes backup on full load (Min VAH = 40000)
21
Battery management
The UPS should have Battery Management feature for:
Periodic Battery Test
Controlling Charging Time and Current
Increase in Battery Life
Protection : Battery low Cut-off without draining current
-Charger capacity shall be min. 10% of the Ah of the battery being offered
135
22
LCD Panel & LED indications
The UPS should have LCD panel for measuring Output voltages, Output currents and Frequency, Battery Voltage/Amp, display status of the battery capacity and backup time left and event logging (record 500 event, built-in SRAM). LED indicators for operation in Normal / Battery / Bypass / Fault
23
Interface RS232 interface to be provided. Total six programmable dry contact outputs & two smart slots
Power Management Software
The UPS should have Power management software and interface cable, providing complete power monitoring and control capabilities to system administrators.
24
SNMP Card
Should come with an SNMP Card for connecting UPS to Ethernet LAN to monitor and manage the UPS with a standard Web browser.
25
Synchronization
The UPS should come with hardware/software required to provide Synchronization capability between the outputs of two or more independent UPS systems.
26
Protection(MCB)
Input Protection Circuit Breaker; Bypass Input Protection Circuit Breaker; Manual Bypass Protection Circuit; Output Protection Circuit Breaker
27
Product (IEC/EN) Standards
- CE Certificate - EN 62040-1-2
5.3.2 Rack & Accessories
S.No Specifications Compliance (Yes/No)
Offered Specification with Document Proof
1 Supply and installation of high density 42 U height, Rack with Integrated cold aisle & hot aisle containment frame, with basic rack accessories.
2 Total 04 Nos. of Racks to be supplied along with each Integrated Data Centre infrastructure
3 Rack & Accessories Technical Specification:
4 Rack Containment Frame is 42 U, 19'' mounting type with 2200 (Height) x 600 (Width) x 1800 (Depth, including Rack + Cold & Hot Aisle Containment).
5 Rack frame is, scalable and modular with safe load carrying capacity of 1000 Kg.
6 Each Rack should 4# of have digital PDU with minimum 10# of 5/15 Amps socket. Should have surge protection and MCB
7 Base plinth with 100 mm height.
136
8 Cable entry provision from top & bottom both side of rack.
9 Cut outs with rubber grommet on top and bottom cover of rack for cable entry.
10 Vertical Cable manager on both LHS & RHS on rear side.
11 Front & Rear glass door for complete 42U height visibility.
12 Thermally insulated cold aisle chamber.
13 Blanking panels to prevent air mixing.
14 Fixed Shelf to be provided.
15 Plastic Cable duct on vertical LH & RH section of racks for cable routing.
16 Front Rack doors are provided with Biometric Access Control with 02 nos. of Electromagnetic lock per door.
17 Gas spring to be provided on front doors of racks.
18 LED light to be provided on each rack.
19 RACK OEM must be ISO9001 and ISO 14001 certified
5.3.3 Biometric Access Control and Fire alarm system
S.No Specifications Compliance (Yes/No)
Offered Specification with Document Proof
Biometric based Access Control
1 The IP based Access Control System shall be used to serve the objective of allowing access to authorized personnel only. The system deployed will be based on Biometric Technology. The front rack doors will be provided with magnetic locks and will operate on fail-safe principle through one common Biometric access control system. Rear doors will be operated through mechanical lock & key mechanism.
2 The system would be designed and implemented to provide following functionality:
3 Configurable system for user defined access
4 Built-in Real Time Clock (RTC), calendar; complete Database stored locally and shall be capable of operating offline on standalone mode
5 Record, report and archive each activity (permission granted and / or rejected) with log formats
6 Fail safe operation in case of no-power condition and abnormal condition such as fire, theft, intrusion, loss of access control, etc.
7 At the biometric reader, user presents the finger to the biometric reader which is unique to each employee. The pattern is read and compared with stored data to grant / deny access.
Fire Alarm System
1 The integrated Data Centre infrastructure is designed as a complete stand-alone unit with security, fire detection and fire suppression systems. Each of the systems is inter-operable and inter connected.
2 Environmentally friendly Novec 1230 agent to be used to ensure that no harm to human beings and environment is
137
caused.
Following systems to be installed.
1 Novec 1230 Clean Agent for fire suppression system
2 Fire detection and alarm systems, with detectors and panel.
3 Protected area: The entire enclosed volume of the integrated data centre & Utility cabinet having electrical distribution panel is protected with fire detection and fire suppression system.
4 The Novec 1230 system should be designed and installed as per NFPA 2001-2012 Edition. SMPV, Petroleum and Safety Explosives Organization (PESO) approved cylinder filled with Novec 1230 is installed in specially designed utility cabinet integrated with Data centre
Monitoring
1 Supply and installation of RDU based / monitoring system with Sensors & notification system. The system shall continuously collect critical information from network connected devices such as UPS system, Cooling Units, temperature & humidity sensors, Door sensors, Water Leak sensor and other dry contact monitoring. Beacon & Buzzer-Sound and Flash Led Alarm. Based on pre-set parameters, automated email alerts are sent to the intended recipients
2 Environmental monitoring with Temperature & Humidity sensors
3 Monitoring Technical Specification:
4 Intelligent Rack environment remote monitoring.
5 Modbus 485 Communications
6 SNMP Communication.
7 Single window for monitoring all sensors.
8 Data and logs of historical information of alarms and notification.
9 Temperature & Humidity Sensor, with LCD display and RJ45 connector.
10 Door opening sensor with RJ 45 connector.
11 Water leak detection sensor with RJ45 connector.
12 Smoke detection sensor with RJ45 connector
13 Alarm device with LED flash and sound option
5.3.4 DC CCTV Surveillance with Camera, storage and Switch
Indoor Fixed Dome Cameras for internal surveillance
S.No. Features Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 Image sensor 1/2.8" Progressive Scan CMOS 5MP or better
2 Lens Min 2.8~12 mm Varifocal Motorized Lens, DC‐iris or P-iris, Auto Focus
3 IR Range Min 30 Mtr or better
4 WDR True WDR 120 db or better
138
5 HLC Should support HLC with adjustable settings
6 Min. Illumination
Color mode: 0.05 lux and B&W mode: 0.01 lux, 0 LUX With IR ON
7 Electronic Shutter
1/25-1/100000s or better, Auto/Manual Adjustment
8 Video Compression
MJPEG, H.264, H. 265
9 Streaming Support
Individually configurable 3 video streams (H.264/H.265), Unicast/ Multicast
10 Resolutions and frame rates
Max: 30 fps at 2592x1944, 25/30 fps at 2592X1520, 25/30 fps at 2560x1440, 25/30 fps at 1920x1080, 25/30 fps at 1280x720, Min : 25/30 fps at 480x240
11 Protocol Support
IPv4,IPv6, HTTP, HTTPS, 802.1X, QoS, FTP, SMTP, UPnP, SNMP, DNS, NTP, RTSP, RTP, TCP, UDP, IGMP, ICMP, DHCP
12 Network Security
Should support IP and Mac conflict detection, ACL
13 Intelligent Video
Motion Detection, Camera Tampering detection, Zone Intrusion detection, Perimeter intrusion detection, Object counting, Trip wire detection
14 Behavior analysis
Line crossing detection, Missing object detection, Crowd detection
15 Video detection
Scene change detection, image defocus detection
16 Corridor Mode Support 9:16 aspect ratio for narrow corridors, hallways or aisles.
17 image stabilization
Should support electronic image stabilization
18 Privacy Mask Support Minimum 4 areas / Zones
19 OSD Should support OSD of Camera Name, Time, Date, week, Location, etc
20 Image setting
Image Defog, ROI, BLC, Flicker Control, White Balance, 3DNR, Image enhancement, lens correction, Auto Exposure control, Automatic gain control, Hue, automatic noise reduction, Automatic dead pixel cancelling, Watermark
21 Viewing/configuration
Support IE Browser/VMS/NVR and IOS/Android/windows
22 Audio Function
Camera Should have high quality built-in Mic for Audio recording and should have audio in/out interfaces
23 Internal Edge Storage
Camera should support Micro SD/SDHC/SDXC memory card for edge recording and support up to 128GB Capacity, Schedule and Event Recording, Support pre-post alarm buffer recording, configurable free disk management
139
24 Edge Storage Auto Backup
Camera should record automatically when NVR not reachable and support automatic Synchronization of backup recording form SD Card to NVR when connection resume
25 Alarm interface
Camera Should support 1ch alarm in and 1ch alarm out
26 Interface 10/100BaseT or better RJ45 Port
27 POE Internal 802.3af POE Support
28 Environment Protection
IP 66 Rated, IK10 Vandal Proof Housing with clear vandal proof Bubble
29 Housing Full Metal housing with Mounting bracket included for Wall/Ceiling Mount
30 ONVIF compliance
ONVIF version 2.4 or better and ONVIF Profile S compliant
31 Time and Date
When camera reboots or powered ON after long time, the time and date of camera should remain same as per last configured without any update or synchronization required using NVR or internet
32 Certification CE, FCC, UL, cUL, ROHS , UL 60950-1, BIS All IP cameras should be of Same Make
33 Operating Temperature
-10 to 60 °C, or better
34 Surge Protection
Minimum 2Kva surge protection should be included with each camera
35 NVR
16 channel or more NVR with 2 Hard disk slot, default 4TB or more Surveillance Hard disk to be loaded, should support all analytics form camera and audio recording. NVR must be same make as IP camera. Bidder should ensure to increase the number of NVR channels if cameras are more than 16 Nos. Bidder should ensure that minimum 30 days video footage backup should be available in TMMC/ATCS Command center. Minimum 4TB Hard disk and can be increased more based on the cameras quantity and storage requirement.
36 Face Recognition
Should have 4 Face recognition software licenses, required hardware/Processing unit must be suggested by bidder, Should support minimum 5K databases, support whitelist/blacklist, face attendance, access control functions, etc. This is used for DC/TMMC security.
37 Industrial POE Switch
24 port gigabit industrial grade L2 managed POE switch with 4 1G Fibre port, IP30 Rated with 400W POE Budget, operating temperature support up to 75 degree C. The Switch should be
140
UL and CE certified
38 Monitor
Should include 32” Full HD Monitor with following functions: Aspect Ratio - 16:9 Resolutions - 1920 X 1080 (1080p) Contrast Ratio - 1000 :1 or better Connectors - HDMI, VGA Continuous operation - 16/7 or more Mounting - Table and wall mount
39 Coverage Locations
Bidder should calculate the camera quality as per 4000 Sq.ft DC/TMMC command center including 1000 Sq.ft ATCS Command center. Which included reception, DC, Helpdesk cabins, common work area, Lobby, Command center, Etc
5.3.5 DC wireless access point with controller
Wave2 Wireless access Point 1200 Mbps Throughput:
S.No. Features Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 Network protocol
IEEE wireless LAN standards shall supported (802.11a/b/g/n/ac)
2 Performance
Should be Highest Performing Access Point with the latest 802.11ac Wave 2 standard
3 Transmit Power
23dbm on each 2.4 & 5 Ghz
4 Interface 1#10/100/1000Mbps RJ45 Ports,1# Reset Button ,1#DC Port ,
5
Data Rate
Support 1200Mbps speed Should support 2.4 GHz and 5.x GHz for single-band, dual-radio operation, Max Data rate up to 1167 Mbps
6
Discovery and Roaming
Should support MIMO Technology AP should support discovery of controller between L2 and L3 network AP should support seamless and fact roaming through L3 network Should support fast roaming, Forced roaming and load balancing between weak signals
7 Wireless Working frequency
802.11a/n : 5.150 GHz to 5.850 GHz, 802.11b/g/n : 2.4 GHz to 2.483 GHz, 802.11ac: 5.150GHz to 5.250GHz,5.250GHz to 5.350GHz, 5.725GHz to 5.850GHz
8 Wireless Antenna
AP shall support Built-in 2.4 GHz 4 dBi antenna and 5 GHz 5 dBi antenna or better
141
9 Operate Mode Repeater, Wireless AP, WDS
10 Protection Level
Shall Support IP30 or better Rating
11 Wireless SSID
AP should support a minimum of 16 or better SSIDs
12 Power AP’s should comply to PoE input standard 802.3af and DC 12V/1A
13 Wireless Management
AP should be Centralized management through an AC; both fit and fat modes and Both local and remote maintenance
14 Wireless Accessories
AP should be quoted including all the installation accessories like Original mounting brackets (T-Rail , Wall and Ceiling Mounting.), power supply units, power injectors.
15 Firmware management
Should support dual firmware loaded to support failover between firmware
16 AP Load Balancing
AP Should support load balancing based on traffic, number of users and frequency bands
17
IPv6 support
Should support IPv4 and IPv6 Dual stack Should support IPv6 address, DHCPv6, IPv6 Portal, IPv6 forwarding
18
QOS
Should support WMM, 802.1P and 802.11e Should support wireless priority mapping, SSID policy mapping and data streams policy mapping
19 Wireless Security
AP should support authentication methods: 802.11i, WEP , WPA , WPA2 & RADIUS,WPA-EAP using TKIP,LDAP authentication, PEAP authentication, WIDS/WIPS, Protection against DoS attacks, ACL Should support LDAP, PEAP and Mac address authentication Should support 802.1x, captive portal, internal/external portal, encrypted password and mac address user admission authentication Should support intrusion detection, Rouge AP and client detection
20 Certificate CE, FCC, RoHS
21 OEM Compliance
Access point OEM should comply to all OEM Conditions of Network Switch
22
Coverage Locations
Bidder should calculate the access point quality as per 4000 Sq.ft DC/TMMC command center including 1000 Sq.ft ATCS Command center. Which included reception, DC, Helpdesk cabins, common work area, Lobby, Command center, conference room, Manager/officer cabins, Etc
Wireless Controller with AP License
S.No. Features Specification Compliance (Yes/No)
Offered Specification with Document Proof
142
1 Physical ports 6# 10/100/1000 Mbps Base-T Ports
2 Management Ports
RJ45 Console port 2# USB Ports
3 Internal Storage and RAM
64G SSD/Msata drive and 4GB RAM should be loaded
4 AP License Basic License as per access point quantity should be loaded, upgradable Maximum up to 512 AP
5 Concurrent users
Should support minimum 1500 Concurrent users per AC Should have built-in Portal server
6 AP Discovery Should support L2 and L3 Discovery
7 CAPWAP Protocol
Should Support L2/L3 network topology between AP and AC AP Should support discover and accessible AC automatically AP should support update of firmware and download of configuration from AC automatically
8 Roaming Should support Seamless roaming, Fast roaming
9 L3 Features Support Static route , ARP entries, OSPFv3, BGP, PIM-SM/DM, PIM Routing
10 Management Features
Web, CLI, Telnet and Console access TFTP/FTP and SSH v1/v2 SNMPv1/v2c/v3 Radius Authentication Syslog (Internal & External) and SNTP/NTP
11 Authentication,
Should support internal and external Portal authentication Should support customized Portal, External Radius, LDAP and Mac authentication
12 Security encryption
Support 64/128 WEP, dynamic WEP, TKIP, SMS encryption mode Support 802.11i safety authentication, Should support 802.1x authentication Should support PSK mode, Enterprise and Personal version Support WAPI encryption and authentication
13 Vlan 802.1Q, Port based vlan, Vlan groups
14 Security management
Should Support wireless intrusion detection and intrusion prevention, Support WIDS/WIPS (wireless intrusion detection and wireless intrusion protection) Anti-wireless flooding attack, Anti-spoof attack
15 IPv6 Features Should support ICMPv6, DNSv6, IPv6 Static route, IPv6 ACL
16 High Availability
Support N+1 Hardware failover and Backup Support Hot backup for internal Portal server
143
and DHCP server
17 Certificates CE/FCC, ROHS
18 General Conditions
All the software features and Hardware ports should be available from Day1 of purchase
19 Environment Operating Temperature: 0°C~50°C Relative Humidity: 10%~90% non-condensing
5.3.6 Ruggedized Hand held devices
Parameter Tech Specs
1 Processor Octa core Min 1.8 Ghz
2 Operating System Android 8 or better
3
Memory Min 3GB RAM, 32 GB Internal storage, expandable micro SD card slot support up to min 64GB
4 Interface Micro USB 2.0
5 Wireless WLAN (IEEE 802.11 a/b/g/n), 2G,3G ,4G LTE
6 Communication Class 1, Bluetooth 5.0
7
Power
Rechargeable battery min 3200 mAh (Li-ion battery), with warm swap, Back up time is at least 8 hrs of use in the field suitable mechanism for charging from 220V standard AC power supply along with Vehicle charger must be provided
8 Camera
Rear Camera 8 MP, Autofocus, night vision capacity, LED flash , 5 MP front camera
9
Display and Keypad 4.7 inch HD or higher, (1280X720 or higher) Capacitive touch screen with direct bonding & anti-reflective treatments readable in sunlight.
10 Storage eMMC 32 GB
11 Global positioning Integrated GPS, CEP50, GLONAS
12 Security FIPS 140-2 level-1 compliant
13
Operating Conditions Operating Temperature -10 to +50 degree Celsus, operating Humidity 30% ~80% non condensing
14 Rugged Structure
Drop Specification: at least 7 ft drop tested as per MIL-STD 810G, IP66 rating
15 Dimensions and Weight
Dimensions (HxWxL) compact Design weight less than 350 gms.
16 Indication
Suitable indication on Equipment for charging, low battery, connectivity etc
144
17 Voice & Audio
Built in speaker good quality speaker with high decibel output
145
6 Non-IT Requirements, Specifications & Office Interior
The selected bidder should adhere to the specifications given below for Non-IT components. It is
essential that Fire Proof material be used as far as possible and Certification from Fire
Department be taken for Command Centre and Office premises before Go-Live.
6.1 General Standards:
The ICOMC interiors shall be state of the art adhering to the various best practices norms for
integrated control centres, including Development of ergonomic reports for the TMMC covering
Human Factors Engineering (HFE), ISO9241 (Ergonomic requirements for office work with visual
display terminals - VDTs) and ISO11064 (Ergonomic Design of Control Centres)
The proposed interior material should meet to basic control room norms, including but not
limited to:
• ASTM E84 or equivalent fire norms,
• High scratch resistant surfaces,
• Seismic zone compliance, and
• Green Guard passed Desk for ensuring safe environment for operators.
6.2 Civil and Architectural Work
6.2.1 False Ceiling
Metal false ceiling with powder coated 0.5mm thick hot dipped galvanized steel tiles 595 x
595 mm with regular edge (10mm) suitable for 25mm grid supported on suitable powder
coated galvanized steel grid as per manufacturer specification. The same shall be inclusive of
cut outs for lighting, AC grills, Fire detectors, nozzles, etc.
Minimum 12 mm thick fire line Gypsum false ceiling and lighting troughs 300 mm as per
design including 100 mm high cornices as lighting pelmets on G.I. framework, in G.I. vertical
supports at every 450mm c/c and horizontal runners at every 900mm c/c self-taping metal
screws to proper line and level. The same shall be inclusive of making holes and required
framing for fixing electrical fixtures, A.C. grills etc. GI vertical supports to be anchored to slab
by means of anchor fasteners.
146
6.2.2 Furniture and Fixture
Workstation size of min. 18” depth made with 1.5mm thick laminate of standard make over
18mm thick commercial board complete with wooden beading including cutting holes &
fixing of cable manager etc. complete with polish. Edges shall be factory post-formed. The
desk shall have the necessary drawers, keyboard trays, cabinets etc. along with sliding /
opening as per approved design with quality drawer slides, hinges, locks etc. All
workstations, cabins should be as per industry best practices and standards.
Providing & making of storage unit with 18 mm thick MDF board along with 1.5 mm
approved laminate colour outside and 2 coat of enamel paint inside the storage of size
1'6"x1'6"x2'4". The same should be provided with all the required accessories including the
handle, lock, sliding channel and necessary hardware, etc. complete with polish
An enclosure for gas cylinder of Shutters and Partitions along with wooden support and 18
mm thick MDF board along with 1.5 mm approved laminate colour outside and 2 coat of
enamel paint inside the shutter. The same should be provided with all the required
accessories including the handle, lock, loaded hinges, tower bolt and necessary hardware
etc. complete with French polish.
6.2.3 Partitions (wherever required as per approved drawing)
Full height partition wall of 125 mm thick fire line gyp-board partition using 12.5 mm thick
double fire line gyp-board on both sides with GI steel metal vertical stud frame of size min.
75 mm fixed in the floor and ceiling channels of 75 mm wide to provide a strong partition.
Glass wool insulation inside shall be provided as required. Fixing is by self-tapping screw with
vertical studs being at 610 mm intervals. The same should be inclusive of making cut-outs for
switch board, sockets, grill etc. It shall also include preparing the surface smoothly and all as
per manufacture’s specification etc. finally finishing with one coat of approved brand of fire
resistant coating. Glazing including the framework of 4" x 2" powder coated aluminum
section complete (in areas like partition between server room & other auxiliary areas).
Fire Rated Wire Glass minimum 6 mm thick for all glazing in the partition wall complete.
(External windows not included in this). All doors should be minimum 1200 mm (4 ft.) wide.
147
6.2.4 Flooring (wherever required as per approved drawing)
SI shall procure and install a raised floor to match the floor height and room aesthetic in
accordance with the approved final layout and design. SI shall consider standard parameters
for developing the final height, width, point of load, and uniform distribution load of the
raised floor for the rooms based on type of furniture and overall load.
SI shall ensure the following features and parameters are considered while designing and
commissioning the raised floor:
• Point of Load (PoL) shall be considered 20% more than the actual load
• Uniform Distribution Load shall be calculated according to the final Point of Load
• Noise-proof, Fireproof
• Maintenance window for easy access to under the raised floor
• Separate electrical and data cable tray under the raised floor
• Face of floor tiles shall conform to the aesthetic part of the approved design
• SI shall perform load test and noise test of the constructed raised floor.
The SI shall complete the following requirements for the raised flooring panels:
• Floor shall be designed for standard load conforming to BIS 875-1987.
• Panels shall be made up of 18-gauge steel of 600 mm × 600 mm size treated for corrosion
and coated with epoxy conductive paint (minimum thickness 50 Micron).
• Raised flooring covering shall be antistatic, high- pressure laminate, two (2) mm thick in
approved shade and color with PVC trim edge. It shall not make any noise while walking on
it or moving equipment. Load and stress tests on floor panels shall be performed as part of
acceptance testing.
6.2.5 Air Conditioning and Natural Convection for Data Centre
Precision remote control and manual operated air conditioning system shall be exclusively
installed to maintain the required temperature in the data center server farm area. The A/C
shall be capable of providing sensible cooling capacities at ambient temperature and
humidity with adequate air flow. Air conditioner shall be linked to secondary power supply
as well to prevent them from shutting down in case of power outage
148
6.2.6 Painting
Provide and apply Fire retardant paint of pre-approved make and shade to give an even
shade over a primer coat as per manufacturers’ recommendations after applying painting
putty to level and plumb and finishing with 2 coats of fire retardant paint. Base coating shall
be as per manufacturer’s recommendation for coverage of paint, For all vertical Plain surface
and fire line gyp-board ceiling.
Use approved fire retardant coating on all vertical surfaces, furniture etc. as per
manufacturer's specification.
6.2.7 PVC conduit
The conduits for all systems shall be high impact rigid PVC heavy-duty type and shall comply
with I.E.E regulations for non- metallic conduit 1.6 mm thick as per IS 9537/1983. All sections
of conduit and relevant boxes shall be properly cleaned and glued using appropriate epoxy
resin glue and the proper connecting pieces, like conduit fittings such as Mild Steel and
should be so installed that they can remain accessible for existing cable or the installing of
the additional cables.
No conduit less than 20mm external diameter shall be used. Conduit runs shall be so
arranged that the cables connected to separate main circuits shall be enclosed in separate
conduits, and that all lead and return wire of each circuit shall be run to the same circuit.
All conduits shall be smooth in bore, true in size and all ends where conduits are cut shall be
carefully made true and all sharp edges trimmed. All joints between lengths of conduit or
between conduit and fittings boxes shall be pushed firmly together and glued properly.
6.2.8 Wiring
PVC insulated copper conductor cable shall be used for sub circuit runs from the distribution
boards to the points and shall be pulled into conduits. Looping system of wring shall be used,
wires shall not be jointed. No reduction of strands is permitted at terminations.
149
Wherever wiring is run through trunking or raceways, the wires emerging from individual
distributions shall be bunched together with cable straps at required regular intervals.
Identification ferrules indication the circuit and D.B. number shall be where required
Where, single phase circuits are supplied from a three phase and a neutral distribution
board, no conduit shall contain wiring fed from more than one phase in any one room in the
premises, where all or part of the electrical load consists of lights, fans and/or other single
phase current consuming devices, all shall be connected to the same phase of the supply.
Circuits fed from distinct sources of supply or from different distribution boards or M.C.B.s
shall not be bunched in one conduit. In large areas and other situations where the load is
divided between two or three phases, no two single-phase switches connected to difference
phase shall be mounted within two meters of each other.
All splicing shall be done by means of terminal blocks or connectors and no twisting
connection between conductors shall be allowed. Metal clad sockets shall be of die cast non-
corroding zinc alloy and deeply recessed contact tubes. Visible scraping type earth terminal
shall be provided. Socket shall have push on protective cap.
Balancing of circuits in three phases installed shall be arranged before installation is taken
up. Unless otherwise specified not more than ten light points shall be grouped on one circuit
and the load per circuit shall not exceed 1000 watts.
6.2.9 Cable Work
Cable ducts should be of such dimension that the cables laid in it do not touch one another.
If found necessary, the cable shall be fixed with clamps on the walls of the duct. Cables shall
be laid on the walls/on the trays as required using suitable clamping/ fixing arrangement as
required. Cables shall be neatly arranged on the trays in such manner that a crisscrossing is
avoided, and final take off to switch gear is easily facilitated. Cable shall be laid as per the IS
standard
All cables will be identified close to their termination point by cable number as per circuit
schedule. Cable numbers should be properly punched. For trip circuit identification
additional red ferrules are to be used only in the switch gear / control panels, cables shall be
supported to prevent appreciable sagging. In general distance between supports shall not be
greater than 600mm for horizontal run and 750mm for vertical run.
150
Each section of the rising mains shall be provided with suitable wall straps so that same can
be mounted on the wall. Whenever the rising mains pass through the floor, they shall be
provided with a built-in fire proof barrier so that this barrier restricts the spread of fire
through the rising mains from one section to the other adjacent section.
Neoprene rubber gaskets shall be provided between the covers and channel to satisfy the
operating conditions imposed by temperature weathering, durability etc.
Necessary earthling arrangement shall be made alongside the rising mains enclosure by
Mean of a GI strip of adequate size bolted to each section and shall be earthed at both ends.
The rising mains enclosure shall be bolted type.
The space between data and power cabling should be as per standards and there should not
be any crisscross wiring of the two, in order to avoid any interference, or corruption of data.
6.2.10 Fire Detection and Control Mechanism
Fire can have disastrous consequences and affect operations of a Control Room. It is
required that there is early-detection of fire for effective functioning of the Control Room.
The facility shall be equipped with adequate and advanced Fire Detection and Suppression
system. The system shall raise an alarm in the event of smoke detection. The system shall
have proper signage, response indicators and hooters in case of an emergency. The system
shall be based as per NFPA standards.
• Should proactively alert in case there is a possibility of an electrical fire (short circuit
or over current)
• The system should have the capability to integrate with different makes of fire alarm
systems in the DCs and provide the alarms generated by the system on the
centralized Dashboard.
• The system should be able to plan and process a proper evacuation plan in case of
fire
• Trigger Audio and Visual alarm
• Co-relate with the nearest camera in the site with the zone of the FAS.
• Switching ON of lights on the evacuation pathway.
151
6.2.11 Rodent Repellent System
The entry of Rodents and other unwanted pests shall be controlled using non-chemical,
nontoxic devices. Ultrasonic pest repellents shall be provided in the false flooring and ceiling
to repel the pests without killing them. However, SI shall conduct periodic pest control using
chemical spray once in a quarter as a contingency measure to effectively fight pests.
6.2.12 Access Control System
The Access Control System shall be deployed with the objective of allowing entry and exit to
and from the premises to authorized personnel only. The system deployed shall be based on
Biometric Technology. An access control system consisting of a central PC, intelligent
controllers, power supplies and all associated accessories is required to make a fully
operational on line access control system. Access control shall be provided for doors. These
doors shall be provided with electric locks, and shall operate on fail-safe principle. The lock
shall remain unlocked in the event of a fire alarm or in the event of a power failure. The fire
alarm supplier shall make potential free contacts available for releasing the locks in a fire
condition especially for staircase and main doors. Entry to the restricted area shall be by
showing a proximity card near the reader and exit shall be using a push button installed in
the secure area. The system shall monitor the status of the doors through magnetic reed
contacts. The system should be designed and implemented to provide following
functionality:
# Description 1 Controlled Entries to defined access points 2 Controlled exits from defined access points 3 Controlled entries and exits for visitors 4 Configurable system for user defined access policy for each access point 5 Record, report and archive each activity (permission granted and / or rejected) for each
access point. 6 User defined reporting and log formats 7 Fail safe operation in case of no-power condition and abnormal condition such as fire,
theft, intrusion, loss of access control, etc. 8 Day, Date, Time and duration-based access rights should be user configurable for each
access point and for each user.
9 One user can have different policy / access rights for different access points.
152
6.2.13 Monitoring Workstations
S.No. Features Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 Processor
Intel Xeon E-2274G, 4 Core, 8MB Cache, 4.0Ghz, 4.9GHz Turbo
2 Operating System
Windows 10 Pro, 64bit
3 Chipset Intel C246 Chipset or equivalent
4 Memory
32GB 2666MHz ECC DDR4 Memory expandable up to 64GB (4 Dimm Slots)
5
Memory Reliability
A inbuilt tool which works with ECC Memory and can help to solution multiple hard errors or soft errors within the same block of memory. Which can helps reduce system downtime as far as the memory failure is concerned. (Document required to support the above requirement)
6 Hard Drive
256GB SSD + 1TB 3.5inch Serial ATA (7,200 Rpm) Hard Drive
7 Graphic Card
Professional Graphics with 8GB Memory (NVIDIA Quadro or AMD)
8 Optical Drive DVD RW
9 Slots
(1) Full Height PCIe x16 Gen3; (2) Full Height PCIe x4 Gen3 (open ended); (1) Full Height PCI; (1) M.2
10 Network Card Intel Ethernet Connection 10/100/1000
11 PSU
Less than 480W 90% efficient PSU (80PLUS Gold Certified) Energy Star Compliant
12 I/O Front 2 - USB 2.0 Type A 1 - USB 3.1 Type A (5Gb) 1 - USB 3.1 Type C (10Gb), data only 1 - Microphone & 1 - Headphone Rear 2 - USB 2.0 Type A 4 - USB 3.1 Type A (5Gb) 2 - HDMI Port 1 - RJ45 Network Connector 1 - Serial 1 - Audio Line out
13 Software
Artificial Intelligence Based Performance optimizer software
14 System Management
Out-of-Band Systems Management (Intel vPro Technology)
15 Energy Efficiency and other Compliance
EPEAT Registered, BIS Standards
153
16 ROHS Compliance
Yes
17 Dust Protection
Dust Filter
18 Warranty 3 Years
19
Monitor
Should include 32” Full HD Monitor with following functions: Aspect Ratio - 16:9 Resolutions - 1920 X 1080 (1080p) Contrast Ratio - 1000 :1 or better Connectors - HDMI, VGA Continuous operation - 16/7 or more Mounting - Table and wall mount
6.2.14 Desktops for Helpdesk
S.No Parameters Minimum Technical Specifications Compliance (Y/N)
Offered Specification with Document Proof
1 Processor latest & high performance Intel i3 (3.0 GHz) or higher
2 Memory 8 GB DDR4 Ram upgradable up to 32GB
3 Motherboard
OEM Motherboard
4 Hard Disk Drive
Minimum 500 GB SATA III Hard Disk @7200 RPM or higher
5 Audio Line/Mic In, Line-out/Speaker Out (3.5 mm)
6 Network port
10/100/1000 Mbps auto-sensing on-board integrated RJ-45 Ethernet Port
7 Wireless Connectivity
Wireless LAN - 802.11b/g/n/
8 USB Ports Minimum 4 USB ports
9 Display Port Minimum 1 Display Port (HDMI/VGA) port
10 Keyboard 104 keys Heavy Duty Mechanical Switch Keyboard (USB Interface) with 50 million keystrokes life per switch. Rupee Symbol to be engraved.
11 Mouse Optical with USB interface (same make as desktop)
12 Monitor Should include 32” Full HD Monitor with following functions: Aspect Ratio - 16:9 Resolutions - 1920 X 1080 (1080p) Contrast Ratio - 1000 :1 or better Connectors - HDMI, VGA Continuous operation - 16/7 or more Mounting - Table and wall mount
13 Operation System and Support
Pre-loaded Windows 10 (or latest) Professional 64-bit, licensed copy All Utilities and driver software, bundled in CD/DVD/Pen-drive media.
154
14 Certifications CE or FCC, BIS or Equivalent. Reputed Make
6.2.15 Multifunctional Device
S.No Tender Specification Description Compliance
(Y/N) Offered Specification with Document Proof
2 General Automatic 2-sided Colour laser Printer with Wireless Connectivity and NFC Reader
3 Functions Print, Scan, Copy, Fax Color LED Printer
4 Print Speed (A4/Letter)
Up to 24/25 ppm
5 Interface
Hi-Speed USB 2.0, 10Base-T/100Base-TX, IEEE 802.11b/g/n (Wireless), IEEE 802.11g/n (Wi-Fi Direct) H
6 Display 2.7” Colour LCD Touchscreen
7 PAPER SIZE
A4, Letter, A5, A5(Long Edge), A6, Executive, Legal, India Legal
6.2.16 DG Set
S.No. Features Specification Compliance (Yes/No)
Offered Specification with Document Proof
1 General Auto Starting DG Set Mounted on a common based frame with AVM (Anti-Vibration) pads, residential silencer with exhaust piping, complete conforming to ISO 8528 specifications and CPCB certified for emissions. KVA rating as per the requirement.
2 Capacity 250 KVA
3 Fuel High Speed Diesel (HSD) With 30 ltr. Tank Capacity or better. It should be enough and suitable for containing fuel for 12 hours continuous operation, Complete with level indicator, fuel inlet and outlet, air vent, drain plug, inlet arrangement for direct filling and set of fuel hoses for inlet and return.
4 Power Factor 0.8
5 Engine Engine should support electric auto start, water cooled, multi cylinder, maximum 1500 rpm with electronic/manual governor and electrical starting arrangement complete with battery, 4 stroke multiple cylinders/single and diesel operated conforming to BS 5514/ ISO 3046/ IS 10002
6 Alternator Self-exciting, self-regulating type alternator rated at 0.8 PF or better, 415 Volts, 3 Phase, 4 wires, 50 cycles/sec, 1500 RPM, conforming to
155
IS 4722/ BS 5000, Windings of 100% Copper, class H insulation, Protection as per IP 23.
7 AMF (Auto Main Failure) Panel
AMF Panel fitted inside the enclosure, with the following meters/indicators: Incoming and outgoing voltage Current in all phases Frequency KVA and power factor Time indication for hours/ minutes of operation Fuel Level in field tank, low fuel indication Emergency Stop button Auto/Manual/Test selector switch MCCB/Circuit breaker for short-circuit and overload protection Control Fuses Earth Terminal Any other switch, instrument, relay etc. essential for Automatic functioning of DG set with AMF panel
8 Acoustic Enclosure
The DG set shall be provided with acoustic enclosure / canopy to reduce the sound level and to house the entire DG set (Engine & Alternator set) assembly outside (open-air). The enclosure shall be weather resistant powder coated, with insulation designed to meet latest MOEF/CPCB norms for DG sets, capable to withstand local climate. The enclosure shall have ventilation system, doors for easy access for maintenance, secure locking arrangement.
9 Output Frequency
50 HZ
10 Tolerance +/- 5% as defined in BSS-649-1958
11 Indicators Over speed /under speed/High water temperature/low lube oil etc.
12 Intake system Naturally Aspirated
6.2.17 Field Equipment
6.2.17.1 Specification of Field Junction Box
S.No Tender Specification
Description Compliance (Y/N)
Offered Specification with Document Proof
1 Installation Type
Outdoor
2 Size Suitable size as per site requirements to house the field equipment Should have space to include all items like Field
156
switch, Power meter, Field Ups, Batteries, Solar power system, fiber FMS, Etc.
3 Type Wall mounting rack – Rigid frame that can be fixed to the wall,
4 Protection IP66 Rated
5 Mounting On Camera Pole / Ground mounted on concrete
base
6 Form Factor Rack Mount/DIN Rail
7 Accessories Should have 6 socket PDU with MCB and surge
protection Should have a Fan and all requires accessories
8 General
Rubber Closure for cable entry holes
19”Adjustable rails in the front and rear, Front section with glass door and lock, Top and bottom cable entry facility
Hardware Screw pocket included
OEM should be ISO9001 and ISO14001 certified Server Rack and Field Junction box should be from Same OEM.
6.2.17.2 Camera Poles
S.No Tender Specification Description Compliance(
Y/N) Offered Specification with Document Proof
1 Pole type Hot Dip Galvanized after Fabrication with Silver
coating of 86 micron as per IS:2629; Fabrication in accordance with IS-2713 (1980)
2 Height 5-10 Meters, as-per-requirements for different types of cameras & Site conditions
3 Pole Diameter Min. 10 cm diameter pole (bidder to choose larger diameter for higher height)
4 Cantilevers Based on the location requirement suitable size cantilevers to be considered with the pole
5 Bottom base plate
Minimum base plate of size 30x30x15 cm
6 Mounting facilities
To mount CCTV cameras, Switch, etc.
7 Pipes, Tubes All wiring must be hidden, through tubes/pipes. No wires shall be visible from outside.
8
Foundation Casting of Civil Foundation with foundation bolts, to ensure vibration free erection (basic aim is to ensure that video feed quality is not impacted due to winds in different climatic conditions). Expected foundation depth of min. 100cms. Please refer to earthing standards mentioned
157
elsewhere in the RFP.
9 Protection Lightning arrester at select sites as per the requirements
10 Sign-Board A sign board describing words such as “This area under surveillance” (in English and Hindi)
6.2.17.3 Industrial Grade Outdoor PoE switches
The proposal should adhere to the following minimum eligibility criteria of Switch OEM:
• OEM of Switch have its own service centre in India and should have a toll free number
• OEM or Manufacturer should be ISO 9001, ISO 14001 and ISO 27001 certified.
• OEM or Manufacturer of the offered goods/ equipment’s should be a company registered under the companies Act since last 5 years in India. Valid company registration certificate should be submitted
• OEM should have experience in supplying 500 pcs of IP based Fully Managed POE switches in one single project for any government department in India.
• All the Core Blade switches, TOR Switches, Access Switches, Industrial Switches and fibre modules used in this project form one singe OEM
S.No Tender Specification
Description Compliance (Y/N)
Offered Specification with Document Proof
1 Ports
8x 10/100/1000Base-T POE Ports+ 8 x 1000Base-X (SFP), RJ45 Console port, All expansion module should be added form day 1 Minimum 4* Gigabit SFP module should be loaded form day1 (Each SFP module should support minimum 20KM distance, SFP module should be same make of Switch and support operating temperature of 75 degree C), Bidder can include additional SFP modules incase required at site without any other additional cost. Each switch will have multiple Ring networks, a maximum of 6 switches should be in one ring topology, One switch can have up to 4 rings to occupy 8 SFP ports maximum
2 Performance
Shall support 32 Gbps or more Switch Capacity
Shall support 23 Mpps or more forwarding rate
3 Power Supply Dual Redundant Industrial Power Supply loaded, Hot Changeable
4 IP Rating IP30 Rating or better
5 Ring protection G.8032 ERPS, <50ms ring protection
6 ACL & VLan Table Shall support 2048 ACL Table & 4K Vlan Table
7 Jumbo Frame 9K or More
158
8 Mac address 16K or more
9 Vlan Port Based Vlan, IEEE802.1Q, Protocol Based Vlan, Voice Vlan, Mac Vlan
10 Multicast Functions
IGMP v1/v2/v3 snooping, IGMP Fast Leave, MLD v1/v2 snooping,
11 Security Features
Mac Based ACL, IP based ACL, MAC-IP ACL, User-Defined ACL, Time range ACL, VLAN ACL, Port Security, Mac Limit on Vlan and Port, Ani-arp scan and snooping, ARP Binding, AAA, IEEE 802.1x, TACACS+, Radius, Stacking/virtual stacking with single IP Management
12 DHCP Management DHCP Client, DHCP Snooping
13 Qos 8 Queues Per Port, COS, TOS, DSCP, 802.1p, Precedence, SP, WRR, SWRR, DWRR
14 Spanning Tree 802.1D STP, 802.1W RSTP, 802.1S MSTP Root Guard, BPDU Guard, BPDU Forwarding
15 LACP 16 groups / 8 ports
16 Management Port Must Have RJ45 Console Port
17 L2 Ring Protection ITU-T G.8032, Loopback Detection
18 Maintenance and Operation Management
TFTP/FTP CLI, Telnet, RJ45 Console, Web/SSL (IPv4/IPv6), SSH, SNMPv1/v2c/v3, SNMP Trap Public & Private MIB interface, Ping, Trace Route Radius Authentication Syslog (IPv4/IPv6) SNTP/NTP, Dual IMG, Multiple Configuration Files Port Mirror, LLDP/LLDP MED, Support DAD, IPv6 Source guard.
19 IPv6 Features Support IPv4/v6 Dual stack
20 POE Protocols IEEE 802.3af POE(15.4W) and IEEE 802.3at POE+ (30W) support on all ports
21 POE Management
Support POE Management on Switch GUI Support Power time scheduling, power limit configuration, power priority configuration, etc.
22 POE Budget 240 Watts or better POE budget
23 Power supply Dual industrial grade power supply must be loaded from Day1
24 Operating temperature - 40 ~ 75 or better
25 Certifications
CE, FCC, UL, ROHS, UL 60950-1 (should not be an UL Multi listed certificate or report, UL verification letter to be submitted along with bid for non multi listing) All types of Switches should be from same OEM
159
6.2.17.4 Specification of Field UPS.
S.No Tender Specification Description Compliance
(Y/N) Offered Specification with Document Proof
1 Capacity 1 KVA
2
Input Range Voltage Range 155-280 V on Full Load Voltage Range 110-280 V on Less than 70% Load Frequency 50 HZ ±3 HZ
3 Output Voltage & Waveform
220V AC/ 230V AC/ 240V AC (Selectable)
4 I/P & O/P Power Factor
0.9 or higher power factor
5
Mains & Battery
Sealed Lead Maintenance Free VRLA type (Lead Calcium SMF batteries NOT acceptable), Mains & Battery with necessary indicators, alarms and protection with proper battery storage stand
6. Frequency 50 Hz +/- 0.5% (free running), Pure Sine wave
7. Crest Factor min. 3:1
8. Third Harmonic Distribution
< 3%
9. Input Harmonic Level
< 10%
10. Overall Efficiency
Min. 90% on Full Load;
11. Noise Level < 55 dB @ 1 Meter
12. Backup at least 60 minutes (1 hours / VAH)
13. Warranty 3 years with UPS & battery
14. Certification ISO 9001:2008 & ISO 14001 certified
15. Protection To be provided for overload/ short circuit; overheating; input over/under voltage; output over/ under voltage.
16. Alarms & Indications
All necessary alarms & indications essential for performance monitoring of UPS like mains fail, low battery & fault detection
17. Interface SNMP interface support (for remote monitoring)
18. Galvanic Isolation
To be provided through Inbuilt transformer
19. Compatibility UPS to be compatible with DG Set supply and mains supply
20. Bypass Automatic Bypass Switch
21. Technology True ON-LINE (Double Conversion) with IGBT based inverter and PWM Technology
160
22. Support The system should not be an end of life / end of service product
23. Operating Temperature
0 to 55 Degrees Centigrade
24. Certifications BIS / UL
6.2.17.5 Networking Cost (Passive Components including Patch Panel, LIU, Cat6 Cable, Patch Cords)
TECHNICAL SPECIFICATION FOR PASSIVE COMPONENTS
S.No General Passive Specifications Compliance (Y/N)
Offered Specification with Document Proof
1 OEM should submit ISO 9001, 14001 and 27001 certificates for the manufacturing related to all products involved in tender.
2 All Passive Components should be RoHS (Restriction of Certain Hazardous Substances) compliant. Declaration to be provided for RoHS Compliance
3 OEM should provide 20 year extended performance warranty/Application Assurance for end -to-end channel.
4 All the components should comply with their respective specifications stated below.
5 All Copper cable, Fiber cable, Copper accessories and fiber accessories should be from the same OEM/Brand.
6.2.17.6 Fiber Cable 12 cores Type & Construction:
S.No Tender Specification Description
Compliance (Y/N)
Offered Specification with Document Proof
1 Cable Type 12Core Fiber Cable SM 9/125 micron, graded index, anti rodent. The Single Mode Fiber cores should be Low Water Peak.
2 wavelengths, 1310 nm & 1550 nm
3 Standards should conform EIA/TIA 455, EIA/TIA 568 , ISO 11801
4 Strength Fiber should be protected inside jelly filled loose tube armoring with acrylic coated good quality steel
5 tube colour Each tube should be different color for easy identification
6 Armour ECCS armour followed by a jacket of polyethylene. Over the armour, water blocking powder applied for water tight cable.
7 Core The fiber core should be ITU 651 /652.D specification, should support Gigabit.
8 Tube Type Should have HDPE jacket with UV compliant.
161
6F/12F with UniTube and 24F Multitube (8Fx3 Tubes, 3 Fillers)
9 Attenuation : not more than 0.38 dB/km at 1310 nm and 0.25 dB/km at 1550 nm using ITU 652D fiber core
10
Optical characteristics - Parameter / Unit / specification
Optical characteristics - Parameter / Unit / specification
Cladding Diameter / µm / 125.0 ± 1.0
Cladding Non-Circularity / % / ≤ 1.0%
Coated Fiber Diameter / µm / 235 to 255
Core/Cladding Concentricity Error / µm / ≤ 0.8
Mode Field Diameter / µm / 9.3 ± 0.5 @ 1310 nm
Coating/cladding concentricity error / µm / ≤ 12
Minimum Proof Strength Strain / GPa% / 0.70 (100 kpsi)
Fiber Curl / M / > 4
Zero-Dispersion Wavelength / Nm / 1300 to 1324
Zero-Dispersion Slope / ps/nm2-km / ≤ 0.092
Maximum Dispersion / ps/nm-km - 1285-1330 /
≤ 3.5 - 1550 nm / ≤ 18
Polarization Mode / ps/√km / ≤ 0.2
Fiber Macrobend / dB / ≤ 0.05@ 1310 nm
(100 turns. 60 mm dia.) / ≤ 0.10@ 1550 nm
Fiber Macrobend / dB / ≤ 0.5 @ @ 1550 nm
(1 turn @ 32 mm diameter)"
Coating Strip Force / N / 1.3 ≤ F ≤ 8.9
Dynamic Tensile Strength / Kpsi / Unaged
:>550 (3.8 GPa)
Aged :>440 (3.0 GPa)"
B. Fiber LIU
S.No Tender Specification Description
Compliance (Y/N)
Offered Specification with Document Proof
1 Mount Din rail Mount for outdoor environment
2 Cable Entry/Exit Should have at least one cable entry and one exit
3 Splice tray Should be fitted with 12 port Splice tray
4 Adaptor plate Should be fitted with 12 Core support Adaptor plate
5 Compatibility To be fitted in the Supplied LIU, Should have auto Lock and Screw
162
The LIU should have aluminum base The LIU should be sliding options.
6 Color Should able to differentiate between SM should use standard color
7 Adaptor Duplex LC Adaptor with Zirconia Sleeve, Adaptor loaded to support 24 core fiber
8 Pigtail 1.5 M SM LC type Pigtail to be supplied12 nos per LIU
S.No Tender Specification Description
Compliance (Y/N)
Offered Specification with Document Proof
C. Ruggedized Outdoor Single Mode Fiber Patch cord –Duplex (LC LC) with Stainless Steel Tape for stronger protection 1 Cable type Ruggedized LC type SM patch cord Tight
buffered G.652D
2 Cable Protection/Armor
Hellical Stainless steel tape over a buffered fiber surrounded by a layer of aramid and stainless steel mesh.
3 Cable Jacket Low Smoke Zero halogen /PVC
4 Length 3 meter in length
5 Ferrules Pre-radiused Ceramic Ferrules
6 Insertion Loss ≤0.3dB
7 Return Loss >=20dB,
D. CAT6-Outdoor Double Jacket , Anti Rodent Cable (STP Type) 1 Cable Outer
jacket material: HDPE Outer Sheath with anti rodent chemical
2 Conductor diameter:
AWG 23
3 Cable Inner jacket material:
LSZH
4 Fire class IEC-60332-1
5 General Specs All Fiber and copper cabling should be from same OEM and should have minimum20 years of application warranty
E. CAT6 23AWG Outdoor Armoured SFTP Copper Per Meter 1 Standard Length 305 Meters (1000 Feet),
2 Standard Length 305 Meters (1000 Feet),
3 Cable Type and support
4 Pair Shielded Foil Twisted Pair Cable, Support for Fast and Gigabit Ethernet, IEEE 802.3/5/12, Voice, ISDN, ATM 155 & 622Mbps. Should be Tested up to 550Mhz
4 Conductor 23 AWG Annealed bare solid copper
5 Insulation High Density Polyethylene
163
6 Core Colour
Pair 1 : White – Blue
Pair 2 : White – Orange
Pair 3 : White – Green
Pair 4 : White – Brown
7 Sheath Fire Retardant PVC Compound (FRPVC)
8 Pair Separator 4 twisted pairs separated by internal X shaped, 4 channel, polymer spine / full separator. Half shall not be accepted.
9 Sheath Colour Grey / Blue
10 Approx. Cable OD 6.2 mm
11 Flame Rating 60 deg.C As per UL 1685 CM
12 Operating Environment Outdoor, Armored, Black colour
13 Electrical Specification at 250 MHz
14 Standards TIA / EIA 568 C.2
15 Impedance 100Ohms +/- 15%
16 (NVP) Velocity of Propagation 69% or more
17 @ 250 MHz Approx.
18 Delay Skew 45 ns /100 mtrs. max. @ 20 deg. C, for 1 MHz~250 MHz Approx.
19 Propagation Delay <=536 ns / 100 mtrs. max.
20 @ 20 deg. C, @ 250 MHz
21 DC Resistance <= 9.38 ohm / 100 mtrs. max. @ 20 deg. C
22 Mutual Capacitance 5.60 nF / 100 mtrs. max. Approx.
23 Safety UL Listed
F. UTP Field Termination Connector IP20 1 Connection type Toolless Insulation Displacement Connection
2 Category Cat 6 STP
3 IP Class IP 20 rated
4 color Coding Should have option for visual color coding
G. Information Outlet 1 Connection type Toolless IDC type outlet
2 material Low Smoke Zero halogen
3 Category Cat 6 STP
4 mating cycles min 750 mating cycles
H. STP Patch Panel Unloaded 1 Mount 1U Rack Mount 24 Port STP Patch Panel
164
2 Type 110 wiring block at rear end & RJ 45 jack on front panel
3 Quality The modules should have high quality PCB
4 General The IDC should have 45 degree/ V shape contact
5 Cable Manager 19” rack mountable and shuttered with cable manager
6 Standards Should conform or exceed the EIA/TIA 568 standards for CAT6
7 General Metallic high strength & 1U height, should have
routing rings, ties, labeling strips for identification
6.2.17.7 ANPR software with required no. of Licenses
S.No Specifications Compliance (Y/N)
Offered Specification with Document Proof
ANPR System shall enable monitoring of vehicle flow at strategic locations. The system shall support real-time detection of vehicles at the deployed locations, recording each vehicle, reading its number plate, database lookup from central server and triggering of alarms/alerts based on the vehicle status and category as specified by the database. The system usage shall be privilege driven using password authentication. System should have following requirements:
1
The System should automatically detect a vehicle in the camera view using video detection and activate license plate recognition
3 The System shall automatically detect the license plate in the captured video feed in real-time.
4 The system shall perform OCR (optical character recognition) of the license plate characters (English alpha-numeric characters in standard fonts).
5 The System shall store JPEG image of vehicle and license plate and enter the license plate number into DBMS like MySql etc. database along with date time stamp and site location details.
6 The system should be able to handle multiple vehicles simultaneously i.e. if there are more than one vehicle in the camera view the system should be able to detect all of them, extract their license plate numbers and perform OCR on the license plate characters
7 System should be able to detect and recognize the English alphanumeric License plate in standard fonts and formats of all vehicles including cars, HCV, LCV and two wheelers.
8 System should able to detect single row, double row, multi row, square and rectangular plates as well
9 The system shall be robust to variation in License Plates in terms of font, size, contrast and color and should work with good accuracy.
165
10 The success rate should be minimum 80%+ in Day and Night
Alert Generation
11 The system should have option to input certain license plates according to the hot listed categories like “Wanted”, “Suspicious”, “Stolen” unauthorized, VIP etc. by authorized personel.
Vehicle Detection and Video Capture Module
12 The system should be able to generate automatic alarms to alert the control room personnel for further action, in the event of detection of any vehicle falling in the Hot listed categories
Graphical User Interface
13 The system Graphical User Interface should be bi-lingual: it shall support both English & Graphical User interface (GUI) should provide following information: - a. Image of the vehicle b. Image of the number plate c. Text conversion of number plate after using OCR (Optical Character Recognition) technology d. Date, Time and location of offending vehicle e. Event/images/chart of ANPR
Report
14 System should able to give camera ID / Camera Location etc on report page
15 System should able to give vehicle image with license plate image
16 System should able to give OCR Image/License plate Image
17 System should able to give Watch list (“Wanted”, “Suspicious”, “Stolen” ,”Authorized”, “Lost”) on report page
Vehicle Status Alarm Module
18 On successful recognition of the number plate, system should be able generate automatic alarm to alert the control room for vehicles which have been marked as "Wanted", "Suspicious", "Stolen", "Expired". (System should have provision/expansion option to add more categories for future need).
19 The Instantaneous and automatic generation of alarms. In case of identity of vehicle in any category which is define by user.
Vehicle Log Module
20 The system shall enable easy and quick retrieval of snapshots and other data for post incident analysis and investigations. For example a database could be searched using criteria like date, time, location and vehicle number
21 The system should be able to generate suitable MIS reports that will provide meaningful data to concerned authorities and facilitate optimum utilization of resources. These reports shall include.
166
i. Report of vehicle flow at each of the installed locations for Last Day, Last Week and Last Month.
ii. Report of vehicles in the detected categories at each of the installed locations for Last Day, Last Week and Last Month.
Vehicle Detection and Video Capture Module
23 The system shall have Search option to tune the reports based on license plate number, date and time, site location as per the need of the authorities.
24 The system shall have option to save custom reports for subsequent use. The system shall have option to export report being viewed to common format for use outside of the ANPRS or exporting into other systems.
25 The system should provide advanced and smart searching facility of License plates from the database. There should be an option of searching number plates almost matching with the specific number entered (up to 1 and 2 character distance).
Storage
26 The System shall store JPEG/MJPEG images of vehicle as well as of thumbnail of the license plate for each vehicle
27 The system shall store the vehicle license number into a relational SQL database (MySQL) along with date timestamp and site location details. The necessary license/ subscription/support services of the database software should be bundled with the ANPR software.
Vehicle Category Editor
28 The system should have option to input certain license plates according to category like "Wanted", "Suspicious" "Stolen", “Expired" etc. by Authorized personnel.
29 System should have option to specify maximum time to retain vehicle records in specific categories.
30 The system should have option to update vehicle status in specific category by authorized personnel. e.g. on retrieval of stolen vehicle, system entry should be changed from "Stolen" to "Retrieved".
Extra Integration and more features
31 ANPR system should be able to integrate with Airport authority Vehicle/Parking management system
32 ANPR can recognize the any Split number plate of 2W, 3W, 4W, truck and buses.
33 ANPR Application can support More than one IP camera.
34 ANPR Application can integrate with Boom barrier, E challan, Vahaan app.
35 ANPR Application system can alarm can be generated in the form of sound burger or it can be also integrated with any other alerting system.
36 ANPR application support two types of admin login support 1.Regular user 2.Admin user
167
37 API & SDK Support
Central Management Module
38 The Central Management Module shall run on the ANPRS Central Server in control booth. It should be possible to view records and edit hotlists from the Central Server.
39 ANPR and VMS should be integrated with each other
RLVD Specification
1. The following Traffic violations to be automatically detected by the system by using appropriate Non- Intrusive sensors technology: The system should have both provisions to detect red light status by taking the signal feed from the traffic signal controller as well as by video analytics method using another camera (Evidence Camera) focused at the red light. The Evidence camera should also be used for evidence snap generation. Red Light Violation Stop Line Violation
2. The system should be capable of capturing multiple infracting vehicles simultaneously in Different lanes on each arm at any point of time with relevant infraction data like:
a) Type of Violation
b) Date, time, Site Name and Location of the Infraction Registration Number of the vehicle through ANPR Camera system for each vehicle identified for infraction.
3. The system should be equipped with a camera system to record a digitized image and video of the violation, covering the violating vehicle with its surrounding and current state of signal (Red/Green/Amber) by which the system should clearly show nature of violation and proof thereof
a. When it violates the stop line.
b. When it violates the red signal.
c. Besides, a closer view indicating readable registration number plate patch of the violating vehicle for court evidence for each violation.
d. The system must have in-built tool to facilitate the user to compose detail evidence by stitching video clips from any IP camera in the junction (including but not limited to the red light violation detection camera, evidence camera), and any other surveillance cameras in the vicinity of the spot of incidence. The entire evidence should be watermarked and encrypted to stand the court of law.
e. The system shall be able to detect all vehicles infracting simultaneously in each lane/ arm at the junction as per locations provided. It should also be able to detect the vehicles infracting serially one after another in the same lane. The vehicles should be clearly identifiable and demarcated in the
168
image produced by the camera system.
f. The Evidence image produced by the system should be wide enough to give the exact position of the infracting vehicles with respect to the stop line and clearly indicate colour of the Traffic light at the instant of Infraction even if any other means is being used to report the colour of the light.
g. The system should interface with the traffic controller to validate the colour of the traffic signal reported at the time of Infraction so as to give correct inputs of the signal cycle.
h. The Evidence and ANPR camera should continuously record all footage in its field of view to be stored at the local base station. This should be extractable onto a portable device as and when required. The option of live viewing of evidence cameras from the locations shall be available at the TMC. The network should have the capability to provide the real time feed of the evidence camera to the TMC at the best resolution possible on the available network.
i. The system shall be equipped with IR Illuminator to ensure clear images including illumination of the Number Plate and capture the violation image under low light conditions and night time.
4 Recording & display information archive medium
a. The recording and display of information should be detailed on the snapshot of the infracting vehicle as follows:
b. Computer generated unique ID of each violation
c. Date (DD/MM/YYYY)
d. Time (HH:MM:SS)
e. Equipment ID
f. Location ID
g. Carriageway or direction of violating vehicle
h. Type of Violation (Signal/Stop Line)
i. Lane Number of violating vehicle
j. Time into Red/Green/Amber
k. Registration Number of violating vehicle
5 On site-out station processing unit communication & Electrical Interface
a. The system should automatically reset in the event of a program hang up and restart on a button press.
b. The system should have secure access mechanism for validation of authorized personnel.
c. Deletion or addition and transfer of data should only be permitted to authorized users.
d. A log of all user activities should be maintained in the system.
e. Roles and Rights of users should be defined in the system as per the requirements of the client
169
f. All formats of the stored data with respect to the infractions should be Non Proprietary.
g. The communication between the on-site outstation processing unit housed in the junction box and the detection systems mounted on the cantilever shall be through appropriate secured technology.
h. The system should have the capability to transfer the data to Police Command Centre through proper encryption in real time and batch mode for verification of the infraction and processing of challan. Call forwarding architecture shall be followed to avoid any data loss during transfer.
i. In the event that the connectivity to the CCC is not established due to network/connectivity failures, then all data pertaining to the infraction shall be stored on site and will be transferred once the connectivity is re- established automatically. There shall also be a facility of physical transfer of data on portable device whenever required. There should be a provision to store minimum one week of data at each site on a 24x7 basis.
6 Mounting structure
a. Should be cantilever mounted and shall have minimum 6 meters height with appropriate vertical clearance under the system from the Road surface to ensure no obstruction to vehicular traffic.
b. It should be capable to withstand high wind speeds and for structural safety, the successful bidder has to provide structural safety certificate from qualified structural engineers approved/ certified by Govt. Agency.
c. It shall be painted with one coat of primer and two coats of PU paint. The equipment including poles, mountings should have an aesthetic feel keeping in mind the standards road Infrastructure (e.g. Poles, Navigation boards etc.) currently installed at these locations. The equipment should look “one” with the surroundings of the location and not look out of place.
d. Rugged locking mechanism should be provided for the onsite enclosures and cabinets.
7 RLVD Application
a. It should be capable of importing violation data for storage in database server which should also be available to the Operator for viewing and retrieving the violation images and data for further processing. The program should allow for viewing, sorting, transfer & printing of violation data.
b. It should generate the photograph of violations captured by the outstation system which include a wider view covering the violating vehicle with its surrounding and a closer view indicating readable registration number plate patch of the violating vehicle or its web link on notices for court evidence.
c. All outstation units should be configurable using the software at the Central Location.
d. Violation retrieval could be sorted by date, time, location and vehicle registration number and the data structure should be
170
compatible with Raipur Police database structure. It should also be possible to carry out recursive search and wild card search.
e. The operator at the back office should be able to get an alarm of all fault(s) occurring at the camera site (e.g. sensor failure, camera failure, failure of linkage with traffic signal, connectivity failure, Camera tampering, sensor tampering).
f. The automatic number plate recognition Software will be part of the supplied system, Success rate of ANPR will be taken as 80% or better during the day time and 60% or better during the night time with a standard number plate.
g. The application software should be integrated with the E Challan software for tracing the ownership details of the violating vehicle and issuing/printing notices. Any updates of the software (OS, Application Software including any proprietary software), shall be updated free of cost during the contract period by the SI.
h. Image zoom function for number plate and images should be provided. In case the number plate of the infracting vehicle is readable only through the magnifier then in such cases the printing should be possible along with the magnified image.
i. Various users should be able to access the system using single sign on and should be role based. Different roles which could be defined (to be finalized at the stage of SRS) could be Administrator, Supervisor, Officer, Operator, etc.
j. Apart from role based access, the system should also be able to define access based on location.
k. Rights to different modules / Sub-Modules / Functionalities should be role based and proper log report should be maintained by the system for such access.
l. Components of the architecture must provide redundancy and ensure that there are no single points of failure in the key project components. Considering the high sensitivity of the system, design shall be in such a way as to be resilient to technological sabotage. To take care of remote failure, the systems need to be configured to mask and recover with minimum outage.
m. The architecture must adopt an end-to-end security model that protects data and the infrastructure from malicious attacks, theft etc. Provisions for security of field equipment as well as protection of the software system from hackers and other threats shall be a part of the proposed system. Using Firewalls and Intrusion detection systems such attacks and theft shall be controlled and well supported (and implemented) with the security policy. The virus and worms attacks shall be well defended with Gateway level Anti-virus system, along with workstation level Anti-virus mechanism. There shall also be an endeavour to make use of the SSL/VPN technologies to have secured communication between Applications and its end users. Furthermore, all the system logs shall be properly stored & archived for future analysis and forensics whenever desired.
n. The evidence of Infraction should be encrypted and protected
171
so that any tampering can be detected.
o. Ease of configuration, ongoing health monitoring, and failure detection are vital to the goals of scalability, availability, and security and must be able to match the growth of the environment.
p. System shall use open standards and protocols to the extent possible and declare the proprietary software wherever used.
q. The user interface should be user friendly and provide facility to user for viewing, sorting and printing violations. The software should also be capable of generating query based statistical reports on the violation data.
r. The data provided for authentication of violations should be in an easy to use format as per the requirements of user.
s. User should be provided with means of listing the invalid violations along with the reason(s) of invalidation without deleting the record(s).
t. Basic image manipulation tools (zoom etc.) should be provided for the displayed image but the actual recorded image should never change.
u. Log of user actions be maintained in read only mode. User should be provided with the password and ID to access the system along with user type (admin, user).
v. Image should have a header/footer depicting the information about the site IP and violation details like date, time, equipment ID, location ID, Unique ID of each violation, lane number, registration. Number of violating vehicle and actual violation of violating vehicle etc. so that the complete lane wise junction behaviour is recorded including (Red Light violation and Stop Line Violation)
w. Number plate should be readable automatically by the software/interface. There should be user interface for simultaneous manual authentication / correction and saving as well.
x. Interface for taking prints of the violations
6.2.17.8 ANPR and RLVD cameras Hardware specification for covering all the arms & lanes
Sr. No. Features Specification Compliance (Y/N)
Offered Specification with Document Proof
1 Image sensor 1/2.5" or 1/1.8” Progressive Scan CMOS 5MP
2 Lens C/CS Mount Detachable type lens default with 5~50 mm, DC‐iris or P-iris,
3 WDR True WDR 120 db or better
4 HLC Should support HLC with adjustable settings
5 Min. Illumination Color mode: 0.05 low lux and B&W mode: 0.01 lux, 0 LUX With IR ON
6 Electronic Shutter 1/25-1/100000s or better, Auto/Manual Adjustment
172
7 Video Compression MJPEG, H.264, H. 265
8 Streaming Support Individually configurable 3 video streams (H.264/H.265), Unicast/ Multicast
9 Resolutions and frame rates
Max: 30 fps at 2592x1944, 25/30 fps at 2592X1520, 25/30 fps at 2560x1440, 50/60 fps at 1920x1080, 50/60 fps at 1280x960, 50/60 fps at 1280x720, Min : 50/60 fps at 480x240
10 Protocol Support IPv4,IPv6, HTTP, HTTPS, 802.1X, QoS, FTP, SMTP, UPnP, SNMP, DNS, DDNS, NTP, RTSP, RTP, TCP, UDP, IGMP, ICMP, DHCP
11 Network Security Should support IP and Mac conflict detection, access control list
12 Intelligent Video
Motion Detection, Camera Tampering detection, Zone Intrusion detection, Perimeter intrusion detection, Object counting, Trip wire detection
13 Behaviour analysis Line crossing detection, Missing object detection, Face detection, crowd detection
14 Video detection Scene change detection, image defocus detection
15 Corridor Mode Support 9:16 aspect ratio for narrow corridors, hallways or aisles.
16 image stabilization should support electronic image stabilization
17 Privacy Mask Support Minimum 4 areas / Zones
18 OSD Should support OSD of Camera Name, Time, Date, week, Location, etc
19 Image setting
Image Defog, ROI, BLC, Flicker Control, White Balance 3DNR, Image enhancement, lens correction, Auto Exposure control, Automatic gain control, Hue, automatic noise reduction, Automatic dead pixel cancelling, Watermark
20 Viewing/configuration
Support IE Browser/VMS/NVR and IOS/Android/windows
21 Audio Function Camera Should support 2 way audio and should have audio in/out interfaces
22 Internal Edge Storage
Camera should support Micro SD/SDHC/SDXC memory card for edge recording and support up to 128GB Capacity, Schedule and Event Recording, Support pre-post alarm buffer recording, configurable free disk management. 128GB Memory card must be loaded on each camera for Edge level recording.
23 Edge Storage Auto Backup
Camera should record automatically when VMS not reachable and sync back to VMS
173
when link restored
24 Alarm interface Camera Should support 1ch alarm in and 1ch alarm out
25 Interface 10/100BaseT or better RJ45 Port
26 POE Internal 802.3af POE Support
27 ONVIF compliance ONVIF version 2.4 or better and ONVIF Profile S compliant
28 Time and Date
When camera reboots or powered ON after long time, the time and date of camera should remain same as per last configured without any update or synchronization required using NVR or internet
29 Certification
CE, FCC, UL, cUL, ROHS, UL 60950-1, BIS Direct UL Test report to be submitted for the product and brand (should not be an UL Multi listed certificate or report, UL verification letter to be submitted along with bid for non multi listing)
30 Test Reports
Complete UL test report must be submitted with the following standards tested by UL such as UL 60950-1, CAN/CSA, 60950-1-07, 60950-22, 60529, 60068-2-11 Should submit complete test report of IS 13252(Part 1): 2010+A1: 2013+A2: 2015 from NABL approved Lab
31 Operating Temperature -10 to 60 °C, or better
32 Surge Protection Minimum 2Kva surge protection should be included with each camera
33 Outdoor Housing
Suitable outdoor IP66 Housing should be added along with Heater, Fan. Mounting bracket must be included. Housing and mounting bracket should be cable through design The outdoor housing should be full strong metal which can protect against vandalism For ANPR Cameras Additionally one High Power 150M External IR illuminator shall be integrated with Camera to have clear View of Number plate during High Beam lights at night. Camera Housing, Mounting bracket and IR illuminator should be same brand as Camera OEM.
6.2.17.9 Local Processing unit/industrial grade Server for ANPR & RLVD
S.No Features Description Compliance (Y/N)
Offered Specification with
174
Document Proof
1
Type High end Processing unit with high performance Industrial Grade, support din rail kit. Full Aluminum Industrial fan less embedded server
2
Main Processor Intel i7 latest 8th Gen 6 core or Xeon Gold 6 core processor, 9MB processor cache. Minimum 3Gz and max support up to 4Gz or better Fan less design
3 Motherboard OEM Motherboard & Compatible 64 bit Chipset
4 RAM Default 8GB DDR4 Workstation RAM, dual channel, Scalable to 32 GB
5 Power supply Power supply with industrial grade components.
6
Interface 6 x USB 3.0, 2 x USB 2.0, 1x 2.5” SATA/SSD HDD BAY, (2TB SFF Hard disk must be loaded ) 2 x 485 COM port, 4x RS232 COM port, 1 x Audio Line-in, 1 x Audio Line-out, 1 x MIC-in jack On Board 1 x M.2 Socket Onboard SIM Card slot support
7 LAN 2x 10/100/1000 Gigabit Lan Port, Support load balancing and failover,
8 Display 1x Display Port support 4K Resolution 1x HDMI Port support 4K Resolution
9 OS Support Windows and Linux, required OS to be loaded.
10 Accessories Wall mount kit, Din rail kit for industrial mount,
11 Temperature & environment
Operating Temperature: 0 ~ 65°C Storage Temperature: -20 ~ 85°C Support IP20 or better rating
12 Certifications
CE, FCC, ROHS OEM should have ISO 9001, ISO 14001 and ISO 27001 certified OEM should have toll free number and Service center in India
6.2.18 AD Panels
S. No Parameter Specifications Compliance (Y/N)
Offered Specification with Document Proof
Parameter Specifications
1 Display Size (W x H)
Minimum 0.96 m x 1.92m or bigger
2 Pixel Pitch 10 mm or better (Lower pitch is regarded
175
as better) 3 LED
Configuration RGB 3 in 1 SMD
4 Pixel Density Minimum 10,000 pixels per sqm or higher
5 Half Gain Horizontal / Vertical Viewing Angle
H 140 deg / V 90 deg or better
6 Refresh Rate >960 Hz or better
7 Temp Range -20 to +50 Degrees C or better
8 Gray Scale Processing
12 Bit or better
9 Brightness (Calibrated)
5000 cd/m² or better
10 Maximum Power Consumption
850 w/sqm or lower
11 Dimming Capability
255 levels
12 Power Input 100 ~ 240 VAC
13 Individual Tile/Cabinet Dimensions
960 mm ( W) x 960 mm ( H) x 143 mm ( D)
14 Contrast Ratio 3000:1 or better
15 Access For Maintenance
Rear
16 IP Level Front IP65 / Rear IP54
17
International Safety Certifications( Mandatory to submit along with the bid)
CE certification for Compliance to CE Under Standards : EN 55022:2010 + AC:2011 Class A, EN 55024:2010+A1:2015, EN 61000-3-2:2014, EN 61000-3-3:2013, AS/NZS CISPR 22:2009+A1:2010
UL Listed for Compliance to UL Standard For Safety : UL 60950-1 & CAN/CSA C22.2 No. 60950-1-07- Information Technology Equipment-Safety-Part 1: General Requirements
FCC Certification for Compliance to FCC For Electro Magnetic Emission which may not cause harmful interference, and must not accept any interference received Under Standard : FCC CFR Title 47 Part 15 Subpart B: 2015 Class A, CISPR 22:2008, ANSI C63.4:2014, ICES-003 Issue 6:2016 : Class A
BIS Registration ( Bureau Of Indian Standards) As per Standard : IS 13252( PART 1) :2010
176
CB Certification for Compliance to CB Standard for Safety : EN 60950-1:2006/A11:2009/A1:2010/A12:2011/A2:2013, IEC 60950-1(ed.2), IEC-1(ed.2);am1, IEC 60950-1(ed.2);am2
18 Quality/Health & Safety/Environmental Certifications of OEM/OEM subsidiary in India ( Copy to be submitted along with the bid
Quality Management System 9001:2015 ,
Occupation health & Safety Management System - OHSAS 18001:2007 ,
Environmental Management System 14001: 2015
19 LED package vendor acceptable makes(certificate from the LED package vendor to be provided during the supply certifying the same)
Cree /Nichia/Nationstar or Equivalent
20 Installations by OEM
OEM should have at least 250 nos installations of outdoor LED wall in a single network with content being published centrally and control also being done centrally. Proof of this should be submitted. Size of these installs should be similar or bigger and should be in India running for at least one year successfully.
21 OEM Registered Office in India
OEM should have a registered office in India for minimum 5 years from this tender.
6.2.18.1 Rack Frame Power Distribution Unit
An IP 54 rack shall be provided. The rack shall be at least 13 U high with a provision to mount 19" wide equipment.
S. No Parameter
Specifications Compliance
(Y/N) Offered Specification with Document Proof
1 Front Door 2 Hinges with Rack & Aircon bolted
2 Wall Mount Clamp Welded on Rack frame rear side
3 19" pillar front & 19" pillar rear Bolted on rack side wall
177
4 Locking Arrangement To be provided with a locking system
5 Limit Switch
The rack door to be provided with a limit switch
6 Earthing
Earthing studs should be provided in the rack for earthing purposes
7 Cable points
Cable entry and exit points should be provided in the rack
8
Mounting
Should be possible to mount the rack either on a pole or on a wall with options of different mounting types
9 Rack Internal size 13U 19" rack
10 AC input 380V/220V
11 AC Power Load Max 45KW
12 AC power Load Max Each output
5KW
13 Surge protection Class C
6.2.18.2 LED Processor
S. No Parameter
Specifications Compliance
(Y/N) Offered Specification with Document Proof
1 Loading Capacity
1.3 Million pixels
2 Processing capability
1.5 Ghz 8 core
3 Operating Memory
2GB
4 Onboard internal storage
8 GB with at least 4 GB for usage
5 Inputs HDMI, USB and Gigabit Ethernet
6 Operating Temperature
As per requirement
6.2.18.3 Item 4: Mechanical Structure For Mounting Of LED Walls
S. No Parameter Specifications Compliance (Y/N)
Offered Specification with Document Proof
1 Mounting Structure
LED wall should be mounted on the wall.
2 Material Should be made from mild steel and painted black along with antirust coating.
178
6.2.18.4 Content Management Server with Software
S. No Parameter Specifications Compliance (Y/N)
Offered Specification with Document Proof
1 Signage & Content Manager (Software & Hardware)
To be able to create playlists and send them over the network to 200 media players or more for playout based on schedule and sequencing.
2 License support The license of the software should support
management of more than 200 video walls
3 Playlist Automation Flexible scheduling Playlist Scheduling;
4 Content Distribution
Scalable, simultaneous publishing, at least 200 simultaneous subscribers
5 Content Management Design simplified user interfaces
6.2.18.5 Auto Brightness Sensor
S. No Parameter Specifications Compliance (Y/N)
Offered Specification with Document Proof
1 Rated voltage 5V
2 Operating temperature
As per city requirement
3 As per city requirement
As per city requirement
4 Brightness range
0~65535 lux
5 Cable 5m
6 Features Monitor the ambient brightness to achieve automatic brightness adjustment of LED display Outdoor use proofing No external power supply required
=
6.2.19 IP based Public Address System – Functional
S. No Broadcasting System Control Server Software Compliance (Y/N)
Offered Specification with Document Proof
179
The Software should be centralized server based system, it centrally manages all audio terminals in the system, including paging MIC, intercom terminal, broadcasting terminal and fire interface device, and real-time show operating conditions of audio terminals like IP address, online condition, task condition and volume, etc.
1 Software manages Support
Should manage all audio terminals, Including paging Mic, Intercom terminal, Broadcasting Terminal, Fire interface Device, Real time operating condition of audio terminal
2 Software Manages source
Provide timing Broadcast and real time VOD for all audio terminals
3 Calling Strategy
Support multiple Calling Strategy (Calling hold on, Calling Transfer, Nobody answer guidance,) Support caller ringtone and waiting ring tone
4 Central management
Supports centrally manage terminals login password, Multiple Priority Management and automatic authority
5 Partition Management
Support partition management of multiple users and arbitrary degree achieve remote broadcast .
6 Should support customize bell, bell cloning, task execution and stop control, disable and enable function of timing task.
7 Should Support customize bell, bell cloning, task execution and stop control, disable and enable function of timing task.
8 Should Support whole area, partition area fire linkage, support N+N fire mode, support artificial alarm and digital alarm mixing
9 Should Support 3, 4-wire volume control strong cut function of terminal, (4-wire volume control requires external power supply).
10 Should Support 5-band equalizer adjustment for terminal , it supports 80Hz, 300Hz, 1KHz, 3KHz, 10KHz frequency +16dB adjustment.
11 Should supports setting different lighting modes for terminals. It can customize the setting of red light, red light, green light and green light out time of 0.1S-10S.
12 Support recording for broadcasting, intercom, real-time collection and terminal monitor
180
13
Support remote control and on demand programs function. Support terminal audio collecting and broadcasting programs function. Support local audio collection function, Play to any designated terminal, Supports text-to-voice broadcasting function; it can set speech rate, male/female voice. Support local audio collection function, Play to any designated terminal. Support offline timing bell, When disconnected from the network, the terminal is managed to perform regular ringing tasks
14 Should Support mobile phone on demand, broadcast and intercom function with Wi-Fi, also can be compatible with Android and IOS system App.
15 Should Support timing system which is highly based on GPS, to make it separably offline system timing, to enable time error of system less than 1/300000 sec
16 System is compatible with arbitrary network structure, such as router, switch, gateway and bridge, 3G, 4G, multicast, unicast, etc.
17 Should able to record system operation, calling, broadcasting and all type of communications.
6.2.19.1 Desktop Intercom Paging Microphone with touch screen
S. No Desktop Intercom Paging Microphone with touch screen Compliance (Y/N)
Offered Specification with Document Proof
1 Display Size & resolution 6.8”inch & 720x480 Pixel or better
2 Screen type 64K color digital touch screen
3 Keyboard Type Virtual QWERTY.
4 Sampling Rate 8K~48KHZ or better
5 Audio Format MP3, Built in 2W full frequency hi-fi speaker
6 Transmission Speed 100Mbps
7 Audio mode 16-Bit Cd sound quality
8 Support protocol TCP/IP, UDP, IGMP (multicast)
9 Network Interface RJ45 port
10 Inscribed Speaker impedance power rating 4Ω, 2W
11 THD ≤1%
12 Phone OUT output Speaker impedance power rating
16Ω, 2mW
13 Line Out Output Level 1000mV Industry standard Wire Terminals
14 Line Out Output impedance 470Ω
181
15 `Line IN input sensitivity 350mV Industry standard Wire Terminals
16 MIC Input sensitivity 10mV
17 Short Circuit Input Dry contact Input
18 Short Circuit Output Max 1A/20VDC Dry contact Input
19 Working Temperature 5°C~ 40°C
20 Working Moisture 20%-80% Relative humidity, No condensation
21 Working Consumption ≤6W
22 Power Input -190-240V 50-60Hz ( power Adapter); DC24V/2A
23 Size & weight 200x158x163mm & 1.2kg
24 Support Application LAN, WAN, compatible with any 2G,3G, 4G, internet, Modem
25 Support Functions Full Duplex Two-way intercom Function, Automatic answer, One Key accept, Support multiple Paging mode.
26 Audio function Should support built-in echo cancellation, 2 way intercom, multiple zone support, etc.
27 Call functions
Should support call forwarding, call waiting, no answer, manual answering, auto answering, page waiting, page forwarding, etc.
6.2.19.2 Outdoor IP Based smart speakers
S. No IP Network Column Speaker Compliance (Y/N)
Offered Specification with Document Proof
1 Audio Format MP3, built in power amplifier Module
2 Transmission Speed 100Mbps
3 Audio mode 16-Bit Cd sound quality
4 Support protocol TCP/IP, UDP
5 Network Interface RJ45 port
6 Support Application LAN, WAN, compatible with any 2G,3G, 4G, internet, Modem
7 Total gear Wave Distortion Less than 1%
8 Frequency Response 130Hz~16Hz+1dB/-3dB
9 SNR More than 65dB
10 Protection Level IP54
11 Working temperature -20°C~ 60°C
12 Working Humidity 20%-80% Relative humidity, No condensation
182
13 Working Voltage -220V 50Hz
14 Rated Power 60W
15 Overall power Consumption Less than 95W
16 Speaker Unit 4”x4
17 Size 814x150145mm
18 Weight 7.5Kg
19 Security Encryption User name& password
20 Control Function Support 100 self-defined audio priority silence
21 Certifications
CE, FCC, ROHS OEM should have ISO 9001, ISO 14001 and ISO 27001 certified OEM should have toll free number and Service center in India OEM should have direct registered company in India for last 5 years
6.2.20 Emergency Call Box – Functional
Field Side Equipment Compliance
S.No Parameter Compliance (Y/N)
Offered Specification with Document Proof
1 Construction: Cast Iron/Steel Foundation, Sturdy Body for equipment
2 Call Button: Watertight Large Push Button, Visual Feedback for button press
3 Connectivity: GSM/RF/PSTN/Ethernet as per solution offered
4 Sensors: For tempering/ vandalism
5 IP66, IK09 Protection
6 Operating Temperature 0 to 70 C
7 Speaking Distance minimum 5 ft
8 Inbuilt Class D Amplifier
9 Minimum 3 Inputs ad 2 Output relay contacts
10 ECB should be able to make calls to the PA system
11 Central Software based server application capable of working on virtual environment/cloud with 100% redundancy
12 Access control mechanism would be also required to establish so that the usage is regulated.
183
13 Integration with VaMS and Command and control centre or any other component if required
14 PA Master Controller to have facility for multiple mic inputs, direct dialing buttons, LCD screen
15 Software Client for making Calls to PA and ECB
16 Automatic Volume Control
17 Transmission bandwidth16000 KHz
18 Operating temperature for control desk 0 to +60C
19 Certifications - CE, FCC, ROHS OEM should have ISO 9001, ISO 14001 and ISO 27001 certified OEM should have toll free number and Service center in India
6.2.21 City Surveillance
6.2.21.1 BOX Camera
Fixed Cameras along with Complete mounting accessories (for general surveillance)
Sr. No. Features Specification Compliance (Y/N)
Offered Specification with Document Proof
1 Image sensor 1/2.5" or 1/1.8” Progressive Scan CMOS 5MP
2 Lens Min 2.8~12 mm Varifocal Motorized Lens, DC‐iris or P-iris, Auto Focus
3 IR Range Support 50 Mtr internal/external
4 WDR True WDR 120 db or better
5 HLC Should support HLC with adjustable settings
6 Min. Illumination Color mode: 0.05 lux and B&W mode: 0.01 lux, 0 LUX With IR ON
7 Electronic Shutter 1/25-1/100000s or better, Auto/Manual Adjustment
8 Video Compression MJPEG, H.264, H. 265
9 Streaming Support Individually configurable 3 video streams (H.264/H.265), Unicast/ Multicast
10 Resolutions and frame rates
Max: 30 fps at 2592x1944, 25/30 fps at 2592X1520, 25/30 fps at 2560x1440, 25/30 fps at 1920x1080, 25/30 fps at 1280x960, 25/30 fps at 1280x720, Min : 25/30 fps at 480x240
11 Protocol Support IPv4,IPv6, HTTP, HTTPS, 802.1X, QoS, FTP, SMTP, UPnP, SNMP, DNS, DDNS,
184
NTP, RTSP, RTP, TCP, UDP, IGMP, ICMP, DHCP
12 Network Security Should support IP and Mac conflict detection, access control list
13 Intelligent Video
Motion Detection, Camera Tampering detection, Zone Intrusion detection, Perimeter intrusion detection, Object counting, Trip wire detection
14 Behavior analysis Line crossing detection, Missing object detection, Face detection, Crowd detection
15 Video detection Scene change detection, image defocus detection
16 Corridor Mode Support 9:16 aspect ratio for narrow corridors, hallways or aisles.
17 Image stabilization Should support electronic image stabilization
18 Privacy Mask Support Minimum 4 areas / Zones
19 OSD Should support OSD of Camera Name, Time, Date, week, Location, etc
20 Image setting
Image Defog, ROI, BLC, Flicker Control, White Balance, 3DNR, Image enhancement, lens correction, Auto Exposure control, Automatic gain control, Hue, automatic noise reduction, Automatic dead pixel cancelling, Watermark
21 Viewing/configuration Support IE Browser/VMS/NVR and IOS/Android/windows
22 Audio Function Camera Should support 2 way audio and should have audio in/out interfaces
23 Internal Edge Storage
Camera should support Micro SD/SDHC/SDXC memory card for edge recording and support up to 128GB Capacity, Schedule and Event Recording, Support pre-post alarm buffer recording, configurable free disk management 128GB Memory card must be loaded on each camera for edge level Storage
24 Edge Storage Auto Backup
Camera should record automatically when NVR not reachable and support automatic Synchronization of backup recording form SD Card to NVR when connection resume
25 Alarm interface Camera Should support 1ch alarm in and 1ch alarm out
185
26 Interface 10/100BaseT or better RJ45 Port
27 POE Redundant: Internal PoE /PoE+(802.3 af/at) and AC 24V/ DC12V/ 100‐ 230VAC
28 Environment Protection IP 67 Rated Housing
29 Housing Full Metal housing with Mounting bracket included for Wall/Ceiling Mount
30 Integration tools SDK, CGI, API or other integration related files to be provided for any integration requirement
31 ONVIF compliance ONVIF version 2.4 or better and ONVIF Profile S compliant
32 Time and Date
When camera reboots or powered ON after long time, the time and date of camera should remain same as per last configured without any update or synchronization required using NVR or internet
33 Certification
CE, FCC, UL, cUL, ROHS, UL 60950-1, BIS Direct UL Test report to be submitted for the product and brand (should not be an UL Multi listed certificate or report, UL verification letter to be submitted along with bid for non multi listing)
34 Test Reports
Complete UL test report must be submitted with the following standards tested by UL such as UL 60950-1, CAN/CSA, 60950-1-07, 60950-22, 60529, 60068-2-11 Should submit complete test report of IS 13252(Part 1): 2010+A1: 2013+A2: 2015 from NABL approved Lab
35 Operating Temperature -10 to 60 °C, or better
36 Surge Protection Minimum 2Kva surge protection should be included with each camera
6.2.21.2 Surveillance PTZ Camera
PTZ Cameras System with Complete mounting accessories
Sr. No. Features Specification Compliance (Y/N)
Offered Specification with Document Proof
1 Image sensor 1/2.8" Progressive Scan CMOS 2MP or
186
better
2 Zoom 32x Optical Zoom and 12x Digital Zoom or better
3 Lens
Focal Length Min 4.7 to 152 mm or Longer focal length, Auto Focus, Remote optical zoom, Support Manual focus and IRIS Control
4 Pan/Tilt Range Pan: 0° ~ 360° endless; Tilt: 0° ~ 90°, auto flip 180°
5 Manual Control Speed Pan: 0.1° ~240° /s; Tilt: 0.1° ~240° /s or better
6 Preset Speed Pan: 240° /s; Tilt: 240° /s or better
7 Presets Minimum 300 Preset Points
8 IR Range Min 150 Mtr or better
9 WDR True WDR 120 db or better
10 HLC Should support HLC with adjustable settings
11 Min. Illumination Color mode: F1.2 @ 0.002 lux and B&W mode: F1.2@ 0.001 lux or better
12 Electronic Shutter 1/25-1/100000s or better, Auto/Manual Adjustment
13 Video Compression H.264, H. 265, MJPEG
14 Streaming Support Individually configurable 3 video streams (H.264/H.265), Unicast/ Multicast
15 Resolutions and frame rates
Max: 50/60 fps at 1920x1080, 50/60 fps at 1280x960, 50/60 fps at 1280x720 Min : 50/60 fps at 704x576, 50/60 fps at 352x288
16 Protocol Support
IPv4,IPv6, HTTP, HTTPS, 802.1X, QoS, FTP, SMTP, UPnP, SNMP, DNS, DDNS, NTP, RTSP, RTP, TCP, UDP, IGMP, ICMP, DHCP
17 Network Security Should support IP and Mac conflict detection, access control list
18 Intelligent Video
Motion Detection, Camera Tampering detection, Zone Intrusion detection, Perimeter intrusion detection, Object counting, Trip wire detection
19 Behavior analysis
Line crossing detection, unattended object detection, Missing object detection, Zone entrance detection, Zone exiting detection, People Counting, Loitering detection, Crowd detection
20 Video detection Scene change detection, image defocus detection
187
21 Corridor Mode Support 9:16 aspect ratio for narrow corridors, hallways or aisles.
22 image stabilization should support electronic image stabilization
23 Privacy Mask Support Minimum 24 areas / Zones, Support Dynamic Privacy Mask
24 OSD Should support OSD of Camera Name, Time, Date, week, Location, etc
25 Image setting
Image Defog, ROI, BLC, Flicker Control, White Balance, 3DNR, Image enhancement, lens correction, Auto Exposure control, Automatic gain control, Hue, automatic noise reduction, Automatic dead pixel cancelling, Watermark
26 Viewing/configuration Support IE Browser/VMS/NVR and IOS/Android/windows
27 Audio Function Camera Should support 2 way audio and should have audio in/out interfaces
28 Internal Edge Storage
Camera should support Micro SD/SDHC/SDXC memory card for edge recording and support up to 128GB Capacity, Schedule and Event Recording, Support pre-post alarm buffer recording, configurable free disk management 128GB Memory card must be loaded on each camera for edge level Storage
29 Edge Storage Auto Backup
Camera should record automatically when NVR not reachable and support automatic Synchronization of backup recording form SD Card to NVR when connection resume
30 Alarm interface Camera Should support 1ch alarm in and 1ch alarm out
31 Interface 10/100BaseT or better RJ45 Port
32 Power
Internal PoE /PoE+(802.3 af/at) and AC 24V/ DC12V/ 100‐ 230VAC, Dual redundant power supply support (Hi-POE not acceptable )
33 Environment Protection IP 67 Rated certified by UL for all PTZ Cameras
34 Housing Full Metal housing with Mounting bracket included for Wall/Pole Mount
35 ONVIF compliance ONVIF version 2.4 or better and ONVIF Profile S compliant
36 Time and Date When camera reboots or powered ON
188
after long time, the time and date of camera should remain same as per last configured without any update or synchronization required using NVR or internet
37 Certification
CE, FCC, UL, cUL, ROHS, UL 60950-1, BIS Direct UL Test report to be submitted for the product and brand (should not be an UL Multi listed certificate or report, UL verification letter to be submitted along with bid for non multi listing)
38 Test Reports
Complete UL test report must be submitted with the following standards tested by UL such as UL 60950-1, CAN/CSA, 60950-1-07, 60950-22, 60529, 60068-2-11 Should submit complete test report of IS 13252(Part 1): 2010+A1: 2013+A2: 2015 from NABL approved Lab
39 Operating Temperature -10 to 60 °C, or better
40 Surge Protection Minimum 2Kva surge protection should be included with each camera
41 Auto Tracking Shall support Auto Tracking and smart Tracking
6.2.22 Smart Sensors
6.2.22.1 Technical Specifications – Pollution / Environmental Sensors
S. No Parameter Specification Compliance (Y/N)
Offered Specification with Document Proof
1. Measurement principle Temperature, Humidity, Ambient Light, Sound, CO, NO2, CO2, SO2
2.
Measurement component Measurement range
NO2: 0 to 10 ppm SO2 : 0 to 500 ppm CO : 0 to 50ppm, 5000ppm O3: up to 1000 ppb CO2 : 0 to 10% / 0 to 20% PM 2.5: 0 to 230 micro gms / cu.m PM 10: 0 to 450 micro gms / cu.m Light: up to 10,000 Lux UV: up to 15 mW/ cm2 Noise: up to 120 dB (A)
189
3. Repeatability ±0.5% FS
4.
Temperature and Humidity Sensor
Real-time Temperature Range: Indoor -10ºC ~ +70ºC (+14ºF ~ +122ºF) Real-time in Air Humidity Level Display (up to 100%)
5. Response speed 120 seconds max. for 90% response from the analyzer inlet
6. Connectivity (Minimum) USB / Ethernet connectively to graphical display
6.2.22.2 Technical Specifications – Rain Gauges Sensor
S. No Parameter Specification Compliance (Y/N)
Offered Specification with Document Proof
1. Measurement principle Rainfall
2. Rain Water measurement
Rainfall in millimetres (mm)
3. Accuracy ± 2% at 0 mm/hr to 250 mm/hr ± 3% at 250 mm/hr to 500 mm/hr
6.3 Hand Held based E-Challans
The proposed system should be a comprehensive digital solution for Transport enforcement wing and
Traffic Police delivered. The system should capture all challans information by infield officer using
android device at the time of violation and capture information will be sync to centralized server.
The system should be integrated with Vahan and Sarathi applications and provide a number of user-
friendly features, covering all major functionalities of Enforcement System. An end to end digital
solution for multiple stakeholders: ease of operations for Transport Enforcement Officers/Traffic
Policemen, increased visibility in operations for the State and improved support in maintaining
compliance for citizens should be considered.
9.3.1 Functional Requirements
S. No Functionalities of Handheld based E-challan system.
1 E-challan software for handheld machines shall work in client- server mode, where the devices units, workstation units will act as clients connected to the server through cellular network for data transfer
190
2 E-challan system shall be able to retrieve vehicle owner’s details and vehicle data from RTO/VAHAN/SARTHI data base to minimize data entry.
3 E-challan system shall be able to retrieve vehicle system registration details and driving license details by reading appropriate smart card to minimize data entry.
4 Server should maintain log of all current devices. Any access to the system must be recorded along with data, time user id and IP address.
5 Traffic officer should log in to the hand-held device through the unique user id and password or smart card issued
6 A unique Challan number should be generated through client software for each challan.
7 As soon as a vehicle registration number is entered, the handheld device should automatically check from the server if the vehicle is stolen, wanted in any criminal case or is in the list of suspicious vehicles.
8 The most frequent traffic offences should be kept at the top of the drop-down menu and offence ingredients should be available if required by officer.
9 Date, time and GPS coordinates of place of challan should be automatically populated in the relevant fields of client software.
10 Compounding amount must populate in the field automatically from master table.
11 GUI should be developed as per functional requirements.
12 It should be possible to integrate payment gate way operator with the system for facilitation of payment.
13 The Application Software should work in a web based environment.
14 The application software should be user friendly, easy to operate.
15 The system will function in web based system where the hand-held device shall work as a node.
16 The application software should maintain the logs of user activities to facilitate the audit trail.
17 Database server should be able to handle the activities of all the handheld devices at one time simultaneously with huge database size of prosecution, ownerships, driving license etc. without affecting the performance.
18 The software should be able to generate various periodical reports, summaries, MIS reports, query reply etc. as per the requirements.
19 Administrator should be able to modify the master tables as and when required and should have the capability to push the changes to hand –held devices.
191
20 All database tables, records etc. required for various dropdown menus etc. shall also be created by the vendor
21 In case no network connectivity , Hand held devices shall work in Local mode and shall be designed to operate to capture Challans generated in a day. Once the network is restored, device shall connect back to the backend system and shall upload the transactions which were locally stored
22 In case of speed violations and regular offender identification by ANPR system, E-challan central system shall send alert and SMS to nearby officer using geofence – In Future
23 It shall be possible to share the violation details from the central TMMC application to handheld device with necessary violation details and supporting proofs( video/images)
24 A holistic challan system with Automatic central challaning and handheld based e challaning system should be provided. Both the systems should be integrated with the database server for efficient operations and consolidated reporting
6.4 Automatic E Challan & Centralized monitoring
Functional Requirements of the e-Challan application:
The objective of the e-Challan application is as follows:
1. Issuing challan for traffic violations on a 24x7 basis
2. Maintaining the details pertaining to all the activities of the Traffic circles/violations/violators
3. Providing requisite structured/unstructured information to the traffic management officials as and
when required.
4. Generating various statutory reports for the administrative use and functioning of the Traffic unit
in matters of prosecution of violators and monitoring the functioning of field officers.
5. Integrating and networking the system with state-of-the-art hardware and application software
for the Traffic Police to access and using the information in their day-to-day work.
E-Challan System 1.
The “e‐ Challan system” shall be developed based on the laws/rules of Motor Vehicle Act of
central/ state government as well as per the format of Client department. The Challan generation module will be pre-integrated with the RLVD System. The Challan
generating system will generate and print Challans for all the violation events that are duly
validated and checked by the operator. The Challan generating unit shall be able to generate
Challans in Hindi and English. The content of the Challan form shall be developed in consultation
with Jammu Traffic Police.
2 It is envisaged that system should be permissible in court of law
3 E‐Challan system should be able to automatically generate e‐challan’s based on the laws/rules of Motor Vehicle Act of central/state government for the violations detected by the surveillance
192
6.4.1 Security Provisions
A strong and comprehensive information security system based on leading standards and guidelines from
Department of Information Technology (DIT) to be followed in integration and implementation. Information
system. It should also have a provision/interface for manual e‐ challan generation for violations captured through manual level investigation of video feeds and field level.
4 The management module of the e‐ Challan system shall be hosted at the central control room where challan generation and printing shall take place
5 It should be integrated with the all the required databases/systems for auto generation of e‐Challan like RTO system, VMS system, ITMS system and other required resources.
6 Application development must be documented in detail and the code/script should be properly annotated with comments etc. The software shall be device agnostic and should potentially be able to run on the full range of devices of the same family made by multiple OEMs
7 The system should be able to generate Management Information System reports based on the type/ Date /time/Location of offences/Junctions/Thana, as may be required for the day to day activity. The application software should have the capability to export records in CSV, SQL and binary format
8 The solution should be integrated with applications such as Sarathi, Vahan, CCTNS etc.
9 e-Challan Management Software shall be open architecture software that shall integrate with Intelligent Traffic Management System applications suite offering efficient management of e-challans generated centralizeise traffic violations like red light violation, stop line violation, etc. Additionally, it shall also allows the operator to include other violations such as no helmet, triple riding, etc. as and when visually detected during the validation of challans
10 Challan Traceability • Each challan shall be identified by unique identifier for future references. • Challan shall be tagged to issuing officer's details • Shall be traceable on Vehicle number, violation category, under particular junction, paid/unpaid etc.. Challan shall have accurate date / time stamp
11 The system should provide SMS, Email /WhatsApp alert mechanism to the registered vehicle owners. Citizen should be able to pay their challans online via existing web site of JMC and future web portal of JSCL. The system should be able to provide tracking of receipts and payments of e-challans. System should automatically mark the challans PAID once the violator has completely paid their penalty amount.
12 Software up-gradation must be provided by the ITMS System Integrator from time to time as per available technology without further cost impact to Jammu Traffic Police
193
within the system should be classified as Public, Confidential and Restricted. Access to the information
should be provided based on the classification of the information.
1) The system should have provision for preventing unauthorized access and damage to
information resources.
2) The system should be accessible only after approval from application owner and the
competent authorities.
3) The access should be role based
4) The access control system should cover:
• Identification
• Authentication
• Authorization and Access Control
• Administration
• Audit
5) The system should be able to maintain access control mechanisms, data security and audit
trails to ensure that databases are not tampered or modified by unauthorized users.
6.5 Manpower
The Implementation partners shall provide adequate number of personnel, each responsible for a specific role within the project. Implementation partners shall provide clear definition of the role and responsibility of each individual personnel. Implementation partners shall have a defined hierarchy and reporting structure for various teams that shall be part of the project. Following table indicates the minimum qualification required for Key Positions identified for this project. However, Implementation partners shall independently estimate the teams size required to meet the requirements of Service Levels as specified as part of this tender.
All the below mentioned Positions shall be Onsite throughout the entire project implementation phase.
S.No Position Minimum Qualifications & Experience
1.
Project Manager
a) Education: MBA/MCA/M. Tech & B. Tech/B.E. from a recognized educational institution Experience: Minimum 10 years in IT sector. Should have more than 5 years of experience of handling such large projects as a project manager
2.
Traffic Management and Monitoring System/ Command & Communications/Control Center Expert
a) B.Tech / M.Tech/Post Graduate from a recognized educational institution
b) Experience: Minimum 7 years. Should have experience in designing & implementing Traffic violation detection and CCTV surveillance systems for minimum
2 projects of value more than INR 100 Cr. .
194
3.
Solution Architect
a) Education: MCA/M. Tech/B. Tech/B.E. from a recognized educational institution
b) Experience: Minimum 5 years in IT sector. Should have Experience of more than 5 years as a Solution Architect in large projects of similar nature
4.
QA Manager
a) B.Tech / M.Tech/MBA/MCA from a recognized educational institution
b) Experience: Should have a minimum 5 years of
Experience
5.
Data Center operations Expert
a) B.Tech / M.Tech/MBA/MCA from recognized educational institution
b) Experience: Should have a minimum 7 years of
experience in Managing Data Center Operations for a project size of more than INR 100 Cr.
6.
Technical support Engineer
c) B.Tech / M.Tech/MBA/MCA from recognized educational institution
d) Experience: Should have a minimum 4 years of experience in conducting trainings for similar applications & solutions
Apart from the above –mentioned resources, the selected implementation partners shall also propose manpower to be deployed during the Operation & Maintenance phase of the Project including but not limited to Operators for Command Center, Help desk, internal IT support team and field maintenance team.
195
7 Project Timelines
7.1 Implementation Plan
The implementation of the ITMS Project shall be undertaken in two phases, viz.
Implementation phase and Operation & Maintenance (O&M) Phase. The duration for both
phases shall be as under:
• Implementation phase - 9 months
• Operation & Maintenance UNDER Warrantee /Gaurantee phase – 36 months +60
months AMC
7.1.1 Implementation Phase
A. Implementation Phase
The ITMS System Integrator shall progressively implement the ITMS Solutions for the
scope as described in the table below:
Sl # Milestones for Implementation Phase Coverage#
1. Traffic Management
1. Junction Surveillance Locations
2. Traffic Enforcement
2. Red Light Violation Detection (RLVD) System
3. Automatic Number Plate Recognition (ANPR) System
4. VMA and VA
5. E-Challan System E-Challan Software
* The date of commissioning of complete ITMS solutions, as per the above scope, shall be
the ‘Go-Live’ date.
# Location may vary in number and place as decided by JMC/ Traffic Police.
7.1.2 Operation & Maintenance (O&M) Phase
The O&M phase shall commence from the date of “Go-Live” of ITMS solutions. The O&M
phase shall be for a period of 3 years. The ITMS System Integrator shall operate and maintain
the ITMS solutions for contract duration of three years from the date of “Go-Live”.
196
7.2 Project Timelines
The ITMS System Integrator shall be responsible for the implementation of the project within
the timelines as indicated in the table below.
Where “T” is the date of Signing of Contract between JMC and ITMS System Integrator.
Project Milestones Timelines
Implementation Phase
Signing of Contract T
Project implementation plan, Project scope approval,
Solution Design Sign-off
T + 15 days
Supply & Installation of all IT & Non-IT Infrastructure at
field locations Phase wise for all ITMS and Ad panels
T+ 90 Days
Supply & Installation of all IT & Non-IT Infrastructure, at
Command Communications Center for ITMS and Ad
panels
T+150 Days
Supply & Installation of all IT & Non-IT Infrastructure at
field locations Final Phase for all ITMS and Ad panels
T+ 180 Days
Pre-Acceptance Testing by SI and submitting Readiness
request for carrying out Final Acceptance Testing
T + 210 Days
Final Acceptance Testing of the ITMS Solution Sign-off T+240 Days
ITMS / Ad panels Solution stabilization & Go-Live G = T + 270 Days
Operation & Maintenance Phase
Operation and Maintenance of ITMS solutions G + 1 year+2 years
197
7.3 Annexure 10 - Proposed Bill of Material (Technical Bid)
The Bidder should provide the proposed Bill of Material (BoM) here. Bidders are required to
mention the details of the make/brand and model against each line item, wherever
applicable. The bid can be considered non-responsive in the absence of such details. Once
the bidder provides this information in the submitted bid, the bidder cannot change it with
any other component / equipment etc. of lower specifications / performance; it can only be
upgraded at the time of actual deployment/installation.
Bill of Materials – CAPEX
Sr. No. Item Description UOM Qty Make Model Full Compliance
(Yes/No) Data Center
1 Unified Command & Control Center for TMMC Nos. 1
2 Core Firewall with IPS Nos. 1 3 Anti-APT Nos. 1 4 Core Router Nos. 2 5 Core Switch including all modules Nos. 2 6 TOR Switch including all modules Nos. 2
7 Access Switch 48 Port POE Switch all modules Nos. 2
8 Access Switch 24 Port Non-POE Switch all modules
Nos. 2
9 Server Load Balancer Set 1 10 EMS Set 1 11 Endpoint Security Set 1 12 Rack GPU Server Nos. 2 13 Rack Server Nos. 5 14 SAN/IP SAN Storage Set 1 15 Backup software Set 1
16 Unified management and Virtualization Solution Set 1
17 Video Wall, Controller and Management Software Set 1
18 VMS and Video analytics As per requirement
1
19 Integrated Data Center Infrastructure Set 1
20 30 KVA UPS Nos. 2 21 42U Rack with Biometric lock Nos 4
198
22 Biometric Access Control and Fire alarm system Set 1
23 DC Surveillance Camera, storage and Switch Set 1
24 DC Wireless access Point with controller
Set 1
25 Construction/Facelift of existing ATCS Command center for 1000 Sq. area
Set 1
26 Site Preparation Cost Lump sum 1
27 Non-IT Requirements,& Office Interior construction for DC of area 4000 Sq.ft
Nos 1
28 Passive Requirement including Fiber cable and DC components Lump sum 1
29 Professional Workstation Nos. 10
30 Desktop along with Help Desk software Nos. 5
31 Laser Multifunctional Device Nos. 2 32 DG Set Nos 2
33 Man Power As per requirement
1
ITMS - Field Equipment: 34 Field Junction Box for all Locations Nos 260
35 Camera Poles for Add Panel and Cameras Nos. 196
36 Heavy Poles for Ad Panel and PTZ Cameras Nos. 64
37 Industrial Grade Outdoor PoE switches (10% Spare to be maintained at Site all the time)
Nos 260
38 Field UPS for Outdoor locations (10% Spare to be maintained at Site all the time )
Nos 220
39
Networking Cost (Passive Components including Patch Panel, LIU, Cat6 Cable, Patch Cords)
Lump Sum 260
40 ANPR/RLVD Software Nos 365
41 ANPR Cameras (10% Spare to be maintained at Site all the time ) Nos 365
42 RLVD Cameras (10% Spare to be maintained at Site all the time ) Nos 195
43 Local Processing unit (10% Spare to be maintained at Site all the time )
Nos 220
44 AD Panels (10% Spare to be Nos 220
199
maintained at Site all the time ) 45 Field Site Preparation cost Nos 260
46
IP Based Public Announcement system with touch screen intercom microphone and accessories
Nos
1
47 Outdoor IP Based smart speakers (10% Spare to be maintained at Site all the time )
Nos 260
48 Emergency call box with complete hardware and accessories Nos
260
49 IP Fixed Box Cameras (10% Spare to be maintained at Site all the time )
Nos 225
50 IP PTZ Cameras (10% Spare to be maintained at Site all the time ) Nos
80
51 128 GB SD/Micro SD Card for all cameras Nos
865
52 Road Marking (Zebra / Stop line) at all Junctions
Nos 260
53 Electrical Work and Power supply with Mains switch at all Junctions
Nos 260
54 Pollution / Environmental Sensors/Air Quality Sensors Nos 2
55 Rain Gauges Sensors/Particulate Sensors Nos 2
56 Hand Held Terminals for E-Challans Nos 50
57 Commissioning and integration cost Lump sum 1
200
8 Annexure 11 – Formats for Submission of the Commercial Bid (will be given in online portal)
General Instructions
1. Bidder should provide all prices as per the prescribed format as per the RFP. Bidder
should not leave any field blank. In case the field is not applicable, Bidder must indicate
“0” (Zero) in all such fields.
2. All the prices are to be entered in Indian Rupees ONLY
3. All unit rates indicated in the schedules shall be inclusive of all taxes, GST levies, duties
etc. The prices should also be inclusive of all costs till end of the contract period.
4. JSCL, reserves the right to ask the Bidder to submit proof of payment against any of the
GST/taxes, duties, levies indicated.
5. The Bidder needs to account for all Out of Pocket expenses due to Boarding, Lodging and
other related items.
6. The Unit Rate as mentioned in the following formats shall be used for the purpose of
‘Change Order’ for respective items, if any. However, based on the market trends, JSCL,
retains the right to negotiate this rate for future requirement
7. Bidder shall be bound to give same or more % discount on the list price on the future
purchases by JSCL. SI shall ensure that the future products supplied are of latest
specifications as per the OEM roadmap.
8. For the purpose of evaluation of Commercial Bids, the JSCL, shall make appropriate
assumptions to arrive at a common bid price for all the Bidders. This however may not
direct co-relation with the Contract value or actual payment to be made to the Bidder.
9. The detailed commercial bid as per given templates below shall be submitted in separate
sealed covers. The summary of the commercial bid should be indicated in as per
prescribed template in the online portal.
201
8.1 Capital Expenditure (Capex (A))
S.No Item Description
Unit
Quantity
Unit Rate
Price
Tax Amount (GST/Duties/ Etc.) on 4
Amount (Including Tax)
1 2 3 4 = (2 x 3) 5 6 = (4 + 5)
Data Center
1 Unified Command & Control Center for TMMC Nos. 1
2 Core Firewall with IPS Nos. 1
3 Anti-APT Nos. 1
4 Core Router Nos. 2
5 Core Switch including all modules Nos. 2
6 TOR Switch including all modules Nos. 2
7 Access Switch 48 Port POE Switch all modules Nos. 2
8 Access Switch 24 Port Non-POE Switch all modules Nos. 2
9 Server Load Balancer Set 1
10 EMS Set 1
11 Endpoint Security Set 1
12 Rack GPU Server Nos. 2
13 Rack Server Nos. 5
14 SAN/IP SAN Storage Set 1
15 Backup software Set 1
16 Unified management and Virtualization Solution Set 1
17 Video Wall, Controller and Management Software Set 1
18 VMS and Video analytics As per requirement 1
19 Integrated Data Center Infrastructure Set 1
20 30 KVA UPS Nos. 2
21 42U Rack with Biometric lock Nos 4
22 Biometric Access Control and Fire alarm system Set 1
202
23 DC Surveillance Camera, storage and Switch Set 1
24 DC Wireless access Point with controller Set 1
25 Construction/Facelift of existing ATCS Command center for 1000 Sq. area
Set 1
26 Site Preparation Cost Lump sum 1
27 Non-IT Requirements,& Office Interior construction for DC/TMMC of area 4000 Sq.ft
Nos 1
28 Passive Requirement including Fiber cable and DC components
Lump sum 1
29 Professional Workstation Nos. 10
30 Desktop along with Help Desk software Nos. 5
31 Laser Multifunctional Device Nos. 2
32 DG Set Nos 2
33 Man Power for 3 years project management Lump sum 1
ITMS - Field Equipment:
34 Field Junction Box for all Locations Nos 260
35 Camera Poles for Add Panel and Cameras Nos. 196
36 Heavy Poles for Ad Panel and PTZ Cameras Nos. 64
37 Industrial Grade Outdoor PoE switches (10% Spare to be maintained at Site all the time)
Nos 260
38 Field UPS for Outdoor locations (10% Spare to be maintained at Site all the time )
Nos 220
39 Networking Cost (Passive Components including Patch Panel, LIU, Cat6 Cable, Patch Cords)
Lump sum 260
40 ANPR/RLVD Software Nos 365
41 ANPR Cameras (10% Spare to be maintained at Site all the time)
Nos 365
42 RLVD Cameras (10% Spare to be maintained at Site Nos 195
203
all the time)
43 Local Processing unit (10% Spare to be maintained at Site all the time)
Nos 220
44 AD Panels (10% Spare to be maintained at Site all the time)
Nos 220
45 Field Site Preparation cost Nos 260
46 IP Based Public Announcement system with touch screen intercom microphone and accessories
Nos 1
47 Outdoor IP Based smart speakers (10% Spare to be maintained at Site all the time)
Nos 260
48 Emergency call box with complete hardware and accessories
Nos 260
49 IP Fixed Box Cameras (10% Spare to be maintained at Site all the time)
Nos 225
50 IP PTZ Cameras (10% Spare to be maintained at Site all the time)
Nos 80
51 128 GB SD/Micro SD Card for all cameras Nos 865
52 Road Marking (Zebra / Stop line) at all Junctions Nos 260
53 Electrical Work and Power supply with Mains switch at all Junctions
Nos 260
54 Pollution / Environmental Sensors/Air Quality Sensors
Nos 2
55 Rain Gauges Sensors/Particulate Sensors Nos 2
56 Hand Held Terminals for E-Challans Nos 50
57 Commissioning and integration cost Lump sum 1
Training and Overall Project Management
52 Functional Training (10 trainees per batch) Lump sum 30
53 Administrative Training batches Lump sum 10
54 Sr. Management Training Batches Lump sum 10
204
55 Project Management/Coordination during implementation
Lump sum 10
56 Security Audit Charges Lump sum 1
57 Operational Expenses during implementation Lump sum 1
8.2 Operational Expenditure (Opex (B))
Sr. No.
Particulars
Year_1
Year_2
Year_3
Amount for 3 years
Applicable Tax Amount on "4"
Amount for 5 years with Tax
1 2 3 4 = sum ( 1,2,3)
5 6 = (4 + 5)
Data Center
1 Cloud based Smart DR connectivity
2 Connectivity to TMMC for all cameras live/recording, PA system, Ad panels, etc
3 Connectivity to 260 field Junctions from TMMC
4 O&M for Networking and fiber connectivity
5 Re-Training and Overall Project Management during O&M Period
6 CCTV Surveillance data management
7 Facility Management, Technical & Operational support by Technical/ Operational /Support personnel of SI
8 Additional Infrastructure / Services (if any)
9 Smart Environmental Sensors
Sub Total Section 1: OPEX (B)
205
8.3 Sub-Total
S.No
Particulars
Total Amount with Taxes
1 Sub Total Section I –CAPEX (A)
2 Sub Total Section I –OPEX (B)
3 Sub-Total Section-1 (Total Project Cost) T
4 CAPEX: OPEX Ratio [capped to 82% i.e. is (A / T) x 100 ]
Note:
The above table total cost summaries the actual project cost & contract value for the bidder. The payments to the successful bidder would be made as per this value only. The bidders shall ensure that the CAPE:OPEX ratio does not exceed 82%. The CAPEX:OPEX ratio is calculated by dividing the CAPEX by Total project Cost in above table.
206
9 Annexures:
9.1 PTZ, Fixed, ANPR and RLVD Camera, Ad Panel and Environment Sensor Locations:
A survey was conducted by PMC of all the junctions. A new fly-over is being constructed; Junctions highlighted in Yellow fall in the area of construction of the flyover and may not need to be included in the final implementation. The details of the requirement at all the identified junctions are:
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
1
Gandhi Nagar, Hospital Turning
4 arms 1 4 8 4 4 1 1 4 1
1.No stop line. 2.Four pole required for ad panel.
2 Panjtirthi-By Pass Point
3 arms 1 3 6 3 3 1 1 3 - - 1
1.No stop line 2.Three pole for ad panel
3 DC Office Jammu
3 arms 1 3 6 3 3 1 1 3 - - 1
1.No stop line. 2.Four pole required for ad panel.
4
G L Dogra Chowk Opp PHQ
4 arms 2 4 - - 4 1 1 - - - 2
1.One PTZ 2.No Traffic
1.Only survelliance 2.Four pole required for
207
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
Light. ad panel
5
Railway Station Trikuta Nagar
3 arms 1 3 6 3 3 1 1 3 1
1.No Zebra Crossing and no stop line 2.Three pole for ad panel
6
Marble Market Road-Greater Kailash Point
- - - - - - - - - - - - -
Data covered in Greater Kailash Crossing on NHW junction.
7 Bahu Plaza Junction
3 arms 1 3 6 3 3 1 1 3 - - 1
1.No Zebra Crossing and no stop line 2.Three pole for ad panel
8
Trikuta Nagar, Nideesh Flats Point
3 arms 1 3 6 3 3 1 1 3 1
1.No Zebra Crossing and no stop line 2.Three pole for ad panel
9 Channi Himmat
- - - - - - - - - - - - - Data covered in Jammu Darbhar
208
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
Central Lane Three
junction
10
Greater Kailash (G S Charak Lane) Point
3 arms 1 3 - - 3 1 1 - - - 1 No traffic light
1.Data only of Survelliance 2.Three pole for ad panel
11 Diagiana Pulli
3 arms 1 3 6 3 3 1 1 3 1
1.No Zebra Crossing and no stop line 2.Three pole for ad panel
12
Nanak Nagar-RBI Turning
3 arms
1 3 6 3 3 1 1 3 1
1.No Zebra Crossing and no stop line 2.Three pole for ad panel
13
Tawi Vihar Sidhra Colony By Pass Point
3 arms
1 3 - - 3 1 1 - - - 1
No traffic light
1.Data only of Survelliance 2.Three pole for ad panel
14
Bahu Fort By Pass Point
3 arms
1 3 6 3 3 1 1 3 1
1.Data only of Survelliance 2.Three pole for ad panel
209
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
15 Disco Turning
2 arms 1 2 - - 2 1 1 - - - 1 No traffic light
1.Data only of Survelliance 2.No near electtic junction box. 3.Two pole for ad panel
16
Qasim Nagar Chowk By Pass Point
4 arms 1 4 6 3 3 1 1 3 1
Traffic light on 3 arms only
1.No stop line 2.Four pole for ad panel
17
Billol Bridge Parmandal Turning Point
3 arms
1 3 6 3 3 1 1 3 1
1.No Zebra Crossing and no stop line 2.Three pole for ad panel
18
Jammu Nagotra Bypass Crossing
3 arms
1 3 6 3 3 1 1 3 1
1.No Zebra Crossing and no stop line 2.Three pole for ad panel
19
R S Pura Airport Point
3 arms
1 3 6 3 3 1 1 3 1
1.No stop line 2.Three pole for ad panel
20 Kunjwani Chowk
4 arms 2 4 10 4 4 1 1 4 2
1.No Zebra Crossing and
210
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
no stop line 2.Four pole for ad panel
21
Sainik Colony Crossing on NHW
3 arms
1 3 6 3 3 1 1 3 1
1.No Zebra Crossing and no stop line 2.Three pole for ad panel
22 Sunjwan Chowk
2 arms 1 2 4 2 2 1 1 2 1
1.No stop line 2.Three pole for ad panel
23 Bohri Talab Tillo chowk
4 arms
1 4 8 4 4 1 1 4 1
1.No Zebra Crossing and stop line 2.Four pole for Ad panel
24
Gujjar Nagar Jammu
3 arms
1 3 4 3 3 1 1 3 1
1.No stop line 2.Three pole for ad panel
25 Asia Crossing
3 arms 1 3 6 3 3 1 1 3 1
1.No stop line 2.Three pole for ad panel
26
Channi Head Crossing Near
3 arms
1 3 6 3 3 1 1 3 1
1.No stop line 2.Three pole for ad panel
211
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
Jammu Darbar
27 Bantalab Chowk
3 arms
1 3 6 3 3 1 1 3 1
1.No Zebra Crossing and stop line 2.Three pole for Ad panel
28 Muthi Camp Bridge
- - - - - - - - - - - - -
Flyover under constrction so exact positioning of pole not possible
29
Railway Station Turning
4 arms
2 5 10 5 4 1 1 5 2 1 PTZ
1.No Zebra Crossing and stop line 2.Four pole for Ad panel
30
Greater Kailash Crossing on NHW
4 arms
2 4 10 4 4 1 1 2 2 2
1.No Zebra Crossing and stop line 2.Four pole for Ad panel
31 Gangyal Junction
3 arms
1 4 6 3 3 1 1 3 1
1.No Zebra Crossing and stop line 2.Three pole
212
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
for Ad panel
32
Narwal Petrol Pump Near wine shop (Road Towards SDPO East Office)
3 arms
1 3 - - 3 1 1 - - - 1
No traffic light
1.Data only of Survelliance 2.Three pole for Ad panel
33 Valmiki Chowk
4 arms
1 4 - - 4 1 1 - - - 1
No traffic light
1.Data only of Survelliance 2.Four pole for Ad panel
34
University of Jammu Main Gate
2 arms
1 2 4 2 2 1 1 2 1
1.Faded Zebra Crossing and no stop line 2.Two pole for Ad panel
35 Satwari 4 arms
1 4 10 4 4 1 1 2 2 1
1.Faded Zebra Crossing and no stop line 2.Four pole for Ad panel
213
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
36
Main stop Gandhi Nagar
3 arms
1 3 8 3 3 1 1 1 2 1
1.Faded Zebra Crossing and no stop line 2.Three pole for Ad panel
37 Green Belt Park
4 arms 1 4 8 4 4 1 1 4
1.No stop line 2.Four pole for Ad panel
38 Bikram Chowk
4 arms
2 4 10 4 4 1 1 2 2
1.No stop line. 2.Four pole for Ad panel.
39 Jewel 4 arms
2 5 8 4 4 1 1 4
- - 2
1 PTZ
1.Faded Zebra Crossing and no stop line 2.Four pole for Ad panel
40 K C Chowk 3 arms
2 3 6 3 3 1 1 3
- - 2
1 PTZ
1.Faded Zebra Crossing and no stop line 2.Three pole for Ad panel
41 Shakuntala Chowk
3 arms 1 3 6 3 3 1 1 3
- - 1
1.No stop line 2.Three pole
214
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
for Ad panel
42 Ambphalla Chowk
4 arms
2 3 6 3 3 1 1 3
- - 2
1.Faded Zebra Crossing and no stop line 2.Three pole for Ad panel
43
Radio Station Panjthirthi
4 arms
1 4 6 3 3 1 1 3
- - 1
1.No stop line 2.Three pole for Ad panel
44 Library Chowk
4 arms
1 4 4 4 4 1 1 4
- - 1
1.Faded Zebra Crossing and no stop line 2.Four pole for Ad panel
45
Women College, Parade
3 arms
1 3 3 3 3 1 1 3
- - 1
1.No stop line 2.Three pole for Ad panel
46 Rameshwer Temple
4 arms
2 4 5 4 2 1 1 4
- - 2
1 PTZ
1.Faded Zebra Crossing and no stop line 2.Two pole for Ad panel
215
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
47 Shalamar Chowk
3 arms
1 3 5 3 2 1 1 3
- - 1
1.Faded Zebra Crossing and no stop line 2.Two pole for Ad panel
48 Indira Chowk
4 arms
1 4 8 4 4 1 1 4
- - 1
1.Faded Zebra Crossing and no stop line 2.Four pole for Ad panel
49 Vivekanad Chowk
4 arms
1 4 8 4 4 1 1 4
- - 1
1.Faded Zebra Crossing and no stop line 2.Four pole for Ad panel
50 Shaheedi Chowk
4 arms
1 4 3 3 4 1 1 3
- - 1
1.Faded Zebra Crossing and no stop line 2.Four pole for Ad panel
51 Panama Chowk
4 arms
1 4 8 4 4 1 1 4
- - 1
1.Faded Zebra Crossing and no stop line
216
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
2.Four pole for Ad panel
52 Railway Crossing
3 arms
1 3 6 3 3 1 1 3 1
1.Faded Zebra Crossing and no stop line 2.Three pole for Ad panel
53 Narwal Chowk
3 arms
1 3 6 3 3 1 1 3
1
CCTV Camera
1.Faded Zebra Crossing and no stop line 2.Three pole for Ad panel
54 Bathindi Chowk
4 arms
1 4 8 4 4 1 1 4
- - 1
1.Faded Zebra Crossing and no stop line 2.Four pole for Ad panel
55 Canal Head - - - - - - - - - - - - -
Flyover under constrction so exact positioning of pole not possible
217
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
56 Bakshi Nagar Pulli
- - - - - - - - - - - - -
Flyover under constrction so exact positioning of pole not possible
57 Paloura BSF - - - - - - - - - - - - -
Flyover under constrction so exact positioning of pole not possible
58 Talab Tillo 3 arms
1 3 6 3 3 1 1 3 1
1.Faded Zebra Crossing and no stop line 2.Three pole for Ad panel
59 Medical College
2 arms
1 2 4 2 2 1 1 2 1
1.Faded Zebra Crossing and no stop line 2.Two pole for Ad panel
60 High Court, Janipur
3 arms 1 3 6 3 3 1 1 3 1
1.No stop line 2.Three pole for Ad panel
218
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
61 Main stop, Janipur
3 arms
1 3 6 3 3 1 1 3 1
1.Faded Zebra Crossing and no stop line 2.Three pole for Ad panel
62 Roop Nagar 5 arms
1 5 6 3 3 1 1 4 1
1.Faded Zebra Crossing and no stop line 2.Four pole for Ad panel
63 Chattri Point
3 arms 2 4 9 5 3 1 1 1 1 1 2
1.No stop line 2.Three pole for Ad panel
64 Vigilance Rotary
5 arms 1 5 10 5 5 1 1 5 1
1.No stop line 2.Five pole for Ad panel
65 Bakshi nagar chowk
6 arms
2 6 - - 6 1 1 - - - 2
1.Two PTZ 2.No Traffic Light.
1.Data only of Survelliance 2.Three pole for Ad panel
66 Greater Kailash by pass
3 arms
1 3 6 3 3 1 1 3 1
1.Faded Zebra Crossing and no stop line
219
Surveillance
Cameras ITMS
Cameras
S. No.
Location Type of
Junction PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
CPE
L-Type Pole for 2
Lanes
L-Type Pole for 3
Lanes
L-Type Pole for 4
Lanes
9 Mtr. Long Pole
for PTZ
Existing Infra
Remarks
2.Three pole for Ad panel
67 Last morh Gandhi nagar
3 arms
1 3 8 3 3 1 1 1 2 1
1.Faded Zebra Crossing and no stop line 2.Three pole for Ad panel
70 Ambedkar Chowk
3 arms 1 3 6 3 3 1 1 3 1
1.No stop line 2.Three pole for Ad panel
Total (Junctions) 73 213 359 182 202 62 62 169 11 1 70
Total (Exit Points) 4 10 6 3 10 4 4 3 0 0 4
9.2 City Exit Points:
220
Surveillance
Cameras ITMS
Cameras
Location Types of
Junctions PTZ Fixed ANPR RLVD
Ad Panels
Env Sensor
W-Fi Hotspot
L-Type Pole for 2
Lanes
9 Mtr. Long Pole
for PTZ Remarks
Bari Brahmna near pahalwan
2 Arm 1 3 - - 2 1 1
1
1.Two Poles for fixed camera and Ad panel 2.No Electric box so wire taken from near transformer
Hari Palace 3 Arm
1 2 - - 2 1 1 1
1.No stop line. 2.Two Poles for fixed camera and Ad panel
Jammu Nagotra Bypass Crossing near Sidhra Bridge 3 Arm 1 3 6 3 3 1 1 3 1
1.Already Covered in initial Survey. 2.No Zebra Crossing and no stop line 3.Three pole for ad panel
Damana jammu
3 Arm
1.Highway construction going on.
Nagrota near poilce check point
2 Arm 1 2 - - 3 1 1 1
1.Outside Muncipal limits 2.Overhead Gantry so fixed camera can be placed on it required for ad panel. 3.Two Poles for Ad panel
221
9.3 Public Address System
S. No. Location Types of Junctions
1 Gandhi Nagar, Hospital Turning 4 arms
2 Panjtirthi-By Pass Point 3 arms
3 DC Office Jammu 3 arms
4 G L Dogra Chowk Opp PHQ 4 arms
5 Railway Station Trikuta Nagar 3 arms
6 Marble Market Road-Greater Kailash Point
7 Bahu Plaza Junction 3 arms
8 Trikuta Nagar, Nideesh Flats Point 3 arms
9 Channi Himat Central Lane Three
10 Greater Kailash (G S Charak Lane) Point 3 arms
11 Diagiana Pulli 3 arms
12 Nanak Nagar-RBI Turning 3 arms
13 Tawi Vihar Sidhra Colony By Pass Point 3 arms
14 Bahu Fort By Pass Point 3 arms
15 Disco Turning 2 arms
16 Qasim Nagar Chowk By Pass Point 4 arms
17 Billol Bridge Parmandal Turning Point 3 arms
18 Jammu Nagotra Bypass Crossing 3 arms
19 R S Pura Airport Point 3 arms
20 Kunjwani Chowk 4 arms
21 Sainik Colony Crossing on NHW 3 arms
22 Sunjwan Chowk 2 arms
23 Bohri Talab Tillo chowk 4 arms
24 Gujjar Nagar Jammu 3 arms
25 Asia Crossing 3 arms
26 Channi Head Crossing Near Jammu Darbar 3 arms
27 Bantalab Chowk 3 arms
222
S. No. Location Types of Junctions
28 Muthi Camp Bridge
29 Railway Station Turning 4 arms
30 Greater Kailash Crossing on NHW 4 arms
31 Gangyal Junction 3 arms
32 Narwal Petrol Pump Near wine shop (Road Towards SDPO East Office)
3 arms
33 Valmiki Chowk 4 arms
34 University of Jammu Main Gate 2 arms
35 Satwari 4 arms
36 Main stop Gandhi Nagar 3 arms
37 Green Belt Park 4 arms
38 Bikram Chowk 4 arms
39 Jewel 4 arms
40 K C Chowk 3 arms
41 Shakuntala Chowk 3 arms
42 Ambphalla Chowk 4 arms
43 Radio Station Panjthirthi 4 arms
44 Library Chowk 4 arms
45 Women College, Parade 3 arms
46 Rameshwer Temple 4 arms
47 Shalamar Chowk 3 arms
48 Indira Chowk 4 arms
49 Vivekanad Chowk 4 arms
50 Shaheedi Chowk 4 arms
51 Panama Chowk 4 arms
52 Railway Crossing 3 arms
53 Narwal Chowk 3 arms
54 Bathindi Chowk 4 arms
55 Canal Head
223
S. No. Location Types of Junctions
56 Bakshi Nagar Pulli
57 Paloura BSF
58 Talab Tillo 3 arms
59 Medical College 2 arms
60 High Court, Janipur 3 arms
61 Main stop, Janipur 3 arms
62 Roop Nagar 5 arms
63 Chattri Point 3 arms
64 Vigilance Rotary 5 arms
65 Bakshi nagar chowk 6 arms
66 Greater Kailash by pass 3 arms
67 Last morh Gandhi nagar 3 arms
70 Ambedkar Chowk 3 arms
224
