REQUEST FOR PROPOSAL FOR SELECTION OF SYSTEMINTEGRATOR

FOR DESIGN, DEVELOPMENT, SITC, O&M FOR 05 YEARS OF

INTEGRATED COMMAND & CONTROL CENTER(ICCC) & OTHER
ASSOCIATED ACTIVITIES FOR PUDUCHERRY SMART CITY AREA
VOLUME 2 – SCOPE, FUNCTIONAL & TECHNICAL SPECIFICATION

Original RFP NO: RCIL-2023-PDY-Smart City-RFP-01 DATED: 01.06.2023

Corrigendum: RCIL-2023-PDY-Smart City-RFP-01 (Modified) Dated 27-07-2023

Page 1 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Table of Contents
1 Disclaimer ........................................................................................................... 6
2 Definitions and Acronyms ...................................................................................... 7
3 Overview ............................................................................................................ 9
3.1 Introduction .................................................................................................. 9
3.2 Vision ........................................................................................................... 9
3.3 Project Background ........................................................................................ 9
3.4 Objective of the Project and RFP ............................................................... 10
3.4.1 Objective of the Project ............................................................................. 10
3.4.2 Objective of the RFP ................................................................................. 11
4 Project broad scope ............................................................................................ 13
5 Project Scope of Work ........................................................................................ 23
5.1 Assessment, Site Survey and Project Plan ....................................................... 23
5.2 Documents/ Drawings Submission after Award of Contract ................................ 24
5.2.1 Stage 1: Design engineering ...................................................................... 24
5.2.2 Stage 2: Project execution......................................................................... 24
5.2.3 Stage 3: Post commissioning ..................................................................... 25
5.3 Finalization of Detailed Technical Architecture .................................................. 25
5.4 Site Clearance Obligations and Other Relevant Permissions ............................... 28
5.4.1 Survey And Commencement of Works......................................................... 28
5.4.2 Existing Traffic Signal system..................................................................... 28
5.4.3 Electrical Works and Power Supply ............................................................. 28
5.5 Miscellaneous .............................................................................................. 28
5.6 Design and Implementation of Integrated Command & Control Center System .... 29
5.7 Design, Supply, Installation & Commissioning of the Field Equipment ................. 30
5.8 City Surveillance System – (CCTV Camera) ..................................................... 30
5.9 Integrated Traffic Management System (ITMS) ................................................ 32
5.10 Lightning-Proof Measures .............................................................................. 35
5.11 Earthing System .......................................................................................... 36
5.12 Junction Box / Outdoor Cabinet, Poles and Cantilever ....................................... 36
5.13 Power & UPS - for Field Locations ................................................................... 38
5.14 Civil and Electrical Works .............................................................................. 38
5.15 Cabling Infrastructure .................................................................................. 39
5.16 Responsibility Matrix - Overall ....................................................................... 39
5.17 Project Deliverables ..................................................................................... 42
5.18 Project Timelines – Phase wise ...................................................................... 44
Page 2 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 5.19 Project Timelines – Component wise............................................................... 46
5.20 Project Defect Liability Period (DLP) / Warrantee of Product & Services ............... 47
6. Functional Requirement and Technical Specifications .............................................. 48
Details of Key Modules ........................................................................................... 48
6.1 Integrated Command and Control Centre ........................................................ 48
6.2 On Premise Data Centre (DC) ........................................................................ 76
6.2.1. 42U Rack with All Accessories .................................................................... 76
6.2.2 Core Router: ............................................................................................ 77
6.2.3. Firewall + IPS .......................................................................................... 78
6.2.4. Server Specification .................................................................................. 82
6.2.5. Storage Specification ................................................................................ 82
6.2.6. Hypervisor ............................................................................................... 83
6.2.7. Core Switch ............................................................................................. 84
6.2.8. TOR Switch & WAN Aggregation switch: ...................................................... 86
6.2.9. Access Switch -8 Port – POE ...................................................................... 88
6.2.10. Access Switch-24 Port –POE ...................................................................... 89
6.2.11 Wireless LAN Controller ........................................................................... 91
6.2.12. Indoor Access Points: .............................................................................. 92
6.2.13 AAA Server .............................................................................................. 94
6.2.14 Centralized-Anti Virus Solution For ICCC ..................................................... 95
6.2.15 Video wall and Video wall Controller ............................................................ 96
6.2.16 Lan Networking For ICCC ........................................................................ 104
6.2.17 Centralized Help Desk ............................................................................. 105
6.2.18 IP Phones .............................................................................................. 105
6.2.19 Three Monitoring Workstations ................................................................. 107
6.2.20 Data Center & ICCC: Non-IT Components .................................................. 109
6.2.21 Intranet router at DC .............................................................................. 109
6.2.22 Backbone Router .................................................................................... 111
6.3 Cloud Services to deploy all smart solutions .................................................. 126
6.4 Intelligent Traffic Management System ......................................................... 136
6.4.1 Key Issues............................................................................................. 136
6.4.2 Indicative Key Outcomes and KPIs............................................................ 136
6.4.3 Key components..................................................................................... 137
6.4.4 Automatic Number Plate Recognition (ANPR) ............................................. 137
6.4.5 Red Light Violation Detection (RLVD) ........................................................ 139
6.4.6 Speed Violation Detection (SVD) .............................................................. 139

Page 3 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6.4.7 Traffic Analytics ..................................................................................... 140
6.4.8 Adaptive Traffic Control System (ATCS) .................................................... 141
6.4.9 Reports ................................................................................................. 143
6.4.10 Graphical User Interface .......................................................................... 144
6.4.11 Video Management & Operator Functions .................................................. 145
6.4.12 Entry Exit Point Management ................................................................... 151
6.4.13 Corridor Management ............................................................................. 155
6.4.14 Variable Message Display ........................................................................ 156
6.4.15 Specification for Speed Violation Camera ................................................... 158
6.4.16 Instant Speed Violation Detection ............................................................. 160
6.4.17 Average Speed Violation Detection ........................................................... 161
6.4.18 Wrong Side Driving Violation.................................................................... 161
6.4.19 Adaptive Traffic Control System ............................................................... 161
6.4.20 Automatic E Challan System .................................................................... 185
6.5 Enterprise Management System (EMS) ......................................................... 188
6.6 Citizen Engagement System: Creation of Online and Mobile Applications ........... 193
6.7 Smart Poles .............................................................................................. 201
6.7.1 Smart Pole Specification .......................................................................... 201
6.7.2 Digital Bill Board .................................................................................... 202
6.7.3 Environmental Sensors ........................................................................... 203
6.7.4 Emergency Call Box: ............................................................................... 211
6.7.5 IoT Gateway Specification ....................................................................... 212
6.7.6 Public Address System ............................................................................ 213
6.7.7 City Public Wi-Fi ..................................................................................... 215
6.8 Geographical Information System ................................................................ 217
6.9 Flood Sensors & Alert System ...................................................................... 217
6.10 City Surveillance System ............................................................................ 220
6.10.1 Video Management System...................................................................... 223
6.10.2 City Surveillance fixed Camera Specifications ............................................. 243
6.10.3 City Surveillance PTZ Camera Specifications .............................................. 246
6.11 Smart Kiosks ............................................................................................. 248
6.12 Local Processing Units (LPU): ...................................................................... 252
6.13 External IR Illuminator (Optional) ................................................................ 252
6.14 Network Connectivity - OFC ........................................................................ 253
7 Approach and methodology to be adopted for implementation ............................... 254
8 Lifecycle of implementation of ICT intervention: ................................................... 256

Page 4 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
9 Detailed Technical and Non-Technical Manpower: ................................................. 257
10 Use cases to be deployed / integrated ................................................................ 258
10.1 Digital Assistant Application ........................................................................ 258
11 Training, Audit and Change Management Plan: .................................................... 260
12 Proposed Governance Model .............................................................................. 261
13 Exit Management Under Contract Completion: ..................................................... 261
14 Detailed work Phases and considerations ............................................................ 263
14.1.1 Phase 1(Implementation Phase) ............................................................... 263
14.1.2 Phase-2 (Operations and Maintenance) ..................................................... 268
14.1.3 Project Management and Governance ....................................................... 268
14.1.4 Change Management & Control ................................................................ 270
14.1.5 Testing and Acceptance Criteria ............................................................... 272
14.1.6 Factory Testing ...................................................................................... 273
14.1.7 Final Acceptance Testing ......................................................................... 273
15 Annexure III: Project Milestones and Payment Schedules for Implementation .......... 274
15.1 Quality Assurance ...................................................................................... 277
16 Annexure V : Guidelines ................................................................................... 278
17 Annexure VI Security – General Guidelines .......................................................... 280
17.1 Security Framework ................................................................................... 280
17.2 Security Policy ........................................................................................... 280
17.3 Security Governance .................................................................................. 281
17.4 Smart City IT Asset Management ................................................................. 281
17.5 Physical & Environmental Security ............................................................... 281
17.6 Access Control ........................................................................................... 281
17.7 Communications and Operations Management ............................................... 282
17.8 Information Systems Acquisition, Development and Maintenance ..................... 284
17.9 Business Continuity Planning and Disaster Recovery ....................................... 284
17.10 Information Security Audits ...................................................................... 285
17.11 Awareness Training ................................................................................. 285
17.12 Security Controls for Cloud Services .......................................................... 285
18 Annexure VI – Smart City Guidelines .................................................................. 287

Page 5 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
1 Disclaimer

The information contained in this Request for Proposal document (“RFP”) whether subsequently
provided to the bidders, (“Bidder/s”) verbally or in documentary form by RailTel Corporation of
India Limited (henceforth referred to as “RailTel” in this document) or any of its employees or
advisors, is provided to Bidders on the terms and conditions set out in this Tender document and
any other terms and conditions subject to which such information is provided.

This RFP is not an agreement and is not an offer or invitation to any party. The purpose of this RFP
is to provide the Bidders or any other person with information to assist the formulation of their
financial offers (“Bid”). This RFP includes statements, which reflect various assumptions and
assessments arrived at by RailTel in relation to this scope. This Tender document does not purport
to contain all the information each Bidder may require. This Tender document may not be
appropriate for all persons, and it is not possible for RailTel and their employees or advisors to
consider the objectives, technical expertise and particular needs of each Bidder. The assumptions,
assessments, statements and information contained in the Bid documents, may not be complete,
accurate, adequate or correct. Each Bidder must therefore conduct its own analysis of the
information contained in this RFP and to seek its own professional advice from appropriate
sources.

Information provided in this Tender document to the Bidder is on a wide range of matters, some
of which may depend upon interpretation of law. The information given is not intended to be an
exhaustive account of statutory requirements and should not be regarded as a complete or
authoritative statement of law. RailTel accepts no responsibility for the accuracy or otherwise for
any interpretation of opinion on law expressed herein.

RailTel and their employees and advisors make no representation or warranty and shall incur no
liability to any person, including the Bidder under law, statute, rules or regulations or tort, the
principles of restitution or unjust enrichment or otherwise for any loss, cost, expense or damage
which may arise from or be incurred or suffered on account of anything contained in this RFP or
otherwise, including the accuracy, reliability or completeness of the RFP, and any assessment,
assumption, statement or information contained therein or deemed to form part of this RFP or
arising in any way in this Selection Process.

RailTel also accepts no liability of any nature whether resulting from negligence or otherwise
howsoever caused arising from reliance of any Bidder upon the statements contained in this
RFP. RailTel may in its absolute discretion, but without being under any obligation to do so, can
amend or supplement the information in this RFP.

The issue of this Tender document does not imply that RailTel is bound to select a Bidder or to
appoint the Selected Bidder (as defined hereinafter), for implementation and RailTel reserves the
right to reject all or any of the Bidders or Bids without assigning any reason whatsoever.

The Bidder shall bear all its costs associated with or relating to the preparation and submission of
its Bid including but not limited to preparation, copying, postage, delivery fees, expenses
associated with any demonstrations or presentations which may be required by RailTel or any
other costs incurred in connection with or relating to its Bid. All such costs and expenses will remain
with the Bidder and RailTel shall not be liable in any manner whatsoever for the same or for any
other costs or other expenses incurred by a Bidder in preparation for submission of the Bid,
regardless of the conduct or outcome of the Selection process.

Page 6 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
2 Definitions and Acronyms

Terms Acronyms
AAA Authentication, Authorization, Accounting
ABD Area Based Development
AI Artificial Intelligence
AMC Annual Maintenance Contract
AP Access Points
API Application Programming Interface
AQM Air Quality Monitoring
ANPR Automatic Number Plate Recognition
ATCS Adaptive Traffic Control System
BOM Bill of Material
BEC Bidders Evaluation Committee
BG Bank Guarantee
CC Capital Cost
CCTV Closed Circuit Television
CEO Chief Executive Officer
CPU Central Processing Unit
CSP Cloud Service Provider
DB Data Base
DC Data Centre
DD Demand Draft
DG Diesel Generator
DR Disaster Recovery
DRDM Department of Revenue and Disaster
Management
DWC Double Wall Corrugated
ECB Emergency Call Box
EMD Earnest Money Deposit
EMS Element Management System
FAT Factory Acceptance Test
FMS Facility Management Services
GIS Geographical Information Systems
GI Galvanized Iron
GPS Global Positioning System
GST Goods and Services Tax
PSCDL Puducherry Smart City Development Limited
HDD Horizontal Drilling
HDPE High Density Polyethylene
HOD Head of Department
ICCC Integrated Control and Command Center
ICT Information and Communication Technology
IOT Internet of Things
IP Internet Protocol
ISP Internet Service Provider
IT Information Technology
ITMS Integrated Traffic Management System
INR Indian Rupee
IVR Interactive Voice Response System
KPI Key Performance Indicator
LOA Letter of Acceptance or Letter of Award

Page 7 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Terms Acronyms
LAN Local Area Network
LoI Letter of Intent

Page 8 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Terms Meaning
MoU Memorandum of Understanding
MOUD Ministry of Urban Development, GOI
SI Master System Integrator
NPV Net Present Value
NPW Net Project Worth
OEM Original Equipment Manufacture
O&M Operations & Maintenance
OFC Optical Fiber Cable
PA Public Address
PAS Public Address System
PAT Prototype Acceptance Test
PABX Private Automatic Branch Exchange
PBG Performance Bank Guarantee
PDD Proposal Due Date
PDU Power Distribution System
POA Power of Attorney
PoC Proof of Concept
PoE Power over Ethernet
PoP Point of Presence
PQ Pre-Qualification
PTZ Pan Tilt Zoom
PV Present Value
PWD Public Work Department
QCBS Quality cum Cost Based Selection
RFP Request for Proposal
RLVD Red Light Violation Detection
ROW Right of way
RI Right to Inspect
SCM Smart Cities Mission
SCP Smart City Proposal
SI System Integrator
SITC Supply Installation Testing Commissioning
SLA Service Level Agreement
SOP Standard Operating Procedures
SVD Speed Violation Detection
SSD Solid State Drive
TOR Top of the Rack
TQ Technical Qualification
TRV Total Revenue
UAT User Acceptance Testing
UPS Uninterrupted Power Supply
VA Video Analytics
VAPT Vulnerability Assessment and Penetration Testing
VM Virtual Machine
VMD Variable Message Display
VMS Video Management System

Page 9 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Definitions

Term Definition
Client DRDM / PSCDL
MSI cum PMC RailTel Corporation of India Ltd
/Authority/
Tender Inviting
Authority
System Integrator Selected Bidder with whom the contract agreement
is signed against this RFP.

Page 10 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
3 Overview

3.1 Introduction
Puducherry, formerly known as Pondicherry, gained its significance as “The French Riviera of the
East” after the advent of the French colonialization in India. Puducherry is the Tamil interpretation
of “new town” and mainly arrived from “Poduke”, the name of the marketplace as the “Port town”
for Roman trading, way back in 1st century as mentioned in the ‘The Periplus of the Erythraean
Sea’. The settlement was once an abode of many learned scholars as evidently versed in the
Vedas, hence also known as Vedapuri.

Puducherry Smart City Participated in the Government of India Launched Smart City Mission
challenge in which Puducherry City was qualified as Smart City in 3rd round of Smart city
Challenge keeping The Vision is to “Transforming Puducherry into a global tourism
destination by leveraging its heritage, cultural, spiritual, and educational advantages.
Enhance the quality of life of the citizens by providing efficient urban mobility, smart
civic infrastructure, smart service delivery and participative decision making.”

3.2 Vision

Transforming Puducherry into a global tourism destination by leveraging its heritage, cultural,
spiritual, and educational advantages. Enhance the quality of life of the citizens by providing
efficient urban mobility, smart civic infrastructure, smart service delivery and participative
decision making.”

Based on the above formulated vision, Smart City Proposal was focused on the following

opportunities and Challenges:

a) Livelihood Opportunities Through Promotion of Tourism

b) Protection of Heritage and Preservation of the Unique Features of the City

c) Urban Poverty Alleviation through Affordable Housing

d) Urban Mobility, Traffic Decongestion and Safety & Security of Citizens

e) Better Delivery of Citizen Services with accountability

3.3 Project Background

The vision of Puducherry Smart City is to drive citizen centricity through improvements in City
Operations, improve efficiency of municipal services and promote a better quality of life for
residents. In order to achieve these Puducherry Smart City Development Limited desires to foster
the development of a robust ICT infrastructure that supports digital applications and ensures
seamless oversight of city-wide operations.

The key objective of this project is to establish a collaborative framework where input from
different functional departments of Puducherry Municipal Corporation and other stakeholders
such as transport, fire, police, e-governance, etc. can be assimilated and analyzed on a single
platform; consequently, resulting in aggregated city level information. Further, this can be
Page 11 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
converted to actionable intelligence, which would be propagated to relevant stakeholders
and citizens.
Puducherry Smart City Development Limited (PSCDL) has entrusted implementation of works
to the Department of Revenue and Disaster Management (DRDM), Puducherry. The DRDM
has engaged RailTel as MSI-cum-PMC for the implementation of the project who will float
tender, finalize tender with the approval of DRDM/PSCDL and execute the work under the
Smart City mission which will include ICCC and Smart Elements like, Intelligent Traffic
Management System, City Surveillance, Smart Poles, Smart Kiosk, Environmental sensors,
Variable Message Display, Public Address System, Public Wi-Fi, OFC Network, Incident
Management and Urban Flood Plain Management.

3.4 Objective of the Project and RFP

3.4.1 Objective of the Project

a) The DC & DR will be connected with various city level ICCCs and various applications of the
city from where feeds are to be received (except video feeds). It will host command center
application platform for all Smart City projects. It will also host other common applications
like integrated analytical layer / BI engine. Eventually all the smart components /
applications deployed in the cities will be integrated with the common platform layer for
managing smart city operations using the Open Application Programmable Interface (API)
Structure.

b) ICCC is required to be scalable for hosting more applications and services in future for
managing smart cities more effectively. ICCC will help in managing the utilities for Centre
Business District (CBD) areas of smart cities and in future capable of managing utilities of
entire Puducherry urban through city ICCC. It is also planned to have a Citizen Mobile
Application for providing various services to the citizens of the UT of Puducherry. The Citizen
Mobile Application will serve as a single unified platform for the citizens to engage with the
government, avail citizen centric services (G2C & B2C services), register municipality
related complaints, receive issue resolution, access live city feeds through the city
dashboard, learn about governance schemes, projects, and initiatives.

c) The four main components of the planned ICCC platform are: Citizen Collaboration,
Grievance Redressal, Citizen Service Delivery (G2C & B2C services) and City Dashboard.
The Citizen Mobile Application will receive grievances and inputs from both citizen and the
Government, using multiple channels (including external social media) to drive the different
redressal services, and in turn disseminate information using external media and the
platform itself as channels. All the discussion topics, surveys, polls, blogs are specific to
discussion groups. Hence, separate Government departments can create, and moderate
different discussion groups and the discussion topics, surveys, polls can be created within
these discussion groups and moderated by the concerned department using the admin
console. The solution also boasts of a robust analytical engine & dedicated team to monitor
the collaboration platform and stakeholders about the citizen sentiment/feedback on various
discussion topics/polls on regular intervals.

Page 12 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
d) The Enhancement and integration of existing E-Governance platform with ICCC is also in
the scope of SI. The SI is required to enhance the current application and add the missing
modules of E-Governance application which are required for seamless operations for all the
departments of the UT of Puducherry. The proposed ICCC for Puducherry smart city will
have physical capacity up to 50% of current plan for future activities like expansion of
services and its infrastructure based on the agreed plans of PSCDL/DRDM.

3.4.2 Objective of the RFP

1. In line with the above vision and an understanding of the pulse of citizens, following smart
city components are proposed to be executed vide this RFP:

a) Intelligent Traffic Management System

b) Creation of online/mobile based platform to facilitate tourists & visitors
c) City level application and Smart Dashboard
d) Command & Control Centre with Data Centre (DC) and cloud hosted Data Recovery (DR)
which will be an advanced integrated system to operate and manage multiple city service
operations.
e) Smart Kiosks.
f) Smart poles with CCTV, Wi-Fi, Air Quality Monitoring (AQM), Smart Street lighting, digital
billboard, Emergency call box, Public address system.
g) OFC
h) Flood sensor, Environmental Sensor, Variable Message Display, Public Address System,
Emergency Call Box
i) City Wide Surveillance system

2. Through this RFP, RailTel with the approval of client intends to select System Integrator
(SI) to:

a) Carry out location specific feasibility survey in consultation with different stakeholder units
of the Union Territory of Puducherry like DRDM, Police Department, Transport Department,
Puducherry Municipality, Electricity Department, Public Works Department, Town and
Country planning, Science and Technology etc., at the locations to be covered under the
Smart City projects jointly with RailTel.
b) Project period for SI would start with effect from issuance of work order to roll out of the
project and its five-year maintenance period.
c) Design, Develop, Implement, Roll-out and Maintain Governance Application and
infrastructure.
d) Design, Develop & Maintain city and state level Network highway with ITMS, City
Surveillance with Video Analytics, Smart Poles and OFC network.
e) Build/implement/operate Data Center and Disaster Recovery Center for all the smart city
projects outlined above.
f) Design, develop and maintain the Integrated Command and Control Center (ICCC) and
associated activities at the proposed location (to be finalized in consultation with different
stakeholder units of the Union Territory of Puducherry) with city-based controls and
analytics and a state-of-the-art Integrated

Page 13 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Command and Control Center (ICCC). The scope of State level ICCC infrastructure should
be such that it may be expanded to integrate smart city components and modules in
future.
g) The Common Data Center and Disaster Recovery Center for the Puducherry Smart City
shall be a platform for management for the operations of the proposed smart city projects
as well as all currently operational E-Gov and smart city initiatives in the UT of
Puducherry. The city specific ICCC shall be helpful in managing the smart operations and
emergency response in the locations/wards to be covered under the Puducherry Smart
City project.
h) Integration of the existing and future ICT based urban solutions (in coming future
during the project period) and ICCC solution of Puducherry Smart City Development
Ltd.
i) Design, Develop & Maintain city and state level Network highway with Smart Traffic &
Transport system, City Surveillance with Video Analytics & Kiosks system.

3. This RFP provides a high-level overview of the technology approach for setting up a
common DC/DR for the city based ICCC and includes in-depth details of the functional
roles of system components of PAN city application, and the interactions between roles,
to achieve an end-to- end system design and project objective. The SI will be responsible
for the following:

a) Design, Development, Implementation, Operation & Maintenance of ICCC and associated

Projects at Puducherry, its roll out, and integration with existing smart city applications/E-
Gov platforms.
b) Intelligent Traffic Management System
c) Creation of online/mobile based platform to facilitate tourists & visitors
d) City level application and Smart Dashboard
e) Command & Control Centre with DC and cloud hosted DR which will be an advanced
integrated system to operate and manage multiple services of the smart city
infrastructure.
f) Smart Kiosks.
g) Smart poles with CCTV, Wi-Fi, Air Quality Monitoring (AQM), Smart Street lighting, digital
billboard, Emergency call box, Public address system.
h) OFC
i) Flood sensor, Environmental Sensor, Variable Message Display, Public Address System,
Emergency Call Box
j) City Wide Surveillance system

The system is to be designed taking into consideration the future scalability and integration
with upcoming systems.

The system shall help to meet the following objectives:

• Security and Safety
• Improved & Smooth Traffic Movement in the City
• Effective Monitoring
• Improved Responsiveness
• Improved Management

Ensuring safety and security in fragile settings remains among the department’s key
Page 14 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 objectives in addition to handling crisis management during serious incidents, the list of
strategic objectives include:

• Live monitoring of critical infrastructures, city entry & exit points,

important locations/ public places in city area like area near to
railway stations, airport, bus stops and other public places through
surveillance camera.
• Live monitoring and control of Traffic Signals, Live monitoring of
over speeding vehicles, live monitoring of vehicles passing
Security and Safety through important locations of the city including entry and exit
points.
• Live alerts in case of an event/ incident.
• Help to identify, apprehend and prosecute offenders.
• Monitoring of suspicious people, activity, vehicles, objects etc.
with respect to protecting life & property and maintaining law and
order in the city.

• Access to Police by the Citizens for quick and effective

response, improved visibility and transparency.
Improved • Better Management of Security breaches based on alerts
Responsiveness received from system.
• Provide assistance to emergency services and fast turn-around
time.
• Address detection of hot listing vehicles.
• Assist in management and policing of large-scale events
(political, religious etc.).
• Aid to investigation by Police Department by integration of
Effective Monitoring
analytic tools.
• Providing evidence for criminal and civil action in the courts.
• Address the manual Traffic Signaling in the city.
Improved Traffic
Management
• Optimizing the traffic movement with help of Adaptive
Traffic Signal Control
• Help in maintaining Law & Order situations.
Improved
Management • Help in improving traffic discipline.

4 Project broad scope

4.1 Overview
The Overall aim is to select System Integrator (SI) for the Puducherry smart city project area
that would be responsible to provide an end-to-end ICT Solutions for the works mentioned in
para 3.4.2(3).

4.2 Services
The SI will design and develop concept of Smart City works and services, get it implemented
/ executed, rollout and including operation & maintenance period for 05 years on a turnkey

Page 15 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
basis.
4.3 Responsibilities

The SI would be responsible for designing in following packages mentioned below:

a) Design, Development, Implementation, Operation & Maintenance Central ICCC
along with DC at Puducherry
b) Puducherry Smart City rollout and integration with Central ICCC
c) Establishment of DR center and its integration with the ICCC, & DR
d) Deploy:

i. City Surveillance system - CCTV/PTZ camera with video analytics capabilities

ii. Intelligent Traffic management system - Adaptive Traffic Control System (ATCS), Red
Light Violation Detection (RLVD) and Automatic number-plate recognition (ANPR),
Automatic Traffic Counter & Speed Violation Detection (SVD)
iii. Environmental sensors, Flood sensor
iv. E governance - Citizen Services application
v. GIS platform integrated with Command-and-Control Center
vi. Variable Message Board (VMD),
vii. Smart Poles with Emergency Call Box, Public Announcement system, Smart street
lighting, digital billboard, public Wi Fi, etc.
viii. Smart Kiosk
ix. Emergency call box, Flood sensor, Public address system
x. OFC network.

e) Provide Operation & Maintenance services (O&M), including warranty & IT Helpdesk
services for a period of five (05) years from Go-Live.
f) The SI shall provide City network backbone through OFC fiber. The provisioned network
infrastructure shall be designed in a manner, which shall be capable to carry all the key
services that shall be implemented in due course by the authority.
g) In order to achieve the convergence with other city level projects, the Integration with
existing/proposed ICT systems as below are also envisaged, Water/sewerage SCADA,
Electrical SCADA, e- Health, Public Bike Sharing System, Transport Monitoring center,
ERSS (Dial 100/112).
h) Necessary civil and electrical interior infrastructure of the building for the City ICCC is to
be developed through this project. The ICCC building shall be provided by the Puducherry
Authority.

4.4 Establishment of ICCC

Under the Smart City initiative, it is envisaged to establish an Integrated Command &
Control Centre (ICCC) Data Centre, Disaster Recovery, Intelligent Traffic Management
system, Smart Elements and Smart Parking Management System shall be deployed &
commissioned at Puducherry in real time which shall be the single & dedicated place for
integrating, implementing, monitoring, controlling & commanding all City-Wide Smart
ICT for line departments.

4.5 Elements
Elements of Smart City are as follows but not limited to: -

Page 16 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
a) Integrated Command & Control Centre (ICCC)

b) Data Centre (DC) & Disaster Recovery Centre (DR)

c) Intelligent Traffic Management System (ITMS)

i. Red Light Violation Detection (RLVD)

ii. Speed Violation Detection (SVD)
iii. Auto-Number Plate Recognition System (ANPR)
iv. Adaptive traffic control system (ATCS),
v. Other analytics including Violation of Helmet, seatbelt rules, triple riding on bikes, stop
line violation, wrong side movement detection etc.
vi. E-Challans integration

d) City wide CCTV surveillance

e) Smart Elements

i. Smart Kiosk
ii. Public Address (PA) System / Emergency Call Box (ECB)
iii. Variable Messaging Display (VMD)
iv. Environmental Sensors for AQM
v. Flood Sensors

f) Any other E-Governance Application or Citizen facing application

g) Creation of online/mobile based platform to facilitate tourist and visitors

h) City level application and smart dashboard

i) Smart poles with CCTV, Wi-Fi, Air Quality Monitoring (AQM), Smart Street lighting,
Digital billboard, Emergency call box, Public address system.

j) OFC network.

k) Integration with other ICT systems of the Smart city.

4.6 Network Backbone

The connectivity between the field/end devices and the ICCC over its own network fiber
backbone. The network availability would be monitored through a Network Operations Centre
with implementation of a robust EMS, which will be housed along with the Integrated
Command and Centre. The SI will be responsible to deploy the Optical Fibre backbone for
the requirement for connectivity. Seamless and resilient connectivity required for the
following but not limited to:

a) Managed Service - End devices to Data Centre

b) Internet Bandwidth
c) DC DR Connectivity
d) DC Backhaul Bandwidth
e) VPN Remote Connectivity

Page 17 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
4.7 Smooth & efficient operation of ICCC

The SI is to further ensure that all the smart city components and devices are connected to
the Data Centre, DR and Command Control Centre in a reliable and resilient mode for smooth&
efficient operation of the ICCC. It should be noted that the subsequent sections of this
document detail out the expectations from the overall ICT Solution with respect to the above
components. The activities defined /described/discussed/ mentioned within this document are
indicative in nature and may/may not be exhaustive.

4.8 Connectivity to DC & DR

The SI is expected to have performed an independent & in-depth analysis of any additional
work(s) that may be required to be carried out to fulfil the requirements for the overall
Puducherry Smart City ICT Solutions and duly factorize those in while preparing a
response to this RFP.

4.9 Security & Monitoring of all ICT infrastructure

SI must make all the necessary provisioning for security of all ICT hardware’s along with
network backbone at DC, DR and Edge devices and their monitoring from the Central ICCC at
Puducherry.

4.10 Project Activities

While this RFP lists out primary ICT objectives for catering to immediate pressing needs,
keeping in view the long-term scalability and sustainability of the ICT Solutions, the Bidders
are encouraged to propose the State- of-Art, cutting edge ICT solutions for the proposed
project using Hi-Tech solutions.
The SI shall be responsible for carrying out the following activities:

a) Project Management
b) Survey and Detailed Design of all smart solutions components
c) Prototype Acceptance and Final Acceptance Testing
d) Software Development
e) System Integration
f) Testing & Pilot Deployment
g) Training
h) Change Management
i) Final Deployment & Documentation
j) Operational System Acceptance Tests
k) Comprehensive Operations and Maintenance of 5 years after Go-Live
l) Facility Management Staff

4.10.1 Implementation Phase:

Implementation of ICCC for Puducherry Smart City along with implementation of Citizen Mobile
Application and Integration of Existing E-Governance platform.
a) Activities related to Common Data Center and Data Recovery Center for the Smart City
project along with implementation of Citizen Mobile Application and Integration of Existing E-
Governance platform. Implementation of common applications on DC & DR and integration as
per the agreed Functional Requirement Specification (FRS), Software Requirement
Specification (SRS) and Standard Operating Procedure (SOP).
Page 18 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
b) Creation of city specific interface for accessing the common applications.

c) Integration of city specific applications with common command center platform.

d) Facilitating user acceptance testing and conducting the pre-launch security audit of
applications
e) Develop provisions for a scalable system which can integrate with more devices of the same
kind (as those deployed today) and can integrate with future applications and sensors
through open standards and data exchange mechanisms.

f) Planning, implementation and integration of all the necessary modules of Citizen Mobile
Application

4.10.2 Activities related to Smart City & ICCC Puducherry

i. Physical Setup of ICCC as per the layout agreed with the DRDM/PSCDL. This includes
activities like false flooring, false ceiling, partitions, network cabling, electric fitting, Online
UPS (built in storage), DG Set, auto on-off lighting system and other facilities as mentioned
above along with required furnishing of the complete DC facility
ii. A Centralized Helpdesk and a Situation room will only be setup in ICCC
iii. IT and Non-IT Infrastructure installation, development, testing and production environment
setup
iv. Safety and security of IT and Non-IT Infrastructure
v. Housekeeping facility for ICCCs.
vi. Software Application customization, data migration, integration with third party
services/application
vii. Preparation of User Manuals, training curriculum and training materials
viii. Role based training(s) on the Smart City Solutions
ix. SoP implementation, Integration with City GIS Platform, Integration of solutions with
Command-and-Control Center
x. Network connectivity establishment and configuration between DC & DR, City ICCC, existing
applications (which are to be integrated with DC & DR and City ICCC).
xi. User training and roll-out of solution
xii. Integration of the various services & solution with DC & DR and ICCC platform
xiii. Submit Monthly Progress reports as per the defined format to DRDM along with invoices.
xiv.Submit Joint Monthly Progress reports after approval as per the format defined to DRDM
along monthly progress report on common DC and DR along with total invoices.
xv. Go-Live of City ICCC will happen in this phase only, where complete setup of the ICCC will
be required to be done along with complete integration with minimum 1 service.

4.10.3 Post Implementation Scope for the Operation and Maintenance Phase
a) Activities related to Common Data Center and Disaster Recovery Center for SmartCities

i. Operations and maintenance of DC & DR facility.

ii. Annual technical support for all hardware and software components for the O & Mperiod
iii. Overall maintenance of the DC & DR facility and continuity of operations as per Service Level
Agreement (SLA).

b) Activities related to City ICCC

Page 19 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 i. Deploying manpower at city level ICCC for solution maintenance and monitoring support
which includes change request management, bug tracking and resolution, production
support, performing version and patch updates
ii. Integration of various services of the city based on the requirements of the city
iii. Annual technical support for all hardware and software components for the O & M period
iv. Preventive, repair maintenance and replacement of hardware and software components
as applicable under the warranty and AMC services during the contract period
v. Provide a Helpdesk and Incident Management Support at State level till the end of
contractual period
vi. Recurring refresher trainings for the users and Change Management activities
vii. Provide facility, information and required access to DRDM/PSCDL/Municipal Corporation
or its authorized agency for doing various kinds of Audits as and when required
viii. Preventive, repair maintenance and replacement of non-ICT components as
applicable under the warranty and AMC services during the contract period
ix. LAN at ICCC
x. Overall maintenance of the ICCC facility and continuity of operations as per SLAs
xi. Overall maintenance of housekeeping and physical security at ICCC, DC & DR
xii. Provide necessary security to the ICCC premises and its setup during the period of
contract
xiii. Submit Monthly Progress reports as per the defined format to DRDM along with
invoices
xiv. Submit Joint Monthly Progress reports after approval as per the format defined by
DRDM/ PSCDL along monthly progress report on common DC and DR along with
total invoices.

4.10.4 Expectations from Integrated Command and Control Center Platform

ICCC platform shall be the ‘heart’ of the Smart City of Puducherry that assists in enhancing
efficiencies of city operations and management of all smart cities. It provides a holistic view
of all city operations allowing monitoring, control and automation of various functionalities at
an individual system level along with enabling cross-system analytics.
This application will be required to be installed on the common data center and disaster
recovery center for smart cities. This application platform will be common to all cities with
different instances of each city.
The business requirements that the Integrated Command and Control Center Application
Platform shall achieve are:
a) Shall enable cross-system and cross-agency coordination to monitor, operate and
manage the city in an integrated manner
b) Shall enable different agencies and departments of State and Cities to monitor and utilize
information of other departments for delivering services in an integrated and more
efficient manner
c) All systems being provided as part of this RFP and by others (mentioned in this RFP)
shall be integrated with Command Center Application as per the requirements of the
Project.
d) The platform shall enable various visualization and analytics of city operations to
improve decision making. These analytics shall be achieved via cross-system integration
of various systems and as per the standard operating procedure (SOPs) discussed and
agreed upon with the Client. Analytics shall include both prescriptive, predictive analytics
and cognitive analytics.
e) Command Center Application shall provide reporting capabilities for city administrators

Page 20 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 to keep record of city operations
f) Command Center Application shall ensure that integrity and confidentiality of all
information gained is always secure
g) Command Center Application platform shall be the integration point at which data from
across the city converges for processing. This shall allow all information to be managed
within the same network, eliminating many communication problems that are faced by
working in siloes
h) Command Center Application shall provide shift-based operations for an overall 24x7
support
i) Map and integrate all systems to city specific GIS platform being provided as part of this
RFP
j) The system shall be scalable to accommodate future growth and support hardware and
software additions and upgrades.

k) Command Center shall leverage information provided by multiple city systems to support
an integrated, seamless, proactive and comprehensive response mechanism for day-to-
day city operations and challenges. The platform shall provide a combination of system
layers that when combined shall make use of Data, ICT and ITS infrastructure,
advanced computing, analytics, and visualization to enhance the city’s intelligence. In
addition, it shall provide the tools for the city decision makers to better manage the
services they provide to its citizens.

l) There are several functions and systems that shall be managed out of the Command
Center Application. Depending on the type of systems and functions, they shall be
monitored and/or controlled from the Command Center Application and will have the
option of sharing a feed to another agency as required via the platform. This shall
integrate all the City Systems procured under the Smart City Mission, which include
systems procured through this project and system which are/will be procured as other
projects.

Note: Responsibility of integration is of the SI, whereas SI for other application which is to be
integrated, SI will be responsible for providing interface layer / API / Software Development
Kit (SDK) in its system for doing the application. Authorities will be responsible for getting
required interface layer / API / SDK for particular application from respective department
(whose application is required to be integrated with ICCC interface) for SI to integrate with
Common Command Center Application Expectations from Data Center and Data Recovery
Center of ICCC.

4.10.5 Expectations from DC & DR

a) DC & DR is required to host & save data related to common command center and
applications hosted in ICCC environment.
b) DC & DR will not host any smart application (implemented in smart cities) which is being
integrated with command center application. This smart application (which is being
integrated with command center application) is responsibility of the respective vendor /
SI of the city who is managing the particular application implementation and rollout.
c) DC & DR will also host common applications like Integration Layer, Analytical Layer,
Enterprise Management Software (EMS), Knowledge Management (KM), Information &
Cyber Security applications, etc. required for Command Center Applications and ICCC
working.
d) DC & DR will save data coming from the applications hosted in datacenter of ICCC

Page 21 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Puducherry
e) DC & DR should be able to receive information (ex: from the field devices) and send the
information to the ICCC platform or visualization layer.
f) DC & DR will only save log of the transactions performed with common command center
application.
g) DC & DR will also have dashboard views of the applications (integrated with command
center application) for historical data as required by the city.

4.10.6 Manpower and resources

The SI has to deploy all resources including manpower (project manager and his team with
sufficient number of assistants) and setup office in Puducherry within 15 days from the date
of issuance of work order.

4.11 SI’s Obligations:

a) SI obligations shall include all the activities as specified in this RFP. It shall be SI’s
responsibility to ensure the proper and successful implementation, performance and
continued operation of the proposed solution in accordance with and in strict adherence
to this RFP.
b) SI shall adhere to the Smart City Mission (SCM) guidelines issued by the MoHUA and the
advisories issued by SCM, MoHUA from time to time on the implementation of ICCC by
Smart Cities.
c) SI shall also satisfy the minimum functional and technical requirement, service level
agreement conditions, as specified in this RFP.
d) In addition to the aforementioned, SI shall provide services to manage and maintain the
said system and infrastructure as mentioned in the RFP.
e) Department of Revenue and Disaster Management, Puducherry reserves the right to
interview the team composition that shall be deployed as part of the project team. If found
unsuitable, the DRDM may reject the deployment of the personnel.
f) SI is encouraged to propose equipment which are compliant with “Make in India” initiative.
g) Department of Revenue and Disaster Management, Puducherry reserves the right to
require changes in personnel which shall be communicated to RailTel.
h) SI shall provide the project team necessarily comprising the following key resources
namely Project Manager, ICCC/ Command Center Expert, Solution Architect, Security
Infrastructure expert, GIS expert, Data Management expert
/Analyst, Business Analyst / Use-case/SoP expert, Network Architect, and Server/ Storage
& Database Expert only after assessment and approval of DRDM/PSCDL.
i) SI with the prior approval of Department of Revenue and Disaster Management/PSCDL
may make additions to the project team. SI shall provide Department of Revenue and
Disaster Management, Puducherry with the resume of Key Personnel and provide such
other information as the DRDM may reasonably require through RailTel. The Authorities
also reserves the right to interview the personnel and reject, if found unsuitable. In case
of change in its team members, for any reason whatsoever, SI shall also ensure that the
exiting members are replaced with at least equally qualified and professionally competent
members.
j) SI should submit profiles of only those resources who shall be deployed on the project.

Page 22 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Any change of resource should be approved by the tenderer and compensated with equivalent
or better resource. The Authority may interview the resources suggested by SI before their
deployment on board. It does not apply in case of change requested by the tenderer.

k) In case of change in its team members, SI shall ensure a reasonable amount of time
overlap in activities to ensure proper knowledge transfer and handover / takeover of
documents and other relevant materials between the outgoing and the new member.
l) SI shall ensure that their Team is competent, professional and possesses the requisite
qualifications and experience appropriate to the task they are required to perform under this
RFP. SI shall ensure that the services are performed through the efforts of their Team, in
accordance with the terms hereof and tothe satisfaction of the tenderer. Nothing relieves SI from
its liabilities or obligations under this contract to provide the Services in accordance with the
RFP and SIshall be liable for any non-performance, non-compliance, breach or other lossand
damage resulting either directly or indirectly by or on account of its Team.
m) SI shall be fully responsible for deployment / installation / development/ laying of network fiber
and integration of all the software and hardware componentsand resolve any problems /
issues that may arise due to integration of components.
n) SI shall ensure that the OEMs supply equipment/ components including associated
accessories and software required and shall support SI in the installation, commissioning,
integration and maintenance of these components during the entire period of contract. SI
shall ensure that the OEMs supply thesoftware applications and shall support SI in the
installation / deployment, integration, roll-out and maintenance of these applications
during the entireperiod of contract. It must clearly be understood by SI that warranty and
maintenance of the system, products and services incorporated as part of system would
commence from the day of Go-Live of system as a complete Smart city solution including
all the solutions proposed. SI would be required toexplicitly display that they have a back-to-
back arrangement for provisioning of warranty and maintenance support till the end of
contract period with the relevant OEMs. The annual maintenance support shall include
patches and updates the software, hardware components and other devices.
o) Factory visits may be required by the Authorities at the cost of SI to verify the claims of the
SI.
p) Site visits to any of the operating Command Centre / Data Centre developed by SI at cost to
SI may be required by client to verify the claims of the SI.
q) All the software licenses that SI proposes should be perpetual software licenses. The software
licenses shall not be restricted based on location and DRDM should have the flexibility to use
the software licenses for other requirements if required.
r) Authorities reserve the right to review the terms of the Warranty and Annual Maintenance
agreements entered into between SI and OEMs and no such agreement/contract shall be
executed, amended, modified and/or terminated without the prior written consent of the
tenderer.
s) An executed copy of each of such agreements/contracts shall, immediately upon execution
be submitted by SI to the Authorities.
t) SI shall take approval of the PSCDL board/DRDM/ RailTel for sub contract.
u) SI shall follow all the codal formalities while executing the work.
v) If a product is de-supported by the OEM for any reason whatsoever, from the date of
Acceptance of the System till the end of contract, SI should replace theproducts/solutions
with an alternate that is acceptable to the tenderer at noadditional cost to the tenderer
Page 23 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 and without causing any performance degradation.
w) The Licenses will be in the name of DRDM only.

4.12 SI’s Reporting Obligations:

a) SI shall monitor progress of all the activities related to the execution of this contract and shall
submit to the Authorities, progress reports with reference to all related work, milestones and
their progress during the implementation phase.
b) Formats for all above mentioned reports and their dissemination mechanism shall be discussed
and finalized along with project plan. The Authorities onmutual agreement may change the
formats, periodicity and dissemination mechanism for such reports.
c) Periodic meetings shall be held between the representatives of theAuthorities and SI once
in every 15 days during the implementation phase todiscuss the progress of implementation.
After the implementation phase isover, the meeting shall be held as an ongoing basis, as desired
by Authorities,to discuss the performance of the contract.
d) SI shall ensure that the respective solution teams involved in the execution ofwork are part of
such meetings.
e) All the goods, services and manpower to be provided / deployed by SI underthe Contract and
the manner and speed of execution and maintenance ofthe work and services are to be
conducted in a manner to the satisfactionof DRDM’s representative in accordance with the
Contract.
f) Authorities reserves the right to inspect and monitor/ assess the progress/performance of
the work / services at any time during the course of the Contract. Authorities may demand
and upon such demand being made, SIshall provide documents, data, material or any other
information which Authorities may require, to enable it to assess the progress/performance
of the work / service.
g) At any time during the course of the Contract, Authorities shall also have theright to conduct,
either itself or through another agency as it may deem fit, an audit to monitor the
performance by SI of its obligations/ functions inaccordance with the standards committed
to or required by the Authorities and SI undertakes to cooperate with and provide to the
Authorities any otheragency appointed by the Authorities, all Documents and other details
as may be required by them for this purpose. Such audit shall not include SI’s books of
accounts.
h) Should the rate of progress of the works or any part of them at any time fall behind the
stipulated time for completion or is found to be too slow to ensure completion of the works by
the stipulated time, or is in deviation to Tender requirements/ standards, the Authorities’
representative shall so notify SI in writing.
i) SI shall reply to the written notice giving details of the measures they propose to take to expedite
the progress so as to complete the works by the prescribed time or to ensure compliance to
RFP requirements. SI shall not beentitled to any additional payment for taking such steps. If
at any time itshould appear to the Authorities representative that the actual progress ofwork
does not conform to the approved plan SI shall produce at the request of the Authorities
representative a revised plan showing the modification to the approved plan necessary to
ensure completion of the works within thetime for completion or steps initiated to ensure
compliance to the stipulated requirements.
j) The submission seeking approval by the Authorities of such plan shall notrelieve SI of any of
his duties or responsibilities under the Contract.
k) In case during execution/implementation of works, the progress falls behind

Page 24 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 schedule or does not meet the Tender requirements, SI shall deploy extra manpower/
resources to make up the progress to meet the RFP requirements. Plan for deployment of
extra man power/ resources should betaken care by SI. SI shall prepare and distribute Service
level performancereports in a format by Authorities.
l) The reports shall include “actual versus target” Service Level Performance, a variance
analysis and discussion of appropriate issues or significant events. Performance reports
shall be distributed to the Authorities.
m) Also, SI may be required to get the SLA reports audited by a third party auditor under its
responsibility with necessary approval from Authorities. All related cost will be borne by
SI.

5 Project Scope of Work

5.1 Assessment, Site Survey and Project Plan

After signing of contract, the SI needs to deploy team locally proposed for the project and ensure
that a Project Inception Report is submitted to the Authorities which should cover following aspects.
The SI shall first carry out a detailed survey to identify & finalizethe locations, requirements vis-a-vis
proposed solutions.

a) Names of the Project Team members, their roles and responsibilities

b) 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).
c) Responsibility matrix for all stakeholders
d) Risks the SI anticipates and the plans they have towards their mitigation
e) Detailed project plan specifying dependencies between various project activities / sub-
activities and their timelines
f) The SI shall conduct a comprehensive study to establish the key performance indicators
(KPIs) for the project. The KPIs of the study shall be included in the survey.

g) The SI shall study the existing business processes, functionalities, existing management
systems and applications including MIS reporting requirements. Additionally, the SI should
provide detailed designs specifying the following:

i) Post completion of Survey the SI shall consult the various Stake Holder of the project, in
consultation with the Authorities, and finalize the locations for execution. Upon freezing
the locations for execution, the SI shall detail out the final functional requirement system
for each of the proposed ICT intervention and get a sign off from the user department and
the Authorities.

ii) Post finalization of the SRS and FRS the SI shall submit a High-Level Design Document
which shall cover the broad architecture and a solution document for each of the proposed
ICT intervention.

iii) The HLD will comprise of the compute, storage and the OS requirements.

Page 25 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
iv) Post HLD, the SI shall be submitting the Low-Level Design Document with the good for
construction drawing, network connectivity drawing, LPU details, if any, API for
integration, communication protocol etc.

v) Upon approval of LLD by the Authority the SI shall implement the said ICT
intervention.

vi) Software Requirement Specification (SRS), Test cases and conducting the PAT/FAT of
the project.
vii) Location of all field systems and components proposed at the junctions, (KML /KMZ file
plotted on GIS platform like google earth etc.)
viii) Location of Network Provider’s Point of Presence (PoP)
ix) Design of Cables, Ducts routing, digging and trenching
x) Electrical power provisioning.

5.2 Documents/ Drawings Submission after Award of Contract

SI shall submit documents and drawings as mentioned below within One (1) Months after
award of contract for review and approval from Client/ Consultant. Following are the minimum
list of documents and drawings to be submitted, however, SI shall not restrict himself to the
same and it is in the obligation of the SI to submit all supporting documents, detailed drawings
as requested by Client/ Consultant during engineering and execution stage.

5.2.1 Stage 1: Design engineering

a) Design basis report and individual system block diagram.

b) Overall system architecture and flow diagrams
c) Design calculation sheets for all systems
d) System and location wise Equipment list along with GIS coordinates
e) System and location wise Load list/ power requirement
f) System and location wise UPS load list System and location wise Heat load
calculation list
g) Technical specifications and datasheets for all systems.
h) Standard Operating Procedures (SOPs) for Integrated Command & Control
Center (ICCC).
i) Key Performance Indicators (KPIs) for each system.

5.2.2 Stage 2: Project execution

a) General arrangement drawings.

b) Job execution schedule
c) Equipment general arrangement, internal wiring and third-party integration provision
d) QAP and FAT/ SAT procedures
e) System/ equipment Installation/ erection drawings.
f) Installation manuals

Page 26 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
5.2.3 Stage 3: Post commissioning

a) As-built drawings
b) Training manuals and schedules.
c) Operation and maintenance manuals.
d) Spares list (recommended spares, commissioning spares and operation spares)

5.3 Finalization of Detailed Technical Architecture

Page 27 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
While implementing the ICT intervention the SI shall adopt the following:

a) Scalability - The system should also support both vertical and horizontal scalability. There
must not be any system-imposed restrictions on the upward scalability in number of field
devices, or other smart city components. The Applications proposed for various vertical
solutions shall be capable of handling 50% growth for the next 5 years. SI shall clearly
quantify the expansion capabilities of the application software without incurring additional
cost.

b) Availability -. The SI shall make the provision for high availability (N:N or N:1) for all
the services of the system. Redundancy has to be considered at the core components
level.

c) Security- 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. 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 endeavour to make use of the SSL/VPN technologies
to have secured communication between Applications and its end users.

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 supplied under this project.
The security services used to protect the solution shall include: Identification,
Authentication, Access Control, Administration and Audit and support for industry
standard protocols. 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

Page 28 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 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 OWASP top 10 principles. All the field devices will be
X.509 certified for compliance to policy change management and to ensure that there is
no default password.

d) Manageability - Ease of configuration, ongoing health monitoring, and failure detection

are vital to the goals of scalability, availability, and security and must beable to match the
growth of the environment. Network should be auto/manual configurable for various future
requirements for the ease of maintenance / debugging.

e) Interoperability - The system should have capability to take feed from cameras installed
by private / Govt. at public places, digitize (if required) & compress (if required) this feed
& store as per requirements.

f) Open Standards - Systems should use open standards and protocols to the extent possible
g) Single Sign On- The application should enable single-sign-on so that any user once
authenticated and authorized by system is not required to be re-authorized for completing
any of the services in the same session. For employees of the department concerned, the
browser-based application accessed on the intranet, through single-sign-on mechanism,
will provide access to all the services of the departments concerned (based on their roles
and responsibilities), Help module, basic and advanced reporting etc. Similarly, for
external users (citizens, etc), based on their profile and registration, the system shall
enable single-sign on facility to apply for various services, make payments, submit queries
/complaints and check.

h) Support for PKI based Authentication and Authorization- The solution shall support PKIbased
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.

i) Interoperability Standards- Keeping in view the evolving needs of interoperability,

especially the possibility that the solution shall become the focal point of delivery ofservices,
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 proprietarysoftware, particularly,
through the use of proprietary ‘stored procedures’ belonging to a specific database product.
The standards should:

1. At least comply with the published e-Governance standards, frameworks, policies and
guidelines available on http://egovstandards.gov.in (updated from time-to-time); and

2. Be of leading industry standards and /or as per standards mentioned in the technical
specifications

j) Application Architecture

1. 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
Page 29 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 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.
Standards should (a) at least comply with published e- Governance standards,
frameworks, policies and guidelines available on http://egovstandards.gov.in (updated
from time-to-time); and (b) be of leading industry standards and /or as per standards
mentioned in the technical specifications
2. The modules of the application are to be supported by the Session and TransactionManager 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 logof activities happening within the
system / application to avoid any kind of irregularities within the system by any User /
Application.

3. SI shall design and develop the Smart City System as per the Functional and Systemrequirement
specifications finalized.

4. The Modules specified will be developed afresh based on approved requirement.

5.4 Site Clearance Obligations and Other Relevant Permissions

5.4.1 Survey And Commencement of Works

Prior to starting the site clearance, the SI shall carry out survey of field locations, for buildings,
structures, fences, UG utilities’ – Power Cables & WaterPipelines, OFC Network of other Operators,
Trees, existing installations, etc. TheAuthorities 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
Authorities. Restoration will be the responsibility of the SI. Right of Way and Track rent will be
borne by PSCDL/DRDM.

5.4.2 Existing Traffic Signal system

The infrastructure of existing traffic signal systems including the aspects, controllers etc. will
be dismantled and replaced with the new systems whichare proposed and required under the
scope of this project. The dismantled infrastructure shall be delivered at the designated location
of PSCDL/DRDM without damage at no extra cost.

5.4.3 Electrical Works and Power Supply

The SI shall directly interact with PSCDL/DRDM for provision of mains power supply at all locations
for ICCC field systems. The SI shall be responsible to pay the electricity bills including connection
charge, meter charge, recurring charges etc. to the PSCDL/DRDM directly. SI shall have to submit
the challan of bill submission to PSCDL/DRDM. PSCDL/DRDM will reimburse the amount deposited
by the SI after verification in next billing cycle.

5.5 Miscellaneous:

a) Authority shall assist in obtaining all necessary go ahead, legal permissions, NOC (No
Objection Certificate) from various departments to execute the project. SI shall have to
identify and obtain necessary legal / statutory clearances for erecting the poles and
Page 30 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 installing cameras, for provisioning ofthe required power, etc. SI shall provide & manage all
necessary paper work to pursue permission from respective authorities. Commercial/legal
fees / RoW charges shall be applicable to Authority for obtaining the necessary
permissions.
b) The SI shall provide all material required for mounting of components such ascameras and other
field equipment. All mounting devices for installation of CCTV cameras such as mounting
bracket, Lens, Weather proof housing, Pole, Junction Box, Power Supply, Cables, accessories,
etc. shall be included in the costs of the respective component. The same is also applicable
to crossheads and cross arms, mounting brackets, stainless steel bands, screws and other
accessories.

c) All the equipment, software and workmanship that form a part of the service are to be under
O&M from the SI throughout the contract period.

d) SI shall also get comprehensive insurance from reputed insurance company for the project
duration for all the equipment’s / components installed under this project.

e) SI shall ensure all the equipment’s installed in the outdoor locations are vandal proof and
in case the equipment’s get damaged /stolen for reasonswhatsoever, it shall repair/replace
the same in the specified time as per SLAsat no extra cost to the Authority. All such costs
shall be factored in the comprehensive insurance of field equipment for the duration of the
contract.

f) Preventive maintenance shall be carried out once in a quarter along with corrective
maintenance and also when calls are placed by Authority or itsdesignated agency.

g) In addition to above, the SI shall be fully responsible for all maintenance activities for the
period between installation of equipment and roll-out of the system.

h) During implementation, if observed that any camera / field equipment requires change in
the field of view / orientation, it shall be done by SI withoutany extra cost.

i) In case of request for change in location of field equipment post installation, the same shall be
borne by Authority at either a unit rate as per commercials or a mutually agreed cost.

5.6 Design and Implementation of Integrated Command & Control Center System

The SI should ensure the successful implementation of the proposed ICCC Project as per the
scope of services described below. SI shall implement and deliver the following systems and
capabilities linked ICCC.

i. City Surveillance system - CCTV/PTZ camera with video analytics capabilities

Page 31 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 ii. Intelligent Traffic management system - Adaptive Traffic Control System (ATCS), Red
Light Violation Detection (RLVD) and Automatic number-plate recognition (ANPR) &
Speed Violation Detection (SVD)
iii. Environmental sensors, E governance - Citizen Services application
iv. GIS platform integrated with Command-and-Control Center
v. Variable Message Board (VMD),
vi. Smart Poles with Emergency Call Box, Public Announcement system, Smart street
lighting, digital billboard, public Wi Fi, etc.
vii. Smart Kiosk
viii. Emergency call box, Flood sensor, Public address system
ix. OFC network.

5.7 Design, Supply, Installation & Commissioning of the Field Equipment

The Scope includes Supply, Installation, commissioning and Customization (as required) of
various field systems which include Integrated Traffic Management System (ITMS) at Traffic
Junctions, City Surveillance System, Smart Poles, Smart Kiosk, VMDs, DC & DR and other IT
infrastructure required for successful operations of the ICCC project.

Based on the approved Survey report, the SI will undertake the system configuration and
customization in line with the changed, improved or specific requirements of the Authorities
including:

5.7.1. The implementation methodology and approach must be based on the global best
practices in-order to meet the defined Service Levels during the operation.
5.7.2. Best efforts have been made to define major functionalities for each sub- system of
ICCC system. However, SI should not limit its offerings to the functionalities proposed
in this RFP and is suggested to propose any functionality over and above what has
already been given in this tender with no additional cost.
5.7.3. The SI shall design the field level equipment architecture to ensure maximum
optimization of network equipment, poles, cantilever, mounting infrastructures, power
supply equipment including, electric meters and junction box.
5.7.4. Finally approved/accepted solution for each component of ICCC project shall be
accompanied with “System Configuration” document and the same should be
referenced for installation of ICCC systems at Junctions/Locations that are identified
within the scope of this project.
5.7.5. The SI shall be required to submit a detailed installation report post installation of all
the equipment at approved locations. The report shall be utilized during the acceptance
testing period of the project to verify the actual quantity of the equipment supplied and
commissioned under the project.
5.7.6. The SI shall be responsible for obtaining all permissions/ NOC and approvals
necessary to install the ICCC systems components as per the approved design.

The sub-systems included as part of the ICCC project which are required to be implemented
and integrated are given in the subsequent sections.

5.8 City Surveillance System – (CCTV Camera)

Page 32 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
The broad scope of work to be covered under this sub module will include the following, but is not
limited to:

5.8.1. This Component covers planning & implementation of the Surveillance system
comprising cameras and other field equipment at identified locations. Actual placement
of pole & number of cameras at each location, type of cameras, fixation of height &
angle for the cameras to ensure maximum coverage shall be done in consultation with
the Puducherry Smart City authority.
5.8.2. A detailed survey shall be conducted, by the SI along with a team of Authority and the
Puducherry police, at each of the strategic locations. This survey shall finalize the
position of all field equipment’s and the orientation/ field of view of the cameras.
Appropriate field of view snapshot shall be taken by a handheld camera for future
reference at the time of survey. The surveyors shall also finalize the approximate
location of foundation for junction box and camera poles. The route for all the
underground cable laying shall be finalized during this survey (wherever required).
Every detail, finalized during the survey, shall be demarcated on an AutoCAD drawing
by the SI and submitted to Authority in the form of a detailed site survey report along
with other details for its approval.
5.8.3. The SI shall install Surveillance System Cameras for CCTV monitoring and
management at all locations across Puducherry city mentioned in the respective
annexure.
5.8.4. The SI shall undertake due diligence for selection and placement of surveillance cameras
to ensure the optimized coverage of the traffic junction and other locations along with
all associated junction arms, accuracy of the information captured on the field and for
rugged operations.
5.8.5. The SI shall design, supply, and install the surveillance cameras as defined in the RFP;
all wiring connections for the system shall be installed by the SI. The SI shall supply
all of 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.
5.8.6. The SI shall be responsible for providing the entire necessary IT infrastructure for
monitoring, recording, storage & retrieval of the video streams at ICCC or any otherlocation
as specified in the RFP.
5.8.7. System shall provide inter-operability of hardware, operating system, software, networking,
printing, database connectivity, reporting, and communication protocols. SI shall prepare the
detailed report for field level requirements e.g. Cameras (types & numbers), Camera Mounting
requirements, Power Requirements, Connectivity Requirements etc. for perusal of Authority.
Indicative list of the field level hardware to beprovided by SI is as follows:
5.8.8. Cameras (Fixed Box Cameras, PTZ Cameras etc.)
5.8.9. Dome camera for the indoor applications – POP sites monitoring
5.8.10. Industrial Grade Switches
5.8.11. Outdoor Cabinets
5.8.12. Pole for cameras / Mast
5.8.13. Outdoor Junction box
5.8.14. UPS
5.8.15. Networking and power cables and other related infrastructure
5.8.16. SI shall use industry leading practices during the implementation phase w.r.t positioning and
mounting the cameras, poles and junction boxes. Some of the check-points that need to be
adhered to by the SI while installing / commissioning cameras are as follows:
Page 33 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
5.8.17. Ensure surveillance objective is met while positioning the camera such that the requiredfield of
view is being captured as finalized in field survey.
5.8.18. Ensure camera is protected from the on-field challenges of weather, physical damageand theft.
5.8.19. Make proper adjustments to have the best possible image / video captured.
5.8.20. Ensure that the pole is well placed for vibration resistance adhering to the road safety norms.

5.8.21. Appropriate branding or color coding (Police/Authority Branding) of poles and junctionboxes, to
warn mischief mongers against tampering with the equipment at the junction.
5.8.22. The functional requirements and technical specifications provided in this RFP are indicative and
carry guiding rule. The SI is free to offer products and solutions which meet requirements of the
RFP focusing on the outcome, future scalability, security, reliability and adherence to specified
SLA under this RFP, in line with applicable standards & best practices adopted in the industry. The
SI is encouraged to design an Optimized solution which is technically superior, innovative, proven,
better in terms of functionality and is cost effective. Any specified parameters mentioned in the
scope/technical requirement inthe RFP may be considered if it is required for meeting current &
future requirements during the contract period. The SI is fully responsible for the specified
outcome to be achieved.
5.8.23. For more details on technical and functional specifications of Surveillance Cameras, SIshould
refer to Section: 6.0 for Functional and Technical specifications.

5.9 Integrated Traffic Management System (ITMS)

The broad scope of work to be covered under ITMS sub module will include thefollowing, but is
not limited to:

5.9.1. Preparation of Solution Architecture for Adaptive Traffic Control System (ATCS) as per the BOQ for
installation of traffic signaling systems.
5.9.2. Installation of Vehicle Detectors, Controllers, Traffic Light Aspects, Poles, Cantilevers, Junction Box
and other required accessories at Traffic Junctions for successful operation of the ITMS project for
Puducherry Smart City.
5.9.3. Integration of ITMS field infrastructures with the proposed ITMS software application.
5.9.4. Configuration of traffic signal at each of the junction along with development of signal control plan
for individual operations, coordinated signal plan for the junction in sync with the area wide signal
plan for different operating conditions. The operating conditions may include different peak and
off-peak conditions, special events, contingency plans etc.
5.9.5. The functional requirements and technical specifications provided in this RFP are indicative and
carry guiding rule. The SI is free to offer products and solutions which meet requirements of the RFP
focusing on the outcome, future scalability, security, reliability and adherence to specified SLA
under this RFP, in line with applicable standards & best practices adopted in the industry. The SI is
encouraged to design an Optimized solution which is technically superior, innovative, proven, better
in terms of functionality and is cost effective. Any specified parameters mentioned in the
scope/technical requirement in the RFP may be considered if it is required for meeting current &
future requirements during the contract period. The SI is fully responsible for the specified outcome
to be achieved.

Page 34 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 5.9.6.For more details on technical and functional specifications of ITMS, SI should refer to Section # 6.0
for Functional and Technical specifications.

A. Traffic Violation Detection System

The broad scope of work to be covered under this sub module will include thefollowing, but
is not limited to:

a. The SI shall install the Traffic Violation Detection System at traffic junctions across the city. This system
shall capture the infractions of Red light and stop line violations at these junctions.
b. The SI shall design, supply, and install the Traffic Violation Detection System as defined in the RFPs,
all wiring connections to the traffic signal controllers and to the camera platforms shall be installed
by the SI. The SI shall supply all of the necessary equipment for the camera and detection system,
including but not limited to: computers, ancillary camera equipment, camera housings, camera poles,
warning signs and shall make the final connections to the camera.
c. The solution proposed by the SI shall seamlessly integrate with the existing E-Challan system proposed
under the scope of this project. RAILTEL / DRDM/ PSCDL shall facilitate to get access to the Vaahan
and Sarathi database. Bidder shall be required to access the same through use of appropriate APIs.
d. The SI shall be responsible for providing all the necessary IT infrastructure for analysis, storage &
retrieval of the infraction information at ICCC or any other location as specified in the RFP.
e. The functional requirements and technical specifications provided in this RFP are indicative and carry
guiding rule. The SI is free to offer products and solutions which meet requirements of the RFP
focusing on the outcome, future scalability, security, reliability and adherence to specified SLA under
this RFP, in line with applicable standards & best practices adopted in the industry. The SI is
encouraged to design an Optimized solution which is technically superior, innovative, proven, better
in terms of functionality and is cost effective. Any specified parameters mentioned in the
scope/technical requirement in the RFP may be considered if it is required for meeting current &
future requirements during the contract period. The SI is fully responsible for the specified outcome
to be achieved.
f. For more details on technical and functional specifications of Traffic Violation Detection system, SI
should refer to Section: 6.0 for Functional and Technical specifications.

B. ANPR System

The broad scope of work to be covered under this sub module will include thefollowing, but
is not limited to:

a) The SI shall install the ANPR Cameras at every entry & exit points of the city onmajor highway
and ITMS junctions/locations across the city. This system shall automatically capture the
license number plate of the vehicle at these junctions.
b) The SI shall design, supply, and install the ANPR camera system as defined in theRFPs, all camera
accessories such as IR Illuminators, camera housing and mounting shall be installed by
the SI. The SI shall supply all of the necessary equipment for the camera and local
processing system, including but not limited to: computers, local storage, and ancillary
camera equipment, camerapoles, warning signs and shall make the final connections to the
camera.

Page 35 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
c) The SI shall be responsible for providing all the necessary IT infrastructure for detection,
analysis, storage & retrieval of the number plate information at ICCC or any other location as
specified in the RFP.
d) The functional requirements and technical specifications provided in this RFPare indicative
and carry guiding rule. The SI is free to offer products and solutions which meet requirements of
the RFP focusing on the outcome, future scalability, security, reliability and adherence to
specified SLA under this RFP, in line with applicable standards & best practices adopted in
the industry. The SI is encouraged to design an Optimized solution which is technically
superior, innovative, proven, better in terms of functionality and is cost effective. Any
specified parameters mentioned in the scope/technical requirement in the RFP may be
considered if it is required for meeting current & future requirements during the contract
period. The SI is fully responsible for the specified outcome to be achieved.
e) For more details on technical and functional specifications of ANPR Cameras,SI should refer
to Section: 6.0 for Functional and Technical specifications.

C. RLVD System

The broad scope of work to be covered under this sub module will include the following, but
is not limited to:

a) The SI shall install the RLVD Systems at traffic junctions across the city. This system shall
capture the infractions of Red light and stop line violations at these junctions.
b) The SI shall design, supply, and install the RLVD system as defined in the RFPs, all wiring
connections to the traffic signal controllers and to the camera platforms shall be installed by
the SI. The SI shall supply all the necessary equipment for thecamera and detection system,
including but not limited to: computers, ancillary camera equipment, camera housings,
camera poles, warning signs and shall make the final connections to the camera.
c) The SI shall be responsible for providing all the necessary IT infrastructure fordetection,
analysis, storage & retrieval of the number plate information at ICCC or any other location as
specified in the RFP.
d) The solution proposed by the SI shall seamlessly integrate with the existing E- Challan
system proposed under the scope of this project. RAILTEL / DRDM/ PSCDL shall facilitate to get
access to the Vaahan and Sarathi database. Bidder shall be required to access the same
through use of appropriate APIs.
e) The functional requirements and technical specifications provided in this RFP are indicative
and carry guiding rule. The SI is free to offer products and solutions which meet requirements
of the RFP focusing on the outcome, future scalability, security, reliability and adherence to
specified SLA under this RFP, in line withapplicable standards & best practices adopted in
the industry. The SI is encouraged to design an Optimized solution which is technically
superior, innovative, proven, better in terms of functionality and is cost effective. Any
specified parameters mentioned in the scope/technical requirement in the RFP

Page 36 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 may be considered if it is required for meeting current & future requirements during the
contract period. The SI is fully responsible for the specified outcome tobe achieved.
f) For more details on technical and functional specifications of RLVD Cameras, SIshould refer
to Section: 6.0 for Functional and Technical specifications.

D. Speed Violation Detection (SVD) System

The broad scope of work to be covered under this sub module will include the
following, but is not limited to:

i. SVD camera will be installed on major highways of the city.

ii. Primarily, SVD will be at major locations along with real time visual indications of speed
violation on LED display board.
iii. System will be able to record the vehicle speed with proof of video/photograph andevent
time and date.

The SI shall design, supply, and install the SVD system as defined in the RFPs, all wiring
connections to the traffic signal controllers and to the camera platforms shall be installed by the
SI. The SI shall supply all the necessary equipment for thecamera and detection system, including
but not limited to: computers, ancillarycamera equipment, camera housings, camera poles,
warning signs and shall make the final connections to the camera

E. E-Challan Devices

The SI is required to supply devices for junctions to integrate in to the existing e- Challan
application for spot challan issuance.

The functional requirements and technical specifications provided in this RFP are indicative and
carry guiding rule. The SI is free to offer products and solutions which meet requirements of the RFP
focusing on the outcome, future scalability, security, reliability and adherence to specified SLA
under this RFP, in line with applicablestandards & best practices adopted in the industry. The SI is
encouraged to design an Optimized solution which is technically superior, innovative, proven, better
in terms of functionality and is cost effective. Any specified parameters mentioned in the
scope/technical requirement in the RFP may be considered if it is requiredfor meeting current &
future requirements during the contract period. The SI is fully responsible for the specified outcome
to be achieved.

5.10 Lightning-Proof Measures

The SI shall comply with lightning-protection and anti–interference measures for system structure,
equipment type selection, equipment earthing, power, signal cables laying. The SI shall
describe the planned lightning-protection and anti – interference measures in the As-Is report.
Lightning arrester for all pole shall be erected for the entrance cables of power line, video
line, data transmission cables. Signal separation of low and high frequency; equipment’s
protective field shall be connected with its own public equal power bodies; small

Page 37 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
size/equipment signal lightning arrester shall be erected before the earthling. The Internal
Surge Protection Device for Data Line Protection shall be selected as per zone of protection
described in IEC standards. Data line protection shall be used for security system, server data
path and other communication equipment.

5.11 Earthing System

All electrical components are to be earthen by connecting two earth tapes fromthe frame of the
component ring and will be connected via several earth electrodes. The cable arm will be
earthen through the cable glands. The entireapplicable IT infrastructure i.e. field locations/traffic
junctions or command centre shall have adequate earthing. Further, earthing should be done as
per Local state national standard in relevance with IS standard.

i. Install the earthing devices for the equipment, including lightning earthing, protection
earthing and shielded earthing. All earthing shall meet the related industry standards.

ii. The earthing cable shall be installed in a secure manner to prevent theft and shall be rustproof.
Earthing down lead and the earthing electrode shall be maintenance free.
iii. Earthing should be done for the entire power system and provisioning should be there toearth
UPS systems, Power distribution units, AC units, etc. so as to avoid a ground differential.
RAILTEL / DRDM/ PSCDL shall provide the necessary space required to prepare the
earthing pits.
iv. All metallic objects on the premises that are likely to be energized by electric currents should
be effectively grounded.
v. There should be enough space between data and power cabling and there should notbe any
cross wiring of the two, in order to avoid any interference, or corruption of data.
vi. The earth connections shall be properly made.
vii. A complete copper mesh earthing grid needs to be installed for the server farm area,every
rack needs to be connected to this earthing grid. A separate earthing pit needs tobe in place
for this copper mesh.
viii. Provide separate Earthing pits for Servers, & UPS as per the standards.

5.12 Junction Box / Outdoor Cabinet, Poles and Cantilever

i. The SI shall provide the Junction Boxes, poles and cantilever to mount the field sensors like
the cameras, traffic sensors, traffic light aspects, active networkcomponents, controller and
UPS at all field locations, as per the specificationsgiven in the RFP.

ii. Each intersection shall be fitted with outdoor cabinets dimensioned to host all equipment
necessary to operate enforcement systems and traffic surveillance systems as defined in this
RFP.
iii. SIs shall reserve additional room in the intersection controller cabinet to accommodate the
future system requirements

iv. The size of outdoor cabinet / Junction Boxes shall be sufficient to house all the system
components, which may be installed at the intersection or nearby. Boxesshall be dustproof and
impermeable to splash-water. They shall be suitable for the Puducherry’s environmental
conditions.

Page 38 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
v. The cabinets shall be of robust construction and shall include 3-point security- locking
mechanisms to prevent unauthorized access to the field equipment

vi. The Junction Box for UPS with Battery bank needs to be considered separately.

vii. It should be noted that the SI should design the Junction box keeping in mindthe scalability
requirements of the project.

viii. Temperature and Humidity Control: All enclosure compartments shall be equipped with a
natural convection air circulation system via provision of aircirculation filters that shall not
require maintenance and shall allow free circulation of air inside the enclosures to prevent
overheating as well as thebuild-up and effects of humidity and heat, without permitting
the entry of elements that might endanger system operation.

ix. SI shall ensure that all the hardware is placed inside the junction boxes that could withstand
temperatures prevalent in Puducherry throughout the year.

x. At selected traffic junctions, if the existing infrastructure of poles and cantilevers can be used
for mounting/installing the traffic light aspects then RAILTEL / DRDM/ PSCDL shall
facilitate to obtain NOC from respective department for installation by the SI. However, SI
will be responsible for obtaining all the necessary permissions etc. The details of traffic
junctions/locations are providedin Annexure VIII under Section of 12.0

xi. The SI shall ensure that all installations are done as per satisfaction of Authority.

xii. For installation of CCTV Cameras, PTZ Cameras etc. SI shall provide appropriate poles &
cantilevers and any supporting equipment. SI shall be required to supply, install, configure
and integrate surveillance cameras at the identified locations and thereafter undertake
necessary work towards their commissioning.

xiii. SI shall ensure that the poles erected to mount cameras are good, both qualitatively and
aesthetically

xiv. SI shall use the industry leading practices while positioning and mounting thecameras and
ensure that the pole / mast implementation is vibration resistant. Arrangements for bird scare
spikes on top of camera shall be made to prevent birds from sitting on top of camera box.

xv. The poles shall be installed with base plate.

xvi. Base frames and screws shall be delivered along with poles and installed by the SI.

xvii. In case the cameras need to be installed beside or above the signal heads, suitable
extensions for poles need to be provided and installed by the SI so thatthere is clear line of
sight.

xviii. SI shall be responsible to undertake required structural analysis regarding the regulated load
conditions and considering the respective wind load while installing the poles / cantilevers
for cameras and Variable Messaging Sign boards

Page 39 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
xix. SI shall provide structural calculations and drawings for the approval of Authority. The
design shall match with common design standards/ IS Codes as applicable under the
jurisdiction of Authority/authorized entity.

xx. SI shall coordinate with concerned authorities / municipalities for installation.

xxi. Poles and cabinet shall be so designed that all elements of the field equipmentcould be easily
installed and removed.

xxii. SI shall ensure that physical look of the installation area returns to neat & tidy conditions after
installation of poles, cantilevers etc. The placement shall bedesigned keeping in mind the
normal flow of vehicular traffic and pedestrian movement is not disturbed.

5.13 Power & UPS - for Field Locations

i. SI Shall coordinate with Energy distribution Company for provision of power for field
installations. Desired energy meters shall be installed in the junction box at appropriate
locations. Energy consumption costs shall be borne by SI during implementation and O&M
Period which will be reimbursed by RAILTEL / DRDM/ PSCDL at actual.
ii. UPS shall serve as a backup for commercially available utility power at the intersections
and shall ensure no-break functioning of all field components ateach intersection in event of
failure of utility power supply.

iii. SI shall carry out a study and identify locations to provide UPS backup, depending upon
power situation across city, to meet the camera and other field equipment’s uptime
requirements.

iv. SI shall install UPS at the identified intersections in secure, tamper-proof housing in corrosion
resistant cabinets.

v. SI shall ensure that the UPS is suitably protected against storms, power surges and lightning.

vi. SI shall provide UPS for efficient heat dissipation without air conditioning. It shall be able to
withstand temperatures prevalent in the Puducherry throughout the year.

5.14 Civil and Electrical Works

i. SI shall be responsible for carrying out all the civil work required for setting up all the field
components of the system including:

a) Preparation of concrete foundation for MS-Poles & cantilevers

b) Laying of GI Pipes (B Class) complete with GI fitting

Page 40 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
c) Hard soil deep digging and backfilling after cabling
d) Soft soil deep digging and backfilling after cabling
e) Chambers with metal cover at every junction box, pole and at road crossings
f) Concrete foundation from the Ground for outdoor racks

ii. SI shall provide electricity to the cameras through the aggregation point. Since this component
has dependency on approval from local authorities, it is recommended that SI plans this
requirement well in advance & submits theapplication to the concerned electricity distribution
agency with requisite fees, as applicable.

iii. SI shall carry out all the electrical work required for powering all the componentsof the system

iv. Electrical installation and wiring shall conform to the electrical codes of India.

v. SI shall make provisions for providing electricity to the cameras (PTZ and Fixed) via SJB
(Surveillance Junction Box), housing the UPS/SMPS power supply, with minimum backup as
defined in this RFP,

vi. For the wired Box cameras, SI shall provision for drawing power through PoE(Power over
Ethernet), while PTZ cameras shall be powered through PoE+ /dedicated FRLS power cable
laid separately along with STP cable.
vii. Registration of electrical connections at all field sites shall be done in the name of Authority.

viii. SI shall house the electricity meters inside the power cabinet as mentioned inthe controller
Cabinet section as above.

ix. Electricity Charges for implementation and O&M period for all the systems has to be borne by
the SI and cost of electricity will be reimbursed on monthly basisto SI by RAILTEL / DRDM/ PSCDL.

5.15 Cabling Infrastructure

i. The SI shall provide standardized cabling for all devices and subsystems in the field.
ii. 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.
iii. 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.
iv. Cabling must be carried out per relevant BIS standards. All cabling shall be
documented in a cable plan by the SI.

Page 41 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
5.16 Responsibility Matrix - Overall

Successf Puducher RAILT Infr a Othe r Oth PM Existi

# Key Activities ul Bidder ry EL & OEM Electricit Utiliti er O/ SI ng ICT
authority PSCD L s y es Dep
ts

Project Inception Phase

1 Project Kick Off R/A C C C I I I C I
Deployment of
2 R/A C C C I I I C I
manpower
Requirement Phase
Assess the
requirement of
3 IT Infrastructure R/A C C C C C C C C
and Non IT
Infrastructure
Assessment of
4 Business R/A C C C I I C C I
processes
Assessment of
5 requirement of R/A C C I I I C C I
Software
requirements
Assess the
6 Integration R/A C C C C I C C C
requirement
Assess the
connectivity
7 requirement all R/A C C C I I C C I
locations
(including
Building)
Assessment the
R/
8 Network laying C C C I I C C I
A
requirement
Assessment of
9 training R/A C C I I I C C I
requirement
Design Phase
Formulation of
1
Solution R/A C C C I I C C I
0
Architecture
1 Creation of
1 R/A C C C I I C C I
Detail Drawing
Detailed Design
1
of Smart City R/A C C C I I C C I
2
Solutions

Page 42 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Development
1 of test cases
3 R/A C C C I I C C I
(Unit, System
Integration and
User
Acceptance)

Preparation of
1 final bill of
R/A C C C C I C C I
4 quantity and
material
1
SoP preparation R/A C C C C C C C I
5
Development Phase 1 & 2
1
Helpdesk setup R/A C C I I I I C I
6
Physical
1
Infrastructure R/A C C I I I I C I
7
setup

Procurement of
Equipment ,
1
edge devices, R/A C C I I I I C I
8
COTS software
(if any), Licenses

IT and Non IT
1
Infrastructure R/A C C I I I I C I
9
Installation
Development,
Testing and
2
Production R/A C C I I I I C I
0
environment
setup
Software
2 Application
R/A C C I I I I C I
1 customization (if
any)
Development
2
of Bespoke R/A C C I I I I C I
2
Solution (if any)
2
Data Migration R/A C C I I I I C I
3
Integration with
2 Third party
R/A C C I I I I C I
4 services/applic
ation (if any)
Unit and User
2
Acceptance R/A C C I I I I C I
5
Testing

Page 43 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 2 Implementation
R/A C C I I I I C I
6 of Solutions

Preparation of
User Manuals ,
2 training
R/A C C I I I I C I
7 curriculum and
training
materials
Role based
2 training(s) on
R/A C C I I I I C I
8 the Smart City
Solutions
Integration Phase 1 & 2
2 SoP
R/A C C C C C C C I
9 implementation
3 Integration with
R/A C C C C C C C I
0 GIS
Integration of
3 solutions with
R/A C C C C C C C I
1 Command and
Control Centre

Go –Live Phase 1 & 2

3
Go Live R/A C C I I I I C I
2
Operation and Maintenance
Operation and
Maintenance of
3 IT, Non IT
R/A C C I I I I C I
3 infrastructure
and
Applications
SLA and
3
Performance R/A C C I I I I C I
4
Monitoring
Logging,
3 tracking and
R/A C C I I I I C I
5 resolution of
issues.
3 Application
R/A C C I I I I C I
6 enhancement
3 Patch & Version
R/A C C I I I I C I
7 Updates
3 Helpdesk
R/A C C I I I I C I
8 services

R/A = Responsible/Accountable

C = Consulted

Page 44 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
I = Informed

5.17 Project Deliverables

# Key Activities Deliverables

1 Project Kick Off Project Plan

2 Deployment of manpower Risk Management and Mitigation Plan

Assess the requirement of IT Functional Requirement Specification

3 Infrastructure and Non-IT Infrastructure document

4 Assessment of Business processes System Requirement Specification document

Assessment of requirement of Software

5 requirements Requirements Traceability Matrix
6 Assess the Integration requirement

Assess the connectivity requirement of all

7 locations (including Building)

Assessment of network laying

8 requirement Site Survey Report
9 Assessment of training requirement
HLD documents
LLD documents

Application architecture documents

Technical Architecture documents.

Network Architecture documents.

Logical and physical database design.

Logical and physical infra-architecture

11 Creation of Detail Drawing Data dictionary and data definitions.

GUI design (screen design, navigation,
12 Detailed Design of Smart City Solutions etc.).

Development of prototype (Unit, System

13 Integration and User Acceptance) Test Plans

Preparation of final bill of quantity and

14 material SoPs & KPIs
15 SoPs & KPIs preparation Change management Plan

Page 45 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
16 Helpdesk setup IT and Non-IT Infrastructure Installation Report

17 Physical Infrastructure setup Training Completion report

Application deployment and configuration

18 Procurement of all IT & Non-IT equipment’s report

19 IT, Non-IT and Cloud-based Infrastructure Unit Testing Report

Installation

Development, Testing and Production

20 environment setup

Development of Software Application

21 and customization (if any)

Integration of Third party

22 services/application (if any)

23 Unit Testing
24 Implementation of Solutions
Functional Testing Report
Preparation of User Manuals, training
25 curriculum and training materials

26 Role based training(s) on the Smart

City Solutions
Integration Testing Report

27 SoP & KPIs implementation

28 Integration with Smart Components

Integration of solutions with Integrated

30 Command and Control Centre

Completion of UAT and closure of

31 Integration Testing observations report

32 User Acceptance Testing

Go-Live Report
33 Go Live
Detailed plan for monitoring of SLAs and
Operation and Maintenance of IT, performance of the overall system
34 Non-IT infrastructure and Applications
35 Fortnightly Progress Report
SLA and Performance Monitoring
Page 46 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Monthly SLA Monitoring Report and Exception
36 Logging, tracking and resolution of Report
issues.

38 Patch & Version Updates

Issues logging and resolution report
39 Helpdesk services

5.18 Project Timelines – Phase wise

Time Schedule
Sr.
Stage Key Deliverables (In month (M) /
No.
Days)

Project Management, Supply,

Installation, Testing and
Commissioning of ICCC and other
Phase1(Impleme associated activities including Go-
1 T0+ 6M=T1
ntation period) Live. support at the time of
execution and the entire project is
to be rolled out on or before the T1
stage.
Operation and Maintenance of
Phase 2(O & M ICCC and other associated
2 activities and SLA calculation. T1+60M=T2
period)

Once the project is over including

O&M for five years with the
3 Phase 3 T2+2M
adjustment of flaws, dues,
penalties etc. for Handover.

T0: Date of issue of LoA/PO.

* If the there is any delay in the implementation of the project due to the delay of SI,
then the SI shall not be paid for the delay timeline & penalty may also be imposed as
per penalty clause.

Page 47 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
5.19 Project Timelines – Component wise

Timeline
Project
(Max
Component Deliverables Value of Penalty
Limit)

After T/0+2 weeks, a penalty of 2% per week

Successful
on the amount to be released thereof up
Deployment of
Deployment T/0+2 to the maximum value of 10% on the
All Resources as
of Resources weeks amount to be released. However, Delay
per project
beyond three (03) weeks would lead to
requirement
termination of contract.

Implementation After T0+180 days, a penalty of 5% on the

on of different amount to be released on completion of
milestone of the same milestone value per week up to the
Project, i.e., the maximum value of 10% on the amount to
project is to be T/0 + 180 be released on completion of same
Implementation
roll out in full- milestone. However, Delay beyond two (2)
of Project Days
fledge with all weeks would lead to termination of
certification, contract.
clearances on or
before T/0+180
days

Monthly Progress
Reports during
By 5th of
the
each After 5th of succeeding month, a penalty
implementation
Progress succeedin of Rs. 1000 per day with a capping of
on period and
Reports g month Rupees 1 lakh.
during the O&M
period

User
Acceptance
Test (UAT)
completion and After 15 days of T/0+180 days, a penalty
Project other T/0+180 of1 lakh per day with a capping of 15 lakh.
Deliverables completion days Delay beyond 60 days would lead to
certificates termination of contract.
enabling roll
Out

T/0: The date of issuing of LOA/PO to SI

The maximum Penalty is capped at 10% of the overall Contract value.

Page 48 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
If any financial penalty imposed on RailTel by Puducherry Authorities during the contract period
due to non-performance/non-compliance shall be borne by SI as per the above table. In addition
SI has to borne the SLA penalties / any other deductions by the Puducherry Authorities.

5.20 Project Defect Liability Period (DLP) / Warrantee of Product & Services

Bidder shall be responsible for Operation and Maintenance of each component (HW, SW, SW
Patches, Upgrades and Service) related to this RFP for period of Five (5)-Years after final
acceptance testing and handover to client.

• All hardware items should to be quoted with 5 years replacement warrantyfrom OEM and
onsite support and services.
• All software/subscription/licenses should be quoted with 5 years warranty, updates, upgrades
(wherever applicable), support and services from OEM"

Page 49 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6. Functional Requirement and Technical Specifications

The functional requirements and technical specifications are provided in the belowsections. The
SI is free to offer products and solutions which meet requirements of the RFP focusing on the
outcome, future scalability, security, reliability and adherence to specified SLA under this RFP, in
line with applicable standards & best practices adopted in the industry. All specified parameters
mentioned in the scope/technicalrequirement in the RFP may be considered for meeting current &
future requirements during the contract period. The SI is fully responsible for the specified outcome
to beachieved for the project. Some of the basic prerequisites that bidder shall fulfill the under
this RFP are mentioned below;

i. All hardware items shall be quoted with 5 years advance replacement warranty from
OEM/Supplier/Manufacturer and onsite support and services.
ii. All software/subscription/licenses should be quoted with 5 years warranty, updates,upgrades
(wherever applicable), support and services from OEM.
iii. Manufacturer Authorization Form should be submitted for each item clearlymentioning
the items for which the bidder is authorized to quote.
iv. OEM undertaking that the quoted product will not become end of sale within next
12 months.
v. OEM undertaking that the quoted product will not become end of support/end of
life for next 5 years.
vi. OEM undertaking that they have not been blacklisted by any Govt./PSU in India.
vii. Bidder should submit complete Bill of Materials for each item
viii. Incorrect/Incomplete Bill of Material may lead to rejection of bid.
ix. OEM of all active IT components should have online portal to raise tickets for support and
services.
x. Product serial numbers of all IT active components should be available in the OEMonline
portal for ease of maintenance and support.
xi. OEM should have end user web interface to log case with product serial number.
xii. Malicious Code Certificate:
(Both Bidder and OEM should submit following certificate along with the biddocument):

“This is to certify that the Hardware and the Software being offered, as part of the contract,
does not contain Embedded Malicious code that would activate procedures to:

a. Inhibit the desires and designed function of the equipment.

b. Cause physical damage to the user or equipment during the exploitation.
c. Tap information resident or transient in the equipment/network.

The firm will be considered to be in breach of the procurement contract, in case physical
damage, loss of information or infringements related to copyright and Intellectual Property Right
(IPRs) are caused due to activation of any such malicious code in embedded software.”

Details of Key Modules

6.1 Integrated Command and Control Centre
The Integrated Command and Control Centre (ICCC) serves to collate and standardize data from
various sensors for subsequent analytics and visualization together with initiating requisitealerts and
standard operating procedures (SOPs) in terms of responding to incidents. Theplatform should
support and be open for community development requirement and will beextended to citizens
Page 50 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
as and when required.

Proposed Solution

• Monitor and utilize information of other departments for delivering services in an integrated
and more efficient manner.

• Use of Big Data, ICT and infrastructure, advanced computing, analytics, and visualization to
enhance the city’s intelligence.

• Capturing real time information through sensors, cameras, GPS devices and citizen
feedback/input.

a) Envisaged Benefits

For Authorities,

• Efficient planning and control mechanisms

• Seamless integration

• Addressing issues based on real time data insights

• Better administration with real-time access to data across interventions. For Citizens,

• Citizen Engagement System - Citizen Services application – Open Data Collaboration

Platform for Better citizen services in a timely manner

• Improved user satisfaction

Integrated Command & Control Center capable of communicating, correlating,

collaborating with other city systems, departments such as emergency response forces,
utilities (energy, water and sewage), transportation, city surveillance, citizen engagement
platform, Traffic Enforcement System, etc.

To improve citizen service delivery through seamless integration and proactive monitoring of
departmental services, and to provide Integrate command and control center (ICCC) to
Puducherry Smart City Development Ltd.
The Long term objective of ICCC is to establish a collaborative framework where input from
different functional departments of PSCDL and other stakeholders such as City Corporation,
City Development, Town Planning Department, transport/RTO, fire, police, e-governance etc.
can be assimilated and analyzed on a single platform; consequently resulting in aggregated
city level information. Further, this aggregated city level information can be converted to
actionable intelligence, which would be propagated to relevant stakeholders and citizens.

As a first step is to design and commission ICCC to provide a common picture by assimilating
data coming from various field devices/sensors related to traffic, surveillance, variable
message signboard, Public Address System and other smart components installed on the field.

Objective is also to provide visualization / monitoring of ground situation through CCTV feed,
standard operating procedures and provide support in effective decision making and
response in real time manner.

6.1.1. Integrated City Operation Platform

The ICCC Platform should serve as a foundation for building the technology base of the smart
city and should harness advances in digital technologies in IoT, Big Data, BI, AI, Mobile and
Page 51 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
GIS. The Software Suite should cover a Digital platform to integrate the various urban systems
and Pre -integrated Application software covering Integrated Command
and Control Center, Mobile workforce Management, Citizen Engagement . It should also act
as a central system through which the city administrators can monitor and operate the various
city services intelligently and efficiently.

The proposed Smart City Software Suite should at the minimum support the following services
and capabilities.

Services Capabilities
Seamlessly 1. It should be able to connect, collect and process data from various
connect & urban systems and detect anomalies.
monitor urban 2. It should provide an easy-to-use interface to onboard and provision
systems sensor data and data from various applications systems
Analyze data
1. It should enable Intelligent automation of the workflows based on
in real time
anomalies detected including actuating devices/systems and work with
and
AI/ML system for predictive actions.
automate
2. It should enable the operator to configure various types of SOPs and
core
automate the processes
processes
Drive in-line 1. It should support ready to deploy Smart Cities AI/ML applications for
departments various domains to drive efficiency across various in-line departments.
operational 2. It should be integrated with a tool to support composing the data,
efficiency building ML models and deploy them as APIs to be used by various AI/ML
through AI applications.
1. It should enable effective management of City Operations through a
Build 360º
Integrated Command and Control Center Application System.
situational
2. It should enable handling of major events and incidents that occur in
awareness for
the city by unifying the data from the various systems and creating a
operations
common operating picture for Situation Management.
1. It should be integrated with Unified Workforce managementApplication
Empower city
system so that City Workforce across all departments can be integrated
workforce
and equipped with Mobile App to efficiently run their day today activities.
with insights
2. It should provide complete visibility to the events and real time insight to
to respond
take action faster by the workforce.
faster
1. It should be integrated with Citizen Engagement Application System to
Deliver civic engage with and allow citizens to raise grievances and avail civic services
services digitally.
digitally to 2. The Application should support delivery of the services through
citizens grievance Case Management System, City Mobile App and City Portal
integrated with Chatbot
Enable
community It should be integrated with Open Data Collaboration Platform and
driven provide an open data-sharing platform to foster community driven
innovation innovation and to enable communities to access data and build third-
through open party applications to deliver more services.
data

Page 52 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 ICCC Specifications

Sl No Parameters Requirements Comp

liance
(Yes /
No)

Make :

Model :

The digital platform should be a pre-integrated with IoT and AI

1
capabilities, thus enabling the city with actionable intelligence.

The platform should be able to integrate with any type of sensor

platform being used for the urban services irrespective of the
Data Acquisition
2 technology used. The Platform shall be agnostic to
from
communication channels such as LoRA, ZigBee, GPRS, Wi-Fi, IP
Sensors/Devices
Camera

It supports a secured multitenant layer to acquire and validate

3 data collected (push/pull) from the sensor and transform rough
data into valid, verified, possibly corrected data.

It should preprocess the data in real-time from the sensors using

4
Edge computing capability.

The Platform should provide integration support with low code,,

5
highly secured integration with edge devices .

ICCC application should enable local and real-time analytics on

6 the continuous streams of data from vehicles, systems,
appliances, devices and sensors of all kinds

The ICCC Application should integrate with domain specific IoT

Edge application which should be working, even it gets
disconnected from the IoT Edge Application cloud backend. It
7 Edge Analytics needs to store messages that would go upstream and saves
them until the device reconnects. Also, it should be able to
authenticate modules and child devices so that they can
continue to operate.

The Edge Analytics from domain specific applications should

work in conjunction with centralized analytics systems at ICCC, it
8
should further provide efficient time analytics across the whole
IoT ecosystem.

Page 53 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 ICCC should integrate with Domain specific Edge Applications
9 which are made up of two components that work
independently:

1. IoT Edge modules with containers that runs the Domain

10
specific IoT Edge services

2. Domain specific Modules deployed to IoT Edge devices and

executed locally on those devices. The IoT Edge Management
11
should run on each IoT Edge device and manage the modules
deployed on each device.

It should support bi-directional communication between

12
platform and the sensor system.

13 It should be network and protocol agnostic.

The platform should be able to collect and aggregate data in

real time from on-field sensors/Edge Infrastructure like Bin Sensors,
14
Water Sensors, Environment Sensors, Access Sensors, and
Actuators etc.

The Platform should support industrial protocols like OPC UA

BACNET (can be achieved through OPC UA, Modbus, IEC and
15
Serial communication) and IOT (LoRA, MQTT, Stomp, AMQP
Network etc.).
Protocol
Adoption The Platform shall integrate with domain specific applications
which include a broad range of Device Integration services for
establishing the I/O interface to field devices such as RTU’s, PLC's,
16
IBMS etc. systems with bi-directional control. Similarly, it should
seamlessly integrate with IoT devices/Sensors/gateways and
applications.

The Platform should provide the user with the ability to change
17 the encryption keys, without any interruption to the operation of
the system.

The Platform should set up individual identities and credentials

18 for each of the connected devices and help retain the
confidentiality.

The Platform should have a Backbone Messaging System like

19 Kafka for building horizontally scalable real-time data pipelines
to receive, store, route and deliver messages.

Backbone Platform shall contain Plug and play approach to integrate with
20 Messaging diverse M2M Protocols/ (IOT protocols )

Page 54 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 System The backbone messaging system, should be highly durable to
handle all the incoming messages and it should be able to
21
prioritize and allow the message to jump the queue based on
the priority.

The Platform shall automate the steps required to analyse data

Data from IoT devices. It should transform and enrich IoT data before
22
Normalization using it for real-time analytics and time-series data storage for
analysis.

It should support transformation of messages from native

23 protocol of devices to a common format and should have data
transformation adaptors to perform better analytics on runtime.

It should be agnostic to sensor technologies and integrate with

24
various types of sensor platform.

The Platform should allow normalization of all the in-coming data

25
from different devices of various OEMs.

The data Normalization approach shall be using Visual

programming (no code or low code) that helps the administrator
26
to provision various types of sensors and devices and normalize
the data.

With the help of the built-in ETL platform, the platform shall
cleanse the data, transform and load the data to create an error
27
free data pool, and provide secure access to that data using
data API(s) to application developers.

The Smart City digital platform should be pre-integrated with API

& ESB Integration System/ API management system that enables
28 various smart city applications to be integrated covering existing
and proposed new applications in a seamless manner and
provide service automation.

API Management System shall support various integration

29
methods through - API, Sockets, OPC UA (SCADA API), APIs, etc.

The platform should enable contextual information and

30 API correlation across domains and verticals (Multiple vendor and
Management Multi-sensor in future

Page 55 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 System The API & ESB subsystem/API management system shall cover -
31 API gateway, Key Manager, API Portal, ESB and Analytics &
Monitoring.

API Management System shall be capable of supporting policy

32 enforcement for API subscriptions, application creation, etc. with
the help of customizable workflows.

API Management System shall have custom behaviour

33 capability on lifecycle transitions from cradle to grave: create,
publish, block, deprecate, and retire

Normalized APIs for the City Application domains should be

available (Parking, Outdoor Lighting, Traffic, Environment, Urban
mobility etc.) to monitor, control sensor and/or actuators
34
functionality to enable app developers to develop apps on the
platform. For example, Lighting APIs: Vendor agnostic APIs to
control Lighting functionality

API Management System should possess Cross collaboration

APIs: Enabling contextual information and correlation across
35
domains and verticals (Multiple vendor and Multi-sensor in
future)

The platform should enable decentralized API management

36 API Gateway
policies

The platform should authenticate and authorize API requests

from any client or device types that requests the resource servers
37 Key Manager
which are operating on traditional and microservice
architectures.

The API portal shall be the repository of standard APIs for

38
consumption by any third-party applications/ sub-systems

Normalized APIs should be available to carry out integration with

39
API Portal other platforms/applications

Enables City and/or its partners to write software adaptors based

on the API(s) provided by device vendors and have the ability
40
to control, monitor and collect the data from these street
devices

API Management System should support API composition,

41
protocol and data transformation

Page 56 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 API Management System should be capable of enforcing rate
42 limiting and dynamic throttling based on usage quotas and
bandwidth quotas
Manage
and Scale API Management System should be able to protect API
43 API Traffic backends with limit throttling capability

API Management System should possess extremely high-

44 performance pass-through message routing capability with
minimal latency

API Management System shall be able to publish API usage to a

pluggable analytics framework (Analytics framework includes -
45
Monitor and requests, responses, faults, throttling, subscriptions and self-sign
Monetize ups etc.)

API Management System should be capable of monitoring SLA

46
compliance

API Management System should be able to integrate with

47 centralized Logging and Monitoring platform to provides the
following services:

API Management System shall have Statistical graphs for API

48 latency and API usage comparison to monitor API and
application performance

API Management System shall have the ability to analyze logs

49 pertaining to application errors, API deployment stats, Login
errors, number of API failures and access token errors

API Management System track consumer analytics per API, per

50
API version, per tier and per consumer usage

API Management System should have configurable payment

51
schemes to monetize API usage through policies

API Management System should possess integrated ESB solution /

52 API management system capability of ensuring pluggable
Services approach to Smart City Applications
and
Protocol API Management System should have pre-configured
53 Support connectors across various Smart City Solution vendor, payments
gateways, CRM, ERP, social networks or legacy systems

Page 57 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 API Management System should support formats & protocols
54
such as JSON, XML and SOAP etc.

API Management System should support Network transport

55
protocols such as HTTP, HTTPS, WebSocket.

API Management System should have adapters to COTS systems

56 such as SAP BAPI and IDoc, IBM WebSphere MQ, Oracle AQ and
MSMQ

API Management System should possess following routing

57 capabilities such as header based, content based, rule-based
and priority-based routing
Route,
Mediate and
Transform
Data API Management System should possess mediation capability to
58 support all Enterprise Integration Patterns (EIPs), database
integration, event publishing, logging & auditing and validation

API Management System should possess payload transformation

59
capability.

60 The access to data should be highly secure and efficient.

61 Access to the platform API(s) should be secured using API keys.

API Management System should support security standards:

62 OAuth 2.0, HTTPS over SSL, and key management help protect
API & Interface the data across all domains.
Security

API Management System should support security features built

for many of its components by using HTTPS, TLS for all its public
facing API implementations. For deployment where CCC
63
Software API(s) exposed to application eco system, API
Management, API security features and API Key management
functions are required.

API Management System should be capable of having security

64
policies ensured for all APIs exposed which would

65 Restrict API access tokens to domains/Ips,

66 Validate APIs payload contents against a schema

Page 58 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
67 Ensure all API access to the system rely only on OAuth2 standard
Control
Access and
Enforce Ensures Integrated Identity Server for application registration,
68
Security OAuth2 token generation & validation

API Management System should be capable of blocking the

69 subscription for an administrator and to restrict a complete
application

API Management System should be capable of configured

70 Single Sign-On (SSO) using SAML 2.0 for easy integration with
existing web apps

Data Processing Layer

The Smart City digital platform should be pre-integrated with

Complex Event Processing System with BPM enabling the
configuration of the Policy, alarm management and execution
71
of SOPs. The system shall provide extensive capabilities in
detecting anomalies and also correlating anomalies across
various city domains.

The Complex Event Processing sub-system should be cloud

ready that captures events from the Platform and diverse data
72
sources, processes the data, executes complex conditions, and
acts on the same through predefined Business process and rules.

The Complex Event Processing sub-system shall allow the city to

73 create complex analytics on sensor data with Adaptive
Intelligence

Complex Event The Complex Event Processing sub-system shall have a drag and
Processing drop functionality using which rules can be applied to a single
74
Engine stream of data or multiple streams from interconnected sensor
systems.

The Complex Event Processing sub-system shall process and

75 scale to handle millions of events in real time with in the time
range of 1 to 5 seconds.

Page 59 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The Complex Event Processing sub-system shall support
streaming and complex event processing types such as filters,
streaming aggregations, patterns, non-occurrence, anomaly
76
detection, Aggregative Functions (window based, or Start
Based, Group based), Joins (works with Windows) Pattern,
Sequence, Geo Spatial and etc.

The Complex Event Processing sub-system shall have Out of the

box support for event sources from the Platform like HTTP, TCP,
77
Kafka, JMS, MQTT, Email, File, RabbitMQ and social media
platforms etc.

The Complex Event Processing sub-system shall support for in-

memory data storage and rich data integration via out-of-the-
78 box store connectors for RDBMS like MSSQL, Oracle, MySQL,
Maria, Postgres, MongoDB, HBase, Cassandra, Solr, Redis,
Elasticsearch and Hazelcast etc.

It should provide an integrated development environment to

79 develop Object Model (OM) which defines the elements and
the relationships

It should be able to deal with the change in operational systems

80
based on the operator's decision

The Complex Event Processing sub-system shall Integrate with

81 REST services and clients to retrieve live analytics and stored data
and access management services.

The Complex Event Processing sub-system should allow

82
Application to

83 Generate alerts based on thresholds

84 IF, Then Else analysis - Based on input

The Complex Event Processing sub-system should calculate

85 aggregations over a short window (time, length, session, unique,
etc) or a long time period

86 Average, Sum etc

Page 60 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The Complex Event Processing sub-system should perform
87
Analytics based on geo spatial data which includes

88 Alert based on geo boundaries - Geo Fencing

89 Distance Travelled

90 Speed

The Complex Event Processing sub-system should calculate

91 aggregations over long time periods with seconds, minutes,
hours, days, months & years granularity

92 Correlate data while finding missing and incorrect events

93 Detect temporal event patterns

94 Analyse trends (rise, fall, turn, tipple bottom)

95 Run pre-treated machine learning models (PMML, TensorFlow)

Learn and predict at runtime using online machine learning

96
models

It should support Static rule processing, Context specific rule

processing,
97
Dynamic rule processing, Decision making through synchronous
stream processing, Query tables, Windows and Aggregation.

98 It should serve the following value propositions,

- Ability to respond to real-time data with intelligent &

99
automated decisions

- Should provide an environment for designing, developing,

100
anddeploying business rule & event applications

- Should provide an integrated development environment to

101 develop Object Model (OM) which defines the elements
and the relationships

- Should be able to deal with the change in operational

102
systemsbased on the operator's decision

Data Analytics Layer

Page 61 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The Smart City digital platform OEM should be pre-integrated
103
with analytics engine to enable necessary insights and analytics.

The Analytics sub-system should be an AI-based smart city

analytics platform module to maximize business value through
104 advanced machine learning capabilities. The machine learning
capabilities aid in automating policies that result in better asset
and infrastructure management.
Analytics Engine The platform shall be pre-integrated with analytics to perform
multi-dimensional analysis on incidents data supporting business
intelligence and machine learning capabilities that enable
105
delivery of pre-packaged analytics applications like dashboard,
reports, advanced analytics - disaster management, social
analytics, etc.

The Platform shall be integrated with analytics engine, and

106
which shall support following capability.

The Analytics sub-system should support multiple Data Sources.

107 Min below standard data sources should be supported from day
1 – CSV, TSV, MS Excel, NoSQL, RDBMS

The Analytics sub-system should be able to discover, compare,

and correlate data across heterogeneous data sources to
108
unravel the patterns that are previously hidden. At a broader
level system shall support following tasks:

109 Connect to a variety of data sources

110 Analyze the result set

111 Visualize the results

112 Predict outcomes

The Analytics sub-system should be capable of performing

113 descriptive, predictive, and also prescriptive analytics wherever
applicable.

The Analytics sub-system should have capability to analyse data

114 in motion to display the alerts in real-time and store the data in
centralized database for future trend analysis.

Page 62 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The Analytics sub-system should be capable of developing
115 predictive analytics based on the requirements of the city.
Domains can range from Solid Waste, Transport etc.

The Analytics sub-system should provide with end user access

ranging from ETL, integration of data from structured &
unstructured data sources, intelligence with simulation and
116
modelling and interactive dashboards with ad-hoc query,
integration with spreadsheets, proactive alerting, Scorecards
and so on.

The Analytics sub-system should provide capabilities to create

KPIs to measure progress and performance over time and
117 graphically communicate strategy & strategic dynamics using
Strategy maps, Cause and Effect diagrams, and Custom views.
Intuitive and dense visualizations must be available.

The Analytics sub-system should help simulate what if scenarios.

It should help visualize assets/resources at risk due to the
pending/ongoing incident, should render impacted region on a
GIS/2D map. The solution should help build the list of assets, their
118
properties, location and their interdependence through an
easy-to-use Graphical User Interface. Solution should highlight
not only the primary asset impacted but also highlight the linked
assets which will be impacted.

The subsystem should be capable of providing time-shifted or

119
offline analytics on the archived data.

It should provide capabilities for the analysis to run

120 autonomously, refreshing data and re-analyze the situation
continuously across a complex set of variables.

121 Analytics sub-system should provide visualizations dashboard.

In the visualization workspace, it should allow to change visual

122
attributes of a graph.

User should not be allowed to alter the graph/visualization

123
definition.

In the visualization workspace, user should be able to do the

124
following operations:
Analytics Engine
125 Visualizations - Change the graph/visualization type

126 - Print the graph

Page 63 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
127 - Export the graph

128 - Narrow down on the value ranges

129 - Toggle the axis labels

130 - Integrate with other 3rd party applications seamlessly

The Analytics sub-system shall have the capability to provide

sentiment analytics of configured key words/accounts through
internet crawling through the platform. Ability to categorize key
Sentiment
131 issues/topics/words in real time on social media platform
Analytics
(Instagram ,Twitter, Facebook, Website Discussion Forums, News
Papers) which are contributing to negative/positive perception
among citizens.

Platform should enable machine learning with big data,

132 providing the ability to obtain valuable insight from large
amounts of structured, unstructured and fast-moving data

AI Data Platform should enable organization and labelling of data by the

133
Pre-Processing intelligent methods of alignment and indexing

134 Platform should be capable of handling missing data

135 Platform should support data cleaning operations.

Platform should be capable of native support for asynchronous

136 execution of collective operations and peer-to-peer
communication

Platform should allow user to export models in the standard file

137
ML Libraries formats (Pickle, H5, ONNX)

Platform should enable fast, flexible experimentation and

138 efficient production through a hybrid front-end, distributed
training and ecosystem of tools & libraries

Platform should allow the user to convert ML model to a

139
bitstream, store it in disk and reloaded at any point of time.

Model Store and Platform should allow the user to do real time and batch
140
Service predictions using the models

Page 64 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Platform should create an API wrapper around the predicted
141
model and should be capable of deploying it as a web-service

Common Enabling System

The Smart City digital platform shall have the capability of

integration with Business Process Management (BPM) sub-system
142
that would enable the process automation, delegation, parallel
workflows, etc.

Business Process
Management It should be capable of handling parallel process flows, that
143 would carry out all possible combinations including split, merge
and cross reference of processes.

It should also enable the user to delegate or assign an activity to

144
individuals or teams.

Platform must provide ability to configure various geo-spatial

145 GIS Map Support data from different providers including but not limited to City GIS
systems

Platform must provide ability to support different geo spatial

146
formats from commercial and open geospatial standards.

System should support integration with any Map API services like
Google, Esri, Open Street, etc. It should be possible to visualize
147
all the Assets (Sensor, Devices, Vehicles, Cameras, other city
resources) on map.

It should be possible to visualize all the Assets (Sensor, Devices,

148
Vehicles, Cameras, other city resources) on map.

The Assets must be provided as layers with ability to switch these

149
layers and visualize the assets of only selected layers.

The GIS Maps should provide interactive visualization of travel

150 time and traffic based on the sensor data and data ingested
from 3rd party sources.

It should allow the operator to execute dynamic messaging

151 across the city through the sign boards to inform the citizens in
real time.

Page 65 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 GIS Platform shall support GIS Maps in following file format PDF,
JPG, PNG, Vector PDF Map , Web Map Service (WMS), GeoJson
152 defined by the Open Geospatial Consortium (OGC), Google
Map-aerial; terrain, Bing Map, aerial, satellite, hybrid, ArcGIS/ESRI
and Open Platform GIS Applications.

GIS platform should provide a picture-in-picture map view

153
capability,

Upon the availability of GPS positioning of a file, the user should

154 be able to quickly alternate between the video and map view
within the video player

The application must be able to ingest and present either a static

location (e.g., for a fixed camera) or dynamic location (e.g., for
155
mobile cameras) that allows users to validate the location where
the video was recorded at the time of the event

Map services and geospatial coordinates: Shall provide the

156 geographical coordinates of specific facilities, roads, and city
infrastructure assets.

Location engine
Geospatial calculation: Shall calculate distance between two,
157
or more, locations on the map

158 Location-based tracking locates and traces devices on the map

Security

The Platform should set up individual identities and credentials

159 for each of the connected devices and help retain the
confidentiality

The Platform should provide mutual authentication and support

encryption at all points of connection, so that data is never
160
exchanged between devices and IoT Platform without a proven
identity.

To maintain the integrity of the system, the Platform shall allow

161 the user to selectively revoke access rights for specific devices
as needed.

Page 66 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 IoT Security To ensure the flexibility for the device vendor, the platform should
allow the user to create Authentication and Authorization
162
policies based on device profile level, it shall also support the
below policies:

163 a) Standard Authentication

164 b) Custom Authentication

165 c) x.509 Certificate based Authentication

Standard Authentication should comprise of Time-based

166 password for the device to ensure that in case the device gets
compromised, it can only utilize the token for the defined time.

All IoT Device connecting to the IoT Platform shall be secured

167 through strict device Identity Policies and token-based
authentication
Security-IoT
Device Identity The Platform shall Support AES 128, 256 Based Payload
168
Registry Encryption.

The Platform shall have Per device authorization policies to

169
ensure zero data leak tolerance.

170 Role based access shall be enforced for all application activities.

Security-
User Identity The Platform should support LDAP to be used as an additional
171
and Access data store for user management and authentication.
Manageme
nt nt
Shall have Single Sign on and Multi factor authentication for
172
secure user access to application services

Data Governance / Role Based Access Control: The Platform

should support data governance & stewardship model, in which
173
roles, responsibilities are clearly defined, assigned, implemented,
documented and communicated

Data Protection / Production Data integrity: The Platform should

174 support procedure in place to ensure production data shall not
be replicated or used in non-production environment

Data Protection / Data at rest: The Platform should support

175
Data Security & encryption for tenant data at rest (on disk/storage)
Integrity

Page 67 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Data Retention: The Platform should support capabilities to
176
enforce tenant data retention policies

Data recover & restore: The Platform should support capability

177
to recover and restore data in case of a failure or data loss.

Data disclosure & privacy: The Platform should disclose data

attributes, elements collected from source. All the attributes
178 should be disclosed & appraised to data owner. With
appropriate approval from City authority, Platform should have
ability to encrypt sensitive data element at rest.

The Platform shall have the ability to configure user access and
Configurati authorization control to provide specific set of
on of Data information/data/application control to designated or
179
Security authorized set of users. For E.g.: Ability to restrict water
Features department operation team to view water billing data (if not
authorized).

A Cybersecurity framework as per guidelines of MoHUA should

be integrated with ICCC aimed at building a secure and resilient
Cybersecurity application for citizens and stakeholders of Smart City. The
180 framework and framework comprising of policy, procedures, and guidelines
security should be designed to protect the application and information;
build capabilities to prevent and respond to cyber-attacks; and
minimize damages through cyber-attacks.

The Platform shall be Integrated with data governance to ensure

181 only authorized owner have permission to read / write data into
the system.

The Platform shall allow storage encryption to prevent illegal

182
data and behavioral tracking activities

Data The Platform shall assure data quality in terms of accuracy,

183 Governance accessibility, consistency, completeness and updating.

The Platform shall Govern all aspects of API Access services

including data service descriptions, data consumption, service
184
usage, service discovery, service lifecycle management and
service policy

Monitoring - all the data access from the application shall be

185
logged and monitored

The Platform shall integrate with a centralized logging and

186 Monitoring platform which integrates with all part of platform
services for Audit and performance monitoring.

Page 68 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The Centralized Logging and Monitoring sub-system should be
187 integrated with all smart city application and the IoT platform to
give the user an operational view

The logging and monitoring system should be able monitor the

188 application/platform infrastructure for performance with time
series view of:

189 - Up time

190 - CPU Utilization

Centralized
Logging &
Monitoring - Network Utilization (Bytes received per second, Bytes sent
191
Platform persecond, Packet drops and Timed out connection)

192 - User connection count

193 - Disk connection count

194 - Process Count

195 - Total threshold count

Platform should keep track of sensor last seen date and time and
196
be able to detect disconnected sensors & raise alarms

197 The Platform shall allow time shifted analytics with the log data.

The user should be enabled to control all the platform service

198
from a single system, the control operation includes

199 - Service Restart

200 - Update Configuration

The system should allow user to get detailed SLA monitoring

201
along with SLA report

Provisioning and Administration Tool

The ICCC platform shall provide solution for enabling end to end
202 Platform Administration which includes Asset Management, Rule
Configuration & Workflow Management.

The solution shall have a view of all the sensors connected to the
203
platform with their health status for real time monitoring.

The solution shall support secure device onboarding process with

204
bulk uploading options.

The solution shall enable remote device management

205
capabilities via API.

Page 69 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The solution shall support remote health monitoring and
206
managing capability

The solution shall be capable of sensor health abnormality

207 detection and automated workflow execution with integrated
workforce app.

The solution should provide icon-based user interface on the GIS

208
map to report non-functional assets.

Provisioning & The solution should also provide a single tabular view to list all
209 Service assets along with their availability status in real time.
Management
The solution should allow maintenance personnel to manage
210 and plan incoming work requests and automatically generated
work from preventive maintenance programs.

The solution should provide proactive maintenance alerts (by

211
analysing live data and historic maintenance data)

The solution should provide accurate and up to date warranty

tracking from the date of commissioning, product lifecycle
212
management, alerts on warranty expiry dates for devices/
sensors

The solution shall provide all the capability to provision the

213 sensor/device, normalize, create policy, SOP and build the
necessary workflow for deployment.

The solution should provide access or restrict access to user

214
group for any actuators/devices.

The Asset Management functionality of the tool should enable

215 to manage events such as generating service order request for
faulty and disconnected.

Asset Management should be capable of policy configuration

such as preventive maintenance scheduling based on asset
216
maintenance frequency, installation date, Schedule asset shut
down or restart on pre-defined date and time

Asset Management should have capability of pre-defined SOPs

217
such as Notify service provider in case of asset failure

218 Intentionally left Blank

Asset Management should support creating check list for field

219
work force units for performing asset maintenance

Machine Learning Builder capability

Page 70 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 ML Learning Builder should provide an environment to build
machine learning models through low-code/no-code visual
220
toolkit for developing, deploying, and operating enterprise AI ML
driven applications.

The system also supports traditional ML models, time series

221
forecasting, and deep learning.

There shall be a tool for the city administrators to create analytics

/ predict outcomes, when necessary, the tool provided shall
222
allow the user to develop models for analytics using the
necessary data available to the user.

The Machine Learning Tool should have an easy-to-use, visual

223
interface that gives users the access to data exploration.

The Machine Learning Tool shall support data input from multiple
224
Machine data Sources for data accumulation.
Learning Builder
The Machine Learning Tool supports ready to use ML Pipeline for
prediction, recommendation,
225
optimization, forecasting, Natural Language Processing,
Anomaly detection.

The Machine Learning Tool should support users to choose from

226
multiple Machine Learning Model types like (Not limited to:)

- Auto ML: Users can select this option and the system
automatically selects the Algorithm based on best accuracy
227
- Manual ML: Users can select Algorithms manually and
provideparameters based on the selected Algorithm

- Geo ML: Users can select ML Algorithms especially built

228
forGeospatial Data.

Users can Export files in multiple data formats (CSV, PDF, Excel
229
etc.)

The Machine Learning Tool shall allow the users to load disparate
230 data sources and join, filter, and wrangle data, all without
having to write queries.

Dashboard

Configurable Configurable Dashboard should help in reducing the

231
Dashboard customization time for building the dashboard.

Configurable Dashboard should provide a single web interface

232 for configuring the data source to visualize the data using various
visuals available

Page 71 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Application should allow to connect various data sources for
fetching the data. The Configurable Dashboard shall provide the
233 user to connect with any data source provided in the
application for fetching the data and later can be configured in
the widgets

Standard Dashboard templates should be available for various

234 Smart City Domains- Surveillance, Traffic, Environment, Parking,
Waste Management, Energy, Buildings

The application should provide GIS based visuals for geospatial

235
analysis.

The application should allow user to configure the basic settings,

236 colour theme, etc. which need to get updated throughout all
the widgets built

The application will allow user to create widgets or similar which

can be used for building the dashboard. Once the widget
237
configuration is done, the same widget can be used in multiple
dashboards without the need to create multiple times

The user should be able to fetch the data from the saved data
238
source and configure the dataset for the selected widget.

The user should be able to view the configured widgets which

239 user can bring a common place and create the layout as per
the need.

The user should be able to save the dashboard and can get
240 shareable link which can be used to embed the dashboard in
any application

The user should be able to create a KPI defined on top the

241 connected data source. If the KPI has been met, a pre-defined
process should be executed.

ICCC Application shall integrate with other Smart City

242
Applications/E-Governance Platform

243 a) Smart parking system

244 b) Intelligent Traffic Management System -

Adaptive Traffic Control
System (ATCS), Red Light Violation Detection (RLVD) and
Automatic number-plate recognition(ANPR), Automatic Traffic
Counter and Classifier (ATCC) & Speed Violation Detection
(SVD)

c) City Surveillance system - CCTV/PTZ

245
camera with video analytics capabilities

246 d) Environment management system -

Environmental sensors
Page 72 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
247 e) Variable Message Board (VMD),

f) E governance - Citizen Engagement

248
System - Citizen Servicesapplication –
Open Data Collaboration Platform
249 g) Storm Water level Monitoring system

h) Smart Street Lighting system - Smart

250
Street light controllers(CCMS)

251 i) GIS platform integrated with Command-

and-Control Center
j) Smart Poles with Emergency Call Box,
252
Public Announcement system, Smart
Street lighting, digital billboard, public Wi
Fi, etc.
253 k) Information Kiosk

254 l) OFC network.

m) The Integration with existing/proposed ICT

systems as below are also envisaged,
255
Water/sewerage SCADA, Electrical
SCADA, e- Health, Public Bike Sharing
System, Transport Monitoring centre,ERSS
(Dial 100/112).

256 The application should:

- help the city operators to run the city efficiently by integrating

257 allthe alarms and provides an easy-to-use GUI interface
(web & client server)

- help manage: alarms, map-based visualization of the city

258 General
assetsand events, execute SOPs and coordinate the
Capabilities
operations;
- provide 360-degree situational awareness and insights
259
acrossurban functions to city administrators.

Based on the incident type, system shall open the activities that
need to be carried out for the incident. The SOP shall provide the
actions like notification, correlate, dispatch, and close incident.
260
This activity should be defined in the administrator system for
each type of incident. This activity will be either manual or
automated.

It should be integrated with a real-time KPI dashboard that will

261 provide 360-degree situational awareness of the various urban
system operations and efficiency.

Page 73 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
262 The alarm management module should:

a) enable the ICCC to service all alarms

263 generated automatically by the city
digital platform for operators to
visualize the alarms, create incidents
and dispatch city workforce for action.
b) provide the details about each alarm
264
Alarm received from the varioussub-systems
Management integrated.
c) provide the operator details regarding
265 the source of the alarm,type of alarm,
generated time, priority, and elapsed
time to takeappropriate action.
d) provide advanced map & video
266
visualization for situationawareness.

267 e) provide an easy use GUI that is simple

to operate.
f) operator to view various types of
268
alerts in a single place andvalidate the
alerts for further processing.
The application shall provide map-based visualization for all the
269 details of the alarms and enable the operator in decision
making.

Application enables visualization of all the assets (camera,

270
access control, lighting) on the GIS map as a layer.

Unique identification (icon /symbol) should be provided for each

271
of the asset types.

The application shall allow health status (functional /non-

272
functional) of assets to be identified using colour code.
GIS Visualization

All field resources (vehicles /field workforce) should be location

273 enabled and mapped to the GIS with unique identification (icon
/symbol).

Each of the asset shall be created as a layer on the map and

274 can be turned ON /OFF by the operator depending upon the
alarm type and incident use case.

The application shall enable operator to search assets based on

275 the type and jurisdiction and enables operator to object based
interactive building floor plan, parking lot layouts, bus inside, etc.

The application shall provide video-based visualization of all the

276 associated cameras for the alarms in matrix view and enables
the operator in decision making.
Video Selection of cameras can be based on the following:

Page 74 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Visualization a) Map based selection
277
b) Jurisdiction/ camera selection from the
camera list alert thedetails of the alerts

278 The application should:

1. provide a 360-degree view of the situation lifecycle covering

279
Preparedness, Response, Recovery and Mitigation.

2. provide a portal for all the major incidents/events and help in

280
coordinating and managing response.

3. help monitor, control, and effectively take measures to save

281
lives and properties during any situation.

The system should have intelligence of the emergency policies

282 and procedures for streamlined information sharing among
multiple agencies.

The application should provide a rich GUI based web console

283 through which the administrators can monitor and respond
intelligently and efficiently to a situation.

The application should have the capability to integrate with

industry standard video management systems, video analytics
284
and unified communication to support advanced situational
awareness.

The application should provide a single view of all the active

situations to the operator in the home screen and the status of
285 the associated events against each situation such as the time for
completion of an activity, escalated activity due to SLA breach
etc.
General
Capabilities
The Application should provide a GIS based visualization of the
286
various locations of the events within a particular incident

287 There should be provision to create or modify a situation

The application should provide a repository of pre-defined SOPs

288 to be executed for a situation event management, incident
management, call receipt, health and safety etc.

Application should allow operator to define SOP based on the

289
situation

The Situation Management System supports decision makers

with a powerful machine learning based solutions to build
290 domain specific predictive analytics capabilities. The system
further enables the decision maker to get complete visibility of
the events, assets and support impact analysis.

Page 75 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The situation management application should also be
integrated with ICCC. Based on the nature of the incident and
the associated location intelligence and situational awareness
the ICCC operator can qualify an incident to be a possible
291
situation and alert the situation management operator. The
situation management operator should be provided with
advanced visualization capabilities with ability to correlate
various incidents as a situation.

Standard ICCC platform shall provide for authoring and invoking un-
Operating limited number of configurable and customizable standard
292
Procedures operating procedures through graphical, easy to use tooling
(SOPs) interface.

Standard Operating Procedures shall be established, approved

293 sets of actions considered to be the best practices for
responding to a situation or carrying out an Operations.

The users shall be able to edit the SOP, including adding, editing,
294
or deleting the activities.

The users shall be able to also add comments to or stop the SOP
295
(prior to completion).

There shall be provision for automatically logging the actions,

296 changes, and commentary for the SOP and its activities, so that
an electronic record is available for after-action review.

297 Platform must be able to create SOP workflows

Workflow must support both automated and manual activities

298
(tasks) and each of the activity should be configurable

The SOP Tool shall have capability to define the following activity
299
types:

Manual Activity - An activity that is done manually by the owner

300
and provide details in the description field.

If-Then-Else Activity - A conditional activity that allows branching

301 based on specific criteria. Either enter or select values for Then
and Else.

Notification Activity - An activity that displays a notification

302 window that contains an email template for the activity owner
to complete, and then sends an email notification.

SOP Activity - An activity that launches another standard

303
operating procedure.

Platform should support simple and complex event processing in

304
real time

305 Platform must be able to raise events based on thresholds

Page 76 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Platform must be able to raise events based on conditions
306
happening in a time window

307 Platform must raise events based on one or more events

308 Platform must map SOP workflows with event

Platform should provide an ability to request an approval before

309
SOP workflow is executed

Platform should provide an ability to create and manage

310
distribution lists for emails, SMS.

Platform should provide a responder mobile app for the field

staff to view real time events, manage their tasks, assign
311 tasks, report incidents and collaborate with back-office and
other field officers to address a SOP task
Responder mobile application should only display events and
tasks based on pre-configurable access rules based on
312
Responder Mobile department and region
App integrate Responder mobile application should support escalation
with ICCC hierarchy of the tasks or events are not redressed with-in a
313 defined SLA
Responder mobile application should provide an ability to
314
track field officers

Responder mobile application should provide collaboration

315
with the app for field officers and other staff to coordinate

Responder mobile application should be available on iOS and

316
Android latest versions

Platform must have redundancy baked into the architecture

317
High Availability

Platform must support on-prem and cloud deployments

318

Scaling Platform must be able to scale both horizontally and vertically

319
at both on-prem and cloud deployments

Proposed ICCC Platform should have been deployed and

operational in at least 3 smart cities/Safe City/ITMS Projects
in India /Global with Integration to minimum 5 different sub
systems /applications.
ICCC OEM
Document Proof: OEM Shall submit P.O and Completion
Criteria
Certificate/ Installation Notes/UAT Certificates from SI
as documentary proof.
ICCC Platform OEM should have valid ISO 9001 & ISO 27001.
320

Page 77 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
S.
Parameter Minimum Description
No
ICCC Will be required to integrate with Intelligent Traffic Management
solution using Open API standards.

ICCC will be required to receive the feeds from ITMS related to the traffic
violations in facilitation by PSCDL.

ICCC will be required to receive the health (Offline/Fault Detection) Alerts

of the Traffic Management Devices.
ITMS (Intelligent Traffic
1
Management System) Geo visualization of the alerts and Operational Status of Traffic
Management sensors & Camera.
All the information received from ITMS will get into Analytics layer of ICCC
and provide useful insights and KPI’s over dashboard and Generate the
Reports for the specific alerts.

SOP will be executed for specific Traffic Management sensor/Camera alerts

based on the alert type.
ICCC will be required to integrate with City Surveillance through VMS
using Open API standards.
ICCC will be required to receive the feeds from City Surveillance related
events.
ICCC will be required to receive the health alerts (Offline/Fault Detection)
of VMS device
2 City Surveillance System All the information received from City Surveillance system will be mapped
on GIS map.
ICCC will be able to create SOP and execute for specific VMS alerts

All the information received from City Surveillance will provide useful
insights and KPI’s over dashboard and Generate the Reports
ICCC will be required to integrate with Environmental Management System
using Open API standards.
ICCC should be able to map this information on the GIS layer and help
authority monitor the environment condition across the city.
Environmental Sensor / ICCC should also be able to trigger the commands / alerts (if required) to
3
Flood sensor the respective system.

All the information received from Environmental management system will

get into Analytics layer of ICCC and provide useful insights and KPI’s over
dashboard and Generate the reports based on the specific alert type.

ICCC will be required to integrate with Citizen Engagement Application

System including social platform (Citizen Mobile and Citizen Web portal)
Citizen Engagement
4 using Open API standards.
System
ICCC will be required to show case the citizen complaint Location on the
MAP Screen

Page 78 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 ICCC should also be able to trigger the commands / alerts (if required) to
the respective system.

All the information received from Citizen Engagement system will get into
Analytics layer of ICCC and provide useful insights and KPI’s over dashboard
and Generate the reports based on the specific alert type.

ICCC will be required to integrate with variable Message signboard sub

system using Open API standards.
ICCC should be able to map variable Message signboard locations over the
GIS layer.
The operator at ICCC should be able to click on the GIS map to view the
Variable Message
5 details of particular Variable message sign board’s status (On/off) etc.
Signboard
ICCC should also be able to trigger the commands / alerts (if required) to
the respective sub system.
All the information received from variable message signboard sub system
will get into Analytics layer of ICCC and provide useful insights and KPI’s
over dashboard.
ICCC will be required to integrate with Public Address System using Open
API standards.
ICCC should be able to show case the health Alerts (offline/Fault Detection)
of speaker device

ICCC Should be able to show case the Geo visualization of the alerts and
Operational Status of Speaker devices
6 Public Address System
ICCC should be able to execute the SOP based on the specific speaker
alerts.

All the information received from Public Address System will get into
Analytics layer of ICCC and provide useful insights and KPI’s over dashboard
and Generate the reports to specific alerts.

Ministry of Housing an d ICCC platform will have capabilities to integrate with India Urban Data
7 Urban Affairs (MoHUA) Exchange of MoHUA and share the data with www.data.gov.in. Please refer
IUDX platform to www.iudx.org.in for more details.

Advisory no 22 of cyber security framework guidelines recommended by

8
MoHUA shall be considered.

Page 79 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 ICCC should be integrated with future applications that are used for
engaging citizens, ICCC should be ready to fetch the standard reports and
KPI’s, display the same over the dashboard.
Further it is to be seen
the same can be
9 incorporated in BOQ as ICCC should fetch relevant KPI’s and reports from all future
optional item and used applications/System and display the same over ICCC dashboard.
only if budget allows.
ICCC should have provision for defining SOP’s related to future applications.

ICCC should generate the specific reports based on the alerts for the future
applications

Page 80 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.2 On Premise Data Centre (DC)
Functional requirement:

It is proposed to setup on premise DC for the video-based applications like ITMS and city
surveillance. The servers and storage set up are made with redundancy and high availability.
The solution shall have the capability to scale up to 50% for 5 years. Detailed elaboration
is mentioned in Applications Architecture under sec. 5.3.

6.2.1.42U Rack with All Accessories:

Sl. Compliance
Technical Specification
No (Yes / No)
Make <to be provided by the bidder>
Model <to be provided by the bidder>
1 ISO Certified.
Network Rack Dimension :( 800x1000) Rack.
2
Server Rack Dimension :( 600x1000) Rack.
3 Height: Full 42U.
4 Front & Rear perforated doors.
5 FHU WITH FANS, CASTOR (Lockable) and 4 nos horizontal cable managers
6 2 Vertical Power stripe (5/15 Amp Sockets)

Page 81 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.2.2 Core Router:

Compliance
Sl. No Specification
(Yes / No)

Make: <to be provided by the bidder>

Model : <to be provided by the bidder>

The Router Should support minimum 160 Gbps full duplex throughput and should
1 be of max 3 RU in height, 19-inch rack mountable. Should have 8x10G SFP+ and
2x40G QSFP based ports on day one.

Router should support Optical Transceiver Digital Diagnostic

2
Monitoring.

3 Router Should support Dual Images.

4 Router should support jumbo frames (9000) on all ports

5 Router should support BFD for single hop and multihop sessions.

6 Router should support MPLS-FRR to ensure high availability (optional)

Router should support OSPFv2, OSPFv3, ISIS, BGPv4.

7
(and Optional Configuration: MP-BGP, BGP confederations and route
reflector and RSVP-TE Fast Reroute (FRR)).
8 Router should support VRRP, VRRPv3.

9 IPv4 and IPv6 enabled from day one

The Router scaling should be minimum:

a. 1M IPv4 FIB routes and 64K IPv6 FIB routes.
b. 32 VRF/L3VPN and 200 L2VPN.
10 c. HQoS and minimum 2K Queues.
d. 1K number of MPLS Labels (Provider Router) - optional.
e. 6PE /6VPE, MPLS label-Switching router (LSR & LER)
functionalityOptional
f. 4K VLANs.
Shall support following class of service features:
a) Classification, policing, marking, shaping, filtering
b) Manage congestion using a weighted random early detection
(WRED) algorithm
11 c) Ingress policing
d) egress shaping
e) strict queuing , WFQ
f) Router should be able to classify based on 802.1 ad, 802.1 p, EXP
and DSCP bits

Shall support the OAM feature

12 a) 802.3ah/802.1ag/TWAMP
b) LLDP

Page 82 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 IPv6 Features
a) IPv6 Ping
13 b) IPv6 trace route
c) OSPF v3
d) IS-IS

Multicast Feature: It shall support following:

a) It shall support IGMP snooping v2/v3
14
b) The router shall support PIM Sparse Mode, RFC 4601
d) RFC 3569, Source Specific Multicast (SSM)

Routers should support Timing and Synchronization such as

15
Synchronous Ethernet or Precision Time Protocol (PTP)

16 The router shall support LACP 802.3ad and bundle upto 8 links.

The router should support IP SLA or RPM (or equivalent) for

performance measurements, it should also support monitoring of IP
17
SLA/RPM (or equivalent) probes using SNMP polling (OEM has to
provide SNMP MIB information)

The router should support filtering based on different parameters like:

18
src ip, dst ip, src port, dst port, protocol etc

The Router Should support DHCP server and client functionality, it

19
Should support DHCPv6 server/relay as well.

20 The Router Should support DHCP based option 82.

It shall support role-based privileges for the system access and radius
21
authentication.

22 The router should have a Console or Out-of-band Management.

Router should support Control-plane and management plane

23
protection

The Router Should support network management based on SNMP

24
v2c/v3, Syslog, RADIUS/TACACS+, Access via CLI.

The Router shall be able to operate at Operating Temperature: 0°C to 40°C and
25
Operating Humidity: 20 - 80% RH non-condensing.

The Router shall support dual redundant AC power supply and AC

26 Power voltage shall be 110 - 240V. Should have dual power supply
with hot swappable.

27 The Router Should be NEBS Level III or equivalent complied.

The Router operating system of the Routers category/series/family

28
should be MEF-9/14 or CE (Carrier Ethernet) Certified/compliant.

Page 83 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 All necessary SFPs, interfaces, connectors, patch cords (if any) &
29 licenses must be delivered along with the Router from day one.

Warranty –Hardware/ Software License should be for 5 years.

6.2.3. Firewall + IPS

Compliance
Sl.No Specification
(Yes /No)

Make :<to be provided by the bidder>

Model :<to be provided by the bidder>

The Firewall should be appliance based and must have

1 redundant power supply. Should have dual power supply with hot
swappable.

Firewall Should have minimum 8 Gigabit RJ45, 8 nos. of 1G SFP and 4 nos. of
2
10G SFP+ ports populated with the transceivers.

Firewall Should have console port and dedicated management

3
port.

4 Should have Firewall throughput of minimum 60 Gbps.

5 IPSec VPN throughput should be 40 Gbps or more.

NGFW throughput (With IPS) should be minimum 10 Gbps with enterprise mix
6
traffic.

Threat protection throughput should be minimum 8 Gbps with enterprise mix

7
traffic.

8 Must support at least 7,000,000 or more concurrent TCP connections.

Must support at least 4,50,000 or more new TCP sessions per second
9
processing.

Should Support Virtualization (Virtual Systems/Virtual Domains/Context).

10 Should have 6 or more Virtual Systems/Virtual Domains/Context license from
day one.

Should support both “bridge mode” or "transparent mode” apart

11
from the standard NAT mode.

Should provide NAT functionality, including PAT. Should support

12 NAT 66, NAT 64, Static NAT IPv4 to IPv6 and vice versa (VIP64 and
VIP46) and IPv6-IPv4 tunnelling or dual stack.

13 Should support IPv4 & IPv6 policies.

14 Provision to create secure zones.

Page 84 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Should support Link aggregation technology (IEEE 802.3ad) to
15
achieve higher bandwidth using redundant links.

16 Should support VLAN tagging (IEEE 802.1Q).

17 Should support Static routing and Dynamic Routing (OSPF & BGP).

18 Should support Active-Active/clustering.

Should support ISP Load balancing/Link Sharing and Failover and

19
should support link performance check based on packet loss, latency & jitter..

Should support protocols such as DES & 3DES, MD5, SHA-1, SHA-
256 authentication, Diffie- Hellman Group 1, Group 2, Group 5,
20
Group 14, Internet Key Exchange (IKE) v1 as well as IKE v2
algorithm, The new encryption standard AES 128, 192 & 256

Should support minimum 100 IPSec Site-to-Site and 2000 no of

21
IPSsec Site-to-Client VPN tunnels.

Should have integrated SSL VPN with license for 50 concurrent SSL
22
VPN users

Support for Client based VPN is mandatory and support for SSL
23
Web VPN is preferable.

24 Should support Windows, Linux and MAC OS for SSL-VPN.

25 Should support NAT within IPSec/SSL VPN tunnels.

26 Should support Stateful failover for both Firewall and VPN sessions.

27 Should have protection for 2000+ signatures.

28 Firewall able to prevent DOS and DDOS attacks.

29 Supports user-defined signatures (i.e., Custom Signatures).

Should have Application control feature with 1000 or more

30
application signatures.

Should perform Traffic Shaping/ Rate Limiting based on

31
applications.

Should control popular IM/P2P, proxy applications regardless of

32
port/protocol.

The appliance should facilitate embedded anti-virus/anti-

33
malware support

Gateway AV/ Antimalware should be supported for real-time

34 detection of viruses and malicious code for HTTP, HTTPS, FTP, SMTP,
SMTPS, POP3 and IMAP protocols etc.

Should also include Botnet filtering and detecting and preventing

35
Botnet command and control traffic

Page 85 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Should have configurable policy options. Possible to select traffic
36
to scan for viruses

The appliance should facilitate embedded Web Content and URL

37
Filtering feature

Web content and URL filtering solution should work independently

38
without the need to integrate with External proxy server.

URL database should have 100 million or more URLs under more
39
than 40 categories

Should be able to block different categories/sites based on User

40
Authentication.

Firewall should support management either through GUI/CLI or

41
through Central Management

42 Firewall should support logging to multiple syslog servers.

Hardware /Software should have 5 year Warranty.

43 Log & Reporting should be a dedicated solution out of the Firewall

The log & reporting tool with OS or any other licenses needs to be
bundled or quoted along with the solution. The logging and
44 analysis should either be an Appliance/Server or VM platform with
minimum RAID6/RAID10 usable 10TB storage to store logs for 6
months with suitable warranty.

Page 86 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6.2.4. Server Specification

Compliance (Yes /
# Parameter Minimum Specifications
No)

1.
Make : The solution will be provided by the SI along with the make

2. Model: The solution will be provided by the SI along with the model

2 processors Intel® Xeon® Scalable or AMD 3rd Gen processors

or latest
3. Processor
Minimum 10 cores/processor @ 2.1 GHz base frequency or
better

4. RAM Minimum 128 GB RAM

5. Internal Storage Minimum 2x480 GB SSD/Flash

2X1 Gbe copper ports and 4 x 10G Fibre Ethernet ports along
with transceivers SFP+ to connect TOR switch
6. Network interface
Optional: 1 X Dual-port 16Gbps FC HBA (or FCoE) for
providing FC connectivity

7. Power supply Dual Redundant Power Supply

8. RAID support As per requirement/solution

Licensed version OS, DB or any 3rd party Licenses should be

9. Operating System
supplied as per solution requirement.

10.
Form Factor Rack mountable/Blade

Server should support industry leading virtualization like

11. VMWare VCentre, Citrix XenServer, Hyper V, Oracle VM, KVM
Virtualization etc. In case the MSI proposes the solution to virtualization, then
they should propose suitable associated management solution
to meet or exceed the SLAs.

Server can be Rack mountable/ Blade Server. If blade server solution, chassis should be 19” rack-mountable, capable
12 of accommodating minimum 8 or higher hot pluggable blades with Two hot-plugs/hot-swap redundant modules for
connectivity to the external TOR Switches and to storage device.

Server should have remote management ILO/ILOM/IDRAC/IPMI/RSA or equivalent with support capabilities
13
include KVM over IP, power on, off & reset, virtual media, SNMPv2 or higher with appropriate perpetual licenses.

14 Server should provide with required power cables and rack mounting kit.

15 Server Average CPU load during peak time should be below 75% and RAM should be below 80%.

Page 87 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6.2.5. Storage Specification

Compliance (Yes
# Parameter Minimum Specifications
/No)

Make : The solution will be provided by the SI along with themake

1.

Model : The solution will be provided by the SI along with the

2.
model

1) IP Based/iSCSI/FC/NFS/CIFS
Solution/
3. 2) If bidder is offering FCoE based solution, corresponding ports
Type
must be present in server as well as storage controller.

1) Storage Capacity should be as per Overall Solution

Requirement (usable, after configuring in offered RAID
configuration). Storage Capacity after RAID to be provided with
20% additional capacity for future useto be provided.
2) RAID solution offered must protect against double disc failure.
4. Storage 3) Disks should be preferably minimum of 1.2 TB capacity for SSD /
SAS and 3 TB for SATA/ NL-SAS ( combination as per performance
and SLA requirements of overall solution)
4) To store all types of data (Data, Voice, Images, Video, etc)
5) Proposed Storage System should be scalable
(vertically/horizontally)

Hardware 1) Rack mounted form-factor

5.
Platform 2) Modular design to support controllers and disk drives expansion

1) At least 2 Controllers in active/active mode

2) The controllers / Storage nodes should be upgradable
6. Controllers seamlessly, without any disruptions / downtime to production
workflow for performance, capacity enhancement and software /
firmware upgrades.

7. RAID support Should support various RAID Levels RAID 0, 1, 1+0, 5+0 and 6

Minimum 64 GB of useable cache across all controllers. If cache is

8. Cache provided in additional hardware for the storage solution, then
cache must be over and above 64 GB.

Redundancy The Storage System should be able to protect the data

9. and High against single point of failure with respect to hard disks,
Availability connectivity interfaces, fans and power supplies

10 Should also include storage performance monitoring and management software.

11 Storage should use the latest stable technology platform, with support available for next 7 years.

12 Storage should be provided with the required optics, cables and rack mounting kit.

Page 88 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.2.6. Hypervisor

Compliance (Yes
Sl.No Specification
/No)
1 Make :<to be provided by the bidder>
2 Model :<to be provided by the bidder>
Hypervisor sits directly on the bare metal server hardware with
3 no dependence on a general-purpose OS for greater reliability &
security.
Must be support all leading Operating Systems like
4
Linux/Windows etc..
Proactive High availability capability that utilizes server health
5 information and migrates VMs from degraded hosts before
problem occurs.

Migration of VMs in case one physical server fails all the VMs
6
running on that server shall be able to migrate to another
physical server running same virtualization software.
Should support continued operations in the event of 1 node
7
failure or 1 disk failure.
8 Should support quick boot.
The Solution should support taking clones of individual Virtual
9
Machines for faster provisioning.
10 The Solution should support VM snapshots.

11 It should allow taking snapshots of individual Virtual Machines to

be able to revert to an older state, if required.

6.2.7. Core Switch

Compliance
Sl.No Specification
(Yes / No)

Make :

Model :

Should have minimum 16 nos. QSFP28 based 40/100G ports day one. Should
1
have dual power supply with hot swappable.

2 Should have at least 1.6 Tbps switching fabric.

3 Should have minimum 1000 Mpps (64 Byte) throughput

Should support transceiver Digital Diagnostic Monitoring for optical

4
ports.

5 Should have support for 802.3x flow control.

Page 89 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6 Should support at least 64K entries in the MAC table.

7 Should support at least 4000 active VLANs.

8 Should support jumbo frame (9000 Byte or above)

9 Should support Port-based VLAN, 802.1Q Tagged VLAN.

10 Should support LLDP or similar functionality.

11 Should support port mirroring.

12 Switch should support IPv6.

Should support 802.1D spanning tree control/RSTP support and MSTP

13
Support.

Should support spanning-tree portfast for fast convergence or

14
similar functionality.

15 Should support spanning-tree root guard or similar functionality.

Should support spanning-tree bpdu guard, bpdu filter or similar

16
functionality.

17 Should Support VRRP.

Should support ITU-T G.8032 Ethernet Ring Protection designed for

18 loop protection and fast convergence times (sub 50 ms) in ring
topologies

19 Should be Ethernet OAM compliant with IEEE 802.3ah/Y.1731.

20 Should support IGMP v1/v2/v3 and IGMP Snooping

Should support security features Broadcast, Multicast and Unicast

21
Storm Control

22 Should support security features DoS Attack Prevention

23 Should support console port and telnet/ssh based management.

Should support Static IPv4 and Ipv6 routing. It shall also support
24
OSPFv2 and OSPFv3.

25 Should support OSPFv2, OSPFv3 day one.

26 Should support BFD for OSPF.

27 Should support multicast routing PIM-SM.

Should support minimum 64K for IPv4 FIB routes and 16K for IPv6 FIB
28
routes.

29 Should Support for minimum 256 VLANs SVI or RVI interfaces.

Should Support VRRP, DHCP local server, DHCP relay and DHCP
30
snooping.

Page 90 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 31 Should support management features SNMP, NTP, RFC 2138 RADIUS

32 Should support 802.1Q VLAN, 802.1p priority queues.

Should support 8 hardware queues per port and shall support

33
ingress policing and egress shaping.

Should support Quality Of Service (QoS):

i) Priority Queue,
34
ii) Ingress policer,
iii) Rate Limiting (Bandwidth Control),

35 Should support automation NETCONF/YANG/OpenConfig

36 Should have redundant AC Power Supply 100 to 240 V AC.

37 Should have redundant fan modules

Switch to be mounted on a 19-Inch rack and should consume

38 maximum 2 RU. All accessories required for this mounting and
commissioning should be supplied.

Switch should comply to Operating Temperature range 0°C to 40

39
°C

Ports should be populated with transceivers as required.

40
Hardware/Software should have 5-year warranty.

6.2.8. TOR Switch & WAN Aggregation switch:

Compliance
S.No Specification
(Yes / No)

Make :

Model :

Should have minimum 24 SFP+ based 10G and 2 nos. QSFP28 based
1 40/100G ports day one. Should have dual power supply with hot
swappable.

2 Should have at least 400 Gbps switching fabric.

3 Should have minimum 300 Mpps (64 Byte) throughput

Should support transceiver Digital Diagnostic Monitoring for optical

4
ports.

5 Should have support for 802.3x flow control.

6 Should support at least 64000 entries in the MAC table.

7 Should support at least 4000 active VLANs.

8 Should support jumbo frame (9000 Byte or above)

Page 91 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
9 Should support Port-based VLAN, 802.1Q Tagged VLAN.

10 Should support LLDP or similar functionality.

11 Should support port mirroring.

12 Switch should support IPv6.

Should support 802.1D spanning tree control/RSTP support and MSTP

13
Support.

Should support spanning-tree portfast for fast convergence or similar

14
functionality.

15 Should support spanning-tree root guard or similar functionality.

Should support spanning-tree bpdu guard, bpdu filter or similar

16
functionality.

17 Should Support VRRP.

Should support ITU-T G.8032 Ethernet Ring Protection designed for

18 loop protection and fast convergence times (sub 50 ms) in ring
topologies

19 Should be Ethernet OAM compliant with IEEE 802.3ah/Y.1731.

20 Should support IGMP v1/v2/v3 and IGMP Snooping

Should support security features Broadcast, Multicast and Unicast

21
Storm Control

22 Should support security features DoS Attack Prevention

23 Should support console port and telnet/ssh based management.

Should support Static IPv4 and Ipv6 routing. It shall also support
24
OSPFv2 and OSPFv3.

25 Should support OSPFv2, OSPFv3 day one.

26 Should support BFD for OSPF.

27 Should support multicast routing PIM-SM.

Should support minimum 16K for IPv4 FIB routes and 8K for IPv6 FIB
28
routes.

29 Should Support for minimum 256 VLANs SVI or RVI interfaces.

Should Support VRRP, DHCP local server, DHCP relay and DHCP
30
snooping.

31 Should support management features SNMP, NTP, RFC 2138 RADIUS

32 Should support 802.1Q VLAN, 802.1p priority queues.

Page 92 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Should support 8 hardware queues per port and shall support ingress
33
policing and egress shaping.

Should support Quality of Service (QoS):

i) Priority Queue,
34
ii) Ingress policer,
iii) Rate Limiting (Bandwidth Control),

35 Should support automation NETCONF/YANG/OpenConfig or

equivalent.
36 Should have redundant AC Power Supply 100 to 240 V AC.

37 Should have redundant fan modules

Switch to be mounted on a 19-Inch rack and should consume

38 maximum 2 RU. All accessories required for this mounting and
commissioning should be supplied.

39 Switch should comply to Operating Temperature range 0°C to 40 °C

40 Ports should be populated with transceivers as required

Core Switch and TOR switch should be from same OEM.

41
Hardware /Software should have 5-year warranty

Page 93 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.2.9. Access Switch -8 Port – POE-Industrial Grade (Field Switch)

Compliance
S.No Specification
(Yes / No)

Make :

Model :

Should have minimum 8 GE ports.

1

2 Should have minimum 4 nos. SFP based 1 GE ports.

3 Should have at least 20 Gbps switching fabric.

4 Should support port Trunking of at least 4 nos. 1GE ports.

5 Should support 802.3af and 802.3at

6 Should support PoE of 8 ports.

7 Switch should have minimum POE power budget of 120 watts

8 Switch should support IEEE 802.3ad, IEEE 802.3az standards

Should support transceiver Digital Diagnostic Monitoring for optical

9
ports.

10 Should support Auto MDI-II/MDI-X uplink for all the twisted pair ports.

11 Should support for 802.3x flow control.

12 Should support at least 8000 entries in the MAC table.

13 Should support vlan range 1-4000 and at least 32 active VLANs.

14 Should support jumbo frame (9000 Byte or above)

15 Should support Port-based VLAN, 802.1Q Tagged VLAN.

16 Should support LLDP or similar functionality.

17 Should support port mirroring.

18 Switch should support IPv6.

Should support 802.1D spanning tree control/RSTP support and MSTP

19
Support

Should support spanning-tree portfast for fast convergence or similar

20
functionality.

21 Should support spanning-tree root guard or similar functionality.

Should support spanning-tree bpdu guard, bpdu filter or similar

22
functionality.

Page 94 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
23 Should support DHCP snooping

Should support ITU-T G.8032 Ethernet Ring Protection designed for

24 loop protection and fast convergence times (sub 50 ms) in ring
topologies

25 Should be Ethernet OAM compliant with IEEE 802.3ah/Y.1731.

26 Should support IGMP v1/v2/v3 and IGMP Snooping

Should support security features Broadcast, Multicast and Unicast

27
Storm Control

28 Should support security features DDoS Attack Prevention

29 Should support console port and telnet/SSH based management.

Should support management features viz. CLI, Web-based GUI,

30
SNMP, Syslog, NTP, RFC 2138 RADIUS

31 Should support Dual Images

32 Should support 802.1Q VLAN, 802.1p priority queues.

33 Should support Layer 2 QoS

Should support strict Priority Queue, Weighted Round Robin (WRR),

34
Rate Limiting (Bandwidth Control) or equivalent

Should have AC Power Supply 100 to 240 V AC with 50 to 60 Hz

35
without any external adaptors

36 Switch should comply to Industrial Grade with minimum Operating

Temperature range 0°C to 60 °C and Relative Humidity 95% or
better.
All accessories required for this mounting should be supplied from
37
day one. Hardware/Software should have warranty for 5 years.

38
Switch should have EMI CERTIFICATE of FCC/IC or CE or equivalent.

6.2.10. Access Switch-24 Port –POE -Field Switch (Industrial Grade)

Compliance
Sl.No Specification
(Yes / No)

Make :

Model:

Should have minimum 24 GE ports. Should have dual power

1
supply with hot swappable.

2 Should have minimum 2 nos. SFP based 1 GE ports.

Page 95 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
3 Should have at least 52 Gbps switching fabric.

4 Should support port Trunking of at least 2 nos. 1GE ports.

5 Should support 802.3af and 802.3at

6 Should support PoE of 24 ports

7 Switch should have minimum POE power budget of 540 watts

8 Switch should support IEEE 802.3ad, IEEE 802.3az standards

Should support transceiver Digital Diagnostic Monitoring for

9
optical ports.

Should support Auto MDI-II/MDI-X uplink for all the twisted pair
10
ports.

11 Should support for 802.3x flow control.

12 Should support at least 8000 entries in the MAC table.

13 Should support vlan range 1-4000 and at least 32 active VLANs.

14 Should support jumbo frame (9000 Byte or above)

15 Should support Port-based VLAN, 802.1Q Tagged VLAN.

16 Should support LLDP or similar functionality.

17 Should support port mirroring.

18 Switch should support IPv6.

Should support 802.1D spanning tree control/RSTP support and

19
MSTP Support

Should support spanning-tree portfast for fast convergence or

20
similar functionality.

21 Should support spanning-tree root guard or similar functionality.

Should support spanning-tree bpdu guard, bpdu filter or similar

22
functionality.

23 Should support DHCP snooping

Should support ITU-T G.8032v2 Ethernet Ring Protection designed

24 for loop protection and fast convergence times (sub 50 ms) in ring
topologies

25 Should be Ethernet OAM compliant with IEEE 802.3ah/Y.1731.

26 Should support IGMP v1/v2/v3 and IGMP Snooping

Should support security features Broadcast, Multicast and Unicast

27
Storm Control

28 Should support security features DoS Attack Prevention

Page 96 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 29 Should support console port and telnet/SSH based management.

Should support management features viz. Web-based GUI, SNMP,

30
Syslog, NTP, RFC 2138 RADIUS

31 Should support Dual Images

32 Should support 802.1Q VLAN, 802.1p priority queues.

33 Should support Layer 2 QoS

Should support Strict Priority Queue, Weighted Round Robin (WRR),

34
Rate Limiting (Bandwidth Control) or equivalent

Should have AC Power Supply 100 to 240 V AC with 50 to 60 Hz

35
without any external adaptors

Switch should comply to Industrial Grade with minimum Operating

36 Temperature range 0°C to 60 °C and Relative Humidity 95% or
better.
All accessories required for this mounting should be supplied by
37
day one. Hardware/Software should have 5 year warranty.

Switch should have EMI CERTIFICATE of FCC/IC or CE or

38
equivalent.

6.2.11 Wireless LAN Controller:

Compliance
Sl. No Technical Specification
(Yes / No)

Make:

Model:

1 WLC should support 1+1 failover for high availability.

The proposed WLC must be compliant with IEEE CAPWAP or equivalent for controller-
2
based WLANs.

The proposed WLC should be virtualized/ hardware appliance, rack mountable with 2
3
x10G (or better) Ethernet interface.

The proposed WLC should support both centralized as well as distributed traffic
4
forwarding architecture from day 1. It should be IPv6 ready from day one.

The proposed controller should support minimum 10K users/devices and WLANs-100
5
or more.

The proposed WLAN controller should be supplied with minimum 100 AP license from
6 Day-1 and can scale up to 250 APs without change / additional hardware. Additional AP
license will be procured in future.

Page 97 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The wireless access points must securely download image from WLC and should be
7
configured from WLC only.

8 The proposed WLC should support L2/L3 roaming for mobile clients

The proposed WLC should provide real-time radio power adjustments based on
9 changing environmental conditions and signal coverage adjustments. It should also
adjust radio channel automatically.

Should support dynamic bandwidth selection among 20Mhz, 40 MHz, and 80Mhz
10
channels.

11 Controller should support Wi-Fi 6, 802.11ax technology

The proposed system must support coverage hole detection and correction that can be
12
adjusted on a per WLAN basis.

Should support web-based authentication to provide a browser-based environment to

13
authenticate clients that do not support the IEEE 802.1X supplicant.

14 Should support port-based and SSID-based IEEE 802.1X authentication.

Should support MAC authentication to provide simple authentication based on a user's

15
MAC address.

Should support AP grouping to enable administrator to easily apply AP based or radio-

16
based configurations to all the APs in the same group

WLC should support Comprehensive Integrated Network Security

17 Services Wired/wireless, built-in Wireless Intrusion Protection System (WIPS), and se-
cure guest access with Captive web portal or equivalent solution.

WLC should provide BYOD Support. It should provide device fingerprinting and
18
required to help manage and secure user-owned devices.

19 WLC should support 802.11w to secure management frames, NAC integration support.

20 WLC should support guest access.

21 WLC architecture should support tunnel forwarding and local forwarding.

WLAN Solution should support captive portal with time-based access, Customize Guest
22 page and must have option for self-guest registration options, so that guest can auto-
matic register himself from day 1 or with equivalent solution.

WLAN Solution should have feature to create captive portal guest users for
authenticating using their User ID (Email Address/ Mobile Number/ Member ID) and
23
the received pass code on Email or SMS in order to complete the registration process
or any equivalent solution/ third-party components to full-fill the requirement.

24 SMS Gateway integration required for OTP should be provided along with the WLC.

Page 98 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6.2.12. Indoor Access Points:

General Minimum Requirement:

Sl.No Specification Compliance

(Yes /No)
Make :
Model:
1.
Access Points must comply with IEEE 802.11ax and must include tri radios (2.4
GHz, 5 GHz and dedicated sensor WIPS) or Access Points must include dual radios
with MU-MIMO and access point for dedicated dual band sensor (WIPS)

2.
Dual band 802.11ac , 2 x2 MIMO radio interfaces

3.
Sustained throughput shall be minimum 1 GBPS or more

4.
Support minimum 50 concurrent clients for Indoor

5.
Should support minimum 16 BSSIDs or more per radio
Features
6.
Should be integrated antenna

7.
The access point shall be capable of performing security scanning
and serving clients on the same radio

8.
Should have at least 1 Gigabit Ethernet port

9.
Should support power over Ethernet

10.
Should support 20, 40, and 80 MHz Channels

11.
Must have a dynamic or smart RF management features which allows WLAN to
adapt to changes automatically and intelligently in the RF environment

12.
Access Point Should have a Transmit power of 18dbm

13.
Must support regulatory domain as per country 2.412 to 2.462 GHz
and 5.745 to 5.825 GHz

14.
Should have LEDs to indicate device status.

15.
Must support fast secure roaming

16.
Should support RADIUS based 802.1 x authentication including EAP-
PEAP, EAP-TTLS, and EAP-TLS

Page 99 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
17.
Must support telnet and/ or SSH login to Aps directly for
troubleshooting flexibility

18.
AP should have mounted kit from the same OEM.
Hardware/Software should have 5-year warranty

19.
In case of Outdoor Access point the same shall be IP 67, Support
minimum 200 concurrent clients.

Page 100 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.2.13 AAA Server:
Sl.No Minimum Functional requirements Compliance
(Yes / No)
Make:
Model:
1.
The Solution should provide a highly powerful and flexible attribute-
based access control solution that combines authentication,
authorization, and accounting (AAA); posture; profiling; BYOD, and
guest management services on a single platform.
Solution should include all required licenses to perform above mentioned
capabilities for 300 endpoints from day one and scalable to 1000 over a period
of time.

2.
It should allow enterprises to authenticate and authorize users and
endpoints via wired, wireless, and VPN with consistent policy throughout
the enterprise..

3.
Provides complete guest lifecycle management by empowering
sponsors to on-board guests

4. Must be dedicated appliance based with each appliance supporting 1000

endpoints from day one

5. Enforces security policies by blocking, isolating, and non compliant

machines in a quarantine area /VLAN without requiring administrator
attention
6.
Offers a built-in monitoring, reporting, and troubleshooting console
to assist helpdesk operators and administrators streamline operations

7.
Allows you to get finer granularity while identifying devices on your
network with Active Endpoint Scanning

8.
Offers a rules-based, attribute-driven policy model for creating
flexible and business-relevant access control policies. Provides the
ability to create fine-grained policies by pulling attributes from
predefined dictionaries that include information about user and
endpoint identity, posture validation, authentication protocols,
profiling identity, or other external attribute sources. Attributes can
also be created dynamically and saved for later use

9.
Utilizes standard RADIUS protocol for authentication, authorization,
and accounting (AAA).

Page 101 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 10.
Verifies endpoint posture assessment for PCs connecting to the
network. Should be a persistent client-based agent to validate that an endpointis
conforming to a company's posture policies. Provides the ability to create
powerful policies that include but are not limited to checks for the
latest OS patches, antivirus and antispyware software packages
with current definition file variables (version, date, etc.), registries
(key, value, etc), and applications.

11. It should allow Administrators to create their own device templates.

These templates can be used to automatically detect, classify, and
associate administrative-defined identities when endpoints connect
to the network. Administrators can also associate endpoint-specific
authorization policies based on device type.

12. The Solution should have capability to collect endpoint attribute

data via passive network telemetry, querying the actual endpoints,
or alternatively from the infrastructure via device sensors on switches.

13. Should support full guest lifecycle management, whereby guest users can
access the network for a limited time, either through administrator
sponsorship or by self-signing via a guest portal. Should include guest portal
customize from day one
14. Solution should support receiving updated endpoint profiling policies and the
updated OUI database as a feed from the OEM database. Solution should have
profiling capabilities integrated into the solution in order to detect headless host.

6.2.14 Centralized-IT security Solution For ICCC

Sl. Compliance
Technical Specification
No (Yes / No)
1 The solution must utilize Client Server architecture where Central Endpoint Management
Console can be used for creating and distributing policies. Central Endpoint Management
Console should be able to create, manage and monitor all the endpoints across the
organization centrally. Central Endpoint Management Server should utilize On-Premise
architecture and no SaaS / Cloud model.
2 The solution should support All-in-One Centralized Management — deploy, manage and
monitor Clients on-premise or off-premise. Management Server console also should help to
provide real-time control and visibility into endpoints when they are either on or off corporate
networks.
3 Solution should support integration and synchronization with Microsoft Active Directory (AD)
to deploy the Agents to all the endpoints.
4 Solution should support installing and managing agents on Microsoft Windows 7 / 8 / 8.1 / 10 /
11 & Windows Server 2012+, Mac OS 11+, Linux, UNIX
5 Endpoint should be integrated with the on-premise sandbox solution for submitting suspicious
files for further analysis & can share the threat intelligence with the other endpoints.
6 Endpoint should block the access to the file till it gets the verdict from the sandbox.
7 Should be able to manually submit files to sandbox for analysis

Page 102 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 8 Solution should support Endpoint Protection features of Anti-Malware, Anti-Exploit, Web
Filter, Application Firewall, Vulnerability Assessment and Management, Software Inventory
Management and USB Control .
9 Solution should be able to Block Access to Malicious Websites, Scan Compressed Files, Scan
Network Files, Scan Removable Media on Insertion, Scan Email attachments.
10 Solution should support easy creation of security profiles with customizable features such as
Antimalware, Exploit Prevention, Application Firewall, Web Filter, USB Control etc. applied to
specific set of devices or for all devices.
11 The management server should support creation of Custom Installer Packages with included
Security Profiles to help simplify deployment and management of endpoints from a single
console.
12 Custom Installer Package should be available from web-link of Management Console in MSI /
EXE / DMG packages.
13 The centralized management console should be web-based and should support Role Based
Access (RBAC).
14 Solution must offer comprehensive client/server security by protecting enterprise networks
from Viruses, Trojans, Worms, Network Viruses, Spyware and Rootkits.
15 Solution must provide real-time on-access scanning for file systems to prevent or stop malicious
code execution.
16 The proposed solution should provide tamper protection to prevent end-users or malicious
actors from disabling the endpoint protection software.
17 Tamper protection should support configurable password in case emergency override is
required.
18 The proposed system shall be able to querie a real time database of over 50 million+ rated
websites categorized into 70+ unique content categories.
19 Should support Endpoint Quarantine to quickly disconnect a compromised endpoint from the
network and stop it from infecting other assets.
20 Solution should be able to detect and prevent communication patterns used by Bots like
information about botnet family.
21 Solution should be able to block traffic between infected host and remote C&C operator but at
the same time allow traffic to legitimate destinations.
22 The solution should detect and prevent various exploit techniques providing protection against
memory-based attacks.
23 Solution should monitor behaviour of applications like Web Browsers (IE, Chrome, Firefox,
Opera), Java/Flash plug-ins, Microsoft Office applications, and PDF reader as part of anti-exploit
feature.
24 Endpoint solution should have vulnerability scanning feature to check for known vulnerabilities
in the endpoints.
25 The solution must support creation of exclusions / exceptions from Central Console and pushing
them to the endpoints. It should not require creation of exclusions on individual endpoints.
26 The solution must be provided for at least 100 endpoint licenses including software updates,
upgrades and technical support for 5 years.

6.2.15 Video wall and Video wall Controller

Following are the minimum expected technical specifications for Video wall and Video Wall
controller.

Compliance
Sl. No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Page 103 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Model:

Video Wall cubes of 70"(± 5 %) diagonal in

a 6(C) x 2(R)configuration complete with
1 Configuration
base stand with Unique cooling system
ensures longer LED lifetime

Cube & controller, Software should be from

2 Cube & Controller
the Same OEM

Full HD (1920x 1080) DLP Single chip/DLP

3 Native Resolution
LED Technology or higher or better

LED Lit DLP Rear Projection Technology

4 Technology
without any colour wheel or Laser or better

Compliance
Sl. No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Model:

LED light source with a minimum life time of

1,00,000 hrs. in Normal Mode & Eco Mode;
Individual cube should be equipped with
multiple LED banks and each LED bank
5 Light Source
should have an array of diodes. Single or
multiple diode failure should not impact
image display on the screen or Laser or
better

DLP Rear Projection with single DMD Chip

6 Display Technology Along with Color Gamut of REC 709 or
Better.

Minimum 500 (nits or cd/m2) and should be

adjustable for lower or even higher
7 Brightness on Screen
brightness requirements. This should be
supported by datasheet

8 Brightness Uniformity >95% or better

Should provide auto color adjustment

function and should be sensor based,
automatic calibration system which works
9 with an advanced color sensor. The sensor
continuously measures the primary levels of
Color the entire wall and adjusts white point and
color when needed.

Page 104 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Color and brightness sensor should be in-
built inside the projector only
10
Placing sensors outside the projector and
projector body is not acceptable

11 Screen 180° viewing angle

System must be modular in installation;

12 General Dark box type stacking model is not
acceptable. 1000000:1 or more

Brightness of
13 Typ. 1100 lumens or Better
Projection engine

15 Control IP Based control or better

IP based control should also be provided

16 Remote for quick access and IR remote control
should also be provided for quick access.

Compliance
Sl. No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Model:

Screen to Screen
17 <0.2 to 0.5 mm Gap between 2 screens
Gap

2x Input (DP1.2)
2x Input (HDMI2.0)
Terminal in each
19 2x LAN
Cube
2x USB
1x Output (DP1.2)

100 – 240 VAC, 50-60Hz; Power supply:

Rack Mountable Redundant Hot
21 Power Supply swappable power supply to be provided
in N+1 Redundancy for 24x7 Fail safe
operations.

Any advanced cooling mechanism, Low

noise and high dissipation system. Less
24 Cooling Inside Cube
than 510 BTU / h. This should be supported
by datasheet.

Maintenance Cube should be accessible from the

26
Access rear/front side for maintenance only

Page 105 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Video wall should be equipped with a
cube control & monitoring system. It
27 should provide options to view control
layouts on remote devices such as tab,
laptop, etc through web browsers

Should be able to control & monitor

28 individual cube, multiple cubes and
multiple video walls
Cube control &
Should provide a virtual remote GUI over
29 Monitoring
the IP to control the video wall

Status log file should be downloadable as

30
per user convenience

System should be AI (Artificial Intelligence)

with Advance Pro-active real-time
31 Monitoring and Diagnosis of hardware
over cloud for predictive failure to have
maximum uptime

Sharing & It should be possible to share the layouts

32
Collaboration over LAN/WAN Network with Display in
Compliance
Sl. No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Model:

Meeting room or on Remote Workstations

connected on LAN/WAN Network

Engine should be protected from dust

33 Dust Protection
ingress

34 Internal Temperature
Monitoring of critical
35 parameters to ensure Brightness
stable operation of
the system 24 x 7 Should be possible to demonstrate these
38
parameters through an active monitoring

6.2.15.1 Video Wall Controller

Compliance
No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Page 106 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Model:

Controller to be able to control mentioned

video wall and should be based on the
1 Display controller
latest architecture. Hardware / software
should have 5-year warranty

2 Chassis Type 19" Rack mount industrial chassis

3 Network 2 x 1Gb/s LAN

4 DVI/HDMI Inputs 8 or more

Resolution Support
5 Each o/p should have 4K support
for Outputs

480 GB or Higher, 8GB or Higher, Windows 10

Hard disk, RAM, OS,
6 or higher, R.A.I.D-1 redundant setup with 2x
RAID
480 GB or higher

7 Tampering Alarm Controller cover opening alarm

The system should have the capabilities of

interacting (Monitoring & Control) with
various applications on different network
8 Control
through the single Operator Workstation. It
shall be possible to launch layouts, change
layouts in real time using Tablet.

Complia
No Parameters Minimum Technical Requirements
nce
(Yes
/No)
Make:

Model:

Keyboard and Mouse along with mechanism to

Keyboard & Mouse extend them to 20mtrs. Operator desk from
9
Extension display controller to beprovided

The controller shall be designed for 24 x 7

10 24 x 7 operation
operation

11 Redundancy Redundant controller should be provided

The Video Wall and the Controller should be of the

12 Others same make to ensure better performance and
compatibility

13 Output DP/DVI/HDMI

Page 107 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 H.264, MPEG2/4, MxPEG, MJPEG, V2D, H.263
14 Input
or better

15 Dimensions 19” Rack mount

Operating 100-240V ,10-5A, 50/60Hz, Redundant Power supply

16
Conditions

The operator should be also possible to show

Laptop Or Android/IoS phone over the video wall
17 Wireless
without disturbing the existing network over
wireless

The software should be able to preconfigure

various display layouts and access them at any
18 Software
time with a simple mouse click or schedule/timer
based.

The software should be able display multiple

sources anywhere on video wall in any size Key
features of Video Wall management Software

•Central configuration database

19 Software •Browser based user interface
•Auto-detection of network sources
•Online configuration of sources, displays and
system variables

Video Wall Control Software shall allow commands

20 Software on wall level or cube level or aselection of cubes:
• Switching the entire display wall on or

Compliance
No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Model:

off.
• Setting all projection modules to a
common brightness target, which can be
either static (fixed) or dynamic to always
achieve maximum (or minimum) common
brightness between projection modules.
• Fine-tune colour of each cube

Should support Multiple clients / Consoles to

33 Software
control the Wall layouts

Page 108 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The Software should be able to share
layouts b/w available different videowalls
34 Software
on same network as well as preview of
sources on the workstation

Software should enable the user to display

multiple sources (both local & remote) up to
35 Software
any size and anywhere on the display walls
(both local & remote).

The software should be able to create

36 Software layouts and launch them as and when
desired

The display Wall and sources (both local &

remote) should be controlled from Remote
37 Software
PC through LAN without the use of KVM
Hardware.

38 Software Software should support display of Alarms

The software should provide at least 2 layers

39 Software
of authentication

Software should able to Save and Load

40 Software desktop layouts from Local or remote
machines

All the Layouts can be scheduled as per user

convince.
41 Software Software should support auto launch of
Layouts according to specified time event
by user

It should be possible to create layouts

42 Software comprising of screen scrapped content of
Workstations, DVI inputs, Web sources, URLs

Page 109 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Compliance
No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Model:

configured as sources. Layouts can be pre-

configured or changed in real timeCan
be pre-configured or changed in real time

It should be possible to schedule specific

Layout based on time range It should be
possible to share the layouts over LAN/WAN
43 Software
Network with Display in meeting room or on
Remote Workstations connected on
LAN/WAN Network

System should have a quick monitor area

to access critical functions of the video
wall User should be able to add or delete
critical functions from quick monitor area
Full featured Web services-based API
44 Software
supports Legacy RS-232 and TCP/IP.
All software communication should be
encrypted, Secure user Management with
AD and LDAP Support Zero Maintenance,
automatically saves the user’s work

Integrated Embedded & External Audio

formats with Audio decoding of video
streams also possible. Software also supports
45 Software
UMD, IDC, Source name, Time (time zone
aware), Date, text, Logo, Message Ticker,
Source Status

The system shall include complete Bi-

directional Soft KVM to permit operators to
46 Software take mouse & keyboard control of Displays,
Screen Scrapped applications and DVI
source

It should be possible to create two separate

Tickers which run concurrently. These can
be positioned at top or bottom and can run
47 Software independently. The Ticker can be picked
from data source through screen scrapping
or through typing specific incidence,
manually

Page 110 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
48 Software The system should have the capabilities of
interacting (Monitoring & Control) with
Compliance
No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Model:

various applications on different network

through the single Operator Workstation. It
shall be possible to launch layouts, change
layouts in real time using Tablet

The control of the wall shall be possible via

a network. All cubes shall have their own IP
address, and the control software can
access all of them at the same time. The
available features shall be: On/Off,
Brightness and Colour, Input control.
Separate hardware server for monitoring
49 Software
features Wall or Panel On/Off, Brightness
and Colour, Input control, health
monitoring.

Also, software have feature to show

maximum, minimum and current brightness
/ colour values of all the projectors.

Central setup & Connection management,

Central configuration database, Fully
50 Software distributed & modular component
technology, Browser based UI, Auto-
detection of network sources

Online configuration of sources, backup &

restore, Scheduled backup, Fully features
51 Software
web services based API covering all legacy
and encrypted communications

Save and load layouts (complete display

presents including perspectives and
applications), start stop and position
52 Software applications & sources freely over the
complete desktop, remote keyboard and
mouse control from and towards other
networked desktops (bi-directional)

Page 111 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Supported sources:

Analog & digital / streaming video, Analog

53 Software
(RGB) and Digital (DVI-I) Sources, Network
desktops, Network multi-channel
workstations and applications, Internet &
Compliance
No Parameters Minimum Technical Requirements
(Yes /No)

Make:

Model:

internet sources, Embedded & external

audio formats, Localization

The Display Modules, Display Controller &

54 Modules
Software should be from a single OEM

6.2.16 Lan Networking For ICCC

• The System Integrator shall prepare the sites for commencement of work. Site
preparation in terms of laying LAN cables in the buildings will be the responsibility of theSI. The
SI would need to undertake the provisioning of LAN cabling between end user till the access
switch in each of the respective buildings as per the scope of work.

• SI shall provide and install all cables and connectors necessary, including both copper (Cat 6)
and fiber optic patch cables, to complete the installation. The Authority expects all cables
to be installed in a neat and workmanlike manner and adhere tobest practices for cable
management.

• The SI is required to have structured cabling in place for both LAN and Internet
Connectivity.

• All fiber jumper/patch cables installed must be labeled according to TIA/EIA standards and
must indicate connections at both ends.

• When installing patch cables, the SI shall provide and install “hook and loop” stylewraps
to provide proper support and management of cables. No plastic tie wraps maybe used.
• SI is responsible to provide and install horizontal wire management devices above,below,
and between stacks of devices (only those devices part of this project) at allthe floors and
wiring closets.

• The distance between any I/O point and the corresponding switch should not be morethan 90
meters. The place for installing the racks & network equipment will be theresponsibility of
SI.

• Cat 6 shall be laid for connecting the user systems with the network.

• Fiber cables should be laid between any two uplinks between the NetworkEquipment’s.

Page 112 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• Dedicated raceways / cable-trays should be used for laying LAN.

• Additional cabling requirements on an on-going basis shall also need to be cateredto.

• All the cable raceways shall be adequately grounded / Overheated and fully concealed
with covers.
• The cables should be appropriately marked, numbered and labeled.
• There should be enough space between data and power cabling and there should not be
any cross wiring of the two, to avoid any interference, or corruption of data.

• There shall not be any network outages in the existing network due to laying of new cables.
6.2.17 Centralized Help Desk
• Proposed helpdesk solution must provide flexibility of logging, viewing updating andclosing
incident manually via web interface for issues.

• Helpdesk system should provide incident management, problem management templates

along with helpdesk SLA system for tracking SLA’s pertaining to incidentresolution time for
priority / non- priority incidents.

• Helpdesk should be an ITIL certified tool from certified Authority like Pink Verify forIncident,
Problem, Change, Knowledge, Configuration and SLA Management processes.

• The proposed helpdesk solution must have a built-in workflow engine to define escalations
or tasks to be carried out after issues or change order are logged pertaining to surveillance
project.

• Solution should provide a clustered view of recurring themes hidden in the huge quantities
of data for spotting service desk trends easily

• Helpdesk should have capability to automatically categorize, understand the impact, and
assign the service desk ticket to relevant helpdesk team members

• Centralized Help Desk System should have integration with Network / Server MonitoringSystems
so that the Help Desk Operators can to associate alarms with Service Desktickets

6.2.18 IP Phones
Compliance
# Parameter Minimum Specifications
(Yes / No)

Make:

Model:

2 line or more, Monochrome display for

1 Display
viewing features like messages, directory

10/100 mbps for a direct connection to a

2 Integral switch 10/100BASE-T Ethernet network through an
RJ-45 interface

3 Speaker Phone Yes

Page 113 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Wired, Cushion Padded Dual Ear-Speaker,
Noise
4 Headset Cancelling headset with mouthpiece
microphone, port compatibility with IP
Phone

5 VoIP Protocol SIP V2

IEEE 802.3af or better and AC Power

6 POE Adapter
(Option)

Supported
7 SNMP, DHCP, DNS
Protocols

G.711, G.722, G.729 including handset and

8 Codecs
speakerphone

Full duplex speaker phone with echo

9 Speaker Phone cancellation
Speaker on/off button, microphone mute

Easy decibel level adjustment for speaker

10 Volume control
phone, handset and ringer

Phonebook/Address
11 Minimum 100 contacts
book

Access to missed, received, and placed

12 Call Logs
calls. (Minimum 20 overall)

13 Clock Time and Date on display

14 Ringer Selectable Ringer tone

15 Directory Access LDAP standard directory

16 QoS QoS mechanism through 802.1p/q

6.2.18.1 IP PABX
Compliance
# Minimum Specifications
(Yes / No)

Make:

Model:

The IP telephony system should be a converged

communication System with ability to run analog and IP on the
1.
same platform using same software load based on server and
Gateway architecture

Page 114 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The single IP PBX system should be scalable to support up to
2. 500 stations (any mix/percentage of Analog/IP) to achieve
the future capacity

The system should be based on server gateway architecture

3. with external server running on Linux OS. No card-based
processor systems should be quoted

The voice network architecture and call control functionality

4.
should be based on SIP

The call control system should be fully redundant solution with

5.
no single point of failure & should provide 1:1 redundancy.

The communication server and gateway should support IP V6 in

6.
future

The entire solution (IP PBX, its hardware, IP Phones, Voice

7.
Gateway) should be from a single OEM

8. Support for call-processing and call-control

Should support signaling standards/Protocols – SIP, MGCP,

9.
H.323, Q.Sig

Voice Codec support - G.711, G 719, G.729, G.729ab, g.722,

10.
ILBC, GSM

The System should have GUI support web-based management

11.
console

12. Security

The protection of signaling connections over IP by

13. means of authentication, Integrity and encryption should be
carried out using TLS

14. System should support MLPP feature

Proposed system should support SRTP for media encryption and

15.
signaling encryption by TLS

Secure HTTP support for Call Server Administration,

Serviceability, User Pages, and Call Detail Record Analysis and
16.
Reporting Tool. Should support Secure Sockets Layer (SSL) for
directory

The administrator logging on to the call control server needs

17. to authenticate by suitable mechanism such as User Login
Information and Passwords/ Radius Server

Voice gateway to be provided with 1 PRI card scalable to 3 PRI

18. in future
for PSTN (PRI) line termination.

Page 115 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.2.19 Three Monitoring Workstations:

Sl. Compliance
Parameter Minimum Specifications
No (Yes / No)

Make:

Model:

Intel i7 11th generation/AMD Rayzen Thread ripper or Higher latest

1 Processor
Processor with 3GHz or higher frequency

2 Chipset Latest series 64bit Chipset

3 Cores 6 Cores or Higher

4 RAM Minimum 16 GB DDR4 or latest

Minimum Graphics card with 1 GB or higher video

5 Graphics card
memory (non- shared)

6 HDD 256 GB, PCIe NVMe, SSD and 1TB SATA SSD

7 Media Drive NO CD / DVD Drive

10/100/1000 Mbps autosensing on board integrated RJ-45 Ethernet

8 Network interface
port.

9 Audio Line/Mic IN, Line-out/Spr Out (3.5 mm)

Minimum 6 USB ports (out of that 2 in front), HDMI Port and Mini
10 Ports
DP Port

11 Keyboard 104 keys minimum OEM keyboard

12 Mouse 2 button optical scroll mouse (USB)

1) PTZ speed dome control for IP cameras

PTZ joystick 2) Minimum 10 programmable buttons

controller (with 2 of 3) Multi-camera operations

13
the workstations in 4) Compatible with all the camera models offered in the
ICCC) solution

5) Compatible with VMS /Monitoring software offered

Three Monitors of 22” TFT LED monitor, Minimum 1920 x 1080

resolution, 5 ms or better response time, TCO 05 (or higher)
14 Monitor
certified. The TFT Monitor, CPU, Mouse and keyboard workstation
shall be of same make.

15 Certification Energy star 5.0/BEE star certified.

16 Operating System 64 bit pre-loaded OS Latest windows 11 pro or latest and MSOffice

Page 116 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 BIOS controlled electro-mechanical internal
17 Security
chassis lock for the system.

18 Warranty Hardware /Software should have Minimum 5-year warranty.

Page 117 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6.2.20 Data Center & ICCC: Non-IT Components
ICCC and Data Center in terms of redundancy and concurrent maintainability requirements.
Solution Provider is expected to establish and operationalize ICCC as per the location provided
by PSCDL.

General Standards for interiors and Console

Sl. No Minimum Requirements

1 The ICCC interiors shall be state of the art adhering to the various best practices
norms for integrated control centres, including:

• The scope of the project includes designing; engineering, supply & installation of
24X7 ICCC Interiors. As ICCC is a significant place, it is imperative that it is designed
properly in terms of Aesthetics, Ergonomics and Functionality. Various aspects
should be considered while designing ICCC area to create ideal workplace,
considering physiological aspects such as line of sight and field of vision and
cognitive factors such as concentration and perceptivity.
• Should have ISO 11064, ISO 14001 (environment), OHSAS 18001, HFE and ISO 9241 or similar
certifications
• ICCC is considered to be heart of any Operation. Hence the project get world
class ICCC in line to standard norms. The proposed interior material for ICCC
should be designed properly in terms of Safety, Aesthetics, Ergonomics and
Functionality
• The proposed wall panelling tiles and Ceiling tiles shall be industrial grade for
surface spread of flame and smoke generation. This is mandatory to ensure that
the materials used in the interiors do not provoke fire.
• Safety of User & ICCC: Safety is a high concern area therefore panelling and
Plank ceiling must be standard one to withstand vibrations.
• Standard design feature of integrated channel in ceiling for quick installation &
replace ability of continuous linear light: The ceiling system having
integrated inbuilt channel for installation of cove lights and shall permit quick
and easy replacement of cove light without using any tools.
• The Metal Panelling and Ceiling shall ensure restriction of hazardous
substance so that the final product does not contaminate the environment
and we give a healthy life to our coming generations.
• Sound transmission class (STC) value should be as per site conditions.
• Standard design feature of Load bearing capacity of panelling - panelling
structure shall have sufficient load carrying capacity .

6.2.21 Intranet router at DC:

Sl. Compliance
Technical Specification
No (Yes / No)

Make: <to be provided by the bidder>

Model: <to be provided by the bidder>

Page 118 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The Router Should support minimum 160 Gbps full duplex throughput and should be of max 3
1 RU in height, 19-inch rack mountable. Should have 8x10G SFP+ and 2x40G QSFP based ports
on day one.

2 Router should support Optical Transceiver Digital Diagnostic Monitoring.

3 Router Should support Dual Images.

4 Router should support jumbo frames (9000) on all ports

5 Router should support BFD for single hop and multihop sessions.

6 Router should support MPLS-FRR to ensure high availability.

Router should support OSPFv2, OSPFv3, ISIS, BGPv4, MP-BGP, BGP confederations and route
7
reflector and RSVP-TE Fast Reroute (FRR).

8 Router should support VRRP, VRRPv3.

9 IPv4 and IPv6 enabled from day one

The Router scaling should be minimum:

a. 64K IPv4 FIB routes and 16K IPv6 FIB routes.
b. 32 VRF/L3VPN and 200 L2VPN.
10 c. HQoS and minimum 2K Queues.
d. 1K number of MPLS Labels (Provider Router).
e. 6PE /6VPE, MPLS label-Switching router (LSR & LER) functionality.
f. 4K VLANs.

Shall support following class of service features:

a) Classification, policing, marking, shaping, filtering
b) Manage congestion using a weighted random early detection (WRED) algorithm
11 c) Ingress policing
d) egress shaping
e) strict queuing , WFQ
f) Router should be able to classify based on 802.1 ad, 802.1 p, EXP and DSCP bits

Shall support the OAM feature

12 a) 802.3ah/802.1ag/TWAMP
b) LLDP

IPv6 Features
a) IPv6 Ping
13 b) IPv6 trace route
c) OSPF v3
d) IS-IS

Multicast Feature: It shall support following:

a) It shall support IGMP snooping v2/v3
14
b) The router shall support PIM Sparse Mode, RFC 4601
d) RFC 3569, Source Specific Multicast (SSM)

Routers should support Timing and Synchronization such as Synchronous Ethernet or Precision
15
Time Protocol (PTP)

Page 119 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
16 The router shall support LACP 802.3ad and bundle upto 8 links.

The router should support IP SLA or RPM (or equivalent) for performance measurements, it
17 should also support monitoring of IP SLA/RPM (or equivalent) probes using SNMP polling (OEM
has to provide SNMP MIB information)

The router should support filtering based on different parameters like: src ip, dst ip, src port,
18
dst port, protocol etc

The Router Should support DHCP server and client functionality, it Should support DHCPv6
19
server/relay as well.

20 The Router Should support DHCP based option 82.

21 It shall support role based privileges for the system access and radius authentication.

22 The router should have a Console or Out-of-band Management.

23 Router should support Control-plane and management plane protection

The Router Should support network management based on SNMP v2c/v3, Syslog,
24
RADIUS/TACACS+, Access via CLI.

The Router shall be able to operate at Operating Temperature: 0°C to 40°C and Operating
25
Humidity: 20 - 80% RH non-condensing.

The Router shall support dual redundant AC power supply and AC Power voltage shall be 110 -
26
240V. Should have dual power supply with hot swappable.

27 The Router Should be NEBS Level III or equivalent complied.

The Router operating system of the Routers category/series/family should be MEF-9/14 or CE

28
(Carrier Ethernet) Certified/compliant.

All necessary SFPs, interfaces, connectors, patch cords (if any) & licenses must be delivered
29 along with the Router from day one.

Warranty –Hardware/ Software License should be for 5 years.

6.2.22 Backbone Router

Sl. Compliance
Technical Specification
No (Yes / No)

Make: <to be provided by the bidder>

Model: <to be provided by the bidder>

The Router Should support minimum 80 Gbps full duplex throughput and should be of
1 max 3 RU in height, 19-inch rack mountable. Should have 8x10G SFP+ based ports on
day one.

2 Router should support Optical Transceiver Digital Diagnostic Monitoring.

Page 120 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
3 Router Should support Dual Images.

4 Router should support jumbo frames (9000) on all ports

5 Router should support BFD for single hop and multihop sessions.

6 Router should support MPLS-FRR to ensure high availability.

Router should support OSPFv2, OSPFv3, ISIS, BGPv4, MP-BGP, BGP confederations and
7
route reflector and RSVP-TE Fast Reroute (FRR).

8 Router should support VRRP, VRRPv3.

9 IPv4 and IPv6 enabled from day one

The Router scaling should be minimum:

a. 32K IPv4 FIB routes and 8K IPv6 FIB routes.
b. 32 VRF/L3VPN and 200 L2VPN.
10 c. HQoS and minimum 2K Queues.
d. 1K number of MPLS Labels (Provider Router).
e. 6PE /6VPE, MPLS label-Switching router (LSR & LER) functionality.
f. 4K VLANs.

Shall support following class of service features:

a) Classification, policing, marking, shaping, filtering
b) Manage congestion using a weighted random early detection (WRED) algorithm
11 c) Ingress policing
d) egress shaping
e) strict queuing , WFQ
f) Router should be able to classify based on 802.1 ad, 802.1 p, EXP and DSCP bits

Shall support the OAM feature

12 a) 802.3ah/802.1ag/TWAMP
b) LLDP

IPv6 Features
a) IPv6 Ping
13 b) IPv6 trace route
c) OSPF v3
d) IS-IS

Multicast Feature: It shall support following:

a) It shall support IGMP snooping v2/v3
14
b) The router shall support PIM Sparse Mode, RFC 4601
d) RFC 3569, Source Specific Multicast (SSM)

Routers should support Timing and Synchronization such as Synchronous Ethernet or

15
Precision Time Protocol (PTP)

16 The router shall support LACP 802.3ad and bundle upto 8 links.

The router should support IP SLA or RPM (or equivalent) for performance
17 measurements, it should also support monitoring of IP SLA/RPM (or equivalent) probes
using SNMP polling (OEM has to provide SNMP MIB information)

Page 121 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The router should support filtering based on different parameters like: src ip, dst ip, src
18
port, dst port, protocol etc

The Router Should support DHCP server and client functionality, it Should support
19
DHCPv6 server/relay as well.

20 The Router Should support DHCP based option 82.

21 It shall support role based privileges for the system access and radius authentication.

22 The router should have a Console or Out-of-band Management.

23 Router should support Control-plane and management plane protection

The Router Should support network management based on SNMP v2c/v3, Syslog,
24
RADIUS/TACACS+, Access via CLI.

The Router shall be able to operate at Operating Temperature: 0°C to 60°C and
25
Operating Humidity: 20 - 90% RH non-condensing.

The Router shall support dual redundant AC power supply and AC Power voltage shall
26
be 110 - 240V. Should have dual power supply with hot swappable.

27 The Router Should be NEBS Level III or equivalent complied.

The Router operating system of the Routers category/series/family should be MEF-9/14

28
or CE (Carrier Ethernet) Certified/compliant.

All necessary SFPs, interfaces, connectors, patch cords (if any) & licenses must be
29 delivered along with the Router from day one.

Warranty –Hardware/ Software License should be for 5 years.

Page 122 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Civil and Architectural Work

Sl. No Minimum Specifications Compliance

(Yes / No)
a. Designer Acoustic Metal False ceiling with Plank
b. ICCC ceiling must be 100% modular to accommodate
future technological expansions/retrofitting without
taking any shut-downs and must be easily replaceable
in case of damage.
c. The proposed ceiling tiles shall be as per industrial grade
standards .
d. Standard design feature of integrated channel in ceiling
for quick installation & replace ability of continuous linear
light: The ceiling system having integrated inbuilt
channel for installation of cove lights and shall permit
quick and easy replacement of cove light without using
any tools.
e. The Ceiling system must ensure restriction of hazardous
substance in any of the materials.
f. The Non uniform gaps between the designer Metal
ceiling / Grid type Snap Fit Ceiling shall be covered with
Calcium Silicate Ceiling.
g. Control Desk: The control desk solution shall conform to
high standard of engineering. It shall be capable of
performing 24X7 operations under the all environmental
conditions.
h. Structure: - Made of heavy duty Extruded Vertical and
Horizontal Aluminium profiles. The Extrusions shall be duly
powder coated with 40+ micron over all surfaces. All
sheet metal parts must be finished with a durable, black,
electrostatic powder coating.
i. To allow future extension and expansion, a weld free
system shall be proposed. Interconnecting joints shall not
be visible. The structure shall be rigid enough. The

Page 123 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 structure shall allow easy assembly of Hinged Shutters,
Slat wall, Gland Plate, Monitor arms in extremely rigid
manner.
j. Table-top: - The material of the working surface should
be of industrial grade.
k. Front Edge: - Industrial Standard design feature of
modular Edge. The edge shall be mechanically
replaceable in case of damage or wear without opening
or removing the worktop.
l. Slat Wall shall be made of industrial grade material .
m. Monitor Arm: - Feature of monitor arm assembly shall
have auto lock, push & remove feature for quick release
of VESA mounts and modular arm extensions for ease in
maintenance and fixing of monitor .
n. Shutters & Side Legs: - Front, back shutters shall be
industrial grade material . Side leg shall be of the same
finish.
o. Cable Trays Cable Trays and Wiring: - The desks must be
designed with vertical and horizontal cable trays to
allow for continuous cable management between the
cabinets. Wire shall be routed into the cabinet through
gland plate.

p. Acoustic Metal Panelling: Factory made removable

type self inter lockable metal panels with front sheet of
Preformed Textured Hot dip galvanized sheet with rigid
polyvinylchloride (PVC) film on one side and on the other
side a coating to avoid rust . The panelling design shall
comprise of specially designed combination of
perforated and non-perforated panels through CNC
laser Cutting, bending & punching.
q. Acoustic Metal Partition - The material of construction
shall remain the same however in partition the cladding
shall be done on either side of the section/grid work.
r. Sound transmission class (STC) value as per site
conditions.
s. Standard design feature of Load bearing capacity of
panelling - panelling structure shall have sufficient load
carrying capacity .
t. The Metal Panelling and Ceiling shall ensure restriction of
hazardous substance so that the final product does not
contaminate the environment and we give a healthy life
to our coming generations.
u. Industrial grade feature of Modular wall panelling tile
having secure locking arrangement for equidistant
mounting.
v. Acoustic Laminate Flooring: - Acoustic flooring shall be
decorative type of approved shade, pattern, texture
and design and of industrial grade. Dimensions shall be
as per the final approved design and site requirement.
Flooring shall be laid over concrete floor with laying
compound.

Page 124 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Sl. No Minimum Specifications Compliance
(Yes / No)
w. False Flooring: Mandatory: Top Surface shall be Acoustic
Laminate flooring.
x. The Panel should be as per industrial grade.
y. Painting: To maintain the aesthetic appeal of the ICCC,
painting shall be done only on those walls which are not
visible within & from the ICCC.

Fireproof Enclosure

Sl. No. Minimum Specification

1 Capacity: as per site requirement.

Fire Suppression System

Sl. No Minimum Specification Compliance

(Yes / No)
1 Comply with NFPA 2001 or ISO 14520 standard or better . Hardware
should have 5 year warranty

2 Be efficient, effective and shall not require excessive space and

high pressure for storage.

3 Key components are valves and its accessories, actuators, flexible

discharge and connection hoses, check valves, pressure switch,
and nozzles

Water Leak Detection System

Sl. No Minimum Specification

1 • Should be mechanically strong, resistant to corrosion and abrasion.

• Shall have end circuit to detect open circuit fault.

Raised Floor

Sl. No Minimum Specification Compliance (Yes /

No)

Page 125 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
1 System:
• Access floor system to be installed at finished floor
height as per site conditions.
• The system will provide for suitable pedestal and
under-structure designed to withstand various static
loads and rolling loads subjected to it in an office /
server / DCS / panel / rack area.
The entire Access floor system will provide for adequate
fire resistance, acoustic barrier and air leakage resistance.

Page 126 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
PVC Conduit

Sl. No. Minimum Specification Compliance(Yes/No)

1 • The conduits for all systems shall be high impact rigid
PVC heavy-duty type and shall comply with I.E.E
regulations for standardized conduit.
• 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.
• 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.
• Cables shall not be drawn into conduits until the
conduit system is erected, firmly fixed and cleaned
out. Not more than two right angle bends or the
equivalent shall be permitted between draw and
junction boxes
• Conduit concealed in the ceiling slab shall run parallel
to walls and beams and conduit concealed in the
walls shall run vertical or horizontal.
• The chase in the wall required in the recessed conduit
system shall be neatly made and shall be of angle
dimensions to permit the conduit to be fixed in the
manner desired.

Wiring

Sl. No Minimum Specification Compliance (Yes

/ No)

Page 127 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
1 • 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. They shall be stranded
copper conductors as per industrial grade. Colour code
for wiring shall be followed.
• Looping system of wring shall be used, wires shall not be
jointed. No reduction of strands permitted at
terminations.

Page 128 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Sl. No Minimum Specification Compliance (Yes
/ No)
• Wherever wiring is run through trucking 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 used for sub main, sub circuit wiring
the ferrules shall be provided at both end of each sub
main and sub-circuit.
• 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.
• All power sockets shall be piano type with associate’s
switch of same capacity. Switch and socket shall be
enclosed in a mild steel sheet enclosure with the
operating knob projecting. Entire assembly shall be
suitable for wall mounting with Bakelite be connected
on the live wire and neutrals of each circuit shall be
continuous everywhere having no fuse or switch installed
in the line excepting at the main panels and boards.
Each power plug shall be connected to each separate
and individual circuit unless specified otherwise. The
power wiring shall be kept separate and distinct from
lighting and fan wiring. Switch and socket for light and
power shall be separate units and not combined one.
• Balancing of circuits in three phases installed shall be
arranged before installation is taken up.

Earthing

Sl. No Minimum Specification Compliance(Yes/No)

Page 129 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 1 All electrical components are to be earthen by
connecting two earth tapes from the frame of the
component ring and will be connected via several
Sl. No Minimum Specification Compliance(Yes/No)
earth electrodes. The cable arm will be earthen
through the cable glands. Earthling shall be in
conformity with provision of latest Indian Electricity
rules and as per IS standard. The entire applicable IT
infrastructure in the ICCCs shall be earthed.
• Earthing should be done for the entire power system
and provisioning should be there to earth UPS
systems, Power distribution units, and A.C units etc. so
as to avoid a ground differential. State shall provide
the necessary space required to prepare the
earthing pits.
• All metallic objects on the premises that are likely to
be energized by electric currents should be
effectively grounded.
• The connection to the earth or the electrode system
should have sufficient low resistance in the range of
0 to 10 ohm to ensure prompt operation of respective
protective devices in event of a ground fault, to
provide the required safety from an electric shock to
personnel & protect the equipment from voltage
gradients which are likely to damage the equipment.
• Recommended levels for equipment grounding
conductors with very low impedance level.
• There should be enough space between data and
power cabling and there should not be any cross
wiring of the two, in order to avoid any interference,
or corruption of data.
• The earth connections shall be properly made. A
small copper loop to bridge the top cover of the
transformer and the tank shall be provided to avoid
earth fault current passing through fastened bolts,
when there is a lighting surge, high voltage surge or
failure of bushings.
• A complete copper mesh earthing grid needs to be
installed for the server farm area, every rack need to
be connected to this earthing grid. A separate
earthing pit need to be in place for this copper mesh.
• Provide separate Earthing pits for Servers, UPS &
Generators as per the standards.

Cable Work

Page 130 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Sl. No Minimum Specification

1 • 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
Sl. No Minimum Specification

shall be neatly arranged on the trays in such manner that a criss-crossing is

avoided and final take off to switch gear is easily facilitated.

• All cables will be identified close to their termination point by cable number
as per circuit schedule. Cable numbers will be punched on 2mm thick
standard strips and securely fastened to the. In case of control cables all
covers shall be identified by their wire numbers by means of PVC ferrules. For
trip circuit identification additional red ferrules are to be used only in the
switch gear / control panels, cables shall be supported so as to prevent
appreciable sagging. In general distance between supports shall not be
greater than 600mm for horizontal run and 750mm for vertical run or as per
site conditions.

• 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 criss-cross wiring of the two, in order to avoid
any interference, or corruption of data.

Air-conditioning

Sl. No Minimum Specification Compliance

(Yes / No)
Make:
Model:

Page 131 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
1 • Cooling Capacity as per the requirements at each of the
ICCCs
• Compressor – As per site condition
• Refrigerant – As per site condition
• Power Supply – Three Phase, 380-415 V, 50 Hz
• Air Flow Rate – minimum 19 cu m / min
• Noise Level - < 50 dB
• Operation – Remote Control

Page 132 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Fire Alarm System

Sl. No Minimum Specification Compliance

(Yes / No)

1 • System Description

➢ The Fire alarm system should be installed as per latest NFPA 72

guidelines.
➢ Detection shall be by means of automatic heat and smoke
detectors (multi sensor) located throughout the ICCC (ceiling,
false floor and other appropriate areas where fire can take
place) with break glass units on escape routes and exits.

• Smoke detectors – Smoke detectors shall be of the optical or

ionization type.

➢ Heat detectors
➢ Heat detectors shall be of the fixed temperature (58° C) or rate
of temperature rise type with a fixed temperature operating
point.
➢ Detector bases shall fit onto an industry standard conduit box.

• Audible Alarms – Electronic sounders shall be provided.

Access Control System

Sl. No Minimum Specification Compliance

(Yes / No)

1 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. Access control shall be provided for entry / exit 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:

• Controlled Entries to defined access points.

• Controlled exits from defined access points.

• Controlled entries and exits for visitors.

Page 133 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 • Configurable system for user defined access policy for each
access point.
• Record, report and archive each and every activity
(permission granted and / or rejected) for each access
point.

• User defined reporting and log formats.

• Fail safe operation in case of no-power condition and
abnormal condition such as fire, theft, intrusion, loss of
access control, etc.

• Day, Date, Time and duration based access rights should be

user configurable for each access point and for each user.

• One user can have different policy / access rights for

different access points Hardware / Software should have 5
year warranty.

Ceiling Speakers

Sl. No Minimum Specification Compliance

(Yes / No)

1 • The ceiling speakers shall have high power and high sensitivity
with extended frequency responses.
• The ceiling speakers shall have wide, controlled constant
directivity dispersions for optimum coverage.
• The ceiling speakers shall have in-built amplifiers or shall be
supported by an external amplifier.
• The ceiling speakers shall have a conical coverage pattern.
• The ceiling speakers shall be in a colour to match the ceiling
and surrounding interior design.
• Full audio coverage within the command centre room and
video room should be made.
• The Ceiling Speakers shall automatically adjust the output
audio level based on ambient noise.
• Hardware /Software should have 5-year warranty

Diesel Generator Set 200 KVA Specification: Kirloskar/Cummins/Eicher/Mahindra/Cooper

Sl. No Minimum Specification Compliance

(Yes /No)
Make:
Model:

Page 134 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
1 DIESEL ENGINE SPECIFICATION:
Diesel Engine 6 cylinders, water cooled, turbocharged,
developing suitable BHP @ 1500 RPM, confirming to ISO
3046/ BS:5514, with an overload capacity of 10% for One
hour in any 12 continuous hours operation. DG set shall be
BMS compatible. The bidder shall ensure compliance to
relevant Central Pollution Control Board (CPCB) guidelines as
applicable.
The Engine shall be complete with following accessories
• In-line fuel pump with mechanical governor
• Optimised turbocharger
• Stainless steel exhaust flexible coupling
• Silencer
• Radiator
• Coolant inhibitor
• Plate-type lube oil cooler
• Dry-type, heavy duty, replaceable paper element air
cleaner with restriction indicator
• Flywheel housing and flywheel to suit single bearing
alternator
• Electrical starter motor
• Battery charging alternator
• First fill lube oil
2 ALTERNATOR SPECIFICATIONS:
Stamford make standard design alternator, suitably rated at
200KVA, 0.8P.F., 415 Volts, 3 phases, 4 wires, 50 cycles/sec.,
1500RPM, self-excited & self-regulated, with brushless
excitation, band of voltage regulation 1% of rated voltage,
from no load to full load. Insulation class `H’. The alternator
generally conforms to BS:5000/IS:4722.
• Self-excited, self-regulated
• Class ‘H’ insulation
• Salient pole revolving field
• Single bearing
• Digital automatic voltage regulator (part of PCC 1301)
3 BASE FRAME:
Sturdy, fabricated, welded construction, channel iron base
frame for mounting above Engine & Alternator.
4 FUEL TANK:
400 Litres capacity fuel tank with mounting brackets,
complete with level indicator, fuel inlet & outlet, air vent,
drain plug, inlet arrangement for direct filling & set of 5 ft.
Long fuel hoses.
5 BATTERY:
Set of 2 nos., 12V, Dry Lead acid automotive batteries.

Page 135 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6 MANUAL CONTROL PANEL:
Cubicle Type, floor mounting control panel with hinged
doors, undrilled bottom gland plate, AL. Bus Bar &
accommodating following, Panel shall be BMS compatible.
7 SWITCH GEARS:
• 1250A, 4 Pole Contactor for ALTERNATOR with Thermal O/L
relay
• BACK-UP PROTECTION:
• HRC fuse for short circuit protection.

8 MICROPROCESSOR BASED AMF MODULE INCORPORATING:

Functions:
• Supply Failure Timer
• Restoration Timer
• Impulse automatic engine start / stop logic
• Mains / Generator Voltage & Frequency sensing
Controller with the following features:
Water Temperature/ Lube Oil Pressure / engine speed
Voltage / Ampere / Frequency / kVA o Running-hour
counter
No. of starts
• Fault Indication (LED Type)
Over /Under Speed
Fails to Start
Low Oil pressure
High Engine Temperature
Under / over voltage
Over current
• Combined Meter for kW / Power Factor / KVA
• Electronic kWH Meter (Counter Display)
• Current Transformers
9 Relay:
• Earth Fault Relay (Electronic type)
• Reverse Power Relay
10 Indications (LED):
• DG ON, Load on DG
• Mains ON, Load on Mains, Battery Charger ON
11 Push Buttons (AMF MODULE BY PASS MODE):
• Generator Contactor CLOSE / TRIP
• Mains Contactor CLOSE / TRIP (If Provided)
• Fault ACCEPT / RESET
12 BATTERY CHARGER:
• SMPS Based Unit with inbuilt Auto / Manual & Float /Boost
Facility
• DC Voltmeter & Ammeter (Separate)
• PLHO / 0712/RKS/ASN

Page 136 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Online UPS for indoor (Data Center / ICCC) Location: 60 kVA

Sl. No Minimum Specification Compliance (Yes /

No)
Make:
Model:
1 Capacity / Credentials: Adequate capacity to cover all above IT
Components at respective location. Modular (only for ICCC/DC),
Redundant(N+N), Scalable upto 300kva & with Hot Swappable
type full rated rectifier, inverter & battery charger Power Modules
of capacity more than 60 kVA for Command Centre/Data Centre
UPS with 10" inch Touch LCD. Hot swap type Dual and Redundant
Sl. No Minimum Specification Compliance (Yes /
No)
Make:
Model:
main Controller & Hot swap type with Static Switch. Unitary type
UPS for all other purpose in Indoor requirements.

2 Output Waveform: Pure Sine wave

3 Output Power Factor at Full Load: >0.90 for input & Unity for
Output

4 Input: Three Phase 3 Wire

5 Input Voltage Range: 305-445 VA Cat Full Load, or 3Ph and 175-
280VAC at Full Load for 1Ph, 50Hz+/-3 Hz

6 Output Voltage: 400V AC, Three Phase for over 60 KVA UPS Else
Single Phase 220/230/240 Vac
7 Output Frequency: 50 Hz+/-0.5 % (Free running); +/-3 % (Sync.
Mode)

8 Inverter efficiency: >90%

9 Overall AC-AC Efficiency: >88% for 1Ph & 95% for all 3Ph UPS

10 UPS Shutdown: UPS should shut down with an alarm and indication
on following conditions 1) Output over voltage 2) Output under
voltage 3) Low Battery 4) Inverter over load 5) Over temperature
6) Output short

11 Battery Back-up: Min 2 Hours and as per design consideration

(On 0.8 O/P PF load)

Page 137 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 12 Battery: For ICCC/DC, only Li-Ion batteries to be supplied with
NMC technology. Compliance/Certification to IEC 62619 or
equivalent or Higher, UN38.3. Compact form factor with individual
rack of 600mm(W) x 1090mm(D) x 2000mm(H). 2 Level BMS Design
(Module CMU & Rack BMU). Communication - CAN2.0/RS485

13 Indicators for AC Mains, Load on Battery, Fault, Load Level, Battery

Low Warning, Inverter On, UPS on Bypass, Overload, etc. Metering
for Input Voltage, Output Voltage and frequency, battery
voltage, output current etc. Event log in display – min 200 no’s for
3Ph Unitary UPS & min. 10000 nos for Modular UPS (for ICCC/DC)

14 Not used.

15 Cabinet: Tower (other than DC UPS if required) / Modular type (For

ICCC/DC UPS), SNMP support through TCP/IP

Sl. No Minimum Specification Compliance (Yes /

No)
Make:
Model:
16 Operating Temperature - As per City condition and requirement
(0 to 50 deg without de-rating on offered O/p Power Factor)

17 Management Protocol: SNMP Support through TCP/IP. Warranty

– 5 years

UPS for Outdoor application (2 KVA)

Compliance (Yes /
Sl. No Minimum Specification
No)
Make:
Model:
Capacity: Adequate capacity to cover filed sensors and
1
installations respective location

2 Output Waveform: Pure Sine wave

3 Input & Output Power Factor at Full Load: min. 0.90

4 Input: Single Phase

5 Input Voltage Range:

Single Phase 175 to 280Vac for any rating below 10kva

Page 138 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6 Output Voltage: 400V AC, Three Phase for over 2 KVA UPS. Single
Phase 220/230/240Vac for any rating below 10kva. UPS below
3kva shall have min. one programmable inbuilt Indian type Outlet
at back of UPS

7 Output Frequency: 50 Hz+/-0.5 %( Free running); +/-3 %( Sync.

Mode)

8 Inverter efficiency: >90%

9 Overall AC-AC Efficiency: >89% for 1 Ph upto 3kva. For 5kva or

higher – 95%

10 UPS Shutdown: UPS should shut down with an alarm and

indication on following conditions 1) Output over voltage 2)
Output under voltage 3) Low Battery 4) Inverter over load 5) Over
temperature 6) Output short

11 Battery Back-up: Min 2 Hours and as per design consideration (on

0.8 O/p PF load). All UPS below 5kva shall have min. internal
charger capacity of 15A

12 Battery: VRLA (Valve Regulated Lead Acid), SMF (Sealed

Maintenance Free)

Compliance (Yes /
Sl. No Minimum Specification
No)
Make:
Model:

13 Indicators & Metering(LCD) : Indicators for AC Mains, Load on

Battery, Fault, Load Level, Low Battery Warning, Inverter On,
UPS on By- pass,Overload, etc.

14 Metering for Input Voltage, Output Voltage and frequency,

battery voltage, output current(for any 3PH UPS) etc.

15 Audio Alarm: Battery low, Mains Failure, Over temperature,

Inverter overload, Fault etc.

16 Cabinet: Rack/Tower type. Should have 5 year warranty

6.3 Cloud Services to deploy all smart solutions

It proposed to have all the smart solutions deployed on industry standard Cloud. It isproposed
to host all ICCC applications and smart solution applications on industry standard Cloud. The
proposed Cloud Service Provider (CSP) should be MeiTY empaneled and offer all services from India
only as per guidelines of MeiTY. The solution provider should estimate the required cloud computing
requirements based the proposed solution.

Detailed architecture is mentioned in Sec. 5.3: Finalization of Detailed Technical Architecture

Page 139 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
And following are the minimum technical requirements,

i) Cloud DR Should be at least 500 KM from On-premise Data Centre and

ii) Both On-premise DC and Cloud DR should be in the different seismic zone and
iii) Both On-premise DC and Cloud DR should not be in same River Flood plain and
iv) The proposed Cloud Data center must be TIA 942/Tier III or above for better availability of
cloud services and certified under:

a) Valid and active TIA 942/ Uptime Institute Certification

b) CSP to have ISO-22301 or similar certification for business continuity.
c) The CSP should provide financially backed SLAs for all the services offered.
d) The offered cloud solution of proposed CSP should be as per MeiTY guidelines.

Following are the minimum expected Cloud Services specifications

Compliance
Sl. No Specifications
(Yes / No)

Make:

Model:

The CSP must provide the following services from both DC and DR
1
VM and dedicated physical server based compute services

Multiple options of storage including managed disks, unmanaged

2 disks, block storage, file share and data lake storage in multiple
performance tiers.

3 PaaS/SAAS, IAAS Services to be offered.

Options for container registry and resource template libraries to

4
support faster deployment and best practice implementation.

Managed instances and Database as a service for databases

5
such as Microsoft SQL, MYSQL and PostGre SQL etc

Options for shipping of data from CSP to department if required for

7
backup purposes

Native Firewall, EDR and WAF services both as a native PaaS from
8 the CSP as well as certified third party solutions.

Native Bastion host as a service to ensure secure and resilient

9
access to VMs without opening up public IP addresses.

Page 140 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Native CSP VPN based access to cloud services to ensure no open
10
direct public IP based access to any cloud service under this RFP.

11

Offering for perimeter, host and in-memory security solutions for the
12
compute and storage offerings provided by CSP.

The CSP should provide the below or equivalent services

seamlessly:

• Layer 3 and Layer 4 Firewall

• Layer 7 Firewall (WAF)
13
• SIEM & SOAR ( CSP / CSP marketplace)
• Vulnerability Scanner
• Endpoint Security ( Attack Surface Management)
• Backup Tools
• Disaster Recovery Tools
The CSP should have minimum following features .
14
• Providing the Public Cloud Services (PaaS OR SaaS) in India
CSP should support both BYOL (Bring your own license) and with
a Pay as you go option. The OS offered should come with
15
continuous updates and upgrades anytime.

Monitoring services for cloud resources hosted in the data centre

16
and support for customized report generation.

Blank
17

Blank
18

Blank
19

20 Data Centers should be compliant to MeitY recommended

security guidelines.

21 Blank

The CSP must support dedicated connectivity from at least 3 ISP

22 providers for department/organization to choose between at the
time of deployment.

23 Cloud Native Monitoring & Management & Security Services

Page 141 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Cloud Resource Monitoring: Capability to monitor cloud
environment centrally, custom monitoring metrics, monitor and
store logs, view graphs & statistics, set alarms, monitor and react to
resource changes. Support monitoring of custom metrics
24 generated by your applications and services and any log files your
applications generate. Gain system-wide visibility into resource
utilization, application performance, and operational health, using
these insights to react intelligently and keep applications running
smoothly.

Audit Trail: Logs of all user activity within a CSP account including
actions taken through the CSP's Management Console, CSP's SDKs,
command line tools, and other CSP services. The recorded
25 information includes the identity of the API caller, the time of the
API call, the source IP address of the API caller, the request
parameters, and the response elements returned by the Cloud
service.

Cloud Advisor: Analyses the Cloud environment and provides best

practice recommendations (or checks) in five categories: cost
26
optimization, security, fault tolerance, performance, and service
limits.

Cloud Service Providers must offer Cloud native/ 3rd party SIEM
Marketplace solutions turnkey SIEM offering by which customers
can configure real-time analysis and alerting of security events. At
27
a minimum, the integration or service must support alerting, log
retention and some form of forensic analysis that is able to search
across logs and periods of time for patterns.

Cloud Service Providers should provide Integration with existing

Local identity management system (that is, local accounts) with
granular role-based authorization for network services in both the
service interfaces and management console. At a minimum, the
28 role-based authorization must support assigning authorization
based on individual users and groups of users and delineation must
be assignable per firewall, load balancer, IP address and network
segment and support, as applicable, the following granular
actions: create, delete and configure.

Cloud Service Providers must allow customers to access the cloud

29
service via an IPsec VPN tunnel or Secure Sockets Layer (SSL)
VPN tunnel over the public Internet. This shall be a self service
capability from the provider side, with the capability to make
configurations for customer
Blank
30

Page 142 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 A CSP must provide an option to the customer to encrypt the data
on the instance block storage volume so that data remains
31
encrypted at rest. This shall be a simple, self-service option when the
instance is provisioned.

The block and object storage services must offer customers the
self-service ability from both management console and
32 Command Line Interface to opt into provider-enabled server side
encryption (SSE) for objects or object hierarchies within the storage
service.

Large instance support: Providers must offer customers instances

with a large number of processor cores and memory for processor-
33
or memory intensive use cases. The provider must be able to
provide instances that support at larger vCPUs and RAM.

Cloud provider should offer a dashboard that displays up-to-the

34
minute information on service availability across multiple regions.

Cloud provider should offer Service Health Dashboard history as

35
required

Cloud provider should offer a service that acts like a customized

36 cloud expert and helps provision resources by following best
practices.

Monitoring tools that will enable collection and tracking metrics,

collection and monitoring log files, set alarms, and automatically
react to changes in the provisioned resources. The monitoring tools
37
should be able to monitor resources such as compute and other
resources to gain system-wide visibility into resource utilization,
application performance, and operational health.

Able to define guidelines for provisioning and configuring cloud

resources and then continuously monitor compliance with those
guidelines. Ability to choose from a set of pre-built rules based on
common best practices or custom rules (e.g., ensure Storage
38
volumes are encrypted, Compute instances are properly tagged,
and static IP addresses are attached to instances and continuously
monitor configuration changes to the cloud resources and
provides a dashboard to track compliance status.

Provide Audit Trail of the account activity to enable security

39
analysis, resource change tracking, and compliance auditing

CSP should offer a fully managed service in India that makes it easy
40 to identify potentially fraudulent online activities such as online
payment fraud and the creation of fake accounts.

Page 143 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 CSP should provide in India, a single location to track migration
41 tasks across multiple cloud native tools and partner solutions
certified on the cloud to provide visibility into migration.

CSP should offer a fully managed service in India, that lets

customer to easily create and publish interactive dashboards that
42 include Insights. The dashboards should be accessible from any
device and embedded into city applications, portals, and
websites.

Web Application Firewall (Layer 7): Protection from attacks by

filtering traffic based on rules that you create. Filter web requests
based on IP addresses, HTTP headers, HTTP body, or URI strings,
which allows you to block common attack patterns, such as SQL
43
injection or cross-site scripting that could affect application
availability, compromise security, or consume excessive resources.
Features like protection against Web Traffic visibility, east of
deployment and maintenance, integrated security.

DDoS Protection: Managed DDoS protection service that defends

against most common, frequently occurring network and transport
layer DDoS attacks that target web site or applications. When used
with Content Delivery Network and global DNS service, should
44
provide comprehensive availability protection against all known
infrastructure (Layer 3, 4 and 7) attacks. Should provide always-on
detection and automatic inline mitigations, minimize application
downtime and latency.

Identity and Access Management: Service that properly separates

users by their identified roles and responsibilities, thereby
45
establishing least privilege and ensuring that users have only the
permissions necessary to perform their assigned tasks.

Managed Threat Detection Service: Continuously monitor for

malicious or unauthorized behavior to help you protect your
46 accounts and workloads. It should monitor for activity such as
unusual API calls or potentially unauthorized deployments that
indicate a possible account compromise.

The service should also detect potentially compromised instances

47
or reconnaissance by attackers.

Appropriately configure the security groups in accordance with

48
the Clients’s networking policies.

Regularly review the security group configuration and instance

49
assignment in order to maintain a secure baseline.

Secure and appropriately segregate / isolate data

50
traffic/application by functionality using DMZs, subnets etc

Page 144 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Ensure that the cloud infrastructure and all systems hosted on it,
respectively, are properly monitored for unauthorized activity and
51
follow the security advisories (Advisory No. 22 and any other)
guidelines provided by MoHUA

Properly implementing anti-malware and host-based intrusion

detection systems on their instances, as well as any required
52
network-based intrusion detection systems in accordance with the
Client’s Security policies.

Review the audit logs to identify any unauthorized access to the

53
Client’s systems.

Virtual Machines offered should be compatible with applications

54
and meet the SLAs.

55 Physical core to vCPU ratio should meet the SLA requirement.

Ability to automatically increase/scale the number of

56 Instances/VMs during demand spikes to maintain performance if
required (i.e. ‘scale-out’).

Cloud service architecture should be in such a way that avoids VM

57 outages or downtime when the provider is performing any kind of
hardware or service maintenance at the host level

MSP should have capability to provide dedicated hosts in its native

58 Cloud Infrastructure in India, which allows usage of existing third-
party software license

59 CSP Should meet monthly uptime as per SLA.

Cloud provider should offer the following instance types –

• Optimized for generic applications and provides a balance

60 of compute, memory, and network resources.
• Optimized for memory intensive applications.
• Optimized for compute intensive applications.
• Graphics intensive GPU compute applications
Cloud provider should offer instances that provide a baseline level
61
of CPU performance with the ability to burst above the baseline.

Cloud provider should offer instances that run on hardware

62
dedicated to a single customer.

Cloud provider should offer instances that can run nested virtual
63
machines, that is virtual machine inside a virtual machine.

Cloud provider should be able to support OS as per solution

64
requirement.

Page 145 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Customer must be able to specify and modify server configuration
66
(CPU, memory, storage) parameters seamlessly.

Cloud service should support local storage for compute instances

67 to be used for temporary storage of information that changes
frequently.

Cloud service must offer self-service provisioning of multiple

68 instances concurrently either through a programmatic interface
(API/CLI) or through a management console.

Cloud capability: should be able to logically group instances

69 together for applications that require low network latency and/or
high network throughput.

Cloud capability: should be able to split and host instances across

70 different physical data centers to ensure that a single physical
failure event does not take all instances offline.

Cloud capability: should be able to import their existing image and

72 save it as a new, privately available image that can then be used
to provision instances in the future.

Cloud service must support the ability to take an existing running

73 instance or a copy of an instance and export the instance into a
VMDK or VHD image format as per user requirement

Cloud service must be architected in such a way to automatically

75
restart instances on a healthy host if the original physical host fails.

Cloud provider must be able to schedule events for customer’s

instances, such as a reboot, stop/start, or retirement. Depending
76
on the event, customer might be able to take action to control the
timing of the event.

Cloud service should support containers, including Docker and/or

77
other containerization platforms.

Cloud provider should offer a highly scalable, high performance

78
container management service.

Cloud service should be able to run customer code in response to

79
events and automatically manage the compute resources.

Cloud provider should offer VMs with up to large storage (TB) size
81
or as required.

Support complete eradication of data such that it is no longer

86
readable or accessible by unauthorized users and/or third parties.

Page 146 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Offer object storage tiering capability, i.e. the ability to
88 recommend transitioning an object between object storage
classes based on its frequency of access.

Block Storage

• Cloud provider should offer persistent block level storage

volumes for use with compute instances.
• Cloud provider should offer higher block storage volumes as
required
• Cloud service should support solid state drive (SSD) backed
storage media that offer millisecond latencies.
• Cloud service should support the needs of I/O-intensive
workloads, particularly database workloads that are
sensitive to storage performance and consistency in
random access I/O throughput.
• Cloud service should support encryption of data on
volumes, disk I/O, and snapshots using industry standard
AES-256 cryptographic algorithm.
• Cloud service should support encryption using customer
89
managed keys.
• Cloud service should support point-in-time snapshots. These
snapshots should be incremental in nature.
• Cloud Service should support sharing of snapshots across
regions making it easier to leverage multiple regions for
geographical expansion, data center migration, and
disaster recovery.
• Cloud service should support adding more than one
compute instance to a single storage volume in R/W mode
so that many users can access and share a common data
source.
• Cloud service should support a baseline IOPS/GB and
maintain it consistently at scale
• Cloud service should be durable and support annual failure
rates of less than 0.01% or as required by SLA, and the
information must be disclosed.

Page 147 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Object Storage

• Cloud provider should offer secure, durable, highly scalable

object storage for storing and retrieving any amount of data
from the web.
• Cloud provider should support an extremely low-cost
storage for archival. The CSP should automatically tier the
data.
• Cloud service should support encryption for data at rest
using 256-bit Advanced Encryption Standard (AES-256)
encryption to encrypt your data.
• Cloud service should support encryption using customer
provided keys. These keys should be used to manage both
the encryption, as data is written to disks, and decryption,
when data is accessed.
• Cloud service should support encryption using a Key
• Management Service that creates encryption keys, defines
the policies that control how keys can be used, and audits
key usage to prove they are being used correctly.
• Cloud Service should support managing an object's
lifecycle by using a lifecycle configuration, which defines
how objects are managed during their lifetime, from
creation/initial storage to deletion.
• Cloud service should be able to send notifications when
90 certain events happen at the object level
(addition/deletion).
• Cloud service should be able to host a website that uses
client side technologies (such as HTML, CSS, and JavaScript)
and does not require server-side technologies (such as PHP
and ASP.NET).
• Cloud Service should support versioning, where multiple
versions of an object can be kept in one location. Versioning
protects against unintended overwrites and deletions.
• Cloud service should support flexible access-control policies
to manage permissions for objects.
• Cloud service should be able to provide audit logs on
storage location including details about a single access
request, such as the requester, location name, request time,
request action, response status, and error code.
• CSP should offer a mechanism to avoid accidental deletion
of data. In such case data when deleted should be
preserved for a minimum of 3 months or as required.
• Cloud service should support a lower cost option for
noncritical, reproducible data at lower levels of
redundancy.
• Cloud service should allow uploading a single object as a
set of parts where each part is a contiguous portion of the
object's data and these object parts can be uploaded
Page 148 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 independently and in any order.

• Cloud provider should offer service to speed up distribution

of static and dynamic web content.
• Cloud service should support read-after-write consistency
for PUT operations for new objects.
• Cloud provider should offer a solution for seamlessly storing
on premises data to the cloud, primarily for Video
Management Systems data storage in cloud for longer
durations.
• Cloud provider should support moving large amounts of
data into the cloud by bypassing the internet.
• Cloud provider should support replicating data to DR site
and should provide read-only access to the replicated
data.
File Storage

• Cloud provider should offer a simple scalable file storage

service to use with compute instances in the cloud.
• Cloud service should offer SSD backed storage media to
provide the throughput, IOPS, and low latency needed for
a broad range of workloads.
• Cloud service should support petabyte-scale file systems
and allow thousands of concurrent NFS connections.
• Cloud service should support consistent low latency
performance and should support scalable IOPS and
91
throughput performance.
• Cloud service should support thousands of instances so that
many users can access and share a common data source.
• Cloud service should automatically scale up or down as files
are added or removed without disrupting applications.
• Cloud service should be highly durable - file system object
(i.e. directory, file, and link) should be redundantly stored
across multiple data centers.
• Cloud service should support read after write consistency
(each read and write operation is guaranteed to return the
most recent version of the data).

Page 149 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.4 Intelligent Traffic Management System

Towns and cities are facing traffic-related challenges, from improving safety, to addressing mobility-
related emissions and reversing levels of congestion. Congestion is one of the most prevalent
transport challenges in large urban agglomerations. Pollution, including noise generated by
circulation, has become an impediment to the quality of life and even the health of urban
populations. Further, energy consumption by urban transportation hasdramatically increased,
and so the dependency on petroleum.

6.4.1 Key Issues

The main challenges of Traffic Management in urban ecosystem are as follows:

• Traffic congestion and parking difficulties.

• Longer commuting
• Public transport inadequacy
• Difficulties for non-motorized transport
• Loss of public space
• High infrastructure maintenance costs
• Environmental impacts and energy consumption.
• Accidents and safety
6.4.2 Indicative Key Outcomes and KPIs
The KPI and outcomes can be achieved bringing in multiple domain data integration withICCC
along with ITMS data.

i. Reduction in stoppage time

ii. Optimized cycle times of intersection to regulate and maintain free flow of traffic toenhance
the efficiency of the road and transport infrastructure.
iii. Extent of signal synchronization
iv. Increased Travel Speed
v. Improve Traffic Services: The traffic services to the public can be improved through the
user-friendly presentation of the various traffic information in real time.
vi. Higher Productivity: Achieving improvement in the productivity, logistics and othereconomic
activities by obtaining the precise-real time information on transport dueto the availability of
data on traffic flow in key areas of the city.
vii. Real Time Information and Response: The real time information at the control room shall
enable the operator to take necessary actions based on the real time information, arranging
alternate route to VIP convoys, diverting the traffic to different routes etc.
viii. Improved and accurate Traffic violation detection for the following traffic rules
violations:
ix. Red Light Violation Detection
x. Speed Violation Detection
xi. Free Left Blocking Violation Detection
xii. No Helmet Detection
xiii. Triple Ride Detection
xiv. No Seatbelt Detection
xv. Driver Talking on Phone while Driving
xvi. Improved Traffic Related Emergency Notification and Personal Security
xvii. % emergency vehicle dispatches facilitated by ICCC or Dial 100 or Dial 108
xviii. % urban intersections providing safety enhancements for pedestrians and disabled or other
vulnerable road users
xix. Traffic-related fatality per lakh population (livability index)
xx. Change in number of all reported accidents per vehicle km
xxi. Change in severity of accidents (i.e., numbers killed or serious injured) per number of
accidents reported
Page 150 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
xxii. Change in crime reports relating to illegal parking
xxiii. Improve Environmental Impacts
xxiv.Change in CO2 emissions per vehicle km
xxv. Percentage of interchanges with bicycle parking facilities
xxvi.Change in number of hours where NOx levels are above threshold
xxvii. Change in PM10 emissions per vehicle km
xxviii. Change in number of hours where transport noise is above dB threshold
xxix. Add any other innovative use cases as proposed/ modify of the above features asper
requirements.

6.4.3 Key components

Automatic Number Plate Recognition (ANPR)

a) Red Light Violation Detection (RLVD)

b) Speed Violation Detection (SVD)

c) Vehicle Detector

d) Adaptive Traffic Control System (ATCS)

e) Traffic Analytics

f) e-Challan

g) Video Management & Operator Functions

6.4.4 Automatic Number Plate Recognition (ANPR)

a) The System should automatically detect a vehicle in the camera view using video
detection and activate license plate recognition.

b) The System should automatically detect the license plate in the captured video feed inreal-
time and the system should perform Optical Character Recognition (OCR) of the license
plate characters.

c) System should be able to detect and recognize the English alpha numeric license plate in
standard fonts and formats for classes of vehicles such as cars, Heavy Commercial
Vehicles, Three Wheelers and Two Wheelers. The system should be innovative to detect
English Alphanumeric license plate in non-standard fonts and formats too.

d) The system should capture standard vehicle’s number plates with an accuracy of at
least 90% at day time and at least with an accuracy of 70% at night time.

e) The System should store JPEG image of vehicle and license plate and enter the license
plate number into the database along with the date, time stamp and site location
details.

Page 151 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
f) The system should detect the color of all the vehicles on best effort basis, in the cameraview
during daytime and label them as per the predefined list of configured system colours.
The system should store the color information of each vehicle along with the license plate
information for each transaction in the database.

g) The system should identify the category of the vehicle such as cars, Heavy Commercial
Vehicles, Three Wheelers and Two Wheelers and should store this information along with the
license plate information for each transaction in the database.

h) The system should have an option to store certain license plates of vehicles which arestolen
or suspicious. The system should have the functionality to enter such license plate numbers to
lists such as “Wanted”, “Suspicious”, “Stolen” termed as hot lists of vehicles. The system should
allow the user to import the vehicle license plate data in the hot lists storedin Excel sheets for
batch operation.

i) The system should generate an automatic alert in the ICCC, when it detects the vehicle from
the hot list/s through the ANPR camera. The system should give an instant alert in suchcase. The
system should also have the functionality to send the alert via email and SMS todesignated
email addresses and mobile phone numbers.

j) The system should allow the operator to change the hot list category of the vehicle and
accordingly the new hot list category should be reflected in the records stored in the
database. E.g., on retrieval of stolen vehicle, system entry should be changed from "Stolen"to
"Retrieved”.

k) The system should be able to store license plates numbers of at least suspected vehicles at a
time and should generate an Alert if any one of the vehicles is found crossing the stop line
(irrespective whether the signal is GREEN or RED) in form of Video popup at the Monitor and/or
SMS on Cell phones.

l) The system should have the functionality to trace the movement of a vehicle of interest onGIS
Map. The Function should show the trajectory of the vehicle drawn on the map. The vehicle
of interest should be tracked for all the junctions where it is detected through ANPR.

m) The system should give an option to the operator to edit the license plate number of the
vehicle. The system should show the license plate of the vehicle in a zoomed window foreasy
inspection of the license plate number. The system should keep audit trail of anylicense
plate number edited by the operator.

n) The system should have function of quickly searching the number plate based on the
following criteria:

i. full or partial number of the license plate,

ii. color of the vehicle,
iii. classification of vehicle,

Page 152 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 iv. junction Name,
v. Event Type (e.g., ANPR, Red light Violation, Speed Violation, etc.)

o) The ANPR system should improve the number plate detection for up to 90 percent for
four-wheeler vehicles with standard and non-standard number plates during the night
time (with proper illumination / provision of IR light).
p) The system should detect the vehicles with no license plate and should raise an alert along
with the video and snapshots of the vehicle.
q) The system should allow the operator to set traffic rule such as “no heavy vehicles during
certain time of the day” for selected traffic junctions and display in VMD. The system should
identify the heavy vehicles and generate an alert in case the vehicle is violating the rule
within the configured time.

6.4.5 Red Light Violation Detection (RLVD)

I. The system should capture the License Plate of the vehicles violating the red light or stop line
when the signal is Red.
II. The system should have provisions to either detect red light status by taking the signal feedfrom
the traffic signal controller or by video analytics by recording the evidence snap showing
the violating vehicle and the traffic signal status.
III. The system should have an in-built tool to facilitate the operator to compose detailed
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.

IV. The system should have the functionality export the violation evidence with water markand
encryption as per the techno-legal requirements.
V. The system should synchronize the evidence camera, license plate recognition cameraand
store the record in database with License plate image, image of the vehicle, and atleast five
snaps showing clearly that the vehicle is crossing the red light / stop line while thesignal is RED.
This event should be corroborated with the video clip archived in the VMSsystem at the ICCC.
It should be possible to intimate the incidence in real time through SMS to the designated
mobile phone.
VI. The system should allow mapping of multiple ANPR cameras to a single evidence camera
associated with the traffic junction.
VII. The system should allow capturing multiple evidence snaps based on the time duration
before, during and after the event.
VIII. The system should allow restricting an operator to a single or multiple traffic junction/s and
associated cameras.
IX. The system should have function to forward the generated alerts to designated email and
mobile phone number.
X. The System should also record the video of all the cameras/selected cameras using a
predefined and user configurable schedule. The recorded video can be searched usingthe
following filters:
a) Appearance of a particular license plate.
b) When the signal is RED

Page 153 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
c) When the signal is GREEN
d) During any given date-time span

XI. The system should generate alert when the signal light doesn’t change for the pre-
configured duration. The system should allow the user to set minimum and maximum timefor
the signal light status change.

6.4.6 Speed Violation Detection (SVD)

i. The system should be video based speed violation detection system to be used for
speed detection.

The offered system should be able to detect vehicle license plates along with speed
violation detection for vehicles having speed in excess of 5KMPH or as defined by the local
authorities (with suitable camera with required frame rate) with an accuracy of at least
±2KMPH as compared to conventional speed laser gun system. The system should
generate an automatic alert in case of a speed violation.

ii. The system should have the capability to classify the vehicle under categories such
as car, three wheelers, two wheelers, heavy vehicle, etc.
iii. The system should allow the operator to set different speed limits for different
categories of vehicles.
iv. The event window should show the video associated with the event. The window should
also show at least five snapshots associated with the event.
v. The system should allow the operator to flag the event for storing the event perennially.

6.4.7 Traffic Analytics

i. The system should have the proven technology-based video analytics for intelligent
traffic management applications such as:

a) No Helmet Detection System

b) Triple Ride and No Helmet Detection System
c) Free Left Blocking Detection
d) Object classification for detection of stray animals on the road

ii. The system should work on centralized or decentralized architecture.

iii. In case of any failure in any LPUs, the SI must ensure design and implementation for no
data loss and functionalities of video analytics processing of failed LPU at ICCC.

6.4.7.1 No Helmet Detection

i. System should have the capability to capture image of two-wheeler rider not wearing a
helmet and should have automatic number plate recognition (ANPR) of the violating vehicle
with auto-localization and OCR conversion. The system should have the capability to detect
the ‘no helmet’ instance for the rider and pillion.
ii. The system should collectively identify and detect the motor bike, the rider and the pillion (if
applicable), helmet for the rider and the pillion and the number plate. The system shouldbe able

Page 154 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 to differentiate between a helmet and various other conditions such as the baldhead, person
covering the head with a cap or dupatta or pagree, or any other headgear.
iii. The system should be able to differentiate a person sitting on a motor bike and a
pedestrian in the close proximity of the motor bike.
iv. The system should be able to detect the speed of the motor bike.
v. On detection of No-Helmet, the system should generate events, store them and should
allow retrieval of such events on need basis for later analysis.
vi. The system should be able to search and show the report of the No Helmet violations
based on the day, time of the day, license plate number (partial or full), location nameetc.
vii. System should have capability to identify and eliminate non-standard crash helmets like
industrial safety helmets, sports helmets (cricket, cycling, etc) and mark them as invalid.
viii. System should integrate with challan generation software and RTO database to generate
challans for No-Helmet violation event with details like violation image, time stamp, date,
vehicle number.
ix. No- Helmet detection system should seamlessly integrate with traffic management
systems like ANPR, RLVD, Speed Detection and should have unified user interface.

Page 155 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.4.7.2 Triple Ride Detection

i. The system should have the capability to detect the persons riding triple seat on the motor
bike. The system should capture the number plate of the motor bike with ANPR and
generate an alert with the evidence video.
ii. The system should be able to detect the No Helmet violation for persons riding in triple
ride.

6.4.7.3 Free Left Blocking Violation Detection

i. The system should detect the vehicle blocking the free left traffic wherever it is allowed.
ii. The system should capture the number plate of the vehicle blocking the free left traffic
from the front side.
iii. The system should generate an automatic alert with the details of the vehicle blocking
the traffic.

Object classification for detection of stray animals on the road

i. The system should detect the animal blocking the traffic.

ii. The system should generate an automatic alert with the details (image, location etc..) of
the animal blocking the traffic.

6.4.8 Adaptive Traffic Control System (ATCS)

• The ATCS should address typical Indian driving and traffic conditions such as poor lane
discipline and high heterogeneity. The traffic signal controller should be ready for
integrating with Vehicle priority system (Red light enforcement system, and other similar
applications). The software and hardware supplied should comply with applicable
standards for interoperability and data sharing between different applications.
• Objective of the ATCS would be to minimize the stops and delays in a road network to
decrease the travel time with the help of state-of-the-art technology.
• The adaptive traffic control system shall operate in real time with the capacity to calculate
the optimal cycle times, effective green time ratios, and change intervals for all system
traffic signal controllers connected to it.
• Identify the critical junction of a corridor or a region based on maximum traffic demand
and saturation.
• The critical junction cycle time shall be used as the group cycle time i.e., cycle time
common to all intersection in that corridor or region.
• Stage optimization to the best level of service shall be carried out based on the traffic
demand.
• Cycle optimization shall be carried out by increasing or decreasing the common corridor
cycle time based on the traffic demand within the constraints of Minimum and Maximum
designed value of cycle time.
• Offset correction shall be carried out to minimize number of stops and delays along the
corridor for the priority route. Offset deviation measured using distance and speed
between successive intersections shall be corrected within 5 cycles at a tolerance of +/- 5
seconds maximum.
• The system shall have provision to configure priority for upstream signals as default. The
ATCS software shall continuously check the traffic demand for upstream and downstream

Page 156 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 traffic and automatically suggest the priority route to the higher demand direction.
• Develop appropriate stage timing plans for each approach of every intersection under
the ATCS, based on real time demand
• Propose timing plans to every intersection under the ATCS in every Cycle
• Verify the effectiveness of the proposed timing plans in every cycle
• Identify Priority routes
• Synchronize traffic in the Priority routes
• Manage and maintain communication with traffic signal controllers under ATCS
• Maintain database for time plan execution and system performance
• Maintain error logs and system logs
• Generate Reports on request
• Graphically present signal plan execution and traffic flow at the intersection on desktop
• Graphically present time-space diagram for selected corridors on desktop
• Graphically present network status on Desktop
• Make available the network status and report viewing on Web
• The ATCS shall generate standard and custom reports for planning and analysis. Report
formats to be finalized during design stage.
• Shall provide a decision support tool for assessing strategies to minimize congestion, delays
and emergency response time to events with real time traffic data fusion and control of
traffic signaling infrastructure on ground.
• Shall calculate customizable Key Performance Indicators (KPI) to quickly assess the results
• Shall generate alerts to the operator that trigger on customizable conditions in the
network
• Shall distribute both collected and calculated traffic information via a variety of
communication protocols and channels, ensuring high interoperability degree and thus
acting as a “traffic data and information hub”.

• Shall create a traffic data warehouse for all historic traffic information gathered from the
hardware installed on the road network.
• Shall operate in real time that is continuously updating the estimates on the state of the
network on the basis of data collected continuously over time.
• Shall operate the traffic lights with the adaptive traffic controls, based on the current and
forecasted traffic demand and the current incidents, thus optimizing the green waves
continuously throughout the network
• Enable a smart public transport priority respecting the delays for all road users at once
with the adaptive signal controller
• Junctions with similar traffic patterns can be grouped flexibly into sections or sub- areas.
The system shall allow group of compatible junctions to be linked and operated in a
coordinated manner to optimize traffic operations in a real time basis. It shall be possible
for the operator to lock junctions, sub-areas together causing them to operate on a
common cycle length if desired
• Pedestrian zone scheme: The system shall allow individual signal groups to be switched on
or off according to time of the day as required to facilitate for special pedestrian zone
operation. Should be capable of pre-programmed in site configuration data being
activated or de-activated by time scheduling. Should be capable of being activated by
central system or at controller connected to the system
• Traffic adaptive control: The system shall be capable of utilizing inputs from the detectors
to dynamically implement the most suitable cycle time, splits and offset to optimize traffic
operations on the junction network on a real-time basis. The system shall be equipped with
flexibility to handle partial or total failure of detectors in an appropriate and logical

Page 157 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 manner.
• A controller drop procedure shall be provided to safely transfer a controller from the
central computer-controlled state to local control. The drop procedure shall allow for the
drop of controller either in the total network, a section or an individual controller, as desired
by the operator, both manually and through the activity scheduler. The drop could be
planned or emergency situation.
• Traffic adaptive system should have green wave route pre-emption capability.. Route pre-
emption can be applied to a single junction or a series of junctions to allow emergency
(fire/ambulance/VVIP) vehicles. The software shall be capable to simultaneous operation
of two or more route pre-emption plans
• Communications Monitoring – The System shall monitor the status of the communication
continuously and shall provide for the “recording” of all pertinent data for any specified
controller into a disk file. The recorded data shall include the current time, second by
second current operating information (e.g., timing plan data, etc.), and the current
communications messages being transmitted and received between the control
computer and the field control equipment. Once there is any lack of communication from
any one of the local controllers, an alarm shall be raised to indicate that the controller is
off-line or there is a communication alarm. An appropriate message shall be recorded in
the System alarm and event log and fault databases
• System shall deliverable measurable performance for the important use-case for
Adaptive traffic control system for the benefit of the end user.
• The system should be able to handle emergency priority routing on a consistent basis.
• Adaptive Traffic Control System shall offer traffic signal optimizing functionalities, use data
from vehicle detectors and optimize traffic signal settings resulting improved vehicle delays
and stops. The system shall also allow interconnecting individual area controllers and thus
enabling traffic monitoring and regulating functionality from the central location. This shall
allow each intersection controller to be monitored from central control for proper
functionality. Any corrective action can be initiated either automatically based on status
information or by an operator. The real time detection data shall be communicated to the
ICCC by each controller.
• ATCS shall be driven central control system, on real time basis, with the capacity to
calculate the optimal cycle times, effective green time ratios, and change intervals for all
system traffic signal controllers connected to it which in turn can also work in configurable
manner
• The system after update, creating or expanding database, including the addition of new
junctions or deleting of existing junction should not require system reboot

6.4.9 Reports

System shall generate Corridor based and Intersection based reports. The application software
shall generate the following reports, but not limited to the below. All the reports shall be
possible for selected dates.

• Intersection based reports

• Stage Timing report – The report shall give details of time at which every stage change has
taken place. The report shall show the stage sequence, stage timings and stage saturation
of all stages of all cycles for a day.
• Cycle Timing report – The report shall give details of time at which every cycle has taken
place. The report shall show the cycle sequence and cycle timings for all the cycles in a
Page 158 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 day.
• Stage switching report – The report shall give details of time at which a stage switching has
taken
place. The report shall show the stage sequence, stage timings and stage saturation for a
day.
• Cycle Time switching report – The report shall give details of time at which a cycle switchinghas
taken place. The report shall show the cycle sequence and cycle timings for the cyclein a
day.
• Mode switching report – The report shall give details of the mode switching taken place on
a day.
• Event Report - The report shall show events generated by the controller with date and
time of event.
• Power on & down: The report shall show time when the master is switched on, and last
working time of the master controller.
• Intensity Change – The report shall show the brightness of the signal lamp is changed
according to the light intensity either manually through keypad or automatically by LDR
with time stamp.
• Plan Change – The report shall show the time of change of plan either through remotely
through a PC or Server.
• Time Update – The report shall show the time when the Master controller updated its time
either manually or through remote server.
• Mode Change – The report shall show the time when Master controller’s operating modeis
changed either manually or a remote server. The typical modes are FIXED, FULL VA SPLIT,FULL
VA CYCLE, FLASH, LAMP OFF and HURRY CALL.
• Lamp Status Report – The report shall show lamp failure report with date and time of
failure, color of the lamp and associated phase
• Loop Failure Report –The report shall show the date and time of detector failure with
detector number and associated phase.
• Corridor Performance Report – The report shall show the saturation of all the intersections in
a corridor for every cycle executed for the corridor and the average corridor saturation for a
day

• Corridor Cycle Time Report – The report shall show the Corridor cycle time, Intersection
cycle time, Mode of operation and degree of saturation of all the intersections in a corridorfor
every cycle for a day

6.4.10 Graphical User Interface

The application software shall have the following Graphical User Interface (GUI) for user
friendliness

• Network Status Display – This online display shall indicate with appropriate color coding on
site map whether an intersection under the ATCS is online or off. On double clicking the
intersection a link shall be activated for the traffic flow display for the intersection.
• Traffic Flow Display – This online display shall indicate the current traffic flow with
animated arrows, mode of operation, stage number being executed and elapsed
stage time.
• Saturation Snapshot – This display shall show the current saturation levels of all
intersections in a corridor.

Page 159 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• Reports Printing/ Viewing – This link shall allow selection, viewing and printing of
different reports available under ATCS
• Time-Space Diagram – The time-space diagram shall display the current stages being
executed at every intersection in a corridor with immediate previous history.
• Junctions shall be plotted proportional to their distance on Y-axis and time elapsedfor
the stage in seconds on X-axis.
• Junction names shall be identified with each plot.
• Currently running stage and completed stages shall be identified with different
colors.
• Stages identified for synchronization shall be shown in a different color.
• Speed lines shall be plotter for stages identified for synchronization to the nearest
intersection in both directions.
• The system shall have other graphical interfaces for configuring the ATCS, as
appropriate.

6.4.11 Video Management & Operator Functions

• The system should have built-in Video Management features for continuous recording of
the traffic cameras. The system should have the following functionality:
• Continuous recording of every lane video irrespective of presence of vehicle.
• Such recording schedules can be continuous, event based, schedule based, trigger
based etc.
• Archive Search using dates, time, event etc.
a) High Availability/Redundancy of Recording & Database
• The system should have operator clients for all ITMS related functions including video
management functions and configuration of the system.
• The system should allow the operator to create continuous recording schedule for the
camera based on the time of day and day of week. It should be possible to set the camera
recording schedule for a single camera or a group of cameras or all cameras.
• The system should have the functionality to restrict the user to login from a specific
workstation.
• The system should be able to show Live video in multiple matrix layout for all the cameras
in the system in real time. At least 1x1, 2x2, 3x3, 1+5, 1+7 views must be supported. The
system should have the function to enable multiple matrix layouts to appear on the screen
with configurable on-screen duration for each matrix layout.
• The system should allow configuring cameras in multiple groups independently. It should
be possible to assign all, single or multiple groups to operators. At least 100 such groups
should be possible with unlimited number of cameras in each group. It should be possible
to assign camera/s to single or multiple groups simultaneously.
• It should be possible to drag and drop cameras from the camera directory to the display
screen.
• The system should allow creation of customised, layered maps using standard picture files
and it should be possible to drag and drop the cameras on the map for easy navigation
based on the location on the map. It should be possible to select any camera or group of
cameras on the map for live viewing or archive viewing.
• The system should allow creation of events for any camerafrom the drop-down menu or
any other easy to use interface. Such an event, when stored, should be searchable based
on the camera, time, and event type. It should be possible to write description about the
event.

Page 160 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• The system should show event notification from the cameras on the map itself. The
operator should be able to click on the event notification of a particular camera on the
map and the system should open the event window on the operator screen.
• The system should integrate with existing city GIS, online maps such as Google Maps,
OpenStreetMap etc.. as required by the local authorities
• The system should generate an alert when the total available storage drops below the
configured threshold limit.
• The operator console should show icons for the quick understanding of the system health
status related to camera status, junction server status, database server connection status
and storage status. The respective icons should change the color when any of the system
component has problems. The health status should have the following information in drill
down report format:
• System map showing all junction servers in the system. Clicking a junction server entry
should lead to details of the junction server such as camera status, real time utilization of
server resources such as cores, RAM and storage. Drilling further down, camera details
should be available such as camera name, IP address, major and minor stream, real time
bitrate and frames configured for analytics.

• Storage Status showing central storage and all the network drives and utilization of the
storage
• All the users logged into the system with the time since login. It should be possible to force
log-out the user, send a message to the user and mirroring the desktop of the user from
the same screen.

a) Recording server status showing status of the live recording of the cameras in the central
server, list of junctions which are sending live feed, total events generated at each
junction and events pending to synchronized.

• The system should have a dashboard which should show the following information:

a) Status of analytics, events and clips generated at junction servers

• Camera-wise status showing processed and dropped frames

a) Event clip generation time, status of transfer of clips from junction server to central
aggregation server

• The operator console should show vital system parameters for components such as
Database Server, Media Servers, Local Workstation and Storage System (all available
storages). The client should show the parameters such as CPU Core Usage, RAM Utilization
and Storage Utilization.
• The system should have reports such as camera uptime availability, camera recording
percentage, recording status, critical events, incident video, etc.
• The system should provide facility to search for the cases of violations occurred during any
specific span of time, and provide a statistical analysis of the number of such incidences
occurring during various days of the month, various months of the year in graphical format.A
report of all such incidences should be automatically generated by the system in a
spreadsheet (.xls format),and can be automatically emailed to the designated email
addresses.

Page 161 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• The system should allow the users to download multiple segments of the video, which are
encrypted with password from single or multiple cameras from the archive with an option
to tag each downloaded segment with text messages. The Video segments should be
downloaded in a single folder along with excel spreadsheet where details of each of the
video segments are listed as hyperlinks to the exported video.
• The system should allow the operator to configure email account and SMS gateway for
sharing various alerts through email and SMS.
• The system should maintain log of various system generated alerts. The system should also
maintain full audit trail in the logs.
• The system should be integrated with ICCC platform to show alerts and any other details
required.

Data Security

• The system should have the capability to transfer the data to ICCC through proper
encryption in real time. The application for traffic violation detection system should adhere
to National Cyber Security Policy to ensure that the critical information processed and
stored by the application is secure from cyber-attacks / hacking / hijacking.
• Integration with CCTNS & Transport Dept Systems: Bidders need to ensure that there is
seamless integration between various Government databases and security of citizens &
their assets is carried in a holistic manner. Please note that some of the integration would
need to be through web services while in some cases it may be required to maintain local
databases.

Page 162 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
ICT Solution:
With a view to address the above issues it is now proposed to implement the following
modules under Intelligent Traffic Management System

1. Entry Exit Point Management

2. Corridor Management
3. Red Light Violation Detection
4. Speed Violation Detection
5. Adaptive Traffic Controller System
6. Automatic E Challan System

Following are ICT solutions.

1. Entry Exit Point Management with video based automatic traffic count & classification
along with ANPR for all major Entry Exit points to have precise information about vehicle
entering, exiting, monitoring and control of traffic in primary city corridor for Traffic
Information, management & Control.
2. ATCS system with edge based processing using Local processing units(LPU)
3. Variable Messaging Display integrated with video based speed detection to display the
speed information for awareness of drivers
4. Traffic Enforcement System:
The ITMS shall provide various traffic violation detection use cases using Artificial
Intelligence and Deep Learning based technology. It shall provide insights for the traffic
planners using innovative dashboards for various parameters such as violations, traffic
count, vehicle classification, present and historical trends, comparison of roads or
junctions. The ITMS shall serve as a decision support system and provide actionable
intelligence to help make the city roads safer and less congested for both motorists and
pedestrians.
The ITMS shall have the components such as Junction Servers (available at a traffic junction or
available centrally), Event Aggregation Servers, Management Server and a Database. Each
component shall provide failover redundancy. There shall be no dependency on thespecific
operating system, database software, virtualization platform, storage technology and compute
infrastructure.
The ITMS platform architecture shall allow flexible and modular deployment of software
components in a distributed computing architecture. At the same time, it shall allow fully
centralized deployment of the software application. The distributed architecture shall
support a Junction Server installation in any COTS hardware server suitable for operation
as per the respective temperature and environmental conditions at the traffic junction for
local processing of the connected video surveillance cameras. The Junction Server should
send the traffic events and the metadata to the Events Aggregation servers. The Events
Aggregation Server shall manage and aggregate the alerts generated from the Junction
Servers spread across various locations. Under the centralized deployment the video feeds
shall be processed on the servers at the data center. The platform shall be robust to
support on-premise or on-cloud infrastructure.
It shall be possible to connect the Junction Servers using wireless connectivity such as 3G
/ 4G or 5G if required, without any dependency on the static public IP addresses. The
Junction Servers shall store the violation records and the junction camera video streams
locally for the configurable duration.
The ITMS shall offer business continuity in case of disasters. DC-DR architecture shall
Page 163 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 support granular control on the data safe-keeping and business continuity with automated
two-way synchronization of events, violation records, images, and video clips. It shall be
possible to configure business continuity, data safe -keeping , store archived information on DR
.
The ITMS shall have support for Block and Object Storage on cloud platforms. The system shall
support pushing the recorded video file on a definable schedule to the Object Storage.
The ITMS shall be built considering the information security risks. It shall have multiple levels of
authentication and access control mechanisms such as

A. Role based Authentication

B. Session control using encrypted tokens
C. Restricted user to a particular hardware workstation
D. Multi Factor Authentication with provision to receive the OTP via text message on the
registered mobile of the user and through the registered email address and
F. Single sign-on based on LDAP and Active Directory. It shall allow restricting an operator
to a single or multiple traffic junction/s and associated cameras.
ITMS must provide necessary software required to meet the security requirements
stated above.

All the communication among the servers and clients shall be secured and the ITMS shall
support the SSL and TLS communication. It shall have option of encryption with AES 128/
256 and RSA 1024/2048 encryption standards. It shall support secure communication
between the camera and the server using SRTP and RTSP protocols. The ITMS shall have
been tested for vulnerabilities and shall have been penetration tested as per the OWASP
guidelines. Certificates from the CERT-In empaneled auditor from the respective country
of origin clearly indicating the encryption and Vulnerability Assessment and Penetration
Testing (VAPT) test shall be available.

To facilitate communication and information collaboration among the operators from

various traffic zones, the ITMS shall provide the built-in chat function to exchange the
text, image, video clips or any other file from the workstation to other fellow operators or
supervisors, thus creating an ad-hoc collaborative environment for incident investigation.
The ITMS shall provide all the use cases and functionalities mentioned in the specifications
in a unified platform. The ITMS shall provide the multicasting functionality for monitoring
live and archived videos from the unified client. It shall provide an integrated management
functionality for camera, recording, traffic violation and incident use cases management
and user management for ease of operation.
The ITMS shall be a futuristic solution and shall offer flexibility in distributing the compute
at various stages within the architecture to optimize the compute requirements.

System Management Functions

ITMS should have robust system management functions. The ITMS shall provide centralized
management of the Junction Servers, aggregation, and processing servers through a unified
client interface. The ITMS shall be based on the latest Artificial Intelligence and Deep Learning
technologies for continuous improvement of accuracy in generating data by means of
analyzing video frames.
At minimum, ITMS shall have:
Page 164 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• User friendly, centralized software update mechanism on Junction Servers based on the
schedule.
• Framework to deploy trained model files to all the Junction Servers at a single go.

• Provision to check the performance of various stages in Analytics application deployment

pipeline
• Camera-wise status showing processed and dropped frames.
• Total number of events generated in the Junction Servers, total events, event clips and
images transferred to the control room servers and events in the queue that are yet to be
transferred.
• Dashboard to display storage availability and in the Junction Servers including camera and
Junction Servers uptime or SLA reports
• Provision to prioritize the transfer of data from the Junction Server to the central servers.
Event Metadata and event images shall be prioritized over the video clips and also prioritize
the latest events over the old events.
• Health-dashboard to display CPU and memory utilization status of Junction Server and
servers

The ITMS unified client shall show system health alerts for camera, junction server, database
server and storage. The drill-down system health shall cover area, junction, to further details
of system utilization, major and minor stream, real time bitrate and frames configured for
analytics, camera details such as Camera Name, IP Address, Recording Server status showing
status of the live recording of the cameras in the central server, list of junctions which are
sending live feed etc.
The storage status shall show central storage and all the network drives and utilization of the
storage and alert when the total available ITMS storage drops below the configured threshold
limit.
The ITMS shall maintain log of various system generated alerts. The system shall also maintain
full audit trail in the logs.

Video Handling and General Functions

The Junction Servers shall record the camera streams locally (continuous, event based, schedule
based, trigger based) for the duration as per the requirement. The ITMS shall synchronize the
recorded video streams from the Junction Servers to the Control Room storage devices. The
system shall synchronize such videos in the background depending on the event transfer
priority. For example, during the night when there are fewer events generated in the system,
the Junction Server shall transfer the recorded video to the Control Room ITMS servers. It shall
be possible for the operators to replay the recorded videos stored in Junction Servers on-
demand.

The below functionalities should be achieved by ITMS or VMS or integration of both as required.

1. ITMS shall allow recording a matrix of cameras from the operator workstation in a single
file to create investigative report as a single video file in case of an event or an accident.
Page 165 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 It shall be possible to share such a file to the fellow operators or supervisors using a built-
in chat function. It shall be possible to search the archive video using date, time, type of
event, etc. It shall be possible to view live/archive videos in multiple matrix layout for all
the cameras in the system in real time. At least 1x1, 2x2, 3x3, 1+5, 1+7. It shall be
possible to cycle multiple layouts with configurable time. A drag and drop functionality shall
be supported for viewing cameras on the screen.
2. ITMS shall allow creation of customized, layered maps using standard picture files or GIS
maps and it shall be possible to drag and drop the cameras on the map for easy navigation
based on the location on the map. It shall be possible to select any camera or group of
cameras on the map for live viewing or archive viewing.

3. ITMS shall allow creation of manual events by the operators. from any live camera view
using a drop-down menu of various anomalies. Such an event, when stored, shall be
searchable based on the camera, time, and event type. It shall be possible to write
description about the events.

4. The system shall allow the users to download multiple segments of the video, which are
encrypted with password from single or multiple cameras from the archive with an option
to tag each downloaded segment with text messages. The Video segments shall be
downloaded in a single folder along with excel spreadsheet where details of each of the
video segments are listed as hyperlinks to the exported video files.

The system shall provide facility to search for the cases of violations occurred during any
specific span of time and provide a statistical analysis of the number of such incidences
occurring during various days of the month, various months of the year in graphical format.
A report of all such incidences shall be automatically generated by the system in a spreadsheet
(.xls, .csv format) and can be automatically emailed to the designated email addresses.

The system shall allow the operator to configure email account and SMS gateway for sharing
various alerts through email and SMS.

Data Analytics and Decision Support Functions

The ITMS shall support to implement a data driven ITMS and not a mere transaction based
system. ITMS shall be useful to all the stakeholders such as Crime investigation department,
Traffic Police and City Planners. The ITMS shall provide various ways to collect and synthesize
the data. At minimum it shall be possible to:

• Analyze the frequency of the events and generate notifications on the configurable
deviation from the median.
• It shall assist in finding the anomaly than mere violation alerts.
• It shall help extract various attributes for the actors operational on the road forassisting in
traffic planning and investigation.
• Show graphical representation of the data generated from the system such as traffic
violations by A. type, B. vehicle classes, C. Junction D. Time frame E. TrafficDistrict, F. Traffic
Flow, G. Average Speed, H. Headway, I. Private, Commercial, Auto, Electric Vehicles, J.
License Plate Quality and classification such as HSRP, Non-HSRP, Dilapidated, No License
Page 166 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Plates, etc. It shall allow comparison for a group of junctions (up to three) on these
parameters.
• Provide impact analysis of the traffic planning decisions taken such as making a road one-
way, blocking turns in a junction, restricting certain classes of vehicles during certain
times of the day, restricting lanes for certain classes of vehicles, etc. It shall be possible
via a video analysis, synopsis and simulation tool to analyze the before and after effect of
the traffic planning decisions. It shall allow entering information for such decisions and
monitor the same on the graph. It shall have ready to use filters – last 1 day, 7 days, 15,
days, month, year, etc.
• Plot average count of vehicles or violations on the GIS map. The system shall show traffic
violations hotspot on the GIS.
• Provide customized dashboards for various stakeholders with configurable information
such as a developing congestion, dropping headway, dropping average speed, increasing
violations, etc.
• The system shall make use of the data being generated through the ITMS system for the
benefit of the authority as a decision support system. ITMS shall generate an alert on the
following conditions:
• When the average speed of any junction drops by the configured threshold (e.g., 20%)
as compared to the regular average of last one or two weeks.
• When an average volume of vehicles of any category increases suddenly by the configured
threshold (e.g., 20%) as compared to the regular average of last one or two weeks.
• When an overall volume of vehicles increases suddenly by the configured threshold (e.g.,
20%) as compared to the regular average of last one or two weeks.
• Detect commercial vehicles having age more than the configured age in years (e.g., 15
years).
Integration Functions

ITMS should have published APIs to interface with external systems such as Integrated
Command and Control Application,

The ITMS should have a proven track record in automatically validating the traffic violations
based on the ANPR conversion confidence level.

The system should have the capability to integrate with the VAHAN / SARATHI system to fetch
vehicle related details as required and as made available by the VAHAN / SARATHI system.
It should allow automated and on-demand modes for verification.

The system should provide a query service to the other districts / states to query a particular
vehicle if it was seen in the city OR a provision to issue a lookout notice to police which can
be fed in the database and any detection of the lookout vehicle should generate an alert.
The system should have integration with the WhatsApp messaging service to share
information on the selected groups. The operator should be able to share
alert/violation/footage related to an event or a vehicle.

The system should be able to integrate with external systems such as integrated command
and control system, C4i systems, IP Speakers, etc.

Page 167 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.4.12 Entry Exit Point Management:

The City of Puducherry has 4 entry exits and it is proposed to install the Entry & Exit point
Management system in the following indicative locations to monitor the Public transportation
schedules and Bus timing thru ANPR along with City Entry/Exit.

1 ECR Entry

2 Near Accord Pondy

3 Indira Gandhi Junction
4 Cuddalur Exit

The functional/ Technical requirement of the proposed system for entry exit point shall be
as follows:

6.4.12.1 ANPR for Entry Exit:

The system shall capture the license plates of the vehicles while capturing the vehicle
categories such as cars, Heavy Commercial Vehicles, Three Wheelers, Two Wheelers andBuses
and shall store this information along with the license plate information for each transaction in
the database. The system shall provide 95% and better detection accuracyand 90% and better
license plate conversion accuracy into a text string for Four wheelers and above vehicles for
standard reflective license plates.

The system shall categorize the license plates into Good (readable), Bad/dilapidated (partial
or fully non-readable), Broken, License Plates without numbers. System shall also provide the
license plate conversion confidence percentage. Dashboard with various filters shall also be
available with the application. The system shall have the dashboard to viewcaptured vehicles
with categories such as private, commercial, electric, and other specialvehicles such as military
(subject to the availability of training datasets for the special categories) at day time without
connecting other systems, e.g vehicles registry database.

The ITMS shall provide the ability to capture vehicles with no number plate, hand-written /
fancy number plates, number plates with regional languages.

The system shall have Vehicle Counting and Classification functions using the ANPR and
overview cameras.

The system shall detect the colour of all the vehicles on best effort basis, in the camera view
during daytime and label them as per the predefined list of configured system colours. The
system shall store the colour information of each vehicle along with the license plate information
for each transaction in the database.

The system shall store certain license plates of vehicles which are stolen or suspicious with a
facility to edit the lists as required including bulk importing functionality. The system shall
generate an automatic alert in the control room when it detects the vehicle from the hot list/s
through the ANPR camera. It shall be possible to get a trajectory of such/any selected vehicle

Page 168 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
on a GIS map on demand.

The operator shall be able to edit the license plate number of the vehicle in case it is wrongly
captured. The system shall show the captured vehicles with selectable, ANPR conversion
confidence. The system shall keep full audit trail of the user actions.

The system shall have function of quickly searching the number plate based on criteria such
as full or partial number of the license plate, colour of the vehicle, Speed of the vehicle,
Classification of vehicle, Junction Name, etc.

The system shall allow the operator to set traffic rule such as “no heavy vehicles during certain
time of the day” for selected traffic junctions/cameras and display in VMD. The system shall
identify the heavy vehicles and generate an alert in case the vehicle is violating the rule within
the configured time.

The system shall self-analyse the confidence level of the ANPR conversion. In case the
confidence level is above user-configured threshold, the violation shall be pushed
automatically for traffic ticket generation.

The system shall be flexible to capture the license plates and the traffic violations (subject to
the required field of view) from front-side or back-side using a single camera for each lanes
at least.

6.4.12.2 Specification for ANPR Camera /Overview Camera/ Evidence Camera

Compliance
Sl. Minimum Specification (Yes / No)
No
Make:

Model:

1 Image Sensor 1/2.8” 2MP Progressive Scan CMOS or better

Day/Night
2 Operation Yes with IR Cut Filter

Minimum
3 Illumination Color: 0.03 lux or better ; B/W 0 Lux with IR

5.5-62 mm (+/- 1mm) Motorized Varifocal Lens or

4 Lens better

5 Electronic Shutter 1/5 to 1/50,000s or better

6 Image Resolution 1920x1080 or better

7 Compression H.265 or better

Frame Rate and Bit Up to 60 fps with Controllable bit rate, frame rate
8 Rate and Maximum Bit rate

Page 169 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Compliance
Sl. Minimum Specification (Yes / No)
No
Minimum 3 Nos, individually configurable
simultaneous streams in H.265 @ 1920x1080 & 60
9 Video Streams Fps

H: 54.58°(Wide)~5.30°(Tele) / V:
Angular Field of 32.19°(Wide)~3.00°(Tele) / D:
10 View 61.4(Wide)~6.06(Tele)

Built in 8 point polygonal zones areas in the video

11 Motion Detection stream.

Lens/Barrel
Distortion
Correction &
12 Corridor View Built in feature required

Wide Dynamic
13 Range 150 dB or better

14 IR 100 Meter (Built in or External) IR.

15 Alarm 1 Input & 1 Output

Selectable (Mic in/Line in), Supply voltage:

16 Audio In 2.5VDC(4mA), Input impedance: 2K Ohm

17 Audio Out Line out, Max. output level: 1Vrms

G.711 u-law /G.726 Selectable

G.726(ADPCM) 8KHz, G.711 8KHz
G.726 : 16Kbps, 24Kbps, 32Kbps, 40Kbps
18 Audio Compression AAC-LC : 48Kbps at 16KH

Defocus detection, Directional detection, Fog

detection, Face detection, Motion detection,
Digital auto tracking, Appear/Disappear,
Enter/Exit, Loitering, Tampering, Virtual line,
Audio detection, Sound classification. Can be
19 Analytics achieved via VMS and VA

Alarm input, Motion detection, Analytics,

20 Event Triggers Network disconnect and others

FTP, HTTP, Email notification, Edge Storage,

21 Event Actions Alarm Output

Micro SD/SDHC/SDXC 1 no. slot of 512GB

22 Edge Storage capacity or better with min.512GB Memory card

Page 170 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Compliance
Sl. Minimum Specification (Yes / No)
No
IPv4, IPv6, TCP/IP, UDP/IP, RTP(UDP), RTP(TCP),
RTCP,RTSP, NTP, HTTP, HTTPS, SSL/TLS, DHCP, FTP,
SMTP, ICMP, IGMP, SNMPv1/v2c/v3(MIB), ARP,
DNS, DDNS, QoS, PIM-SM, UPnP, Bonjour ,
23 Protocols LLDP(optional), SRTP

HTTPS(SSL) Login Authentication, Digest Login

Authentication, IP Address Filtering, User access
Log
24 Security 802.1X Authentication (EAP-TLS, EAP-LEAP)

The firmware upgrade shall be done though

web interface, The firmware shall be available
25 Firmware Upgrade free of cost

26 Interface RJ 45, 100 Base TX or better

27 Memory 1024 MB RAM, 256 MB Flash or better

28 Enclosure IK10 &IP67 or Nema4x or better

Power
29 requirements Vendor to specify, POE Preferred

Operating
30 Temperature 0 °C to 55°C or better

Operating
31 Humidity 90% RH or better

32 Certification UL, CE, FCC, BIS,

1. The interface shall be available for integration

Application with 3rd party analytics and applications in
Programmers public domain
33 Interface 2. ONVIF

34 Deleted

35 Mount Wall Mount/ Pole Mount

36 Warranty Min. 5 Years

37 Privacy Masks Minimum 4

6.4.13 Corridor Management:

• With a view to ensure that the traffic in the major trunk roads are monitored and proper
details are being disseminated to the commuters. It is proposed to install corridor
Page 171 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 management systems in three corridors. These Corridors will also have Traffic enforcement
systems like Instant Speed, Average Speed, Wrong direction, sudden lane changing. Prime
corridor as mentioned above will have evidence cameras video-based analytics to provide
traffic data and will also provide possibility to view video from these monitoringstations to
verify any unusual incident from ICCC. The precise information from solution will provide
volume, classification, average speed of traffic, any unusual incident on the corridor which
can impact traffic flow conditions. The system should have Vehicle Counting and
Classification functions using the ANPR and evidence cameras.

The details of the said corridor are as follows:

Sl. No Name From To

1 Main Corridor ECR Entry Cuddalur Exit

2 Corridor 1 Indira Gandhi Junction Beach Start

PWD Office
Corridor 2
3 Adigal Salai Junction Junction

The functional/Technical requirement of the said system shall be as follows:

6.4.14 Variable Message Display

Page 172 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• The Variable Message Display(VMD) will be able to play Text Image and Full Color Video
and approximately 3.8 meterX1.9 meter. Hardware should have minimum 5 year warranty
• The (VMD) should have : pixel density 2500Pixels/sq.m , RGB Resolution 16pixelsX 8 pixels
, brightness >12300 cd/sq.m., color amount 16million., Contrast 3000:1,
• The (VMD) should have best view distance of 20 to 100 meter with optimum viewing
Horizontal>30, Vertical>
• The (VMD) shall be of IP 67
• The cabinet material should be steel and should double side back door

• The (VMD) system should be supplied with all required controllers and should have
integrated base with traffic and other information portal from smart city control roomICCC
and Central Control Software shall allow controlling multiple (VMD) from one console.
Capable of programming to display all types of Message/ advertisement having
alphanumeric character in English, - and combination of text with pictograms signs. The
system should have feature to manage video / still content for VMS display.
• The system should have capability to divide VMS screen into multi-parts to display diverse
form of information like video, text, still images, advertisements, weather info, city info
etc. The system should also provide airtime management and billing system for paid
content management. Capable of controlling and displaying messages on VMS boards as
individual/ group.
• Capable of controlling and displaying multiple font types with flexible size and picture sizes
suitable as per the size of the (VMD). Capable of controlling brightness & contrast through
software.
• Capable to continuously monitor the operation of the Variable Message sign board,
implemented control commands, and communicate information to the ICCC via
communication network.
• Real time log facility – log file documenting the actual sequence of display to be available
at central control system.
• Multilevel event log with time & date stamp.
• Access to system only after the authentication and acceptance of authentication based on
hardware dongle or similar with its log.
• Location of each (VMD) will be plotted on GIS Map with their functioning status which
can be automatically updated.
• Report generation facility for individual/group/all (VMD) with date and time which
includes summary of messages, dynamic changes, fault/repair report and system accessed
logs, link breakage logs, down time reports or any other customized report.
• Configurable scheduler on date/day of week basis for transmitting pre-programmed
message to any (VMD) unit.
Page 173 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• Various users should access the system using single sign or similar 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.
• Apart from role-based access, the system should also be able to define access based on
location.
• Rights to different modules / Sub-Modules / Functionalities should be role based and proper
log report should be maintained by the system for such access
• Mounting : Should be mounted with standard poles , erecting structures and road
clearance.

Page 174 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.4.15 Specification for Speed Violation Camera:
Compliance
# Parameter Minimum Specifications or better
( Yes or No)

Make:

Model:

1 Image Sensor 1/2.8” 2MP Progressive Scan CMOS or better

2 Day/ Night Operation Yes with IR Cut Filter

3 Minimum Illumination Color: 0.03 lux or better ; B/W 0 Lux with IR

5.5-62 mm (+/- 1mm) Motorized Varifocal

4 Lens
Lens or better

5 Electronic Shutter 1/10 to 1/12,000s or better

6 Image Resolution 1920x1080 or better

7 Compression H.265 or better

Upto 60 fps with Controllable bit rate, frame

8 Frame Rate and Bit Rate
rate and Maximum Bit rate

Minimum 3 Nos, individually configurable

9 Video Streams simultaneous streams in H.265 @ 1920x1080 &
60 Fps

H:54.58°(Wide)~5.30°(Tele)/V:
10 Angular Field of View
32.19°(Wide)~3.00°(Tele)/D:
61.4(Wide)~6.06(Tele)
Built in 8 point polygonal zones areas in the
11 Motion Detection
video stream.

Lens/ Barrel Distortion

12 Correction & Corridor Built in feature required
View

13 Wide Dynamic Range 150 dB or better

14 IR 100 Meter (Built in or External) IR

15 Alarm 1 Input & 1 Ouput

Selectable(Mic in/Line in), Supply voltage:

16 Audio In
2.5VDC(4mA), Input impedance: 2K Ohm

17 Audio Out Line out, Max. output level: 1Vrms

Page 175 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 G.711 u-law /G.726 Selectable
G.726(ADPCM) 8KHz, G.711 8KHz
18 Audio Compression
G.726 : 16Kbps, 24Kbps, 32Kbps, 40Kbps
AAC-LC : 48Kbps at 16KH

19 Analytics Defocus detection, Directional detection,

Fog detection, Face detection, Motion
detection, Digital auto tracking,
Appear/Disappear, Enter/Exit, Loitering,
Tampering, Virtual line, Audio detection,
Sound classification and others. Can be
achieved via VMS and VA

Alarm input, Motion detection, Analytics,

20 Event Triggers
Network disconnect and others

FTP, HTTP, Email notification, Edge Storage,

21 Event Actions
Alarm Output

Micro SD/SDHC/SDXC 1 no. slot of 512GB

22 Edge Storage capacity each or better with min.512GB
Memory card

IPv4, IPv6, TCP/IP, UDP/IP, RTP(UDP), RTP(TCP),

RTCP,RTSP, NTP, HTTP, HTTPS, SSL/TLS, DHCP,
23 Protocols FTP, SMTP, ICMP, IGMP, SNMPv1/v2c/v3(MIB-
2), ARP, DNS, DDNS, QoS, PIM-SM, UPnP,
Bonjour , LLDP, SRTP

HTTPS(SSL) Login Authentication, Digest Login

Authentication, IP Address Filtering, User
24 Security
access Log 802.1X Authentication (EAP-TLS,
EAP-LEAP)

The firmware upgrade shall be done though

25 Firmware Upgrade web interface, The firmware shall be
available free of cost

26 Interface RJ 45, 100 Base TX or better

27 Memory 1024 MB RAM, 256 MB Flash or better

28 Enclosure IK10 & IP67 or Nema4x or better

29 Power requirements Vendor to specify, POE Preferred

30 Operating Temperature 0 °C to 55 °C or better

31 Operating Humidity 90% RH or better

32 Certification UL, CE, FCC, BIS,

Page 176 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 1. The interface shall be available for
Application integration with 3rd party analytics and
33
Programmers Interface applications in public domain
2. Onvif

Deleted
34

35 Mount Wall Mount/ Pole Mount

36 Warranty Min. 5 Years

Speed detection system

37 Upto 200 Kmph +/- 2%
to capture speed

Speed Enforcement
38 Radar/Laser/Other better technologies
Technology

6.4.16 Instant Speed Violation Detection:

The broad scope of work to be covered under this sub module will include the following,but is
not limited to:

• Install the Speed Violation Detection Systems across the city. This system shall capture
the infractions of speed violations at these locations. The proposed Instant Speed system
should have proper test certification in compliance with standards for speed enforcement
systems.
• Design, supply, and install the speed violation detection system as per requirement. This
includes supply all the necessary equipment for the camera and detection system,
including but not limited to sensors, computers, ancillary camera equipment, camera
housings, camera poles, warning signs and shall make the final connections to the camera.
• The solution proposed shall seamlessly integrate with the E-Challan system proposed
under the scope of this project.
• Providing all the necessary IT infrastructure for analysis, storage & retrieval of the
infraction information at ICCC or any other location as per the requirement.

The functional requirement of the said system shall be as follows:

Functional Specification for Instant Speed System:

Compliance
S/N
Functional Requirement ( Yes / No)

Page 177 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Make:

Model:

1 The proposed solution should have video based speed violation detection
feature with a facility to set different speed limits for different categories of

vehicles and schedule. The feature should have the functionality to prove
the vehicle speed using a simple on-screen tool.

The speed detection use case (along with license plate recognition)
should be capable to read speeds in excess of 100- 200 km/hr. A certificate
2
from an institute of repute, which can issue such a certificate in India should
be provided to substantiate the claim.

The speed detection software system shall be certified by any accredited

laboratory for speeds from 40 KMPH to 200 KMPH with variation of less than
3 2% at various speed thresholds such as 40 KMPH, 70 KMPH, 100 KMPH,
130KMPH, 170 KMPH and 200 KMPH speeds.

Software should also provide Average Speed detection functionality for a

control section / corridor within the city. All vehicles passing through the
4 control section at a Speed greater than a determined speed limit shall be
detected as violation. It should be possible to create multiple points within
a long corridor for determining the average speed.

6.4.17 Average Speed Violation Detection:

Software should also provide Average Speed detection functionality for a control section
/ corridor within the city. All vehicles passing through the control section at a Speed
greater than a determined speed limit shall be detected as violation. It should be possible
to create multiple points within a long corridor for determining the average speed.

6.4.18 Wrong Side Driving Violation

Compliance
# Minimum Requirements
( Yes / No)

A. General

1. Wrong Side Detection of Vehicle Movement –The system should

be installed at critical junctions or streets as identified by the
department to capture the wrong direction vehicle movement.

2. The system should identify and capture multiple violating

vehicles and the E-Challan standard procedure should be
triggered.

6.4.19 Adaptive Traffic Control System

Page 178 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
It is proposed to implement Adaptive Traffic Controller at identified junctions. The
proposed system shall have a fully adaptive traffic controller with the following
functionalities:

Traffic Signal Controller

Compliance
# Description
( Yes / No)

Make:

Model:

The Traffic Signal Controller equipment is a 32 bit or 64-bit

microcontroller with a solid-state traffic signal lamp switching module with the
ability to program any combination of traffic signal stages, phases, and
1 junction groups. The controller will ideally have a conflict monitoring facility to
ensure that conflicting, dangerous are pre-flagged at the programming stage
and these are disallowed even during the manual override phase. Should have
5 year warranty

The Traffic Signal Controller can be controlled through the central traffic control
center as an individual junction or as part of the group of traffic junctions along
2 a corridor or a region. The signal controller design must be flexible for the
junction could be easily configured to be part of any corridor or group
definition and could be changed through a central command controller easily

Site-specific configuration data shall be stored in a non-volatile memory device

(FLASH memory) easily programmable at the site through a keypad or laptop.
3 A minimum of 512KB flash memory and 128KB RAM shall be provided. Volatile
memory shall not be used for storing the junction-specific plans or signal timings.

All timings generated within a traffic signal controller shall be digitally derived
4
from a crystal clock which shall be accurate to plus or minus 100 milliseconds.

The controller shall provide a real-time clock (RTC) with battery backup that
sets and update the time, date, and day of the week from the GPS. The RTC
5
shall have a minimum of 10 years battery backup with maximum time
tolerance of +/- 2 sec per day.

The controller shall have the facility to update the RTC time from the ATCS
6
server, GPS, and through manual entry.

The traffic signal system including the controller shall have provision for audio
7
output tones and should be disabled-friendly.

The controller shall be capable of communicating with the ATCS server through
8 Ethernet on a managed leased line network or any other appropriate
stable communication network.

Police Panel

Page 179 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Compliance
# Description
(Yes / No)

Make:

Model:

Four Hurry Call switches: The Hurry Call mode will provide the means to force
the controller to a defined stage, without violating safety clearances. A pre-
1 emption input may be used to demand the Hurry Call mode to give theright
of way to emergency vehicles. It should be possible to configure the Hurry
Call switches to any stage as per site requirements.

One Forced Flash Switch: Activation of this switch should force the signal to
2
Flashing Amber / Flashing Red.

One Auto / Manual Switch: Activation of this switch should enable the manual
3 operation of the controller. Deactivation of the manual switch shall continue
from the current stage without interruption.

One Manual Advance Pushbutton Switch: In manual operation mode, the

stages appear in the sequence specified in the signal plan timetable.
4
Activating the pushbutton switch shall terminate the currently running stage
and start the next, without violating safety clearances.

One Junction OFF Switch: Activating this switch should put OFF all signal lamps.
5 On deactivation of the switch, the traffic signal controller shall resume its normal
operation without violating any safety clearances.

Modes of Operation

Compliance
# Description (Yes / No)

Fixed Time: In fixed time (pre-timed) mode the traffic signal controller shall
execute stage timings according to the site-specific timetable maintained in
1 the traffic signal controller FLASH memory. Inputs from vehicle detectors shall be
ignored in this mode and no pre-emption shall be made at any stage. Cycle
time remains constant in every cycle execution for a given time period.

Vehicle Actuation with All Stages Pre-emption: In the vehicle actuation with all
stages pre-emption mode, the traffic signal controller shall execute stage
timings as per demand from vehicle detectors within the constraints of
2 Minimum Green, Maximum Green running period for the stage, and Cycle time
stored in the traffic signal controller FLASH memory. Pre-emption shall be
possible for all demand actuated stages. Cycle time may vary in every cycle
execution.

Page 180 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Semi-Actuation: In the semi-actuation mode, the traffic signal controller shall
execute stage timings in the vehicle actuated stages as per demand from
vehicle detectors within the constraints of Minimum Green, Maximum Green
3 running period for the stage, and Cycle time stored in the traffic signal
controller FLASH memory. All other stages shall execute the Maximum green
time configured for the stage. Pre-emption shall be possible for all demand
actuated stages. Cycle time may vary in every cycle execution.

Stage Skipping: The traffic signal controller shall not execute the stage enabled
4 for skipping when there is no vehicle demand registered for the stage till the
clearance amber time of the previous stage.

Transit Signal Priority (TSP) for buses: The traffic signal controller shall provide
5 transit signal priority for buses in the dedicated lane to ensure minimum stop
delay at the intersection, without violating safety clearances.

Vehicle Actuation with Fixed Cycle length: In-vehicle actuation with fixed cycle
length mode, the traffic signal controller shall execute stage timings as per
demand from vehicle detectors within the constraints of Minimum Green,
6
Maximum Green running period for the stage, and Cycle time shall be
maintained constant during a given timeslot. Pre-emption for all demand
actuated stages except for the Priority Stage shall be possible.

Page 181 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Full ATCS (FATCS): In FATCS mode, the traffic signal controller shall execute
stage timings as per demand within the constraints of Minimum Green,
Maximum Green running period for the stage, and Cycle time specified by the
Central Computer during every cycle switching. Pre-emption for all demand
actuated stages except Priority Stage shall be possible in this mode. The traffic
signal controller shall identify a communication failure with the central
computer within a specified period. In such an event the signal plan timings
shall be executed from the local timetable stored in the traffic signal controller
FLASH memory. The fallback mode of the traffic signal controller shall be
vehicle actuated. On the restoration of the communication with the central
computer, the traffic signal controller shall automatically resort to FATCS mode.
The traffic signal controller shall accept commands for remote selection
/ de-selection of the following from the Central Computer at ICCC.
· Hurry Call
· Flashing Amber / Flashing Red
· Junction Off
If not reverted to the normal operation within the period listed below, the
traffic signal controllers shall timeout the commands and operate normally
· Hurry Call – 5 Minutes
· Flashing Amber / Flashing Red – 30 Minutes
· Junction Off – 30 Minutes
The traffic signal controller shall report the following to the Central Computer
through the communication network every cycle or on an event as
appropriate.
· Green time exercised for each approach (stage pre-emption timing)
against the Green running period set for the approach by the Central
Computer
· Mode of Operation
· Lamp failure, if any
· Output short circuit, if any
· Detector failure, if any

Traffic Signal Controller Operating Parameters

Compliance
# Description (Yes / No)

It shall be possible to operate the filtered green (turning right signal)

1 along with a vehicular phase. The filter green signal shall flash for some time

Page 182 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 equal to the clearance amber period at timeout when operated with a
vehicular phase.

The pedestrian phase signal shall be configured for flashing red or flashing
2
green aspects during pedestrian clearance.

It shall be possible to configure any phase to the given lamp numbers at

3
the site.

4 Stages – The controller shall have the facility to configure at least 32 Stages

Cycle Plans – The controller shall have the facility to configure 24 Cycle Plans
and the Amber Flashing / Red Flashing plan. It shall be possible to define
5 different stage switching sequences in different cycle plans. The controller shall
have the capability for a minimum of 32 cycle-switching per day in the fixed
mode of operation.

Day Plans – The controller shall have the facility to configure each day of the
week with different day plans. It shall also be possible to set any of the day's
6
plans to any day of the week. The controller shall have the capability to
configure 20-day plans or as per requirement.

Special Day Plans – The controller shall have the facility to configure a minimum
7
of 20 days as special days in a calendar year or as per requirement.

Starting Amber – During power up the controller shall initially execute the
Flashing Amber / Flashing Red plan for some time of 3 Seconds to 10 Seconds.
8 The default value of this Starting Amber is 5 Seconds. The facility shall be
available to configure the period of Starting Amber within the given limits at
the site.

Inter-green – Normally the inter-green period formed by the clearance Amber

and Red extension period will be common for all stages. However, the
9
controller shall have a facility to program individual inter- green periods from 3
Seconds to 10 Seconds.

Minimum Green – The controller shall allow programming the Minimum Green
period from 5 Seconds to 10 Seconds without violating the safety clearances. It
10
should not be possible to pre-empt the Minimum Green once the stage starts
commencing execution.

All Red – Immediately after the Starting Amber all the approaches should
be given the red signal for a few seconds before allowing any right of way, as a
11
safety measure. The controller shall have programmability of 3 Seconds to 10
Seconds for All Red signal.

Signal lamps monitoring – The controller shall have inbuilt circuitry to monitor the
12
lamp status

Page 183 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Green – Green Conflict Monitoring – The controller shall have a facility to list all
conflicting phases at an intersection. The controller should not allow
13 programming of these conflicting phases in a Stage. A hardware failure leading
to a conflict condition (due to faulty devices or a short circuit in the output)
shall force the signal into Flashing Amber / Flashing Red.

Cableless Synchronization – It shall be possible to synchronize the traffic signal

controllers installed in a corridor in the following modes of operation, without
14
physically linking them and without a communication network. GPS enabled
RTC shall be the reference for the cable less synchronization.

15 Fixed Time mode with fixed offsets

16 Vehicle Actuated mode with fixed offsets

Input and Output facilities

Compliance
# Description (Yes / No)

Lamp Switching: The controller shall have a minimum of 48 (Scalable to 64)

1 individual output for signal lamp switching. The signal lamps shall be operating
on appropriate DC/AC voltage of applicable rating

Detector Interface: A minimum of 16 vehicle detector inputs shall be available

2 in the controller. All detector inputs shall be optically isolated and provided with
LED indication for detection of the vehicle For future scalability to ATCS

Communication Interface: The traffic signal controller shall support an Ethernet

3
interface to communicate with the ATCS server

Power Saving: The traffic signal controller shall have a facility to regulate
4 the intensity of signal lamps during different ambient light conditions thereby
saving energy.

Real-time Clock (RTC): The GPS receiver for updating time, date, and day of
5 the week information of the traffic signal controller should be an integral part of
the traffic signal controller.

The traffic signal controller shall update the date, time, any day of the week
6
automatically from GPS during power ON and at scheduled intervals.

Manual entry for the date, time, any day of the week shall be provisioned
7
for setting the traffic signal controller RTC (Real Time Clock).

It shall be possible to set the RTC from the Central Server when
8
networked

Page 184 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Keypad (optional): The traffic signal controller shall have a custom- made
9 keypad or should have provision for plan upload and download using
PC/laptop/Central Server

Operator Display (optional): The traffic signal controller shall have a LED-backlit
10
Liquid Crystal Display (LCD) as the operator interface.

Countdown Timer

Countdown Timer shall be installed at each traffic junction under this Project

Compliance
# Description
(Yes / No)

Make:

Model:

Count Down Timer to be configured in Vehicular Mode. Hardware

1
should have 5 year warranty

The Vehicular countdown timer should be dual-color,

2 · Red for Stop or STP
· Green color for Go

There should be alternate Red and Balance phase time for STOP or
3 STP
in Flashing

4 Alternate Green and Balance Phase Time for Go in Flashing

Communication Network

Compliance
(Yes / No)
# Description

Function of the Communication network is for remote monitoring of the

intersection and its management. Real time data (like RTC time, stage timing,
mode, events, etc.) from the traffic signal controller is required to be sent to
the ICCC and also individual
junctions can be controlled and actuated from central ICCC(Hurry Calls,
1 Forced Flash , Junction Switch off, Plan download and upload etc.).

ATCS Software Application :

The Adaptive Traffic Control Software application software shall do the following:

Page 185 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Compliance
# Description
(Yes / No)

Identify the critical junction(s) of a corridor or a region based on

1
maximum traffic demand and saturation.

The critical junction cycle time shall be used as the group cycle time i.e.
2
cycle time common to all intersections in that corridor or region.

Stage optimization to the best level of service shall be carried out based
3
on the traffic demand.

Cycle optimization shall be carried out by increasing or decreasing the

4 common corridor cycle time based on the traffic demand within the
constraints of Minimum and Maximum designed value of cycle time.

Offset correction shall be carried out to minimize the number of stops

and delays along the corridor for the priority route. Offset deviation
5 measured using distance and speed between successiveintersections
shall be corrected within 5 cycles at a tolerance of +/- 5 seconds
maximum.

The system shall have provision to configure the priority for upstream
signals as default. The ATCS software shall continuously check the traffic
6
demand for upstream and downstream traffic and automatically assign
the priority route to the higher demand direction.

Develop appropriate stage timing plans for each approach of every

7
intersection under the ATCS, based on real-time demand

8 Propose timing plans to every intersection under the ATCS in every Cycle

9 Verify the effectiveness of the proposed timing plans in every cycle

10 Identify Priority routes

11 Synchronize traffic in the Priority routes

Manage and maintain communication with traffic signal controllers

12
under ATCS

13 Maintain database for time plan execution and system performance

14 Maintain error logs and system logs

15 Generate Reports on request

Graphically present signal plan execution and traffic flow at the

16
intersection on desktop

Graphically present time-space diagram for selected corridors on

17
desktop

18 Graphically present network status on desktop

19 Make available the network status and report viewing on Web

Page 186 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The ATCS shall generate standard and custom reports for planning and
20
analysis

It shall be possible to interface the ATCS with a popular microscopic

21 traffic flow simulation software for pre and post-implementation analysis
and study of the proposed ATCS control strategy

Shall have the ability to predict, forecast, and smartly manage the traffic
22 pattern across the signals over the next few minutes, hours, or 3-5 days
and just in the current real-time.

Shall provide a decision support tool for assessing strategies to minimize

congestion, delays, and emergency response time to events via
23
simulation and planning tools like real-time traffic data fusion and control
of traffic signaling infrastructure on the ground.

Shall collect continuous information about current observed traffic

24 conditions from a variety of data sources and of different kinds (traffic
states, signal states, vehicle trajectories, incidents, road works etc)

Shall infer a coherent and comprehensive observed traffic state (speeds,

vehicular densities, and presence of queues) on all network elements,
25 from the above-mentioned observations, including vehicle trajectories,
through several map matching, data validation, harmonization, and
fusion processes

Shall extend the measurements made on only several elements both on

the rest of the unmonitored network, and over time, thus obtaining an
26
estimation of the traffic state of the complete network and the evolution
of this traffic state in the future

Shall forecast the traffic state concerning current incidents and traffic
management strategies (e.g., traffic signal control or variable message
27
signs), improving the decision-making capabilities of the operators even
before problems occur

Shall calculate customizable Key Performance Indicators (KPI) to quickly

28
assess the results

Shall provide calculated traffic flows estimation and forecast, queues

and
29
delays to Urban Control and Adaptive Signal Control Systems, allowing
for proactive Traffic Management and Control

Shall generate alerts to the operator that trigger on customizable

conditions in the network (starting with simple drops inflow, up to total
30
queue lengths along emission sensitive roads surpassing a definable
threshold)

Shall distribute both collected and calculated traffic information via a

variety of communication protocols and channels, ensuring high
31
interoperability degree and thus acting as a “traffic data and information
hub”

Page 187 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Shall create a traffic data warehouse for all historic traffic information
32
gathered from the hardware installed on the road network.

Shall operate in real-time that is continuously updating the estimates on

33 the state of the network and the travel times based on data collected
continuously over time.

Shall operate the traffic lights with the adaptive traffic controls, based on
34 the current and forecasted traffic demand and the current incidents,
thus optimizing the green waves continuously throughout the network

Enable a smart public transport priority respecting the delays for all road
35
users at once with the adaptive signal controller

Reports
Reports System shall generate corridor based and junction/Intersection based reports. The
application software shall generate the following reports, but not limited to the below. All
the reports shall be possible for selected dates.

Compliance
# Description
(Yes / No)

1 Junction/Intersection based reports

Stage Timing report – The report shall give details of the time at which
every stage change has taken place. The report shall show the stage
sequence, stage timings, and stage saturation of all stages of all cycles
2
for a day. The saturation is defined as the ratio between the available
stage timings to the actual stage timing executed by the traffic signal
controller for the stage (stage pre-emption time).

Cycle Timing report – The report shall give details of the time at which
3 every cycle has taken place. The report shall show the cycle sequence
and cycle timings for all the cycles in a day.

Stage switching report – The report shall give details of the time at which
4 a stage switching has taken place. The report shall show the stage
sequence, stage timings, and stage saturation for a day.

Cycle Time switching report – The report shall give details of the time at
5 which a cycle switching has taken place. The report shall show the cycle
sequence and cycle timings for the cycle in a day.

Mode switching report – The report shall give details of the mode
6
switching that takes place on a day.

Event Report - The report shall show events generated by the controller
7
with the date and time of the event.

Power on & down: The report shall show the time when the master is
8
switched on, and the last working time of the master controller.

Page 188 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Intensity Change – The report shall show the brightness of the signal lamp
9 is changed according to the light intensity either manually through the
keypad or automatically by LDR with a time stamp.

Plan Change – The report shall show the time of change of plan either
10
through the keypad or remotely through a PC or Server.

RTC Failure – The report shall show the time when the RTC battery level
11
goes below the threshold value.

Time Update – The report shall show the time when the Master controller
12 updated its time either manually through the keypad, automatically by
GPS, or through the remote server.

Mode Change – The report shall show the time when the Master
controller’s operating mode is changed either manually through the
13
keypad or a remote server. The typical modes are FIXED, FULL VA SPLIT,
FULL VA CYCLE, FLASH, LAMP OFF and HURRY CALL.

Lamp Status Report – The report shall show lamp failure report with date
14
and time of failure, the color of the lamp, and associated phase

Loop Failure Report – The report shall show the date and time of detector
15
failure with detector number and associated phase.

Conflict – The report shall show the conflict between lamps (RED, AMBER,
16 GREEN) in the same phase or conflict between lamps with another
phase.

Corridor Performance Report – The report shall show the saturation of all
17 the intersections in a corridor for every cycle executed for the corridor
and the average corridor saturation for a day

Corridor Cycle Time Report – The report shall show the Corridor cycle
18 time, Intersection cycle time, Mode of operation, and degree of
saturation of all the intersections in a corridor for every cycle for a day

Graphical User Interface

The application software shall have following Graphic User Interface (GUI) for user friendliness

Compliance
# Description
(Yes / No)

User login – Operator authentication shall be verified at this screen with

1
login name and password

Network Status Display – This online display shall indicate with

appropriate color coding on the site map whether an intersection under
2
the ATCS is online or off. On double-clicking the intersection, a link shall
be activated for the traffic flow display for the intersection.

Page 189 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Traffic Flow Display – This online display shall indicate the current traffic
3 flow with animated arrows, mode of operation, stage number being
executed, and elapsed stage time.

Saturation Snapshot – This display shall show the current saturation levels
4
of all intersections in a corridor.

Reports Printing / Viewing – This link shall allow selection, viewing, and
5
printing of different reports available under ATCS

Time-Space Diagram – The time-space diagram shall display the current

6 stages being executed at every intersection in a corridor with immediate
previous history.

Junctions shall be plotted proportionally to their distance on Y-axis and

7
time elapsed for the stage in seconds on X-axis.

8 Junction names shall be identified with each plot.

9 The facility shall be available to plot the time-space diagram from history.

Currently running stage and completed stages shall be identified with

10
different colors.

11 Stages identified for synchronization shall be shown in a different color.

Speed lines shall be plotter for stages identified for synchronization to the
12
nearest intersection in both directions.

It should be possible to freeze and resume online plotting of the Time-

13
Space diagram.

The system shall have other graphical interfaces for configuring the ATCS,
14
as appropriate.

Other features of the components in ATCS:

The proposed traffic controller shall be disabled friendly and shall also provide audio tones
output. The supplied ATCS controller would have all the functional capability as mentioned
above and also the future scalability to work an any of adaptive traffic algorithms available

• The system shall be able to detect the presence of vehicles near stop-line and do advance
detection for vehicles such as Traffic volume, count
• The system shall be capable of
- Counting the vehicle with at least 80% accuracy
- Classification of the vehicle with at least 3 classes
Red Light Violation Detection:

The broad scope of work to be covered under this sub module will include the following, but
is not limited to:

1. The RLVD Systems at traffic junctions across the city. This system shall capture the

Page 190 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 infractions of Red light and stop line violations at these junctions.
2. The RLVD system as defined of, all wiring connections to the traffic signal controllers and
to the camera platforms. Supply all of the necessary equipment for the camera and
detection system, including but not limited to: computers, ancillary camera equipment,
camera housings, camera poles, warning signs and shall make the final connections to the
camera. In some of the accident-prone junctions client might decide to put over speed
detection system and thus Shall consider these accident prone junctions.
3. The solution proposed shall seamlessly integrate with the E-Challan system proposed
under the scope of this project. The Authority shall facilitate to get access to the Vaahan
and Sarathi database, to access the same through use of appropriate APIs.
4. Providing all the necessary IT infrastructure for analysis, storage & retrieval of the
infraction information at ICCC or any other location as per requirement

Functional Specification for RLVD Application:

Compliance
S/N
Functional Requirement (Yes / No)

Proposed software should capture the License Plate of the vehicles

violating the red light or stop line when the signal is Red. It should be
1 possible to detect the signal color through image analysis or through
controller integration. The system should generate 3-5 violation
images of the vehicle as required.

Proposed software should have an in-built tool to compose detailed

evidence by stitching video clips from any IP camera in the junction
2 including surveillance cameras in the vicinity. The system should have
the functionality to export the violation evidence with water mark and
encryption as per the techno-legal requirements.

Proposed software should flag the RLVD event in the recorded video
3 within the system. It should allow mapping of multiple ANPR cameras
to a single evidence camera associated with the traffic junction.

It should be possible to view the video from an ANPR camera and the
4
evidence camera side-by-side for any selected violation.

To assess the traffic pattern, proposed software should have the report
of number of vehicles crossed during any signal state such as Green
5 Light / Orange Light, etc. The report should be available for each arm
and each signal. It should be possible to analyse the report for traffic
planning.

The system should generate alert when the signal light doesn’t
change for the pre-configured duration. The system should allow the
6
user to set minimum and maximum time for the signal light status
change.

Red Light Violation Detection System

Page 191 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Compliance
# Description
(Yes / No)

1 General

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
a. 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.

a) Red Light Violation

b) Stop Line Violation

The system should be capable of capturing multiple infracting

vehicles simultaneously in Different lanes on each arm at any
b. point of time with relevant infraction data like:
a) Type of Violation
b) Date, time, Site Name, and Location of the Infraction

c) Registration Number of the vehicle through ANPR Camera

system for each vehicle identified for the infraction.

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 the
nature of violation and proof there of: -

When it violates the stop line.

When it violates the red signal.
Besides, a closer view indicating readable registration number
c.
plate patch of the violating vehicle for court evidence for each
violation.
The system must have the in-built tool to facilitate the user to
compose detailed 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
in the court of law.

Page 192 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 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
d.
serially one after another in the same lane. The vehicles should be
identifiable and demarcated in the image produced by the
camera system.

The Evidence image produced by the system should be wide

enough to give the exact position of the infracting vehicles
e. concerning the stop line and indicate the color of the Traffic light
at the instant of Infraction even if any other means are being used
to report the color of the light.

The system should interface with the traffic controller to validate

f. the color of the traffic signal reported at the time of Infraction to
give correct inputs of the signal cycle.

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
g.
locations shall be available at the ICCC. The network should have
the capability to provide the real- time feed of the evidence
camera to the ICCC at the best resolution possible on the
available network.

The system shall be equipped with IR Illuminator to ensure clear

h. images including illumination of the Number Plate and capture the
violation image under low light conditions and night-time.

2 Recording & display information archive medium

The recording and display of information should be detailed on the

a.
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

Page 193 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 On site-out station processing unit communication & Electrical
3
Interface

The system should automatically reset in the event of a program

a. hanging up and restarting on a button press. However, the system
should start automatically after power failure.

The system should have a secure access mechanism for the

b.
validation of authorized personnel.

Deletion or addition and transfer of data should only be permitted

c.
to authorized users.

d. A log of all user activities should be maintained in the system.

Roles and Rights of users should be defined in the system as per the
e.
requirements of the client

All formats of the stored data concerning the infractions should be

f.
Non-Proprietary.

The communication between the on-site outstation processing unit

g. housed in the junction box and the detection systems mounted on
the cantilever shall be through appropriate secured technology.

The system should have the capability to transfer the data to ICCC
through proper encryption in real-time and batch mode for
h. verification of the infraction and processing of challan. Call
forwarding architecture shall be followed to avoid any data loss
during transfer.

If the connectivity to the ICCC is not established dueto

network/connectivity failures, then all data about the infraction
shall be stored on-site and will be transferred once the connectivity
i. is re- established automatically. There shall also be a facility for the
physical transfer of data on the portable device whenever
required. There should be a provision to store a minimum of one
week of data at each site on a 24x7 basis.

4 Mounting structure

Should be cantilever mounted and shall have a minimum of 6 mtrs

a. height with appropriate vertical clearance under the system from
the Road surface to ensure no obstruction to vehicular traffic.

It should be capable to withstand high wind speeds and for

structural safety, the successful bidder has to provide a
b.
structural safety certificate from qualified structural engineers
approved/ certified by Govt. Agency.

Page 194 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 It shall be painted with one coat of primer and two coats of PU
paint.
The equipment including poles, mountings should have an
c. 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.

Rugged locking mechanism should be provided for the onsite

d.
enclosures and cabinets.

5 RLVD Application

It should be capable of importing violation data for storage in

the database server which should also be available to the
a. 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.

It should generate the photograph of violations captured by the

outstation system which include a wider view covering the
b. violating vehicle with its surrounding and a closer view indicating
readable registration number plate patch of the violating vehicle
or its weblink on notices for court evidence.

All outstation units should be configurable using the software at the

c.
Central Location.

Violation retrieval could be sorted by date, time, location, and

vehicle registration number and the data structure should be
d.
compatible with the Police database structure. It should also be
possible to carry out recursive search and wild card search.

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
e.
failure, failure of linkage with a traffic signal, connectivity failure,
Camera tampering, sensor tampering).

The automatic number plate recognition Software will be part of

the supplied system, Success rate of ANPR will be taken as 95% or
f.
better during the daytime and 90% or better during the nighttime
with a standard number plate.

The application software should be integrated with the E Challan

software for tracing the ownership details of the violating vehicle
g. 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.

Page 195 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Image zoom function for number plates and images should be
provided.
h. 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.

Various users should be able to access the system using a single

sign-on and should be role-based. Different roles which could be
i.
defined (to be finalized at the stage of SRS) could be Administrator,
Supervisor, Officer, Operator, etc.

Apart from role-based access, the system should also be able to

j.
define access based on location.

Rights to different modules / Sub-Modules / Functionalities should

k. be role-based and proper log reports should be maintained by the
system for such access.

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, the
l.
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 the minimum outage.

The architecture must adopt an end-to-end security model that

protects data and the infrastructure from malicious attacks, theft,
etc. Provisions for the 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 as attacks and theft shall be controlled
and well supported (and implemented) with the security policy.
m.
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 endeavor to make use of the
SSL/VPN technologies to have secured communication between
Applications and their end-users. Furthermore, all the system logs
shall be properly stored & archived for future analysis and forensics
whenever desired.

The evidence of Infraction should be encrypted and protected so

n.
that any tampering can be detected.

Ease of configuration, ongoing health monitoring, and failure

detection are vital to the goals of scalability, availability, and
o.
security and must be able to match the growth of the
environment.

System shall use open standards and protocols to the extent

p.
possible and declare the proprietary software wherever used.

Page 196 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The user interface should be user-friendly and provide facilities to
the user for viewing, sorting, and printing violations. The software
q.
should also be capable of generating query-based statistical
reports on the violation data.

The data provided for authentication of violations should be in an

r.
easy-to-use format as per the requirements of the user.

Users should be provided with means of listing the invalid violations

s. along with the reason(s) of invalidation without deleting the
record(s).

Basic image manipulation tools (zoom etc.) should be provided for

t. the displayed image but the actual recorded image should never
change.

Log of user actions is maintained in read-only mode. The user

u. should be provided with the password and ID to access the system
along with user type (admin, user).

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, Regn.
v.
Number of violating vehicle and actual violation of violating
vehicle etc. so that the complete lane wise junction behavior is
recorded including (Red Light violation and Stop Line Violation)

Number plate should be readable automatically by the

software/interface. There should be a user interface for
w.
simultaneous manual authentication/correction and saving as
well.

Interface for taking prints of the violations (including image and

x.
above details).

RLVD Camera Technical Specification:

Compliance
# Parameter Minimum Specifications or better
(Yes / No)

Make:

Model:

1 Image Sensor 1/2.8” 2MP Progressive Scan CMOS or better

Day/ Night
2 Yes with IR Cut Filter
Operation

Page 197 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Minimum
3 Color: 0.03 lux or better ; B/W 0 Lux with IR
Illumination

5.5-62 mm (+/- 1mm) Motorized Varifocal Lens or

4 Lens
better

Electronic
5
Shutter 1/5 to 1/50,000s or better

Image
6 1920x1080 or better
Resolution

7 Compression H.265 or better

Frame Rate Up to 60 fps with Controllable bit rate, frame rate and
8
and Bit Rate Maximum Bit rate

Minimum 3 Nos, individually configurable

9 Video Streams
simultaneous streams in H.265 @ 1920x1080 & 60 Fps

Angular Field H: 54.58°(Wide)~5.30°(Tele) / V:

10
of View 32.19°(Wide)~3.00°(Tele) / D: 61.4(Wide)~6.06(Tele)

Motion Built in 8 point polygonal zones areas in the video

11
Detection stream.

Lens/ Barrel
Distortion
12 Built in feature required
Correction &
Corridor View

Wide Dynamic
13 150 dB or better
Range

14 IR 100 Meter (Built in or External) IR.

15 Alarm 1 Input & 1 Output

Selectable (Mic in/Line in), Supply voltage:

16 Audio In
2.5VDC(4mA), Input impedance: 2K Ohm

17 Audio Out Line out, Max. output level: 1Vrms

G.711 u-law /G.726 Selectable

Audio G.726(ADPCM) 8KHz, G.711 8KHz

18
Compression G.726 : 16Kbps, 24Kbps, 32Kbps, 40Kbps

AAC-LC : 48Kbps at 16KH

Page 198 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Defocus detection, Directional detection, Fog
detection, Face detection, Motion detection, Digital
auto tracking, Appear/Disappear, Enter/Exit,
19 Analytics
Loitering, Tampering, Virtual line, Audio detection,
Sound classification. Can be achieved via VMS and
VA

Alarm input, Motion detection, Analytics, Network

20 Event Triggers
disconnect and others

FTP, HTTP, Email notification, Edge Storage, Alarm

21 Event Actions
Output

Micro SD/SDHC/SDXC 1 no. slot of 512GB capacity or

22 Edge Storage
better with min.512GB Memory card

IPv4, IPv6, TCP/IP, UDP/IP, RTP(UDP), RTP(TCP),

RTCP,RTSP, NTP, HTTP, HTTPS, SSL/TLS, DHCP, FTP, SMTP,
23 Protocols
ICMP, IGMP, SNMPv1/v2c/v3(MIB-2), ARP, DNS, DDNS,
QoS, PIM-SM, UPnP, Bonjour , LLDP, SRTP

HTTPS(SSL) Login Authentication, Digest Login

24 Security Authentication, IP Address Filtering, User access Log
802.1X Authentication (EAP-TLS, EAP-LEAP)

Firmware The firmware upgrade shall be done though web

25
Upgrade interface, The firmware shall be available free of cost

26 Interface RJ 45, 100 Base TX or better

27 Memory 1024 MB RAM, 256 MB Flash or better

28 Enclosure IK10 & IP67 or Nema4x or better

Power
29
requirements Vendor to specify, POE Preferred

Operating
30
Temperature 0 °C to 55°C or better

Operating
31
Humidity 90% RH or better

32 Certification UL, CE, FCC, BIS,

Application 1. The interface shall be available for integration with

33 Programmers 3rd party analytics and applications in public domain
Interface 2. ONVIF

Deleted
34

35 Mount Wall Mount/ Pole Mount

36 Warranty Min. 5 Years

Page 199 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
37 Privacy Masks Minimum 4

System shall be Non-Intrusive. It shall not be

Red Light connected with traffic light and red light status is
38 Detection detected without any physical connection to traffic
light.
Red light system shall be completely fair system with
39 Fair System all evidences captured before and after the red light
jumping infraction has happened.
Lane Each camera shall cover atleast one lane having
40 Coverage width of 3.5m

41 E-Challan Integration with E-Challan system

Countdown Timer

Compliance
# Parameters Minimum Specifications or better
(Yes / No)

Make:

Model:

1 CPU MicroController

Mechanical
2
Specifications

Structural Polycarbonate strengthened against UV rays

A
Material

B Body Color Light Grey/Black

C Dimensions 360mm x 370mm x 220mm or similar

Display
3
Specification

Lamp 300mm
A
Diameter

B Digit Height 150 -165mm

C Display Type Dual Coloured (Red & Green)

D No. of Digit 3

LED
4
Specifications

A LED Diameter 5mm LED

B Viewing Angle 30°

LED Wave 630-640nm (Red), 505nm - 520nm (Blue- Green)

C
Length

Page 200 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 LED Dice AIInGap (Red), InGaN (Blue-Green)
D
Material

LED Warranty 5 years

E
period

Technical
5
Features

Power 20 - 30 Watt Per Lamp

A
Consumption

B Input Power 85-260V AC, 50Hz

Operating -20 to + 60 °C
C
Temperature

D Humidity 0% to 95% Relative Humidity

Water & Dust IP 67

E
Ingress

F Standard EN12966 Compliant

Pedestrian Lamp Heads: Signal Controller Specification:

Compliance
# Component (Yes / No)

Make:

Model:

Key Features

This pedestrian signal controller should be a 32-bit microcontroller-

1
based unit or better.

Should have GPS-based Real-Time Clock (RTC) with battery

2
backup.

3 Should have a minimum of 16 independent lamp outputs.

4 Keyboard and LCD for easy junction programming

5 Should have loop-based or Camera based detection module.

6 Should be able to operate on 12/24 VDC and 230 VAC.

Should have Ethernet- communication to have remote

7
administration and monitoring from the central computer

8 Should have a minimum of 16 programmable phases and stages

Page 201 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Should have the programmable facility for Hurry calls, week
9
plans, holiday/special day plans

Should be enclosed in IP65/67-grade box and should

10
withstand temperatures up to 60C.

Should have relevant certification like ERTL/STQC/CE/FCC etc.

11
should have minimum 5 year warranty

Page 202 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
SIGNAL LIGHTS

A. Traffic lights (RED, AMBER, and Green)

Compliance
# Component
(Yes / No)

Make:

Model:

Single Source LED type

LED retrofits should comply with the EN12368 standards or other

1
international standards

The LED signal heads are to be compliant with Class A (-15 to + 60) for
2
use in a class A environment,

3 Should have the luminosity of intensity of 400cd

Should have a medium intensity distribution, a luminous uniformity of

4
1:10

5 It should be phantom class 5

Should be impact resistance to 0.51kg dropped from a height of

6
1.3 meters.

7 The minimum working life of LEDs should be at least 18,000 hours

Should withstand temperatures ranging from 0 Degree Celsius to 70

8
Degree Celsius

9 LED retrofits used to be of low power consumption-based

10 Size 300 mm dia. Should have minimum 5 year warranty

Pedestrian Graphical Count down timer

Compliance
# Component
(Yes / No)

Make:

Model:

1 8-bit microcontroller based or better

2 Housing should be made of polycarbonate and should be IP65/67

3 Dimensions 360 mmx 370mm x 220mm or similar

Page 203 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 5 LED lifetime should be 1,00,000 Hrs. from the date of commissioning

6 Full graphic and dual-color display

The Vehicular countdown timer should be dual-color, Red for STOP or

7
STP, and Green color for GO.

8 These should have alternate Red and Balance Phase Time for STOP or

STP in flashing. Alternate Green and Balance Phase Time for GO in

9
flashing

The Pedestrian Countdown timer should be the dual color with REDMAN
10 & balance phase time in flashing and GREEN MAN & balance phase time
in flashing. Should have minimum 5 year warranty

Housing for Lights

Compliance
# Component
(Yes / No)

This is also called traffic signal aspects and should have the following
1
features

The color of the signal body and visors shall be black UV stabilized
2 high impact or impact
a. Modified Polypropylene.

It should be made of polycarbonate and should have adequate

3 mechanical strength and durability to withstand the conditions of
installation, operation, and maintenance.

4 It shall be capable of withstanding winds of up to 145 km/h.

It shall be made in such a way that it could be retrofitted with a 300

5
mm LED light in it.

Poles for Traffic Signals

Compliance
# Component Minimum Specification (Yes / No)

1 Material GI Class ‘B’ pipe

Hot Dip Galvanized after Fabrication with Silver

2 Paint coating of 86 micron as per IS:2629;Fabrication in
accordance withIS-2713 (1980)

3 5-10 Meters, as-per-requirements for

Height different types of cameras & Siteconditions

Page 204 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Pole Min. 10 cm diameter pole (bidder to choose larger
4
Diameter diameter for higher height)

Based on the location requirementsuitable size

5 cantilevers to be
Cantilevers
considered with the pole

Bottom
6 Minimum base plate of size 30x30x1.5cm
baseplate

Mounting
7 To mount CCTV cameras, Switch, etc.
facilities

All wiring must be hidden, through tubes/pipes. No

8
Pipes, Tubes wires shall be visiblefrom outside.

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
9
Foundation winds in different climaticconditions).
Expected foundation depth of min.100cms.
Please refer to earthing standardsmentioned in the
RFP

Lightning arrester at select sites as per the

10 Protection
requirements

11 Sign Board Sign board describing words such as “This area under
surveillance” (in English and Local language)

Cables for Traffic Signals

Component
# Compliance (Yes / No)

Make:

Model:

1 No’s of core 7 and 14 core1.5 sq.mm. 3 Core 2.5 sq. mm.

PVC insulated and PVC sheathed armored

2 Materials cable with the copper conductor of suitable
size as specified in BOQ.

3 Certification ISI Marked

4 Standards Indian Electricity Act and Rules

5 IS:1554 PVC insulated electric cables (heavy-duty)

Page 205 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.4.20 Automatic E Challan System:

• The proposed system is a comprehensive digital solution for Transport enforcement wing
and Traffic Police delivered through an Android based mobile application and a web portal.
The system will capture all challans information by infield officer using

mobile device at the time of violation and capture information will be sync to centralized
server.
• The system will be integrated with Vahan and Sarathi applications and provides several
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
Transport department and improved support in maintaining compliance for citizens should
be considered.
• The system will self-analyze the confidence level of the ANPR conversion. In case the
confidence level is above user-configured threshold, the violation will be pushed
automatically for eChallan generation.
• It will be possible to store the e-Challans based on the functional and legal requirements
in terms of the number of days. The system will not delete the e Challans which are under
legal or court procedure. The system will have postal record maintenance facility to keep
track of dispatched, returned, refused, etc. e-Challans sent to the violating individuals.
The e-Challan generation system will be able to generate e-Challans in local language and
English. The Operator will have the option to filter the violations based on the following
criteria for generation of Challans:

a. Number of violations by the same vehicle multiple times

b. For a particular category (e.g., 4-wheelers) of vehicles

c. For a particular Thana / police jurisdiction

d. Paid/Unpaid Challans

e. Ageing Analysis of Pending Challans

• The system will generate end-of-the-day report of the e- Challans generated. The report
will contain the number of e-Challans generated, number of e-Challans paid,pending e-
Challans, etc. The system will have the capability to send such reports via email to the
designated persons. The system will have robust search functionality to search the
violations by violation types, date and time duration, police jurisdiction / thana, operator,
hand held device, location, vehicle number, etc. The system will generate statistical
reports in terms of bar charts based on various categories.
Page 206 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6.4.20.1 E Challan System application
# Minimum Requirements
A. General
1. E-challan software shall work in client -server mode, where all handheld devices units will
act as clients connected to the server through cellular network for data transfer. The system
should be scalable to as many required number of devices, which may be added later on,
server requirements to be calculated as per scalability for at least 500 devices initially,
which may be added later on.
2. E-challan system shall be able to retrieve vehicle owners details and vehicle data from RTO
data base to minimise data entry
3. Server should maintain log of all current devices. Any access to the system must be
recorded along with date, time, user id and IP address
4. Traffic officer should log in to the hand held device through the unique user id and pass
word or smart card issued for the purpose
5. A unique challan number should be generated through client software for each challan
6. 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 oris
in the list of suspicious vehicle
7. The most frequent traffic offences should be kept at the top in the drop down menu and
offence ingredients should be available if required by officer
8. Date, time and GPS coordinates of place of challan should be automatically populated in
the relevant fields of client software
9. Compounding amount must populate in the field automatically from master table
10. The successful bidder should develop the GUI and functionality as per requirements of the
Police
11. The GUI should be lingual i.e English and local state language
12. It should be possible to integrate payment gate way operator with the system for
felicitation of payment
B. Handheld Device Software
1 Once the application is loaded on the hand-held device there should be no possibilities to
modify the application by the user. Reloading and modifying of application should be
possible only by an administrator.
2 On switching on the hand-held device the system must give access only after validation
through user ID and password.
3 The communication between the server and hand-held device would be through
GSM/GPRS/ 3G/4G or better connectivity etc.
4 Every challan created must have a unique self-populated number.
5 The Handheld application must be able to access information from the main Server and
display upon request, pop- up tables/codes, vehicle and license details, all types of
offences, compounding amount, challan types, vehicle details, court calendar etc. in
order to minimize the typing by the prosecuting officer.
6 The Handheld device should be able to access data/ information on the basis of driving
license number, vehicle registration number etc. from the main server data relating to
previous offences.

Page 207 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
7 The hand-held application software should also suggest date of challan, place of challan,
name of the Court and court date etc. to further reduce typing by the officer. These fields
should be designed in consultation with Police.
8 When a challan is issued, the name and ID of the officer should be printed on the challan.
9 The Handheld device must be able to input and print multiple offences on the same
challan.
10 The Handheld software must validate challan fields automatically before the challan is
printed. The system must ensure that certain fields are properly completed before allowing
the challan to be printed.
11 When downloading application software or pop-up tables or lists to the Handheld, or
uploading challan records to the Server, synchronization of Handheld system must be
automatic, in order to minimize human intervention.
12 Uploading data to the Database Server should be automatic in consistent manner.
13. The application should provide features wherein when a driving license/ vehicle registration
number is entered; it should be able to pull from the server all the details relating to the
driving license holder/ vehicle owner including history of previous offences.
14 Software should capture the list of documents seized during prosecution and such list must
be reflected on the printed court challan.
15 The handheld application software shall allow the user to generate a summary report to
facilitate evaluation of his daily work.
16 Once the challan is complete and saved any further editing should not be possible unless
so authorized by administrator.
17 Each hand-held device should be provided with original printed user manual and
appropriate carry case for Handheld device with charger.
18 The application software should allow online payment
19 There should be automatic rejection of payment for the settlement of expired notices or
challans. Partial payment of an offence must not be accepted by the system.
20 The software should update DL/RC smart card with the booked offence.
C. E-Challan Application Software
1 The Application Software should work in a web based environment.
2 The application software should be user friendly, easy to operate even by police personnel
with minimum qualification of that of a head constable.
3 The software must provide comprehensive data back-up and restoration capability.
4 The system will function in web-based system where the hand-held device shall work as a
node.
5 The application software should maintain the logs of user activities to facilitate the audit
trail.
6 The system should have sufficient security features such as biometrics, password protection,
audit trail, etc.
7 The system 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.
8 The software should be able to generate various periodical reports, summaries, MIS reports,
query reply etc. as per the requirements of Police.
9 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.

Page 208 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 10 Software up-gradation must be provided from time to time as per available technology
without further cost impact to Police.
11 The Department will provide the entire data of vehicle ownership and driving license for
integration with the vendor’s application software.
12 All database tables, records etc. required for various dropdown menus etc. shall also be
created.
13 The application software is to be provided to handle various processes of the prosecution
required by the office of senior police officers, Courts etc.
14. The application software should have the capability to export records in CSV, SQL and
binary format

6.4.20.2 Challan Handheld device

Specifications Compliance
(Yes / No)
Make:
Model:
Processor : latest high speed processor min 800 MHz with suitable
operating
System
Memory : 512MB RAM or higher, 1 GB Flash or higher,
With expandable micro SD card Capacity min 32GB
Interface : Interface : RS232, USB 2.0 Host USB 2.0 Client
Wireless : Wireless : WLAN (IEEE 802.11 b/g/n)
GSM/GPRS/EDGE/CDMA
should support 3G/4G/5G
Communication: USB 2.0, Bluetooth
Power : must last for minimum 6 hrs of use in the field (Rechargeable
battery)
suitable mechanism for charging from 220V standard
AC powersupply must be provided, Vehicle charger
also to be provided
Printing method: Width Minimum 3” Print Technology: Direct Thermal, at
least 200DPI
Print Speed: 60 mm per Second or better Easy paper
loading mechanism
Media Type: Direct Thermal Receipt Paper
Rugged Structure Drop Specification: 5 ft multiple drop
Ingress Protection: IP 65 or better
Camera 5MP Integrated Camera with flash or better

Page 209 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Display and Keypad Minimum 3.5” color VGA 640 x 480 resolution
QWERTY keypad with long life buttons, touch screen
with backlight, must also have option for virtual
QWERTY keypad andshould be readable in sunlight.
Indications suitable indication on device for charging, low battery,
connectivity etc
Operating Operating Conditions: Temperature (0 – 50 deg C) 5 – 95%
Conditions: RH (Non condensing)
Dimensions and Lightweight and should be easy to hold in the palm
Weight:
Storage expandable micro-SD card capacity min 32GB
Global positioning Integrated GPS with A-GPS
System (GPS)
Other Features login through unique ID, password and biometric
data captureReal time clock with Battery backup
Embedded e-challan Software
e-challan Application: - Required device client software
should be developed and installed on each device by
the vendor to perform E-challan process on line and off
line mode with server as per user requirement.
Operating System and application drivers: -
Suitable operating system.

Accessories User manual , Device cover casing , USB Cable and e-

challan Software CD.
Reader Contact & Contactless Smart Card Reader and MSR
reader, Fingerprint scanner, Integrated Bar Code Reader
(1D/ 2D)
Payment Interface The device should have lPCI , EMV certified PINPAD as per
RBI guideline for accepting payment through Credit / Debit
card/NPCI
Warranty 5 Years

6.5 Enterprise Management System (EMS)

Page 210 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Sl. Compliance (Yes
Technical Specification
No / No)
Make· <to be provided by the SI>
Model: <to be provided by the SI>
Complete end to end fault & Performance monitoring
1. Fault & Performance Monitoring (Network, Server, Cloud, VMs, CCTV, Wi-Fi, all IP
network)
2. Network configuration & Change management
3. Traffic analysis
1 4. Assets Management
5. Log management
6. Network zero trust Access
7. Reporting & Dashboarding with integration
8. Helpdesk ITSM Tool
9. IPAM (IP Address Management)
2 The OEM should have a support center in INDIA
3 The solution should be capable of running in Linux platform
The tool must be certified by PinkVerify or equivalent for ITIL v3 on incident management,
4 change management and availability management processes and certificate must be
provided when sought
The solution should have dual-stack IP support (support both IPv4 and IPv6) and should be
5 completely vendor-agnostic in nature to be able to monitor a multi- vendor environment
The solution should be a unified system which can monitor networks, servers, apps and any IT
or Non-IT Communicable device (ex.: RF device, etc.)
6
The solution should be completely multi-tenant where in every module and system being used
can be assigned to a specific set of users or a group of users.
7
The system should be capable to retrieve and show fault, performance , inventory and SLA
data in a single dynamic view with option to export the views into PDF, Word, Excel, HTML
etc. formats depending on the need. System should have capability to add any additional
8
information about the nodes via custom fields.

Page 211 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 System should have Node Tags for device grouping and resource/interface tagging for element
9 grouping. Apart from Node Tags additionally system should have options to do device grouping
based on default fields and customer fields
Provides the option to have the portal account to the end customers with restricted views limits to
10 their specific infrastructure. System should have the capability to be implement in DMZ and non-
DMZ zone with adequate security.
11 Tool must provide Role based Access Control option
The system should have an integrated ITSM tool from the same OEM. In future, it should be
possible to use the service management features like Incident Logging, Viewing, Assignment,
12
Escalation, Reporting, SLA Management etc. in the Service Manager tool GUI. The integration
should be bi-directional in nature.
Tool must provide intelligent Email-to-Incident feature in which tool admin has the option to allow
certain domains for automatic conversion of emails to tickets. Tool should merge all subsequent
email communication for a particular email-to- incident ticket into the same ticket in the form of
13 a message thread. Tool should be intelligent enough to understand email conversation chains for
merging emails to a particular incidnt. Merging logic should be not only based on TicketID but also
on
email sender, cc responses to that email chain
Tool should be able to provide real-time Email, SMS Notification alerts to notify respective users
about any changes in ticket state and status. Tool should provide Email Communication Interface
14 to allow technicians to send replies to customers / end users from the tool GUI and Record all
the Email Communication in Chronological Order
15 The integrated ITSM module should have its own Android & IOS app
System should have a bi-directional integrated NCCM tool with option to use NCCM features in
future easily by enabling the license for it without having to do any additional installations. The
16 integration should allow assets and topology to sync
from the NMS module to the NCCM features for helping in Root-Cause-Analysis of faults
System should have option for multiple options for discovery including IP address based discovery,
IP address range discovery, CSV based discovery for bulk discovery and it should allow options
17
to add custom fields to support customer specific data to upload during discovery
The system should fetch topology via SNMP for ARP tables from routers , MAC tables from layer 2
switches, cisco Discovery Protocol, Link Layer Discovery Protocol,
18
Foundry Discovery Protocol or SynOptics Network Management Protocol. The discovery should be
automated and continuous.
Discovery has to work intelligently by identifying the device in the network by the given IP range
19 and categorize into network devices and servers with vendor and model details.

Automatically learn devices that supports SNMP, HTTP, Ping, SMTP, POP3, WMI,JMX,SOAP, REST
20 API,PDC, SSH and Telnet along with any required protocol to communicate to the devices.

System should support global threshold and it should have option to define individual
21
resource/interface statistics level threshold
System should have built in self learning algorithms to auto baseline and auto calculate thresholds
22 of components or nodes to enable tool admin to start the monitoring with zero threshold
configurations
Configurable parameters like frequency, data duration, resolution duration, sigma based polarity
23
value, reset points should be available
All thresholds should have set point , reset point, polarity , set point message and reset point
24
message for ease of use.
Detect & highlight faults (abnormal situations) in near real-time occurring anywhere within the
25
monitored IT Infrastructure

Page 212 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Provides Filtering, De-duplication, Holding, Suppression and Correlation capability to let user
26 focus on the critical event that affects the business and business processes

Provides multi-level (preferably six-level) Severity definition, will handle events automatically and
27
inform the designated person as per operational requirement
System should support separate Rule Engine based alarms apart from the generic threshold.
a. Should have capability to configure Device Group based, Node Based,
Resources/Interface based, Aggregation link based.
b. On Selection of Nodes/Resources/Aggregation links it have flexibility to filter based on
fields available in node information
c. Rules should have option to apply configuration on top of performance value or based on
configured threshold alarms
28 d. Rules should have option configure the breach based on min, max and average values
e. Should have option to configure rules n repeat counters
f. Should have options to select custom alarm and clear alarm messages for individual
configured rules
g. Should have option to send severity levels like error, warning and information
h. Notifications support based on configured rules

29 Provides alarm suppression with hold time and aid in prevention of flooding
Sends alert via E-mail, SMS, Execute Batch file, SNMP Trap, XML notification, Pop-up window and
30
Audio alert
Monitors all traffic from all the interfaces of the network device. Provides traffic Utilization based
on individual interface level, nodes level or based on the group by location, branch,
31
departments etc.… as an Avg, Min and Max bandwidth, utilization, throughput or any custom
monitoring parameters.
Provision to change the polling interval to any frequency depending on the priority till the
individual component / resource level like each interface might have the different polling
32
interval in the same device based of the criticality and importance of service customer

System should have capability to configure business , non-business hours or custom time polling.
33 These configuration should be available for every device as well as every component in the
device.
34 Provision to disable and enable the polling of specific type of devices
System should have capability to configure the maintenance period for any device. When device
35 is in maintenance period there is no polling done and the SLA clock on the device is stopped.

SLA calculation / Isolation report should be made with the consideration of both the Primary and
Secondary link together instead of individual link based. The downtime calculation will be
36 measured when both the links are down for internal reporting and link based for ISP reporting.
System should provide the flexible configuration in UI itself based on user needs

Provide a notification mechanism that allows administrator to define what

37 notification channel to be used in different time of days, and able to trigger multiple notifications
to alert multiple person and actions
Provide standard reports that display current status of nodes and interfaces. Reports could be
viewed on daily graph (5 minute average), weekly graph (1 hour average minute average),
38
monthly graph (1 hour average) and yearly graph (1 day average)

Page 213 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Provide online and offline reports that allow the user to view the present usage of their devices.
Reports generates should be exportable in the format of HTML, PDF, Excel and CSV. Allows end-
39 users to browse all reports using any web browser like Internet Explorer, Mozilla Firefox, Google
Chrome etc. without the need to install any
report specific software

Automatically generate daily reports that provide a summary of the IT Infrastructure as well as
40 custom Reports and that are automatically sent by email at a pre- defined schedule to any
recipient or save into any specific folder or drive.
41 Supports instant diagnosis of the node status through Ping, Telnet and SNMPwalk
Support Real-Time report generation for checking continuous reachability of target device
42
System should provide many different types of topology representation. To perform the following:
1. Display physical connections of the different devices being monitored in the system
2. Display flat maps of the entire network or networks in a single view
43 3. Display customer maps based on user configurations
4. Display maps based on geo locations

Automatically learn IP Networks and their segments, LANs, hosts, switches, routers, firewalls etc.
44
and to establish the connections and to correlate
45 Provides provision to draw & map user specific network diagram
The tool should have Integrated Web based feature to build Network Diagram, No separate client
46 window to configure network Diagram. The builder should be similar to MS Visio with all pre-
loaded shapes and icons.
It should be a Drag & Drop based Network Diagram builder, Dynamically Upload Images,
47 Customizable objects to support multiple vendors, capability to export maps in an XML
format and upload to any other system.
Panel View
a. Panel view should look similar to the actual device front panel
b. System should automatically detect the device model display the right panel without
48
any additional configuration
c. Panel should show all the monitored interface with status
d. Fan status with live fan icon and LED status for power
Tool should have complete inventory information of the assets discovered along with an option
49
to fetch the target network device EoL / EoS information if required
Tool must support CLI-based network device configuration snapshot management including
backup of configuration files, traffic logs, messages etc. , pushing configuration files to target
50
network devices, with option to perform remote
firmware upgrades.
The configuration changes to be done on target network devices must follow an approval-
based system wherein changes can be performed only after required approvals are
51 passed. Tool must have in-built approval mechanism along with option to integrate with
Change Management module of other ITSM tools for the approval process.

Tool must provide option for target CLI-based network device vulnerability detection based on
their model number and firmware version. It should also provide options to remedy the
52
vulnerabilities with help of pre-configured scripts for certain vulnearbility types.

Tool must provide option to perform standard compliance checks like PCI-DSS, NIST, DISA
53
etc. across all target CLI-based network devices

Page 214 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Tool must provide an option for taking remote access via Telnet / SSH to target CLI- based
Network Devices with an option to record all sessions to capture all commands being
executed on the remote devices. The tool must allow session relay wherein a higher-
54 privileged user can view the ongoing CLI session of a lower- privileged user in real-time from
the tool GUI. The sessions should be saved for historical analysis with flexible filter options like
searching for sessions in which a particular command has been executed.

The proposed monitoring solution should be able to monitor network traffic by capturing flow
55 data from network devices, including Netflow v5 or v9, J-Flow, IPFIX, sFlow, NetStream data and
also sampled Netflow data. Solution must be able to

store ALL flows without any rollups or loss for retention period - for security and audit purposes.

Should identify which users, applications, protocols, countries, AS numbers, top routers,
56
and top interfaces are consuming the most bandwidth
System should have capability to alternatively capture traffic data via packet capture.
57
Should be able to associate traffic coming from different sources to application names
58
Should be able to receive flows from non-SNMP-enabled devices, like VMware vSwitch
59
Should monitor Type of Service (ToS), Differentiated Services Codepoint (DSCP), and Per-Hop
60
Behavior (PHB),BGP AS and NEXT HOP
Should provide flow analysis with 1-minute granularity and The solution should be able to
61 monitor up to 5 million flows per second, and should employs advanced
optimization methods
Tool should allow QoS monitoring of WAN links across multiple technologies like IPSLA, RPM, NQA
62
etc. across multiple protocols like HTTP, TCP, FTP, DNS etc.
QoS paramters should include link response time, link-level latency, link-level packet loss,
63
link-level jitter, Round-Trip-Time etc.
Should monitor Class-Based Quality of Service (CBQoS) to find out if traffic prioritization policies
64 are effective and if business-critical applications have network traffic priority. Should also
support CBQoS Nested policies
Tool should have option to collect and store system logs from target devices including
65
firewalls, routers, switches, WLC, servers, applications & databases
Tool should have multiple filtering options for incoming system logs based on target device,
66
log_ID, severity, level, message, OS type, application / database etc.
67 Tool should have option to export specific syslog messages to users via email / SMS
System should support VM, Hypervisor and Cluster monitoring from different vendors like VMWare,
68
Citrix, Nutanix, Linux etc.
System licensing should be based only on Physical Hosts and not charge separately for
69
individual guest VMs running on VM Hosts
System show have capability to monitor availability and performance of industry standard web
server like IIS / Tomcat / Apache / Jboss, email server like Exchange
70
/ Zimbra / Lotus Notes, and databases like Oracle / MSSQL / MySQL / PostgreSQL etc.

System show have capability to monitor HTTP service,HTTPS service,FTP server statistics,
71 POP/SMTP services,ICMP services or any customer specific port based systems

Cover geographically distributed networks through multi-level scalable distributed deployment

72
architecture
73 Ability to add new pollers at no extra cost.

Page 215 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The tool should have option to be deployed in HA mode (High Availability) for redundancy
74
purpose
Integration should provide the option in both north as well as south bound integration on
each module level. Any fault details should be able to send to third party CRM, Customer
75
Portal, UNMS or even EMS if needed using the Trap, XML and even direct database query
integration
Provide open APIs in the system which can be used by customers for integrating their own
systems. Integration should provide the option in both north as well as south bound integration
using multiple options like RestAPI, XML, SOAP, Corba etc. on each module level. Any fault
76
details should be able to send to third party CRM, Customer Portal, UNMS or even EMS if
needed using the Trap, XML and even direct database query integration

The system should allow remote access to the internal network via a Zero Trust system and
77
no use of VPN or agents.

Only specific protocols like SSH, RDP, Telnet , VNC which are essential for remote access should
78
be allowed
All the actions taken during the remote access should be recorded and have ability to
79
audit them later.
All remote access should be authenticated and all devices a user has access should be
80
pre-allocated
The system should have ability to authenticate access to any device via Single sign on and
81
password should not be exposed to users
All CLI session should have command control, any command that is not authorized cannot be
82
used and session should be terminated
Administrator should be able to view the live session of any ongoing session and can
83
terminate them also
Any file being transferred should be via the Zero trust system. File will be scanned for virus and
84
only then be transferred to the target location
85 Time based; temporary users should be configurable in the system
IPAM solution should have complete IP discovery, IP management with historical tracking
86
87 IPAM should have IP Grouping, Subgrouping and role and privileged based access.
88 Support both IPv4 and V6 along with IP Classes and VLSM based

Page 216 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.5 6.6 Citizen Engagement System : Creation of Online and Mobile Applications

SMART captures the important attributes of Good Governance i.e., Simple, Measurable,
Accountable, Responsive and Transparent governance.

ICT in governance has been experienced in the form of e-Governance, which redefined theway
Governments work, share information, engage citizens and deliver services to external and
internal clients for the benefit of both government and the clients that they serve.

Governments harnesses information technologies to reach out to citizens, business, and otherarms
of the government to: a)Improve delivery of services to citizens, businesses and employees
b) Engage citizens in the process of governance through interaction c) Empowercitizens through
access to knowledge and information and d) Make the working of the government more
efficient and effective

This results in enhanced transparency, convenience and empowerment; less corruption;

revenue growth; and cost reduction.

Authority intends to implement a robust Smart governance & citizen services solution for
delivering efficient and effective citizen centric services as well as improving municipal
finance/expense management and administrative functions.

The Smart governance solution, while modular, should be capable of providing all the
functionality described in this section as an integrated platform.

The SI shall ensure that all the modules under Smart Governance are integrated with the
overall project. SI shall create an enabling platform to link the relevant features with the Citizen
Services.

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
solution should comply to the below standards as applicable:

Page 217 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
(a) At least comply with the published e-Governance standards, frameworks, policies and
guidelines available on http://egovstandards.gov.in (updated from time-to-time); and

(b) The Smart governance solution shall be of leading industry standards and as per
requirements mentioned in IS 18006 (Municipal Governance Reference Architecture).

Shall comply to applicable elements of data layer reference architecture (IS 18002) as well
as IS 18000 (UNIFIED DIGITAL INFRASTRUCTURE – ICT REFERENCE ARCHITECTURE (UDI-
ICTRA), Section 8

Should build an integrated Collaboration Platform to provide all citizens services on a single
platform. Services that are universally accessible and that follow an international standard for
accessibility and operational or to be made operational by other Government or approved
agencies shall be made available through the CCP. Citizen engagement and Grievance
Redressal Management Systems with back-end workflow.

The principal objective of CCP is to create one all-inclusive system which allows citizens /
tourists/ visitors/ stakeholders to access various government services and information. Key
functionalities of CCP include:

• Improving delivery of services to citizen and tourists, businesses and employees

• Engaging citizens/ stakeholders in the process of governance
• Empowering citizens/ stakeholders through access to information
• Improving government functioning across departments – making it more efficient and
effective The envisaged benefits post implementation of CCP include enhanced
transparency and accountability, increased revenue, reduced cost, empowerment of
citizen and lesser time for service delivery, ease of multi departmental operations for a
cause.

By implementing CCP following benefits are envisaged, For

City Authorities

• Digital portfolio of city services

• Better citizen connect
• Efficient and effective delivery of citizen services
• Creating positive social impact
• Reduced cost of delivery of services for Citizens
• 24*7 Service Access
• Time saving
• Improved connect with city authorities
• 24*7 information dissemination
• Multiple services on a single platform
• Chatbot

The principal objective of CCP is to create one all-inclusive system which allows citizens /
tourists/ visitors/ stakeholders to access various government services and information. Key
functionalities of CCP include:
Page 218 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• Improving delivery of services to citizen and tourists, businesses and employees
• Engaging citizens/ stakeholders in the process of governance
• Empowering citizens/ stakeholders through access to information
• Improving government functioning across departments – making it more efficient and
effective

The envisaged benefits post implementation of CCP include enhanced transparency and
accountability, increased revenue, reduced cost, empowerment of citizen and lesser time for
service delivery, ease of multi departmental operations for a cause.

Key Functional Requirements - Collaboration Platform

City Collaboration platform should provide below information in the form of Audio/ Video/
image/ GIS map/ text.

• “About Puducherry” will provide details about Puducherry city and will have dedicated
sections for about the city, history of Puducherry, how to reach, climate, local cuisines,
festivals, Important Business locations, places of interest, art and craft, facts at a glance,
where to stay, where to eat, places of interest, heritage spots, weekend getaways, places
to visit, best time to visit, gallery (Photos & videos), etc. few of these points have been
elaborated below in detail.
• “Explore City” giving details about the city, history, how to reach, cuisine, festivals,
Important Business locations, places of interest, Beaches, art and craft (Add to Favorite,
Get Directions, About, get there nearby and each linked with City GIS Map and Photos of
concerned location)
• “Facts at a Glance” giving details about area, population, religion, linking roads, postal
code, longitude, latitude, area, altitude, population, literacy rate, STD code, average
rainfall, villages, language and the different seasons and reasons to visit.
• “Tourism destination” giving details on tourism experience (Add to Favourite, Get
Directions/Driving Directions, About, get there nearby and each linked with City GIS Map
and Photos of concerned location) heritage spots, pilgrim destination, nature discovery,
heritage, highway, adventure spots, Beaches, Nearby places to visit, Places to Stay etc.
• City Collaboration Platform will provide the web-link of Tourism Development Corporation
(PTDC) portal for booking the Puducherry State tourism packages.
• City has many artifacts, memoirs and items with historic perspectives and are available in
designated markets in and around the many important places of interest in the city. A list
of unique memoirs and the connected stores are to be listed through mobile apps showing
distances from current location, etc.
• “Cultural events calendar” section will provide the list of cultural events within city
including dates, venues and details of the event.
• “Tenders” will provide the list of PSCDL tenders in downloadable format.
• “Key Personnel-staff directory” will have the details (such as emails, contact information,
designation, job profile, office address etc.) of PSCDL stakeholder members, Elected
Political Members, Mayor, Municipal Commissioner and all Officials
• “Important GOs / Policies” section will have the list of all important and relevant
government orders and policies.
• “Downloads” section will provide the list of important document in downloaded format to
the user.
• “Recruitment” section will provide the current job openings in PSCDL and their
stakeholders departments.
• “Educational Institutions” listings, including location, contacts, courses etc.
• “Sports Facilities” will provide the details of facilities available within the city including list
of play grounds, details on in-door or out-door facilities, list of tournament / event dates
etc. Please note that this section will provide only information.
• “Ward Information” section will provide the below information:
Page 219 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
- Municipal officers contact.
- Water supply information / announcements.
- Power supply information / announcements.
- Garbage collection schedule.

List of schools, community centres, playing ground, parks etc. and the contacts for
bookings.

• “Health Services” will provide the details of hospitals including contacts, address,
emergency contacts, available facilities and OPD timings. It will also provide the list of
ambulance services available in the city with contact numbers.
• “Emergency Services” module will have the contact details of below emergency services.
- Ambulance
- Fire
- Police
- Traffic
All the contacts shall support for “dial to call feature” from a page.

• “Social Networking & City-wide Collaboration” will help citizens to communicate through social
networking platform such as Twitter / Facebook / WhatsApp etc.

- Current news, events will enable citizens to get live feeds of various activities & events in the
city.
- Feedback/ inputs / opinions will help citizens to collaborate and provide inputs/ opinions on
various policy related aspects, local governance aspects, feedback on specific issues etc.
- Search tools will enables citizens / tourists to search for desired information available in the
City Collaboration Platform.

Collaboration platform should be integrated with below modules but not limited below list.

- Environment information from nearest available Environment sensor.

- Citizen / Tourists can view their e-challan in case of any traffic violation.
- Integration with Property Tax System
- Water Supply and sewerage system
- Birth and Death, Marriage Registration, Trade Licensing etc.

Key Functional Requirements - Collaboration Platform

Sl. Compliance
Specifications
No. (Yes / No)

Citizen Engagement Application

The application shall accept requests or inquiries from the

citizens and track those requests from different channels such
1 as phone, e-mail, SMS, Web Portal, Chatbot, VoIP Call, Smart
Phone Application (City App) & social media (Facebook,
Twitter.) etc.

Page 220 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 It should integrate all service requests through Voice & IVR
2 based system for efficiently managing the citizen grievance
request

The operator should be able to chat/reply to any queries

3
raised through different channels via the same channel

The application shall allow the user to select service request

category type or use auto-filled information for incident
4
creation. A unique service transaction number should be
assigned for each incident after a service request is created.

The application shall auto-populate fields based on previous

5
calls or known data from other channels.

The application shall capture different types of input data,

including but not limited to: date, citizen profile data, issue
6
type, issue description, time of day the grievance occurred,
location, etc.

The platform should have the ability to view map of service

requests on top of a City GIS base map and display service
7 requests and associated data (service request number, status,
short description, field assets and workforce) on the same
map.

The application should provide information regarding the

8 exact location of the service request (e.g., actual location of
garbage or downed tree).

The application should automatically determine duplicate

9
requests and associate a request with multiple citizens.

The application must have the ability to display the citizen's

10 previous interactions from different channels using search
feature and view citizen's previous service request status.

The application should have the ability to display "top"

11 grievance types based on historical trends ranked according
to the most viewed and most relevant service request.

The application should provide the operator the ability to view

12 and attach files (such as PDF) and other documents (e.g.,
images)

The application should prevent a request from being closed

13
until all associated actions are completed.

The application should have the ability to dispatch a service

14 request to the workforce, a particular department or an
outside agency.

The application should provide a set of standard reports that

15 will provide statistical reporting for open, closed, escalated,
priority, completion time, based on address and location.

Page 221 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The application should have a dashboard module that can
give a quick and easy view to know overall Grievance details:
16
trend, status, channels, incident trends, response of
department and feedback.

The application should provide the dispatch the incident to

City Command Centre, City Emergency Operation Centre,
17
relevant department application based on the nature of the
grievance/complaint.

The application should provide the operator with the facility

18
to view all dialled, missed, received calls.

The application should allow the administrator to define SLAs

19
for all the incidents.

The application should allow the administrator to add, edit

20
and delete various department

Citizen Mobile App

It shall integrate the Citizen Service request and also provide

21
visibility to the citizen of the various city notifications.

22 Key Features of the app should include:

23 • Incident Reporting

24 • Complaints Tracking

25 • City Services – Parking, Transport

26 • e-Governance Services

27 • Bills Payment

28 • News

29 • Events

30 • Notifications

31 • Emergency

32 • Chatbot

The Application shall integrate Citizen Grievance and

Compliant from various channels – social media through
33
Keywords, Mobile App based reporting as a crowd source,
Citizen Calls, etc.

Citizen app shall provide capability to citizen to report

incidents across various grievances covering emergency,
garbage collection, accidents, water leakage, electricity
34
outage etc. Such requests shall be integrated with ICCC
platform, and the service delivery will be automated through
the ICCC functions.

Page 222 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 City App should allow to make SOS calls with location and
35
video snapshot

City App should be capable to schedule waste collection from

36
Citizen’s location

City App should allow to search the parking space across the
37
city

City App should allow to view different modes of transport

38
available for Citizen in the city

City App should allow the citizens to receive the traffic related
39 notification and be updated about the traffic condition in
selected areas

40 City App should allow citizens to pay utility bills and taxes

City Web Portal

It should provide a single view to the citizen for engaging with

41
the city departments.

It should provide live update of the City Service and also act
42 as a foundation for Citizen to register the identity and
download the Citizen App.

It should also provide interface for the citizen to request

43 through Email, Chat Services so that the citizen can also call
for service through these channels.

Email and chat services: service request and distribution to the

44
right operators.

Portal should allow citizen to use different City services by

45
selecting services categories

The Web portal should provide the citizen the facility to report
Civic grievances by selecting grievance categories and
46
subcategories by attaching Image or Video to support the
Grievance request

The citizen can view the history and status of all the
47
complaints that have been requested.

The Citizen should be able to see the GIS view of the city and
48
can find POIs as when required

The web portal should have Content Management System to

49 create content and publish content and it will integrate with
all public Channels for News and other feeds.

The web portal should have CMS that shall provide a role-
based user access mechanism where an administrator can
50
create and manage users, user groups, roles, and role
permissions.

Page 223 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The CMS should support login module using which content
51
authors will be able to login.

Login module should have forgot password mechanism. In

case user forgets the password/wish to reset a link should be
52
sent to user’s registered Email address from where password
can be reset.

CMS should support integration with Directory Services

53 (supporting LDAP) to manage users and their preferences.
CMS should also support latest security certificates like SSL 3.0

CMS should be able to publish content to any external portal

54
apart from its native portal

CMS shall support the creation, modification, and deletion of

55 templates to enable easy management of site and page
layout and navigation

CMS should contain a WYSIWYG editor and provide standard

Word authoring features (also known as a Rich Text Editor) to
56 enable an editor to add and format text, links, and images to
content areas, create tabular layouts within a text area and
apply styles without needing HTML skills

CMS should support drag and drop feature to enable easy

57 management of content. The CMS shall support the following
minimum preview and publication functions: -

58 a) Preview only on CMS (not visible to users)

59 b) Save as unpublished (draft)

60 c) Preview on Portal

61 d) Send for approval

62 e) Approve

f) Publish after approval (i.e., after successful completion of

63
the approval workflow)

64 g) Unpublish (save as unpublished, not visible to users)

65 h) Publication scheduling

66 i) Publication expiration date (automatic unpublish)

CMS shall contain a content approval workflow to enable the

67 approval of modifications (create, modify, delete) before
publication (i.e., before becoming visible to the public)

CMS shall support Administrator (or a designated user with an

68 appropriate permission level) to assign and reassign users to
workflow tasks (i.e., define the targets within the workflow)

Page 224 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 CMS shall support the creation and application of styles using
Cascading Style Sheets (CSS) enabling the swift alteration of
the look and feel (colour, font, image size and positioning, link
69 attributes, table properties). Graphics should be avoided
altogether regarding navigation (e.g., no navigation buttons -
these should be text, which gets its look and feel through
CSS).

CMS shall include a social media integration module that

allows configurable publishing of content (pages, interactive
data visualizations, images, videos) to a variety of social
70
media (Facebook, Twitter, Google+, LinkedIn, Pinterest,
Tumblr, etc. CMS should also support publishing of content
specific to mobile app if required

The CMS should have the capability to create and deploy

71
content on different portals with same or different branding

72 The CMS shall support the Unicode character set (UTF-8)

6.7 Smart Poles Proposed

ICT Solution:

It is now proposed to install smart poles in different locations of the city which shall be in turn
connected to the ICCC. The various components that are envisaged in the said smart poles are as
follows:

• Fixed Box Camera

• Smart Lighting
• AQM : (Environmental Sensor, Weather Sensors, Rain Gauge Sensors )
• Public Address System
• Digital Bill Board
• Emergency call box
• Wi-Fi
• 5 G ready

Scope of work:
The scope includes procure, supply, install and commission smart poles including allcivil
foundation works and provide the data and power connectivity for the said poles.

Page 225 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.7.1 Smart Pole Specification

Compliance (Yes
No Specification
/ No)

Make:

Model:

Smart pole should be able to meet city aesthetic requirement

1. and it should visually appealing. It should easily blend-in into city
street pole master plan.

Pole Height requirement is 12-15 meters. TRAI and DOT

2. guidelines to be followed as the pole will be used as a telecom
site.

It should be able to support telecom technologies like 5G, GSM,

3.
WCDMA, LTE and Wi-Fi.

It should be possible to support LED luminaries from reputed

4.
OEMs.

Smart pole should be designed as per telecom standards of

5. India and specifically Puducherry weather conditions such as
wind speed, climate, aesthetic.

The allowed diameter will be as per the BIS regulations and wind
7.
speed requirement

All cabling, cooling/heating etc should either be via/inside the

8. pole or should be camouflaged (aesthetically concealed) so
that it is not visible from outside.

The minimum power backup requirement is 1 hrs for all

11.
equipment

It should be possible to provide multiple color options as asked

12.
by city Authority as per city light pole colors

It should be possible to house radio units with integrated

antenna, MW /optical transmission unit, SMPS (AC to DC
13. convertor), batteries, controllers, power distribution etc. either
inside the smart pole or should be camouflaged (aesthetically
concealed) so that it is not visible from outside

It should be possible to provide light connection in daisy chain

15.
with separate MCB for lighting

The cabinet where electrical electronics equipment is store

20.
should be IP 67 compliance or better

22. The ambient temperature requirement is 0-50 degrees

Page 226 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The overall power budget for smart pole should not exceed
23.
2KW ( lights) or as per standards.

It should support minimum two light arm per smart pole.

24. However, the same may vary depending on location to be
surveyed and finalized by the selected bidder.

The minimum life requirement of above smart pole structure is

25.
10 years

The Concessionaire should not use any banned /restricted

26.
material as per Indian regulations. Should have 5 year warranty

6.7.2 Anti-Climb Galvanized Poles for Mounting Camera etc.

S.N. Parameter Minimum Specifications

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. 10cm diameter pole (SI 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 300mmx300mmx15mm
(or) 30cmx30cmx1.5cm
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
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.7.3 Digital Bill Board

No Specification

The Bill boards should be hanged at the height of at least 5 meters or above,
1 however the uniformity should be maintained on all the poles. Should have
minimum 5 year warranty

Page 227 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 2 The Smart Billboard will be operated from Command & Control Center

3 It should have provision for incoming power input cables and fiber connectivity

4
It should be Vandal Proof ; IP Level IP67 or better

5 It should have display of minimum (80 Inches +/- 5%) , Rectangular shape (2mx1m
)+/- 5% as per city regulations.

No Specification

6 It should be Aesthetical & Camouflaged finish with respect to environment

Pixel Pitch 10 mm or Lower, Lower pixel pitch is better, LED Configuration RGB 3 in
7
1 SMD

8 Pixel Density Minimum 10,000 pixels per sqm or higher

Viewing distance Suitable for readability from 40 Mtrs. or more at the character
9
size of 240mm, from moving vehicles

10 Viewing Angle H 140 deg / V 90 deg or better with Refresh Rate>1920 Hz or better

11 Temp Range 0 to +50 Degrees C or better; Gray Scale Processing 12 Bit or better

12 Brightness (Calibrated) 5000 cd/m2 or better; Contrast Ratio 2500:1 or better

13 Maximum Power Consumption 825 w/sqm or lower; Power Input 100 ~ 240 VAC

Dimming Capability Auto dimming capability to adjust to ambient light level

14
(sensor based automatic control)

6.7.4 Environmental Sensors

Environmental pollution, particularly of the air, is nowadays a major problem that

unknowingly affects lives in the cities. Air Pollution is defined as the presence of contaminants
or pollutant substances in the air that Interfere with human health or welfare, or produce
other harmful environmental effects and it is important that the citizens know of the air that
they breathe.

Citizens & visitors to City can enjoy unique experiences that keep them feeling good by
knowing city’s environment condition at different locations.

Environmental Management solutions can be used to determine the quality of air (And water,
SWM, Energy,) and the environmental parameters to enable a deeper understanding of the
polluting sources like vehicles, industries, construction or natural reasons etc.

It is recommended to deploy Environment Sensing Units spread across a region, to create a

larger data pool leading to better understanding of spatial and temporal trends in air pollution
to take measures for corrective actions.
Page 228 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Key Issues

Rapid urbanization, which strains basic infrastructure, coupled with more frequent and
extreme weather events linked to global climate change is exacerbating the impact of
environmental threats. Common environmental threats include flooding, tropical cyclones (to
which coastal cities are particularly vulnerable), heat waves and epidemics.

Owing to the physical and population density of cities, such threats often result in both
devastating financial loss and deaths. Making cities more resilient against these
environmental threats is one of the biggest challenges faced by city authorities and requires
urgent attention.
Indicative Key Outcomes and KPIs

• Improved monitoring of city environmental Parameters

• Temperature, Humidity
• Ambient Light
• Level of Noise Pollution
• CO, NO2.
• Water quality of public surface water bodies
• City to add/ update based on city objective.
• Improved communication with citizens through other city solutions like City App, PA
system, ECB etc. based on city environmental parameters
• Improved management of pandemic situations in the city

Key components

A typical Environment Management solution may consist of the following components. One
may not need all of these or may be even more than these based on the technology and
design used.

Sensors to measure the pollutants and other environmental parameters

Electronic displays to communicate the measured levels to the citizens

IoT gateways, network switches, copper, fiber optic or wireless connectivity to interconnect
the local system components and also to the datacenter/cloud.

Desktop application for administration, operation and service/repair.

Functional Requirements

The SI shall;

a) Install environment sensors (as per the functional requirement) to display environment
related information at various strategic locations through variable message display (VMD)
system.
b) The environment sensors shall be integrated with the ICCC to capture and display/ provide
feed on Temperature, Humidity, Pollutants like So[X], No[X], Co[X], PM2.5, PM10, Noise
Pollution, etc. The data it collects should be location-marked.
c) Various environment sensors should sense the prevailing environment conditions and send
the data to the ICCC where real time data resides and the same shall be made available

Page 229 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 to various other departments and applications for decision making.
d) This information should be relayed instantaneously to signage – large, clear, digital-
display screens which let citizens know regarding the prevalent environmental conditions.
e) Environmental sensors recorded data shall be used by Smart Environment Mobile
application to enable user for alarm management and notification of environmental details
on real time basis.
f) Mobile app should be developed for Grievance Redressal of Citizen – where citizen can
take the picture, upload the same with Geo Tagging. The complaint should be
automatically forwarded to the respective staff, with escalation within specified timelines
supported with multilingual text to speech, speech to text and speech to speech systems.

g) The system should provide ability to ;

i. View Air Quality Index across city, levels of various constituents (CO, CO2,SO2,NO2,
PM10) etc.
ii. Correlate the data emanating from various Environmental sensors in different areas of city
with respect to city mobility/traffic
iii. Communicate the levels of AQI and Noise in locality to citizens, businesses and industry
on daily basis via Citizen Mobile App.
iv. View the hotspots across various areas in city where high noise cases are reported by
citizens
v. Predict the poor quality of air and water on various dimensions like timelines, seasons
where there is high density of markets, industry or shops.
vi. Spread awareness at chronic location/spots identified over VMD, website, mobile app,
WhatsApp etc.
vii. Allocate and monitor noise complaint to the on-field squad to take intervention as per
defined SoPs.
viii. View the heat-map of noise pollution over different dimensions
ix. Educate the masses using bulk SMS, email and messages about best practices
x. Send the aggregated data of AQI and Noise to concerned authority to address the
problems through policy.
xi. Address the noise issue by issuing advisory to local businesses, marriage gardens etc.
xii. View hospitals and staff/beds/medicine availability in real time.
xiii. Provide City wide Hot-Spot Analysis based on lab reports.
xiv. Correlate cause like the impact of water quality, air quality, stress on diseases reported
at primary, secondary and tertiary care.
xv. Do the predictive analytics over the past data to predict the outbreak of disease in
community
xvi. Coordinate with Hospitals, Labs and on-field staff in real time using handheld devices etc.
Ability to coordinate with Hospitals, Labs and on-field staff in real time using handheld
devices etc.
xvii. View heat-map of different diseases on different dimensions over city maps
xviii. Provide awareness drive for citizens in targeted areas through email, SMS, WhatsApp,
VMD etc. as per preventive healthcare SoPs
xix. Coordinate with Sanitation Department and other line department to take corrective
action.

Page 230 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Install environment sensors (as per the functional requirement) to display environment
related information at various strategic locations through variable message system

● The environment sensors shall be integrated with the ICCC to capture and display/
provide feed on Temperature, Humidity, Pollutants like SoX, NoX, CoX, etc PM2.5, PM10,
Noise Pollution. The data it collects is location-marked.

● Various environment sensors shall sense the prevailing environment conditions and send
the data to the integrated control system where real time data resides and the same
shall be made available to various other departments and applications for decision
making.

● Then this information is relayed instantaneously to signage –large, clear, digital-display

screens which let citizens know regarding the prevalent environmental conditions.

● The data should be collected in a software platform that allows authorized software
applications to read that data. Various environment sensors shall sense the prevailing
environment conditions and send the data to the integrated control system where real
time data resides and the same shall be made available to various other departments
and applications for decision making.

● SI can also make use of the nearby Variable messaging displays wherever possible (need
to be finalized post detailed survey of locations).

● The sensor management platform should allow the configuration of the sensor to the
network and location details etc.

Functional Requirements (AQM on smart Pole and standalone Environmental Sensor)

S. No. Description Compliance

(Yes / No)
1 Shall be ruggedized enough to be deployed in open air
areas on streets and park
2 Environmental Sensor station shall be housed in a
compact environmentally rated outdoor enclosure. It shall
be an integrated module which shall monitor overall
ambient air, noise quality, weather etc.
3 Mounting of the environmental sensor module shall be co-
located on streetlight pole or shall be installed on a
tripod/standalone pole.

Page 231 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
4 Environmental sensor station shall monitor following
parameters and include the following integrated sensors
inside one station:

• Carbon Monoxide (CO) sensor

• Ozone (O3) sensor
• Nitrogen Dioxide (NO2) sensor
• Sulphur Dioxide (SO2) sensor
• Carbon Dioxide (CO2) sensor
• Particulate/SPM Profile (PM10, PM2.5, and TSP)
sensor
• Temperature sensor
• Relative Humidity sensor
• Wind Speed sensor
• Wind Direction sensor
• Rainfall sensor
• Barometric Pressure sensor and
• Noise sensor

5 Solution shall display trends of environmental parameters

based on user specific time periods.
6 Data shall be collected in a software platform that allows
third party software applications to read that data.
7 Solution shall display real time and historical data in chart
and table views for dashboard view of the Client.
8 Alarms shall be generated for events where the
environmental parameters breaches the safe or normal
levels.
9 The sensor management platform shall allow the
configuration of the sensor to the network and also
location details etc.
10 The platform shall comprise of an Industrial PC running
latest version OS and compatible software.
11 Data logging with central Monitoring System will be
through GPRS/TCP-IP from all the AQMS system and shall
have an ability to program and log channels at different
intervals and shall have a capability of averaging and
displaying real time data and averaged data over a
period of 1 min, 10 min, 30 min, 1 hr, 4 hr, 8, hr, 24 hr and so
on.
12 Real time or averaged data can be viewed quickly and
easily through a remote interface on the central
computer.
13 System shall be able to perform nested calculations vector
averaging and rolling averages
14 The platform shall have a feature for viewing
instantaneous and historical data in the form of tables and
graphs either locally or from a remote client.
15 Data retrieval from CMS via USB shall be possible.
16 Generation of reports as per requirement of customer etc.
17 Alarm annunciation of analyzer/sensor in abnormal
conditions

Page 232 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
18 The environment sensors shall be integrated with the
integrated command and control centre system to
capture and display/ provide feed. The data it collects is
location-marked.
19 Various environment sensors shall sense the prevailing
environment conditions and send the data to the
integrated control system where real time data resides
and the same shall be made available to various other
departments and applications for decision making.
20 Information shall be relayed to signage – large, clear,
digital-display screens which let citizens know regarding
the prevalent environmental conditions.
21 Further environmental sensors recorded data shall be used
by Mobile application to enable user for alarm
management and notification of environmental details on
real time basis.

Page 233 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Technical Requirements

S. No. Description Compliance(Yes/No)

1 Carbon Monoxide (CO) Sensor

• CO sensor shall measure the carbon monoxide

in ambient air
• Range of CO sensor shall be between 0 to 1000
PPM
• Resolution of CO sensor shall be 0.001 PPM or
better
• Lower detectable limit of CO sensor shall be
0.040 PPM or better
• Precision of CO sensor shall be less than 3% of
reading or better
• Linearity of CO sensor shall be less than 1% of full
scale or better
• Response time of CO sensor shall be less than 60
seconds
• Operating temperature of CO sensor shall be
0°C to 60°C
• Operating pressure of CO sensor shall be ±10%.
2 Ozone (O3) Sensor

• O3 Sensor shall measure the ozone in ambient

air
• O3 Sensor shall have a range of at least 0-1000
PPB
• Resolution of O3 sensor shall be 0.001 PPM or
better
• Lower detectable limit of O3 sensor shall be
0.001 PPM or better
• Precision of O3 sensor shall be less than 2% of
reading or better
• Linearity of O3 sensor shall be less than 1% of
full scale
• Response time of O3 sensor shall be less than
60 seconds
• Operating temperature of O3 sensor shall be
0°C to 60°C
• Operating pressure of O3 sensor shall be ±10%

Page 234 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
3 Nitrogen Dioxide (NO2) Sensor

• NO2 Sensor shall measure the Nitrogen dioxide

in ambient air
• NO2 Sensor shall have a range of at least 0-10
PPM
• Resolution of NO2 sensor shall be 0.001 PPM or
better
• Lower detectable limit of NO2 sensor shall be
0.001 PPM or better
• Precision of NO2 sensor shall be less than 3% of
reading or better
• Linearity of NO2 sensor shall be less than 1% of
full scale
• Response time of NO2 sensor shall be less than
60 seconds
• Operating temperature of NO2 sensor shall be
0°C to 60°C
• Operating pressure of NO2 sensor shall be ±10%

4 Sulphur Dioxide (SO2) Sensor

• SO2 Sensor shall measure the Sulphur dioxide in

ambient air
• SO2 Sensor shall have a range of at least 0-20
PPM
• Resolution of SO2 sensor shall be 0.001 PPM or
better
• Lower detectable limit of SO2 sensor shall be
0.009 PPM or better
• Precision of SO2 sensor shall be less than 3% of
reading or better
• Linearity of SO2 sensor shall be less than 1% of
full scale
• Response time of SO2 sensor shall be less than
60 seconds
• Operating temperature of SO2 sensor shall be
0°C to 60°C
• Operating pressure of SO2 sensor shall be ±10%

Page 235 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
5 Carbon Dioxide (CO2) Sensor

• CO2 Sensor shall measure the carbon dioxide

in ambient air
• CO2 Sensor shall have a range of at least 0-
5000 PPM
• Resolution of CO2 sensor shall be 1 PPM or
better
• Lower detectable limit of CO2 sensor shall be
10 PPM or better
• Precision of CO2 sensor shall be less than 3% of
reading or better
• Linearity of CO2 sensor shall be less than 2% of
full scale
• Response time of CO2 sensor shall be less than
60 seconds
• Operating temperature of CO2sensor shall be
0°C to 60°C
• 6Operating pressure of CO2 sensor shall be
±10%

6 Particulate Profile Sensor

• Particulate profile sensor shall provide

simultaneous and continuous measurement of
PM10, PM2.5, SPM and TSP (measurement of
nuisance dust) in ambient air
• Range of PM2.5 shall be 0 to 230 micro gms /
cu.m or better
• Range of PM10 shall be 0 to 450 micro gms /
cu.m or better
• Lower detectable limit of particulate profile
sensor shall be less than 1 µg/m3
• Accuracy of particulate profile sensor shall be
<± (5 µg/m3 + 15% of reading)
• Flow rate shall be 1.0 LPM or better
• Operating temperature of the sensor shall be
0°C to 60°C
• Operating pressure of the sensor shall be ±10%

7 Temperature Sensor

• Temperature sensor shall have the capability to

display temperature in °Celsius
• Temperature range shall be -10° to +80°C
• Sensor accuracy shall be ±0.3°C (±0.5°F) or
better
• Update interval shall be 10 to 12 seconds

Page 236 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
8 Relative Humidity Sensor

• Range of relative humidity sensor shall be 1 to

100% RH
• Resolution and units of relative humidity sensor
shall be 1% or better
• Accuracy of the sensor shall be ±2% or better
• Update interval shall be less than 60 seconds
• Drift shall be less than 0.25% per year

9 Wind Speed Sensor

• Wind speed sensor shall have the capability of

displaying wind speed in km/h or knots
• Range of sensor shall be 0-60 m/s
• Accuracy of wind speed sensor shall be ±5% or
better
• Update interval shall be less than 60 seconds

10 Wind Direction Sensor

• Range of the wind direction sensor shall be 0°

to 360°
• Display resolution shall be 16points (22.5°) on
compass rose, 1° in numeric display
• Accuracy shall be ±3% or better
TR 6.70 Update interval shall be 2.5 to 3
seconds

11 Rainfall Sensor

• Rainfall sensor shall the capability of displaying

level of rainfall in inches and milli meter
• Daily Rainfall range shall be 0 to 99.99” (0 to
999.8 mm)
• Monthly/yearly/total rainfall range shall be 0 to
199” (0 to 6553 mm)
• Accuracy for rain rates shall be up to 4”/hr (100
mm/hr) or ±4% of total
• Update interval shall be less than 60 seconds
• 0.02” or (0.5mm) of rainfall shall be considered
as a storm event with 24 hours without further
accumulation shall end the storm event

Page 237 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
12 Barometric Pressure Sensor

• Barometric pressure sensor shall have the

capability of displaying barometric pressure in
Hg, mm Hg and hPa or mb
• Range of barometric pressure sensor shall be
540 hPa or mb to 1100 hPa or mb
• Elevation range of the barometric pressure
sensor shall be -600 m to 4570 m
• Uncorrected reading accuracy shall be ±1.0
hPa or mb at room temperature or better
• Equation source of the sensor shall be
Smithsonian Meteorological tables
• Equation accuracy shall be ±0.01" Hg (±0.3 mm
Hg, ±0.3 hPa or mb) or better
• Elevation accuracy shall be ±10’ (3m) to meet
equation accuracy specification or better.
• Overall accuracy shall be ±0.03" Hg (±0.8 mm
Hg, ±1.0 hPa or mb) or better.
• TR 6.85 Update interval shall be less than 60
seconds

13 Noise Sensors

• Noise sensor shall detect the intensity of the

ambient sound in a particular area
• Noise Sensors shall be installed for the outdoor
applications
• Noise sensor shall be able to identify the areas
of high sound intensity ranging from 30 dBA to
120 dBA
• Noise sensor shall have resolution of 0.1 dBA

14 Integration with ICCC platform, City Portal and Mobile

applications

Page 238 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.7.5 Emergency Call Box:

Compliance
No Specification
(Yes / No)

1 ECBs to be installed one each at smart poles.

2 They shall mostly be mounted on a pole in a housing with

a canopy along with the ECB.

3 The unit shall preferably have a single button which when

pressed, shall connect to the ICCC or to the nearest/any
of the control room having the local control console.

4 These should also be capable of being used for Public

Address.

5 The PA control desk to be used for communicating with

ECB

6 Construction: Cast Iron/Steel Foundation, Sturdy Body for

equipment

7 Call Button: Watertight Large backlit Push Button, Visual

Feedback for button press and call indication

8 Connectivity: Ethernet

9 Sensors: For tampering/ vandalism

10 IP66 as per EN 60529, IK09 Protection EN 62262 or better

11 Operating Temperature 0 to 60° C

12 Speaking Distance as per site requirement

13 Inbuilt Class D Amplifier, 99db SPL

14 Minimum 3 Inputs and 2 Output relay contacts

15 ECB should be able to make calls to the PA system

16 Transmission Bandwidth 16000 Hz

17 Front panel: stainless steel of minimum 3 mm

18 Software Client for making/receiving Calls to ECB

19 Automatic Volume Control, Call recording

Page 239 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.7.6 IoT Gateway Specification

Sl.No. Description Compliance

(Yes / No)

1 Should be Linux / Windows latest version based operating system

powered gateway or microcontroller based gateway.

2 Gateway routers Single Board Computer running at 1.2GHz or better.

Should have a 1GB RAM

3 The receiver on the gateway should use a 867 Mhz or higher range and
follow a multi hop mesh networking protocol

4 The gateway should periodically update the central management server

at ICCC about the diagnostics status of each sensor, LED, controller and
display

5 The gateway should use secure http protocol to communicate with the
cloud server

6 The gateway should be able to control the sensors or IOT devices

7 The gateway should ensure the display data sync at all locations and
floors where they are placed

8 Should have Wi-fi on board, Ethernet connector on board

9 Should have Bluetooth Low Energy (BLE) on board for future tech
integration

10 Should have multiple USB ports for communication via USB GSM/3G/4G
dongle

11 Should use micro SD port for loading your operating system and storing
data

12 Should have a Micro USB power source (up to 2.4 Amps)

6.7.7 Public Address System

Compliance
Sl.No Minimum Specification
(Yes / No)

Make :

Model:

1 IP based PAS to be used for automated announcements or for

paging announcements from ICCC or from the local area as per
city traffic regulations. Should have 5 year warranty

Page 240 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
2 Each site will have multiple speakers connected to one IP amplifier

3 A local paging microphone (“Control Desk, Local”) shall also be

provided for doing local announcements

Outdoor Horn Speaker

Technical Specifications

1 Speaker – Minimum 30 Watts

2 Protection – IP66 and preferably IK10 or better

3 Frequency Range – 350 to 10Khz

4 Maximum Sound pressure level @1 m – 110 db or above

5 Operating Temperature - -10 to + 55 C

6 Construction – ABS Self Extinguishing

IP PA Amplifier

Technical Specifications

1 Amplifier: 120 Watt or above, Class D

2 Should have the capability to control individual PAS i.e. to make an

announcement at select location (1:1)
or multiple locations (1: many). The PAS should also support both, Live
and Recorded inputs

3 Native IP connectivity, no convertors to be used

4 0 to 55 C Temperature rating for Amplifier

5 Frequency Response: 70 Hz to 15000 Hz for Amplifier

6 Minimum 2 Inputs and 1 Output relay contacts in Amplifier for

connecting external beacon

7 Speaker: Minimum 3 Speakers 30 W capacity per location

8 Line Monitoring Facility for speakers

9 180-240 V mains input supply

10 Compliant: CB/CE/EN/UL and BIS/IEC

Control Desk

Technical Specifications

1 Should have the capability to control individual PAS i.e. to make an

announcement at select location (1:1)
or multiple locations (1: many).

2 Noise cancelling in built microphone with audio monitoring

Page 241 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 3 Frequency range – 200Hz – 16Khz

4 Display – 8 lines X 14 characters or better

5 Connectivity- IP Based, POE powered

6 Amplifier – Inbuilt 2.5W or better class D

7 Operating temperature - 0 to 50C

8 It should have RJ-45 Information Outlet, Minimum Dual Port (1 Uplink

and 1 downlink)

PAS Central Software

Specifications

1 The system shall deliver pre-recorded and live messages to the

loudspeakers attached to them for public
announcements.

2 The system shall contain an IP based amplifier and uses power that
could drive the speakers.

The system shall also contain the control server that could be used to
3 control/monitor all the components of the system that includes
Controller, Calling Station & Amplifier.

Central Server operating on 2 or more network interfaces

4
1Gbps or more data rate Compliance – UL 62368-1

5 Integration with ICCC and any other component if required

PAS Central Server

Technical Specifications

1 Central Server operating on authorized operating system

2 2 network interfaces

3 1Gbps data rate

4 Compliance – UL 62368-1

6.7.8 City Public Wi-Fi

It is proposed to set up city wide public Wi-Fi across Puducherry City at the designated
locations and connected to ICCC using the OFC proposed. The minimum expected Public Wi-
Fi systems specifications are as follows. Outdoor AP should have controller license from day
one and should be integrated with WLC at DC.

Compliance
Sl. No Technical Specification
(Yes / No)

Page 242 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Make

Model

Access Points proposed must include dual radios (2.4 GHz and 5 GHz) and should
1 cover a distance of 250 meters in open area. Outdoor (IP67 rated or better) Wi-Fi6
802.11ax WLAN AP with Tilt bracket & PoE Injector

The access point should be light weight and should support installations on walls or
2
light poles without disturbing the aesthetics of the area.

3 LED should be available for activity indication

4 The Access Point should have auto-sensing 100/1000 Mbps RJ45 port.

Must support 2x2 multiple-input multiple-output (MIMO) with Radio 1: 2.4GHz: 2x2
5
with 2SS or better and Radio 2: 5GHz: 2x2 with 2SS

6 Should have dual Radios and should support 200 clients

7 Should support 1 Gbps data rates on dual concurrent radio operations

8 Should support 1024-QAM, and 20/40/80 MHz Channels

Minimum conducted transmit power shall support 23 dBm or more on both 2.4 and 5
9
GHz.

AP shall have integrated/ external antenna with minimum gain of 5dBi or more for 2.4
10
GHz and 5dBi or more for 5 GHz radios for Omni Directional Antenna device.

11 The access point or the controller should support DHCP relay

Must have a dynamic or smart RF management features which allows WLAN to

12
automati-cally and intelligently adapt to changes in the RF environment

13 WLAN Solution should support Mesh capabilities

14 Along with a controller the Access Points should support fast roaming feature

15 The access point should provide wireless IPS sensor support on both radios

16 The WLAN Solution should support IP filtering

17 WLAN Solution must support Application Visibility/Control

WLAN Solution must support WPA3, WPA2 (CCMP, AES, 802.11i), WPA2 with open ac-
18
cess public WLAN.

19 Security solution must provide Rogue AP detection and protection

System should support Authentication via 802.1X, mac authentication to local

20
database or external RADIUS Server.

For troubleshooting purposes, the administrator should have the ability to remotely
21 packet capture and / or 802.3 frames from an access point without disrupting client
access

Page 243 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 WLAN solution should provide features that provides no touch AP discovery, adoption,
22
provisioning and should be from same OEM

WLAN solution should provide features that provides other management functions
23
including AP management and configuration, firmware push and statistics reporting

24 Must support telnet and/ or SSH login to Aps directly for troubleshooting flexibility

25 Access point should have Integrated PoE and power injector Support

26 AP shall Support Surge Suppression of up to 4 Kv.

Operating Temperature: 0°C to 65°C and Operating Humidity up to 90% RH non-con-

27
densing.

28 The Access Points should support WMM, WMM-UAPSD, 802.1p, Diffserv and TOS

29 Support for Voice-over-wireless LAN (VoWLAN), quality of service (QoS).

Access point must be supported for a minimum of 5 years by the hardware vendor
30
with software updates and upgrades without additional cost.

Page 244 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.8 Geographical Information System

It is envisioned that location-based GIS applications are critical for PSCDL and plays major role
in disseminating information & data to stakeholders, visitors / tourists. Keeping view of this it
is proposed to deploy integrated GIS Engine in ICCC Platform which can be further integrated
with the MAPs like Google, Open Street Etc.

• It should be possible to visualize all the Assets (Sensor, Devices, Vehicles, Cameras, other
city resources) on map.
• The Assets must be provided as layers with ability to switch these layers and visualize the
assets of only selected layers.
• The GIS Maps should provide interactive visualization of travel time and traffic based on
the sensor data and data ingested from 3rd party sources.
GIS Platform shall support GIS Maps in following file format PDF, JPG, PNG, Vector PDF
Map, Web Map Service (WMS), GeoJson defined by the Open Geospatial Consortium (OGC),
Google Map-aerial; terrain, Bing Map, aerial, satellite, hybrid, ArcGIS/ESRI and Open
Platform GIS Applications etc
GIS platform should provide a picture-in-picture map view capability,
- Upon the availability of GPS positioning of a file, the user should be able to quickly alternate
between the video and map view within the video player.
- The application must be able to ingest and present either a static location (e.g., for a fixed
camera) or dynamic location (e.g., for mobile cameras) that allows users to validate the
location where the video was recorded at the time of the event.
• GIS platform should support different layers like
- Ward Boundary Layer
- Zone Boundary Layer
- Street Boundary Layer etc.

6.9 Flood Sensors & Alert System

a) Proposed ICT Solution:
The storm flooding usually creates havoc and panic situation to the people residing in urban
areas. High intensity rainfall events and flooding in urban areas are increasing every year. In
the past two decades, migration to urban areas and rise in urban population in cities are
experiencing a tremendous growth. Urban flood scenario is increasingly witnessed due to rapid
urbanization in the city. Flood disaster is causing huge economic and social losses and has
resulted in disturbed daily living for the public.

The proposed Flood Sensors & Alert System shall consist of

1. Flood alerts integrated with ICCC

The proposed methodology shall be developed for Urban Flood Sensors and Alerts System have
two stages.

Stage 1: Rainfall and Runoff module Stage

2: Flood Alert

The flood monitoring warning dissemination system: It is proposed to install Flood Sensors.
District at locations covering a geographical spread of 64 Sq. Km of city area. It is proposed
to install Flood sensors in the identified areas like major canals and junctions.
Page 245 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
The rain water level data (in millimeters) is recorded at every 15-minute interval by default
and configurable as required and will be transmitted to the application server through
telemetric GPRS enable system. These water level data shall be used to validate the depth of
water obtained as an output from hydrologic model. The data on Temperature, Relative
Humidity, Wind Speed, Wind Direction, Rainfall Intensity and amount of Rainfall from
telemetric rain gauges and weather sensors are also being collected every 15 minutes and
must be configurable as required. The near-real time data collected through the network shall
be analyzed, and real time maps and reports shall be generated. A GIS and ground truth
analysis along with historical flood event study in the city shall be conducted for finalizing and
mapping of frequently flood vulnerable locations.

Warning System – Published over ICCC

The high intensity rainfall alerts and Flood forecast, warnings, Reports and Advises shall be
disseminated through email, Social media, SMS to the mobile phones of Zonal heads, ward
level officers of city corporation and also to all the connected line department in the city.

To disseminate the flood forecast and warnings to the city public, A dashboard shall be
developed and integrated with ICCC would be the single interface which shall give the insight
about urban flooding in the city. To disseminate weather related information, forecast and
related advises directly to the general public a 24x7 to City Mobile app. The near-real time
data collection, report generation and dissemination shall help the City administrative
authorities in planning and executing disaster management and mitigation plans at microlevel
and finally reducing the risks involved due to the flood disasters.

Major scope of Early Warning and Dissemination System:

1. Warning and Dissemination system development in collaboration with DRDM.

2. Mobile application for citizens & Dashboard development for administrators.
3. Integration with ICCC.

S. No. Description
Flood monitor must be capable to monitor flood levels in water bodies, streams and
1. rivers

Flood monitoring application must be integrated with flood sensors and should be
2.
able to communicate with them.

3. Flood monitoring application must be web based with mobile app

The system should be able to send accurate and instant warnings to make informed
4.
decisions

5. The measured data should be sent to flood monitoring application

The flood monitoring application should have intuitive dashboards providing real-time
6.
monitoring information

The flood monitoring application must be able to integrated with various third party
7.
applications via APIs

8. The application must be able to do real-time continuous measurement

The application must be able to send instance notifications via SMS, Email and/or
9.
push notifications to a mobile app

Page 246 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 10. The solution should also provide a mobile app working in at least Android or iOS

11. The application must provide intelligent analytics based on data captured

12. The application must have custom reporting capabilities

13. The application must be able to provide forecasts and trends

14. The application must be able to provide real-time notifications

15. The application must be able to be deployed on cloud or on-premise

Technical Specifications

Sl.No Component Description Compliance

(Yes / No)
Make:
Model:
Body

1 Build Polymer/Metal

Range Options

2 Max Range 3 ft (91cm)

30 ft (9.1m)

50ft (15.2m)

Communication
Capability

3 Wireless

2G/3G/4G/5G/NB-
GSM
IOT

LoRa (Optional) 865-867 MHz

802.11 b/g//n
Wi-Fi
(2.4GHz)

Wired

Ethernet 1-Port 10/100 FE PHY

RS485 Modbus Protocol

Page 247 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Power Options

4 Input 230V, 50 Hz

Solar Powered

Operating Environment

5 Temperature -0 to 60° C

Humidity 0% to 100% RH

6.10 City Surveillance System

Primarily the function of police, these refer to operations to enhance the safety of the publicand
provide necessary surveillance information to Police for both reactive and predictive policing.
CCTV surveillance has been an important component across multiple cities with increasing
usage of video analytics to aide police in spotting potential incidents and managing them as
they happen.

Key Issues

The main challenges of surveillance in urban ecosystem are as follows:

• The rate of urbanization is increasing and with city growth comes an increase in crime
and safety concerns due to concentrated populations
• Lack of surveillance cameras on a Pan City basis results in delays in crime detection and
response
• Riots and vandalisms go undetected on a real time basis in lieu of absence of CCTV
cameras at important places
• Lack of intra department real-time coordination, with voice and multimedia services
• Need for intelligent analytical capabilities by police
• Fragmented decision making due to lack of inter-departmental collaboration
• Citizens do not have access to a dedicated Emergency Response System

Indicative Key Outcomes and KPIs

• Supporting law enforcement agencies in 24x7 surveillance and monitoring

• Emergency Services Response Time: Average response time for Emergency Services o
Number of CCTV cameras installed in the city per unit of road length
• Number of recorded crimes per lakh population
• Extent of crimes recorded against women, children and elderly per year o Location wise
analysis of crimes in the city
• Creation of emergency corridor/ passage for passing of fire response / police/ ambulance
teams
• Proactive identification of security issues leveraging intelligent analytics from the
Page 248 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 surveillance system
• Supporting active response during emergency & disaster situations
• Providing secured access to video at any time from any network location
• Situation/Rule based alerts based on user inputs
• Automated response based on events including communication of alerts to relevant
authorities like Fire, Hospitals, etc. for swift response in case of emergencies;
• Access to historic video data for investigative purposes
• Improved Crowd management and Security Breach handling

Surveillance System:

I. The Surveillance System shall be a fully distributed solution, designed for large multi-site
and multiple server installations requiring 24/7 surveillance.
II. The solution shall offer centralized management of all devices, servers and users.
III. The Surveillance System should not have any limit on the number of cameras to be
connected for Surveillance, Monitoring and recording. Any increase in the no. of cameras
should be possible by augmentation of Hardware components
IV. The Surveillance System shall support distributed viewing of any camera in the system
using Video walls or big screen displays
V. The Surveillance System shall support alarm management. The alarm management shall
allow for the continuous monitoring of the operational status and event-triggered alarms
from system servers, cameras and other external devices
VI. It should be possible to integrate the Surveillance System with 3rd-party software, to
enable the users to develop customized applications for enhancing the use of video
surveillance solution. (e.g., integrating alarm management to initiate SMS, E-Mail, VoIP
call etc.)
VII. Rule Management: The system shall support the use of rules to determine when specific
actions occur. Rules shall define what actions shall be carried out under specific conditions.
VIII. The system shall support rule-initiated actions such as:

• Start and stop recording

• Set non-default live frame rate
• Set non-default recording rate
• Start and stop PTZ patrolling
• Send notifications via email
• Pop-up video on designated Client Monitor recipients

Video Management Capabilities

The system shall allow an operator to view live / recorded video from any camera on the IP

Network. It should allow switching of video streams across the system.

ICCC/Police personnel shall have followed access to the video feeds of the cameras of their
jurisdiction:

• Viewing rights to all the live Camera Feeds

Page 249 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• Viewing rights to the stored feeds

• Access to view Alerts / Exceptions / Triggers raised

• Trail Report on specific person / object / vehicle for a specific period / location

• Personalized Dashboard (depending upon grade of police officer)

• Accessibility to advanced analytics on recorded footages

• Advanced search based on various filters like alarm / event, area, camera, etc.

• Event Handling Capabilities:

• The camera shall be capable of recording an event as pre and post event images to on-
board SD Media Card and share it with ICCC

• Events may be triggered using camera motion detection or from an external device input
such as a relay.

• Support for various type of Logs such as System Log, Audit Log Alert Log Event Log should
be available.

Recording and Storage:

• For incidents that are flagged by the Police, Authority or any court order, the video of the
relevant portion from all relevant cameras should be stored/archived separately for
investigation purposes and a committee at Authority can decide when this video feed can
be deleted

Audit trail of the system to be maintained on permanent basis / as per the backup policydefined.

The Recording System shall run independently of the Video Management system and continue
to operate in the event that the Management system is off-line.

Investigation Scene Rebuilding

• It should be possible to select the cameras for synchronized and simultaneous archived
viewing. It should be possible to record the videos being rendered from these cameras
into a single video. Such a single video should support up to eight such cameras in vertical,
horizontal or overlay fashion. An easy feature of cloning the time stamp from one camera
to multiple other cameras for synchronous archived viewing should be available.

Page 250 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• For quick investigation of the alerts, it should be possible to configure cameras in small
functional group/s. In case of an alert in any one camera in the group, live video from
other cameras in the group should be popped up automatically on the operator screen.

The system should enable tracking of the vehicle on a GIS map to locate any suspicious /
identified vehicle. The Cameras should transmit quality video feed (clear, un-blurred, jitter
free, properly lit, unobstructed, etc.).

The network design should ensure that the Packet losses are less than 0.5%. Integration with

ECB and Citizen App for SOS Management should be available. Integration with ICCC

Integration of all the IT systems and solutions deployed for the Surveillance management
with ICCC should be through APIs

The alerts generated in ICCC should be handled in a coordinate manner with following;

a. Rule engine module for event/alarm handling

b. SOP (Standard Operating Procedure) tool for administrator to configure the SOP responses
based on each alert.
c. Integration with the Incident Management system for the users to log in the incidents and
the alerts, view the report from the module about the incidents etc.
d. Alert processing such as Acknowledging the alert, emergency response, SOP for the alert.
e. Connecting the next steps as per the SOP like informing Police\Fire departments based on
the incident etc.

Technical Requirements

c)Proposed ICT Intervention.

The core objective is to create a supporting mechanism for the city agencies through 24x7
surveillance and
monitoring throughout the city as well as enable proactive identification of issues leveraging
intelligent analytics from the surveillance system.

This module proposes implementation of a holistic City Asset Surveillance and Service
monitoring system across the city including:
• Installation of PTZ cameras, Fixed Box cameras

• Centralized AI based intelligent Video analytics at data center for all the cameras installed

• Centralized AI based intelligent Video analytics for all the feeds received from Department
of Police cameras, where these will provide the feed of CCTV cameras up to ICCC data
centre.
• Develop a full-fledged command and control center for ensuring 24X7 monitoring and
enabling effective action to be taken in case of law and order, Municipal services disruption
, emergency disaster situations

• Integration with existing safety & surveillance systems already implemented like existing
cameras installed, existing command & control centre as Police Station, etc.
It is proposed to have surveillance cameras and a dedicated video analytic system for incident
monitoringbased on events. Further, with a view to share the video to other Stake Holders as
well a dedicated VMS isbeing proposed with a distributed architecture.
Page 251 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6.10.1 Video Management System:General Requirements
Compliance
# Technical Specification
(Yes/ No)

Make :<to be provided by the bidder>

Model :<to be provided by the bidder>

The VMS architecture should support centralized or de-centralized

deployment. The VMS should be modular in design and should have
1
components such as Management Server, Recorder Server, Streaming Server,
Database Server and Integration Server. All hardware / software should

have 5 year warranty’

All the communication among the servers and clients should be secured and
the VMS should support the SSL /TLS communication. It should have option of
encryption with AES 128/256 and RSA 1024/2048 encryption standards. The
VMS should also support secure communication between the camera and
2 the server using SRTP/RTSP protocols. The VMS software should have been
tested for vulnerabilities and should have been penetration tested as per the
OWASP guidelines. Certificates from the CERT – IN empaneled auditor from
the respective country of origin clearly indicating the encryption and VAPT
test should be available.

System Architecture

The Video Management Software should be enterprise class application

1 based on client-server architecture and should support unlimited cameras by
augmenting recorder, management and database servers.

The single master server should handle unlimited cameras, unlimited recording
2
servers and unlimited users.

The VMS should be compatible with Microsoft Windows/Unix/Linux Operating

3
Systems.

Page 252 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
4 The VMS should run on all the leading virtualisation platforms.

VMS should be agnostic to database servers For example it should work on

5 Microsoft SQL, MySQL, PostgreSQL and Oracle. It should also support NoSQL
databases.

VMS should have ONVIF Profile S, G , M and T compliance. Certificate to this

6
effect should be available on the ONVIF website.

The VMS should work on Commercially off the Shelf hardware and storage
7
systems.

The VMS should have an independent media streaming service which can be
8 installed on a separate server to support scaling up of the clients without
affecting the recorder server performance.

The VMS should have manual and automatic mode of assigning cameras to
the available recorder servers. In automatic mode, the cameras should be
9 assigned based on the compute capability of the recorder server. In manual
mode, the system should allow the administrator to assign the cameras to a
recorder server.

The VMS should provide multiple redundancy options in the platform for the
10
following components:

The VMS should have a provision for adding Master and Auxiliary Master Server
to provide the native failover functionality. As a failsafe configuration, the
11
system should work with limited functionality, without affecting the recording
of cameras, even without the Master server.

The VMS shall provide redundant recorder server for single or a group of
recorder servers. In case of the failure of the Recording Server, the VMS should
12 automatically assign the cameras on the failed recording server to other
operational recording servers on the network. The camera recordings shall be
synchronized back to the original Recording Server once it is back online.

Page 253 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Each recorder server should have independent storage configuration for
local and network storage including NAS, SAN storage and Object Storage
from popular cloud platforms such as Amazon AWS, Microsoft Azure, Wasabi,
13
etc. Option of mirroring the storage of camera feeds should be available in
the system. Back up storage on cloud/DC secondary storage for 60 days post
local storage of 30 days.

The VMS should have configurable DC-DR Functionality. The system should
have configurable data retention policies for each DR setup to select what
14
data to move and how long the data to be retained in DR before recycling
the storage space.

The VMS should have multiple options for selecting the business continuity
15 requirements. Following options should be available in an easy to configure
grid such as

Data Replication Policy grid should allow selection of data such as video
data, event messages and incident alerts, event video and the video
16
segments tagged by the operator. It should be possible to select all or a
group of cameras for such replication.

The Business Continuity Policy should allow selecting all or a group of

17
cameras which should switch over to DR for recording and viewing of
videos.
The user access policy should allow the granular control for various
18 categories of users for functions such as login to the DR site, live video
viewing and recorded video replay.

The VMS should have federated architecture with centralised monitoring of

19
the videos, video analytics and system health alerts.

The VMS should have a unified API interface to expose various system
functionalities, including, but not limited to, Analytics event alerts, live and
20
archived video, PTZ control, system health alerts over HTTP protocol to external
systems such as Integrated Command and Control Application,

Page 254 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Deleted

21

The VMS should support unicast and multicast streaming for live viewing and
22
recording functions.

Centralized Management

The VMS should support multi-site deployments with centralized monitoring of

1 the videos, video analytics and system health alerts. The centralised
monitoring platform shall have the following features:

Should support matrix view at full framerate with support for H.265, H.264,
2
MPEG4 and MJPEG video compression.

Drag and drop of cameras and live viewing of cameras from a mix of
3
cameras from all the locations, group of locations, single location.

4 Support digital zoom of the cameras from central site.

Control remote PTZ cameras from central monitoring client application and
5
digital zoom on remote fixed or PTZ cameras.

6 Ability to pick and choose the selected cameras from remote sites.

Ability to search and retrieve the archived video from the remote site with
7
intelligent motion based search

8 Download multiple video segments from multiple sites easily

9 Multi-layer maps with support for static maps or GIS maps.

10 System health dashboard for all connected systems.

Central site management features with Role based User management,

dynamic site management, video feeds aggregation, event information
11
management and distribution, system administration with full audit trail and
logs

Shall support secure and encrypted transmission of video files to cloud as per
12
requirement.

Page 255 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Receive alerts from the remote site with event metadata received first and
13 then the users can request image and video clips to ensure effective
bandwidth management.

14 Dashboard of all connected devices and the health status of the devices.

15 Resource utilization of the system and statistical reports for the remote sites.

16 Camera SLA report with camera connection and uptime information

17 Scheduling of reports

Cloud Readiness of the VMS

The VMS should be cloud deployment ready and agnostic to the cloud
environment - be it a private, public or a hybrid cloud. It should work on the
bare metal servers of the cloud solution providers with in-built intelligent video
streaming and resource orchestration services. The VMS should allow using
1
various tiers of object storage to optimize the storage requirements and data
retrieval times. The VMS should be capable to integrate with Video Analytics
functions powered by the Artificial Intelligence and Deep Learning
technologies on cloud infrastructure.

The VMS should allow adding network storage location by giving path to the
network storage device and authentication credentials. This feature should
2
also allow adding storage locations on the cloud platforms such as AWS, GCP,
Azure, Wasabi etc.

The VMS should have native support for Object Storage from popular cloud
platforms such as Amazon AWS, Microsoft Azure, GCP, Wasabi, etc. The
3
system should support pushing the recorded video file on a definable
schedule to the Object Storage.

Information Security

Page 256 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The system should have multiple levels of authentication and access control
mechanisms: A. Role based Authentication

B. Session control using encrypted tokens

C. User stickiness to a particular hardware workstation

1
D. Dual Factor Authentication with provision to receive the OTP via text
message on the registered mobile of the user and through the registered
email address

E single sign-on based on LDAP and Active Directory.

System configuration data should be stored in encrypted files with checksum

2 and there should be user selectable encryption algorithms such as MD5, RSA
and SHA.

3 The data at rest should be stored in a encrypted format.

The videos downloaded from the system should be watermarked with an

4
option to export with non-tamper format.

5 The software should maintain audit trails of user interaction

The system should have built-in audit tool which generates reports such as
6 report describing health of network connectivity and the throughput of
storage devices against each server.

7 The software should be OS agnostic.

Data in the system should encrypted with either MD5 or SHA256 cryptographic
8
hash functions and video data are stored in encryptedformat when at rest

Storage & Recording Functions

The VMS should allow creation of customised recording profile with day and
hour granularity and an option to add recording profile for special days. It
should be possible to create unlimited recording schedules with option of
selecting various streams, Frame rate and compression available from the
cameras. The recording configuration should have the following options:

1 - Redundant recording

Page 257 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 - Edge recording

- Selection of SRTP or RTSP protocols

- Recording schedule based on motion only recording, FIFO and specific

retention period.

Each recorder server in the system should have independent configuration for
2
database and storage servers.

The VMS should periodically check the gaps in live recording of the cameras
and should check with the on-board storage of the camera. In case of a gap,
3 the VMS should synchronize the video recording on the on-board storage with
the VMS storage. Such synchronized storage should be displayed with
different color for quick attention of the operator.

The event and the associated video clips should have the facility to be
4 marked for non-delete flag to protect the event and metadata from being
wiped out by the data retention policy. Additional option should be available

not to delete the event till a specific date. After that, the event should be
wiped out as per the data retention policy.

The system shall have the capability of recording video at a lower frame than
5
is received from the camera (frame rate reduction mode).

VMS should support H.265, H.265+, H.264, and MJPEG streams for both Live
6
view and Recording.

7 The client should offer below three options for operator-specific recordings:

Record Matrix Videos: Record a matrix of the videos being displayed on the
8
screen.

Record Stitched Videos: Stitch and record the stitched video matrix either in
9 horizontal or vertical direction. Any number of cameras can be added in the
stitched video.

Record Screen: Record the entire screen of the operator including any matrix
of cameras visible and other desktop activity being performed by the user
10
outside of the VMS client. This functionality can be achieved using in-built or
third party tools.

Page 258 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 General VMS Functions

The system, once configured, should work seamlessly, without any

1
configuration, after the server/s pass through the power on-off cycle.

The VMS should offer feature rich desktop client for Microsoft Windows/MAC
2 /Linux OS. It should also have a browser agnostic web client and mobile client
available on Android and IOS platforms.

The VMS should have site-wide, hierarchical tree of cameras visible to all the
3 operators with appropriate rights and should also have operator specific,
unlimited hierarchical grouping of cameras as per the area or functions.

The VMS should allow grouping of cameras as per the Group Name or
4
Location for flexibility of camera management.

VMS User Management & Administration

The VMS should support Microsoft Active Directory or Lightweight Directory

1
Access Protocol (LDAP) for enterprise wide user management.

For additional security and accountability, it should be possible to restrict the

2
operator to a particular workstation.

The VMS should allow addition of new user based on five different profiles. It
3 should be possible to assign various configuration and operation functions for
each profile as required in a user-friendly matrix view.

The VMS should seek answers for the multiple selectable security questions to
each user logging-in for the first time. The answers to the security questions
4 should be validated by the VMS in case the user wants to change the
password. The VMS should not allow using the last three passwords while
selecting the new password.

Page 259 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The system should have collaborative vigilance functions. It should offer chat
room for exchange of information such as text messages, user selectable files,
archived video link, camera layouts, incident snap, clip and VA alerts for
collaboration among the operators. The chat window should show color
coded status for messages which are sent, delivered and read. The
administrator should have access to all the messages being exchanged
5
among the operators. To assist in collaborative investigation of an event, the
operator should have the function of sharing the camera matrix with a mix of
live as well as playback videos to the fellow operators or to the Supervisor. This
function should also allow sharing an event along with event video, stitched
video of a matrix recorded on the operator workstation, any other video clips
received from external sources, etc.

The system should allow camera permissions to the users based on individual
6
camera, group of cameras and all cameras.

VMS should allow the Administrator to import any active users screen on the
video pane by drag and drop to watch the operator’s activity on-line in a
7 matrix layout. Operator should be able to drag a user group on the screen to
watch their desktop activity at one go. Administrator should be able to record
the matrix view for the desired duration if required.

VMS Client and Operator Functions

The unified VMS client should provide all the configuration functions for Video
1 Management Server, Video Recorder Servers, Storage and Video Analytics
for creating rules.

The VMS should allow multi-monitor support for the client workstation. It should
2 allow setting up of different layouts on different monitors such as camera
matrix, map view, VA alerts view, for example.

It should be possible to select cameras for synchronised and simultaneous

archive viewing. It should be possible to record the videos being rendered
3
from these cameras into a movie clip. This operation should be possible in a
matrix recording or stitched recording options.

Page 260 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The VMS should retain the VMS client screen state (including Video Analytics
alert window, message window, Video Matrix, etc.) in case of an accidental
4
shut down of the machine and should offer the exact same screen to the
operator upon logging back into the system.

The client should have configuration option to view the live videos directly
from camera or from the media server. In case of the video feed coming
5
directly from the camera, the live view should be available even if the servers
are not reachable.

The live view window of a particular camera should allow the operator to view
the archived video. The operator should be able to go back in the time by
6 selecting quick shortcuts for 5, 10, 20, 30 seconds, 1, 5 minutes, 1, 5 hours.
Operator should also be able to select the exact date and time though the
calendar widget.

Virtual Workspace Functions

The VMS should present the functional dashboard of the system to the
operator like a virtual workspace. The Dashboard should allow the operator
1 to view and manage the cameras, operator specific camera matrix views as
per the functional requirements, map views for the geo-aware vigilance,
video analytics alerts, and information and alerts from the integrated devices.

When the operator drags a camera group on to the virtual workspace, the
2 VMS should dynamically select and display the number of tiles in the virtual
matrix based on the number of cameras available in the group.

Deleted
3

It should be possible for the operator to configure the virtual workspace using
4 the virtual matrix by assigning the matrix to display alerts and information from
a combination of systems such as live and archived videos,

Map Functions

Page 261 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The VMS should support geo-aware vigilance with the use of layered maps
using standard picture files, City GIS maps and online maps such as Google,
Bing, OpenStreetMap’s. It should be possible to drag and drop the cameras
1 on the map for easy navigation. In case of multi-layered maps, the system
should show all the available maps in a drop down list for easy selection. The
VMS should allow viewing of live and playback videos, event notifications on
the map view with event tracking functionality from multiple cameras.

The VMS should support a geo-fence based vigilance functionality. The VMS
should show the cameras within the selected geo-fence. It should be possible
to associate a base camera within the geo fence with other neighborhood
cameras to form a group for situational awareness of the neighborhood. In
2 case of an alert in the base camera, live feeds from all the cameras in the
group should be popped up. The window should show the live video and the
alert video clip from the base camera where the alert is generated, the
neighborhood cameras and the location of the incident on the map within
the same window.

It should be possible to export the map view to the desired screen in case of
3 multiple screens available. The system should show all the available screens in
a dropdown.

The system should have an easy to use pencil tool /similar easy to use feature
4 to quickly select the cameras on the map (static or GIS) for simultaneous
viewing for both live and playback videos.

It should be possible to forward the map view including the camera streams,
5 live or playback to another user in the system for easy collaboration of geo-
spatial viewing.

The map view should allow searching of the camera by name or IP address
6 to quickly find out the camera on the map. This is useful in emergency
situations when an operator wants to pull the live video on the screen quickly.

The VMS should show event notification from the cameras on the map itself.
7
The operator should be able to click on the event notification of a particular

Page 262 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 camera on the map and the VMS should open the event window on the
operator screen.

Investigation and Tracking Functions/Video Synopsys Tool.

The operator should be able to recreate a scene by arranging the cameras

and their respective time-stamped archived videos. The operator should be
1 able to save such a recreated scene through collection of cameras for quick
access and should also be able to share such collection to the other users or
supervisors.

The operator should be able to associate all neighborhood-view cameras to

a base camera for tracking an activity for investigation. When an alert is
generated in the base camera, the VMS should pop up a screen widget/
similar easy to use interface which shows live video of the base camera,
2 playback of the base camera from the pre-buffer of the alarm and live view
of the associated cameras along with the map view. This entire screen should
be used for forensic investigation and should be recorded as all-in-one
evidence for export and sharing. This event window should be configured to
pop-up on the event hot-spot monitor.

The VMS should allow tracking the movement of a suspect or a motorcade

through live view from the cameras on the map by using a simple pencil
tool/similar easy to use feature on the screen. With the tool/feature, the
3
operator should be able to draw a line on the map touching one or more
cameras and the cameras touched/selected by the tool/feature should
appear for live view on the screen.

The VMS should have PTZ camera control options in a separate PTZ control
widget. The widget should show all the available presets, allow pan, tilt and
4
zoom of the camera, and also allow creation of a preset. It should also support
3-axis USB joysticks for PTZ camera control.

Page 263 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The VMS should allow creation of a PTZ tour based on the presets available
from the PTZ camera. The VMS should allow setting the hover time for each
preset depending on the functional requirement. It should be possible to
5
attach such a tour to any of the associated video analytic use case. The
creation of a PTZ tour should be the function of the VMS without any external
dependency

The system should offer multiple playback mechanisms (including single frame
6 playback) for ease of auditing and investigation, including zooming and
panning simultaneously.

The system should allow ease of tagging of exceptions/audit/investigation

7
findings and creating an institutional library of the same for future reference.

The VMS on integration with Video Analytics software should provide forensic
search operation based on the powerful attribute search analytics feature.
The operator can select any person in the camera field of view and search
8 for the appearance of the selected person based on the attire attributes in
the selected cameras for the selected duration. The attribute search should
show persons with matching attributes in a grid. It should be possible to click
on any match to view the playback video of that instant.

The VMS on integration with Video Analytics software should allow the
operator to select an unidentified object with a selection tool on the screen
9
to identify who left the object in the scene. The analytic should search the
video and show the video frame when someone left the object in the scene.

Event and Alert Functions

The VMS should allow sending the event alert to the designated person or a
1 group of designated persons through SMS or Email. These rules should be
available with configurable priority of the alert.

The VMS should allow monitoring of archived video of the selected camera
under categories such as events, motion or continuous recording. The VMS
2
should also show a report of cameras indicating recording status for the
selected duration, critical video data and Incident Video data.

Page 264 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Live events should be shown on the event hotspot monitor and retained for
the configured time. This should alert the operator of the current events. The
3
unattended events should be queued to be taken up by the operator one-
by-one later.

The events dashboard should be available with multiple filter parameters such
as - by camera, by use case, by camera groups, and the easily selectable
duration such as today, last 7 days, last 30 days, and calendar widget, etc..
4
Reports should be exported in formats such as excel and CSV. The dashboard
should also have the graphical representation of the reports in terms of the
bar charts and pie charts.

It should be possible to pass the specific alarm intimation to specified users

5
rather than sending all alarms to every user.

Camera Management and Viewing Functions

VMS should allow configuring the cameras in multiple groups independently.

It should be possible to assign all, single or multiple groups to operators. At
1 least 100 such groups should be possible with an unlimited number of cameras
in each group. It should be possible to assign camera/s to single or multiple
groups simultaneously.

The operator should have the ability to use digital zoom where the zooming is
performed on any number of cameras simultaneously - for live and playback
2
videos. This functionality should be the default for fixed cameras. The use of
digital zoom should not affect the recording.

Client viewer should allow the same camera to be viewed on multiple display
3
tiles; one may be digitally zoomed, or on high resolution stream.

The VMS should allow restricting the users who are authorized to view the
4
camera feeds to a single camera and to the group of cameras.

The system should allow creation of operator specific camera groups

comprising of live video views and archived video views. It should be possible
5 to share such groups with other users and administrators. The recipient of such
information should be able to see the exact layout of live view and archived
video view.

Page 265 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The camera matrix for live and archived videos should support simultaneous
viewing of cameras in multiple grids ranging from 2x2 to up to 8x8 and should
allow operator to configure as per requirement . A simple click should allow
6
enlarging any of the cameras in the multi-screen displays into a full screen and
full resolution display of the camera. On clicking again on the enlarged
display, multi-screen display should reappear.

The VMS should allow the operator to create multiple camera matrix
comprising of live and archive videos from multiple cameras and create a
7 sequence of such multiple matrix to be displayed in a cycle with configurable
display duration for each matrix. It should be possible to export such a
sequence to any of the connected cameras or the video wall.

It should be possible to drag and drop cameras from the camera directory to
8
the display screen.

The Client Viewer should offer the capability of browsing recordings from
9
cameras on the same panel where other cameras are displayed live.

VMS should have smart management of video streams from camera. It should
10 select lower resolution stream when viewed in a matrix and should
automatically switch to the high resolution stream when viewed full screen.

The Client Viewer should display a time line for each camera to represent
recorded video sequences. The Client Viewer should indicate whether the
11 video was recorded due to motion activation or recorded without motion or
pre and post alarm video. The time line band should be highlighted based
on the camera view selected in the display.

The camera type should be shown with specific camera icon and the state
12 should be displayed in different colours to indicate whether the camera is in
live mode, in recording mode, in stopped mode or video analytics alerts.

13 From the Client Viewer it should be possible to:

14 Bookmark an important event for easy search and retrieval later.

Bookmark the display layout with selected distribution of cameras across the
15
panel with a mix of live and archived video.

Page 266 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Use sound notifications and external annunciators for attracting attention to
16
detected motion or events.

17 Get quick overview of sequences with detected motion.

18 Get quick overviews of detected alerts or events.

The Client Viewer should have the capability to receive multicast streams if a
preset number of clients are requesting the same live view camera. The
Operator should have the option to configure the system to always receive
19 unicast streams at the discretion of the system administrator. The system
should have the capability to detect if the network becomes unreliable and
to automatically switch to unicast to ensure that the operator is able to
receive video.

The Client Viewer should have the following audio functions at specified
locations.

The Client Viewer should allow an operator to play live audio from a camera’s
1 microphone and play back recorded audio. The audio on/off option should
be available on the camera display matrix for each camera.

The operator should have a “press to talk” option which should send the
microphone input from the operator out to the speaker attached to the
2
camera. The microphone button should be available on the camera display
matrix for each camera.

The VMS should have integration with the IP speakers and should be able to
3
send the audio message for the selected IP speaker.

It should be possible to export the video clip of selected duration for export.
The VMS should allow export of a single video clip or multiple clips to a cart.
4 For downloading a single clip, it should have encryption option for the
exported clip and should ask to select the export format such as AVI, MJPEG,
MP4 and AVF.

Video Export Functions

It should be possible export the video clip in a tamper-proof format by adding

1 watermark and encryption to the exported video to verify the authenticity of
the video.

Page 267 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Export of single frame of video in BMP, GIF, TIF, JPG and PNG formats and
2 export of video files in commonly used video formats and Print images, with
optional comments.

VMS should allow the users to download multiple segments of the video from
single or multiple cameras from the archive with an option to tag each
3 downloaded segment with text messages. The Video segments should be
downloaded in a single folder along with excel spreadsheet where details of
each of the video segments are listed as hyperlinks to the exported video.

The Client Viewer should allow an operator to export audio together with
4
video in the AVI or other standard format.

Web and Mobile Clients

The VMS should have web client which should work on all the leading browsers
1
immaterial of the operating system.

The VMS should have mobile client for Android and IOS platforms and should
2
be available from the respective Play Store and App Store.

3 The web application should support HLS and MJPEG streaming.

It should be possible to track mobile app users on GIS map from a central
4 location. The Mobile App user should be able to track the other Mobile App
users on the GIS Map.

It should have view link sharing within authenticated users from the web
5 application. The VMS web interface user can forward video link URL by email
to another user.

The mobile client should allow uploading of the snaps and video clips from
6 within the application to the central VMS. The central VMS should show the
uploaded snaps and videos from the mobile users.

The VMS should have push notifications for the alerts for the mobile and web
7 clients to push the event notifications from the central VMS. The alert
notification should also stream the video clips associated with the alert.

Health Monitoring, Audit Trail, Problem Reporting Functions

Page 268 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The system should support CCTV video footage auditing & investigation to
reduce the data size for disaster recovery purposes , Create a well-
1
categorized searchable institutional library & Report in
PowerPoint/Word/PDF/Excel

The system should have capability to sit as a 'stack' over any live or recorded
video feed from multiple cameras and convert the same into images by
capturing screenshots in the background, at an interval of one or more
2
seconds, thereby reducing the number of frames to be viewed, i.e., creating
a summary without missing any scene, and creating huge reduction of data
size for disaster recovery

The desktop client should show system health dashboard with vital system
parameters for Database Server, Recorder Servers, Local Workstation and all
3
the available storage locations. The client should show real time CPU Core
Usage and RAM Utilization.

The system should be able to generate incident/audit finding reports in

4
PowerPoint that deliver data analytics (business intelligence) in Excel.

The system should be able to import any kind of photo/image and offer a
5
template for easy sharing of mugshots in Word/PDF.

The system should allow ease of tagging of exceptions/audit/investigation

6
findings and creating an institutional library of the same for future reference.

The VMS should show the real time workstation CPU and Memory utilization on
7 the screen along with the color changing System Health Status icon which
indicates real time health updates from the surveillance system.

8 The systems should have following features for reporting and system health:

Camera SLA report showing uptime, recording percentage, recording status,

9
critical events, incident video, etc.

Detailed listing of all active or incoming alarms with filtering options time
10
period, alarm source, operator and alarm state.

11 Generate audit trail reports by incident.

12 Give full audit trail of the user activities in the system.

Page 269 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
13 The system log should be searchable by Level, Source and Event Type.

The Audit Log should record remote user activity searchable by User name,
14
Audit ID, Source and Location

The Alert Log should record alerts triggered by rules and searchable by Alert
15
type, Source and Event type

The Event Log should record event-related information searchable by Service

16
Name, Source and Event Type

The Rule Log should record rules in which the Make new <log entry> action
17 been specified (searchable by Service name, Source, Event type and Rule
name)

The VMS should allow raising support tickets from the Help menu. It should be
18 possible to attach a screenshot of the error for effective communication of
the problem being reported.

The VMS should allow recording of the desktop activity into a movie clip to
19 effectively explain the problems being faced to report the support related
issue.

The VMS should allow the administrator or an operator to record an activity

20 happening in multiple cameras into a single movie clip which help in
improving the security function and the security SOP creation activity.

The VMS should allow the administrator to record the screen activity into a
21 movie clip to create visual manual to explain various functionalities to the new
users for training purpose.

22 API and Integration Functions

The VMS should be able to integrate with external devices such as various
23 types of Cameras, Access Control, Perimeter Intrusion Detection, IP Speakers,
, etc.

The system should be able to push the images to the user’s cloud. Such
24
images can also be used to train AI models.

Page 270 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The VMS should show integrated devices in a list on the operator screen. The
25 events generated from the integrated devices should be available for
viewing.

The VMS should allow easy configuration options to connect to the external
devices for integration and should also have granular control on the alert
26
types to receive based on the information exposed by the external devices
through the API or SDK calls.

The VMS should provide an Open API based integration gateway without any
additional cost or licensing. The API should be able to send the information
27
about various aspects of the VMS system to the external application
requesting the information. The API should provide functions such as:

Find servers, registered users, alert types and alerts, available channels,
channel ID, count, status, type, PTZ cameras and PTZ controls, get event
28
count, event search, event snap ID, event video clip, camera live video play,
playback video play, trigger an event, activate or suspend a device, etc.

The API should support HTTPS based REST API with cryptographic controls to
29
establish secure connection between web and mobile users.

Video Analytics :
Below functionalities can be achieved on integration of VMS with in-built/third party VA.

• System shall have the capability to provide various alarms & triggers and should notified
if any incidence/violation happens.
• The System shall be a real-time video analytics engine that utilizes advanced image
processing algorithms to turn video into actionable intelligence.
• The system shall provide configurable detection zones and lines to detect events of
interest, Detection zones define an area of interest and Detection lines define a perimeter
instead of a region.
• The system shall facilitate creating multiple zones and lines in a single scene to trigger
various alerts
• The system shall allow the configuration of applicable rules and manage them
• The system shall also enable editing the Zones and lines to the desired shape or size.
• The triggers generated by the applied rules shall provide visual indicators to identify the
event. Such as a Green colored Bounding Box changing the Bounding Box colour to Red
on event

Page 271 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• The system shall enable detecting rules in the defined areas (zones/ lines)
• The system shall provide functionality for configuring timelines for various events such as
Crowd Detection, Loitering Detection etc.
• The system shall allow classification of different objects like animals, vehicles and people
• VAS should allow to add, edit, delete or disable and enable Policies.
• System shall have a sophisticated rule-based engine with powerful analytics capabilities
that provides automatic event notification.
• Proposed system needs to have the capability to deploy intelligent video analytics software
on any of selected cameras. This software should have the capability to provide various
alarms & triggers.
• Following video analytics and features should be supported based on licensing:

Perimeter Trip wire/Crossing Virtual line

• Should capture zoomed image of the object causing the Perimeter Breach and
raises appropriate alarm.
• Should also stores the time duration between the pre and post event of the
Perimeter Breach.
• Should have the Option Drawing Single/Multiple Lines along with Defining Logic
for the Multiple Lines.
Loitering Detection

• Should automatically detect objects/Person that has moved continuously within

the camera field of view for a configurable period of time.
• The VA System should have the capability to detect loitering incidents in crime
hotspot areas.
AI Based Unattended Object Detection

• Should detect and generate an alert highlighting Suspicious detected when

carried into the scene and planted by a person as well as when dropped or
thrown into the scene for a Period of time that is considered suspicious by the user.
• Should be able to Detect Multiple object that are left Stationary in a Scene, the
System shall be to detect multiple objects each with its own timer as per the
predefined detection time. Alarms of each Individual Objects Abandoned shall
be alerted Individually.
• The VA should be intelligent to understand the existing objects within the camera
field of view and should generate an alert only when a new object is detected for
more than the preconfigured duration of time.
AI Based Classification of objects like person, vehicle, or animals

• VA can perform object classification once the camera has been calibrated.
Object classification is based on properties extracted from the object including
object area and speed.
AI Based Tripwire/intrusion detection

• Detection of intruder entering/exiting a given area of interest.

Page 272 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 • Once verified and confirmed by operator that it is a rouge object, the system
shall be able to track the person across various cameras and to find the origin
of such person.

AI Based Camera Tampering Detection

• 1. Alert to be generated when camera is tampered by way of change of Field

of view of camera, blurring of view, blocking of view by cloth or obstruction,
camera disconnection, blinding of camera by laser or flashlights.

• 2. Once alert is generated, the incident should be flagged, and system should
have the capability to trace the person responsible for the sabotage in other
cameras and send notification to concerned authority.

AI Based asset protection, Grouping, crowding and Person waving.

AI based no helmet detection, Triple ride detection, no seat belt detection and accident
detection
System must be capable to support below use cases
Garbage Bin Full and Cleared Detection
Detection of Debris on the Road
Detection of Stray Animals on Road
Attribute search Analytics (Search person by Dress , Attire, appearance , age etc)
Video Summarisation

6.10.2 City Surveillance fixed Camera Specifications

Compliance
# Parameter Minimum Specifications or better
(Yes / No)

Make:

Model:

1 Image Sensor 1/2.8” 2MP Progressive Scan CMOS or better

2 Day/ Night Operation Yes with IR Cut Filter

3 Minimum Illumination Color: 0.015 lux or better ; B/W 0 Lux with IR

Auto IRIS 2.8-12 mm (+/- 1mm) Motorized Varifocal

4 Lens
Lens or better

5 Electronic Shutter 1/10 to 1/12,000s or better

6 Image Resolution 1920x1080 or better

7 Compression H.265 or better

Frame Rate and Bit Upto 60 fps with Controllable bit rate, frame rate
8
Rate and Maximum Bit rate

Page 273 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Minimum 3 Nos, individually configurable
9 Video Streams simultaneous streams in H.265 @ 1920x1080 & upto 60
Fps

H: 119.5°(Wide)~27.9°(Tele), V:
10 Angular Field of View
62.8°(Wide)~15.7°(Tele), T: 142.1°(Wide)~32.0°(Tele)

Built in 8 point polygonal zones areas in the video

11 Motion Detection
stream.

Lens/ Barrel Distortion

12 Correction & Corridor Built in feature required
View

13 Wide Dynamic Range 150 dB or better

14 IR Viewable Length 50 Meter or better (Built in or External) IR

15 Alarm 1 Input & 1 Output

Selectable(Mic in/Line in), Supply voltage:

16 Audio In
2.5VDC(4mA), Input impedance: 2K Ohm

17 Audio Out Line out, Max. output level: 1Vrms

G.711 u-law /G.726 Selectable

G.726(ADPCM) 8KHz, G.711 8KHz
18 Audio Compression
G.726 : 16Kbps, 24Kbps, 32Kbps, 40Kbps
AAC-LC : 48Kbps at 16KH

Can be achieved via VMS and VA:

Defocus detection, Directional detection, Fog

19 Analytics detection, Face detection, Motion detection, Digital
auto tracking, Appear/Disappear, Enter/Exit,
Loitering, Tampering, Virtual line, Audio detection,
Sound classificationand others.

Alarm input, Motion detection, Analytics, Network

20 Event Triggers
disconnect

FTP, HTTP, Email notification, Edge Storage, Alarm

21 Event Actions
Output, Handover

Micro SD/SDHC/SDXC minimum of 512GB capacity

22 Edge Storage
or better

23 Protocols IPv4, IPv6, TCP/IP, UDP/IP, RTP(UDP), RTP(TCP),

RTCP,RTSP, NTP, HTTP, HTTPS, SSL/TLS, DHCP, FTP, SMTP,
ICMP, IGMP, SNMPv1/v2c/v3(MIB-2), ARP, DNS,
DDNS, QoS, PIM-SM, UPnP, Bonjour , LLDP, SRTP

HTTPS(SSL) Login Authentication, Digest Login

24 Security Authentication, IP Address Filtering, User access Log
802.1X Authentication(EAP-TLS, EAP-LEAP)

Page 274 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The firmware upgrade shall be done though web
25 Firmware Upgrade interface, The firmware shall be available free of
cost

26 Interface RJ 45, 100 Base TX or better

27 Memory 1024 MB RAM, 256 MB Flash or better

28 Enclosure IK10 & IP67 or Nema4x or better

29 Power requirements Vendor to specify, POE Preferred

Operating
30 -30 °C to 55 °C or better
Temperature

31 Operating Humidity Max 90% RH or better

32 Certification UL, CE, FCC,BIS,

1. The interface shall be available for integration

Application with 3rd party analytics and applications in public
33
Programmers Interface domain
2. ONVIF

Deleted
34

35 Mount Wall Mount/ Pole Mount

36 Warranty Minimum 5 Years

37 Defog Available

Page 275 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 6.10.3 City Surveillance PTZ Camera Specifications

Compliance (Yes
S. No. Description Desired Parameter / No)

Make:

Model:

1 Imaging Device 1/2.8" 2MP Progressive scan CMOS or better

2 Resolution 1920x1080, 1280x1024, 1280x960, 1280x720,

1024x768, 800x600, 800x448, 720x576,
720x480, 640x480, 640x360, 320x240 or better

3 Max. Framerate H.265 or better/H.264: Max.

60fps/50fps(60Hz/50Hz) MJPEG: Min.
30fps/25fps(60Hz/50Hz)

4 Min. Illumination Color: 0.02Lux(F1.6, 1/30sec) BW: 0Lux(IR LED)

5 Focal Length (Zoom 4.45~222.4mm or better

Ratio)
30x Optical Zoom, 10X digital zoom or better

6 Max. Aperture Ratio F1.6(Wide)~F6.5(Tele)

7 Angular Field of View H: 58.6°(Wide)~1.23°(Tele) / V:

34.8°(Wide)~0.71°(Tele)

8 Lens Type DC auto iris, Varifocal or better

9 Pan Range 360˚ Endless

10 Pan Speed Preset: 400˚/sec, Manual: 0.024˚/sec~250˚/sec

11 Tilt Range 95˚(-5˚~90˚)

12 Tilt Speed Preset: 250˚/sec, Manual: 0.024˚/sec~250˚/sec

13 Sequence Preset(300ea), Swing, Group(6ea), Trace, Tour,

Auto Run, Schedule

14 Preset Accuracy ±0.2˚

15 Day & Night Auto(ICR)

16 Backlight BLC, HLC, WDR, SSDR

Compensation

17 Wide Dynamic Range 120dB or better

18 Digital Image Support (built-in gyro sensor)

Stabilization

Page 276 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
19 Defog Available

20 Motion Detection 8ea, polygonal zones Support

21 Privacy Masking 24ea, rectangular zones

22 White Balance ATW / AWC / Manual / Indoor / Outdoor

23 Electronic Shutter Minimum / Maximum / Anti flicker

Speed (2~1/12,000sec)

24 Analytics Defocus detection, Directional detection, Fog

detection, Face detection, Motion detection,
Digital auto tracking, Appear/Disappear,
Enter/Exit, Loitering, Tampering, Virtual line,
Audio detection, Sound classification, Shock
detection and others. Can be achieved via
VMS and VA

25 Interface RS-485/Ethernet

26 Alarm I/O Input 4ea / Output 2ea

27 Alarm Triggers Analytics, Network disconnect, Alarm input

28 Alarm Events File upload via FTP and e-mail Notification via e-
mail
SD/SDHC/SDXC or NAS recording at event
triggers Alarm output
PTZ Preset

29 Audio In Selectable(mic in/line in)

Supply voltage: 2.5VDC(4mA), Input
impedance: 2K Ohm

30 Audio Out Line out, Max. output level: 1Vrms

31 IR Viewable Length 500m or better

32 Auto Tracking Available

33 Ethernet RJ-45(10/100BASE-T), SFP(Optional)

34 Video Compression H.265/H.264: Main/Baseline/High, MJPEG

35 Audio Compression G.711 u-law /G.726 Selectable G.726(ADPCM)

8KHz, G.711 8KHz
G.726: 16Kbps, 24Kbps, 32Kbps, 40Kbps AAC-
LC: 48Kbps at 16KHz

36 Bitrate Control H.264/H.265: CBR or VBR MJPEG: VBR

37 Streaming Unicast (20 users) / Multicast Multiple streaming

(Up to 10 profiles)

Page 277 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
38 Protocol IPv4, IPv6, TCP/IP, UDP/IP, RTP(UDP), RTP(TCP),
RTCP, RTSP, NTP, HTTP, HTTPS, SSL/TLS, DHCP, FTP,
SMTP, ICMP, IGMP, SNMPv1/v2c/v3(MIB-2), ARP,
DNS, DDNS, QoS,
PIM-SM, UPnP, Bonjour

39 Security HTTPS(SSL) Login Authentication Digest Login

Authentication
IP Address Filtering User access log
802.1X Authentication (EAP-TLS, EAP-LEAP)

40 Application ONVIF
Programming
Interface

41 Edge Storage Micro SD/SDHC/SDXC 1 no. slot of 512GB

capacity each or better with minimum 512GB
memory card.

42 Operating minus 50°C~+55°C / Less than 90% RH

Temperature /
Humidity

43 Ingress Protection IP66, IK10

Shock and Vibration
Resistance

44 Input Voltage 24VAC, HPoE

45 Power Consumption 24VAC: Max. 92W HPoE: 60W

46 Certification UL, CE, FCC, BIS, EMC, UL CAP,

47 Warranty Minimum 5 years

6.11 Smart Kiosks

S. No. Indicative Requirement Description Compliance (Yes / No)

Make:

Model:

Self Service Kiosks shall have integrated:

· Emergency Call Box function (with Camera and Microphone)

· MIFARe or equivalent Card Reader

· Contact less EMV Card reader

1
· Touch Screen for availing services with in-built interactive platform

Page 278 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 · Speaker

· Onscreen Keyboard

· Printing of any receipts and bus tickets etc.

· Kiosk structure (shell)

· 3G/ 4G /5G/ Wi-Fi Module

· QR code / Bar code Interface

All these components shall be supplied as part of the integrated multi

services digital kiosk.

Self-service Tourist Information Kiosk shall be fixed units, embedded inside

2
the ground that shall be weather-proof

3 The design of Kiosk terminal shall be based on the City’s heritage theme

The Emergency Call Button (ECB) shall have the capability to trigger
emergency communications with Integrated Command and Control
4 Centre (ICCC). As the Emergency Call Button is pressed, the call should
land up to the operator at ICCC from where it may be routed to the
concerned department.

The ICCC shall able to monitor the video of the user who triggered the
5 ECB. Automatic video recording shall be enabled when ECB button is
pressed at Self-service Tourist Information Kiosk.

The user-interface panel shall built-in capacitive touch screen for

interactive purposes including but not limited to:

· City Guide: This component displays the city information, about city,
business hubs etc. Places near me services which may include hotels,
government offices, shops, tourist attraction, etc.

· Tourist Destination: This component displays the list of tourist destinations in

the city along with the navigation map

· View Hotels: This component displays the list of hotels in the city with
facilities and tariffs etc. with relevant filters

· View Restaurants: This component displays the list of hotels in the city with
6 facilities and tariffs etc. with relevant filters

· View Tourist Packages: This component describes the available tourist

packages

· Helpline: This component displays the helplines of Police, Fire, Ambulance,

Railways enquiry, Public Transport and Tourist Information Centre etc.

Page 279 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 · Events: This component shall have schedule of events in the city with
facility to book the tickets online

· Emergency call: This component shall allow registered users to make

emergency call to the nearest police station based on the current location
of the app user

· Public Transport Route: This component shall list Public transport route and
schedule

· Content Management to be available to admin users: This component be

used to create, update, delete content. It also covers review and approval
of content by the respective content owner

· Weather related information

7 Self-service Tourist Information Kiosk shall have capabilities for making

digital payments for:

· Tickets for the events around the city

· Hotel accommodation

· Railway and Bus tickets

The selected Agency is required to use third party portal integration for
Hotel, Travel and Event ticket booking services.

8 Self-service Tourist Information Kiosk shall have in-built receipt/ticket printer

having the functionality of printing of receipts, any other tickets, etc.

9 Self-service Tourist Information Kiosk shall have the space for providing the
static advertisement. For publishing of any advertisement, necessary
approvals shall be obtained from Purchaser

10 Self-service Tourist Information Kiosk shall be multilingual i.e. it shall support

languages such as English, Hindi and regional language

11 Self-service Tourist Information Kiosk shall be upgradable through a central

system remotely over internet

12 It shall be possible to monitor critical parameters related to health of kiosk

device remotely using the network.

13 Battery Backup of minimum 1 Hour

14 Shall accept all the leading RBI approved wallets and UPI payments

15 Kiosk enclosure shall have the space to house all the hardware
equipment required for the Kiosk including switches, batteries, printer for
receipts and other associated accessories.

Page 280 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 All the wiring shall be concealed within the Kiosk enclosure and shall not
be visible from outside

16 Kiosk Content Management Application:

Following functionality is envisaged in the Kiosk Content Management

Application:

· Provide role-based user access mechanism where an administrator can

create and manage users, user groups, roles, and role permissions

· Shall provide login module using which content authors will be able to
login and enable the creation, modification, and deletion of templates to
enable easy management of Kiosk User interface/site and page layout
and navigation

· Shall provide a WYSIWYG (What you see is what you get) editor and
provide standard Word authoring features (also known as a Rich Text
Editor) to enable an editor to add and format text, links, and images to
content areas, create tabular layouts within a text area and apply styles
without needing HTML skills

· Shall support drag and drop feature to enable easy management of

content. The editor shall support the following minimum preview and
publication functions: -

• Preview only on content editor (not visible to users)

• Save as unpublished (draft)

• Preview on Portal

• Send for approval

• Approve

• Publish after approval (i.e. after successful completion of the

approval workflow)
• Unpublish (save as unpublished, not visible to users)

• Publication scheduling

• Publication expiration date (automatic unpublish)

• Shall contain a content approval workflow to enable the approval

of modifications (create, modify, delete) before publication (i.e.
before becoming visible to the public)

• Shall support Administrator (or a designated user with an

appropriate permission level) to assign and reassign users to
workflow tasks (i.e. define the targets within the workflow)

Page 281 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 • Layout and content shall be managed separately (i.e. it must be
possible to create and edit content without having to amend or
create a template)
17
• Shall support creation of navigation, breadcrumb and sitemap
that will be published and rendered on Kiosk User Interface

• Shall support version control (check-in, check-out, number of

versions) and it must be possible to restore previous versions of a
content item

• Shall support creation of content in different languages (namely

English, Hindi & regional language
• Shall support hierarchical creation of sites (i.e. parent/child sites in
the same domain) and enable the child site to either inherit the look
& feel of the parent site or have its own style and branding

• Shall be capable of storing and categorizing documents, images,

video and audio files.
• CMS shall support the creation of an alert in response to a specific
event, such as:
• Content amendment

• Content expiration date approaching

6.12 Local Processing Units (LPU):

Compliance
Sl.No Specification
(Yes /No)
Make :<to be provided by the bidder>
Model :<to be provided by the bidder>
1 Local Processing Unit shall be of Aluminium Alloy Casing
2 Compute: Intel Core i7, 7th Gen or better
3 LPU should have 2*Intel I210AT PCIe Gig. Ethernet
4 It shall support GPU Intel® HD Graphics 630 min.
5 Memory- DDR4 up to 16GB
6 Display Port- 1 nos. VGA, 1 nos. HDMI, 1 nos. DP
7 It shall support Secondary Storage 1*1TB 3.5”SATA HDD
8 It shall support USB- 6 nos. USB 3.0 and 2 nos. USB 2.0

Page 282 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6.13 External IR Illuminator (Optional)

Technical Specifications -External IR Illuminator

Sr.
Item Description Compliance (Yes/No)
No.
Type: External IR illuminator with high performance LED (42 Pcs.
1 high brightness IR LED), high efficiency, energy saving and
environmental protection.
2 Wavelength: ≥850 nm (Infrared)
Coverage Area: 1 Lane (standard for ANPR), up to 4 lane for
3
Surveillance
4 Illumination Range: up to 100 Mtrs.
5 Protection Level: IP66, IK10
6 IR Power: 80 W

7 Adjustable angle to appropriately focus at the number plate.

Beam Angle: multiple options- 10 degree (standard), 15, 30, 45

Degrees
8 Surge level: Common mode 6KV, Differential mode: 3 KV
9 Deleted
10 Protection function: Transient over peak suppression
11 Housing material: Die-casting aluminum alloy
12 User Interface: RS485
13 Working Temperature: -40 +70 C (working humidity 10% - 95%)
Proposed IR Illuminator should be IP66, IK10, CE, FCC, RoHS and
14
Eye & Skin safety test report IEC-62471 certified.

Power- Voltage Input: DC6~48V

Compliance
Sl.No Specification
(Yes /No)
Make :<to be provided by the bidder>
Model :<to be provided by the bidder>
1 AC Input: External Adapter (Option)
2 Voltage Input: 100VAC~240VAC@50~60Hz
3 Temperature- -20°C ~ 70°C
Page 283 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 4 It shall withstand vibrations
5 It shall withstand shock
Hardware / software should have minimum 5 year
6 warranty

6.14 Network Connectivity - OFC

It is proposed to setup city wide OFC network connectivity as the field components increases
data transfer, size also increases hence there is need for fast data transfer with high availability.

Surveillance and Security

In order to improve the quality of life for residents, the first step is safety for any city to
evolve as a Smart City. In the past few years, implementation of surveillance cameras has
improved public safety and prevented crime. However, today new types of sensors are
installed and those are way too advanced than basic surveillance cameras and requires high
data transmitting speed. Thus, Fiber optics play a very crucial role here.

Traffic Control

Traffic is one of the most significant challenges in the cities that are experiencing rapid growth.
Thus, the need for fiber Optics is increasing, as it’s used at many places in order to tie together
the enormously complex networks that control sensors like the Automatic traffic lights,
Variable message sign board, cameras and ATCS systems technology. The sensors at
Junctions and video with analytic functionality provide real-time data on Traffic congestion
while the traffic control cameras are connected by fibre optics to the transport authority. They
can monitor traffic in real time, making the control centre more efficient and intelligent for
them to increase or reduce the frequency of green lights according to the traffic conditions.

Integrated Command and Control Center

ICCC can be connected with City field components through fiber optic internet. ICCC have the
ability to provide centralized services, security, climate control, etc. Here fiber optic cables
provide the best means of handling this data and transmitting it around a facility.

Cities around the globe have been transforming from traditional to smart cities that will benefit
everyone. Fibre optics and IoT are substantial and helping us get one step closer to this reality.
Reliability, security and speed are key to the efficient implementation of Smart cities and IoT
and fibre optics are one of the first real time solutions available today.

Network Layers

Street Layer

All the access layer devices like outdoor network access points, cameras for surveillance,
environmental sensors, VaMS, PAS including other Smart city initiatives will connect to
ruggedize industrial grade access switches in street cabinets and will create street layer
architecture. Street layer architecture should be built considering the harsh outdoor
deployment environment and should be flexible to connect various devices/ sensors to the

Page 284 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
citywide transport network.

City Network Layer

The city network layer aggregates street access switches and access points and connects to
the data center and other locations used for monitoring and managing the infrastructure.
Network layer will create transport network for City and will laid down the foundation for all
the present and future urban services. This layer will provide City scalability to both expand
existing services and roll out new services as and when required without any dependency on
any service provide bandwidth operation cost. Also this layer provides the flexibility to run
multiple concurrent services with required segregation and prioritization.
Data Center Layer

The data center layer includes all our WAN routers, core switches, servers, and storage
resources for citywide applications and service. Data center layer will be the heart of City
operation will host all the Citizen services and provide the centralized processing for the same.

Considering the above requirement new OFC network is proposed as per BoM.

7 Approach and methodology to be adopted for implementation:

• The SI shall first carry out a detailed survey to identify & finalize the locations,
requirements vis-a-vis proposed solutions.

• Post completion of Survey the SI shall consult the various Stake Holder of the project, in
consultation with the Authority, and revalidate the scope mentioned in this document.
Upon freezing the scope requirement, the SI shall detail out the final functional
requirement for each of the proposed ICT intervention and get a sign off from the
user department and the Authority.
• Post finalization of the SRS and FRS the SI shall submit a High-Level Design Document
which shall cover the broad architecture and a solution document for each of the proposed
ICT interventions. The HLD will comprise of the compute, storage and the OS
requirements.

Page 285 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
• Post HLD, the SI shall be submitting the Low-Level Design Document with the good for
construction drawing, network connectivity drawing, LPU details, if any, API for
integration, communication protocol etc.

• Upon approval of LLD by the Authority, the SI shall implement the said ICT intervention.

• While implementing the ICT intervention the SI shall adopt the following:

Scalability - The system should also support both vertical and horizontal scalability. There must
not be any system- imposed restrictions on the upward scalability in number of field devices,
or other smart city components. The Applications proposed for various vertical solutions shall
be capable of handling 50% growth for the next 5 years. SI shall clearly quantify the
expansion capabilities of the application software without incurring additional cost.
Availability -. The SI shall make the provision for high availability for all the services of the
system. Redundancy has to be considered at the core components level. The SLA for various
solutions is explained under each solution itself .

Security- 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. 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 endeavour to make use of the SSL/VPN technologies to have secured communication
between Applications and its end users.

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
supplied under this project.

The security services used to protect the solution shall include: Identification, Authentication,
Access Control, Administration and Audit and support for industry standard protocols. 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 OWASP top 10
principles. All the field devices will be X.509 certified for compliance to policy change
management and to ensure that there is no default password.

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 growth
of the environment. Network should be auto/manual configurable for various future
requirements for the ease of maintenance / debugging.
Interoperability - The system should have capability to take feed from cameras installed by
private / Govt. at public places, digitize (if required) & compress (if required) this feed & store
as per requirements.

Open Standards - Systems should use open standards and protocols to the extent possible

Single Sign On- The application should enable single-sign-on so that any user once
authenticated and authorized by system is not required to be re-authorized for completing
Page 286 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
any of the services in the same session. For employees of the department concerned, the
browser-based application accessed on the intranet, through single-sign-on mechanism, will
provide access to all the services of the departments concerned (based on their roles and
responsibilities), Help module, basic and advanced reporting etc. Similarly, for external users
(citizens, etc), based on their profile and registration, the system shall enable single-sign on
facility to apply for various services, make payments, submit queries /complaints and check.
Support for 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.
Interoperability Standards- 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, through the use of
proprietary ‘stored procedures’ belonging to a specific database product. The standards
should:

At least comply with the published e-Governance standards, frameworks, policies and
guidelines available on http://egovstandards.gov.in (updated from time-to-time); and

Be of leading industry standards and /or as per standards mentioned in the technical
specifications

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.
Standards should (a) at least comply with published e-Governance standards, frameworks,
policies and guidelines available on http://egovstandards.gov.in (updated from time-to-
time); and (b) be of leading industry standards and /or as per standards mentioned in the
technical specifications

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.
iii. SI shall design and develop the Smart City System as per the Functional and System
requirement specifications finalized.

iv. The Modules specified will be developed afresh based on approved requirement.

8 Lifecycle of implementation of ICT intervention:

Following are the main activities to be carried out I:
Page 287 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
1. Project Planning, execution and Management

2. Assessment and Gap analysis of requirement for all smart city components under scope.

3. Solution Design, System Customization and development for all components mentioned
in this volume.

4. ICT items Procurement, deployment and commissioning

5. Site Preparation including required civil work, LAN Networking

6. Application and general awareness Training

7. Business Process Reengineering for the selected applications/ services, if required

8. STQC Certification

9. UAT & Go live

10. Capacity Building
11. Technical Support
12. Operation & Maintenance (O&M) for 5 Years.

9 Detailed Technical and Non-Technical Manpower:

The project requires being setup initially in an implementation phase spanning about nine
months and to be operated and maintained for a further 60 Months period to transform the
departments of stakeholders of PSCDL into a fully digitized way of operations. This requires a
highly skilled expertise in all the envisioned ICT technical function areas both during the
implementation phase and in the operations and maintenance phase.

The Key experts are listed in the table below along with their functional roles and an
approximate period of implementing the envisioned solution.

To implement and successfully execution of project below is the man months required
for both Implementation and O&M phase

Manpower for
1 Implementation Phase and TYPE UoM QTY
O&M

1.1 Project Manager - 1 no Service Number 1

Solution Architect and Cloud

1.2 Service Number 1
expert - 1 no

ICCC / command center Expert -

1.3 Service Number 1
1no

1.4 Network Architect - 1 no Service Number 1

Security Infrastructure and

1.5 Service Number 1
CCTV specialist - 1 each

1.6 GIS Expert - 1 no Service Number 1

Data Management Expert /

1.7 Service Number 1
Analyst - 1 no

Page 288 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Business Analyst/Use case/SOP
1.8 Service Number 1
Expert - 1 no

Server / Storage/ Database

1.9 Service Number 1
Expert - 1 no

1.10 ITMS & ATCS Expert - 1 no Service Number 1

1.11 Electrical Engineer - 1 Person Service Number 1

1.12 Electrical Technician - 2 Person Service Number 2

1.13 OFC Expert - 1 no Service Number 1

1.14 Helpdesk operator (20 no) Service Number 20

1.15 Security staff (4 no) Service Number 4

1.16 Civil Technician - 2 person Service Number 2

1.17 Civil Engineer - 1 no Service Number 1

1.18 Field Engineer - 5 Persons Service Number 5

1.19 Office staff, Reception (3 no) Service Number 3

10 Use cases to be deployed / integrated:

# Use cases to be deployed

1 ICCC Platform
2 Intelligent Traffic Management System
3 City Surveillance with video analytics
4 Variable Message Display
5 PA system
6 Environmental Sensors
7 Smart Poles (with CCTV, Wi-Fi, AQM, Smart Street Light, ECB, PA, Digital Billboard)
8 Citizen Mobile App and Web Portal with Tourist/Visitors platform
9 City Data Collaboration Platform
10 Smart Kiosk
11 Smart Parking (Additional Deployment as per requirement of DRDM/ PSCDL)
12 EMS
13 Flood monitoring through Flood sensors and cameras
14 GIS Platform
15 OFC
16 Social Media
17 Chat bot
18 Digital assistant Application with ICCC platform Integration
19 Configurable Dashboard

Page 289 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Sl.No Integration of Existing Applications
1 Applications hosted by NIC
2 E-Governance Platform (Property Tax, Building Approval, Birth/Death,
Marriage etc.,)
3 Electrical SCADA
4 e-Health
5 Websites hosted by Puducherry Municipality and Oulgaret Municipality
6 Solid waste Management
7 Water/ Sewage SCADA
8 ERSS (Dial 100/112)
9 Applications hosted by Disaster Management
10 Transport Monitoring Centre
11 Integration with RTO
12 Any other integration as suggested by the Puducherry authorities (up to 12
months from the date of issue of LOA to the SI)

10.1 Digital Assistant Application

In order to ensure that the impact of Smart City investments impacts the common man and
creates smart livelihoods a platform for enabling unemployed youth to be digital entrepreneur
is envisaged While connectivity is the first stage of digital inclusion , enabling digital
transactions would be the right metric to evaluate the access to digital services . Statistics
indicate that only about 3% of the population actually carry out transactions and reap the
benefits of digital world.

It is proposed to depute one technical engineer at one of the smart kiosk location as “ Digital
assistant “to assist the local community to carry out transactions on the net for E-governance
services, tickets, assisted E- commerce , last mile aggregation services and “ Phygital “
interface for other upstream services such as finance , credit , health care etc.

11 Training, Audit and Change Management Plan:

Training and Change Management is highly critical component for implementation of Smart
City Solutions. The objective of Training and Change Management initiatives is to empower
the direct users and other stakeholders of DRDM and Puducherry Smart City Corporation
Limited to optimally use the system and ensure achievement of end objectives of various Smart
City Solutions.

In order to strengthen the staff, structured capacity building programs shall be undertaken for
multiple levels in the organizational hierarchy like foundation process/ soft skills training to the
staff for pre-defined period. Also, refresher trainings for integrated Command Control Centre,
City Operation Staff and designated departments shall be a part of Capacity Building. It is
important to understand that training needs to be provided to each and every staff personnel
of ICCC. These officers shall be handling emergency situations with very minimal turnaround
time. Some directions with regards to the training and change management plan which will
need to be prepared by the implementing solution provider are as follows:

1. Appropriate training shall be carried out as per the User Training Plan prepared in detail
stating the number of training sessions to be held per batch of trainees, course work for

Page 290 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 the training program, coursework delivery methodologies and evaluation methodologies in
detail.
2. End user training shall include all the equipment including but not limited to all the
applications and infrastructure at ICCC, ITMS, Safety and Surveillance and other smart
solutions. End user training shall be conducted at a centralized location or any other
location as identified by PSCDL.
3. Imparting operational and technical training to internal users on solutions being
implemented to allow them to effectively and efficiently use the surveillance system.
4. Preparation of the solution specific training manuals and submit the same to purchaser for
review and approval. Training Manuals, operation procedures, visual help-kit etc. shall be
provided in English language.
5. Ensuring that all concerned personnel receive regular training sessions, from time to time,
as and when required. Refresher training sessions shall be conducted on a regular basis.
6. An annual training calendar shall be prepared and shared with the Client along with
complete details of content of training, target audience for each year etc.
7. Updating training manuals, procedures manual, deployment/Installation guides etc. on a
regular basis (Quarterly/ Biannual) to reflect the latest changes to the solutions
implemented and new developments.
8. Ensuring that training is a continuous process for the users. Basic computer awareness,
fundamentals of computer systems, basic, intermediate and advanced application usage
modules shall be identified by the solution provider.
9. Systematic training shall be imparted to the designated trainees that shall help them to
understand the concept of solution, the day-to-day operations of overall solution and
maintenance and updating of the system to some extent. This shall be done under complete
guidance of the trainers provided by the solution provider.
10. Training sessions and workshops shall comprise of presentations, demonstrations and
hands-on mandatorily for the application modules.

12 Proposed Governance Model:

The proposed project governance structure would comprise the following:

• High level steering committee, Board members of PSCDL, DRDM and Senior Executives of
RailTel
• Project specific working group, comprising the respective departmental functional, RailTel
Project Manager and select team members for the respective module(s).
• Core team members, domain specialists and designated counterpart staff from PSCDL/
concerned Government Agency for individual modules.
• Support team

The steering committee would meet once every month to take important decisions and
approve any strategic decisions to ensure timely implementation and address identified
bottlenecks. The project specific working groups would convene on a weekly or a bi-weekly
basis to discuss progress and address any issues pertaining to implementation.

13 Exit Management Under Contract Completion:

1. Provide a comprehensive exit management plan.

2. Before 6 months prior to the contract ending, SI shall ensure fully train Puducherry

Page 291 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Authorities’ staff or any other agency designated by Puducherry Authorities who is
designated to take over the maintenance of the System.
3. The SI shall ensure for transferring all the knowledge regarding the Systems, technically
and operationally to enable the new agency/ Puducherry Authorities to carry out the
requisite functions.
4. All latest operations & technical manuals, configuration files, software, licenses, as-built
drawings etc. shall be handed over to Puducherry Authorities at least 3 months before
contract completion.
5. The Parties may, if mutually agreed, extend the contract in accordance with the terms and
conditions.
6. All source codes/API, backup data, Puducherry Authorities specific information shall be
handed over to Puducherry Authorities as part of exit management.
7. All ICT systems shall be properly handed over to Puducherry Authorities in operational state
as part of exit management.
8. The SI shall be responsible for providing the tools for import /export of VMs & content and
the SI shall be responsible for preparation of the Exit Management Plan and carrying out
the exit management / transition.
9. SI shall be responsible for migration of the VMs, data, content and any other assets to the
new environment and ensuring successful deployment and running of the Puducherry
Authorities’ solution on the new infrastructure by suitably retrieving all data, scripts,
software, virtual machine images, and so forth to enable mirroring or copying to industry
standard media
10. The format of the data transmitted from the cloud service provider to the new environment
created by the Puducherry Authorities should leverage standard data formats whenever
possible to ease and enhance portability.
11. The SI shall transfer the organizational structure developed during the Contract Duration
to support the delivery of the Exit Management Services. This will include: Document,
update, and provide functional organization charts, operating level agreements with Third-
Party contractors, phone trees, contact lists, and standard operating procedures. Transfer
physical and logical security processes and tools, including cataloguing and tendering all
badges and keys, documenting ownership and access levels for all passwords, and
instructing Puducherry Authorities or its authorized representative in the use and operation
of security controls.
12. Retain the data at the end of the Contract.
13. Once the exit process is completed, remove the data, content and other assets from the
cloud environment and destroy the VM, Content and data of Puducherry Authorities.
14. The ownership of the data generated upon usage of the system, at any point of time during
the Contract or expiration of the Contract, shall rest absolutely with Puducherry Authorities.
15. This sets out the provisions, which will apply on expiry or termination of the Master Service
Agreement, the Project Implementation, Operation and Management SLA.
16. In the case of termination of the Project Implementation and/or Operation and
Management, the Parties shall agree at that time whether, and if so during what period,
the provisions of this Schedule shall apply.
17. The Parties shall ensure that their respective associated entities carry out their respective
obligations set out in this Exit Management Schedule.

Page 292 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
14 Detailed work Phases and considerations

14.1.1 Phase 1(Implementation Phase)

14.1.1.1 Requirement Survey Phase

The SI must perform the detailed assessment of the IT Solution requirements as mentioned
in this RFP. Based on the understanding and its own individual assessment, SI shall develop
& finalize the System Requirement Specifications (SRS) in consultation with RAILTEL / DRDM/
PSCDL and its representatives. While doing so, SI at least is expected to do following:

i. SI shall develop the FRS and SRS documents.

ii. SI shall develop and follow standardized template for requirements capturing and
system documentation.
iii. SI must maintain traceability matrix from SRS stage for the entire implementation.
iv. SI must get the sign off from the various departments of Puducherry.
v. Prior to starting the site clearance, the SI shall carry out survey of field locations as
specified in Annexure VIII, for buildings, structures, fences, trees, existing installations,
etc.
vi. 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 PSCDL guidelines. Road
signs, street name plate, etc. damaged by the SI during their operation shall be repaired
or replaced by SI at no additional cost.

14.1.1.2 Design Phase

The SI shall build the solution as per the Design Considerations detailed in Section 6. The
solution proposed by SI should comply with the design considerations requirements as
mentioned therein.

14.1.1.3 Project Development Phase

Software (Configuration and Customization). Following need to be adhered:

1) SI will be responsible for supplying the application and licenses of related software and
installing the same so as to meet project requirements.
2) The SI shall perform periodic audits to measure license compliance against the number of
valid End User software licenses consistent with the terms and conditions of license
agreements, volume purchase agreements, and other mutually agreed upon licensed
software terms and conditions. The SI shall report any exceptions to license terms and
conditions at the right time to PSCDL/DRDM. However, the responsibility of license
compliance solely lies with the SI. Any financial penalty imposed on PSCDL/DRDM during
the contract period due to license non-compliance shall be borne by SI.

3) SI shall also supply any other tools & accessories required to make the integrated solution
complete as per requirements. For the integrated solution, the SI shall supply:

Page 293 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
a) Software & licenses.
b) Supply tools, accessories, documentation and provide a list of the same. Tools and
accessories shall be part of the solution.
c) System Documentation: System Documentation both in hard copy and soft copy to be
supplied along with licenses and shall include but not limited to following.Documentation to
be maintained, updated and submitted to PSCDL/DRDM/RailTel regularly:
• Functional Requirement Specification (FRS)
• High level design of whole system
• Low Level design for whole system / Module design level
• System Requirements Specifications (SRS)
• Any other explanatory notes about system
• Traceability matrix
• Technical and product related manuals
• Installation guides
• User manuals
• System administrator manuals
• Toolkit guides and troubleshooting guides
• Other documents as prescribed by PSCDL/DRDM/RailTel
• Quality assurance procedures
• Change management histories
• Version control data
• SOPs, procedures, policies, processes, etc. developed for PSCDL/DRDM/RailTel
• Programs
• Entire source codes
• All programs must have explanatory notes for understanding
• Version control mechanism
• All old versions to be maintained
• Test Environment
• Detailed Test methodology document
• Module level testing
• Overall System Testing
• Acceptance test case

These documents need to be updated after each phase of project and to be maintained updated
during entire project duration. The entire documentation will be the property of PSCDL/DRDM.

14.1.1.4 Integration Phase

The Command-and-control center should be integrated with feeds of all component under the
ICCC Project. The SI shall provide the testing strategy including traceability matrix, test cases
and shall conduct the testing of various components of the software developed/customized
and the solution-as-a-whole. The testing should be comprehensive and should be done at each
stage of development and implementation.
Page 294 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
14.1.1.5 Go-Live Preparedness and Go-Live

i. SI shall submit signed-off UAT report (issue closure report) ensuring all issues raised
during UAT are being resolved prior to Go-Live.

ii. SI shall ensure that Go –Live criteria as mentioned in User acceptance testing of Project
is met and SI needs to take approval from the Authorities on the same.

14.1.1.6 Project Management & Facilities Management Services

The SI will be required to provide facilities management services to support the

PSCDL/DRDM/RailTel and stakeholder department officials in performing their day-to-day
functions related to this system.

SI is required to depute a dedicated, centralized project management and technical team for
the overall project management and interaction with PSCDL and stakeholder departments.

14.1.1.7 Provision of the Operational Manpower & Contact Center

Manpower to view the various data feeds and call center operations at ICCC
The SI is required to provide suitable manpower to monitor the data feeds ICCC and support
PSCDL/DRDM/RailTel, Traffic Police and other stakeholder departments for operationalization
of smart solutions of the project. The exact role of these personnel and their responsibilities
would be defined and monitored by PSCDL/DRDM/RailTel and respective departmental
personnel. SI shall be required to provide such manpower meeting following requirements:

i. All such manpower shall be minimum graduate pass

ii. All such manpower shall be without any criminal background / record.
iii. PSCDL/DRDM/RailTel 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.
iv. SI shall have to replace any person, if not found suitable for the job.
v. All the manpower shall have to undergo training from the SI for at least 15 working
days on the working of project. Training should also cover dos & don’ts and will have
few sessions from PSCDL/DRDM/RailTel and Stakeholders/End User Department
officers on right approaches for monitoring the feeds & providing feedback to
PSCDL/DRDM/RailTel, Stakeholders/End User Department officers and other
associated government agencies.

Detail operational guideline document shall be prepared during implementation which

shall specify detail responsibilities of these resources and their do’s & don’ts.

14.1.1.8 Basic Infrastructure Services

Following services shall be provided by the SI under the basic infrastructure services:

Page 295 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
i. Ensure availability of the infrastructure (both physical and IT) including but not limited to
Power, Cooling, Racks, Storage and other peripheral equipment installed at the time of
Project commissioning as per the SLAs.
ii. Ensure scalability in terms of availability of racks and supporting infrastructure.
iii. Proactive and reactive maintenance, repair and replacement of defective components
(physical and other peripheral IT infrastructure) installed for the Project through this RFP.
The cost for repair and replacement shall be borne by the SI.
iv. Any component (Physical & IT installed at the time of Project commissioning) that is
reported to be faulty / non-functional on a given date should be either fully repaired or
replaced by temporary substitute (of equivalent configuration) within the time frame
agreed upon in the Service Level Agreement (SLA).
v. Proactive monitoring of the entire basic infrastructure installed.
vi. SI shall maintain records of the maintenance of the basic infrastructure and shall maintain
a logbook on-site that may be inspected by the PSCDL/DRDM/RailTel, Police department
and other stakeholder departments/end users at any time.

14.1.1.9 Network Monitoring Services

The activities shall include:

i. SI shall provide services for management of ICCC Project to maintain performance at

optimum levels on a 24 x 7 basis.
ii. SI shall monitor and administer the network.
iii. SI shall create and modify VLAN, assignment of ports to appropriate applications and
segmentation of traffic.
iv. SI shall carry out break fix maintenance of the LAN cabling or maintenance work requiring
civil work.

14.1.1.10 Integration Testing

This shall be a black-box testing role primarily to ensure that the application to be deployed
does not disrupt the Puducherry operations and affect other Puducherry infrastructure in
terms of performance and security. The technical tasks to be carried out shall be as follows:

i. Functional Testing: Ensuring that the application functionality as described by the

PSCDL/DRDM/RailTel, Police department and other stakeholder departments/end users.
The functional testing of application will necessarily be minimal as this is a core
responsibility of the Supplier.
ii. Performance Testing: Ensuring that the application meets expressed performance
requirements on the Puducherry servers by using performance test tools and performance
monitoring tools.
iii. Security Testing: Testing for exploitable application security weaknesses that undermine
the application security or the security of the infrastructure.

Page 296 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
14.1.1.11 Vendor Management Services

The activities shall include:

i. Coordination with all the project stakeholders to ensure that all Puducherry activities are
carried out in a timely manner.SI shall coordinate and follow-up with all the relevant
vendors to ensure that the issues are resolved in accordance with the SLAs agreed upon
with them.
ii. SI shall also ensure that unresolved issues are escalated to respective departments.
iii. SI shall maintain database of the various vendors with details like contact person,
telephone nos., escalation matrix, response time and resolution time commitments etc.
iv. SI shall draw a consolidated quarterly SLA performance report across vendors for
consideration of the PSCDL/DRDM/RailTel, Police department and other stakeholder
departments/end users.

14.1.1.12 Network Management

The objective of this service is to ensure continuous operation and upkeep of the Network
infrastructure of the project including all active and passive components. The selected SI shall
be responsible to coordinate with Network Service Provider for network related issues between
ICCC, DC and other sub systems. The services to be provided for Network Management
include:

i. Ensuring that the network is available 24x7x365 as per the prescribed SLAs for the 5
years of operations after final acceptance testing of all equipment’s and services.
ii. Attending to and resolving network failures and snags.
iii. Support and maintain the overall network infrastructure including but not limited to LAN
passive components, routers, switches etc.
iv. Configuration and backup of network devices including documentation of all
configurations.
v. 24x7x365 monitoring of the network to spot the problems immediately.
vi. Provide information on performance of Ethernet segments, including capacity utilization
and error statistics for the segment and the top-contributing hosts, WAN links and
routers.
vii. Ensuring timely information to the PSCDL/DRDM/RailTel, Police department and other
stakeholder departments/end users pertaining to issues of Network Backbone

14.1.1.13 Physical Infrastructure Management and Maintenance Services

All the devices that will be installed in the 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 Infrastructure on one integrated console. The physical
infrastructure management and maintenance services shall include:
i. Proactive and reactive maintenance, repair and replacement of defective components (IT

Page 297 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 and Non-IT/ Hardware and Software). The cost for repair and replacement shall be borne
by the SI.
ii. The SI 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 SI to have back to back arrangement with the OEMs. The SI
needs to provide a copy of the service level agreement signed with the respective OEMs.
iii. 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 SI fails to meet the
above standards of maintenance, there will be a penalty as specified in the SLA.
iv. The selected SI shall also maintain records of all maintenance of the system and shall
maintain a logbook on-site that may be inspected by the PSCDL/DRDM/RailTel, Police
department and other stakeholder departments/end users at any time.

14.1.2 Phase-2 (Operations and Maintenance)

Success of the Project would lie on how professionally and methodically the entire Project is
managed once the implementation is completed. From the SI perspective too, this is a critical
phase since the quarterly payments are linked to the SLA’s in the post implementation phases.
SI shall provide operations and maintenance services for the software, hardware and other IT
and Non-IT infrastructure installed as part of the project after Go-Live for a period of 5 years.
Warranty period of the product supplied under project i.e. hardware, software, IT/Non-IT etc.,
will be considered after phase wise Go-Live.

14.1.3 Project Management and Governance

14.1.3.1 Project Management Office (PMO)

A Project Management office will be set up during the start of the project. The PMO will, at
the minimum, include a designated full time Project Manager from SI. It will also include key
persons from other relevant stakeholders including members of PSCDL/DRDM/RailTel and
other officials/representatives by invitation. The operational aspects of the PMO need to be
handled by the SI including maintaining weekly status, minutes of the meetings,
weekly/monthly/project plans, etc.

PMO will meet formally on a weekly basis covering, at a minimum, the following agenda items:
i. Project Progress
ii. Delays, if any – Reasons thereof and ways to make-up lost time
iii. Issues and concerns
iv. Performance and SLA compliance reports;
v. Unresolved and escalated issues;
vi. Project risks and their proposed mitigation plan
vii. Discussion on submitted deliverable
viii. Timelines and anticipated delay in deliverable if any
ix. Any other issues that either party wishes to add to the agenda.

Page 298 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
During the development and implementation phase, there may be a need for more frequent
meetings and the agenda would also include:

i. Module development status

ii. Testing results
iii. IT infrastructure procurement and deployment status
iv. Status of setting up/procuring of the Helpdesk, DC hosting
v. Any other issues that either party wishes to add to the agenda.

Bidder shall recommend PMO structure for the project implementation phase and operations
and maintenance phase.

14.1.3.2 Helpdesk and Facilities Management Services

The SI shall be required to establish the helpdesk and provide facilities management services to
support the PSCDL/DRDM/RailTel and stakeholder department officials in performing their day- to-
day functions related to this system.

The SI shall setup a central helpdesk dedicated (i.e. on premise) for the Project, which shall be
supported by individual smart city command centres, implemented and proposed to be setup
under Puducherry Smart City Programme. This helpdesk would be operational upon
implementation of the Project. Providing helpdesk/support services from a shared facility of any
other party/provider is not permitted.

Functional requirements of the helpdesk management system fully integrated with the
enterprise monitoring and network management system. The system will be accessed by the
stakeholder department officials for raising their incidents and logging calls for support. The
detailed service levels and response time, which the SI is required to maintain for provisioning
of the FMS services are described in the Service Level Agreement of this Tender.

SI shall deploy Manpower during implementation and O&M phases. The deployed resource
shall report to PSCDL/DRDM/RailTel’s Project In-charge for Smart City Project and work
closely with Program Management Office of the project. Following are the minimum resources
required to be deployed in the Project, however SI may deploy additional resources based on
the need of the Project and to meet the defined SLAs in this RFP:

Note: Numbers provided for staff providing 24*7 support is excluding relievers.

14.1.3.3 Project Monitoring and Reporting

The SI shall circulate written progress reports at agreed intervals to PSCDL/DRDM/RailTel and other
stakeholders. Project status report shall include Progress against the Project Management
Plan, status of all risks and issues, exceptions and issues along with recommended resolution
etc.
Other than the planned meetings, in exceptional cases, project status meeting may be called
with prior notice to the Bidder. PSCDL/DRDM/RailTel reserves the right to ask the bidder for
the project review reports other than the standard weekly review reports.

Page 299 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
14.1.3.4 Risk and Issue management

The SI shall develop a Risk Management Plan and shall identify, analyze and evaluate the
project risks, and shall develop cost effective strategies and action plans to mitigate those
risks.

The SI shall carry out a Risk Assessment and document the Risk profile of
PSCDL/DRDM/RailTel based on the risk appetite and shall prepare and share the
PSCDL/DRDM/RailTel Risk Register. The SI shall develop an issues management procedure to
identify, track, and resolve all issues confronting the project. The risk management plan and
issue management procedure shall be done in consultation with PSCDL/DRDM/RailTel.

The SI shall monitor, report, and update the project risk profile. The risks should be discussed
with PSCDL/DRDM/RailTel and a mitigation plan be identified during the project review/status
meetings. The Risk and Issue management should form an agenda for the Project Steering
Committee meetings as and when required.
14.1.3.5 Governance procedures

SI shall document the agreed structures in a procedure’s manual.

14.1.3.6 Planning and Scheduling

The SI will prepare a detailed schedule and plan for the entire project covering all tasks and
sub tasks required for successful execution of the project. The SI has to get the plan approved
from PSCDL/DRDM at the start of the project and it should be updated every week to ensure
tracking of the progress of the project.

The project plan should include the following:

i. The project breaks up into logical phases and sub-phases;

ii. Activities making up the sub-phases and phases;
iii. Components in each phase with milestones;
iv. The milestone dates are decided by RailTel in this RFP. SI cannot change any of the
milestone completion dates. SI can only propose the internal task deadlines while keeping
the overall end dates the same. SI may suggest improvement in project dates without
changing the end dates of each activity.
v. Key milestones and deliverables along with their dates including those related to delivery
and installation of hardware and software;
vi. Start date and end date for each activity;
vii. The dependencies among activities;
viii. Resources to be assigned to each activity;
ix. Dependency on PSCDL/DRDM/RailTel

14.1.3.7 License Metering / Management

The SI shall track software usage throughout the IT setup so as to effectively manage the

Page 300 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
risk of unauthorized usage or under-licensing of software installed at the ICCC. This may be
carried out through the use of standard license metering tools.

14.1.4 Change Management & Control

14.1.4.1 Change Orders / Alterations / Variations

i. The SI agrees that the requirements given in the Bidding Documents are minimum
requirements and are only indicative. The SI would need to fetch out the details at the
time of preparing the design document prior to actual implementation. It shall be the
responsibility of the SI to meet all the requirements of technical specifications contained
in the RFP and any upward revisions and/or additions of quantities, specifications sizes
given in the Bidding Documents required to be made during execution of the works, shall
not constitute a change order and shall be carried out without a change order and shall
be carried out without any time and cost effect to Purchaser.

Further upward revisions and or additions required to make SI’s selected equipment
andinstallation procedures to meet Bidding Documents requirements expressed and to
make entire facilities safe, operable and as per specified codes and standards shall not
constitute a change order and shall be carried out without any time and cost effect to
Purchaser.

ii. Any upward revision and/or additions consequent to errors, omissions, ambiguities,
discrepancies in the Bidding Documents which the SI had not brought out to the
Purchaser’s notice in his bid shall not constitute a change order and such upward revisions
and/or addition shall be carried out by SI without any time and cost effect to Purchaser.

14.1.4.2 Change Order

i. The Change Order will be initiated only in case (i) the Purchaser directs in writing the SI toinclude
any addition to the scope of work covered under this Contract or delete any part of the
scope of the work under the Contract, (ii) SI requests to delete any part of thework which will
not adversely affect the operational capabilities of the facilities and if the deletions proposed
are agreed to by the Purchaser and for which cost and time benefitsshall be passed on to the
Purchaser, (iii) the Purchaser directs in writing the SI to incorporate changes or additions
to the technical specifications already covered in theContract.

ii. Any changes required by the Purchaser over and above the minimum requirements given
in the specifications and drawings etc. included in the Bidding Documents beforegiving its
approval to detailed design or Engineering requirements for complying with technical
specifications and changes required to ensure systems compatibility and reliability for safe
operation (As per codes, standards and recommended practices referred in the Bidding
Documents) and trouble free operation shall not be construed to be change in the Scope of
work under the Contract.

Page 301 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
iii. Any change order as stated in this RFP comprising an alteration which involves changein the
cost of the works (which sort of alteration is hereinafter called a “Variation”) shall be the
Subject of an amendment to the Contract by way of an increase or decrease inthe schedule
of Contract Prices and adjustment of the implementation schedule if any.
iv. If parties agree that the Contract does not contain applicable rates or that the said ratesare
inappropriate or the said rates are not precisely applicable to the variation in question,
then the parties shall negotiate a revision of the Contract Price which shall represent the
change in cost of the works caused by the Variations. Any change ordershall be duly approved
by the Purchaser in writing.

v. Within ten (10) working days of receiving the comments from the Purchaser or the
drawings, specification, purchase requisitions and other documents submitted by the SI
for approval, the SI shall respond in writing, which item(s) of the Comments is/are
potential changes(s) in the Scope of work of the RFP document covered in the Contract
and shall advise a date by which change order (if applicable) will be submitted to the
Purchaser.

14.1.5 Testing and Acceptance Criteria

i. SI shall demonstrate the following mentioned acceptance criteria prior to acceptanceof the
solution as well as during project operations phase, in respect of scalability andperformance
etc. The SI may propose further detailed Acceptance criteria which the PSCDL/DRDM will
review. Once PSCDL/DRDM provides its approval, the Acceptance criteria can be finalized.
In case required, parameters might be revised by PSCDL/DRDM in mutual agreement with
bidder and the revised parameters shall be considered for acceptance criteria. A
comprehensive system should be set up that would have the capability to log & track the
testing results, upload & maintain the test cases and log &track issues/bugs identified.

ii. The following table depicts the details for the various kinds of testing envisaged for the
project:

Note:

a. Bidder needs to provide the details of the testing strategy and approach including details
of intended tools/environment to be used by SI for testing in its technical proposal.
RAILTEL/ DRDM/ PSCDL does not intend to own the tools.

b. The SI shall work in a manner to satisfy all the testing requirements and adhere to the
testing strategy outlined. The SI must ensure deployment of necessary resources and
tools during the testing phases. The SI shall perform the testing of the solution based on
the approved test plan, document the results and shall fix the bugs found during the
testing. It is the responsibility of SI to ensure that the end product delivered by the SI

Page 302 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 meets all the requirements specified in the RFP. The SI shall take remedial action based
on outcome of the tests.

c. The SI shall arrange for environments and tools for testing and for training as envisaged.
Post Go-Live; the production environment should not be used for testing and training
purpose. If any production data is used for testing, it should be masked, and it should be
protected. Detailed process in this regard including security requirement should be
provided by the SI in its technical proposal. The process will be finalized with the selected
bidder.

d. All the Third-Party Auditors (TPA) as mentioned above will be appointed and paid by
RAILTEL / DRDM/ PSCDL directly. All tools/environment required for testing shall be
provided by the SI.

e. STQC/Other agencies appointed by RAILTEL / DRDM/ PSCDL shall perform the role of TPA.
SI needs to engage with the TPA at the requirement formulation stage itself. This is
important so that unnecessary re-work is avoided, and the audit is completed in time. The
audit needs to be completed before Go-Live of different phases. SI needs to prepare and
provide all requisite information/documents to third party auditor and ensure that there
is no delay in overall schedule.
f. The cost of rectification of non-compliances shall be borne by the SI.

14.1.6 Factory Testing

SI shall have to submit Factory Test Certificate for the below mentioned materials before
the actual supply of the items.

i. Cable
ii. Pole
iii. Signal Aspects

Authorized representative from RAILTEL / DRDM/ PSCDL will visit the manufacturing plant of
the product subject to present in India. Authorized representative will check the testing
process.

14.1.7 Final Acceptance Testing

The final acceptance shall cover 100% of the I Project, after successful testing by the RAILTEL
/ DRDM/ PSCDL, Police Department, other stakeholders/end user department or its PMU; a
Final Acceptance Test Certificate (FAT) shall be issued by the RAILTEL/ DRDM/ PSCDL to the
SI.

Prerequisite for Carrying out FAT activity:

i. Detailed test plan shall be developed by the SI and approved by RAILTEL / DRDM/ PSCDL.
This shall be submitted by SI before FAT activity to be carried out.

Page 303 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
ii. All documentation related to ICCC Project and relevant acceptance test document
(Including IT Components, Non-IT Components etc.) should be completed & submitted
before the final acceptance test to the RAILTEL / DRDM/ PSCDL.
iii. The training requirements as mentioned should be completed before the final acceptance
test.
iv. Successful hosting of Application, NMS and MIS Software.
v. For both IT & Non-IT equipment’s / software manuals / brochures / Data Sheets / CD /
DVD / media for all the Puducherry Project supplied components.

The FAT shall include the following:

I. All hardware and software items must be installed at respective sites as per the
specification.
II. Availability of all the defined services shall be verified.
III. The SI shall be required to demonstrate all the features / facilities / functionalities as
mentioned in the RFP.
IV. The SI shall arrange the test equipment required for performance verification and will
also provide documented test results.
V. The SI shall be responsible for the security audit of the established system to be carried
out by a certified third party as agreed by RAILTEL / DRDM/ PSCDL.

Any delay by the SI in the Final Acceptance Testing shall render him liable to the imposition
of appropriate Penalties. However, delays identified beyond the control of SI shall be
considered appropriately and as per mutual agreement between RAILTEL / DRDM/ PSCDL and
SI. In the event the SI is not able to complete the installation due to non-availability of
bandwidth from the bandwidth service providers, the Supplier and RAILTEL / DRDM/ PSCDL
may mutually agree to redefine the Network so the SI can complete installation and conduct
the Final Acceptance Test within the specified time.

15 Annexure III: Project Milestones and Payment Schedules for Implementation

Project Implementation and Timelines

Payments will be paid to SI on awarding the contract on back-to-back basis on receipt
of payments from client against the invoices submitted by SI.

The contract Management & Paying Authority shall be Corporate Office, RailTel Corporation of India,
New Delhi
The implementation timelines for the project components are as given below.
T = Date of signing of Contract Agreement
G= Go-Live Date

The Payment schedule and milestones are divided into two phases:
i. Implementation phase

Page 304 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 ii. Operations and maintenance phase

Based on findings of the Feasibility Study done by the SI, the SI may propose a change in the
number of sites or individual units to be deployed in each phase as well as overall scope and a
consequent change in phasing. PSCDL also retains the right to Suo-moto change the number of
sites or individual units to be deployed for each scope item. The final decision on change in phasing
and related change in payment schedules shall be at the discretion of PSCDL.

Payment Milestones for Payment Time

Milestone Deliverable
Implementation Schedule Schedule

M1 Contract / Work Order NA T NA

M2 Project Kickoff NA T+7 NA
days

M3 Site Survey NA T+1 1. Project Implementation Plan.

2. Site Survey report
month
3. Final BoQ
4. Inception Report

M4 Solution design signoff NA T + 45 1. Functional Requirement

days Specification document 2.
System Requirement
Specification document 3.
Requirements Traceability
Matrix 4. High Level Design
documents 5. Low Level
Design documents

Page 305 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
M5 Supply of IT and Non-IT Infra and 50%% of the T+3 1. Infra and Systems
systems pertaining to all the Capex Cost months delivery report (
Solution components. on pro-rata delivery challan).

Basis 2. Material inspection

report signed by the
Authority.

3. Tax Invoice

4. Packing list

5. QA/COQ

6. Inspection Certificate

7. Consignee receipt

8. Warranty Certificate of
OEM

9. Insurance certificate

10. Certificate duly signed

by firm certifying that
equipment/materials
being delivered are new
and conformed to
technical specification

11. Undertaking for fall

clause

M6 Installation and Commissioning of 25%of the T+5 Installation and commissioning

Capex Cost certificate duly signed by RailTel

1. General Surveillance. months
official, Customer and SI.
2. ITMS

3. Other Smart solution

Page 306 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 components

4. OFC Connectivity

5. ICCC

6. Any other CAPEX items.

M8 Completion of Integration of Smart 25% of the T+6 1. UAT report

2. Training Completion report
devices and existing applications Capex Cost months
3. Go-live certificate.
with ICCC and Go-Live

M9 Operations and maintenance 100% of the 5 years 100% of the Opex cost

Opex cost from Go- equally spread across

Live quarterly payments in arrears

from Go-
Live .

Note:

i. In cases of fire or any major accidents caused due to the negligence, omissions and
commissions of the SI in any of the installations, the liability is on SI for his commissions and
omissions in the interim and final ICCC, DC deployments and operations during the O&M phase
of sixty months.

ii. It is fixed by a third party auditor on the part of the SI, the claims shall be a minimum of the
loss fixed by any third party auditor including the loss of lives, data, equipment, etc. added
cumulatively on dues from the SI and will be recovered from the SI.

iii. Single component / multiple components Go-Live shall be awarded on successful completion of
the respective component(s) and integration of respective component with ICCC.

iv. In case of partial achievement of the project milestone, the payment shall be made
proportionately.

v. SI is required to provide comprehensive O&M of 5 years from the date of Go-Live provided for
multiple components / single component outlined in the RFP.

vi. All payments to the Implementation Vendor shall be made upon submission of invoices along
with necessary approval certificates from the concerned Authority like PSCDL/DRDM.

vii. In case of Internet Bandwidth (ISP services), System Integrator need to submit the invoices
from Internet Service Provider (ISP) in the name of Tender Inviting Authority.

Mobilization Advance

Page 307 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
The Authority will, if requested by the CONTRACTOR, make mobilization advance payments subject
to approval and receipt of advance from the client of 10(%) percent of the Awarded Contract Value
to the CONTRACTOR to assist in defraying the initial expenses that will necessarily be incurred by
the CONTRACTOR for mobilization and design. The payment of mobilization advance is subject to
the approval & receipt of mobilization advance from the client. The Mobilization Advance will be
given to the CONTRACTOR with Simple Interest of 10 % (Percent) per annum.

The Advance payment will be made in two equal instalments of 5% (five percent) of the contract
price. Advance payment will be paid only after CONTRACTOR submitting unconditional and
irrevocable Bank guarantee for an amount equivalent to 110 % (one Hundred and Ten percent) of
each instalment.

The Authority’s Representative shall issue an Interim Payment Certificate for the first instalment.
The Authority will make payment of the First instalment of the mobilization advance only after the
CONTRACTOR has fulfilled the following conditions:

a) Execution of the Form of Agreement by the parties hereto and submission of Performance Security
bythe CONTRACTOR.

b) Mobilized the Project Manager for the Contract.

c) Established and staffed a functional design liaison office at Puducherry city.

After the first instalment of the advance payment has been utilized as per the approved Programme,
and to the satisfaction of the Authority’s Representative, the CONTRACTOR may then apply for the
Second instalment.

The Authority will make payment of the Second installment after the CONTRACTOR has successfully
fulfilled the following conditions:

a) Submitted the proposed Implementation Programme for approval by the Authority’s

Representative.

b) Submitted, for approval by the Authority’s Representative, mobilization/ deployment schedules

for:

i. CONTRACTOR’s key personnel required for managing, executing and supervising the Works,

ii. CONTRACTOR’s Plant, Machinery and Equipment required for executing the Works; and

iii. Procurement Schedule for materials to be incorporated into the Permanent Works.

c) Submitted a Cash Flow Forecast for approval by the Authority’s Representative.

d) Submitted a list of proposed, suppliers and manufacturers, along with their credentials, for
approval by the Authority’s Representative.

Page 308 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
e) Submitted details of funds mobilized by himself as per the Cash Flow Forecasts.

f) Actual deployment of: (i) such Personnel, (ii) Machinery and Equipment,

g) Established the fully furnished Site office.

h) Placed confirmed orders for supply of major items of material which is to be incorporated into
the Permanent Works as per the approved procurement schedule.

i) Commenced construction work at the Site in accordance with the approved construction
program.

Deduction of Mobilization Advance: Mobilization advance shall be deducted starting from Second
Interim Payment certificate @ of 10 % (Percent) of the certified amount of Interim payment
certificate and to be recovered fully prior to the time when 90 percent (90%) of the work is
completed.

A bank Guarantee of 110 (%) percent against the Mobilization advance is to be submitted. The
mobilization advances and interest on it shall be adjusted and recovered in the Interim Payment
Certificates raised by the Contractor for the work completed as mentioned above. The bank
Guarantee submitted against mobilization advance has to be valid till completion of the work. In
case, the Contractor fails to mobilize necessary manpower, machinery, materials and any
necessary procurement or purchase to start the preliminary work, the bank guarantee against
mobilization advance may be forfeited and will lead to the termination of contract.

15.1 Quality Assurance

A thorough quality check is proposed for the Puducherry Project and its modules, as per standard
Software Development Life Cycle (SDLC). SI is expected to lay down a robust Quality Assurance
program for testing of the developed application for its functionality, performance and security
before putting in production environment. The program must include an overall plan for testing
and acceptance of system, in which specific methods and steps should be clearly indicated and
approved by RAILTEL & PSCDL. SI is required to incorporate all suggestions / feedback provided
after the elaborate testing of the system, within a predefined, mutually agreed timeline. SI must
undertake the following:

i. Outline the methodology that will be used for testing the system.
ii. Define the various levels or types of testing that will be performed for system.
iii. Provide necessary checklist/documentation that will be required for testing the system.
iv. Describe any technique that will be used for testing the system.
v. Describe how the testing methodology will conform to the requirements of each of the
functionalities and expected outcome.
vi. Indicate / demonstrate to RAILTEL & PSCDL that all applications installed in the system have
Page 309 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 been tested.

16 Annexure V : Guidelines

Common guidelines regarding compliance of the system / equipment:

i. The functional requirements and technical specifications provided in the below sections and at
other sections in this RFP are indicative and carry guiding rule. The SI is free to offer products
and solutions which meet requirements of the RFP focusing on the outcome, future scalability,
security, reliability and adherence to specified SLA under this RFP, in line with applicable
standards & best practices adopted in the industry. The SI is encouraged to design an
Optimised solution which is technically superior, innovative, proven, better in terms of
functionality and is cost effective. Any specified parameters mentioned in the scope/technical
requirement in the RFP may be considered if it is required for meeting current & future
requirements during the contract period. The SI is fully responsible for the specified outcome
to be achieved.
ii. The specifications mentioned for various IT / Non-IT components are indicative requirements
and should be treated for benchmarking purpose only. SIs are required to undertake their own
requirement analysis and may propose higher specifications that are better suited to the
requirements.

iii. In case of addition/update in number of license for the Integrated Command and Control
Centre (ICCC) software and VMS licenses for Cameras, the SI is required to meet of technical
specifications contained in the RFP and for the upward revisions and/or additions of licenses
is required be made as part of change order and cost would be commensurate to the itemized
rate approved at the LOI issuance.

iv. Any manufacturer and product name mentioned in the Tender should not be treated as a
recommendation of the manufacturer / product.

v. None of the IT / Non-IT equipment’s proposed by the SI should be End of Life product. It is
essential that the technical proposal is accompanied by the OEM certificate in the format given
in Volume I of this Tender, where-in the OEM will certify that the product is not end of life
product & shall support for at least 6 years from the date of Bid Submission.

vi. All IT Components should support IPv4 and IPv6

vii. Technical Bid should be accompanied by OEM’s product brochure / datasheet. SIs should
provide complete make, model, part numbers and sub-part numbers for all
equipment/software quoted, in the Technical Bid.

Page 310 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
viii. SI should ensure that only one make and model is proposed for one component in Technical
Bid for example all Traffic Surveillance cameras must belong to a single OEM and must be of
the same model etc.

ix. SIs should ensure complete warranty and support for all equipment from OEMs. All the back-
to back service agreements should be submitted during the contract whereas MAF for all the
equipment from OEMs shall be shared along with the Technical Bid as per Format given in the
RFP.

x. All equipment, parts should be original and new.

xi. The user interface of the system should be a user friendly Graphical User Interface (GUI).

xii. Critical core components of the system should not have any requirements to have proprietary
platforms and should conform to open standards.

xiii. For custom made modules, industry standards and norms should be adhered to for coding
during application development to make debugging and maintenance easier. Object oriented
programming methodology must be followed to facilitate sharing, componentizing and
multiple- use of standard code. Before hosting the application, it shall be subjected to
application security audit (by any of the CERTIN empanelled vendors) to ensure that the
application is free from any vulnerability; and approved by the Police Department.

xiv. All the Clients Machines / Servers shall support static assigned IP addresses or shall obtain IP
addresses from a DNS/DHCP server.

xv. The Successful SI should also propose the specifications of any additional servers / other
hardware, if required for the system.

xvi. The indicative architecture of the system is given in this volume. The Successful SI must
provide the architecture of the solution it is proposing.

xvii. The system servers and software applications will be hosted in Data Centers as specified in
the Bid. It is important that the entire set of Data Center equipment are in safe custody and
have access from only the authorized personnel and should be in line with the requirements
& SLAs defined in the Tender.

xviii. The Servers provided should meet industry standard performance parameters (such as CPU
Utilisation of 60 percent or less, disk utilisation of 75 percent or less). In case any non-standard
computing environment is proposed (such as cloud), detail clarification needs to be provided
in form of supporting documents, to confirm (a) how the sizing has been arrived at and (b)
how SLAs would be met.
Page 311 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
xix. SI is required to ensure that there is no choking point / bottleneck anywhere in the system
(end- toend) and enforce performance and adherence to SLAs. SLA reports must be submitted
as specified in the Bid without fail.

xx. All the hardware and software supplied should be from the reputed Original Equipment
Manufacturers (OEMs). Department reserves the right to ask replacement of any hardware /
software if it is not from a reputed brand and conforms to all the requirements specified in the
tender documents.

xxi. Cameras, Network Video Recorder (NVR) and the Video Management / Video Analytics
Software should be ONVIF Core Specification ‘2.X’ or ‘S’ compliant and provide support for
ONVIF profiles such as Streaming, Storage, Recording, Playback, and Access Control.

xxii. SI shall place orders on various OEMs directly and not through any sub-contractor / partner.
All licenses should be in the name of the RAILTEL & PSCDL

xxiii. Technical Solution and Architecture : All the components of the Technical Architecture which
should comply with the published eGovernance standards, frameworks, policies and guidelines
available on http://egovstandards.gov.in and leading industry standards.

xxiv. Consider architecture design with respect to scalability, inter-operability , availability,

manageability and comply with framework Smart City (K-15016/61/2016-SC-1, Government
of India, and Ministry of Urban Development)

17 Annexure VI Security – General Guidelines

17.1 Security Framework

The Bidder shall develop Security Framework aimed at building a secure and resilient security
space for citizens and stakeholders of Smart City. The Framework shall be designed to protect
information and infrastructure; build capabilities to prevent and respond to attacks; and minimize
damages through coordinated efforts of institutional structures, people, processes, and
technology. Framework shall cover security architecture.

17.2 Security Policy

The policy shall address security of hardware and software, along with the connectivity between
the field device and the respective application software. The bidder shall ensure to develop and
implement Standard Operating Procedures for smooth Operations and Maintenance of IT
infrastructure.

Page 312 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 17.3 Security Governance

1. The Bidder shall conduct Risk Assessment and prepare Risk Treatment Plan for the IT
applications and infrastructure deployed in smart city ecosystem.
2. The Bidder shall facilitate management reporting in form of dashboard covering Risk
Assessment results along with risk treatment plan and timeline to the smart city
management.

3. The Bidder shall implement all the controls as identified during the Risk assessment and
treatment plan as per the agreed

17.4 Smart City IT Asset Management

1. The Bidder shall utilize automated asset management tools to prepare the information asset
register (IAR) for all IT assets deployed in the Smart city. The IAR shall capture criticality,
rating, classification, owner and custodian of the Asset.
2. The Bidder shall develop and implement an appropriate set of procedures for information
labelling and handling in accordance with the classification scheme proposed in the security
policy of smart city.

17.5 Physical & Environmental Security

4. The bidder shall implement and manage physical security of IT assets of smart city, which
shall include, as a minimum: locks, alarms, surveillance equipment, sensors, access control
systems (biometrics), etc. The bidder shall also design processes and procedures for same.
5. The Bidder shall ensure that all the equipment, information or software shall not be taken off-
site without appropriate authorization.

17.6 Access Control

1. The Bidder shall ensure that users shall be provided single sign on functionality if required for
the applications and solutions deployed in Smart City.
2. The smart city solution should support multiple authentication methods such as Username
password, two factor authentication, digital certificate and biometric based authentication.
3. The solution should be capable of being deployed on mobile devices deployed for smart city

4. Solution should have the capability to define access based on time of day, day of week or by
group or user defined access.

5. The smart city solution should have the functionality to provide authentication based on the
role.
Page 313 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
6. Remote access to all smart city IT users shall be securely managed.

7. The smart city solution should be able to deploy and configure the approved password policy
and should provide the feature to configure the logs.

8. The smart city solution should have the option of blocking multiple sessions for the user.

9. All smart city applications should support role based access control to enforce separation of
duties.
10. The application deployed in smart city should display the last login status
(successful/unsuccessful, time) to the user and should not store authentication credentials on
client computers after a session terminates
11. All smart city solution should be compliant with Indian IT Act, 2000 and Amended IT Act, 2008

17.7 Communications and Operations Management

1. Bidders must ensure that the IT systems in the smart city infrastructure are open, scalable
and interoperable. The deployed systems must operate within 4 layers – Sensory layer,
communication layer, data layer and application layer adhering to relevant security controls
as mandated by the MoUD guidelines.
2. Bidders shall ensure that all the interfaces between IoT devices, field sensors, device
applications and storage deployed in smart city are encrypted using appropriate protocols,
algorithm and key pairs.
3. All transport link communication must be encrypted and sensitive data both in rest and transit
is to be secured using encryption.
4. Bidders must ensure that all the changes made to the smart city infrastructure incl. of IoT
field devices, sensors and related applications should be tracked and recorded in order to
enable security monitoring of the infrastructure. The maintained logs should be systematically
collated, enabling the access of critical information as per date, fortnight, month, quarter,
year etc.
5. Bidders should ensure that separate environments are maintained for production, test and
development for smart city infrastructure and solutions to reduce the risks of unauthorized
access or changes.
6. Bidders must ensure that smart city IT systems are designed in such a way that only
authenticated users have access to the smart city database. Also, the provision of access has
to be routed only through designated applications.
7. Bidders must ensure that sensitive data is stored in the smart city database in an encrypted
format thereby curtailing the database administrator from reading or modifying the stored
sensitive data.

Page 314 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
8. Bidders must ensure that the smart city architecture should include a VPN solution enabling
designated users to access necessary applications and functions from remote applications.
9. Bidders must enable for the maintenance of an audit trail to record all the administrator, user
level activities including the failed attempts thereby enabling a robust high level security
monitoring of the smart city security infrastructure.
10. Bidders must ensure that the smart city components – Network elements, Operating system,
Applications etc. are in sync and adhere to a singular master clock. Thereby ensuring an
appropriate logging/ time stamping of incidents and bolstering smooth operation of the smart
city.

11. Bidders must ensure that adequate security controls are deployed against the tampering of
log information and unauthorized access to the smart city infrastructure such as the data
center, IoT device control room etc.
12. Bidders must ensure that platforms hosted in the central data center support multi-tenancy
with adequate authentication and role based access. This can be achieved by utilizing
Authentication and privilege management technology thereby controlling the access of data
as per user privileges.
13. Bidders must ensure that the smart city architecture accounts for latency issues for the flow
of data between devices. Suitable protocols should be utilized to minimize data flow latency
upon management of heterogeneous data.
14. Bidders must strictly make sure that the communication between IoT field devices and their
respective management applications happens only over a data layer (digital platform).
Thereby enabling this designated layer to be the one true source of data abstraction,
normalization and correlation.

15. Bidders must ensure that the smart city IT infrastructure including the Wi-Fi network adheres
to relevant and applicable security standards and protocols. Also, bidders must make sure
that the Application Program Interfaces (APIs) are published and the IT systems run on
standard protocols.
16. Bidders must ensure that the smart city architecture end-to-end has adequate security
controls to enforce safety, privacy and integrity of confidential data. Necessary controls must
be deployed to protect the integrity of data flowing into the control systems and other critical
infrastructure.
17. Bidders must enable for wireless/ broadband architecture used in the smart city infrastructure
to interface with other/citywide wireless networks thereby enabling interoperability.
18. Bidders must ensure that IoT field devices and sensory equipment operating within the smart
city periphery connect only to authorize wireless networks. Secure Wi-Fi guidelines as
prescribed by the Department of Telecom must be followed.
Page 315 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
19. Bidders must make sure that the wireless layer of the smart city network is appropriately
segmented, bifurcating the network into various trusted zones. Thereby segregating public
and utility networks via VPN (Virtual private networks), ensuring that the traffic from internet
users is not routed into sensor networks and vice versa.
20. Bidders must enable for the authentication of the sensory equipment during the provisioning
of the sensors and connection into the smart city infrastructure.

21. Bidders must ensure that the data aggregators used for enabling the interoperability between
field IoT devices and sensors functioning on different protocols incorporate appropriate
authentication and encryption at the aggregator gateway when field devices are not capable
of authenticating
/encrypting critical information.
22. Bidders must ensure that the IoT field devices and sensory equipment deployed in smart city
periphery must not have a physical interface for administration. System and Network
monitoring should be only performed remotely thereby ensuring local cyber-attacks/
tampering of field devices is curtailed.

23. Bidders must ensure appropriate network segregation. The smart city data center must be
systematically segmented into multiple zones. Each zone must have a dedicated functionality.
IoT field devices and sensory equipment must be connected to a completely separate network
isolated from public networks and other private networks.
24. Bidders must make sure that the internet facing segment of the data center must incorporate
a DMZ (Demilitarized zone), where customer application servers would be located. Predefined
ports must be assigned for enabling the communication between the customer application
servers and utility application servers to facilitate the access/transfer of data.
25. Bidders must ensure that Smart city data centers are well equipped with adequate security
controls to protect the confidentiality, integrity and accessibility of critical data. The center
should consider including cyber security systems such as firewalls, Intrusion detection &
Intrusion prevention systems, Web Application Firewalls, Behavioral analysis systems for
anomaly detection, Correlation engine, Denial of Service prevention device, Advanced
Persistent Threat notification mechanism, Federated identity, access management system
etc.

26. Bidders must ensure that the proposed smart city architecture provides for:
i Automatic and secure firmware updates
ii Device logging and auditing capabilities
iii Vendor self-certification for non-existence of backdoors, undocumented and hard
codedaccounts.

iv Bidders shall ensure that Data encryption at rest shall be implemented using
Page 316 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 departmentsmanaged keys, which are not stored in the cloud.

17.8 Information Systems Acquisition, Development and Maintenance

1. The Bidder shall prepare the detailed technical security requirement as part of the ‘Software
Requirement Specification’ document with secure coding guidelines for development of
applications for smart city.
2. The Bidder shall incorporate validation checks into smart city applications to detect any
corruption of information through processing errors or deliberate acts.

3. The Bidder shall obtain information about technical vulnerabilities of information systems
being used in smart city, evaluate the exposure to such vulnerabilities, and take appropriate
measures to address the associated risk.
4. The bidder shall implement maintenance and repair process of smart city IT assets in timely
manner, with approved and controlled tools.

17.9 Business Continuity Planning and Disaster Recovery

1. The Bidder shall implement and operate Disaster Recovery site for the Smart city
infrastructure and related IT & OT applications. IT & OT applications and processes should be
supported from the disaster recovery site.

2. The Bidder shall define Business Continuity and Disaster Recovery plan and will perform the
testing on a yearly basis

17.10 Information Security Audits

The bidder shall ensure Information security audits of the smart city infrastructure and related
applications by a CERT-In empaneled vendor. VA/PT (Vulnerability assessment and Penetration
Testing) activities, audits and application security testing must be carried out on once-a-year basis
ensuring optimal operation and security of the smart city infrastructure and applications. Teams
carrying out the audit exercise must be different from the implementation teams. Systematic
actionable need to be derived post audits and necessary changes need to be made periodically.

17.11 Awareness Training

The bidder shall deploy appropriate resources to support periodic awareness training based on latest
standards of ISMS in consultation with the Authorities. The trainings must focus on educating relevant
employees (including privileged users, third party, senior management etc.) on necessary security
practices and processes to be followed in order to maintain the Confidentiality, Integrity and
Page 317 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
Availability of critical data.

17.12 Security Controls for Cloud Services

The security controls for creating and managing cloud services shall comply with the following
guidelines. Empanelment of Cloud Service Offerings CSPs facilities/services shall be compliant
with regulative directives and industry best practices. The SLA shall be based on the guidelines
issued by Government Departments on contractual terms related to Cloud Services (MeitY
guideline dated 31/03/17). The security controls should include the following:

1) The CSP should be empaneled by MeitY for providing cloud services. The CSPs
facilities/services shall be certified to be compliant to the following standards: ISO 27001,
ISO 27017, ISO 27018, ISO 20000- 9, ISO/IEC 20000-1 & PCI DSS.
2) The CSP/Service Provider shall comply or meet any security requirements applicable to
CSPs/Service Providers published (or to be published) by MeitY or any standards body setup
/ recognized by Government of India from time to time and notified to the CSP/Service
Providers by MeitY as a mandatory standard.
3) The CSP/Service Provider shall meet all the security requirements indicated in the IT Act
2000, the terms and conditions of the Provisional Empanelment of the Cloud Service Providers
and shall comply with the audit criteria defined by STQC.
4) Incident Management shall be managed by CSP / third party.
5) Periodic secure code review shall be performed for cloud applications.
6) Data encryption at rest / transit depending on sensitivity of data shall be implemented using
departments managed keys, which are not stored on the cloud.
7) The CSP will undertake to treat information passed on to them as classified. Such Information
will not be communicated / published / advertised by the CSP to any person/organization
without the express permission of the Department.
8) CSP shall inform all security breach incidents to Smart City management on real time.
9) CSP shall ensure data confidentiality and mention Sub-contractual risk shall be covered by
CSP.
10) E-Discovery shall be included as clause in SLA with CSP. It is the process of locating,
preserving, collecting, processing, reviewing, and producing Electronically Stored Information
(ESI) in the context of or criminal cases/proceedings or investigation. Logging and reporting
(e.g., audit trails of all access and the ability to report on key requirements/indicators) must
be ensured.
11) The Law Enforcement Agency as mandated under any law for the time being in force may
seek access to information stored on cloud as provided by the Service Provider. The onus
shall be on the CSP to perform all due diligence before releasing any such information to any
Page 318 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 such law enforcement agency.
12) CSP must ensure location of all data related to smart cities in India only.
13) The Cloud Service Provider’s services offerings shall comply with the audit requirements
defined under the terms and conditions of the Provisional Empanelment of the Cloud Service
Providers (or STQC /MEITY guidelines. The Audit, Access and Reporting Requirements should
be as per the terms and conditions of the Provisional Empanelment of the Cloud Service.
14) CSP’s exit Management Plan shall include - Transition of Managed Services & Migration from
the incumbent cloud service provider’s environment to the new environment and shall follow
all security clauses for smooth transition.

15) SLA with CSP shall cover performance management & dispute resolution escalation.
Guidelines on Service Level Agreement issued by MeitY lists out the critical SLAs for cloud
services.
16) Identification and problem resolution (e.g., helpline, call center, or ticketing system)
mechanism must be defined.
17) Change-management process (e.g., changes such as updates or new services) must be
defined.
18) Appropriate segregation of Virtual Private Cloud (VPC) security rules defined as part of firewall
to restrict access, Role based access management, Logging and monitoring shall be ensured.
19) VPN gateway must be setup to ensure controlled access, appropriate security rules must be
employed to encrypt outward data flow, IDS, IPS, API Gateways to be setup and ELB logs to
be maintained for any activities and access and exceptions to carried out in the cloud setup,
Database logs to be routed as part of the Logging VPC setup.
20) Digital Certificate shall be implemented for secure access.
21) Web Application Firewall must be provided, Host IPS must be setup on all the Web servers,
Web servers must be configured as per the CIS hardening guidelines and baseline security
requirements, logging and monitoring should be enabled.

22) Application access between hosted smart city applications shall be segregated, internal
infrastructure and external traffic, Role based access must be defined, hardening of database
instances as per the CIS baselines configuration guidelines in the cloud setup must be
ensured, Logging and monitoring must be enabled.
23) For SLAs to be used to steer the behavior of a cloud services provider, imposition of financial
penalties is to be incorporated.
24) Monitor Vendor Service level agreement for annual end-to-end service availability of 99.999
percent. The end to end service agreement should be in place for minimum period of six years
form the date of operations of the systems.

Page 319 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 18 Annexure VI – Smart City Guidelines

Universal Access IT Systems to empower differently-abled citizens to access ICT systems with
ease

Sl. Parameters No. Minimum Requirements

Provide text alternatives for any non-text content so that it can be changed

1 Text Alternatives into other forms people need, such as large print, braille, speech, symbols or
simpler language.

All images, form image buttons, and image map hot spots have appropriate,
equivalent alternative text.
Images that do not convey content, are decorative, or contain content that is

2 Non-text Content already conveyed in text are given null alt text (alt="") or implemented as CSS
backgrounds. All linked images have descriptive alternative text. Equivalent
alternatives to complex images are provided in context or on a separate
(linked and/or referenced via longdesc) page.

3 Time-based Media Provide alternatives for time-based media.

Audio Description or A descriptive text transcript OR audio description audio track is provided for
4 Media Alternative
non-live, web-based video
(Prerecorded)
Create content that can be presented in different ways (for example simpler
5 Adaptable
layout) without losing information or structure.

Semantic markup is used to designate headings (<h1>), lists (<ul>, <ol>, and
<dl>), emphasized or special text (<strong>, <code>, <abbr>, <blockquote>, for
example), etc. Semantic markup is used appropriately.
Tables are used for tabular data. Where necessary, data cells are associated
6 Info and Relationships
with their headers. Data table captions and summaries are used where
appropriate.
Text labels are associated with form input elements. Related form elements are
grouped with fieldset/legend.
The reading and navigation order (determined by code order) is logical and
7 Meaningful Sequence
intuitive.

Page 320 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Color is not used as the sole method of conveying content or distinguishing
visual elements.
Color alone is not used to distinguish links from surrounding text unless the
8 Use of Color
luminance contrast between the link and the surrounding text is at least 3:1 and
an additional differentiation (e.g., it becomes underlined) is provided when the
link is hovered over or receives focus.

A mechanism is provided to stop, pause, mute, or adjust volume for audio that
9 Audio Control
automatically plays on a page for more than 3 seconds.

10 Resize text The page is readable and functional when the text size is doubled.

If the same visual presentation can be made using text alone, an image is not
11 Images of Text
used to present that text.

12 Keyboard Accessible Make all functionality available from a keyboard.

All page functionality is available using the keyboard, unless the functionality
cannot be accomplished in any known way using a keyboard (e.g., free hand

13 Keyboard drawing).
Page-specified shortcut keys and accesskeys (accesskey should typically be
avoided) do not conflict with existing browser and screen reader shortcuts.

Keyboard focus is never locked or trapped at one particular page element.

14 No Keyboard Trap The user can navigate to and from all navigable page elements using only a
keyboard.
Automatically moving, blinking, or scrolling content that lasts longer than 5
seconds can be paused, stopped, or hidden by the user. Moving, blinking, or
scrolling can be used to draw attention to or highlight content as long as it lasts
less than 5 seconds.
15 Pause, Stop, Hide
Automatically updating content (e.g., automatically redirecting or refreshing a
page, a news ticker, AJAX updated field, a notification alert, etc.) can be
paused, stopped, or hidden by the user or the user can manually control the
timing of the updates.

16 Seizures Do not design content in a way that is known to cause seizures.

Three Flashes or Below No page content flashes more than 3 times per second.
17
Threshold
Provide ways to help users navigate, find content, and determine where they
18 Navigable
are

Page 321 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 A link is provided to skip navigation and other page elements that are repeated
across web pages. If a page has a proper heading structure, this may be
considered a sufficient technique instead of a "Skip to main content" link. Note
19 Bypass Blocks
that navigating by headings is not yet supported in all browsers. If a page uses
frames and the frames are appropriately titled, this is a sufficient technique for
bypassing individual frames.

20 Page Titled The web page has a descriptive and informative page title.

21 Focus Order The navigation order of links, form elements, etc. is logical and intuitive.
Page headings and labels for form and interactive controls are informative.

22 Headings and Labels Avoid duplicating heading (e.g., "More Details") or label text (e.g., "First Name")
unless the structure provides adequate differentiation between them.

It is visually apparent which page element has the current keyboard focus (i.e.,
23 Focus Visible
as you tab through the page, you can see where you are).

24 Readable Make text content readable and understandable

25 Language of Page The language of the page is identified using the HTML lang attribute

The language of page content that is in a different language is identified using

26 Language of Parts
the lang attribute.

27 Predictable Make Web pages appear and operate in predictable ways.

When a user inputs information or interacts with a control, it does not result in a
28 On Input
substantial change to the page, the spawning of a pop-up window, an

additional change of keyboard focus, or any other change that could confuse
or disorient the user unless the user is informed of the change ahead of time.

Maximize compatibility with current and future user agents, including assistive
29 Compatible
technologies.
Significant HTML/XHTML validation/parsing errors are avoided. In content
implemented using markup languages, elements have complete start and end

30 Parsing tags, elements are nested according to their specifications, elements do not
contain duplicate attributes, and any IDs are unique, except where the
specifications allow these features.

Page 322 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 Markup is used in a way that facilitates accessibility. This includes following the
HTML/XHTML specifications and using forms, form labels, frame titles, etc.
appropriately.

31 Name, Role, Value For all user interface components, the name and role can be programmatically
determined; states, properties, and values that can be set by the user can be
programmatically set; and notification of changes to these items is available to
user agents, including assistive technologies.

A descriptive text transcript (including all relevant visual and auditory clues and
Audio-only and indicators) is provided for non-live, web-based audio (audio podcasts, MP3 files,
32 Videoonly (Pre-
etc.) A text or audio description is provided for non-live, web-based video-only
recorded)
(e.g., video that has no audio track).

Synchronized captions are provided for non-live, web-based video (YouTube

Captions
33
(Prerecorded) videos, etc.)
Synchronized captions are provided for all live multimedia that contains audio
34 Captions (Live)
(audio-only broadcasts, web casts, video conferences, Flash animations, etc.)
Audio descriptions are provided for all video content
Audio Description NOTE: Only required if the video conveys content visually that is not available in
35
(Prerecorded)
the default audio track.
Instructions do not rely upon shape, size, or visual location (e.g., "Click the square
Sensory icon to continue" or "Instructions are in the right-hand column"). Instructions do
36
Characteristics
not rely upon sound (e.g., "A beeping sound indicates you may continue.").
Make it easier for users to see and hear content including separating foreground
37 Distinguishable
from background.
Text and images of text have a contrast ratio of at least 4.5:1. Large text - at least

38 Contrast (Minimum) 18 point (typically 24px) or 14 point (typically 18.66px) bold has a contrast ratio
of at least 3:1.

39 Enough Time Provide users enough time to read and use content.

If a page or application has a time limit, the user is given options to turn off, adjust,
or extend that time limit. This is not a requirement for real-time events (e.g., an
40 Timing Adjustable
auction), where the time limit is absolutely required, or if the time limit is longer
than 20 hours.

Page 323 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST
 The purpose of each link (or form image button or image map hotspot) can be
determined from the link text alone, or from the link text and its context (e.g.,
Link Purpose (In surrounding paragraph, list item, table cell, or table headers). Links (or form
41
Context)
image buttons) with the same text that go to different locations are readily
distinguishable.
Multiple ways are available to find other web pages on the site - at least two of:

42 Multiple Ways a list of related pages, table of contents, site map, site search, or list of all
available web pages.
When a page element receives focus, it does not result in a substantial change

43 On Focus to the page, the spawning of a pop-up window, an additional change of

keyboard focus, or any other change that could confuse or disorient the user.
Navigation links that are repeated on web pages do not change order when
44 Consistent Navigation
navigating through the site.

Elements that have the same functionality across multiple web pages are
Consistent consistently identified. For example, a search box at the top of the site should
45
Identification
always be labeled the same way.

46 Input Assistance Help users avoid and correct mistakes.

Required form elements or form elements that require a specific format, value,
or length provide this information within the element's label. If utilized, form

47 Error Identification validation errors are presented in an efficient, intuitive, and accessible manner.
The error is clearly identified, quick access to the problematic element is
provided, and user is allowed to easily fix the error and resubmit the form.
Sufficient labels, cues, and instructions for required interactive elements are

48 Labels or Instructions provided via instructions, examples, properly positioned form labels, and/or
fieldsets/legends.

If an input error is detected (via client-side or server-side validation), provide

49 Error Suggestion
suggestions for fixing the input in a timely and accessible manner.

Error Prevention If the user can change or delete legal, financial, or test data, the
50 (Legal, Financial,
changes/deletions can be reversed, verified, or confirmed.
Data)
Alternative mode of authentication should be offered to in order to be
51 Visual Captcha
authenticated

Mandatory use of
52 Unicode for regional Unicode facilitates assistive technology to access content.
language

Page 324 of 324

Digitally signed by RAJEEV

KUMAR
Date: 2023.07.27 23:33:07 IST