Signature Not

Verified Central Video Management System (CVMS) on the Public Cloud for the IP-
Digitally signed by
ANIL RAWAT
based CCTV Surveillance System for the Indian Railways
Date: 2024.05.06
12:54:24 IST
Reason: IREPS
Document
Location: IREPS-CRIS

Selection of Master System Integrator for the Central Video Management

System (CVMS) on the Public Cloud for the IP-based CCTV Surveillance for the
Indian Railways
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Bid Document Part-II

(Special Conditions of the Contract)

for

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Page 2 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

1. Table of Contents

1. Table of Contents 3
2. Definitions 11
3. Introduction 16
3.1. About Indian Railways 16
3.2. About CRIS 16
4. Project Vision & Objective 16
4.1. Other CRIS RFPs 16
4.2. Key Objectives of CVMS 17
5. High-level Architecture 18
5.1. Edge Layer 19
5.2. Network Layer 20
5.3. CVMS Layer 21
5.4. Users of the CVMS 22
6. Scope of Work 23
6.1. Inception Phase 26
6.2. Requirement Gathering Phase & Design Phase 27
6.2.1. Requirement Gathering 27
6.2.2. Designing and Development Phase 28
6.3. Integration & Testing - Prototype Phase 31
6.4. Acceptance Tests 32
6.4.1. User Acceptance Test (UAT) 32
6.4.2. Periodic Acceptance Test (PAT) 35
6.4.3. Go-Live 37
6.5. Capacity Building 38
6.5.1. Documentation for identified users. 38
6.5.2. Help/User manuals 39
6.5.3. Manpower to be deployed for the Project 39
6.6. Operations Phase (Post Final Go-Live of the Project) 40
6.7. System Audit (Overall CVMS solution) 43
6.7.1. General Audit Requirements 43

Page 3 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

6.7.2. Technical Audit Requirements 44

6.8. Helpdesk & Training 45
6.8.1. Helpdesk 45
6.8.2. Training 47
6.9. OEM Support for the Project 51
6.9.1. OEM Involvement in Project Implementation and O&M: 51
6.9.2. OEM Support Protocols 51
7. Sizing Parameters for the CVMS Solution 52
8. Functional Specifications 57
8.1. Video Management System 57
8.1.1. Specifications 57
8.1.2. VMS KPI / Performance requirements 67
8.2. Integrated Command & Control Center application 68
8.2.1. ICCC Specifications 68
8.2.2. ICCC Modules 72
8.2.2.1. Geospatial Information System (GIS) 72
8.2.2.2. Alarm Management 76
8.2.2.3. Escalation Management 77
8.2.2.4. Alarm / Event Correlation 78
8.2.2.5. Rule Engine 78
8.2.2.6. Exception management 78
8.2.2.7. Incident Management Module 78
8.2.2.8. Reporting 80
8.2.2.9. Standard Operating Procedures (SOPs) 81
8.2.2.10. Administration Module 82
8.2.2.11. Role Based Access Control (RBAC) 82
8.2.2.12. Dashboard 83
8.2.2.13. Trend Analysis 84
8.2.3. ICCC Integrations 84
8.2.4. Information to be managed at the ICCC & Viewing Centers 85
8.3. Mobile application 85
8.4. Enterprise Management System (EMS) 87
8.5. Invoice Generation Module for the CVMS Solution Stack 96

Page 4 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

8.6. Facial Recognition Solution (FR Solution) 96

8.6.1. Specification 96
8.7. Video Summarization 104
8.7.1. Specifications 104
8.7.2. Indicative Object Search Criteria 105
8.8. Forensic Application (Image & Video enhancement) 107
8.9. Integrations of Systems 108
8.9.1. Integration with Edge Devices 108
8.9.2. Integration with Indian Railways / CRIS applications 118
8.9.2.1. General Specifications 118
8.9.2.2. Tentative List of Applications 118
8.9.2.3. Integration with Other Government applications 120
8.10. Cloud Hosting Platform 120
8.10.1. Design Consideration: Cloud Services 120
8.10.2. Managing the cloud infrastructure: 123
8.10.3. Compute 124
8.10.4. Storage 125
8.10.5. Backup Solution 126
8.10.6. Data Governance and Security 128
8.10.7. Self-Service Portal for CVMS: Management and Governance 131
8.10.8. Technical Specifications for Additional Compute and Storage 132
8.10.8.1. Virtual Machine or Compute 132
8.10.8.2. Storage (Block and Object) 132
8.11. Patch Management 133
8.11.1. Patch Management for CVMS Solution 135
8.11.2. Patch Management for Field Equipment 135
9. Qualifications Criteria 135
9.1. Master Service Integrators Qualifications 135
9.2. Documentation 144
9.2.1. Eligibility for Start-ups, MSEs and Government PSUs: 147
9.3. Cloud Service Providers (CSP) Qualification Criteria 148
9.4. CCTV Surveillance OEM Qualification Criteria 151
9.5. Technical Evaluation Criteria 159

Page 5 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

9.6. Technical Evaluation Parameters for the CSP 162

10. Proof of Concept 171
10.1. Approach for Proof of Concept (PoC) 172
10.2. Proof of Concept Workflow and Use Case 174
10.2.1. Basic ICCC Setup and Configuration 174
10.2.2. Incident Management and Workflow 179
10.2.3. Facial Recognition Use case 184
10.2.4. Video Summarization 188
10.2.5. User Management 189
10.2.6. Enterprise Management System 190
10.2.7. Low Bandwidth (Data Handling Management) 190
10.2.8. Cloud Hosting Environment 192
11. Project Management Tool (PMT) 198
12. Project Implementation Timelines 200
13. Responsibility Matrix 208
14. Service Levels 210
14.1. Service Levels Agreement 210
14.2. Measurement of SLA 211
14.3. Measurements & Targets 211
14.3.1. Definitions 211
14.3.2. Service Level Agreement (SLA) – Pre-Phase 1 Go-Live 212
14.3.3. Service Level Agreement (SLA) – Post Phase 1 Go-Live 218
15. Payment Terms, Deliverables & Timelines 244
15.1. Payment Terms 244
15.2. Documents to be submitted for Payment Claims 251
15.3. Delivery Period Extension 251
15.4. Statutory Variation Clause (SVC) 252
15.5. Completion Period of the Contract 253
16. Schedule of Requirement (SOR) 253
17. Instruction to Bidders 260
17.1. Additional Instruction to Bidders 260
17.2. Eligible Bidders 260
17.3. Pre-Bid Meeting 268

Page 6 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.4. Preparation and Submission of Proposals 268

17.5. Validity of Proposals 271
17.6. Proposal Due Date 271
17.7. Verification of Documents 271
17.8. Bidders Responsibility 271
17.9. CRIS’s Responsibility 274
17.10. Clarification Sought by Bidders 275
17.11. Deviations 275
17.12. Disqualification 275
17.13. Functional Compliance Requirement from MSI 277
17.14. Modification and Withdrawal of Proposals 277
17.15. Confidentiality 277
17.16. Clarifications Sought by CRIS 278
17.17. Priority of Clauses 278
17.18. Evaluation Methodology 279
17.18.1. Techno-Commercial evaluation 279
17.18.1.1. Step I –Commercial responsiveness &Pre-Qualification (PQ) Criteria 279
17.18.1.2. Step II - Technical Evaluation 279
17.18.2. Financial Evaluation of offers 280
17.18.3. E-Reverse Auction (e-RA) 281
17.18.4. Procedure for conducting e-RA: 283
17.18.5. Applicable important conditions after e-RA: 284
17.18.6. Notification 284
17.18.7. Performance Security 284
17.19. Contract Period 285
17.20. Long Term Support 285
17.21. Change Control 285
17.21.1. Change Management Process 286
17.22. Miscellaneous 288
17.23. Exit Management/Transition-out-service 293
17.24. Intellectual Property Rights 295
17.25. Audit, Access & Reporting 295
17.25.1. Audit Notice and Timing 296

Page 7 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.25.2. Annual OEM Audits 296

17.25.3. Access 296
17.25.4. Audit Rights 296
17.25.5. Records And Information 297
17.26. Quality Control Measures 297
17.27. Termination of the Contract 298
17.28. Documentation 300
17.29. Make In India 301
17.30. Land Border with India Compliance 302
17.31. Consignee & Address 304
17.32. Support from CRIS 304
18. Annexures 305
18.1. Annexure-1- Other CRIS Bid Documents 305
18.2. Annexure-2-Edge Layer or Field Equipment 309
18.3. Annexure-3-Network Layer 312
18.4. Annexure-4-Integration of the Applications of CRIS 314
18.5. Annexure-5-Format for Compliance of Functional Requirements 326
18.6. Annexure-6- Integration of the Edge Devices Parameters 327
18.7. Annexure-7-Bidder’s Checklist 341
18.8. Annexure-8- Bidder’s & Key OEM’s Self Information 352
18.9. Annexure-9-Format for Power of Attorney for Lead Member 353
18.10. Annexure-10-Declaration of Non-Blacklisting 356
18.11. Annexure-11-Format for Providing Eligibility Compliance 358
18.12. Annexure-12-Project Experience of the Bidder 359
18.13. Annexure-13-Project Experience of the OEM 361
18.14. Annexure-14-CV of Key Personnel Proposed 363
18.15. Annexure-15-Undertaking for Unpriced Bill of Quantity 366
18.16. Annexure-16-Format For Pre-Bid Queries 368
18.17. Annexure-17-Performance Bank Guarantee 369
18.18. Annexure-18-Change Control 372
18.19. Annexure-19-Long Term Maintenance Support 374
18.20. Annexure-20-Undertaking from OEM For Backend Support 375
18.21. Annexure-21-Non-Disclosure Agreement 376

Page 8 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.22. Annexure-22-Anti-Collusion Certificate 381

18.23. Annexure-23-Deployment of Manpower 383
18.23.1. Annexure-23(A) - Project Implementation Phase 383
18.23.2. Annexure-23(B) –Operations Phase 385
18.24. Annexure-24-Undertaking from OEM for IPR 389
18.25. Annexure-25-Total Responsibility Certificate 391
18.26. Annexure-26-Certificate Land Border with India 392
18.27. Annexure-27-Declaration for Proof of Concept 393
18.28. Annexure-28-Declaration for Project Office 395
18.29. Annexure-29-Undertaking for Valid License for Software 396
18.30. Annexure-30-CSP’s Authorization Form (CAF) 397
18.31. Annexure-31 –Agreements for JV & Consortium 398
18.31.1. Annexure-31(A) - Joint Venture Agreement 398
18.31.2. Annexure-31(B)-Consortium Agreement 402
18.32. Annexure-32-SLA of the Coaches 406
18.33. Annexure-33-SLA of Locomotives 411
18.34. Annexure-34-SLA of the EMU/MEMU 417
18.35. Annexure-35-Template for Monthly Attendance 424
18.36. Annexure-36- Local Content as per Make in India Policy 425
18.37. Annexure-37- OEMs Technical Support in India 426
18.38. Annexure-38- MeitY empanelled Cloud 428
18.39. Annexure-39-Undertaking for VMS scalable architecture. 429
18.40. Annexure-40- Integration of the VMS with more than One NVR 430
18.41. Annexure-41- Integration of ICCC with other applications. 431
18.42. Annexure-42- Certificate to be submitted by Tenderer 433
18.43. ANNEXURE-43- Certificate for I&C and Annual Audits 435
18.44. Annexure-44- Setting up of the Test Environment 441
18.45. Annexure-45-Undertaking to be provided by the Bidder & CSP 442
18.46. Annexure-46-Security Verification Certification 443
18.47. Annexure-47- PoA for signing of proposal 444
18.48. Annexure-48- Completion & Performance Certificates 446
18.48.1. Phase 1 Go-Live Completion Certificate 446
18.48.2. Final Go-Live Completion Certificate 449

Page 9 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.48.3. O&M Phase Performance Certificate 451

18.49. Annexure-49-Abbreviations 453

Page 10 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

2. Definitions
i. Public Cloud – The term "Public Cloud" in this request for proposals (bid
document Part-II) refers to the cloud services, such as Infrastructure as a
Service (IaaS), Platform as a Service (PaaS), and Software as a Service
(SaaS), that are offered in a MeitY-empanelled cloud. The computing
resources, including virtual machines, networks, security, databases,
storage, etc. are made available via the Internet by a MeitY-empanelled
cloud service.
ii. CVMS - The Central Video Management System (CVMS) is a solution
stack which is being planned by CRIS and shall be hosted on the cloud
consisting of systems and applications like the Integrated command and
control center, Video Management System, Video Analytics Engine,
Enterprise Management system and integrations with CRIS and other
applications.
iii. Integrated Command & Control Center (ICCC) – The centralised facility
hosted on the cloud is intended to monitor, manage, and control different
edge systems such as the CVVRS, CCTVSS, and RDAS installed in
Coaches, Locomotives, EMUs & MEMUs.
iv. CCTVSS – The Closed-Circuit Television Surveillance System is the video
surveillance system which is being installed in the Coaches of the various
Zones of the Indian Railways. The CCTVSS includes the IP based
Dome/Wedge Surveillance Cameras, M-NVR/VRU, Wi-Fi network
interface, Panic Button, Video FR and the dual 5 G-based SIMs (with auto-
fall back to 4G) that establish connectivity from the M-NVR/VRU to the
Public Cloud solution offered through this Bid Document Part-II.
v. CVVRS – The Crew Voice & Video Recording System is the Video
Surveillance solution which is being implemented in electric and diesel
Locomotives. The solution consists of IP based cameras comprising the
Locomotive Cab view camera, RDAS Camera, External view Camera,
front view and rear view, and roof-mounted camera for viewing the
Pantograph interaction along with Wi-Fi network interface, and dual 5 G-
based SIMs (with auto-fall back to 4G) that establish connectivity from the
NVR to the Public Cloud solution offered through this Bid Document Part-
II.
vi. RDAS – The Railway Driver Assistance System (RDAS), is a solution
which is being implemented in the Locomotives of the Indian Railways
along with the Video Surveillance System and can execute video analytics
on the live video capturing the Driver cab and raise alarms and trigger
emergency brakes if a driver shows signs of losing alertness over a certain
period.
vii. A Power User is a user who has complete access to all the available
features in a software application.

Page 11 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

viii. Mobile users: The Mobile Users within the CVMS solution are designated
as personnel located in the field, serving as the primary first responders.
Their primary responsibility is to promptly investigate and respond to alerts
generated by the Integrated Command and Control Center.
ix. Desktop users: Desktop Users within the CVMS solution are the static
users stationed at locations such as CRIS offices and Railway Protection
Force (RPF) Thanas, etc. They would be responsible for coordinating with
the field-based first responders in investigating the alerts and events
reported by the Integrated Command and Control Center.
x. Primary Integration – The primary Integration includes the integration of
the CVMS with the Edge devices installed by the Field SI (please refer to
field SI definition), integration of the software applications within the
CVMS (intra-CVMS) and the CRIS and Indian Railways applications (refer
Section Tentative List of Applications) before the declaration of Phase
1 Go-Live (please refer to Phase 1 Go-Live definition).
xi. Floating Licences - A floating license (also known as a concurrent
license) refers to a software licensing model where a limited number of
licenses are shared among multiple users or devices within a network,
meaning a certain number of devices or users can access the software
application and data at any given time. If all the licenses are in use, an
employee must wait for a floating license to become available before being
granted access.
xii. Secondary Integration – The secondary Integration indicates the CRIS,
Indian Railways (refer Section Tentative List of Applications) and other
Government applications (refer Section Integration with Other
Government applications) that shall be integrated with the CVMS
Solution post Phase 1 Go-Live.
xiii. Enterprise Management System (EMS) – The Enterprise Management
System (EMS) is a comprehensive software solution hosted on the public
cloud, capable of monitoring and managing the entire Central Video
Management System (CVMS) solution. The EMS comprises a suite of
management and observability services for thorough SLA monitoring and
management of various systems and applications within the CVMS
solution. This includes monitoring the health status of edge devices to
visualize end-to-end availability and health status.
xiv. Steady State – refers to a period of operational stability where systems
are running smoothly, and there are no major disruptions.
xv. Emergency Situations- Emergency situations refer to sudden and
unexpected events or circumstances that require immediate attention.
Emergency situations can take various forms and may include, Natural &
Man-Made Disasters, Medical & Fire Emergencies, Accidents, Civil Unrest
etc.

Page 12 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xvi. Planned Events - "Planned events" generally refer to occasions or

occurrences that have been organized or scheduled in advance. Planned
events can encompass a wide range of activities, including conferences,
meetings, parties, weddings, concerts, festivals, and more.
xvii. Edge Devices- Devices such as cameras, panic buttons, M-
NVR/NVR/VRU, Microphones, and RDAS Systems, installed in Coaches,
Locomotives, EMUs & MEMUs mentioned in the Section Annexure-1-
Other CRIS Bid Documents of the Bid Document Part-II.
xviii. M-NVR/NVR/VRU: The Video Recorder Unit, the Network Video Recorder
and the Mobile Network Video Recorder are the video recording
appliances that are planned to be installed in the field as per the RDSO
specifications.
a. Coaches - VRU/M-NVR
b. Locomotives - NVR
c. EMU: In the Coaches section - VRU/M-NVR, in the Driving Motor
Cabin - NVR
d. MEMU: In the Coaches section - VRU/M-NVR, in the Driving Motor
Cabin – NVR.
xix. EMU: An electric multiple unit or EMU is a multiple unit train consisting of
self-propelled carriages, using electricity as the motive power. An EMU
requires no separate locomotive, as electric traction motors are
incorporated within one or a number of the carriages.
xx. MEMU: Electric Multiple Unit, Diesel Electric Multiple Unit and Mainline
Electric Multiple Unit is an electric multiple unit train that serves short and
medium-distance routes in India. MEMU trains do not require separate
engines/Locomotives as the engine is incorporated into one of the
carriages.
xxi. Bidder: The Bidder in this Bid Document Part-II is the Master System
Integrator (MSI) identified through the bidding process who shall be
providing the complete CVMS solution.
xxii. Master System Integrator: MSI refers to the Successful Bidder who shall
be awarded the contract against this tender, and who shall be responsible
for coordinating and integrating various services, components, or solutions
provided by multiple partners, joint venture members, or consortium
participants. The Master Service Integrator serves as the central point of
coordination to ensure collaboration among the involved parties and the
successful delivery of the overall project. The MSI shall also be the sole
entity with which CRIS shall interact, sign any contractual agreements, and
apply penalties as per the Service level agreement.
xxiii. Viewing Centers: Viewing centers are locations where one or more users
connect to the CVMS solution, enabling them to access alerts and
associated video content to conduct investigations.

Page 13 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xxiv. Applications & Databases: CRIS and the Railways, have developed
numerous applications and databases to assist in the day-to-day
operations of the Indian Railways.
xxv. Go-Live: The Go-Live is the milestone which refers to the moment when
the application is made operational in the production environment and
becomes available for use to all the identified stakeholders of the project
Post issuance of the Phase 1 Go-Live Completion Certificate by CRIS.
a. Phase 1 Go-Live: The Phase 1 Go-Live is the milestone which refers
to the day when the complete CVMS Solution is made operational in
the production environment along with the on-boarding of 10,000
Cameras (at least 1000 Cameras each from the Coaches, Locomotives
& EMUs/MEMUs) and completion of the primary integration. At this
stage the Phase 1 Go-Live Completion Certificate will be issued by
CRIS based on successful completion of User Acceptance Testing
(UAT) and the VMS solution becomes available for use to all the
identified stakeholders of the project. CRIS shall also issue a Phase 1
Go-Live Completion Certificate.
b. Final Go-Live: The Final Go-Live is the milestone which refers to the
day when the complete CVMS Solution is made operational in the
production environment along with the successful onboarding of all
offered Cameras and Integrations. CRIS shall also issue a Final Go-
Live Completion Certificate.
c. Project Completion Certificate: The project completion certificate will
be issued by CRIS when all the vulnerabilities are fixed by MSI
received from the Security audit (initiated by CRIS) after the Final Go-
Live.
xxvi. Facial Recognition Solution (FR): The AI-enabled system shall be
responsible for face matching of passengers across multiple databases
and faces captured through Coaches /EMUs/MEMUs.
xxvii. Least Cost Selection (LCS) – In the least Cost Selection method, the
Least price quoted by the qualified Bidders is the criteria for selection of
the successful Bidder.
xxviii. Mobile Service Provider (MSP): A mobile service provider is a company
that sells wireless connectivity to customers for mobile data and telephone
calls. It may also be called a mobile network operator, a mobile carrier, a
cellular company, or a wireless service provider.
xxix. Field SI: CRIS has published multiple RFPs through which CCTV
Surveillance Systems like CCTVSS in the Coaches and the passenger
section of the EMU/MEMU and CVVRS in Locomotives and the Driving
Motor Cab of the EMU/MEMU are planned to be implemented. Multiple
System Integrators are being identified through these RFPs who shall be
implementing the CCTVSS and the CVVRS solutions and these are the
System Integrators who are being called as the Field SI.

Page 14 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xxx. Driving Motor Cabin (DMC): The Driving Motor Cabin in an Electric
Multiple Unit (EMU), is a type of railcar that contains traction equipment,
such as motors and control systems, necessary for propulsion of the EMU.
The driving motor cabin provides power to the train and is responsible for
controlling acceleration, deceleration, and speed.
xxxi. Onboarding of Camera: The process of onboarding the NVRs/Cameras
installed in the Coaches, Locomotives and EMU/MEMUs on CVMS
consists of the following activities:
a. View, monitor, manage and receive the video streams recorded by the
NVRs in the VMS,
b. Receive the alerts at the ICCC
c. Monitor the health parameters in the EMS for the NVR’s and the
Camera’s

The NVRs/Cameras are considered to be on-boarded on the

completion of the above-listed activities.

Page 15 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

3. Introduction
3.1. About Indian Railways

Indian Railways is one of the world's largest networks operated under a single
administration and the largest rail network in Asia. Established in 1853, it has grown
and expanded over the years, connecting various parts of India, and providing
international services to neighbouring countries like Nepal, Bangladesh, and
Pakistan. The railway network spans over 68,043 kilometres, encompassing around
7,308 stations across the country. The railway network carries about 18 million
passengers daily and runs more than 7,421 cargo trains carrying more than 3 million
tons of freight daily.

3.2. About CRIS

The Ministry of Railways established the Centre for Railway Information Systems
(CRIS) in 1986 as an umbrella organisation for all IT activities for Indian Railways
(IR). It develops and manages the Information Technology applications of the Indian
Railways. CRIS also provides IT applications for non-railway Government and Public
Sector organisations where the portfolio of projects covers the gamut of Indian
Railways functions, such as passenger ticketing, freight operations, train dispatching
and control, crew management, e-procurement, management of Railways fixed and
moving assets, and production of rolling stock.

4. Project Vision & Objective

Indian Railways aims to improve passenger safety through strategic enhancements
like implementing CCTV Surveillance solutions at the Railway Stations and in its
rolling stock. While these solutions are planned- at Railway stations (being
implemented through a different RFP and not in the scope of the current Bid
Document Part-II), the Railway authorities now plan to extend CCTV surveillance to
include Coaches, Locomotives, EMUs, and MEMUs for comprehensive safety
coverage.

4.1. Other CRIS RFPs

i. The Indian Railways, as part of its initial rollout plan, aims to introduce the
Closed-Circuit Television Surveillance System (CCTVSS) in approximately
44,000 coaches, covering all zones. The current tender does not include the
scope of implementation of the CCTVSS in the Coaches. However, the
Scope of integrating the CCTVSS solution implemented in the Coaches with

Page 16 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

the CVMS solution stack hosted on the public cloud is included in the scope of
the CVMS MSI.
ii. Similarly, in order to monitor the Loco pilot’s performance and to ensure the
vigilance of train drivers during their journeys the Indian Railways is planning to
implement a Crew Voice and Video Recording System (CVVRS) along with
Railway Driver Alertness System (RDAS) in approximately 14,350
Locomotives. The current tender does not include the scope of implementation
of the CVVRS and RDAS in the Locomotives. However, the Scope of
integrating the CVVRS solution implemented in the Locomotives with the
CVMS solution stack hosted on the public cloud is included in the scope of the
CVMS MSI.
iii. The EMUs and MEMUs are also planned to be implemented with the CCTV
Surveillance System. There are two types of solutions which are being planned,
namely CCTVSS for the passenger coaches and the CVVRS for the Driving
Motor Cabin of the EMUs and MEMUs in approximately 8500 EMUs/MEMUs.
The current tender does not include the scope of implementation of the
CCTVSS and CVVRS in the EMUs and MEMUs. However, the Scope of
integrating the CCTVSS & CVVRS solution implemented in the EMUs &
MEMUs with the CVMS solution stack hosted on the public cloud is included in
the scope of the CVMS MSI.
iv. In order to monitor, manage, and record the content in a central system and
receive alerts from the CCTVSS and the CVVRS along with the RDAS, Indian
Railways is planning to build a Central Video Management System (CVMS) and
host it on the Public Cloud along with the other related activities. This Bid
Document Part-II includes the scope of designing, implementing, and
maintaining the CVMS for a period as stipulated in Section Contract
Period.

The Bidders are advised to go through the tender documents for edge devices to
have a better understanding of the integrations required with the other works which
are given in Annexure-1- Other CRIS Bid Documents this tender document.

Obligations of the bidder are in no way limited by any of the integration activities
mentioned in the other tender/contracts of CRIS.

4.2. Key Objectives of CVMS

The objective is to implement a holistic, integrated, and responsive Centralized
Video Management System (CVMS) for Indian Railways. This system shall also
integrate with various Systems, applications and databases installed under CRIS &
Indian Railways respective project to enhance safety and security in the Indian
Railways.

i. Streamlining Surveillance Operations: The CVMS enables Indian Railways to

efficiently manage, and monitor CCTV cameras installed at Coaches,

Page 17 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Locomotives, EMUs and MEMUs from centralized locations and various viewing
centers. This streamlines surveillance operations and enhances overall security
management.
ii. Real-Time Monitoring and Incident Response: The CVMS allows real-time
monitoring of live video feeds and alerts, enabling Indian Railways authorities to
promptly detect and respond to security incidents, emergencies, and operational
disruptions across the railway network.
iii. Improved Situational Awareness: By integrating multiple CCTV camera feeds
into a centralized platform, the CVMS enhances situational awareness for security
personnel. It provides a comprehensive view of railway assets, passenger areas
and potential security threats.
iv. Enhanced Investigation Capabilities: The CVMS facilitates efficient storage,
retrieval, and analysis of video footage for investigative purposes. It enables
authorities to review past incidents, identify perpetrators, and gather and preserve
evidence for legal proceedings or internal inquiries.
v. Optimized Resource Allocation: With centralized monitoring and analytics
capabilities, the CVMS enables Indian Railways to optimize resource allocation by
deploying security personnel and emergency response teams more effectively
based on threat assessments and operational needs.
vi. Integration with Other Systems: The CVMS shall be integrated with other
security and operational systems, such as edge devices, CRIS applications and
respective databases. This integration enhances interoperability and enables a
coordinated response to security incidents and emergencies.
vii. Continuous Improvement and Adaptation: The centralized VMS shall
enable Indian Railways to continuously monitor and evaluate security measures,
identify vulnerabilities, and implement proactive measures to address emerging
threats and evolving security challenges effectively.

To summarize, the implementation of a Centralized video management system for

Indian Railways is aimed at enhancing security, improving operational efficiency, and
fostering a safe and secure environment for passengers, staff, and stakeholders
across the railway network.

5. High-level Architecture
High-Level Architecture of Complete CCTV Surveillance Initiative by IR

The Overall CCTV Surveillance High-level architecture is shown in the below figure.
However, the technical architecture of CVMS will be finalized, in consultation with
CRIS, upon detailed requirement analysis for various systems and applications of
the project including integration with various other systems.

Page 18 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Fig: CVMS System Architecture (Illustrative)

The proposed architecture shall adhere to the latest industry standards in

implementation, security, and data privacy. The proposed overall architecture shall
be open architecture-based, highly scalable, and able to integrate multiple disparate
systems seamlessly on a common platform. The architecture is further divided into
different layers as mentioned below:
5.1. Edge Layer
The Edge Layer consists of the CCTV video surveillance equipment installed in
Indian Railways train Coaches, Locomotives, EMUs, and MEMUs. The CCTV Video
Surveillance equipment installed in the Coaches, Locomotives, EMUs and MEMUs
are described in the below sections:

i. Coaches, EMUs and the MEMUs: The CCTV Surveillance equipment installed in
the Coaches, EMUs and the MEMUs is known as the Closed-Circuit Television
Surveillance System (CCTVSS) solution as described by RDSO as per the RDSO
Specifications -RDSO/SPN/TC/106/2022 Version 2.1 with amendment no. 1 or
latest amendment. The CCTVSS solution consists of IP IP-based Mobile-Network
Video Recorder / Video Recording Unit installed in the Coaches and Passenger
area of the EMUs and MEMUs. Based on the configuration of the Coaches the IP-
based Cameras are placed at different locations and are connected to the Mobile-
Network Video Recorder / Video Recording Unit in each Coach. Based on the
type of the Coach/EMU/MEMU, the IP based Cameras connected to the Mobile-

Page 19 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Network Video Recorder / Video Recording Unit vary in quantity from a minimum
of 4 to 8 nos. per Coach.
ii. Locomotives, Driving Motor Cabin of the EMUs and MEMUs: The CCTV
Surveillance equipment installed in the Locomotives and the Driving Motor Cabin
of the EMUs and the MEMUs is known as the CVVRS Solution as described by
RDSO as per the RDSO Specifications - RDSO Specification No.
RDSO/2015/EL/SPEC/0118 (Rev.1)-2019 along with Amendment No.1 issued on
29-03-2022 and Amendment No.2 issued on 20-01-2024 and Amendment No. 3
issued on 15.02.2024 or latest amendment for Crew Voice & Video Recording
System for Electric & Diesel Locomotives. The CVVRS consists of IP-based
Network Video Recorders installed in the Locomotives and Driving Motor Cabin
section of the EMUs and MEMUs. Based on the type of the Locomotive, the IP-
based Cameras connected to the Network Video Recorders vary in quantity from
a minimum of 10 to 14 nos. per Locomotive.

The Edge layer consisting of the IP-based NVRs, cameras and panic buttons shall
be sending the following data to the CVMS solution hosted on the Public Cloud:

a. Live video streams (including on-demand)

b. On-demand playback of video streams stored on CVMS and edge devices.
c. Alerts and Events from Panic buttons and Camera Tampering
d. Video Snippets along with events and alerts
e. Railway Driver Analytics alerts
f. Audio to and from the Locomotives
g. Cropped Images for the Facial Recognition Solution
h. Equipment Health information
i. Equipment event Logs

The Edge layer shall send across the above listed data to the CVMS layer by
leveraging the Network Layer which is detailed in the subsequent section.
Additional information on the Edge layer can be found in the Annexure-2-Edge
Layer or Field .

5.2. Network Layer

The connectivity between the Edge devices and the Central Video Management
System hosted on the public cloud shall be provided by the Network Layer.

The Network layer consists of the following components:

i. The Network Video Recorders installed in the Coaches, Locomotives, EMUs

and MEMUs are equipped with Dual SIMs (from two different service providers)

Page 20 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

providing 5G Connectivity (fallback to other network modes like

4G/3G/EDGE/2G based on the network availability)
ii. Private APN for each SIM/eSIM provided by the Mobile service provider.
iii. Backhaul from the private APN to the Public Cloud hosting the CVMS solution.

The current tender does not include the scope of the supply of the 5G (with
auto-fallback to 4G) Mobile network connectivity, the private APN and the
backhaul from the private APN to the CVMS cloud.

Additional details on the Network layer can be found in the Annexure-3-Network

Layer.

5.3. CVMS Layer

The Central Video Management System (CVMS) denotes the Video Management
platform that is being planned to be implemented for the purpose of managing and
overseeing the functioning of the edge devices installed in Indian Railways train
Coaches, Locomotives, Electric Multiple Units (EMUs), and MEMUs. The CVMS
solution is planned for implementation through this tender and shall be hosted
on a MeitY empaneled Public Cloud.

The CVMS layer shall have the ability to smoothly integrate with diverse edge
devices, databases, and applications. This envisioned CVMS layer is expected to
accommodate rules engines, alerting systems, diagnostics systems, control systems,
messaging systems, event handling systems, and reporting/dashboard systems,
delivering actionable information to users.

The CVMS layer will consist of the following applications:

i. Video Management System (VMS)
ii. Integrated Command and Control Center application (ICCC)
iii. Enterprise Management System (EMS)
iv. Facial Recognition Solution (FR) including capability to build partial faces.
v. Video Summarization
vi. Forensic Application (Image & Video)
vii. Integration with edge devices, Railways/CRIS & third-party applications &
databases with CVMS

One of the important aspects of building the CVMS layer is to integrate the layer with
the Edge devices in the Field installed in the Coaches, Locomotives, EMUs and
MEMUs. The Integration shall be conducted by employing any of the following
methods:

1. Using the ONVIF protocol OR

2. The Edge devices System Integrator shall use the SDK provided by the
Master System Integrator (MSI) of the CVMS OR

Page 21 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

3. The MSI of the CVMS solution shall use the SDK provided by the System
Integrator implementing the Edge devices in the Field namely the Coaches,
Locomotives, EMUs and the MEMUs.

5.4. Users of the CVMS

The users accessing the CVMS shall involve multiple types of stakeholders. The
type of Users and the location from where the users are likely to access the CVMS
solution are elaborated in this section. The details mentioned in this section are
Indicative and will be deliberated during the Requirement gathering phase of the
project.

The users of the CVMS solution shall be located at various CRIS office locations, the
Zonal offices, Divisional offices and the Railway Protection Force Thanas, etc.

The indicative quantity of the users that are planned to use the CVMS solution are:

# Type of Concurrent Users Quantity

1 Desktop 2000
2 Mobile 2000
Table 1: Users Of the CVMS
The above-mentioned quantity against each type of user is the concurrent users.
Users of the CVMS will continuously keep getting added as and when new users join
the Indian Railways and similarly also get deleted as and when users are transferred
or retire/leave the organization. The overall named users count shall be considered
as 3 lakhs at any given time and the systems & solutions should be accordingly
sized.

The CVMS users shall be categorized into distinct groups, including but not limited to
critical, power, non-critical, field, and other types, to facilitate the implementation of
varying levels of privileges and role-based permissions. This categorization aims to
ensure that each user group receives access and permissions appropriate to their
role. Similarly, these users should also be configured with different idle time-outs to
ensure that the concurrency of the users is optimally configured. The CVMS system
will have provision to enable the authorized users to grant or withdraw permissions
to other users as and when required through a user-friendly Graphical User
Interface.

CRIS/Indian Railways plans to establish Integrated Command & Control Centers at

multiple locations. These centers will operate 24x7, with multiple users managing the
command-and-control functions. Equipped with video walls and other automation
facilities, the Integrated Command and Control Centers aim to enhance response
capabilities and overall preparedness.

Page 22 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

6. Scope of Work
The selected Master Systems Integrator shall have the overall responsibility to
design, build, implement, operate, and maintain the Central Video Management
System (CVMS) solution stack hosted on the Public Cloud, on Pay-per-Use model,
for a period as stipulated in Section Contract Period.

The broad components of the scope of work of the MSI are given below:

# Component Description
1. CVMS Applications a. Video Management System (VMS)
b. Integrated Command and Control Center
(ICCC)
c. Facial Recognition Solution (FR) including
capability to build partial faces.
d. Video Summarization
e. Forensic application (Image & Video
enhancement)
f. Enterprise Management System integrated
with Helpdesk application
2. CVMS Users a. Desktop Users
b. Mobile Users
3. Events/alerts a. Deployment & Configuration of workflow
automation to handle alerts of various
types as per SOPs.
b. Dashboards on the alerts for respective
stakeholders
4. Integrations for all a. Integration of different applications within
Systems CVMS Solution Stack
b. Integrations with the edge devices in
Coaches, Locomotives, EMU & MEMU
c. Integration with Indian Railways/CRIS
applications/other systems/databases
d. Integration with Other Government
Applications
5. Public Cloud Infrastructure a. IaaS, PaaS, SaaS services
b. Compute including OS
c. Storage based on CVMS application
requirements
d. Tiered Storage for the data received from
the edge devices based on CRIS data
retention requirements.
e. Cyber security for the CVMS Solution
Stack

Page 23 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Component Description
f. Network infrastructure at the Public Cloud
including any Public and Private IP
address requirements.
g. Backups (including immutable backups)
and restoration.
h. Internet and Intranet DNS Security &
Service
6. Monitoring & Management a. Edge devices installed in the Coaches,
Locomotives, EMUs and MEMUs
b. CVMS Solution Stack on the Public Cloud
c. The Intra-CVMS applications
d. Integrations with the CRIS and Indian
Railways and other Government
applications.
e. SLA management for all the above items.
7. Support Services a. 24x7 Monitoring by the MSI
b. Helpdesk Support by the MSI
c. OEM backend support for the CVMS
solution for all systems, applications and
integrations during the Implementation,
Operations Phase
d. Documentation, User manuals and multi-
media content of CVMS as well as OEMs.
e. Patch Management, firmware updates,
security updates and feature updates for
the complete CVMS Solution Stack.
8. Audits Security audits through Government Security
agencies (Government Agency from the list of
CERT-ln empanelled Information Security
Auditing Organization)
9. Training Training of the respective stakeholders and users
Table 2: Scope of Work Components
The detailed scope of work to be undertaken by the bidder for setting up &
operationalization of the Central Video Management solution stack is given in
subsequent sections of this bid document Part-II and is to be performed as per the
Scope of Work, functional specifications, sizing information and conditions
mentioned in this Bid Document. The bidder will need to also understand the scope
further by going through any corrigendum issued after the publishing of the bid
document, and the contract to be signed with the successful Bidder subsequently.

Page 24 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Further, the use cases listed and defined in this bid document is not exhaustive. MSI
with support from the respective OEMs shall ensure implementation of new use
cases on request of CRIS/Indian Railways at no additional cost to CRIS.

The CVMS project shall be initiated by defining a clear project plan by breaking it
down into critical sections, outlining not only the overarching project goals but also
the specific security objectives and surveillance requirements. During the
requirement-gathering and design phase, the focus shall lie on identifying and
comprehensively understanding the CVMS solution needs, including the resolution
requirements, and necessary functionalities. Post the requirement gathering, the
process of design & deployment shall start with the overall solution that best meets
the project requirements.

Subsequently, the final acceptance test rigorously evaluates the CVMS system's
performance against predefined security benchmarks. Upon successful testing, the
'Phase 1 Go-Live' phase initiates the operational use of the CVMS infrastructure.
Finally, detailed system documents encompassing CVMS configurations, network
configurations, operational manuals, and maintenance protocols shall be created,
serving as crucial references for ongoing CVMS solutions and future expansions.

The Bidder is required to submit a comprehensive proposal that aligns with the best
industry standards while concurrently adhering to the stipulations outlined in the Bid
Document Part-II. Additionally, the proposed solution must comply with the relevant
Research Design and Standards Organization (RDSO) specifications as read with
the latest amendments, standards, guidelines, etc. The proposal should demonstrate
a meticulous integration of industry best practices, Bid Document Part-II
requirements, and strict adherence to RDSO specifications as read along with the
latest amendments to ensure a robust and compliant solution.

The Bidder shall ensure that they carefully evaluate the sizing parameters specified
in the bid document part-II at Sizing Parameters for the CVMS Solution and, while
proposing a solution, must ensure that the capacity and capabilities of the proposed
solution surpass those elaborated in the Bid Document Part-II. It is imperative that
the Bidder demonstrates a thorough understanding of the sizing requirements and
presents a solution with capabilities that meet the specified parameters, thereby
ensuring a robust and scalable outcome that can effectively meet the project's
requirements.

The Bidder is advised to understand the project milestones outlined in the relevant
RFPs related to Coaches, Locomotives, and EMUs/MEMUs installations. This
understanding is essential to identify and address the interdependencies between
the proposed Centralized Video Management System (CVMS) and the Edge devices
to be installed in the aforementioned components. The Bidder shall factor in these

Page 25 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Inter-dependencies while formulating their proposal, ensuring seamless and logical

integration across the various project components.

The MSI scope of work includes but not limited to the following broad areas:

6.1. Inception Phase

The MSI shall be responsible for the preparation of a detailed project plan. The plan
shall address the minimum following:
i. A defined set of activities for the project and identify the interdependence between
them.
ii. The Project Plan should be mapped in the Project Management Tool which has
been detailed in Section Project Management Tool (PMT).
iii. Manpower resource planning and allocation for each phase / activity. This must
also indicate where each resource would be based during that phase, i.e., onsite
at the CRIS office or off-site at MSI premises.
iv. MSI to share the escalation matrix of its organization as well as respective OEMs
of all components of CVMS.
v. Establish and measure resource assignments and responsibilities.
vi. Highlight the milestones and associated risks.
vii. Communicate the project plan to respective stakeholders.
viii. The bidder shall provide a weekly project progress reporting. During the
implementation of the project, the MSI shall submit weekly reports. This report
shall be presented in the review meeting to CRIS. The report shall contain at the
minimum the undermentioned information:
a. Milestones or targets accomplished during the period (weekly)
b. Cumulative or minor deviations from the scheduled date as specified in the
finalized Project Plan
c. Corrective actions to be taken to return to the planned schedule of progress.
d. Target for the subsequent week.
e. Any revisions to the planned schedule provided such revision is necessitated
by reasons beyond the control of MSI.
f. Support needed from CRIS.
g. Issues/Concerns
h. Risks/Show stoppers along with mitigation
ix. Identify the activities that require the participation of client personnel (including
CRIS, the Program Management team etc.) and communicate their time

Page 26 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

requirements and schedule early enough to ensure their full participation at the
required time.

6.2. Requirement Gathering Phase & Design Phase

6.2.1. Requirement Gathering
The MSI shall perform a detailed assessment of the business requirements and
CVMS Solution requirements as mentioned in the bid document. Based on the
understanding and its assessment, MSI shall develop and finalize the detailed
assessment report in consultation with CRIS and its representatives. While doing so,
MSI at least is expected to do the following:
i. MSI shall have detailed knowledge sessions with CRIS officials to understand the
background as well as the intent behind the project.
ii. MSI shall study and revalidate the integration requirements (both intra and inter-
applications & databases) given in the Bid Document Part-II with CRIS and submit
it as an exhaustive Functional Requirement Specification and Software
Requirement Specification document in the next phase.
iii. MSI shall develop and follow a standardized template for requirements capturing
and system documentation.
iv. The requirement gathering phase should be able to capture all the requirements
of the CVMS solution stack which should be across but not limited to the Public
Cloud Infrastructure requirements, SRS requirements, Scalability Requirements,
Performance Requirements, Availability and Reliability Requirements, Security
Requirements, Compliance Requirements, Integration Requirements, Data
Management Requirements, Comprehensive Testing Requirements, Monitoring
and Logging Requirements, Deployment and Release Requirements,
Documentation and Training Needs, and any other requirements.
v. For all the discussions with the CRIS team, MSI shall be required to be present at
the CRIS office with the requisite team members and subject matter experts.
vi. The MSI is responsible for identifying and documenting requirements during the
requirement-gathering phase, determining the software development tasks to be
undertaken, and outlining any necessary customizations.
vii. The MSI must ensure that, following the establishment of the initial Software
Requirements Specifications (SRS), these requirements will be implemented
before the commencement of Phase 1 Go-Live.
viii. The SRS shall follow an iterative approach until the Final Go-Live. This
implies that the ongoing process of redefining and refining the software
requirements will undergo multiple cycles or iterations until the final Go-Live is
achieved. The iterations to SRS shall be conducted at no additional cost to CRIS.
ix. The MSI shall supply the following documents along with the developed
components:
a. Business process guides
b. Program flow descriptions

Page 27 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. Data model descriptions

d. Sample reports
e. Screen formats
f. Frequently asked question (FAQ) guides
g. User manual
h. Technical Manual
i. Any other documentation required for usage of the implemented solution.

6.2.2. Designing and Development Phase

For the designing of the overall CVMS solution, MSI shall carefully consider the
scope of work and the design considerations for the various systems and
applications mentioned in the tender document and provide a solution that best
meets the project requirements. Considering the scope set in the bid document, the
MSI shall carefully consider the solutions it proposes and explicitly mention the same
in the technical proposal. The implementation of the CVMS applications will follow
the procedure mentioned below:

i. Software Products (Configuration and Customization): In case MSI proposes

software products the following need to be adhered to:
a. MSI shall be responsible for providing the application and
Licenses/Subscriptions of related software products and hosting the same on
the cloud to meet project requirements. No extra cost shall be paid by CRIS
for any of these licenses / subscriptions during the lifecycle of the project.
b. The MSI shall refer to the design considerations of the respective systems
and applications mentioned in this tender document for the “Designing and
Development Phase” of the project.
c. The MSI shall also involve the OEM and shall ensure that the solution is
authenticated and validated by the OEM.
d. MSI shall have provision for procurement of licenses/subscriptions in a
staggered manner as per the actual requirement of the project.
e. The MSI shall perform periodic audits to measure license compliance against
the number of valid end-user software Licenses/Subscriptions consistent with
the terms and conditions of license agreements, volume purchase
agreements, and other mutually agreed upon licensed software terms and
conditions. The MSI shall report any exceptions to license terms and
conditions at the right time to CRIS. However, the responsibility of license
compliance solely lies with the MSI. Any financial penalty imposed on MSI
during the contract period due to license non-compliance shall be borne by
MSI.
ii. MSI shall also use any other tools, databases, applications, accessories, etc.
required to make the integrated CVMS solution complete as per requirements,
provide tools, accessories, and documentation and should provide a list of the

Page 28 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

same. The offered tools and accessories shall be part of the overall CVMS
solution.
iii. The bidder shall consider all security aspects across the OSI layer during the
implementation phase of the project. This includes but is not limited to,
assessing, and addressing security concerns at each layer of the OSI model.
The bidder is required to implement and configure security measures following
industry leading practices and any specific security requirements that are
considered mandatory for providing comprehensive security of the CVMS
solution stack. The implemented security measures should be comprehensive,
robust, and designed to mitigate potential vulnerabilities across the OSI layer.
The bidder must demonstrate a thorough understanding of security principles
and ensure that appropriate safeguards are in place to protect the confidentiality,
integrity, and availability of the system and its components.
iv. MSI shall design, configure, and manage the entire cloud infrastructure
according to the functional requirements of the CVMS solution.
v. MSI shall maintain a traceability matrix from the SRS stage for the entire
implementation.
vi. Configuration, and deployment of complete CVMS solution (including web
mobile application, as applicable, configuration of all edge devices, cloud
infrastructure).
vii. MSI shall ensure the system hardening of the complete CVMS solution
(including Application tier, Web tier and database tier, OS, etc., as per their
proposed solution stack) as per CRIS security policy and industry-leading
practices including the following but not limited to:
a. MSI shall ensure that all default users /accounts which are not required must
be closed /disabled state after the installation.
b. MSI shall install Software (Firmware, OS, RDBMS, Application Server, etc.)
in the underlying infrastructure and ensure that all those services/ports which
are not required should be in closed /deny-all mode.
c. MSI to ensure that all applications which are not required must be
uninstalled or disabled during the implementation/operations Phase.
viii. The MSI shall design and configure Standard Operating Procedures (SOPs) and
also design the dashboards and consider the integrations necessary for
implementation during the project's implementation stage.
ix. On a time-to-time basis, there would be different stakeholders (GRPF, RPF,
Divisional Heads, Zonal Heads, and other senior management from CRIS as
well as the Indian Railways) for whom customised dashboards need to be
created, configured and provisioned. These dashboards would need to be
deployed and provisioned for a long-term deployments or short-term
deployments.
x. System Documentation: A minimum of four (4) sets of System Documentation
both in hard copies and soft copies to be supplied along with
Licenses/Subscriptions and shall include but not be limited to the following.

Page 29 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

a. Functional Requirement Specifications

b. High-level design of the whole system
c. Low-level design for whole system / Module level design
d. System Requirements Specifications
e. Any other explanatory notes about the system
f. Traceability matrix
g. Technical and product-related manuals
h. Installation guides
i. User manuals
j. System administrator manuals
k. Toolkit guides and troubleshooting guides.
l. Other documents as prescribed by CRIS.
m. Quality assurance procedures
n. Change management histories.
o. Version control data
p. SOPs, procedures, policies, processes for all use cases etc. developed
and configured by MSI for CRIS
q. SLA Management
r. Device Management
s. Test Environment documents:

1. Detailed Test methodology document

2. Unit Level Testing and Load & Performance testing use cases and
test parameters
3. Testing infrastructure on Cloud
4. Access to the test bed and visibility of all its functionalities shall be
shared with CRIS.
5. Overall System Testing
6. Acceptance of test cases

(These documents need to be updated after each phase of the project and to be
maintained updated during the entire project contract duration. The entire
documentation will be the property of CRIS).
Periodically, various government departments such as RDSO, MeitY, Cert-In,
etc., issue security and other types of advisories. The MSI is obligated to
promptly adhere to these advisories, including the advisories released in the past
without imposing any additional costs on CRIS. In the event that the bidder is
unable to comply with any of these advisories, the MSI must promptly notify CRIS
of such non-compliance. The MSI is also advised to ensure that such advisories
are also implemented in the design and development of the CVMS solution for
CRIS.

Page 30 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

The MSI shall ensure that the OEMs of the CCTV Surveillance Systems having
history of security breaches and data leakages should be avoided from being
proposed for designing the overall CVMS Solution Stack.

6.3. Integration & Testing - Prototype Phase

After the successful integration of edge devices according to the requirements
mentioned in Integration with Edge Devices and the CRIS/Railway applications,
testing shall be conducted to ensure interactions between multiple applications &
edge devices to ensure the integrated user experience. The successful MSI shall
carry out integration testing focusing on verifying the interactions and interfaces
among various applications. These tests would be carried out based on the test
cases covering all the functional requirements stipulated in this bid document. The
test cases shall be prepared by the MSI and validated by CRIS.

S. Type of Respons Scope of Work

No Testing ibility

1. Integration MSI 1. MSI to prepare and share with CRIS the Integration
Testing test plans and test cases.
2. MSI to perform Integration testing of the edge devices
as per Section Integrations of Systems.
3. MSI to perform Integration testing as per the approved
plan.
4. Integration testing to be performed through manual as
well as automated methods.
5. All types of Automation testing tools to be provided by
MSI.
Table 3: Integration Testing

The MSI may propose further detailed Acceptance criteria which CRIS will review.
Once CRIS provides its approval, the Acceptance criteria can be finalized. In case
required, parameters might be revised by CRIS in mutual agreement with the MSI
and the revised parameters shall be considered for acceptance criteria. In case of
any dispute regarding the finalisation of the Acceptance Criteria, the decision of
CRIS shall be final. A comprehensive document shall be prepared to record & track
the testing results and log and track issues/bugs identified. These documents should
be continuously updated and submitted to CRIS.

Page 31 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

6.4. Acceptance Tests

6.4.1. User Acceptance Test (UAT)
The MSI shall develop a User Acceptance test document along the framework
elaborated below in this Section. The User acceptance tests are mandatory and shall
be conducted on all systems and applications as per delivery milestones to ensure
that the proposed solution aligns with the specified functional requirements in the bid
document part-II. The MSI shall develop the test plans and submit them to CRIS for
necessary approvals. The MSI should note that the UAT requirements are not fully
elaborated in this section. These are just the indicative requirements mentioned
here. The MSI should ensure that the complete end-to-end functional requirements
stipulated in the RFP are demonstrated during the UAT. Each functionality
elaborated in the Scope of Work should be demonstrated during the UAT process.

MSI shall establish the acceptance criteria before the demonstration of the solution.
The MSI may propose further detailed acceptance criteria which CRIS will review.
Once CRIS provides its approval, the acceptance criteria can be finalized. In case
required, parameters might be revised by CRIS in mutual agreement with the MSI
and the revised parameters shall be considered for acceptance criteria without any
additional financial implication to CRIS. In case of any disputes regarding the
finalisation of the UAT plan and the acceptance criteria, the decision of CRIS shall
be final.

A comprehensive process shall be set up and that would have the capability to log
and track the testing results, document, and maintain the test cases, and log and
track issues/bugs identified.

User Acceptance Certificate shall be issued by CRIS to the successful MSI after
successful testing in a real-time condition for at least 15 days of trouble-free
operation or as defined in the delivery milestone of the respective activity.
The following are the minimum activities which shall be part of the UAT plan and
shall be finalised post mutual discussion with CRIS stakeholders.
i. Test end-to-end functionality from video capture to storage and retrieval.
ii. Validate data flow between the Video Management System, Integrated
Command and Control Center, Facial Recognition, Video Summarization,
and Forensics applications.
iii. Check and validate for Integrations.
iv. Integration as per the parameters listed for the M-NVR/NVR & VRU.
v. CRIS & Indian Railways applications.
vi. Other Government applications.
vii. Test video upload, storage, and retrieval functionality in the Video
Management System.

Page 32 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

viii. Tests for live streaming, on-demand streaming, and options to save the
sections of the live streaming or on-demand streaming.
ix. Ensure support for various video formats and resolutions.
x. Validate the synchronization of audio and video.
xi. Verify the accuracy and effectiveness of the Facial Recognition software.
xii. Check video summarization for accurate content representation.
xiii. Test video forensics tools for image and video enhancement.
xiv. Validate the functionalities of all the systems and applications of the CVMS
solution.
xv. Verify real-time monitoring capabilities provisioned for the CVMS solution
xvi. Test alarms, notifications, and alerts for unusual activities.
xvii. Check the Integrated Helpdesk management software for automated
trouble ticket generation on the changing status of the CVMS systems and
applications.
xviii. Check integration of the EMS with the communication channels like the
SMS Gateway and the Email Server.
xix. Measure response times for facial recognition and video summarization
under different load conditions.
xx. Check the ability of the solution to handle concurrent users in the
Integrated Command and Control Center.
xxi. Demonstrate the end-to-end incident management from the Integrated
Command and Control by a user.
xxii. Validate the effectiveness of access controls for different user roles.
xxiii. Test the encryption and decryption processes for video data.
xxiv. Applications and systems which have been configured for High availability
or Redundancy to be validated.
xxv. Software applications should be validated to ensure that they are licensed
and of the latest available s
xxvi. release versions.

The following Table 4: User Acceptance Test explains the details of the various
kinds of tests to be done in the UAT phase.

S. Type of Responsibility Scope of Work

No Testing

1. Unit Testing MSI 1. MSI to perform unit testing of all

respective applications as per functional
requirements defined in the bid
document Part-II.
2. MSI to prepare test plans and test cases
and maintain them. MSI shall work on
the test cases developed by MSI and

Page 33 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Type of Responsibility Scope of Work

No Testing

validated by CRIS.
3. Should be performed through
manual/automated methods.
4. Automation testing tools to be provided
by MSI. CRIS doesn’t intend to own
these tools.

2. Performance MSI 1. MSI to do performance and load testing

and load as per the respective batches.
Testing 2. Various performance parameters such
as transaction response time, throughput
etc. should be considered.
3. Load testing of the Project to be
performed on business transaction
volume.
4. Test cases and test results to be shared
with CRIS.
5. Performance testing to be carried out in
the same architecture that would be set
up for production.
5. MSI needs to use performance and load
testing tools for testing. CRIS doesn’t
intend to own these tools.

3. User MSI and CRIS 1. MSI and CRIS to perform User

Acceptance Acceptance Testing
Testing 2. MSI shall prepare User Acceptance
of Project Testing test cases.
3. UAT to be carried out in the same
environment/architecture that would be
set up for production.
4. MSI shall fix bugs and issues raised
during UAT and get approval on the fixes
from MSI before production deployment.
6. Changes in the application as an
outcome of UAT shall not be considered
as a Change Request. MSI shall rectify
the observations without any additional
financial implications to CRIS.
Table 4: User Acceptance Test

Page 34 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

After successful user acceptance testing including inter-application integrations, the

MSI shall be given Phase 1 Go-Live Completion Certificate.

6.4.2. Periodic Acceptance Test (PAT)

The CVMS shall be subjected to a monthly, quarterly, and annual systematic

process of verifying and validating the accuracy, stability and precision. This shall be
conducted by the MSI to ensure and validate the accuracy of the overall CVMS
solution. CRIS may ask for additional interim tests in the O&M phase for validating
the accuracy and precision of the overall CVMS solution stack.

The MSI shall submit a detailed test plan along with the calendar of the detailed
periodic acceptance tests and the parameters that shall be tested. The submitted
test plans shall include the detailed test plans, frequency of tests, the method of
testing, the parameters that shall be tested, the benchmarks and other aspects of the
CVMS solution stack. On discussion and finalisation of this proposal with CRIS, the
periodic acceptance tests calendar shall be published and executed.

The MSI shall conduct the Periodic Acceptance Checks in the following areas but not
limited to:

i. To verify the system's ability to receive and process alerts in a timely

manner.
a. Simulate various types of alerts (system failures, switchovers, change
of state of the application, services stopping or starting, etc.).
b. Measure the time taken to receive, process, and escalate alerts.
c. Notifications being sent to stakeholders, check whether the right
stakeholders are receiving the alerts, as per the configured frequency
and as per the configured conditions.
ii. To validate the accuracy and functionality of respective applications within
the CVMS as per the test cases approved by CRIS including the
changes/modifications/enhancements done during the change
management procedure.
iii. Ensure the system can create and manage events effectively.
a. Create simulated events and verify their successful creation in the
system.
b. Check for categorization and tagging of events.
c. Validate the creation of the event for the integrated systems for event
generation.
iv. Validate the system's capability to monitor and manage the health and
performance of both applications and infrastructure.
a. Simulate different states and conditions of the systems and
applications which are being monitored to assess system performance.

Page 35 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

b. Monitor resource utilization, response times, and error rates.

c. SLA verifications
d. Invoice Generation Module & Billing audit
v. Confirm that the enterprise management system can automatically
generate accurate and comprehensive reports based on the defined
timelines and frequencies.
a. Schedule and trigger automated report generation.
b. Verify report content, format, and delivery methods.
vi. Confirm that the Mobile application provisioned for the ICCC, and the VMS
are fully functional.
a. Check for the events and alerts received by the ICCC are forwarded
reliably to the mobile application users based on the configured SOPs.
b. Check for the mobile application for the video management system
which should be able to allow the users to access real-time videos,
search for videos, access and download recordings, playback of
recorded videos and any other feature applicable as per the
requirements of the users.
vii. Validate the SOPs which have been implemented that should also
undergo periodic validations. The MSI should choose validation methods
based on the type, complexity, and purpose of the SOPs. Common
methods could include document review, simulation tests, inspection,
testing against predefined criteria, and auditing for compliance with
standards.
viii. Audit of the EMS:
a. Monthly as well as Quarterly audit of the EMS performance
accuracy and stability tests to be conducted in conjunction with
CRIS. MSI to provide the accuracy checks format and demonstrate
the same on a monthly basis.
b. Accuracy tests shall be conducted comprehensively for the EMS
across all the parameters.
c. Accuracy and system stability tests shall be conducted across the
parameters like but not limited to monitoring of different CVMS and
Field installed Edge devices based on thresholds, alerts generation
through different channels, SLA configurations, Penalty
calculations, availability report generation, dashboards generation,
automation, and circulation, RBAC controlled access to EMS
modules, etc.
ix. The PAT should also include validation of the Service levels and check for
corrective actions that are required to address any deviations in service
levels which might involve but are not limited to updating the SLA,
improving the software application, or modifying processes without any
additional financial implications to CRIS.

Page 36 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Periodic acceptance tests shall be conducted on a monthly or quarterly basis or as

per the timeliness defined by CRIS.

6.4.3. Go-Live
The Go-Live in this project shall be declared in two stages namely Phase 1 Go-Live
and the Final Go-Live. This section of the Bid Document Part-II provides the details
of the different milestones that shall be declared in the CVMS project:

1. Phase 1 Go-Live: The Phase 1 Go-Live shall be declared by CRIS based on the
following conditions:
a. MeitY empanelled public cloud environment setup is provisioned to host
the CVMS solution stack as stipulated in the bid document part-II which
includes the below applications:
i. Public Cloud infrastructure along with the required compute,
storage and security infrastructure
ii. Video Management System (VMS)
iii. Integrated Command and Control Center application (ICCC)
iv. Forensic Application (Image & Video)
v. Facial Recognition Solution (FR)
vi. Video Summarization
vii. Enterprise Management System (EMS)
b. On-boarding of 10,000 Cameras [at least 1000 Cameras of each from
Coaches, Locomotives & EMUs/MEMUs] (If the quantity of 10,000
Cameras is not achieved due to delay from CRIS, CRIS may at its sole
discretion decide to declare the Phase 1 Go-Live with the deployment of
less than 10,000 Cameras with a corresponding reduction in the
minimum assured quantity of the cameras).
c. Completion of the primary integration as defined in the Section:
Integrations of Systems.
d. Completion of the Security audit by a CERT-in empanelled agency and
addressing all the vulnerabilities detected during the security audit.
e. Completion of the User Acceptance Tests.
f. Phase 1 Go-Live Completion Certificate issued by CRIS based on
successful completion of User Acceptance Testing (UAT) and the
primary integrations defined in the Section: Integrations of Systems.
g. Designing and implementation of SOPs.
h. Implementation and integration of the mobile app with the CVMS solution
stack.
i. Completion of other integrations like Email Server and SMS server.
j. Configuration of the Service levels in the EMS for both the CVMS
solution stack and the Edge devices.
k. CRIS Shall issue the Go-Live Certificate as per Phase 1 Go-Live
Completion Certificate.

Page 37 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

2. Final Go-Live: The Final Go-Live of the project, will be officially announced by
CRIS and this milestone signifies the following:
a. Completion of the integration of the Edge devices planned under the
CVMS project as mentioned in Section Annexure-2-Edge Layer or
Field Equipment
b. Completion and operationalisation of the primary and secondary
integrations defined in the Section: Integrations of Systems.
c. Completion of the Security audit and addressing all vulnerabilities
detected through the security audit of the complete CVMS solution stack
as per RDSO specification (RDSO/SPN/TC/106/2022 Version 2.1 or
latest amendment) without any additional financial implication to CRIS.
d. CRIS will issue the Project Completion Certificate as per Final Go-Live
Completion Certificate.

3. The Operations Phase of the project shall commence from the Phase 1 Go-Live
and shall remain in force as per the Section Contract Period.

6.5. Capacity Building

Capacity Building for CRIS and Indian Railways which includes preparation of
operational manuals, training documents and capacity building support, including:
i. Training of the respective stakeholders and users on the operationalization
of the system. Please refer to the Section Training for additional details on
the training requirements.
ii. Implementation of the information security policy in compliance with CRIS
ITSG policy, including policies on backup and user management plans.
iii. Revisiting the KPIs for performance monitoring of various systems and
applications of the CVMS solution stack monitored.
iv. Developing new Standard Operating Procedures (SOPs) for incident
management and other services to be rendered by the ICCC Platform.
v. Provide CRIS and Indian Railways with necessary documentation.

6.5.1. Documentation for identified users.

The documentation requirements that the bidders shall provide are elaborated below
but not limited to:

i. Software Manuals: Original Manuals from OEMs (Four Sets, Hard Copy)
ii. Installation Manual: For all the Application Systems (Four Sets, Hard
Copy)
iii. Training Material: Training Material will include the presentations used for
trainings and the required relevant documents for the topics being
covered. (Four Sets, Hard Copy)

Page 38 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

6.5.2. Help/User manuals

Help/User manuals shall be provided by the USI

MSI shall provide the following manuals (up to 4 sets) to CRIS for all applications
listed in the Bid Document Part-II.
i. User Manuals: For all the Application Software Modules, required for
operationalization of the system.
ii. System Manual: For all the Application Software Modules, covering
detailed information required for its administration.
iii. Operations Manual: The MSI shall be responsible for preparing an
Operations Manual for the final solution that has been made operational at
the time of Go-Live for each service of the CVMS solution as mentioned in
the Bid Document Part-II. The prepared documents shall be formally
signed off by CRIS before the completion of the final acceptance test.
These documents shall be provided and maintained in online repository,
updated and reviewed on a quarterly basis to ensure that they are up-to
date for and recent changes that have been made to the CVMS solution.

6.5.3. Manpower to be deployed for the Project

The MSI shall deploy the manpower stipulated in the tender document in Annexure-
23(A) - Project Implementation Phase The requirements of the manpower for the
Project and Operations Phases are elaborated below:

# Manpower to be deployed Phase of Billable as per the

the Project Schedule of
Requirements
a. Project Manager (SPoC)*
b. Surveillance Solution SME Or
Architect*
c. Cloud Solution SME Or Architect*
d. Commissioning Engineer
(Surveillance)
e. Commissioning Engineer (Cloud) Project
1 f. Facial Recognition Solution (FR) Not Billable
Expert* Phase
g. Database Architect*
h. Enterprise Management System
(EMS) Expert*
i. IT/ Cyber Security Expert*
j. Software Developer
k. Software Tester
a. Project Manager (SPoC)* Only Helpdesk
b. Surveillance Solution SME Or Operations
2 Executive and
Architect Phase
c. Cloud Solution SME Or Architect Helpdesk Manager

Page 39 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

d. O&M Engineer (Surveillance)* are billable.

e. O&M Engineer (Cloud)*
f. Facial Recognition Solution (FR)
Expert
g. Database Architect
h. Enterprise Management System
(EMS) Expert*
i. IT/ Cyber Security Expert
j. Helpdesk Executive*
k. Helpdesk Manager/Supervisor*
l. Database administrator
m. Software Developer
n. Software Tester
Table 5:Manpower To be deployed for the Project.
Note:

a. The Project Manager shall be common for both the phases (Implementation & O&M
Phase) of the project and should not be changed while the project migrates from the
Implementation phase to the Operations Phase of the Project.
b. *Key resources for meeting the service levels stipulated in the Section Service Levels .

6.6. Operations Phase (Post Final Go-Live of the Project)

The successful Bidder, post Phase 1 Go-Live phase shall be responsible for the
Operations Phase which are essential for ensuring the smooth functioning, stability,
and ongoing support of the CVMS solution stack.

Further, MSI’s scope shall include below mentioned activities in the Operations
phase for the entire duration of the contract period without any additional cost to the
CRIS:
i. 24x7 Operation and Maintenance of the CVMS Solution Stack.
a. Maintaining the CVMS Solution stack on a 24x7 basis involves
continuous monitoring, support, and management to ensure that the
systems are available and function reliably.
b. The CVMS solution should provide alerts to notify the support team
about potential issues or anomalies.
c. Implement real-time monitoring tools to track system and application
performance continuously.

ii. SLA and Performance Monitoring

a. Monitor and analyse application performance to identify and address
bottlenecks.
b. Generate regular reports on Service Level adherence, highlighting
achievements, areas for improvement and historical trends for capacity
management.

Page 40 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. Communicating SLAs transparently to all relevant stakeholders,

including CRIS internal teams, and management and other Indian
Railway users.
d. Modify SLAs as and when needed based on changing business
requirements, technology advancements, or user expectations.
e. The Enterprise Monitoring System, as directed by CRIS, shall monitor
components not provisioned by the MSI, including but not limited to
WAN links connecting to the CVMS solution stack on the cloud, the
Edge devices deployed in Coaches, Locomotives, EMUs, and MEMUs.
f. The EMS should be configured for monitoring the complete CCTV
surveillance solution against the established Service levels and also
automatically calculate the penalties as per Section Service Levels
and also in the mentioned in the Annexures Annexure-32-SLA of the
Coaches, Annexure-33-SLA of Locomotives and Annexure-34-SLA
of the EMU/MEMU.
g. Implement new SLAs and monitor them using the monitoring solutions
deployed for the CVMS.

iii. Logging, tracking and resolution of issues.

a. Track issues and faults related to the complete CCTV Surveillance
solution namely the CVMS Solution stack and the Edge devices
implemented through the other RFPs mentioned in the Annexure-1-
Other CRIS Bid Documents.
b. Use predefined statuses such as "Open," "In Progress," "On Hold," and
"Resolved" to provide a clear view of the issue lifecycle.
c. Conduct and submit to CRIS root cause analysis to identify the
underlying reasons for the issue.
d. Maintain a historical record of issues, including resolutions,
workarounds, and any lessons learned.
e. Create and submit monthly reports on the faults that are reported and
rectified. Submit improvement plans the CVMS solution stack to reduce
the faults that are occurring on a monthly basis.
f. In case of a failure or degraded performance of the CVMS solution
stack, a detailed incident report including analysis shall be prepared by
MSI in consultation with the OEM of the respective product(s) with an
objective to avoid similar failures in future. Preliminary report should be
submitted within 24 hours. A detailed RCA report shall be submitted to
CRIS as per defined SLA.

iv. Application Maintenance and Enhancements

a. Collaborate with stakeholders, including end-users, to gather
requirements for the desired application enhancements.

Page 41 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

b. Activities shall include bug fixes, performance optimizations, security

updates, compatibility improvements, and feature enhancements.
c. Conduct thorough regression testing to ensure that existing
functionalities are not negatively affected.
d. Dashboard changes as per the user requirement.
e. Integration (changes as well as new) of CVMS application with
Railway, CRIS and other Government applications
applications/databases.
f. Update all types of documentation created and provided for the CVMS
solution stack, including user manuals and system architecture
documents, to reflect the changes made during the enhancement
process.
g. Performance tuning of the respective CVMS applications i.e., resolution
of performance related issues and tunning of supplied system software
for the entire duration of the contract.
h. Major changes and new features to the CVMS solution stack shall be
introduced based on the Section Change Control.

v. User Management
a. Monthly checks on the User IDs created and implemented for the
CVMS Solution Stack to ensure only the valid users with the relevant
privileges only have access.
b. Implement a SOP and also an approval process for addition & deletion
or change of privileges of users to be provided to the CRIS/Indian
Railways officials.

vi. Helpdesk service

a. Implement automated incident response mechanisms to address
common issues without manual intervention.
b. Categorize and prioritize trouble tickets and requests based on urgency
and impact on business operations.

vii. Developing & configuring SOPs as per the user requirement

a. Create clear, concise, and easy-to-follow SOPs that provide step-by-
step instructions for performing tasks and maintaining the system.
b. Monitor the effectiveness of the SOPs and evaluate their impact on
user performance and system maintenance.
c. Regularly update the SOPs to reflect changes in the system, user
needs, or industry leading practices.
d. Communicate any changes on the SOPs to users, ensuring that they
are aware of the updates and understand their impact.

Page 42 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

viii. Establish an escalation Matrix.

a. MSI shall prepare an escalation matrix in consultation with CRIS and
shall involve OEM support teams to ensure faster issue resolution.
b. The Escalation matrix shall clearly identify the stakeholders and
decision-makers by name, and their corresponding roles and
responsibilities and their contact details.

ix. Security
a. MSI shall ensure the hardening of the complete CVMS solution as per
CRIS security policy and industry leading practice as per Section
Designing and Development Phase
b. MSI shall implement and maintain infrastructure and documentation
adhering to industry leading practices in alignment to ISO 27001 for
entire the duration of the contract.
c. Security audit of the CVMS solution as given in Section General Audit
Requirements.

x. Manpower for the O&M Phase of the Project

a. The manpower deployed for the Helpdesk shall be billable as
mentioned in the Section Schedule of Requirement (SOR).
b. Any other manpower which are specified in this Bid Document Part-II to
be provided by the MSI during the Operations phase are not billable.

The MSI and the CSP shall ensure that any changes that are being made to the
CVMS solution should have the approval of CRIS and MSI and the OEM shall
provide an undertaking as per Annexure-45-Undertaking to be provided by the
Bidder & CSP to this effect. While making any changes to the configuration of the
CVMS solution stack, the bidder shall ensure that continuous compliance to ISO
27001 is maintained throughout the contract period.

6.7. System Audit (Overall CVMS solution)

6.7.1. General Audit Requirements
i. The MSI shall conduct a comprehensive security audit of CVMS solution
on a bi-annual basis, by engaging a Government Agency selected from
the List of CERT-in empanelled security auditors.
ii. On completion of the security audit conducted by a Government Agency
selected from the List of the CERT-in empanelled vendor, the MSI shall
implement the mitigations for the detected vulnerabilities and shall submit

Page 43 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

the final closure report to CRIS as per the SLAs mentioned in this Bid
Document Part-II without any additional financial implication to CRIS.
iii. The MSI shall submit to CRIS the findings / non-compliances of security
audit and shall also submit the compliance reports for the findings / non-
compliances.
iv. The MSI shall comply with Third Party Audits and other regulatory,
statutory, and compliance requirements as applicable during the entire
period of contract without any additional financial implication to CRIS.
v. The Third-Party Auditor shall be authorized by CRIS to conduct
comprehensive security and compliance audits on the complete CVMS
solution.
vi. In addition to the CERT-in empanelled Government Agency conducted
security audit, CRIS shall also undertake annual audits of the complete
CVMS solution stack as per the RDSO guidelines and the MSI is required
to coordinate and extend the required support to ensure that the audits are
successfully completed.
vii. Based on the vulnerabilities detected in the security audit, the MSI shall
once again address the discovered security vulnerabilities without any
additional financial implication to CRIS and submit the final closing report
to CRIS.

6.7.2. Technical Audit Requirements

i. The MSI shall provide safe to host (STH) certificate prior to hosting CVMS
applications in production environment and the certificate shall be valid
during entire period of contract.
ii. The MSI shall perform security assessment for all systems and
applications of the CVMS solution including underlying infrastructure,
software, and application.
iii. The MSI shall define plan and timeline to close the vulnerabilities
according to their criticality (all vulnerabilities to be closed within the cycle)
and should periodically review the open vulnerabilities to ensure timely
closure.
iv. The MSI shall provide the level of severity and frequency of security
updates for the CVMS solution including underlying infrastructure,
software and application in consultation with CRIS. The same must be
followed in terms of execution and information updated to CRIS.
v. The MSI shall manage and ensure the availability of all types of logs
including all VMs, OS, DB, network, applications, etc. The logs shall be
retained for a minimum period of six months.
vi. Information in the logs includes the following:
a. Time the API activity occurred.
b. Source of the activity

Page 44 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. Target of the activity

d. Type of action
e. Type of response
vii. The MSI shall ensure that the Configuration management and change
control of Network and Security devices shall be done in compliance of
ITIL standards and processes and by using a defined change control
process.
viii. The MSI shall ensure that the offered auditing service should facilitate the
delivery of logs or events to government agencies for auditing and forensic
purposes as directed by CRIS when required.
ix. The MSI shall ensure that all the unused features and services of the
CVMS Solution should be disabled to avoid any security vulnerabilities.
Any such unused features and services found operational during the
audits of the CVMS solution stack shall be considered as a serious non-
compliance.

6.8. Helpdesk & Training

6.8.1. Helpdesk
The MSI shall provide helpdesk services to the users of the CVMS solution, and
the responsibilities shall include but not limited to:

1. The MSI shall establish the helpdesk and shall ensure around-the-clock
availability of manpower to provide support.
2. The Helpdesk should be staffed with a minimum of 5 nos. of Helpdesk executives
supervised by a Helpdesk Manager on a 24x7 basis post the Phase 1 Go-Live of
the project.
3. The Helpdesk shall be stationed at the CRIS designated premises and should be
staffed on a 24x7 basis.
4. The helpdesk manpower shall be trained for their allocated roles and
responsibilities.
5. Generate regular reports on system performance, incidents, and resolutions.
Circulate the reports to CRIS stake holders to monitor KPIs of the Helpdesk
team.
6. Conduct regular reviews with the CRIS stakeholders to identify trends and
improvement opportunities.
7. MSI shall define the escalation matrix for helpdesk to escalate incident, tickets
and issues to further level.
8. The Helpdesk Team should also be reachable through a mobile number
(minimum 3 nos.) on which the users can also reach out to the helpdesk through
any popular chat application. The MSI should provide the necessary Mobile
handsets (Smart Phones) and the mobile SIMs. The charges for the mobiles

Page 45 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

monthly subscriptions should also be paid and managed by the MSI. The MSI
should ensure that the mobile SIMs are available and operational for the
complete period of the contract.
9. The Helpdesk role and responsibilities are defined further below:

a. Establish an incident management process to promptly address and resolve

system issues and the requests registered with the helpdesk.
b. Provide Helpdesk services as per the defined SLAs for response and
resolution times and review and report on SLA adherence.
c. Helpdesk shall offer support through various communication channels such as
phone, email, and chat applications to the users logging the trouble tickets.
d. Helpdesk shall provide support for any faults or requests that may be received
from the users related to the CCTVSS and the CVVRS solutions.
e. Helpdesk shall be responsible to conduct the first level of trouble shooting to
analyse and understand the alerts and events reported by the EMS. Similarly,
the helpdesk team shall be responsible to address and process the requests
that have been received by them.
f. Helpdesk shall be responsible wherever applicable to assign, update and
follow up on the automatically generated and manually generated trouble
tickets.
g. The helpdesk shall assign the trouble ticket or request ticket to the concerned
stake holders like the Surveillance team supporting the CVMS layer, the
vendors and stake holders who are supporting the Network Layer, the
vendors and stake holders supporting the Edge Layer, CRIS, etc.
h. The Helpdesk team shall act as a nodal point for coordination with multiple
stake holders like CRIS stakeholders, the vendors managing the edge
equipment installed in the field (Coaches, Locomotives, EMUs and MEMUs)
and any other stake holders involved with the CCTV Surveillance project
implementation and maintenance.
i. Categorize and prioritize incidents based on severity and impact on
operations.
j. The helpdesk shall communicate with users to gather additional information,
clarify details, or provide updates on the status of their reported issues on a
time-to-time basis.
k. Shall ensure that the trouble tickets or service requests are routed to the
appropriate support personnel or teams to ensure resolution or completion of
requests.
l. The Helpdesk personnel shall monitor the status of tickets and escalate them
wherever required as per the escalation matrix.
m. The helpdesk agents shall create, update the tickets based on the resolutions
of the faults or the status of the requests provided to the users.
n. Assist users with issues related to system functionality, features, and usage.
o. Conduct thorough troubleshooting to identify and resolve technical issues.

Page 46 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

p. Provide step-by-step guidance and provide remote assistance by using

diagnostic tools to facilitate quick issue resolution and minimize the need for
on-site visits.
q. Helpdesk personnel shall be responsible for identifying and categorizing the
reported issues accurately and shall create trouble tickets or service requests
accordingly.
r. This help desk will also provide support to do the effective incident
management in case of any emergency or disaster.

6.8.2. Training
The MSI as part of the scope also shall provide trainings on the offered
CVMS solution to the different stakeholders identified by CRIS. Some of
the training activities include but not limited to:
i. The trainings shall be conducted by the MSI at the CRIS designated
locations across India as per the details mentioned in the Table
6:Training.
ii. The training plan and contents will be finalized following discussions with
CRIS/Indian Railways stakeholders, though an indicative scope of the
training has been mentioned in this section.
iii. Training arrangements like the training rooms, projectors/displays, user
terminals, etc shall be arranged by CRIS. The MSI at their own expenses
shall arrange for printouts/handouts of the Slides/Manuals/etc. for
distribution to the trainees.
iv. Role-based training for people at different levels of monitoring, control and
usage of the CVMS Solution stack.
a. First level responders using the mobile apps.
b. ICCC Operators of CRIS and Indian Railways
c. CRIS and Indian Railway users to operate and administrate all
applications of the CVMS namely ICCC, VMS, FR Solution, Video
Summarization, Video Forensics, EMS, etc.
d. Vendors of the Edge Devices installed in the Coaches, Locomotives,
EMUs and MEMUs
e. Viewing the Health states of the edge devices on the EMS
f. Updating and closing Trouble tickets
g. Patch management
v. “Train the Trainer” programs, where members of the CRIS/ Indian
Railways staff would be trained to enable them to conduct further training
programs, thus helping build up scalability in the training program and
reducing the dependency on external vendors for training.
vi. System Administrator training: Members of the CRIS staff shall be trained
to act as system administrators and trouble-shooters.

Page 47 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

vii. MSI shall conduct end user training and ensure that the training module
holistically covers all the details around the system applications expected
to be used on a daily basis to run the system.
viii. MSI shall train officers and other staff nominated by CRIS in different
aspects of solution usage, operations, maintenance, and troubleshooting.
ix. MSI shall conduct end user training and ensure that the training module
holistically covers all the details around the system applications expected
to be used daily to run the system.
x. MSI shall prepare the solution specific training manuals and submit the
same to CRIS for review. Training Manuals, operation procedures, visual
help-kit etc. shall be provided in English language.

The training modes that shall be used by the MSI should be a mix of classroom
trainings, remote Video Conferencing or eLearning sessions which shall be decided
by CRIS. The MSI shall also provide the training contents like user manuals,
multimedia files, presentation slides, etc. The below indicative training types and
schedules shall be considered for sizing the training requirements:

Page 48 of 455
 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Numbers of
Training Batches & To be High level Scope of
# Users Type Location Premises Batch Size Frequency
Type Session Provided by the Training
Type
End-to-end training on
all aspects including,
but not limited to:
a. Public Cloud
Concepts
b. Detailed
Up to 25 nos.
Classroom – Understanding of
participants in
2 no. For 10 the CVMS
each batch
Working Architecture and
Days their
Classroom interdependency &
Training for integrations.
Respective
Technical & first year c. Applications Inter-
Technical Provided by OEMs of
1. Administrator Delhi NCR dependency &
Training CRIS CVMS
training Annual Integration,
components
Online d. Administration,
Refresher configuration &
course for 3 privilege
Days (after management
No limit on first year) e. Role Based Access
Online – 1
participants in f. Performance
no.
each batch monitoring,
optimization, and
backup strategies
g. “Train the Trainer”
h. Hands-on exercises
for practical skills
Indian Indian Up to 30 nos. For 3 a. Understanding of
CVMS Helpdesk & Classroom –
2. Railways Railways participants in MSI Working the CVMS Solution
Operators ICCC Operators 15 no.
Zonal HQs Premises each batch Days its various systems
 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Numbers of
Training Batches & To be High level Scope of
# Users Type Location Premises Batch Size Frequency
Type Session Provided by the Training
Type
(Pan India) Classroom and subsystems
Training for b. Incident
first year Management
c. Troubleshooting
Annual d. Configuration
Online Management
Refresher e. Understanding of
No limit on
Online – 2 course for 1 the configured
participants in
nos. Day (after SOPs.
each batch
first year) f. Understanding of
various features in
different Access
levels
g. “Train the Trainer”
h. Hands-on exercises
for practical skills
a. Understanding of
For 2
the CVMS Solution
Up to 50 nos. Working
Classroom – its various systems
participants in Days
20 no. and subsystems
each batch Classroom
b. Incident
Training for
Indian Management
Indian first year
User Mobile & Railways c. Understanding of
3. Railways MSI
Training Desktop Users Locations the Configured
Premises Annual
(Pan India) SOPs
No limit on Online
Online – 5 d. Requesting specific
participants in Refresher
no. video feed
each batch course for 1
e. “Train the Trainer”
Day (after
f. Hands-on exercises
first year)
for practical skills

Table 6:Training

Page 50 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

6.9. OEM Support for the Project

6.9.1. OEM Involvement in Project Implementation and O&M:
i. The Master Service Integrator (MSI) shall ensure that the OEMs of the
software supplied for the Central Video Management System (CVMS)
solution should perform the installation, configuration, and integration
activities during the project implementation phase.
ii. The OEM's involvement should not only include Installation, Configuration
and Integration but also providing technical expertise, guidance, and
assistance to ensure the end-to-end integration of the software.
iii. After the declaration of Phase 1 Go-Live the OEM support shall also be
provided during the Operations phase of the project for the complete
period of the contract.
iv. The MSI shall ensure that an Installation & Commissioning Certificate is
provided for each system and application that is being installed for the
CVMS solution as per ANNEXURE-43- Certificate for I&C and Annual
Audits and this certificate should also be certified by the respective
OEMs.

6.9.2. OEM Support Protocols

The MSI shall establish and share with the CRIS the following support information for
each of the products supplied for the CVMS solution:
i. Call Logging Process: Define and document the process for logging
support calls with the OEM, including required information and escalation
procedures.
ii. Software Bug Reporting Process: Define and document the process for
reporting software bugs to the OEM, detailing the information required and
the expected resolution timeline.
iii. Patch Updating: Document the process for obtaining support from the
OEM for patch updates, including the frequency of updates and the
procedures.
iv. Performance Tuning Support: Resolution of performance-related issues
and tuning of all supplied system software and applications.
v. Troubleshooting Support: Troubleshooting in case of critical failures
(system or services) especially for the failures extending beyond the
permissible downtime.
vi. Escalation Matrix: Provide an escalation matrix that defines the hierarchy
of contacts and procedures for escalating issues to higher levels within the
OEM's support structure.
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

vii. Root Cause Analysis (RCA): RCA of failure and/or incidents along with
an action taken report to preclude recurrence of similar failures/incidents in
future.
viii. OEM Support Turnaround Times: Should provide the turnaround times
for support requests raised with the OEM to CRIS, specifying response
and resolution timeframes along with the escalation matrix.1
ix. Support Plan Details: The MSI is required to offer 24x7 premium support
service from the OEM, for the entire CVMS solution for the entire period of
the contract from the date of Phase 1 Go-Live.
x. Support Portal Login Credentials: Provide the necessary login
credentials and instructions for accessing the OEM's support portal for
logging and tracking of support tickets.
xi. Additional Relevant Information: Share any other relevant information
deemed essential for obtaining immediate and effective support for the
CVMS solution during the project and Operations phase from the OEM.

7. Sizing Parameters for the CVMS Solution

i. The storage tiering solution should be aligned with the following
requirements (FIFO basis):
a. Frequent storage for 07 days for all types of data.
b. Post 07 days the data shall be transferred to Infrequent access for 23
days for all types of data.
c. Post 30 days (07 days frequent storage + 23 days infrequent storage)
the data shall be transferred to Archival/long-term retention for 180 days
for flagged and bookmarked data.
ii. For incidents that are flagged by the user or any court order, the video of
the relevant portion from all relevant cameras should be stored/archived
separately for investigation purposes.
iii. Audit trail of the system to be maintained on permanent basis / as per the
backup policy defined.
iv. Retrieval time for any data stored should comply with the defined service
level agreements. MSI shall consider appropriate data storage, data
transfer and data retrieval changes as required to meet these data
retention policies.
v. The detailed parameters that shall be considered for the sizing of the
overall CVMS solution are elaborated in the below table:

Page 52 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Description For Locos (CVVRS For Coaches For

& RDAS) (CCTVSS) EMUs/MEMUs
(CCTVSS &
CVRRS)
Total Number • Loco with 14 (12 • Coaches with 08 • EMU / MEMU
of Units CVVRS + 2 Cameras - 38,255 with 8
RDAS) Cameras • Coaches with 06 Cameras -
- 9,652 Cameras - 960 8563
• Loco with 12 (10 • Coaches with 05 • EMU / MEMU
CVVRS + 2 Cameras – 2,744 with 7
RDAS) Cameras • Coaches with 04 Cameras – (6
- 1,596 Cameras – 2,079 CVVRS + 1
• Loco with 10 (08 RDAS)
CVVRS + 2 Cameras- 50
RDAS) Cameras • EMU / MEMU
- 3,111 with 6
Cameras (6
CVVRS) - 125

RDAS 28,718 Cameras Not Applicable 50 Cameras

Cameras
Total number 1,85,390 Cameras 3,33,836 Cameras 69,604 Cameras
of Cameras
(Including
RDAS)
Total number 28,718 44,038 8,738
of M-
NVR/NVR/VR
U
High Priority • Live streaming & • Camera Tamper For DMC:
Data recording of 01 alert messages & • Live streaming
Cab view alert videos (30 & recording of
camera at Loco seconds prior and 30 01 Cab view
Pilot side of the seconds post) camera.
active cab. events at Full HD
• On-demand
• On-demand live resolution.
live streaming
streaming of any • Panic button alert of any other
other camera of messages & alert camera of the
the locomotive. videos (60 seconds DMC.
• Alert messages prior and 60 seconds
• Alert
& alert videos post event) at Full
messages &
(30 sec prior and HD resolution.
alert videos
30-sec post • Cropped New Face

Page 53 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Description For Locos (CVVRS For Coaches For

& RDAS) (CCTVSS) EMUs/MEMUs
(CCTVSS &
CVRRS)
events, which Images of pixel size (30 sec prior
shall be 70-pixel x 70-pixel. and 30-sec
configurable) on • On-demand live post events,
priority for Driver streaming of any which shall be
behaviour camera of the coach. configurable)
captured by • Device Health on priority for
RDAS, Camera related alerts. Motor man
Tampering along behaviour
with Metadata at The above-mentioned captured by
Full HD high-priority data shall RDAS
resolution. be received to the (wherever
• Device Health- CVMS** on priority. applicable),
related alerts. Camera
Tampering
The above-
along with
mentioned high-
Metadata at
priority data shall be
Full HD
received to the
resolution.
CVMS** on priority.
• Device Health-
related alerts.
For Passenger
area of DMC & all
other Coaches):
• Camera
Tamper alert
messages &
alert videos
(30 seconds
prior and 30
seconds post)
events at Full
HD resolution.
• Panic button
alert
messages &
alert videos
(60 sec prior
and 60 sec
post event) at
Full HD
resolution.
• Cropped New
Face Images

Page 54 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Description For Locos (CVVRS For Coaches For

& RDAS) (CCTVSS) EMUs/MEMUs
(CCTVSS &
CVRRS)
of pixel size
70-pixel x 70-
pixel.
• On-demand
live streaming
of any camera
of the coach
• Device Health
related alerts.
The above-
mentioned high-
priority data shall
be received to the
CVMS** on
priority.
Normal • Transfer of copy • Transfer of copy of • Transfer of
Priority Data of all recorded all recorded video copy of all
video feeds to feeds to CVMS** recorded video
CVMS** from from the VRU/M- feeds to
the NVR. The NVR. The normal CVMS** from
normal priority priority data must be the
data must be received to the VRU/M-NVR/
received to the CVMS** on a best- NVR. The
CVMS** on a effort basis*. normal priority
best-effort data must be
basis*. transmitted to
the CVMS** on
a best-effort
basis*.
Continuous For 30 days For 30 days For 30 days
recording
Resolution of Full HD (H.265) with 24/25 Frames per Second at average
data to be recording bandwidth of 3Mbps per channel
recorded &
Video
Compression
Flagged & For 180 days For 180 days For 180 days
Bookmarked
Recording

Page 55 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Description For Locos (CVVRS For Coaches For

& RDAS) (CCTVSS) EMUs/MEMUs
(CCTVSS &
CVRRS)
FR images NA For 30 days For 30 days
storage
FR matched NA For 90 days For 90 days
images
storage
Total number NA 88,076 18,027
of Panic
buttons
Users Users as defined in Section Users of the CVMS of the Bid
Document Part-II.
Total number NA 1,76,152 55,024
of cameras in
which FR is
implemented
New Faces NA Minimum 100 Minimum 100
Per Hour Per
Coach
Table 7:Sizing Parameter of CVMS Solution
*Best effort basis –The best-effort basis refers only to the network constraints.

** At the discretion of CRIS, the CVMS may be deployed at two different Data Centers to
record the Normal-priority data (refer Section Sizing Parameters for the CVMS Solution).
The Normal Priority data may be stored at a CRIS provided On-Premises data Center in the
near future. The supply & implementation of the infrastructure for the On-Premises data
Center shall not be part of the scope of the CVMS tender. In such cases, the selected MSI
shall provide all necessary support for a seamless migration, transition, and handover
without any additional financial implication to CRIS.

The edge devices installed in the Field namely the Coaches, Locomotives and the
EMUs & MEMUs are also configured for QoS. The data generated at edge devices
installed in the field within Coaches, Locomotives, EMU & MEMU systems is
classified into two categories: high priority and normal priority data. Further details
regarding the types of data are provided in section Sizing Parameters for the
CVMS Solution. High priority data will be prioritized at the NVR end and promptly
transmitted to the CVMS servers. Therefore, the MSI should ensure that the storage
is provisioned appropriately and should be accordingly provisioned.

Page 56 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

In addition to the above sizing parameters, every year there are planned events and
emergency situations that shall add to the load and hence the MSI should consider
such additional loads while sizing the infrastructure of the CVMS solution. The
Guidelines for meeting the additional workloads for the Planned Events and the
Emergency Situations are elaborated below.
For Planned Events:
The occurrences mentioned above may exhibit variations on a year-to-year basis,
and for calculation purposes, these instances typically span around 30 to 45 days of
the total calendar days. During this period, the total peak load on the comprehensive
Centralized Video Management System (CVMS) infrastructure, encompassing data
storage, videos, users, and field-generated alerts, is expected to surge by up to 20%.
MSI is tasked with designing a solution that aligns with handling the overall load
efficiently during these planned events.
For Emergency Situations:
During this period, the total peak load on the comprehensive Centralized Video
Management System (CVMS) infrastructure, encompassing data storage, videos,
users and field-generated alerts, is expected to surge by up to 40%. MSI is tasked
with designing a solution that aligns with handling the overall load efficiently during
these emergency situations.
Note: For retention of the stored data in the CVMS Stack hosted on the Public
Cloud, beyond the mentioned time periods in the above table, the same shall be
downloaded by the MSI on to storage media and should be handed over to
CRIS/Indian Railways for further storage.
8. Functional Specifications
8.1. Video Management System
8.1.1. Specifications
The video management system shall constitute a platform which will be designed for
viewing, recording, and replaying video, and audio as part of the overall project
solution. Video Management Software shall have the following features:
i. VMS shall be a holistic, highly scalable enterprise-level software solution
built on an open architecture. VMS shall not require any proprietary
hosting infrastructure.
ii. VMS shall provide a user-friendly interface and a provision to add the
required numbers of cameras on a unit-by-unit basis.
iii. The proposed VMS software shall support real-time and on-demand
viewing both directly through the camera or from the cloud environment.
iv. VMS shall have a provision to allow users with administrative rights to
create clients (users) and give access based on predefined roles.

Page 57 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

v. The VMS solution shall have the audit log feature to record the date and
time of action, the user who acted, the computer on which the action was
performed and the description of the action.
vi. The proposed VMS shall have the capability to resume recording (from the
point it was missed/stopped) in case any of the Software, hosting
infrastructure and M-NVR/NVR/VRU operations are interrupted like power
disconnection and once the edge devices and hosting infrastructure are
restarted.
vii. The VMS shall support network fault-tolerant recording such that if the
network connection becomes unavailable, for example through network
availability, network congestion or WLAN interruption, the system
operation shall automatically recover when the connection is restored.
viii. The VMS shall be capable of handling both IPv4 and IPv6 Unicast and
Multicast traffic.
ix. The architecture of the proposed VMS solution shall not have any
limitations on the number of devices connected (shall be capable of
supporting a minimum of 7 lakh+ edge devices in a single GUI), while
supporting functionalities mentioned in this Section Video Management
System.
x. VMS shall be deployed in a clustered/federated environment and support
an inbuilt mechanism for high availability and failover. VMS shall ensure
that there is no loss of data/recording/configurations during failure of
directory/recording resources.
xi. The switchover time (in case of any failure) shall not be beyond One (1)
Minute and there should not be any loss of data due to failure.
xii. The proposed VMS solution shall have an inbuilt automatic logging out of
users after a period of inactivity. The time for Auto log out shall be user-
configurable to prevent unauthorized access to the system.
xiii. The Video Management system shall support multiple instances designed
to handle limitless sessions, multi-sites, and multiple hosting infrastructure
for 24/7 Video Surveillance.
xiv. The VMS shall provide a truly unified management experience for CVMS
solutions, simplifying monitoring center operations and respective systems
and integrated applications (upward & downward) while minimizing the
total cost of ownership and increasing operational efficiency for rapid
decision-making.
xv. VMS shall support a flexible rule-based system driven by schedules and
events.
xvi. VMS shall have the ability to support and function with any of the video
wall systems.
xvii. The proposed VMS solution shall not have any additional cost for client
users.

Page 58 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xviii. The proposed VMS shall support ONVIF compliance internet protocol (IP)
cameras, and the capability to integrate M-NVR/NVR/VRU and any other
VMS from different vendors.
xix. VMS shall support various video resolutions HD, D1, CIF, 2CIF, 4CIF, Full
HD up to 12 MP.
xx. VMS shall have a load balancing feature for effective utilization of
resources & optimal performance.
xxi. All third-party SDK/API shall be configured with VMS in such a way, that
any failure or instability in third-party SDK/API does not affect the core
VMS application.
xxii. The proposed VMS solution shall have an administrator interface to allow
setting system parameters, managing codecs, permissions, role-based
accesses, and storage from a centralized location for all respective users.
xxiii. The VMS shall have role-based authentication such as power user, admin
user, client user etc. The same shall be customizable as per user
requirements.
xxiv. VMS shall be able to auto-discover all IP devices available in the network
and filter out the new IP devices that are not configured in the VMS.
xxv. VMS shall provide an integrated secure, scalable, and easily accessible
software-based solution for the management of existing & future edge
devices.
xxvi. The VMS shall have the ability to allow the administrator to set rules (user-
specific) for storing and avoiding data deletion of the flagged/bookmarked
data, critical data, and Incident reports based on the criticality of the data.
xxvii. VMS shall support MPEG-4, MJPEG, AAC/MP4, H.264, H.265 or better
video compression.
xxviii. The VMS shall support only secured media stream requests unless
explicitly configured otherwise. Secured media stream requests shall be
secured with strong certificate-based authentication leveraging RTSP over
TLS Client authentication for media stream requests is claims-based and
may use a limited lifetime security token.
xxix. The proposed VMS solution shall have the following encryption features:
a. The VMS shall offer the ability to encrypt the media stream, including
video, audio, and metadata with authenticated encryption. Media
stream encryption shall be done at rest and in transit and be a
certificate-based AES 128/256-bit encryption.
b. The VMS shall allow encryption to be set on the respective streaming
of all cameras.
c. Use Secure RTP (SRTP) to encrypt the payload of a media stream in
transit and allow multicast and unicast of the encrypted stream.
d. Allow encrypted streams to be exported.

Page 59 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

e. The VMS solution shall protect archived audio & video files and the
system database against network access and non-administrative user
access.
xxx. To allow complete transparency and anti-tampering of evidence, the
proposed VMS solution shall have the following features:
a. The VMS shall allow exporting evidence by populating a video export
list.
b. Provide a timestamp on the downloaded video with the digital
signature.
c. Tool for exporting video various media such as USB keys, CD/DVD-
ROM for evidence in an encrypted format.
d. Provision to allow external agencies to view recorded/encrypted
videos.
e. VMS shall support exporting videos in tamper-proof format.
f. The VMS shall be able to export parts of recordings to a separate
folder (in the respective operating system), which can then be written to
CD-ROM, DVD-ROM, or USB Flash Drives etc. to be played back at a
location not connected to the network video management & recording
network. The export process shall make available a player application,
which can be provided with the exported video. Export shall be
possible in media player-compatible format.
g. The system shall provide secured recording for evidence purposes and
user authentication to protect data integrity.
xxxi. The software shall have multiple streaming methods such as multi-live
streaming, and multi-casting streaming methods to effectively make use of
bandwidth, the software shall accept different streaming transport modes
RTP over UDP, RTP over RTSP, RTP over HTTP, RTP over multicast,
HTTPs over TCP, secure RTMP over TCP. The same steams shall be
sent via RTSP secured (UDP), secured Web RTC and Secured (TCP)
mode to the required user.
xxxii. The VMS shall support Direct Multicast from the Camera. For network
topologies that restrict the Application from sending multicast UDP
streams, the application shall redirect audio/video streams to active
viewing clients on the network using multicast UDP directly from cameras,
and the architecture should use Multicast streaming via recording hosting
infrastructure.
xxxiii. All CCTV camera video signal inputs to the system shall be provided to
various integrated command control center (s), viewing center (s), etc.
xxxiv. All streams to the above locations shall be available in real time and at full
resolution. Resolution and other related parameters shall be configurable
by the administrator to provide for network constraints.
xxxv. The VMS shall provide a drag-and-drop feature for cameras to be viewed
from the list of cameras in the specific Coach/Locomotive/EMU/MEMU.

Page 60 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xxxvi. VMS shall support multi-tenant architecture for better resource

management and scalability.
xxxvii. VMS shall have auto-scaling of resources to match the cloud computing
paradigm.
xxxviii. VMS shall be agnostic to the cloud and edge devices and shall seamlessly
work in any cloud infrastructure without any dependency on a particular
cloud-native application or services.
xxxix. VMS shall support all standard formats for audio/video/images including,
but not limited to:
a. JPEG, PNG, BMP, TIFF
b. AVI, WMV, MP4, MPEG-4
c. MP3, WAV Audio/MP4
d. Other non-proprietary formats
xl. The VMS shall support bookmarking the videos (important events for later
retrieval on any archiving camera), allowing users to mark incidents on live
and/or playback video streams.
xli. VMS shall be configured in such a way that a single rule shall allow for
executing multiple systems actions.
xlii. The VMS shall support the following administration & operations functions:
a. Adding an IP device
b. Updating an IP device
c. Updating basic device parameters
d. Adding/removing channels
e. Adding/removing output signals
f. Updating an IP channel
g. Removing an IP device
h. Enabling/disabling an IP channel
i. Refreshing an IP device (in case of firmware upgrade)
j. Multicast at multiple aggregation points
k. Live display of cameras.
l. Live display of camera sequences.
m. Playback of archived video.
n. Retrieval of archived video.
o. Instant Replay of live video.
p. Use of site maps.
q. Configuration of system settings.
xliii. VMS shall support access and view of cameras and views on a
smartphone or a tablet (a mobile device) on both Android and iOS devices.
xliv. The VMS should have auto discovery feature to collect information about
all IP devices (Cameras, Switches, Servers, NVR, Storage, Workstations
UPS etc) connected on the network. Auto discovery also ensures to
generate alert when new devices are introduced on the network for

Page 61 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

monitoring them for any suspicious activity. It should also generate alert
whenever a device is detached from the network.
xlv. VMS shall provide a provision for multi-factor authentication for the
operator.
xlvi. VMS shall have a feature to store two video streams with different
resolutions that can be recorded from a single device and adaptively
choose between them for playback.
xlvii. VMS shall organize events into various categories such as hardware,
devices, priority alerts, health, integrations etc.
xlviii. The VMS shall support the use of rules to determine when specific actions
occur. Rules shall define what actions shall be carried out under specific
conditions. The system shall support rule-initiated actions such as:
a. Start and stop recording.
b. Set non-default live frame rate.
c. Send notifications via email, SMS, Mobile Application (iOS & Android),
etc.
d. Pop-up video on designated Client Monitor recipients
e. Defining the priority of the live view access of the cameras
f. Pop-up live video stream on GIS map of ICCC
xlix. The VMS shall support SNMP trap and Active Directory or LDAP.
l. The Video Management system shall not limit the number of video
recording servers that can be networked/clustered together to form a video
management and recording system.
li. The VMS shall enable the client to dynamically create connections
between cameras and clients and view live or recorded video on Monitors.
lii. The VMS shall provide the client with seamless operation of all cameras
and clients available in the system regardless of the actual connection to
different Network Video Recording servers.
liii. The VMS shall detect signal loss and have the capability to alert the
system administrator.
liv. The Video Management Software shall support the following: -
a. The Video Management Software shall provide a user-configurable tile
pattern to view the number of cameras.
b. The VMS shall support edge device settings. Each channel configured
in the VMS shall have an individual setup for the following settings, the
specific settings shall be determined according to the encoding device:

• Resolution
• Frame Rate
• Bit Rate
• Recording scheduling

Page 62 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. The Video Management Software shall have the capability of creating

camera sequences with the following functionalities:

• Guard View / Camera sequencing feature shall have the capability to

organize and display camera feeds of up to 1000 cameras.
• Each camera in the sequence shall have user-configurable dwell
time ranging from 1 to 60 seconds.
• Multiple users shall be able to view the same camera sequence
simultaneously, not necessarily synchronized one with the other.
• Web and Mobile surveillance shall be available.
• Event-based playback shall be available.

d. The VMS shall provide an alarm management module.

• The alarm management module of the VMS shall be able to set any
monitor or groups of monitors to display cameras automatically in
response to alarm inputs.
• The VMS application shall have a feature that automatically notifies
users who have bookmarked/flagged a video for further investigation
before the default storage period has elapsed.
• The alarm management shall be able to reset automatically or
manually alarm video.
• The alarm management module shall allow for monitoring of the
operational status and event-triggered alarms from various system-
hosting infrastructures, cameras, and other devices.
• Shall provide a real-time overview of alarm status or technical
problems while allowing for immediate visual verification and
troubleshooting. An alarm Filtering option should be available, for
example, it should be possible to “silence” alarms for a desired
period.

e. It shall be possible to search for recordings in the software by camera,

date, and time. If a date and time are specified, playback shall
commence from that date and time. It shall be possible to playback
more than one camera simultaneously.
f. The software shall support at least 64 video streams concurrently on a
single workstation. It shall support at least four monitors in one
workstation for displaying live video. It shall allow a minimum of three
levels of user and alarm prioritization. It shall allow a minimum of
10,000 cameras to be re-played simultaneously by respective users.
lv. The user shall have a Help Tab to provide a quick search for topics related
to VMS.

Page 63 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

lvi. The VMS shall have the facility to choose the resolution of the recorded
video feed by respective client users concerning the available bandwidth
i.e., if the camera feed is stored in Full HD resolution in the public cloud,
however, the respective client users are in low bandwidth zone, VMS shall
provide a facility to select the resolution type (HD, D1, CIF, 2CIF, 4CIF,
Full HD etc.) of the recorded video.
lvii. VMS shall provide the following GUI features:
a. All CCTV camera locations shall be overlaid in the GIS on the VMS
Graphical User Interface (GUI). The camera selection for viewing shall
be possible via clicking on the camera location on the graphical map.
The graphical map shall be of high resolution enabling the operator to
zoom in for specific locations while selecting a camera for viewing.
b. The GUI software shall support any form of IP network connectivity
including LAN, WAN and wireless LAN technologies.
c. The GUI software shall support multicast and unicast video streaming.
d. The GUI software shall provide a mechanism, which verifies the validity
of the user.
e. The GUI software shall allow for live monitoring of video.
f. It shall enable a view of 1 to a minimum of 16 video tiles
simultaneously on a single digital monitor at 25 fps per camera.
g. The software shall provide on each of the digital monitors
independently the following tile views:

• Fullscreen
• Quad View
• User configurable tile view
• The Software shall also support any other window division based on
the site requirement.

h. The GUI software shall allow operators to view an instant replay of any
Camera.

• The operator shall be able to define the amount of time he/she

wishes to go back from a timeline bar or through a custom setup
period.
• The operator shall be able to control the playback with play, pause,
forward, and speed buttons.
• Whilst live control and monitoring is the primary activity of the
monitoring workstations, VMS shall allow for GUI features such as
video replay, view surround cameras & pre- and post-alarm
recording display.

Page 64 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

i. The operator shall be able to choose and trigger the following minimum
action from a map:

• View the Camera in a video tile.

• View the map or procedure in a video tile.

j. The GUI software shall provide management and control over the
system using a standard PC mouse, keyboard, and Digital keyboard.
k. The GUI software shall display all cameras attached to the system
regardless of their physical location on the network.
l. The GUI software shall display all camera sequences created in the
system.
m. The GUI software shall allow operators to control (pause/play, skip
forwards, skip backwards) camera sequences.
n. The GUI software shall display all cameras, sequences, and users in a
logical tree.
o. The GUI software operator shall be able to drag and drop a camera
from a tree of available cameras into any video tile for live viewing on
the map.
p. The GUI software operator shall be able to view the camera from a tree
of available cameras into any video tile for live viewing.
q. The GUI software shall support graphical site representation (map)
functionality, where digital maps are used to represent the physical
location of cameras and other devices throughout the facility.
r. The GUI with an inbuilt GIS map display shall have the ability to
contain hyperlinks to create a hierarchy of interlinked maps.
s. The GUI software operator shall be able to view the camera from a
map into a video tile for live viewing in the same browser without
opening a new browser.
t. The GUI software shall support digital zoom on a fixed camera’s live
video streams.
u. The software shall be able to display video of cameras on Large
Format Display Monitors and Workstation Monitors.
v. The software shall allow the control of display from the client's PC.
w. The operator from the GUI software shall be able to decide the screen
layout and the cameras that shall be displayed on the monitors.
x. The software shall support multicasting.
y. The VMS shall allow playback and live view of the same camera
simultaneously.
z. The GUI Software shall support text superimposing the title and date &
time on the video.
aa. The VMS shall provide Mobile Applications for both Android and iOS
devices.

Page 65 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

lviii. In the edge devices, the M-NVR/NVR/VRU are equipped with two
SIM/eSIM slots, each intended for a 5G (with auto-fallback to 4G) M2M
SIM/eSIM from two different mobile service providers. These SIM/eSIM
will be utilized to implement link aggregation, combining the bandwidth
from both SIMs/eSIMs to increase throughput. This aggregation method
merges the bandwidth of the two physical 5G M2M SIMs/eSIM with auto-
fallback to 4G, treating them as one for enhanced bandwidth throughputs.
Furthermore, the CVMS solution stack hosted on the public cloud should
offer a similar option to unbundle the link-aggregated traffic received from
the M-NVR/NVR/VRU. The MSI will ensure that such functionality is
available, ensuring that the link-aggregated traffic can be properly
managed and processed at the CVMS stack.

lix. MSI and its respective OEM must implement all the use cases mentioned
in Annexure-4-Integration of the Applications of CRIS through
seamless integration between M-NVR/NVR/VRU and VMS, SDK is to be
shared with the CRIS for integration purposes.
a. MSI and its respective OEM to fulfil the uses case requirement
mentioned in Annexure-4-Integration of the Applications of CRIS
with the help of ONVIF protocol.
b. In case some of the use cases are not achievable through ONVIF, MSI
and its respective OEM to share the SDK/API with M-NVR/NVR/VRU
OEM/Bidder and integrate M-NVR/NVR/VRU with VMS
c. If the MSI and its respective OEM are not able to achieve all the use
cases mentioned in Annexure-4-Integration of the Applications of
CRIS through the above two integration approaches, in that case, the
MSI has to coordinate with the OEM of M-NVR/NVR/VRU and
consume the SDK/API shared by M-NVR/NVR/VRU
lx. MSI to submit the compliance and specify the type of integration & mode
of integration as mentioned in Annexure-4-Integration of the
Applications of CRIS. The overall responsibility to integrate the system
seamlessly lies with MSI & its respective OEM.
lxi. Security Verification Certification: The Video Recording Software shall
have security features which can be deployed meeting the security
assurance requirements as per the applicable RDSO guidelines
mentioned for the applications.
lxii. VMS shall be able to integrate with other third-party edge devices and
applications as follows:
a. The VMS application must seamlessly Integrate with the ICCC platform
including the sub-modules like Incident management and tools for
handling Big Data.
b. GIS

Page 66 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. GPS (IRNSS/NAVIC) (from third-party multiple OEMs)

d. SMS Gateway & Email Gateway
e. Field edge devices such as IP CCTV cameras (from third-party multiple
OEMs)
f. M-NVR, NVR, VRU, Panic Buttons, etc. (from third-party multiple
OEMs)
g. Microphone (from third-party multiple OEMs)
h. Facial Recognition Solution
i. Edge Analytics (from third-party multiple OEMs)
j. Video Analytics (from third-party multiple OEMs)
k. Post-analysis video analytics to be performed on recorded video as
defined in the Section Video Summarization.
l. RDAS
m. Enterprise Management System
n. Other third-party databases
o. LDAP/ Active Directory
p. NTP and Time synchronization from IRNSS/NAVIC
q. VMS shall be able to integrate with other video management platforms.
r. Any other systems and applications required for successful
implementation of the CVMS solution.
lxiii. The VMS shall feature an interface that allows for configuring the interval
of the Facial Recognition System (FRS) on the edge devices in the field,
specifically in the Coaches, Locomotives, EMUs, and MEMUs, to resend
the image of the already detected face to the FRS central server in the
CVMS servers. This user-configurable interval shall range from 3 to 30
minutes. This interface may be either provisioned in the VMS system or in
the FRS.

8.1.2. VMS KPI / Performance requirements

i. Video Retrieval Time: Time taken by VMS to retrieve specific videos and
audio file from the system. This KPI is crucial for assessing the efficiency
of the system in providing quick access to critical information.
ii. Video Quality and Resolution: Track the quality and resolution of video
footage stored in the system. Ensure that the VMS maintains high-quality
video and monitor for any degradation over time.
iii. User Authentication and Access Control: Monitor the effectiveness of
user authentication and access control features within the VMS. Ensure
that only authorized personnel can access specific video feeds and
functionalities.
iv. Alert and Notification Response Time: Measure the time taken by VMS
to generate and deliver alerts. This KPI is crucial for real-time incident
management.

Page 67 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

v. Compliance with Regulations: Ensure that the VMS complies with

relevant data protection and privacy regulations, as it involves handling
sensitive information or video footage in public spaces.
vi. System Reliability: Track the overall reliability of the VMS, including the
frequency of the system crashes or errors. A reliable system is essential
for continuous surveillance and security operations.
vii. Mobile Accessibility: Assess the accessibility of the VMS through mobile
devices. This KPI is important for users who need to monitor video feeds
remotely.
viii. Scalability: Evaluate the scalability of the VMS to accommodate growing
cameras, video storage and processing requirements. Measure scalability
metrics such as system performance under load, capacity expansion
capabilities, and resource scalability.
ix. Integration with Other Systems: VMS's ability to integrate with other
security systems or other Government applications. This KPI ensures
interoperability with other tools and technologies in the security
ecosystem.

8.2. Integrated Command & Control Center application

8.2.1. ICCC Specifications
ICCC shall comply with the RDSO specification RDSO/SPN/TC/65/2021 Version
6.0 or the latest amendment. In addition to the above specifications below are the
functional requirements of ICCC platform.

i. ICCC shall have the capability to manage more than 7 lakhs+

cameras/Sensors providing unified experience for field devices, improving
the efficiency of the control room operation, and allowing for informed
decision-making.
ii. ICCC application shall be open architecture based, highly scalable and
able to integrate multiple systems seamlessly on a common platform.
iii. ICCC application shall have the playback functionality to give the user
concurrent playback of multiple recorded videos with date, alert sequence
or time searching.
iv. ICCC shall allow the user the following functionalities through the
application UI:
a. View live video from cameras.
b. Browsing recordings of respective cameras
c. Start and stop recording.
d. Set frame rate.
e. Set non-default recording rate.
f. Send notifications via email.
g. Switching between multiple of views.

Page 68 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

h. Viewing video from selected cameras.

v. The ICCC platform shall provide a dashboard functionality to manage
workflows by integrating information from different agencies and systems
to facilitate responsive decision-making.
vi. ICCC shall allow the user to extract different types of logs related to the
CVMS.
a. The System Log
b. The Audit Log
c. The Alert Log
d. The Event Logs
vii. ICCC platform shall provide a user management interface to external
parties for monitoring & maintenance of the field devices.
viii. The ICCC shall have an inbuilt automatic logging out of users after a
period of inactivity. The time for Auto log out shall be user-configurable to
prevent unauthorized access to the system.
ix. The ICCC platform shall support a limitless number of logs and historical
transactions (events and alarms).
x. ICCC shall also be capable of integrating, connecting and corelate
information from various sensors providing rule-based information drawn
from various sensors for KPIs and alerts. ICCC shall have the ability to
add/remove sensors including new OEMs as per future business
requirements.
xi. The ICCC shall aggregate various data feeds from respective sensors &
systems and further process information out of these data feeds to provide
interface/dashboards for generating alerts and notifications in real-time.
xii. ICCC shall have capability for data transformation of the integrated data
which shall be utilized for data normalization, data anomaly verification,
data format change and data filtering.
xiii. ICCC shall be able to integrate with sensors, complex event processing,
ESB, Big Data, BI system, GIS and other third-party Video Management
System (other than CVMS’s VMS) and adhere to the industry standards
for interoperability, data representation & exchange, aggregation,
processing and storage management.
xiv. The user shall have a Help Tab to provide a quick search for topics related
to ICCC application.

xv. User Management

The CVMS users are geographically distributed, and respective users shall be able
to access the ICCC application based on the level of data access provide to
respective users.

ICCC application shall ensure continuous maintaining of user access management

rights. Managing of the user access / role management shall be done by the

Page 69 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

administrators through a user-friendly interface based on the defined SOPs

(prepared by MSI and approved by CRIS during the design phase).

The level of access provided to the users (i.e., view incidents, create incident,
access to live view, recording of respective cameras etc.) shall be set based on
either request basis or rule based through multi-level hierarchical process to ensure
thorough scrutiny, transparency, and alignment with organizational policies.

ICCC shall have the below mentioned interface/fields to allow users (administrator,
operator & supervisor) to manage their respective accounts. The below mentioned
activities are indicative and administrator shall have authority to assign any user with
any privilege /permission.

i. Administrator
a. New User Registration: Interface to create new users and collect
information such as e-mail, mobile number, and department.
b. Role Management: Define roles such as administrator, operator,
supervisor, normal and power users to each user based on
requirement.
c. Data Access Permissions: Each role with specific permissions and
access levels.
d. User Suspension and Deactivation: Interface to suspend or deactivate
user accounts.
e. Manage Accounts: Manage and update user profiles.
f. Implement strict controls and logging for emergency access.
g. Audit Trails: Log information with timestamps for security and
accountability.
h. Time Limits for respective requests: Allow administrator to set time
limits for live camera views, access to respective camera recordings to
ensure that resources are not tied up unnecessarily.
i. Bulk User Operations: Support bulk actions for common tasks, such as
updating roles, and activating, or deactivating multiple users
simultaneously.
j. User Overview: Display a summary of the total number of registered
users, with a breakdown of users based on roles and status (active,
inactive, pending approval).
k. Request Approval Workflow: workflow for requesting live camera
views, retrieval of the recorded videos, request to record specific
cameras etc.

ii. Power user

a. Dashboard Request: User customizable dashboards/reports to view
the real time information of the system.

Page 70 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

b. Video Request: Allow to request access based on the user

requirement:

• To view camera feed,

• Download specific video feed for analysis.
• Record camera feed.

iii. Supervisor
a. Audit Trails: Log & data access information for all the subordinates.
b. Access Approval: Interface to approve live camera view requests (per
the user requirement) as requested by specific operator under the
respective supervisor.

iv. Operator
a. Updating Profiles: Users to update their profiles, including contact
information and password changes.
b. Emergency Access: Provide a mechanism for authorized users to
request immediate access to live camera views in emergencies.
c. Video Request: Allow operator to request access based on the on-filed
requirement:

• To view camera feed,

• Download specific video feed for analysis/investigation.
• Record camera feed.

v. Field User
a. Alarm/Alerts Report: Alarm reports to view the about triggered alarms
or alerts raised based on Severity Levels.

Further, ICCC shall have the following features to allow users to use the application
efficiently.

i. User Authentication & Password Policies: ICCC shall ensure

authentication mechanisms (e.g., username/password, multi-factor
authentication - OTP) to ensure user identity verification and force
password policies (such as complexity, and expiration) to enhance
security.
ii. Password Recovery: Implement a secure password recovery mechanism
for users who forget their passwords.
iii. Alarm / Notifications: Notification system to alert users about role changes,
system updates, or important information delivered through email, or in-
app messages.

Page 71 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

iv. Reporting: Provide reporting capabilities for administrators to review user

activities and access patterns.
v. Dashboards: Real-time dashboard displaying information regarding
concurrent, active users with varied access levels, users engaged in
accessing live feeds, and the data downloaded by individual users.
vi. Integration with ICCC Application: Seamless integration with the main
ICCC application to ensure that role-based access controls apply to all
relevant modules and features.

8.2.2. ICCC Modules

8.2.2.1. Geospatial Information System (GIS)
The ICCC platform shall be integrated with GIS as part of the overall
solution to meet the below mentioned functional requirements:

i. The key components of the proposed GIS solution shall consist of

GIS map, GIS Server, Geo fencing tools etc.
ii. GIS Map shall be developed or procured and integrated by the MSI
at minimum 10 mtr. resolution at 1:1000 scale or better.
iii. GIS Engine shall be able to fetch GIS data based on latitude and –
longitude received and renders on base map for viewing.
iv. The proposed GIS solution should support, host and deliver
information on the service-oriented architecture, and should allow
interoperability such that different client systems can request data in
native application without the need to change the data format, its
location and/or its transmission protocol.
v. All the edge devices shall be integrated with GIS, so that physical
location of the coaches, locos and EMUs/MEMUs including the
CCTVSS & CVVRS equipment’s are brought out on the GIS map.
Such equipment’s shall include:
a. IP cameras
b. NVR, m-NVR, VRUs & interconnected / managed I/O devices
c. Wi-Fi/Network Access Points
d. SIM/Mobile connectivity Module
e. Any other sensor or system interconnected with NVR/m-
NVR/VRU
vi. The GIS must support displaying near real-time user defined
attributes information’s such as device name, device ID,
Coach/Locomotive/EMU/MEMU ID, health status, heading/speed,
positional data (lat/long.), etc.
vii. GPS integration with GIS is required to locate and track all Coaches,
Locos and EMUs/MEMUs (on which GPS units or NVR with inbuilt
GPS are fitted) on GIS Map.

Page 72 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

viii. CCTV Cameras should be accessible through the GIS map and user
shall be able to select any camera and play live and recorded feed of
the cameras on demand.
ix. The system should be able to read popular raster formats like IMG,
GeoTIFF. Vector stored as SHP, GML, KML, DGN, DWG should be
supported along with those stored in database. The GIS map shall
support the industry leading standard file formats such as PDF, JPG,
PNG, etc.
x. The system should be able to access, publish, and consume the
raster datasets, vector datasets, point-cloud data, and non-spatial
data like videos, documents, pictures, and any electronic content.
xi. The proposed GIS Server/solution must support and be compliant to
the Open Geospatial Consortium (OGC) defined Web Services like
WMS, WFS, WCS, WFS-T and WMTS.
xii. The system should be able to consume real-time enterprise
published spatial data. It should be able to consume the third-party
published OGC web-services.
xiii. The system should be able to catalogue the data directly and should
publish the data in open standards (as OGC web services), so that
the clients can request for same via such open interfaces and open
protocols.
xiv. Support for Coordinate Transformation and user definable datum. An
administrator should be able to create and add custom coordinate
system, and should support all EPSG codes, also the proposed
solution should support coordinate transformation on the fly via OGC
Coordinate transformation CT 1.0.
xv. The proposed GIS Server/solution shall provide the ability to display
layer of information in Keyhole Mark-up Language (KML) format.
xvi. The Web client must be able to interactively add following data
services on the fly on the client side by defining and maintaining data
sources:
a. Base map coming from multiple sources which are openly
available
b. Support 3D Data Sources as per industry specific standards
c. GeoRSS
d. Open Geospatial Consortium (OGC) and services including
WMS, WFS etc.
xvii. The software should support all industry specific data format for
vector and raster datasets.
xviii. The proposed solution should have the capability to consume and
serve data directly from supported RDBMS without any bridge or
middleware directly from native tables.

Page 73 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xix. It shall be possible to configure a mixed set of GIS maps consisting

of online (dynamic), offline (static) maps, satellite imagery,
CAD/engineering drawings, private imported files, other map layers
and link them together.
xx. The ICCC platform shall provide a map centric interface with the
system capabilities to display full screen, floating window and dock
able map interface.
xxi. The software should support feature data (Point, line, polygon) as
input data type and tabular data.
xxii. The GIS maps will have the following essential map features:
a. Drag and Pan
b. Zoom
c. Find and zoom to position
d. Search a specific vehicle on the map
e. Dynamically Turn on or Off Customer Specific Map layers
xxiii. It shall be possible to span the map over multi-screens of the ICCC
client. In the scenario where the map is spanned over multi-screens,
it shall be possible to navigate the map including pan and zoom, and
such map movements shall be synchronized between all screens.
Spanning the map over multiple screens must provide the same
Command & Control capabilities than in a single screen display.
xxiv. The GIS map shall offer a smart selection tool and information
display to access the edge devices in the field along with its live &
recorded video feed playback (on demand).
xxv. It shall be possible to customize the icons of any entities represented
on the map. Icons shall have capability to showcase visual
differentiation in between the various health, performance states of
the concerned equipment or system.
xxvi. It shall be possible to select a location by drawing a zone of interest
on the GIS map, and to display all the entities that are part of that
zone of interest at once.
xxvii. GIS window in the ICCC application shall provide Alarm
management capabilities from maps and ease of operator
navigation.
xxviii. The user shall be able to select and display the content of respective
zone on the map in a user-friendly manner.
xxix. It shall support capability of search within the map by Coaches,
Loco, EMUs & MEMUs name or point of interest.
xxx. It shall support event-bases response actions for decision making in
case of any emergency / critical situation.
xxxi. Camera video and audio feeds along with other relevant data as
received from field systems to be viewed on the Map in case of any
event triggers.

Page 74 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xxxii. The proposed GIS solution shall be able to export (in industry
leading open/standard file formats) the map along with the
meta/attribute data being displayed on the screen to share with other
users.
xxxiii. The proposed GIS solution shall support interactive dashboards
having ability to show thematic maps, event clusters, the incidents
over given time-period and provide means to dynamically geo-
visualize time-slicing.
xxxiv. It shall support device & incident clustering wherein the number of
devices and incidents shall be clustered together to reduce the
clutter. The label upon clicking on the cluster should drill down the
cluster to smaller clusters till the individual incidents or the devices
are visible.
xxxv. MSI shall carry out seamless integration to ensure ease of use of
GIS in the CVMS Applications/Dashboards in Integrated Command
Control Center, Viewing Center, Depot and by other authorized
users and respective locations.
xxxvi. Different layers which are proposed to be covered under GIS are as
follows:
a. CCTV Camera
b. NVR, m-NVR, EMUS & MEMUs
c. Locomotives
d. Coaches
e. EMUs/MEMUs
f. Railway Police posts/Thana/Stations
g. Railway Stations & Platforms
h. Bridges, Flyovers
i. Sheds & Yards
j. All the layers which will be integrated with map shall be
decided by CRIS during the requirement and design phase.

xxxvii. The web Client shall have a scale bands configuration on the client
side, wherein a client should be able to define different scales and
define what all layers must be visible on what scale configurations.
xxxviii. The GIS map shall define the boundaries of the jurisdiction limits of
respective railway police stations and zones.
xxxix. GIS system shall be capable to manage base maps, street maps,
satellite images, GIS data of various point of interest information,
infrastructure, and assets etc.
xl. The system should be scalable on IT standards. It should allow and
support the extension of functionalities and capabilities through
hardware or software-based clustering. This is to allow and support
the highest up-time and availability with stability.

Page 75 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xli. The system should support hosting the application over secured
channel like SSL.
xlii. The system should support integration of existing user management
and authentication mechanism like Active Directory, LDAP, JAAS,
etc.
xliii. For better performance and efficient map display, the system should
have to facility to enable caching of data on client-side as well as on
server-side for features which are not frequently updated.
xliv. The system should be scalable any increase in processing should
not have any additional cost on the GIS Server Software and
existing GIS server licenses should cater to the upgraded hardware.
xlv. The system should support interoperability wherein the same data
can be accessed by different systems through OGC web-services.
The client application should be able to consume these web-services
for their application needs on any system; be it web browsers,
desktop systems or mobile devices.
xlvi. The system shall be able to log events of interest such as who is
publishing services for the Logging and Auditing purposes.
xlvii. Administration: The GIS solution administrator should be able to
monitor the performance and quality of the application. The system
should allow administrators to manage the published web-services
so that they can apply necessary security, restrictions and expose
the relevant interfaces. The administrator should be able to manage
the application from a single location wherein the administrator can
configure:
a. Web-services
b. Server parameters
c. Logging configuration
d. Cache configuration
e. Visual folder configuration
xlviii. Report Generation: The proposed GIS solution shall support Spatial
Query Builder as required for Project which can generate spatial
based reports as per the user query (Spatial and Nonspatial).
8.2.2.2. Alarm Management
i. ICCC shall have the ability to manage & integrate alerts from multiple
applications such as Video Management System, Enterprise Management
System, Facial Recognition, Video Summarization & Forensic Application.
ii. ICCC shall have Automatic and Manual incident triggers using both MAP
and Non- Map interface.
iii. The ICCC application shall allow ICCC users to create a customizable
dropdown list of events/incidents, enabling them to provide input and
resolve/close the raised alarms.

Page 76 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

iv. The ICCC application shall have a feature that automatically notifies users
who have bookmarked/flagged a video for further investigation before the
default storage period has elapsed.
v. Create and modify user-defined alarms. An unrestricted number of user-
defined alarms shall be supported.
vi. User configurable priority levels for alarms and its reactivation threshold.
vii. Define whether to display live or recorded video, still frames or a mix once
the alarm is triggered.
viii. Provide the ability to group alarms by source and by type.
ix. Define the recipients of an alarm. Alarm notifications shall be routed to one
or more recipients. Recipients shall be assigned a priority level that
prioritizes the order of reception of an alarm.
x. The workflows to create, modify, add instructions and procedures, and
acknowledge an alarm shall be consistent for various systems.
xi. The ICCC shall also support alarm notification to an email address or any
device using the SMTP protocol.
xii. The user shall acknowledge alarms, create an incident upon alarm
acknowledgement, and put an alarm to snooze.
xiii. The alarm management module shall not create more than alarm for same
recurring event to avoid flooding of system.
xiv. The user shall be able to spontaneously trigger alarms based on
something he or she sees in the ICCC system Dashboard.
xv. ICCC platform shall generate Notification, Alert and Alarm messages as
per the incidences / events that are received, that should be visible within
the Dashboard and the Mobile application (iOS & Android) and web
interface.
xvi. All system messages (notifications, alerts and alarms) shall always be
available from the Notifications View, which provides controls that operator
can use to sort and filter the messages that it displays.
xvii. ICCC shall have the capability to provide Incidence Bookmarking for
further investigations.
xviii. ICCC platform shall notify the respective users through SMS, Email and
through mobile & web interface.

8.2.2.3. Escalation Management

i. ICCC shall provide a notification and escalation module to support Incident
Hierarchic Escalation.
ii. Escalation rules shall support based on Severity or Priority. Based on
Incident Priority the Auto Escalation time to Higher Level should be
different.

Page 77 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

8.2.2.4. Alarm / Event Correlation

i. ICCC shall support capability to configure alarm correlation with multiple
events can be combined for better efficacy.
ii. ICCC shall be able to correlate two or more events coming from different
sensors based on time, place, customizable attributes and provide
correlation notifications to the operators based on predefined business and
operational rules in the configurable and customizable rule engine.

8.2.2.5. Rule Engine

The ICCC rule engine modules shall provide the following functionalities.
i. The system should be able to generate automatic alarms to alert the
control room personnel for further action.
ii. Rule Engine Module shall provide notifications to multiple agencies and
departments based on the alarm type.

8.2.2.6. Exception management

The ICCC shall provide user configurable exception management module.
Exception management shall have the following:
i. Facility to raise triggers based on exceptions.
ii. Facility to raise automatic exceptions based on pre-defined.

8.2.2.7. Incident Management Module

i. The incident management module shall provide situational intelligence to
the operator & respective user with a map-centric approach and detailed
overview of incident data, combining incident history, operator comments,
workflow and operator action logs, standard operating procedures,
relevant live and playback video, and an aggregated events sequence of
the incident.
ii. The incident management module shall log all configuration changes in an
audit trail with before and after configurations including all user activities.
iii. The Incident management module shall provide the ability to trigger
incidents manually or automatically, based on a correlation of events.
iv. Incident management module shall allow to filter incidents based on below
parameters.
a. Incident type
b. Incident state
c. Location / Geo Location / Proximity to Location
d. Priority
e. Trigger time range

Page 78 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

f. Description
g. Attachments
v. ICCC shall have guidance module for operators in the form of a standard
operating procedure (SOP) for the response to an incident type.
vi. Incidents shall be categorized and prioritized. While prioritizing incidents
the impact and urgency of the incident shall be taken into consideration.
vii. The Incident management shall provide management of incident
ownership. It shall be possible to explicitly request or release the
ownership of an incident. Ownership of an incident shall be provided
immediately to an operator and respective users who starts working on an
incident.
viii. A respective zone & area supervisor shall be able to view all incidents that
are under user supervision and see the ownership of each incident. In the
same view, the supervisor shall also be provided with real-time information
about who is currently monitoring an incident.
ix. The incident management module shall notify the supervisor when a
respective zone & area operator skips a step in the standard operating
procedure (SOP).
x. Incident management module shall provide unresolved incidents (known
errors and workarounds) to be recorded and reported to provide
information for effective problem management.
xi. Respective zone and area operators shall be able to perform the following
actions:
a. Change the incident state.
b. Forward and transfer the incident.
c. Edit the incident:
d. Change the description and priority level.
e. Release the ownership.
f. Attach additional entities to the incident.
g. Link related incidents and attach a document to the incident report.
h. Link the flagged incident data.
xii. The incident module shall provide the ability to assign an incident to a user
or group of users. Dispatching an incident to a restricted number of users
will secure the access to information.
xiii. The incident management module shall offer the ability to automatically
link a document to a step in a standard operating procedure.
xiv. The module shall have rule engines and that shall be graphical without
need for a script.
xv. The module shall have a workflow engine to automate the response to an
incident type.
xvi. It shall be possible to define a workflow for each incident type. The
workflow shall be a series of activities that are sequentially executed.

Page 79 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xvii. The incident management module shall provide guidance for operators in
the form of a standard operating procedure (SOP) for the response to an
incident type.
xviii. The SOP shall be dynamic and provide the ability to adapt the next steps
in a procedure based on the responses to previous steps in the procedure.
xix. The module shall track time of respective steps of the SOPs and as well
as the total elapsed time from the initial response to resolution.
xx. A maximum delay shall be allowed for a user to initiate the procedure.
Automated actions associated with this time to response threshold shall be
configurable.
xxi. A minimum time shall be allocated for a user to complete the procedure.
Closing the incident before passing this time to resolution threshold shall
trigger automated actions.

8.2.2.8. Reporting
i. System should have ability to generate reports and have provision to add
reports in favourites list.
ii. Detailed incident reports shall include an incident summary, all the tasks
associated with the incident, sensor related activities, relevant snapshots,
and maps.
a. Periodic Reports
b. Maintenance Reports
c. Statistical Reports
iii. Ability to display report on monitor and print report.
iv. Ability to capture Operators response in Text.
v. Ability to select information to be included in report at time of report
generation.
vi. Details of alarm including severity, time / date, description, and location.
vii. Capture the operator response by text.
viii. The incident reports shall be accessible to any operator and mobile
application user as per the defined role.
ix. The ICCC shall support comprehensive data filtering for most reports
based on entity type, event type, event timestamp, custom fields, and
more as per the user requirement.
x. ICCC shall provide checkbox UI to create user defined reports based on
the on-the-fly requirements.
a. Device ID (Camera / Panic Button / RDAS / Microphone / NVR etc.)
and other device attributes.
b. Train No
c. Coach/Loco/EMU/MEMU Number
d. Location (Zone/Division/Section/Station etc.)
e. Time
f. Type of Incident (not limited to)

Page 80 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

• Child Abuse
• Women Harassment
• Service Request
• Passengers Fights
g. Month
h. Day
i. Year
xi. The ICCC shall support the report export in PDF, Excel, CSV file and
automatically email a report as per user defined parameters to one or
more recipients.
xii. The user shall be able to customize the predefined reports and save them
as new report templates. There shall be no need for an external reporting
tool to create custom reports and report templates.
xiii. Customization options shall include setting filters, report lengths, and
timeout period. The user shall also be able to set which columns shall be
visible in a report. The sorting of reported data shall be available by
clicking on the appropriate column and selecting a sort order.
xiv. ICCC shall support following reports but not limited to:
j. Alarm Reports
k. Logs Reports
l. Configurations Reports
m. Video Specific Reports (archive, bookmark, motion, and more).
n. Respective user specific reports as per the user requirement

8.2.2.9. Standard Operating Procedures (SOPs)

i. The ICCC shall be equipped to respond quickly and effectively to
emergency or disaster situations through Standard Operating Procedures
(SOPs) and step-by-step instructions to support and strengthen
coordination in response to incidents/emergencies/crises.
ii. ICCC should provide for authoring and invoking un-limited number of
configurable and customizable standard operating procedures through
graphical, easy to use tooling interface.
iii. Standard Operating Procedures should be established, approved sets of
actions considered to be the best practices for responding to a situation or
carrying out an operation.
iv. The users should be able to edit the SOP, including adding, editing, or
deleting the activities.
v. The users should be able to also add comments to or stop the SOP (prior
to completion).
vi. There should be provision for automatically logging the actions, changes,
and commentary for the SOP and its activities, so that an electronic record
is available for after-action review.

Page 81 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

vii. The ICCC platform should have capability to define the following activity
types:
a. Manual Activity - An activity that is done manually by the owner and
provide details in the description field.
b. Automation Activity - An activity that initiates and tracks a workflow and
select a predefined flow order from the list.
c. If-Then-Else Activity - A conditional activity that allows branching based
on specific criteria. Either enter or select values for Then and Else
d. Notification Activity - An activity that displays a notification window that
contains an email template for the activity owner to complete, and then
sends an email notification.
e. SOP Activity - An activity that launches another standard operating
procedure.

8.2.2.10. Administration Module

i. Administrator module of the ICCC shall be able to limit what users and
operators can modify them through privileges.
ii. ICCC shall provide comprehensive policy-based administration based on
user's responsibilities.
iii. ICCC shall enable assignment of permissions to groups, and
administration of access control across multiple applications and
resources.
iv. The Administrative module shall be capable of providing Rights to different
modules / sub-modules / functionalities of the mobile application.
v. The ICCC platform shall have asset management functionality to manage
the edge devices. It shall also provide a user-friendly GUI to define and
manage API based integration of the various components.

8.2.2.11. Role Based Access Control (RBAC)

i. Various users should access the system using single sign-on and should
be role based. Different roles which could be defined (to be finalized at the
stage of SRS) could be Administrator, Supervisor, Officer, Operator, etc.
ii. The users accessing the CVMS solution shall be managed from the GUI
interface of the systems from which the RBAC functionality is being
managed and the administrators of the CVMS solution should be easily
able to configure, add, remove and manage the users
privileges/permissions.
iii. ICCC shall have the capability to assign access based on the roles defined
for the mobile application.
iv. The system should also be able to define access based on location. Other
minimum features required in the Role Based authentication Systems are
as follows:

Page 82 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

a. The Management Module should be able to capture basic details

(including mobile number & email id) users requiring Viewing /
Administration rights to the system. There should be interfaced to
change these details, after proper authentication.
b. Rights to different modules / Sub-Modules / Functionalities should be
role based and proper log report should be maintained by the system
for such access.
c. There should be provision to specify hierarchy of operators / officers for
control of the cameras from various locations.

8.2.2.12. Dashboard
i. Dashboard shall provide tools to assemble personalized views of
information pertinent to incidents, emergencies & operations of the
command center.
ii. Dashboards shall provide filtering capabilities that enable end-users to
dynamically filter the data on criteria, such as region, dates, incident type
etc. and the capability to drill down to the details.
iii. The ICCC shall have business intelligence system to support BI analytics,
to build Realtime, map based BI dashboards.
iv. There shall be dynamic dashboarding capability with widget based
dashboarding. There shall be unlimited numbers of dashboards created in
a self-service mechanism by respective user.
v. The dashboard shall provide simultaneous visibility into the edge
equipment installed in Coaches, Locomotives, EMUs, MEMUs and other
field locations as well as public cloud environments, allowing
administrators to seamlessly navigate and monitor the complete CVVRS
and CCTVSS infrastructure.
vi. The user interface shall have an analytics dashboard listing all the patterns
of events from different cameras and analytics with a heatmap of several
events on an hourly basis.
vii. Role Based Dashboards
a. The MSIs shall provide dashboards for different role users such as
Management, admin, and report users as per the user requirements.
b. The Role based Dashboards (summarized view) with queue
management of all the requests made through the system, including
provision to define priority Queues.
c. Role based Dashboards shall provide real-time status when actions,
incidents and resources have been assigned, pending, acknowledged,
dispatched, implemented, and completed.
d. The Dashboard content and layout shall be configurable, and
information displayed on these dashboards shall be filtered by the role
of the person viewing dashboard.

Page 83 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

viii. The user shall be able to configure the same attribute of the dashboard
with respect to country level, zone level, division level, area level and
station level.
ix. The dashboards shall have drill-down capabilities ensuring visibility for
only relevant personnel & data and widgets reloading based in the
selected area.
x. All the dashboards in the system shall be available on the mobile app (iOS
& Android), web basis the access provided by the system.
xi. The ICCC shall integrate with GIS engine (refer Section Geospatial
Information System) Geospatial Information Systemincident dashboards
should also provide heat maps and provision for specifying radius for
generating heat maps.
xii. The incident dashboards should have the ability to show the incidents over
a given time and provide means to dynamically geo-visualize.

8.2.2.13. Trend Analysis

i. Quickly organize large amounts of data to visually identify non-obvious
associations, find patterns, and identify trends in data, yielding
investigative insights that would be impossible to see otherwise.
ii. The module shall include trend analysis reports.
iii. The term "trend analysis reports" refers to the concept of statistical
analysis by collecting information and attempting to spot a pattern for
incident vs time. The proposed customized application will have the
functionality to draw trend reports and show it in an executive dashboard
for easy decision making and to summarizing the crime pattern in selected
locality.

8.2.3. ICCC Integrations

i. Video Management System (including VMS hosted on proposed CVMS
solution on Public Cloud & CRIS provided VMS solutions hosted on any
other Data Center)
ii. GIS Module
iii. GPS Module (IRNSS/NAVIC)
iv. M-NVR/NVR/VRU (from third-party multiple OEMs) connected through
SIM/eSIM.
v. Panic Buttons, etc. (from third-party multiple OEMs)
vi. Microphone (from third-party multiple OEMs)
vii. Facial Recognition Solution
viii. Edge Analytics (from third-party multiple OEMs)
ix. Post-analysis video analytics to be performed on recorded video as
defined in the Section Video Summarization
x. Enterprise Management System
xi. LDAP/ Active Directory

Page 84 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xii. NTP
xiii. Email and SMS Gateway
xiv. Time synchronization from IRNSS/NAVIC
xv. Any other systems and applications required for successful
implementation of the CVMS solution.

8.2.4. Information to be managed at the ICCC & Viewing Centers

The proposed CVMS solution should provide a complete end-to-end
solution for security surveillance solution. The control center shall allow an
operator to view live / recorded video from any camera on the IP Network.
The combination of control center and the IP Network would create a
virtual matrix, shall be simultaneously viewed at Integrated Command
Control Center and at respective Viewing Centers. User shall have access
to the video feeds of the cameras of their jurisdiction as follows:
i. Viewing rights to all the live Camera Feeds
ii. Viewing rights to the stored feeds
iii. Viewing of cameras directly by clicking on GIS map (On clicking of camera
icon on GIS map, the live video feed from camera should open. Also, on
GIS map along with camera icon direction of camera should also be
visible.)
iv. Access to view Alerts / Exceptions / Triggers raised.
v. Trail Report is expected to have geolocations, direction of camera and
tracking route of specific person / object / vehicle for a specific period /
location.
vi. Personalized Dashboard (depending upon grade of respective officer)
vii. Accessibility to advanced analytics on live & recorded footages
viii. Provide search of recorded video. Advanced search should be possible
based on various filters like alarm / event, area, camera, etc.

8.3. Mobile application

The MSI shall provide a mobile application to allow field staff, executives, power
users etc. to access the edge devices and alarms raised. To ensure the latest
features, the MSI shall continuously innovate and upgrade.
i. The Mobile application should be available for both Android and iOS
mobile/tablet devices and shall provide secured access through a multi-
factor authentication (OTP) over the internet.
ii. The Mobile app shall be used to access the CVMS solution and all traffic
from the mobile app to the CVMS solution stack should be encrypted
through a VPN tunnelling application to ensure security and privacy.

Page 85 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

iii. Mobile application shall provide a role-based security model to allow only
authorized users to access and administer the alert and notification
system.
a. Role-based access for mobile users shall be controlled through the
ICCC application.
b. Mobile application shall have the provision of user configurable auto
log off. This shall help in preventing unauthorized access.
c. The app should enforce role-based access control to ensure that users
only have access to video content and features relevant to their
permissions.
iv. Mobile application shall allow for Grouping, aggregating, sorting, filtering,
and merging of alerts based on
a. Types of incidents
b. Event priority, event start time, end time
c. Sorting of incidents based on latest /oldest incidents.
d. Location
v. The mobile application shall enable users to view live video feeds from
cameras, as well as access recorded video footage. It should support
smooth streaming and playback of video content over both Wi-Fi and
cellular networks.
vi. The Mobile Application should provide search capabilities to allow users to
quickly locate and retrieve specific video recordings based on criteria such
as date, time, camera location, and incident events.
vii. The Mobile Application users shall be able to acknowledge the incident
and provide real-time updates from the incident site as per the defined
SOPs by CRIS/Indian Railways.
viii. The Mobile Application shall support at least 08 video streams
concurrently on a mobile app GUI.
ix. The Mobile Application allows users to create, view, update, and close
incidents. It should provide features for categorizing incidents, assigning
priorities, and adding relevant details such as location, type, and status.
x. The Mobile Application shall support the creation and sharing of incident
reports, logs, and other documentation. Users should be able to generate
customizable reports, capture multimedia data (such as photos and
videos) and attach relevant files.
xi. Mobile Application shall support offline mode to ensure that users can
continue to access critical features and data even in environments with
limited or no internet connectivity. Offline data synchronization capabilities
should be provided to sync data once connectivity is restored.
xii. The mobile application shall have the capability to display the real-time
location of the Coaches, Locomotives, EMUs & MEMUs on the map.
xiii. Mobile application shall have a robust encryption mechanism to ensure
data privacy and prevention from security threats.

Page 86 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xiv. Mobile application shall provide user-defined dashboards for CRIS /India
Railways Officials such as field staff/responders, Executives, Power users
etc.
xv. The Mobile Application shall be designed with intuitive user interfaces,
easy navigation, and accessibility.
xvi. The Mobile Application shall be designed to handle a large number of
users, incidents, and concurrent activities without compromising
performance or responsiveness.
xvii. The Mobile Application users shall be able to export video clips or
snapshots from the app for evidence-gathering, reporting, or sharing
purposes. The app should support various export formats and methods,
including sharing via email, messaging apps, or cloud storage services.
xviii. The Mobile Application solution shall have the audit log feature to record
the date and time of action, the user who acted along with the description
of the action.
xix. The Mobile application must undergo an annual security audit conducted
by a Government Agency selected from the List of CERT-In empanelled
auditors to ensure compliance with established industry leading
cybersecurity standards and to mitigate potential risks associated with
external threats, vulnerabilities, and data breaches.
xx. ICCC mobile app shall be integrated with VMS and FR Solution

8.4. Enterprise Management System (EMS)

1. Scope of the Enterprise Management System (EMS):
The EMS shall be deployed to monitor and manage the complete CVMS solution
consisting of the following systems and applications: -CVMS hosting
infrastructure on the public cloud.
a. CVMS hosting infrastructure on the public cloud.
b. CVMS and related applications deployed on the public cloud.
c. Network connectivity from the edge devices and CRIS, Indian Railways (IR)
and other Government locations to the CVMS Solution hosted on the Public
Cloud.
d. Edge devices installed at the Locomotives, Coaches, EMUs and MEMUs.
e. Support for a minimum of 300 users to access the EMS system with capability
to monitor and manage the complete CVMS solution stack.

2. Comprehensive Monitoring and Management Solution:

The MSI shall provide a comprehensive monitoring and management solution. This
includes the following:
a. Centralized dashboards and reports for overall health & performance
overview field SI wise reports.
b. Monitoring of key performance parameters

Page 87 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. Tracking of resource utilization

d. Configuration and patch management
e. Asset inventory management
f. Monitoring SLAs field SI wise (and its respective penalties (as applicable)
g. Integration with IT Service Management (ITSM) or ticketing tool

3. End-to-End Monitoring:
The MSI shall ensure that the EMS solution provides end-to-end Performance &
Health monitoring of the entire CVMS solution stack hosted on the public cloud and
monitoring of the integration with edge devices installed in the field (Coaches,
Locomotive, EMU & MEMU). The proposed solution shall facilitate automated
remedial actions based on various triggers like user configured threshold alarms,
notifications & alerts, logs inputs, and specific events, etc. The EMS shall be
implemented on the same Public Cloud infrastructure on which the CVMS solution is
deployed.

4. Asset Monitoring Capability:

The MSI shall ensure that the EMS solution is capable of monitoring all assets which
includes VMs/Containers, software applications within each VMs/Containers,
versions of the software applications, network services, storage, security services,
Network Video Recorders (M-NVR, NVR, VRU), CCTV cameras, and any other
relevant component/asset/device, both virtual and physical.

5. Coverage Throughout Contract Period:

The MSI shall provide the EMS solution for the entire period of the contract as per
the scope elaborated in the Bid Document Part-II for the entire monitoring and
management solution covering all systems, applications, functionalities, etc. as
specified in the Bid Document Part-II with respect to EMS.
.
6. Technical Support
The EMS solution should include technical support for the entire period of the
contract which spans across features like periodic updates, security patches and any
version enhancements.

The below sections define the overview of the EMS solution:

I. Resource Discovery and Configuration Monitoring:

a. The EMS shall be deployed to monitor and manage the complete CVMS
solution consisting of the following systems and applications -
b. The MSI shall ensure that the EMS solution discovers all provisioned
resources, topologies and views their configurations.
c. Notifications should be triggered upon configuration changes, allowing for
analysis and incident response.

Page 88 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

d. Shall support the management of configurations across the complete edge

devices and the Public Cloud infrastructure.
e. Alerts should be provided by the EMS for any unauthorised or any changes
that are being executed or detected for any of the CVMS solution related
infrastructure from the configurations available in the EMS.
f. Shall be able to establish baseline configurations for various CVMS solution
systems and applications and compare current configurations against these
baselines to identify any unauthorized or unexpected changes.
g. Shall maintain version control for configurations, allowing to roll back to
previous configurations in case of issues or discrepancies.

II. Interface to be provided to external users (CVVRS and CCTVSS solution

providers/Vendors):
a. The EMS shall provide highly restricted access for authorized users to an
interface which will enable them to monitor and manage the Patch upgrades
in the IP-enabled edge infrastructure such as Cameras, MNVR, NVR & VRU.
Refer to Section Users of the CVMS and Section Integration with Edge
Devices for more details.
b. The EMS shall provide an interface to monitor the assigned tickets and update
its resolution progress till its closure.
c. The EMS shall also provide a read-only interface to monitor the SLA
performance of the respective Vendor.
d. The EMS should have the provision to allow a minimum of 300 vendors to
access the EMS on a read-only/view-only basis to view the complete
performance status of the Edge devices for which the vendors are responsible
for meeting the Service levels.

III. Performance and Availability Monitoring:

a. Visibility into the performance and availability of the CVMS application and
associated cloud services should be provided.
b. Network connectivity (Mobile SIMs, ILL, P2P, MPLS, VPN links, etc.) from the
edge devices and CRIS, Indian Railways (IR) and other Government locations
to the CVMS Solution hosted on the Public Cloud. should be monitored.
c. Provide insight on performance metrics like bandwidth utilization, data transfer
rates, Latency, Packet loss, and Jitter.
d. The proposed solution should provide the capability to configure different
polling speeds for different systems and applications.
e. The notifications/alerts should be automatically triggered by changes in the
health status as per the defined threshold levels, allowing for proactive
monitoring.
f. Customizable monitoring of specific parameters/attributes of the application,
network, underlying infrastructure, etc., and at different flexible frequencies.

Page 89 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

g. The MSI shall provide real-time monitoring, log maintenance, and automated
backup reports daily for all VMs/Containers/Applications /Storage.
h. Parameters like CPU usage, memory usage, memory leaks or inadequate
memory allocation, disk space usage, reboots, critical services or any other
outages and other performance aspects of the Virtual Servers are to be
monitored.
i. The MSI shall provide application performance monitoring service and should
support applications running on underlying infrastructure as per their proposed
CVMS solution stack.
j. The EMS Solution should be capable of monitoring multiple applications
simultaneously, providing insights into the performance of each application to
identify and detect parameters like network latency and server response times
which are causing application performance issues.
k. The EMS solution should be capable of monitoring the database performance
parameters like database sessions and user activities, diskspace and I/O,
database events, and other availability parameter to identify performance
issues at an early stage.
l. The EMS solution should be compatible and should support for monitoring a
wide range of programming languages, frameworks, databases, and third-
party services commonly used for building applications.
m. The MSI shall make provisions to analyse the amount of data transferred
(uploaded/ downloaded), via Intranet / Internet traffic, for each VMs/
Containers endpoint.
n. The MSI shall perform 24x7 monitoring of all availability parameters of the
network, security, and related services likewise DNS, AD/LDAP, VPN users
(IPsec/SSL connection, NGFW, IPS, DDoS, PIM/PAM, etc.)
o. The MSI shall make provisions for setting alerts based on defined thresholds
and/or business rules. There should be provision to configure different email
addresses (managed by the user management module of EMS) where alerts
can be sent as per CRIS governance requirements.

IV. System-Wide Visibility:

a. Overall system visibility, proactive monitoring of service/resource utilization,
application performance, and operational health of CVMS resources and
field edge devices should be provided.
b. Status of total generated tickets/incidents/alerts and their resolution time.
c. The solution shall be able to discover both IPv4 and IPv6 devices and
devices operating in dual stack.
d. The solution should provide a single dashboard to track the infrastructure
devices of the Public Cloud, the CVMS and the Edge equipment in the field
with a drill-down facility.
e. The solution should support for SNMP traps, and integration with other third-
party alerting platforms.

Page 90 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

f. The NMS tool should discover different types of heterogeneous devices

which are SNMP/ICMP supported devices like Router, Switches, NVRs, IP
Cameras, Servers, etc., and map the connectivity between them with
granular visibility up to individual port levels and should also show live
interface connections between discovered network devices.
g. The solution shall be scalable to accommodate changes in service levels,
increasing workloads, or the addition of new services without compromising
performance.

V. Integrations:

a. The EMS should be capable of integrating with different IP edge devices,

applications and services which in itself are capable of providing status of
its health and performance.
b. Network devices at Project locations
c. I/O devices connected to MNVR/NVR/VRU such as panic button (preferred,
not mandatory)
d. Cloud-hosted CVMS services
e. Cloud Infrastructure health status
f. The Video Management System which is managing the M-NVR/NVR/VRU
g. The ICCC System which is monitoring the events and alerts being received.
h. Any other system which is capable of providing health & performance
parameters related to the CCTVSS, CVVRS & CVMS solution.
i. The system should also be capable of integrating with other API’s or the
API Gateways.
j. Other applications & services as provided by CRIS/IR which enables the
project stakeholders to execute their functions as prescribed in this Bid
Document Part-II.
k. The EMS should also be integrated with the CVMS helpdesk email id, in
order to auto-generate trouble tickets/ service requests.
l. CRIS plans to implement a call center application in the near future. The
EMS shall also require to be integrated to ensure that the service requests
which are being received through the phone calls, should get auto-
generated.

VI. SLA Dashboard and Penalty Calculation:

Health monitoring feed of edge devices from the field should be integrated with the
CVMS centralized monitoring dashboard as per below mentioned Annexures.

1. CVMS: Please refer the Section Service Levels Agreement of Bid Document -
II

Page 91 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

2. CCTVSS: Please refer the Annexure-32-SLA of the Coaches & Annexure-34-

SLA of the EMU/MEMU
3. CVVRS: Please refer the Annexure-33-SLA of Locomotives

The following are some of the functional specifications of the SLA Dashboard and
Penalty Calculations. These shall be calculated separately for each CVVRS and
CCTVSS field SI and CVMS MSI.
a. Customizable SLA dashboard tailored for CRIS.
b. Providing near real-time display of SLA indices for the CVMS solution
including the field edge devices.
c. Configurable web-based graphical user interface (GUI) should be available
that can be extended to different user groups by using RBAC features.
d. The EMS shall provide a Web interface that is configurable to provide view-
only access to select equipment to the users who are responsible for
maintaining the respective Service Level Agreements (SLAs).
e. GUI must be equipped with alerting functionalities. It should be capable of
sending timely alerts to the specified users responsible for maintaining the
SLAs.
f. EMS shall provide a single dashboard which should be flexible and user
configurable to track the SLAs of the CVMS solution stack hosted on the
Public Cloud and the edge devices in the field with a drill-down facility.
g. EMS shall be capable of creating hierarchy-based user defined groups under
which there may be further different types of sub-groups or devices/systems.
This is to enable better navigation through a large list of devices & systems.
h. The solution shall be user configurable and shall also be capable of defining
and customizing SLA metrics based on specific requirements, including
response time, resolution time, and uptime targets.
i. EMS shall completely automate the tracking of SLA performance against
user/predefined metrics, minimizing manual intervention and ensuring
accuracy in measurements and the calculation of penalties.
j. Implement a robust alerting mechanism to notify stakeholders in real time
when SLA thresholds are at risk of being breached, facilitating proactive
intervention.
k. The EMS solution should have the capability to integrate the CVMS with the
Cloud monitoring tool and any other existing or new tools to provide a
common operating picture for users.

VII. Event-Based Alerts:

a. Proactive notifications/alerts for changes to the CVMS applications,

underlying infrastructure, and field devices for events such as but not

Page 92 of 455
 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

limited to RDAS events, panic button activations, and camera tampering

cases.
b. Administrators should have the capability to temporarily silence or snooze
specific alerts for specific time periods to prevent unnecessary notifications
during planned maintenance or acknowledged issues.
c. The event-based alerts shall be user configurable and should be capable of
providing alerts for any type of parameters based on different thresholds
levels.

VIII. Log Monitoring and Correlation:

a. The proposed EMS solution shall be capable of collecting logs from
various IP devices and sources, including virtual servers, applications,
network devices, and security appliances, which are collected centrally
for audit and analysis and shall be able to monitor the real-time
ingestion of logs to provide timely insights into events as they occur.
b. Monitoring and correlation of logs and events generated by the CVMS
solution, underlying infrastructure, and field edge devices to detect
vulnerabilities, threats, and attacks.
c. The EMS system must use advanced root-cause analysis techniques
and policy-based condition correlation technology for comprehensive
analysis of infrastructure faults from the collected logs.
d. The EMS system shall be capable of providing non editable logs of all
actions by the User or the changes to the status of the devices,
system, applications, etc.
e. The EMS shall have the ability to store/ retain both normalized and the
original raw format of the event log for forensic purposes for 6 months
and allow extension of it for a further duration (if needed) by enhancing
the storage resources without any disruption to the ongoing data
collection.

IX. User Management Module & Access Control:

a. Implementation of two-factor user authentication mechanisms and

access controls to ensure authorized personnel access and
configuration of the EMS system.
b. The EMS view for select view only functionalities shall be extended to
different vendors and stakeholders. The EMS solution shall provide
role-based access control to assign permissions to the end users within
CRIS for using the different functions of the EMS.

X. Reports:

Page 93 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

The EMS should be flexible enough and be capable of generating reports based on
the requirements of CRIS:

a. Incidents Report: Details of incidents.

b. Incident Resolution Timelines: Timelines for incident resolution,
c. Performance Report: For all applications and associated VMs/container
and their utilization including compute, memory, storage, database,
network and security services (DNS, Load balancing, firewall
instances) etc.
d. SLA Compliance Reports: Reports on SLA compliance for key
performance indicators defined in the Sections Service Level
Agreement (SLA) – Pre-Phase 1 Go-Live & Service Level
Agreement (SLA) – Post Phase 1 Go-Live of the Bid Document Part
II.
e. Planned Changes Report: List of planned changes, approvals taken,
and implementation done.
f. Security systems and applications Performance Report: Performance
report on security systems and applications.
g. The EMS shall support the storage and analysis of historical monitoring
data, enabling trend analysis, capacity planning, and retrospective
troubleshooting.
h. The EMS shall be capable of completely automating the process of
generation and distribution of all types of reports like availability,
resource utilisation, patch management etc. The EMS should support
for customized and predefined generation of reports.
i. Overview of the connectivity status such as performance, uptime,
network utilisation etc. as defined in the respective SLAs for each
Coach, locomotive, EMU, and MEMU, Network, CVMS and
consolidated view for the project.
j. Shall be able to provide a complete log of preventive / scheduled
maintenance undertaken for different customized periods.

xi. ITSM Help Desk:

The following functionalities will be part of the incident management, problem

management, and technical helpdesk.

a. The MSI shall ensure that the proposed helpdesk system complies with
ITSM and ITIL version 3 or above standards.
b. The MSI shall also provide flexibility in logging incidents via the web
interface.

Page 94 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. The MSI shall ensure that the proposed helpdesk system supports the
incident tracking system that would allow viewing, updating, and
closing of incident tickets.
d. The proposed helpdesk system shall support tracking of SLA (service
level agreements) for service requests within the help desk on various
service types.
e. Workflow for the Incident management process with escalation
mechanism (escalation hierarchy) and approval processes.
f. The ITSM module shall be capable of handling Service Faults, Service
Requests and Suggestions from stakeholders.

• Apply SLA as per the Bid Document Part-II for resolving tickets and support
auto-escalation of the tickets based on priority and SLA defined.
• Support integration with other EMS modules for auto-generation of tickets
and either automated or manual closer of tickets
• Provide role-based access.
• Support integration with e-mail and SMS for sending notifications/alerts.

g. The EMS solution shall provide categorization on the type of incident

being logged and the criticality of the incident via the priority levels,
severity levels, and impact levels.
h. The MSI shall ensure that the EMS solution should be capable of
assigning tickets upon generation to different stakeholders and each of
these stakeholders should be capable of updating the status of the
allocated tickets within the assigned turnaround time.
i. The system should be integrated with SMS and email server to ensure
that email and SMS alerts are sent to stakeholders as and when a
ticket is assigned to them.
j. The helpdesk system should support multi-channel incident reporting,
allowing users to report incidents through various means such as SMS,
email, chat, etc.
k. The ITSM application shall be able to provide the minimum trouble
ticket/request related information while forwarding/pushing the trouble
ticket/request through the channels like SMS, email, chat, etc.v to the
user who is reporting/requesting or to the personnel to whom the
trouble ticket/request is being assigned.
l. The Helpdesk should be able to receive alerts/messages from
respective modules namely VMS, ICCC, VA, FR Solution, Database
monitoring, application performance monitoring, CCTVSS and CVVRS
parameters to generate tickets basis on the categories of the fault
reported by the respective module.

Page 95 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

m. The ITSM dashboard should provide a summary of resolved,

unresolved and escalated issues/complaints to vendors (OEM/3rd
party AMC vendor, if any)

8.5. Invoice Generation Module for the CVMS Solution Stack

1. The MSI shall provide an Invoice Generation Module which shall be responsible
to provide a monthly invoice for the CVMS services provided to CRIS.
2. The necessary details and format for invoice generation shall be advised by
CRIS. The MSI shall ensure that invoice generation process/ protocols are put in
place so as to ensure audit of the invoice generation processes as well as
quantification of the respective billable items and recoveries.
3. Any change in the module as implemented shall require prior approval of CRIS.
Logs of all such changes shall be maintained by the MSI and made available to
CRIS on demand.
4. In the planning and implementation of the process flow of this module, MSI shall
associate with CRIS stakeholders throughout all the stages of development,
ensuring that their inputs and feedback are actively incorporated.
5. The Enterprise Management Solution (EMS) should be tightly integrated with the
Invoice Generation Module ensuring accuracy & integrity of the invoice
generation process.
6. The Invoice Generation Module shall be responsible for generating invoice of the
previous month around 5th of the subsequent month subsequent to calculating
penalties determined by the EMS.
7. Key factors including, such as the format of the invoice, specific days to be
considered for the billing cycle, parameters to be displayed based on the data
provided by the EMS or any other module, line items aligned with the Schedule of
Requirements (SoR), and other relevant details, shall be thoroughly discussed
and finalized collaboratively.
8. Access to a facility/Dashboard to be provided to authorised CRIS representatives
for verifying the genuineness of the reports, bills based on the actual
consumption of all resources of the CVMS solution stack on the public cloud.
9. It is necessary that the billing process is fully automated, ensuring and requiring
minimal manual intervention. The entire process, from penalty calculation to
invoice generation, should be managed by the integrated system.

8.6. Facial Recognition Solution (FR Solution)

8.6.1. Specification

S. No. Parameter FR System Specification

The Face Recognition Software shall be deployed on the Public Cloud with the

Page 96 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No. Parameter FR System Specification

following minimum requirements:
The Face Recognition Algorithm vendor should have
participated and established in the Face Recognition
Algorithm Evaluation conducted by NIST (National
Institute of Standards and Technology, U.S. Department
of Commerce) or from any Government Test Labs
Algorithm authorized. he benchmark / latest performance FRVT test
1
Benchmarking results of the current calendar year with respect to the
closing date of tender (original/extended) or the last 1
preceding year, the performance efficiency of the
algorithm shall be within the top 25 ranked algorithms of
the FRVT (1:N) test results with FNlR (N=1.6M, T=O,
Rank=1).
For the processing of metadata generated from the Video
Recording Unit/Mobile NVR configured based on the
coach (unique) number in train coaches, adequate
numbers of Face Matching Servers shall be provided at
2 General the cloud assuming a minimum load of 100 new faces per
hour per coach. The central face-matching engine shall
have the capability to process face-matching requests
from the coaches sequentially with Queue management
and load balancing for the matching request.
Matching responses shall be available on web-based
3 General applications which can be configured for individual users
at railway stations, central locations etc.
If the system detects any match, then alarm/alerts carrying
coach (unique) number, frame of the detected person etc.
shall be sent to the Command Control Center and nearest
4 General
RPF Thana/Post via shortest route calculation using GPS
location of the train through available 5G network (auto-
fallback to 4G) or Wi-Fi (if available).
The system shall work on partial occlusion of the face, use
of glasses, scarf, changes of facial expression etc. The
5 General FR system shall also overcome challenges (on best best-
effort basis) such as crowded environments, poor lighting,
moving subjects, angle and distance.
Software such as Facial Recognition etc. as required by
the purchaser shall run on the Cloud and it should be
6 General
possible to send alerts to the central location / Command
Control Center software through the available network.
7 General The system shall be able to work on Windows/Linux

Page 97 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No. Parameter FR System Specification

operating systems.
The FR Solution should preferably possess Artificial
8 General Intelligence and Machine Learning Functional Capabilities
for Higher Accuracy
M-NVR/NVR/VRU installed in all Coaches, EMUs &
MEMUs shall share the cropped images (minimum 70x70
pixels) along with metadata to Facial Recognition
Solution. The FR shall be capable of matching
9 General
desired/intended faces from the cropped images received
from all Coaches, EMUs & MEMUs simultaneously and
generate alerts if a blacklist (face from watchlist) match is
found.
The FR shall be able to work on various kinds of inputs
from any source such as digital image files, live video
sources from any edge devices i.e., IP Camera (on
10 Input Source
demand), Body worn cameras, mobile handset cameras
etc. and generate alerts if a Person of Interest (face from
watchlist) match is found.
Real-time and The Face Recognition System shall work on real-time and
11
offline mode offline mode.
The system shall be able to match suspect faces from
static face images, pre-recorded video feeds as well as
Live and
12 live video feed (if available) from CCTV deployed in any of
Offline Mode
the Locomotives, Coaches, EMUs & MEMUs and mobile
handset cameras.
The system shall support diverse graphic & video formats
as well as live cameras. FR solution shall support
Support for
day/night operation with the ability to detect faces both in
13 cameras/video
Colour and in black/white mode by using H.265 Fixed IP
formats
Cameras with IR Illuminators without any special
configurations required
Resolution The FR shall be able to work on 4CIF, Full HD and higher
14
support resolution.
The system shall be able to utilize any of the file formats
Image Format
15 like JPEG, PNG, BMP, TIFF, etc. for face enrolment or
support
matching.

Page 98 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No. Parameter FR System Specification

The Face Recognition system shall work for matching and
identifying criminals:
Matching a. Videos with Videos
16
Functionality b. Videos with images
c. Images with Videos
d. Images with Images
The FR solution in the Cloud should have a mechanism to
Ability to add
17 update/add any new image of a Criminal in the database
Images
and process it in real time.
The system shall be able to add photographs obtained
Ability to add from law enforcement agencies, newspapers, raids,
18 reference sketches etc. to the criminals‟ repositories along with
Images option details for sex, age, coach number, Geographical
parameters (Lat & Long) etc. for future searches
FR shall be able to simultaneously detect multiple faces in
19 Detection
the crowd.
The system shall have the provision to take multiple
20 Detection
samples of the same face belonging to the same person.
The system shall be able to detect the faces across the
multiple CCTV video sources for online (real-time feed)
and offline (recorded feeds) modes regardless of the
following conditions:
Detection a. Changes in Facial expression
21
robustness b. Changes in facial hair or hairstyle
c. Changes by moderate ageing (up to 15 years)
d. Partially hidden faces or occluded faces like wearing
dark glasses masks etc.
e. Changes in lighting conditions
FR Solution shall be able to check if the newly enrolled
face is already enrolled in the database before registering
the newly enrolled face in the system. Also, the system
22 De-duplication
shall be able to find a previous detection of a POI (person
of interest) upon enrolment to the watch list (retrospective
search) in less than 2 sec.
The FRS shall feature an interface that allows for
configuring the interval of the Facial Recognition System
(FRS) on the edge devices in the field, specifically in the
23 De-Duplication Coaches, Locomotives, EMUs, and MEMUs, to resend the
image of the already detected face to the FRS central
server in the CVMS servers. This user-configurable
interval shall range from 3 to 30 minutes. This interface

Page 99 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No. Parameter FR System Specification

may be either provisioned in the FRS system or in the
VMS.

The system shall be able to detect, track and record the

24 Tracking best images of faces and shall be able to represent them
while providing search results.
The system shall support and simultaneously use multiple
25 Database
watchlist databases.
Categories of The system shall have the capacity to create different
26 database categories of people with the option of user-customizable
faces matching thresholds for different categories.
FR must support a role-based access control (RBAC)
User
27 through a user management module that enables different
Management
user-level groups to support various permission levels.
Simple Search UI that facilitates quick and easy access to
the collection of events recorded by the system without
the constant monitoring by operators
a. Search previous events by images from previous
detections
b. Search previous events by images uploaded by the
Search operator
28
Capabilities c. Search previous events by enrolled names
d. Search previous events by date and time
e. Search previous events by watchlist group
f. Search in the Watch list by image
g. Search with Criminal ID/Number
h. Search with numbers of Coaches and duration
i. Search with geographical parameters (Lat & Long)
The system must perform a full 1: n search of the probe
image under 10 seconds. A database of up to 50 lacs face
images will be considered for face match requests per
face search query.
29 Performance
The database size of the images received from the edge
devices shall grow up to 5 Cr and accordingly, the search
result response time shall be increased by 1 second for
every 5 million increase of face images beyond 1.5 crore
face image records.

Page 100 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No. Parameter FR System Specification

A real-time watchlist should be capable of handling up to
50 thousand POIs (watchlist). The system must perform a
full n: N search of the probe image under 10 seconds
30 Performance wherein;

n= nos. of images received from edge devices

N Nos. of images in the watchlist
The System shall be able to work under the following
conditions:
• Changes in facial expression
• Changes in facial hair or hairstyle
31 Face Matching
• Changes by moderate ageing (up to 15 years)
• Partially hidden faces or occluded faces like fearing
dark glasses etc.
• Changes in lighting condition
The system shall be able to work on moderate face
rotation either horizontal or vertical. It should support a
32 Face Matching
yaw angle of -40 to +40 degrees, a pitch angle of -30 to
+30 degrees and a roll angle of -20 to +20 degrees.
FR System shall have the capability of searching
Retrospective backwards for previous detections and/or recognitions
33
Search (events) of the detected person without enrolment from
live CCTV & other forensic videos / offline videos
FRS must allow tracking of persons on maps (in the ICCC
application) to be uploaded in the system for cameras
34 Map feature
connected to FRS and shall highlight the camera location
on the map for each detection/alert.
Timeline of FR Solution shall provide a timeline sequence of all
35
detections detections of the subject with date, time & location.
Accuracy with Bidder is expected to provide a face recognition solution
36 mask/face using AI & deep learning in such a way that the accuracy
cover in matching an individual with mask shall be at least 95%.
Bidder is expected to provide a face recognition solution
Accuracy using AI & deep learning in such a way that the accuracy
37
without mask in matching an individual without mask shall be at least
99%.
The Face Recognition system must comply with all
prevailing data privacy laws in India to address and aid
38 Privacy
any privacy concerns that may arise from the use of such
software by various agencies in future.

Page 101 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No. Parameter FR System Specification

Use of AI FR shall use extensive AI Technology and perform video
39 accelerator processing on GPUs as per design & sizing vetted by AI
hardware FRS Algorithm OEM.
FR Central Database server as specified by the purchaser
40 Database HA for Facial Recognition system in High Availability (HA)
shall be hosted on the Public Cloud
Build Partial The system shall have the capability to build partial faces
41 and enhance of quality of images before enrolment
Faces
(through inbuilt or other third-party tools).
Automated as well as Manual Data Backup and archiving
42 Backup functionality (through FR application or a backup solution
integral part of overall CVMS solution)
FR Software vendor shall have a mobile application of the
same FR solution software to support iOS and Android-
based smart field devices. Mobile application shall capture
Mobile
the face of the suspect in the field and sending back to the
43 Application
FRS server for matching. The matching result shall be
Support
shown on the mobile application screen with the matching
score. There shall be a provision in mobile applications to
stream mobile device cameras as video streamers.
FR application shall provide floating licenses, having the
44 License capability of deploying the FR application on any live feed
to search through the faces in real-time and offline mode.
The proposed FR Solution shall not have any additional
cost for client users.
45 Users
The MSI shall provide 100 concurrent user licenses/s
subscriptions for the FR application.
FR shall provide an SDK/API for integration with any third-
SDK/API for party software like the ICCC platform. API must be
46
integration available with a full set of documentation of each method
with accompanying sample code.
FR system shall be integrated with the followings applications & databases
47
but not limited to:
The system shall be able to add records obtained from
law enforcement agencies and relevant CRIS/IR
applications (such as Rail Madad) to the respective
47.1 Integration watchlist repositories along with other demographic details
(if available) such as sex, age, coach number,
Geographical parameters (Lat & Long) etc. to present as
part of search results if configured.

Page 102 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No. Parameter FR System Specification

FR shall support email Alerts via Exchange SMTP
services. Different recipients can be defined for different
Camera Groups. Users shall be able to define how
frequently recognition/detection emails are sent, the email
47.2 Integration
subject and the email sender (among other things). The
email itself includes the timestamp of the detection, the
score, the description, the reference image (defined in the
Watch list) and the detected image.
The system shall capture face images from a live CCTV
video feed and generate alerts if a match is found with
47.3 Integration respect to the watchlist. FR alerts should be pushed to the
Video Management System along with a user-defined pre
and post-recording (as per user requirement)
If the system detects any match, then alerts carrying
coach (unique) number, frame of the detected person etc.
shall be sent to the Command Control Center and nearest
RPF Thana/Post via shortest route calculation using the
GPS location of the train through available 5G (with auto-
fallback to 4G) network or Wi-Fi (if available). To achieve
47.4 Integration
this functionality, the FR system must send an alert to
ICCC along with the relevant metadata and other details
as per user configuration/needs. ICCC shall highlight the
camera location on the map (uploaded in ICCC) for each
detection (whenever required) and trigger the respective
SOPs.
The FR system shall be integrated with respective
databases/ applications such as Criminal Dossier from
47.5 Integration various stakeholders, missing personnel records, CCTNS,
Prisons, Courts, or any similar database available from
the State & Central Government agencies.
The Facial recognition system shall have the capability to
integrate with third-party applications such as Big Data
47.6 Integration frameworks and open-source platforms and shall be able
to analyze videos and images received from any third-
party database.
The proposed FR system must also facilitate a mobile app
(android as well as iOS) to carry out facial recognition &
47.7 Integration
verification at the field level. The FR mobile app shall be
integrated with the ICCC mobile app.

Page 103 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No. Parameter FR System Specification

The FR shall be able to integrate with the following:
• ICCC application
47.8 Integration • Video Management System
• LDAP/Active Directory
• EMS & Helpdesk
The Face Recognition Software shall have security
features which can be deployed meeting all the
parameters applicable to software for security,
Security
vulnerabilities, etc. with relevant and equivalent
48 Verification
safeguards with "SAFE TO HOST CERTIFICATE" as per
Certification
the latest OWASP Top 10 from STQC (Ministry of
Electronics & Information Technology) only for testing and
issuing the certificate/clearance
Table 8: Facial Recognition Solution Specifications
8.7. Video Summarization
8.7.1. Specifications
Video Summarization shall apply to live video feeds of identified cameras and to
recorded and exported video feeds. Some of the mentioned features below will be
utilized in the live feed & some of the features will be utilized in the recorded feed.

The Video summarization shall be a cloud-ready application based on computer

vision and AI (Artificial Intelligence) technology enabling rapid video review, search,
quantitative video insights, and smart alerting, thereby shortening time-to-target to
detect and mitigate security threats and enhancing safety and operational
optimization significantly. The system shall be capable of generating the results from
a live feed from the VMS platform with full case management, multi-camera search,
appearance similarity, and face recognition.
i. System shall facilitate leveraging of quantitative video analysis-derived
intelligence for informed, data-driven decision-making, including advanced
trend and dimensional (area, path, duration, and other) as well as full
dashboarding and scheduling capabilities.
ii. The system shall be able to generate live alerts thereby delivering
proactive responses to critical user-defines events ensuring enhanced
safety and security.
iii. The system shall be able to perform the video analysis on the pre-
recorded files. Additionally, it shall be integrated with the video
management system and ICCC proposed by the MSI.
iv. The system shall automatically extract all the moving objects from the
original video and efficiently reconstruct without altering the original

Page 104 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

image/video/data simultaneously displaying events that have occurred at

different times.
v. System shall rapidly pinpoint people of interest, using a range of
appearance and movement filters, across video feeds from multiple
cameras.
vi. Shall Instantly locate people and items of interest by searching for similar-
looking objects or by using facial recognition.
vii. Shall dynamically visualize Key performance (KPI) Indicators (Crowd
Patterns, passenger count, general trends, and insights) derived from
extracted video objects and their classification for comprehensive business
intelligence.
viii. Video Summarization shall summarize the daily alerts and send the
notifications.

8.7.2. Indicative Object Search Criteria

i. Time Range – Shall be able to limit the search criteria to specific time
ranges.
ii. Source – Shall be able to limit the objects to specific CCTV Camera feed
or offline pre-recorded video files.
iii. Classes – Post-analysis, the reviewed video shall be shown based on
People with the following categories:
a. People Class: Man, Woman, transgender, Boy, Girl, etc.
b. People Attributes – Shall be able to select the attributes within the
people class to refine the search. Like:
• Bags: Backpacks, Handheld Bags
• Hats: Hats, No Hats
• Upper Wear: Short/No Sleeves, Long Sleeves
• Lower Wear: Long, Short
c. Colour - Identify objects according to any combination of various
colours like Brown, Red, Orange, Yellow, Green, Lime, Cyan, Purple,
Pink, White, Grey, and Black etc.
d. Size - Select objects based on their actual (real-life) size specified in
meters.
e. Dwell - Select objects dwelling for longer than a certain period in a
scene.
f. Area - Identify objects included or excluded within one or more user-
defined areas.
g. Path - Identify objects and persons travelling along one or more user-
defined paths.
iv. The system shall generate near-real-time alerts based on any of the
above-mentioned search and filter criteria.
v. The system shall be able to extract Facial Profiles of people from the
CCTV Video source.

Page 105 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

vi. The user shall be able to create a watch list of facial profiles uploaded onto
the system using scanned current or old photo images of the known
suspects.
vii. The video summarization solution shall be capable of searching and
summarize relevant video feeds from various cameras for the following
use cases, among others (but not limited to)
a. Information (video feeds) valuable in investigating passenger luggage
thefts, robbery, snatching, thefts of railway fittings and equipment, etc.
b. Evidence for post-incident investigations requested by different security
agencies.
c. Providing evidence in cases of falling passengers from moving trains
and enquiries by RPF in claim cases preferred in RCTs.
d. Supporting RPF & Local enforcement bodies to investigate Kidnapping
& missing cases.
e. Keeping vigilance over the activities of unauthorized hawkers/ vendors/
eunuch/begging.
f. Collecting vital evidence to investigate incidents during Rail Roko
protests.
viii. The application shall have the capability to generate cropped images of
the faces of individuals identified in the video summarization result or
person of interest (Manually by operator). These cropped images shall be
utilized by the Facial Recognition System (FRS) engine to conduct facial
verification against the existing databases and generate alerts in the ICCC
platform.
ix. Video Summarization System/Software should have the capability to
perform all the functionality on recorded video feed. The software shall
essentially evolve to automate the suspect activity capture, and other
analytics as requested in the bid document, and escalation, eliminating the
need for human observation. The MSI along with the respective OEM shall
take complete responsibility for the analytics outcomes as envisaged in the
bid document without any issues (like bad image quality, bad video quality,
camera focus, environmental disturbance, etc.)
x. Performance Parameters:

1. System shall be able to detect the minimum face size of at least

30x30 pixels.
2. The system shall be able to detect the faces across the multiple
CCTV video sources both live and offline videos.
3. System shall be able to detect selected objects from a minimum of
2400 Cameras at a time.
4. System shall use extensive AI Technology and perform video
processing on suitable IT infrastructure.

Page 106 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

5. System shall be integrated with the appropriate database software

for maintaining the various alerts and analysed video feeds.
6. System shall be able to provide video Summarization for 2 hrs.
video in less than 2 mins with selected objects highlighted.
xi. MSI is expected to provide a video summarization solution using AI &
deep learning in such a way that during the first year of operation the
accuracy of provided alerts will be at least 80% accuracy (true alerts/total
alerts). In the future MSI shall train their AI & deep learning model in such
a manner so that the accuracy can increased by at least 5% year on year
until next be achieved more than at least 95% in 3 years from the date of
signing of the contract.
xii. The MSI/OEM is also expected to train their models for other use cases
which may come up during the contract duration, using the raw data
generated within the CVMS project. Certain use cases shall be available
for online feeds, some would be applicable on offline feeds and some on
both feeds.

8.8. Forensic Application (Image & Video enhancement)

i. Image & Video Forensics shall be a cloud-ready Tool to process footage
and still images, analyse the format, clarify content, measure the height of
people/objects & accordingly generate a reliable technical report.
ii. The system shall have easy-to-use functionalities with seamless transition
from one frame to another while processing a video & provide the best
result on applying a minimum number of filters.
iii. The system shall have all possible different filters for all needs during
forensic investigations & shall not require additional plug-ins or third-party
software and filters shall support applications on the whole image, a static
region, or the tracking of a moving object with either static or dynamic
template.
iv. System shall allow users to add, configure, move, and modify an unlimited
number of filters, in real-time even while playing video. Users shall be able
to apply real-time, non-destructive image adjustments that don’t require re-
rendering as changes are applied.
v. System shall display real-time histogram and statistical features of the
image, on one or multiple colour channels. The current filename, image
size and number of frames shall always be visible on the screen for quick
reference.
vi. System shall have advanced video playback with frame-by-frame
navigation, and adjustable frame rate & shall include a special seek
function which allows to move on user-specified intervals. Users shall be
able to manually input a frame number or a time position to quickly move
visualization of frame type in videos.

Page 107 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

vii. System shall support any standard digital image and video format i.e. jpeg,
tiff, png, bmp etc. and avi, mp4, mkv etc. respectively.
viii. System shall allow to loading of multiple images together and support the
conversion of most proprietary video formats from video surveillance
systems to AVI, MP4, MOV etc. formats.
ix. System shall run on any client machine (with Windows & iOS). The client
Licenses/Subscriptions shall not be bound to any specific machine but
shall be possible to move it from one machine to another.
x. The system shall be available in English.
xi. Shall have complete and in-depth documentation which includes a Quick
Start Guide, Tutorials, Program Reference Guide, Filter Reference Guide,
and Keyboard Shortcuts.

8.9. Integrations of Systems

The Integration activity is another critical area which involves the following activities:
a. Integration of different applications within the CVMS Solution Stack hosted on
the Public Cloud
b. Integrations with the edge devices in Coaches, Locomotives, EMU & MEMU
c. Integration with Indian Railways/CRIS applications/other systems/databases
d. Other Government applications
Integration of CRIS and Indian Railways applications and systems is a critical
component in providing an integrated system. Integration of applications and edge
devices shall facilitate smooth flow of data and information allowing systems to work
together as a cohesive unit. Successful integration shall require thoughtful planning,
robust architecture, and the use of compatible technologies to ensure a harmonious
and interoperable ecosystem.
The bidder’s integration scope includes all requisite components essential for the
integration of the applications. This includes, but is not limited to, the identification,
configuration, and deployment of middleware, APIs, connectors, data mapping
interfaces, communication protocols, any other necessary software components, etc.
The integration solution must ensure interoperability and efficient data exchange
between the applications. The bidder shall conduct a comprehensive analysis of
integration requirements, addressing both functional and non-functional aspects, and
shall propose a robust architecture that facilitates smooth communication and data
flow between multiple applications. The integration solution should be scalable,
maintainable, and adhere to industry standards and best practices.
8.9.1. Integration with Edge Devices
The Central Video Management System (CVMS) shall be a central system
integrating all edge devices and applications to provide a common operating picture
and real time situational awareness.

Page 108 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Through the CCTVSS and CVVRS tenders, multiple System Integrators (SI) are
expected to participate to install and commission the edge devices on the field
(Please refer Annexure-1- Other CRIS Bid Documents).

The successful Bidder of the CVMS project shall be responsible to integrate with all
the devices installed by the system integrators in the CCTVSS and CVVRS projects
in the field. Please refer Annexure-1- Other CRIS Bid Documents.

The bidder would need to provide an SDK /API for integration of edge devices so as
to meet the integration requirements given in Table 9:Integration with Edge
Devices“ Integration use cases”. This SDK shall also provide optimization
capabilities such as transmitting at variable resolution/bit rate, appropriate data
packet segmentation or any other alternate mechanism depending upon available
network bandwidth for both mobile data and Wi-Fi (if available) network connectivity
(as available).

The Bidder shall have to use either or combination of the following options to
integrate the edge devices with the CVMS depending on the solution offered by the
Field SI, so as to meet all the Integration requirements as defined in table
“Integration use cases”:

i. Use the ONVIF protocol to provide standardization.

ii. Use the respective SDKs of M-NVR/NVR/VRU provided by the field
System Integrator (SI).
iii. Use SDK/API provided by the CVMS bidder - In case field SI decides to
integrate using SDK/API provided by CVMS bidder.

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
1. Video Streaming Continuous live Yes Yes Yes
(Live) on H.265 streaming of the Edge
Cameras (single
view/multi-view –
static/guard tour) with
the CVMS and ICCC
application on the public
cloud as per the
requested parameters
of the feed (such as –
specific video
resolution, frame rate,
etc.) as per available
network bandwidth

Page 109 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
supporting variable
resolution/bit rate,
appropriate data packet
segmentation or any
other alternate
mechanism.
On-demand live Yes Yes Yes
streaming of the Edge
Cameras (single view
and multi-view –
static/guard tour) with
the CVMS and ICCC
application on the public
cloud as per the
requested parameters
of the feed (such as –
specific video
resolution, frame rate,
etc.) as per available
network bandwidth
supporting variable
resolution/bit rate,
appropriate data packet
segmentation or any
other alternate
mechanism.
2. Video Streaming On-demand playback of Yes Yes Yes
(Playback and video specific to the
Archival) on H.265 defined timeline for the
Cameras (single view
and multi-view) of edge
devices with the CVMS
and ICCC application
on the public cloud as
per the requested
parameters of the feed
(such as – timeline,
video resolution, frame
rate, etc.) and available
network bandwidth

Page 110 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
On-demand playback Yes Yes Yes
(from primary/archived
memory) of
flagged/bookmarked
video (including
respective metadata)
for the Cameras (single
view and multi-view)
with the CVMS and
ICCC application on the
public cloud as per the
requested parameters
of the feed (such as –
bookmark ID,
event/alarm type,
timeline, video
resolution, frame rate,
etc.) and available
network bandwidth
3. Video Compression Interoperability for Yes Yes Yes
Compressing and De-
Compressing the videos
in an interoperable and
open standards
compliant compression
format (H.265) for
transmission from
and/or stored in the M-
NVR/NVR/VRU with the
CVMS/ICCC at Cloud
for reducing the upload
bandwidth.
4. Alerts and Alarms / Receive and Push Yes Yes Yes
Events alarms/events along
with automated on-
demand live video
streams with pre- and
post-recording (as
defined and configured
by the end-user) along

Page 111 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
with date, time, and
geo-location details with
the CVMS on Public
Cloud as per the
defined SOPs
Alert Types: Refer to Yes Yes Yes
Point 5 for details.
Alarm/Event Types: Yes Yes Yes
Press of a panic button,
video analytics triggers
(such as camera
tampering, offline,
RDAS defined
analytics, etc.) at the
camera as well as M-
NVR/NVR/VRU level
5. Health Monitoring Receive, configure, and Yes Yes Yes
(To be integrated display the health
with edge devices monitoring status as
and central EMS well as alerts (on
hosted on public crossing user-defined
cloud) thresholds) for the field
devices but not limited
to the following:
i. Device status Yes Yes Yes
(online/offline/fault),
Uptime and
Downtime (device
as well as network),
Port status,
temperature status
ii. System information Yes Yes Yes
– make, model,
version, serial no.,
and MAC ID
iii. Network Health – Yes Yes Yes
IP address, latency,
bandwidth
utilization
(aggregation as

Page 112 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
well as individual
links), SIM/eSIM
(both) network
strength, availability
of data network and
mode
iv. Resource Yes Yes Yes
Utilization – CPU
and GPU,
RAM/memory,
SSD/Storage,
Recording,
disk/module
removal
v. Audit Logs – Yes Yes Yes
access to audit
logs, alarms, and
SNMP traps
vi. Device Yes Yes Yes
configuration,
firmware/patch
update (camera
and M-
NVR/NVR/VRU)
vii. Video quality and Yes Yes Yes
jitters monitoring
(as feasible)
viii. GPS/NTP for Yes Yes Yes
time
synchronization
ix. User authentication Yes Yes Yes
and access logs
x. SLA monitoring (as Yes Yes Yes
per terms of the bid
document)
6. Remote i. Support for M- Yes Yes Yes
Configuration NVR/NVR/VRU
and Camera level
configuration but
not limited to as

Page 113 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
follows:

ii. Camera Image, Yes Yes Yes

resolution, frames,
compression, BLC,
WDR, NTP, Audio,
IR, streams, and
other general and
network settings.
iii. NVR general Yes Yes Yes
configuration such
as NTP, reboot,
streams, zoom,
network, and other
general settings.
iv. Wi-Fi Access Yes Yes Yes
general
configuration such
as band change,
SSID etc.
7. Interoperability with Receiving of video/data Yes Yes Yes
MSP over true bandwidth
bonding/aggregation
utilizing the SIM/eSIM
cards from multiple
MSPs
Receiving of video/data Yes Yes Yes
over fallback utilizing
the SIM/eSIM cards
from multiple MSPs
Automated video Yes Yes Yes
management for
transmission &
receiving as per the
available network
bandwidth in
aggregation as well as
fallback mode

Page 114 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
Quality of Service Yes Yes Yes
(QoS): CVMS must
facilitate & receive the
prioritization of high
priority data (such as
alarm/event information,
health alerts) over any
other normal priority
data transmission (such
as transfer of all
recorded video feeds on
NVR to the CVMS)
CVMS at Cloud must Yes Yes Yes
support for appropriate
handshaking between
M-NVR/NVR/VRU and
Cloud CVMS for queue
management in case of
connectivity loss. CVMS
shall be able to resume
and start receiving the
recording (video and
audio) based on the
availability of network
connectivity without any
duplication or loss of
the video and metadata.
8. Face Detection Support to receive new Yes No Yes
faces (with minimum
70x70 pixels) in CVMS
on Public Cloud without
compromising the
quality of data as
captured at the source
i.e., Camera.
9. Scalability and CVMS shall support Yes Yes Yes
Upgrades Horizontal scalability of
edge devices (such as
the addition of cameras
or other devices at

Page 115 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
unutilized channels or
Input/Output ports,
feasible module
upgrades) as well as
Vertical scalability of
edge devices (such as
work in coordination
with another M-
NVR/NVR/VRU) for any
expansion or upgrades
in future, if required.
10. Device Discovery Automated discovery of Yes Yes Yes
device (camera as well
as M-NVR/NVR/VRU)
at CVMS
11. Authentication and Role-based user Yes Yes Yes
Encryption authentication to protect
privacy and data
integrity
Encryption (AES Yes Yes Yes
128/256), transmission
& receiving of Secured
video and data as per
the defined
specifications and in
compliance with M-
NVR/NVR/VRU
requirements such as
transmission on
HTTPS, TLS 1.2 or
above, etc.
12. Firmware Update Facilitate firmware and Yes Yes Yes
patch upgrades (on Yes Yes Yes
demand or scheduled)
13. Backup and restore Back-up of device Yes Yes Yes
configurations and data
on demand (manual) as
well as scheduled
(automated) as
configured by the end

Page 116 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. No Integration Details of the Coache Loco EMUs,

Parameter Parameter s s MEMU
s
user

Restore device Yes Yes Yes

configurations and data
on demand (manual) by
the end-user
14. Open Standards Compliance with ONVIF Yes Yes Yes
standard for Yes Yes Yes
interoperability between
M-NVR/NVR/VRU (for
outward Video/data
transmission) and
CVMS application on
profiles as required as
part of the defined
functional and
integration
requirements.
15. Audio Streaming Continuous and on- No Yes Yes
demand audio
streaming of the
Cameras with the
CVMS and ICCC
application on the public
cloud as per the
requested parameters
(such as – specific
audio parameters etc.)
as per available
network bandwidth
supporting variable
resolution/bit rate,
appropriate data packet
segmentation or any
other alternate
mechanism.
Table 9:Integration with Edge Devices
In the future, it is anticipated that certain Locomotives, Coaches, and EMUs/MEMUs
will be factory-fitted with IP CCTV Cameras and M-NVR/VRU/NVR systems. The
scope of the Master Systems Integration (MSI) efforts includes the integration of

Page 117 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

these edge devices which are factory fitted to the CVMS hosted on the Public Cloud
infrastructure.

8.9.2. Integration with Indian Railways / CRIS applications

The given below is the list of CRIS applications being part of the tentative integration
with CVMS setup and will be integrated before Phase 1 Go-live. During the
requirement gathering phase, CRIS will share the priority and timeliness of the
integration with below below-mentioned application, however, all the required
integration to be completed before Phase 1 Go-Live of the overall CVMS solution.

8.9.2.1. General Specifications

i. The Bidder shall provide all relevant integration services and integrate the
service from CRIS applications after finalization with CRIS in the
Requirement Gathering & Design phase.
ii. The CVMS system shall support integrations with the latest technology,
preferably API-based integration (E.g., JSON) with existing CRIS backend
systems.
iii. The assured delivery of alerts and data from CVMS to other CRIS
systems/other systems shall be ensured.
iv. ICCC shall be integrated both ways with other CRIS & IRs applications for
complete incident management and SoP execution.
v. Mobile Applications
a. The integration shall be facilitated with the required Mobile Applications
of CRIS and newly developed as part of the CCTV Project scope.
b. All the incoming integration from CVMS to CRIS systems have to be
integrated through the existing API gateway of CRIS.

8.9.2.2. Tentative List of Applications

The below-mentioned list is not exhaustive, further application and database details
will be shared during the requirement gathering and design phase.
S.No Application Application Purpose (Tentative) Integration
Reference Name Category
Name
1. ICMS Integrated ICMS for Coach, EMU/MEMU Primary
Coaching & Train Service mapping to
Management display train wise video feed
System on VMS Dashboard.
2. NTES National For providing train ETA to Primary
Train plan action required on alert
Enquiry
System

Page 118 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S.No Application Application Purpose (Tentative) Integration

Reference Name Category
Name
3. PRS Passenger Passenger details for a train Secondary
Reservation service
System
4. RSMS RPF Security Criminal database and send Primary
Management all the respective alerts to
System respective RPF stakeholders
5. HHT Hand held Panic button alert details to Primary
Terminal respective field responders
6. GIS Geographical To fetch the position data Primary
Information based on lat & long received
System from CVMS
7. COA Control For Loco & Train service Primary
Office mapping and displayed Train
Application wise video feed on VMS
Dashboard.
8. CMS Crew For Crew information Primary
Management
System
9. CMM Coaching SLAM, CMM, EP for Loco, Primary
Maintenance Coach, EMU/MEMU Units
Module maintenance schedule to help
10. SLAM Software for Bidder plan edge device Primary
Locomotive installation/repair/replacement
Asset on Locos & coaches.
Management
11. RailMadad IR Grievance The resolution update of Primary
Redressal public grievances received
Portal from CVMS to be sent back to
CVMS system
12. HRMS Human To map the employee data of Primary
Resource Indian Railways for single
Management sign on
System
13. NATGRID National Secondary
Intelligence
Grid
Table 10:Tentative List of Application

Page 119 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

8.9.2.3. Integration with Other Government applications

The CVMS system shall be integrated with respective databases/applications such
as Criminal Dossier from various stakeholders, CCTNS, Prisons, Courts or any
similar database available from the State & Central Government.
8.10. Cloud Hosting Platform

The MSI shall ensure that the offered cloud services for hosting CVMS applications
shall comply with MeitY regulations with scalability, high availability, and efficient
data processing capabilities to ensure the seamless operation of the video
surveillance system.
The MSI shall also ensure that the proposed CVMS solution stack should be hosted
on single CSP platform only to meet all the functional and non-functional
requirements mentioned in bid document Part-II.
8.10.1. Design Consideration: Cloud Services

With an envisaged deployment of nearly 7 lakh+ edge devices in various phases (for
more details, Annexure-1- Other CRIS Bid Documents) in the field, the IT
infrastructure services expansion strategy shall be seamlessly aligned with the
rollout of edge devices on the cloud hosting platform. This necessitates that the
underlying infrastructure can efficiently scale up with the growing number of edge
devices without disrupting CVMS services. The infrastructure hosting for the CVMS
system must adhere to the following design principles and considerations, and the
MSI is required to ensure full compliance with their design.

i. Scalability: The MSI shall ensure that the proposed CVMS solution
hosted on the cloud platform shall have the capability to scale, and
accommodate the growing number of cameras, M-NVR/NVR/VRU, and
increasing images, video data storage as per the capacity requirements of
the project during rollout without any performance disruption. There shall
be sufficient buffer capacity available for resources like compute, storage,
network, security, etc. to take care of anticipated growth.
ii. Availability: The underlying infrastructure shall be robust enough to
ensure maximum uptime and "round-the-clock" availability of CVMS
services as per the defined SLA. The proposed Cloud services must
maintain an uptime of 99.9% on monthly basis.
iii. Interoperability: The proposed CVMS solution hosted on the cloud
platform shall have compatibility and compliance with the applicable
industry standards to ensure interoperability with third-party devices,
network backbone, systems etc.
iv. Security: The proposed CVMS solution will store highly sensitive personal
and critical data, both in raw and processed formats, it is imperative to

Page 120 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

have built-in security by design. The deployment architecture and

infrastructure shall provide a high level of security against any form of
breach through necessary technical and process interventions in
compliance with guidelines issued by MeitY / Cert-In / e-Gov, GOI, RDSO,
etc.
v. Data Governance and Security: The framework being put by the MSI
shall ensure that the granularity of the data access shall be maintained.
The framework shall clearly be able to define the rules which basically
answers the following questions.
a. Who gets access to what data...?
b. How much data is accessed...?
c. From where the data is accessed...?
d. Between what times the data is accessed...?
vi. The Data Governance and Security Framework shall have capabilities to
capture and document all data governance rules, define role-based access
requirements, data security standards and accommodate the same
through a well-defined process including the changes in such data
access/governance rules. The proposed design framework shall have
capability to enforce these rules at every level. It shall also have effective
dashboards to monitor deviations at each level.
vii. The proposed CVMS solution shall be compatible with IPv4, IPv6 and dual
stacks.
viii. MSI shall ensure that proposed Solution should have capability to
anonymise/Mask/Encrypt the data depending upon its severity/access
control policy and requirement by CRIS/IR.
ix. For seamless and efficient integration with internal and external application
systems, MSI shall ensure that the proposed CSP has its API gateway
solution that can be utilized as needed to facilitate seamless integration
with these applications throughout the contract period. The API gateway
solution will include robust security and monitoring features. The proposed
CVMS solution will support API-based integration with third-party
applications.
x. The MSI shall propose a high-level architectural diagram of CVMS solution
covering application layer, underlying infrastructure likewise Intranet /
Internet gateway, compute, storage, backup, network, security, and
monitoring layer.
xi. The MSI shall ensure that the proposed solution should have NTP
synchronization with IRNSS/NAVIC.
xii. The MSI shall provision and manage the license for secure remote access
of CVMS services as mentioned below.
a. The MSI shall provide IPsec VPN tunnelling for 100 users with a
b. capacity of 60 users covering laptops, mobiles, and smart tablets.

Page 121 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. The MSI shall provide Site to Site VPN tunneling connectivity for 03
locations.
d. Additionally, PIM/PAM services are required for 60 governance users.
e. The storage tiering solution shall be aligned with FIFO (First in First
Out) mechanism.
(For more detail regarding the storage / recording requirements pls
refer to Section Sizing Parameters for the CVMS Solution)
f. The MSI shall ensure the CSP will provide ports for terminating
different types of backhaul links of different TSPs/ISPs (minimum 6
ports of 10G capacity), which shall be communicated by CRIS during
the contract period.
xiii. A copy of data backup shall be taken at separate remote MeitY
empanelled cloud locations which shall be at a distant site physically to
adhere the Business Continuity Plan (BCP) during any disruptions/failure
of CVMS services in line with the uptime defined in Service Level
Agreement (SLA) – Post Phase 1 Go-Live .
xiv. The MSI shall conduct audit for the entire CVMS setup including
application & underlying infrastructure as per the milestone mentioned in
Project Implementation Timelines.
xv. The proposed CVMS solution hosted on cloud platform shall be all-
inclusive without any price fluctuation impact on CRIS. All data transfer
charges (Ingress and Egress, retrieval) shall be included by MSI in its
proposal and no separate cost shall be paid by CRIS during the period of
the contract.
xvi. The proposed landscape for the CVMS solution deployment includes:
a. Development,
b. UAT/Staging,
c. Production, and
d. other environments if required.

These environments will be deployed on the VPC Cloud of the MeitY -

empanelled CSP platform, with each environment logically isolated from
the others.

xvii. The MSI shall adhere to optimize the performance of cloud-based

services, as per the ensuring responsive and efficient delivery of CVMS
services in line with the performance parameters define in the Section
Service Levels.
xviii. The Overall proposed solution shall be managed centrally so that any
policy and changes can be applied at any cluster from a central
management console.
xix. The MSI shall provision and manage SMS gateway, Email / Mail server &
their integrations with the proposed CVMS solution. MSI shall consider the

Page 122 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

appropriate sizing required for the resources for the email/mail server and
the quantities for the SMS alerts including any recurring charges.
xx. The MSI shall ensure comprehensive SLA monitoring and management of
various systems and applications as part of the proposed CVMS solution
including underlying IT infrastructure, application, integration, resource
utilization, alerts, notifications, incident management, security, compliance
monitoring, and performance reporting etc. and integrations parameter
mentioned in Annexure-4-Integration of the Applications of CRIS, for
monitoring please refer Section Enterprise Management System (EMS).
xxi. For all proposed cloud services, the MSI must ensure that all software
offered are of latest and stable versions, genuine and complies with the
licensing policy.
xxii. The offered CVMS solution shall not result in "Vendor Lock-In," ensuring
ease and smoothness for the migration of applications and associated
systems across MeitY empanelled CSPs. CRIS reserves the right to
migrate from one cloud service provider to another or to on-premises DCs
or CRIS/Railways’ own Cloud during the contract period or on exit. In such
cases, the selected MSI shall provide all necessary support for a seamless
migration, transition, and handover without any additional financial
implication to CRIS.

8.10.2. Managing the cloud infrastructure:

i. The MSI shall engage a MeitY-empaneled Public Cloud Service Provider
to provide IaaS, PaaS, and SaaS services as per the requirement of the
CVMS solution and all the services along with underlying infrastructure
offered shall adhere to the MeitY guidelines.
ii. The MSI is expected to study the design principles and considerations,
conduct a detailed assessment of CVMS solution requirements, and
evaluate the infrastructure needs (Compute, Storage, Networking,
Security, etc.) for provisioning the CVMS solution.
iii. The MSI shall configure and manage the entire cloud infrastructure
according to the functional requirements of the CVMS solution.
iv. The MSI is responsible for operating and maintaining the cloud
infrastructure 24*7, resolving all incidents, and meet performance
parameters defined in the Section Service Levels.
v. The MSI shall provision MZ Zone, DMZ and Management Zone and
appropriate role-based access mechanism for the proposed CVMS
solution.
vi. The MSI shall ensure that the user admin portal shall be accessible for all
the CVMS applications and its related services.

Page 123 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

vii. The MSI shall provide a centralized monitoring dashboard for CRIS to view
the application status and all the underlying infrastructure hosting the
CVMS solution.
viii. The MSI shall ensure that the application and stable system software are
up to date, with an appropriate level of stable security patches for risk
assessment and exploitation of vulnerability during the entire period of the
contract.
ix. The MSI will ensure the quick & timely deployment of security patches and
software on underlying infrastructure with approval from CRIS and submit
the detailed report to CRIS.

8.10.3. Compute

i. The MSI shall provision and manage required cloud IT infrastructure

solution, including VM’s /containers of different configurations (with latest
generation CPU), Storage of different IOPS, networks such as IP Schema,
VLAN, micro-segmentation security, monitoring solution and DNS Service,
etc. to host CVMS solution.
ii. The MSI shall ensure that the underlying infrastructure of CVMS solution
shall be capable of auto-scaling without any manual intervention to add/
reduce cloud resources as per functional requirements of CVMS solution.
iii. The MSI shall be responsible for provisioning and management of
underlying infrastructure including Operating Systems, VM’s/ Containers,
Storage, Network, System software, required security solutions, services
and availability of latest and stable security patches during the entire
period of contract.
iv. The MSI shall ensure provisioning of requisite network and security
Infrastructure (including Network Security for perimeter, DDoS, Anti-APT,
WAF, HSM/KMS/Encryption Services, PIM/PAM, Load Balancers etc.)
along with network segregation in different VLAN as required for
successful operation of CVMS solution.
v. The MSI shall ensure to manage and maintain requisite redundancy and
high availability of systems such as Load Balancers, databases, storage,
network, and compute instances for automatic allocation of the resources
against running load to handle sudden spikes and to minimize the single
point of failure. The uptime shall be in line with the SLAs parameter
mentioned in the bid document Part-II Section Service Levels.
vi. The platform shall allow logical grouping of instances together for
applications that require low network latency and/or high network
throughput or for maintenance operations.

Page 124 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

8.10.4. Storage
i. The MSI shall provide scalable, dynamic, and redundant storage with
efficient storage tiering features and configurable life cycle management
shall be used for efficient data retention, with options for short-term and
long-term storage required for CVMS solution to manage video feeds and
images.
ii. The MSI shall provision and manage storage tiering with respect to
frequent access, infrequent access, and long term archival based on data
usage patterns as per the Section Design Consideration: Cloud
Services.
iii. The MSI shall provide the storage solution to meet IOPS requirements of
frequent, infrequent & archival data storage for different workload.
iv. The MSI shall ensure that the provisioned storage for CVMS solution shall
support the scalability as and when required based on storage utilization
threshold and offer automatic storage allocation to add more storage as
per the requirement.
v. The MSI shall implement efficient data storage solutions that can handle
increased volumes of data during peak periods without compromising on
performance. Refer Section Sizing Parameters for the CVMS Solution
to understand data requirements during peak and emergency situations.
vi. Cloud service shall support attaching of storage volume to multiple
compute instances in R/W mode so that users can access and share a
common data source.
vii. Cloud service shall support point-in-time snapshots. These snapshots
shall be incremental in nature.
viii. Cloud Service shall provide versioning, where multiple versions of an
object can be kept in one object storage account. Versioning shall be
protected against unintended overwrites and deletions.
ix. The CVMS data shall be encrypted adequately in rest and as well as in-
transit to maintain the integrity.
x. Cloud service shall support encryption of data on volumes, disk I/O, and
snapshots using industry standard AES-256 cryptographic algorithm.
xi. Cloud service shall 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.
xii. Cloud service shall provide flexible access-control policies to manage
permissions for objects.
xiii. Cloud service shall be able to send notifications when certain events
happen at the object level (addition/modification/deletion).
xiv. The stored data must support WORM functionality to ensure that the
immutable copy of data is made available in case of an incident in
alignment with data retention policies of CRIS.

Page 125 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xv. Cloud service shall be able to provide audit logs on storage account
including details like the timestamp when the data access activities
occurred (Using API etc.), Source of the activity, Target of the activity,
Type of action and Type of response.

8.10.5. Backup Solution

The backup service shall allow the creation of backup policies, enabling the definition
of backup requirements that can be applied to CVMS's cloud resources, workloads,
and services requiring backup in consultation with CRIS. It shall provide the flexibility
to create distinct backup policies to meet specific business and regulatory
compliance requirements of CRIS. This ensures that each of the cloud resources,
workloads, and services is appropriately backed up and protected.
In view of above, the following activities need to be managed and performed by MSI.

i. The MSI shall configure and manage backup policies according to the
defined SLA mentioned in bid document Part-II (Service Levels) for the
CVMS solution.
ii. The MSI shall be responsible for the provisioning and maintaining the
backup in the cloud environment as per the below backup policy.

Backup Type Data

Full backup Weekly, Monthly, yearly
Incremental
Daily
Backup
Retention One Year
Yearly copy during complete project tenure. The final set must be
Archival
handed over to the department on exit.

11:Backup Policy
iii. The MSI shall
adhere to the following in addition to the backup policies.
a. An Initial full backup.
b. Daily incremental backup with 7 days of retention.
c. Weekly full backup with 15 days of retention.
d. Monthly backup with 30 days retention on Object Storage and 1-
year retention on Long-Term Storage.
iv. The MSI shall adhere to the following restoration policies:
a. Backup taken in last 6 months shall be restored once in a quarter of
the year.
b. Backup taken in last 1 year shall be restored once in half a year.
v. The MSI shall configure and manage backup solution with different
features, like snapshots of VM’s, video data, database backup,

Page 126 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

incremental and full back up of all data, restoration of data in test

environment or as and when required.
vi. The MSI shall manage overall backup solution centrally so that any policy
and changes can be applied on any cluster from the Central Management
Console.
vii. Backup of all system software configurations inclusive of source code ,
database configurations, events & audit log, device mapping & integration
configuration, user configuration, and any other CVMS data stored on
cloud shall be taken regularly and restore data to ensure complete
recovery in case of any disruptions.
viii. The MSI shall be responsible for maintaining the source code of the
Central Video Management System (CVMS) in a designated version
control software. This version control repository shall be accessible to
CRIS. The MSI must ensure that the version control system is regularly
updated and synchronized with the latest developments in the CVMS
software.
ix. The MSI shall clearly define and classify the critical levels of the
data/information and systems, in consultation with CRIS.
x. The MSI shall ensure that data is stored in immutable backup with proper
encryption and version enablement feature so that the data cannot be
modified and deleted under any circumstances.
xi. The backups shall be a fully automated procedure requiring no manual
intervention, shall be scheduled during non-peak hours and completion
status reports shall be circulated to authorized persons through emails.
xii. Backup service shall allow to create customized backup schedules to meet
business and regulatory backup requirements.
xiii. Backup policy shall allow to set backup retention policies that will
automatically retain and expire backups according to the business and
regulatory backup compliance requirements as per the design
consideration. The prior notification shall be sent to the CRIS authorized
person before deletion of any stored data.
xiv. The MSI shall ensure that the proposed CSP shall have its own
centralized backup solution to meet the data backup requirements mention
in the Bid document Part-II.
xv. Backup service shall provide lock mechanism to protect backup from
deletion or changes during data lifecycle by unintended or intended
changes.
xvi. Additionally, the backup service shall offer a monitoring dashboard to track
ongoing backup and restore activities, as well as to view logs of completed
or failed backup jobs.
xvii. Backup and recovery procedures shall be well documented, properly
implemented, and tested periodically, by the respective workgroup

Page 127 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

responsible for the management of different applications of CVMS solution

and report shall be submitted to CRIS.

8.10.6. Data Governance and Security

i. The MSI shall ensure that the CVMS Solution is based on the Zero Trust
Model security architecture, which requires verification for all users
through MFA, attempting to access network resources, means that by
default, neither users inside nor outside the network can be trusted.
ii. The MSI shall provide and manage the adequate security solution for
CVMS system which includes security at the perimeter (FW, IPS, VPN for
secure remote access, DDOS, WAF), for authentication (PKI, IDAM, SSO,
AD/LDAP, MFA, HSM/KMS, SSL certificate) and internal security
measures (endpoint/VMs security, container security, Anti-APT etc.)
iii. The MSI shall provision below network security services to secure the
CVMS System environment.
a. DDoS protection
b. WAF functionality
c. NGFW
d. IPS
e. End-Point protection for VM/Containers
f. Data Encryption at rest and in transit
g. SSL off-loader
h. Data protection
i. SIEM and SOAR
j. Network Zoning/Micro-segmentation
k. DNS Security
l. Identity Access Management and Privileged access management
(IAM/PAM)
m. Others (If required)
iv. The MSI shall always ensure continual compliance as mandated in MeitY
empanelment and in addition must have following certifications.
a. Cloud security guidelines by MeitY/Cert-In, GOI for security and other
compliance controls.
b. ISO 27001:2022, Information Security Management Systems.
v. All components and other system integrated with CVMS should have
defined mechanism/solution/tools to view and identify malicious user
activities and potential security incidents through audit logs.
vi. The MSI shall provide cloud services that support auditing with features
such as what request was made, the source IP address from which the
request was made, who made the request, when it was made, login

Page 128 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

attempts, login failure, software installation attempts, security logs, and so

on.
vii. The MSI shall ensure that the proposed firewall rules/policies can but are
not limited to provide state-full inspection, filter packets based on
protocol/source & destination address/source & destination ports, support
for protection of common internet applications like mail, DNS, AAA, etc.
and must prevent IP Spoofing, be able to filter malicious viz. Java Applets,
ActiveX and perform Network Address Translation.
viii. The MSI shall ensure that the firewall policies monitor network traffic
identify intrusive activity and respond to network attacks. If there is any
intrusive activity, then besides generating an alert, the firewall shall
perform the following actions:
a. Drop traffic.
b. Block traffic
c. Log traffic
ix. The MSI shall ensure CVMS Solution is protected with WAF to avoid
common web exploits that could affect application availability, compromise
security, or consume excessive resources.
x. The MSI shall offer a WAF service which includes features that allow to
detect and either block or allow identified bot traffic to web applications.
xi. The MSI shall ensure to provide and manage Layer 3 & Layer 7 protection
to protect workloads against known and unknown threats, brute force
attacks etc.
xii. The MSI shall ensure that the VPN policies and VPN users are configured
in the VPN server to access an authorized set of devices in the internal
networks.
xiii. The MSI shall ensure that all containers/VM’s, & applications related to
CVMS solution shall be firewall protected and come under the scope of
Managed Security Services.
xiv. The MSI shall implement robust encryption techniques and maintain
appropriate key management to protect data while it's in transit and at rest.
xv. The MSI shall provision SSL certificates for the web servers that are
`being used to access the web applications. SSL certificates shall be used
to ensure the integrity of data transmitted between the client and the
server and shall also ensure that it is not tampered with during transit. The
provisioned SSL certificates validity period shall be monitored and shall be
renewed well before their expiry.
xvi. The MSI shall ensure to uses of strong authentication, authorization and
auditing mechanisms which include (PKI, IDAM/ IAM, SSO, AD/LDAP,
MFA, SSL certificate etc.) and provide access to CVMS systems to
authorized users. Policy of Segregation of duties and least privilege
access shall be ensured to the extent possible.

Page 129 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xvii. The MSI shall provide Identity and Access Management for managing
access to CRIS users.
xviii. Antivirus and proxy server administrators shall ensure that up-to-date
antivirus signatures and OS patches are available on the servers.
xix. Logging shall be enabled on all Information Processing Facilities and shall
store relevant information to identify who access what and when. Stored
logs shall provide sufficient information to support comprehensive audits of
the effectiveness and compliance of security measures. At the same time,
event logging shall be configured so that only significant or unusual events
are logged so that these can be detected easily for quick corrective
measures.
xx. The MSI shall ensure compliance with Cert-In guidelines/directions issued
on Network Time Protocol Synchronization. And ensure availability of logs
in case any deviation of time from Cert-In designated NTP Server.
xxi. The MSI should provide and implement a robust data anonymization
solution, including encryption and tokenization, to ensure that personally
identifiable information (PII) or sensitive data is rendered anonymous
before storage or processing.
xxii. MSI shall ensure that the CVMS solution shall be based on detect-and-
respond framework to provide underlying cloud service visibility, policy
governance, detecting risk, incident and generating alerts.
a. Examine the cloud resources for weakness related to configuration and
these problems shall be mapped to Center for Internet Security (CIS)
Benchmarks.
b. Examine the cloud resources for weakness related to the operators
and users for risky activities.
c. Detect patterns of activity that indicate possible malicious attempts to
gain access to resources in the cloud environment and use them for
corrupt purposes.
d. The proposed solution shall have cloud workload (containers/VM’s)
protection which support following functionality.

a) Security Control – To ensure that only authorized users and

process can interact with the cloud workload.
b) Data Encryption – Data both at rest and in transit shall have the
end-to-end encryption.
c) Run time security – Malware and anti bot detection.
d) Vulnerability management – Promptly addressing any identified,
weakness or any security issues.

e. The MSI shall comply or meet any security requirements applicable to

CSPs published (or to be published) by Ministry of Electronics
Information and Technology (MeitY), Government of India and any

Page 130 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

standards body setup / recognized by Government of India from time to

time and notified to the CSPs by MeitY as a mandatory standard.
f. The overall security solution shall be able to take intelligence / IOC
from multiple threat feeds - MeitY / Cert-in or e-Gov agency /
departments on time-to-time basis.
g. The Live stream received from the edge devices installed in the
Coaches, Locos, EMUs & MEMUs shall be FTPs (FTP – Secure) or
RTSPs (RTSP – Secure) or HTTPS – Live Streams. The MSI shall
ensure that the necessary peer service at the CVMS end at the Cloud
shall also be provisioned to ensure that secure live streams are
seamlessly received and stored at the CVMS.
h. The MSI should ensure that all users using the Internet to access the
CVMS solution stack for using any application of the CVMS or the
Edge devices, their data traffic should be completely encrypted through
a VPN tunnelling application ensuring security and privacy.

8.10.7. Self-Service Portal for CVMS: Management and Governance

The MSI shall be responsible for provisioning and managing the self-service
portal that facilitates the autonomous provisioning of services without requiring
human interaction. The account shall be opened in the name of CRIS as root
entity but shall always maintained by MSI and no data shall remove from the
account by MSI at any time unless specified instruction is provided by CRIS. The
following activities need to be performed by MSI.
i. The service Portal shall have a graphical user interface with an in-built
role-based access control ‘RBAC’ feature.
ii. The portal shall provide access to view, modify, subscriptions, licenses,
and services that will be provisioned for CVMS solution.
iii. The MSI shall offer a set of services through its online administrative
console suite through which they can perform routine tasks on a self-
service basis, e.g., provision the compute instances, mount storage,
configure network topology etc. as required for the application setup.
iv. The proposed CVMS solution shall support cloud self-service portal for
comprehensive suite of management, provisioning, and governance. The
console/ management suite shall support secure login for the allowed
users only. It shall have the facility to configure two-factor authentication
for added security.

Page 131 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

8.10.8. Technical Specifications for Additional Compute and

Storage
8.10.8.1. Virtual Machine or Compute

i. Must support variety of operating systems including Linux, Ubuntu,

Windows Server, Red Hat Enterprise Linux, SUSE Linux, Enterprise
Server, CentOS, Debian, etc.
ii. Secure Web administration interface, which must be provided to remotely
administer the virtual instances Window, Linux, Cent OS etc.
iii. Service shall provide auto-scalable, redundant, dynamic computing
capabilities of virtual machines. Shall support autoscaling of the compute
service based on CPU utilization of the Instance. CSP shall offer an ability
to automatically increase or scale- out the number of Instances/VMs
during demand spikes to maintain performance (i.e., ‘scale-out’), as well
as an ability to automatically decrease the number of deployed Instances if
the demand drops.
iv. Shall support block storage and temporary block storage (to store
Information that changes frequently, such as buffers, caches, scratch data,
and other temporary content)
v. Virtual Machines offered shall be with the latest generation processor
offered by the processor (Not earlier than 2021).
vi. CSP shall provide flexibility to users to choose from Intel, AMD, and Arm
processors from the India Region.
vii. The required Operating System shall be offered along with the Virtual
Machines.
viii. The OS offered shall come with continuous updates and upgrades for the
entire contract duration.
ix. CSP shall support both BYOL (Bring your own license) as well as PAYG
(Pay as you go).
x. Cloud service must offer self-service provisioning of multiple instances
concurrently either through a programmatic interface (API/CLI/Infra as
code) or through a management console.
xi. CSP shall offer a managed service to run web applications directly without
provisioning infrastructure.
xii. Compute Service shall offer Pay-as-You-Go Pricing.

8.10.8.2. Storage (Block and Object)

i. Cloud provider shall offer persistent block-level storage volumes for use
with compute instances which shall provide scalable, redundant, and
dynamic storage up or down per request for service from the end users.

Page 132 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Block Storage with minimum monthly uptime of 99.9% or higher (as

published in the CSP’s Public Portal).
ii. For all volumes pertaining to VMs, the proposed storage should have
sufficient IOPS to ensure application performance in line with functional
requirements & should adhere to performance SLA mentioned in Section
Service Levels
iii. For the proposed Block Storage, CSP shall offer the capability to increase
the size of an existing block storage volume without having to provision a
new volume and copy/move the data. Block Storage shall be one
continuous disk and the CSP shall have capability to add more storage to
the same in increments of 1GB.
iv. Cloud service shall support point-in-time snapshots. These snapshots
shall be incremental in nature.
v. Cloud provider shall offer secure, durable, highly scalable object storage
for storing and retrieving any amount of data from the web.
vi. Cloud provider shall support extremely low-cost storage for archival along
with active storage.
vii. Cloud Service shall offer geographically redundant object storage,
however, data should reside within India only at any given time.
viii. Cloud service shall support encryption of Storage using CSP provided, or
customer provided keys. These keys shall be used to manage both the
encryption, as data is written to disks, and decryption, when data is
accessed. Object storage shall have integration with CSP its HSM to
provide inherent capability of encryption.
ix. Cloud Service shall 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. Send notifications
when certain events happen at the object level (addition/deletion).
x. Cloud service shall have capability to create fine-grained access control
policies to selectively grant permissions to users and groups of users.
Object storage shall support both users based & resource-based access
control policies.
xi. Object storage service shall have archive storage class.
xii. Cloud Service shall support versioning, where multiple versions of an
object can be kept in one folder/bucket. Versioning protects against
unintended overwrites and deletions.

8.11. Patch Management

The MSI shall be responsible for provisioning the patch Management, stable
software, and firmware updates for the CVMS and field implemented edge devices
(CVVRS and CCTVSS Solutions).

Page 133 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

The MSI shall perform the following activities.

i. The patches to be deployed for the CVMS solution must be in accordance

with the approval and recommendation from respective OEMs.
ii. The activity shall be planned in coordination and approval from CRIS.
Depending on criticality of activity, on instructions from CRIS, the MSI shall
arrange the OEM resource at the site.
iii. The MSI shall ensure complete rollback to original status in case of any
problem detected during the updates and shall take necessary system
backups before any activity of hardware/SW upgrade/Changes in
configuration etc.
iv. The patches shall be stable and shall not have any performance impact on
overall CVMS solution.
v. Software updates/upgrades shall also be done keeping in view
advancement in technology, shortcomings of the system, security
vulnerabilities, or changes required for improving functional efficiency and
security level of the system.
vi. Create a test environment for testing all the necessary patches, firmware
updates prior to its deployment.
vii. The deployment shall be initiated post successful testing of new patches
and approval from CRIS.
viii. New patches shall be implemented in consultation with CRIS & shall be
deployed within 15 days after approval from CRIS.
ix. The patches to be deployed in the production environment shall be done in
batches to mitigate the risk of disruption of service in the overall CVMS
solution.
x. MSI shall Coordinate with OEM and Field SI’s (System Integrators for
CCTVSS, CVVRS) for the patch management, software/firmware updates
on the field edge devices.
xi. Submit a weekly report to CRIS for the final deployment of new patches.
xii. MSI shall ensure the security patches are applied after every re-installation
or maintenance activity of all components of CVMS.
xiii. Though the MSI shall not be responsible for the implementation of the
Patches for the Field installed Edge devices, the MSI shall extend
dashboards for CRIS to understand the status of the patches that have
been implemented for the complete CVMS solution stack as well as the
field installed edge devices.
xiv. The dashboard should provide detailed view which clearly indicates the
status of the different type of patches that need to be implemented and
progress of the same on the CVMS solution stack as well as the field
installed edge devices.
xv. All software updates for the CVMS applications must receive security
certification from STQC before being applied to any production

Page 134 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

environment to meet the necessary security standards and reduces the

risk of security vulnerabilities in the CVMS applications.

8.11.1. Patch Management for CVMS Solution

The MSI shall provision the required OS patch Management, software/firmware
updates of CVMS solutions during the entire period of the contract. New patches
shall be implemented in consultation with CRIS & shall be deployed within 15 days
after confirmation from CRIS.

8.11.2. Patch Management for Field Equipment

The MSI’s scope shall also include setting up a patch management interface
(including VM, if required) along with required services for each field SI's managing
the CCTVSS and CVVRS solutions during the entire period of the contract. While the
responsibility of implementing new patches on edge/field devices lies with respective
field SIs, the CVMS solution provider/MSI to ensure the availability of patch
management interface (including required access rights, reports & dashboard) to the
respective field SIs all times. The field SI’s shall test the new patches before
deployment in consultation with CRIS. The dedicated Patch Management Interface
provided to each of the field SIs shall also have a provision that the patch updates
are pushed only to those edge devices that the field SI has supplied.

9. Qualifications Criteria
9.1. Master Service Integrators Qualifications
i. All the criteria given in the Table 12:Qualification Criteria for MSI below
are mandatory for qualification.
a. Joint Venture (JV) is allowed to bid against this tender. Applicable
conditions for JVs are as per Clause 17.2 below. Further, Number of
members in a JV shall not be more than three, including the Lead
Member of the Joint Venture.
b. Consortium is allowed to bid against this tender. Applicable conditions
for Consortium Bidders are as per Clause 17.2 below. Further, Number
of members in a Consortium shall not be more than three, including the
Lead Member of the Consortium.
ii. The criteria must be met by the entity bidding for the project i.e.,
qualification, experience etc. of the sister/associate companies shall not be
considered.

Page 135 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

1. Company The bidder should be a Certificate of Incorporation,
Existence Private/Public Company registered copy of Articles of
under the Companies Act, 2013 or Association (in case of
Proprietorship/Partnership firm, registered firm), Bye Laws &
society and should be registered for certificates of registration (in
more than five years as on the date case of registered society),
of closing of tender. Partnership deed (in case of
[Note: Lead Member or Lead partnership firm) and
Partner of the JV/Consortium has to establishment registration
fulfil the Qualification Criteria] certificate (in case of
Proprietorship firm) shall be
attached
2. Financial Financial turnover of Bidder: * a. CA certificate to this effect
Turnover Average Annual Turnover of Bidder is to be submitted.
during last three Financial Years b. Certified audited copies of
(i.e., 2020-21, 2021-22 & 2022-23) Balance Sheets/Profit &
has to be minimum ₹1200 Crore. Loss Accounts / Annual
[Note: Lead Member or Lead Reports of last three
Partner of the JV/ Consortium shall financial years shall be
have minimum ₹960 Crore of submitted.
average turnover from last three FY
to fulfil the Qualification Criteria] and
balance criteria to be fulfilled by
other JV/ Consortium members.
3. Relevant The Bidder shall have successfully Relevant Project/work
Project/wor completed: experience**
k At least One (1) project of INR 60 (i) Copies of PO or any other
experience crores (INR Sixty Crores Rupees) associated documents
** specifying details of similar
OR nature of Work.
And
At least two (2) projects each of INR (ii) Satisfactory Completion
40 crores (INR forty Crores certificate/performance
Rupees) certificate/Go-Live
Certificate of such order by
OR Government/PSU/
Corporate.
At least three (3) projects each of And
INR 30 crores (INR Thirty Crores (iii) The certificate issued by
Rupees) with scope of IT the CA of the Bidder
implementation projects/services (Annexure-12-Project
in India for Central/State Govt. Experience of the Bidder)

Page 136 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

Department/ Organization/ clearly specifying project
Autonomous body/ PSU/ Semi- name, Purchase
Govt. Organization/Local Order/workorder number
Body/Authority, or A Public Listed along with date of Work
Company in India (having average Order/Purchase Order, type
annual Turnover of Rs.500 Crore or of client, Project stage,
above)” during last five (05) financial which are meeting the
years & current financial year Relevant Project Experience
ending last day of month previous to criteria & status of
the one in which the tender is implementation etc.
invited. Note:
In cases where the
Note: performance of a
1. Relevant project/ work PO/contract, still under
experience criteria are to be met execution, is being
by any of the members of JV/ presented for consideration,
Consortium. such a performance shall
only be considered as
2. IT Implementation projects in under:
India for Central/State Govt. a) The satisfactory
Department/ Organization/ performance being
Autonomous body/ PSU/ Semi- presented is during the
Govt. Organization/Local period specified under the
Body/Authority that shall be criterion,
considered for the project and
experiences b) A performance certificate
is issued by the customer,
specifying the details of the
executed item/s, their
quantity & value/s and the
period of completion of such
items of the PO/contract.
Note: In case, the Bidder
has executed work orders/
Purchase Orders which are
meeting the Relevant project
experience requirement
specified in this item but is
unable to share the copy of
Work Order/Purchase Order
due to binding of Non-
Disclosure Agreement

Page 137 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

(NDA) signed with the
Purchaser. The Bidder shall
furnish the following
document:

a) The certificate issued by

the Company Secretary of
the Bidder clearly specifying
nature of work, components
& services
supplied/provided, date of
Work Order/Purchase Order,
value of items which are
meeting the Relevant
Project Experience criteria &
status of implementation etc.
AND

b) Either of below:

1) Performance Certificate of
the customer, giving
reference of PO No., date of
execution.
OR

2) Any other supporting

document issued by client of
execution of work for the
client clearly indicating
duration of execution and
value of Contract.

3) Project details shall be

submitted as per Annexure-
12-Project Experience of
the Bidder
4. Relevant The Bidder shall have successfully Relevant Project/work
Project/wor completed: experience**
k At least One (1) project of Supply, (i) Copies of PO or any other
experience Installation & Commissioning of associated documents
** minimum 800 Nos. of CCTV specifying details of Scope

Page 138 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

cameras in single project which of Work.
includes Integrated Command & And
Control Center, Data Center (ii) Completion
Infrastructure & applications certificate/performance
managed by Bidder. certificate/Go-Live
Certificate of such order by
OR Government/PSU/
Corporate.
At least two (2) projects of Supply, And
Installation & Commissioning of (iii) The certificate issued by
minimum 500 Nos. of CCTV the CA of the Bidder
cameras which includes Integrated (Annexure-12-Project
Command & Control Center, Data Experience of the Bidder)
Center Infrastructure & applications clearly specifying project
managed by Bidder. name, Purchase
Order/workorder number
OR along with date of Work
Order/Purchase Order, type
At least three (3) projects of Supply, of client, Project stage,
Installation & Commissioning of which are meeting the
minimum 400 Nos. of CCTV Relevant Project Experience
cameras which includes Integrated criteria & status of
Command & Control Center, Data implementation etc.
Center Infrastructure & applications Note:
managed by Bidder. In cases where the
performance of a
For a Central/State Govt. PO/contract, still under
Department/Organization/ execution, is being
Autonomous body/PSU/Semi-Govt. presented for consideration,
Organization/Local Body/Authority such a performance shall
or a Public Listed Company in India only be considered as
(having average annual Turnover of under:
Rs.500 Crore & above) during last
five (05) financial years & current a) The satisfactory
financial year ending last day of the performance being
month previous to the one in which presented is during the
the tender is invited period specified under the
criterion,
Note: Relevant project/ work and
experience criteria is to be met by
any of the members of JV/ b) A performance certificate
Consortium. is issued by the customer,

Page 139 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

specifying the details of the
executed item/s, their
quantity & value/s and the
period of completion of such
items of the PO/contract.
Note: In case of Non-
Disclosure Agreement
(NDA) signed with the
Purchaser. The Bidder shall
furnish the following
document:

a) The certificate issued by

the Company Secretary of
the Bidder clearly specifying
nature of work, components
& services
supplied/provided, date of
Work Order/Purchase Order,
value of items which are
meeting the Relevant
Project Experience criteria &
status of implementation etc.
AND
b) Either of below:
1) Performance Certificate of
the customer, giving
reference of PO No., date of
execution.
OR
2) Any other supporting
document issued by client of
execution of work for the
client clearly indicating
duration of execution and
value of Contract.
3) Project details shall be
submitted as per Annexure-
12-Project Experience of
the Bidder
5. OEM The Bidder shall be an original Authorization letter from
Undertakin equipment manufacturer (OEM) or OEM specific to this tender

Page 140 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

g an authorized representative of the as per sample Performa
respective OEMs. Whenever an given in Annexure-20-
authorized Agent/ Representative Undertaking from OEM For
submit bid on behalf of the OEM, Backend Support. The
the same agent/representative shall authorization shall include
not submit a bid on behalf of details of Tender No., Name
another OEM in the same tender for and address of the OEM and
the same item/product/services. MSI the Bidder authorized and
shall provide Authorization letter for details of the products /
all the products / services as per services (name and model
make & model offered in the bid in No.) for which the Bidder
the SoR. has been authorized. In
case OEM bids directly,
Note: Self-certification and
relevant supporting
1. Applicable to Cloud Service documents, ISO certificates
Provider & All Software etc., for being OEM to be
application OEMs provided.
2. To be issued in the name of
the Sole / Lead bidders name
6. Declaration The Bidder shall submit a self- Self-declaration as per
regarding declaration certificate declaring that Annexure-10-Declaration
blacklisting their firm is not banned/blacklisted of Non-Blacklisting is to be
by Central Govt./PSU/State Govt. as given by Bidder’s authorized
on the closing date of the tender signatory and such
(original/extended). declaration shall be attached
[Note: All members of the JV/ along with the bid.
Consortium have to give this
Declaration]
7. Quality Bidder shall possess the following Self-Attested copy of the
Certificatio certifications valid as of tender valid certificates (validity
ns closing date. periods that are active on
a) ISO 9001 the date of tender
b) ISO 27001:2013 submission (original/
c) ISO 20000 extended) by the authorised
d) CMMI Level 3 or higher signatory along with
Company seal.
Note:
• Lead Bidder must have ISO
9001 & ISO 27001:2013
certificates.
• Remaining certificates shall
be met by any of the

Page 141 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

members of JV/ Consortium.
8. Make in As per Section Termination of the Declaration/Certificate is to
India Contract CRIS reserves the right to be provided and shall be
cancel the contract placed on the attached along with the bid
Successful Bidder and forfeit the
as per Annexure-36- Local
Performance Security under the
following circumstances: Content as per Make in
The Selected Bidder commits a India Policy as applicable.
breach of any of the terms and
conditions of the contract.
CRIS may, without prejudice, to any
other remedy for breach of contract,
by written notice of default sent to
the vendor terminate the contract in
whole or part thereof if:
The vendor fails to deliver any or all
of the obligations within the time
period(s) specified in the contract, or
any extension thereof granted by
the client.
The vendor fails to perform any
other obligation(s) under the
contract.

In case of any change in the

statutory laws which shall prohibits
performance of this contract, CRIS
shall be within its rights to cancel
the contract and refund the
Performance Security.

Time is the essence of the

Agreement, and the delivery dates
are binding on the Implementation
Agency, hence if the successful
Bidder fails to operationalise the
project or is unable to meet the
milestones of the Phase 1 Go-Live
or Final Go-Live as per the timelines
prescribed in the bid document part-
II and the extension if any allowed.
CRIS reserves its right to cancel the
contract.
The MSIs ability to survive as an
independent corporate entity is
threatened or is lost owing to any
reason whatsoever, including inter-
alia the filing of any proceedings for

Page 142 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

bankruptcy, insolvency or winding
up against the MSI or an
appointment of receiver, liquidator,
assignee, or similar official against
or in relation to the MSI, any failure
by the MSI to pay any of its dues to
its creditors, the institution of any
winding up proceedings against the
MSI or the happening of any such
events that are adverse to the
commercial viability of the MSI.
a. If deductions on account of
penalties & liquidated
damages exceeds more than
the limits defined for the
liquidated damages in this bid
document part-II.
b. The MSI or its team has
failed to comply with or is in
breach or contravention of
any law of the land.
c. MSI is ordered to be wound
up by a court of law, except
for the purpose of
amalgamation or
reconstruction provided that,
as part of such amalgamation
or reconstruction, the
property, assets and
undertaking of MSI are
transferred to the
amalgamated or
reconstructed entity and that
the amalgamated or
reconstructed entity has
unconditionally assumed the
obligations of MSI under this
Agreement and provided that:
i. the amalgamated
or reconstructed
entity in the opinion
of the Purchaser
has the technical
capability and
operating
experience
necessary for the
performance of its

Page 143 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

obligations under
this contract; and
ii. the amalgamated
or reconstructed
entity has, in the
opinion of the
Purchaser, the
financial standing
to perform its
obligations under
this contract; and
iii. this Agreement
remains in full force
and effect;
9.2. Documentation
The bidder shall be responsible for
the creation / updation of documents
pertaining to various activities
outlined in the tender document,
including but not limited to the
requirement gathering phase,
design phase, development phase,
implementation phase, Proof-of-
concept, UAT, PAT, O&M phase,
trainings, multiple versions of SoPs,
and any other relevant
documentation required throughout
the contract period and providing
copies of the same to all
stakeholders. The bidder shall
ensure that version control
mechanisms are implemented and
maintained for each type of
document created.
Furthermore, all documents shall be
stored on a central repository
hosted on the same public cloud
platform. The central repository shall
be subject to Role-Based Access
Control (RBAC) measures to
manage and control access to the
documents.
The bidder shall be responsible for
maintaining these documents for the
entire duration of the contract
period. Upon completion or
termination of the contract, the
bidder shall ensure that all

Page 144 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

documents are handed over to
CRIS as part of the exit
management process.

Make In India of bid document.

Note: To be issued by the Sole /

Lead bidder.
9. Land As per Section Land Border with Self-Declaration is to be
Border India Compliance of the bid provided by the Bidder’s
Sharing document. authorized signatory and
shall be attached along with
the bid as per
Note: To be issued by the Sole / Annexure-26-Certificate
Lead bidder. Land Border with India
10. Availability The Bidder shall have project office The proof/willingness of the
of Project at New Delhi/NATIONAL CAPITAL same shall be submitted
Office in REGION or be willing to create the duly signed by the signatory
National required facility in NATIONAL authority as per Annexure-
Capital CAPITAL REGION within 30 days 28-Declaration for Project
Region. from date of issue of PO for the Office
entire duration of the contract.

Note: To be issued by the Sole /

Lead bidder
11. Valid In case, the Bidder is using any Self-Declaration (as per
License licensed software/tool for the said Annexure-29-Undertaking
Undertakin activity the Bidder shall submit the for Valid License for
g undertaking they have valid Software) is to be given by
Licenses/Subscriptions for all such Bidder’s authorized
software/tool. signatory and such
declaration shall be attached
Note: To be issued by the Sole / along with the bid
Lead bidders
12. Undertakin The Bidder shall ensure that the Self-Declaration (as per
g to be Intellectual Property Rights of Annexure-24-Undertaking
submitted Source Code of all Software from OEM for IPR) is to be
by Bidder supplied under this project must not given by Bidder’s authorized
Intellectual reside in any Country that shares a signatory and such
Property Land Border with India. declaration shall be attached
Rights [Note: All members of the JV/ along with the bid.
Consortium have to give this [Note: All members of the
Declaration] JV/ Consortium have to give

Page 145 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Parameter Qualifying Criteria Credentials to be provided

this Declaration]

13. Security Security auditing & testing of the 1. Proof of submission of

Certificatio offered CVMS system (VMS, ICCC application to STQC (if
n & FR Solution) has to be carried out certificate is not being
by STQC as per RDSO submitted along with the bid)
specifications for Security Audit/Testing of
RDSO/SPN/TC/106/2022, Ver 2.1 the offered CVMS System
with amendment No. 1 or latest. (VMS, ICCC & FR Solution)
as per RDSO specification
Bidder will be required to submit the No.
Certificate of Security Audit/Testing RDSO/SPN/TC/106/2022,
of the offered CVMS system (VMS, Ver.2.1 with amendment No.
ICCC & FR Solution) issued by 1 or latest
STQC along with the bid or submit 2. Test certificate/Security
proof, along with the bid, of verification certificate of the
submission of application to STQC offered CVMS System
for Security Audit/Testing of the (VMS, ICCC & FR Solution)
offered CVMS system (VMS, ICCC from STQC
& FR Solution)

Bidder has to ensure that Certificate

of security assurance requirements
of the offered CVMS System (VMS,
ICCC & FR Solution) issued by
STQC is made available to CRIS
within 45 days from closing date
(original /extended) of this tender.
The bidders who fail to provide this
Certificate from STQC within 45
days from the closing date (original/
extended) of this tender will be
summarily rejected and no
extension of time will be given on
any account.
Table 12:Qualification Criteria for MSI

*Financial Turnover of the Bidder as a Member in an earlier JV/ Consortium shall be

reckoned only to the extent of the concerned member’s share in that JV/ Consortium
for the purpose of satisfying his/ her compliance to this criterion in the tender under
consideration.

**Quantum of completed work done by the Bidder as a Member in an earlier JV/

Consortium shall be reckoned only to the extent of the concerned member's share in
that JV/ Consortium for the purpose of satisfying his/ her compliance to this criterion
in the tender under consideration.

Page 146 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# IT Implementation Project/Services that would be considered are as under:

i. Type 1: Projects in which the scope consists of design, implementation,
operations, and maintenance of a turnkey solution which includes software
applications (COTS OR BESPOKE), databases, Storage and Compute,
network and security completely hosted on the Public/Private Cloud. OR
ii. Type 2: Projects in which the scope consists of design, implementation,
operations, and maintenance of a turnkey solution for an on-premises
Data Center for IT solutions like IT hardware (Servers & Storage),
Software applications (COTS OR BESPOKE), databases, Network and
Security appliances (HW/Virtual). OR
iii. Type 3: Projects in which the scope consists of design, implementation,
operations, and maintenance of a turnkey solution which includes IT
hardware (Servers & Storage), Software applications (COTS OR
BESPOKE), databases, Network and Security appliances (HW/Virtual) in
Smart City Projects. OR
iv. Type 4: Projects in which the scope consists of design, implementation,
operations, and maintenance of a turnkey solution which includes IT
hardware (Servers & Storage), Software applications (COTS OR
BESPOKE), databases, Network and Security appliances (HW/Virtual) in
Safe City Projects.

9.2.1. Eligibility for Start-ups, MSEs and Government PSUs:

i. Eligibility for Start-ups: The start-ups recognized by the Department of
Industrial Policy and Promotion; Ministry of Commerce (GOI) are
exempted from submission of Earnest Money Deposit (EMD). However,
considering the criticality of the Project, start-ups are also required to meet
100% of the quantum of requirement against Parameters corresponding to
the “Financial Turnover of Bidder” mentioned in the Section Qualifications
Criteria under Section Master Service Integrators Qualifications. Also,
Start-ups are required to meet 100% of the quantum of requirement
against Parameters corresponding to “Relevant Project/ Work Experience”
mentioned in the Qualification Criteria.
ii. Eligibility for MSEs: MSEs registered under Udyam Registration are
exempted from submission of Earnest Money Deposit (EMD). However,
the registration certificate submitted by such MSEs must be valid as
on closing date of the tender. The conditions of “Financial Turnover of
bidder” for such MSEs are relaxed by 70% subject to meeting of quality
and technical specifications and “Relevant Project/ Work Experience”.
Accordingly, these MSEs are required to meet at least 30% of the
quantum of requirement against Parameters corresponding to “Financial

Page 147 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Turnover of Bidder” mentioned in the Qualification Criteria under Clause

3.3 above. No benefit will be available to traders under MSEs Order 2012.
iii. Eligibility for Government PSUs: Government PSUs who are the OEMs
for the Video Management System / Integrated Command and Control
Center application software, and PSUs owned by Ministry of Railways are
exempted from submission of Earnest Money Deposit (EMD).

CRIS reserves the right to verify the authenticity of the documents submitted by the
Bidder. Wherever certifications have been asked in the subject tender, including
technical specification/requirement, all the relevant certificate(s) shall be valid as of
the date of closing of the subject tender.
9.3. Cloud Service Providers (CSP) Qualification Criteria

Section
# /Type/ Details Supporting Document(s)
Category
Self-Attested copy of the
Data Centers facility shall be valid certificates [(validity
Regulatory located in India. Data Center periods that are active on the
(Tier shall conform to at least Tier III date of tender submission
1
conformance/ standard, certified under TIA (original/ extended)] by the
regulation) 942-B or Uptime Institute authorised signatory along
certifications. with Company seal from the
respective CSP.
CSP shall be empanelled with
MeitY and the CSP Cloud
Infrastructure should be STQC
Self-Attested copy of the
audited, and its validity should
valid certificates (validity
be valid as on the date of bid
periods that are active on the
closing, for providing cloud
MeitY date of tender submission
2 computing services to
Empanelment (original/ extended) by the
government departments /
authorised signatory along
PSUs. CSP shall also commit
with Company seal from the
to maintain its validity
respective CSP.
throughout the contract period
in case it is successful in
winning this contract.
CSP shall have minimum
Copy of Audited Balance
average annual turnover of at
Sheet / annual report for 3
Annual least ₹700 Crore in three
3 financial years and certificate
Turnover Financial Years i.e., 2022–
from CA of the respective
2023, 2021–2022 and 2020–
CSP.
2021.

Page 148 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Section
# /Type/ Details Supporting Document(s)
Category
CSP shall have accreditations
relevant to security, availability,
System and
confidentiality, processing
Organization Respective CSP shall provide
integrity, and/or privacy trust
4 Controls the 3rd party audited report
services principles.
(SOC) for the SOC certifications.
CSP shall be SOC1, SOC2 and
Certifications
SOC3 compliant for higher
security.
CSP shall offer the following
PaaS services-
Self-declaration from the
a. Managed Databases
Breadth of authorized signatory of the
b. Analytics
5 Platform CSP on their letter head or
c. AI/ML services
Services published compliance details
d. IoT service supporting
on CSP’s website.
IPv4 & IPv6 based
communication.
Self-Attested copy of the
The CSP must possess the
valid certificates [(validity
below valid certifications as on
periods that are active on the
last date of submission of this
date of tender submission
6 Certification bid.
(original/ extended)] by the
a. ISO 27001:2013,
authorized signatory along
b. ISO 9001,
with Company seal from the
c. ISO 20000
respective CSP.

This would include:

i. Bringing up new VMs in less
Computation
than 20 minutes
& Existing
ii. Ability of auto-scale Self-declaration letter to
Technical
iii. Shutting down VMs CRIS on the CSPs letter
7 capabilities of
iv. Setting up and configuring head stating compliance to
proposed
Load Balancers the mentioned parameters.
facilities by
v. Setting up of virtual networks
CSP
vi. Add/Shrink Storage
vii. Add/Modify security
controls.

Page 149 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Section
# /Type/ Details Supporting Document(s)
Category

CSP has to validate cloud

architecture proposed by the
CSP MSI and ensure to meet the
capability for required capacity of underlying Self-declaration letter to
maintaining infrastructure and the CRIS on the CSPs letter
8
the availability, scalability and head stating compliance to
underlying functional requirement as per the mentioned parameters.
infrastructure implementation timelines
mention in the bid document
Part-II.

All data must be kept within

India, and under no
circumstances should any data
be moved outside India. CRIS
mandates that the MSI furnish
an undertaking guaranteeing Self-declaration letter to
Data that the data generated from CRIS on the CSPs letter
9
Compliance the CVMS application which head stating compliance to
includes data at rest as well as the mentioned parameters.
data in transit, loaded on the
application, shall reside within
Indian boundaries and servers
located in Data Center facilities
in Indian Territory.
The CSP shall submit a self- Declaration regarding
declaration certificate declaring blacklisting to be submitted
that their firm is not as per Annexure-10-
Non-
10 banned/blacklisted by Central Declaration of Non-
blacklisting
Govt./PSU/State Govt. as on Blacklisting
the closing date of the tender from the authorised signatory
(original/extended). of respective CSP.
CSP shall have published on its
public facing website at least
following information for
transparent visibility- Self-declaration letter to
11 Portal Service Level Agreements CRIS on the CSPs letter
Features (SLAs) head stating compliance to
Dashboard live-status of cloud the mentioned parameters.
services’ health across data
centers and outage details (if
any)
Table 13:Qualification Criteria for CSP

Page 150 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

9.4. CCTV Surveillance OEM Qualification Criteria

i. All the technical criteria given in the table below are mandatory for
qualification. Bids not meeting these parameters of the technical
requirement may be summarily rejected.
ii. The Bidder must ensure that the validity of certificates asked under the
technical specification of the item quoted, if any, shall be valid on the date
of closing of the tender.
iii. Bids are liable to be considered only based on the documents/details
furnished with the bid. However, CRIS reserves the right to seek
clarifications from the Bidders wherever considered necessary.

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

Video i. The OEM of the VMS Solution shall (i) and (ii) The
Management have a minimum installation experience certificate issued by
Software of 10000 camera licenses in the CA (Annexure-13-
(VMS) Central/State Govt. Project Experience
Department/Organization/ Autonomous of the OEM) clearly
body/PSU/Semi-Govt. specifying Project
Organization/Local Body/Authority or a name, Purchase
Public Listed Company in India (having Order/workorder
average annual Turnover of Rs.500 number along with
Crore & above)” during last five (05) date of Work
financial years & current financial year Order/Purchase
ending last day of month previous to the Order, No. of VMS
one in which the tender is invited. license supplied, type
of client, which are
ii. The OEM of VMS Solution shall have meeting the Relevant
experience of implementation of at least Project Experience
one (1) video surveillance project of criteria.
minimum 2500 cameras license in
Central/State Govt. (iii) Undertaking by the
Department/Organization/ Autonomous respective OEM for
body/PSU/Semi-Govt. deployment on MeitY
Organization/Local Body/Authority or a empanelled cloud as
Public Listed Company in India (having per the Annexure-38-
average annual Turnover of Rs.500 MeitY empanelled
Crore & above)” during last five (05) Cloud.
financial years & current financial year

Page 151 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

ending last day of month previous to the (iv) Undertaking by the

one in which the tender is invited. respective OEMs for
OR VMS software to meet
The OEM of VMS Solution shall have scalable architecture
experience of implementation of two (2) as per the Annexure-
video surveillance projects each of 40- Integration of the
minimum 1500 cameras license in VMS with more than
Central/State Govt. One NVR
Department/Organization/ Autonomous
body/PSU/Semi-Govt. (v) Proof of having
Organization/Local Body/Authority or a technical support
Public Listed Company in India (having office in India as per
average annual Turnover of Rs.500 Annexure-37- OEMs
Crore & above)” during last five (05) Technical Support in
financial years & current financial year India
ending last day of month previous to the
one in which the tender is invited. (vi) Undertaking by the
OR respective OEMs as
The OEM of VMS Solution shall have per the Annexure-40-
experience of implementation of three Integration of the
(3) video surveillance projects each of VMS with more than
minimum 1200 cameras license in One NVR
Central/State Govt.
Department/Organization/ Autonomous (vii) Undertaking by
body/PSU/Semi-Govt. the respective OEM
Organization/Local Body/Authority or a complying to the
Public Listed Company in India (having Security Verification
average annual Turnover of Rs.500 Certification criteria as
Crore & above)” during last five (05) per Security
financial years & current financial year Verification
ending last day of month previous to the Certification
one in which the tender is invited.
(viii) Self-Declaration
regarding blacklisting
iii. The proposed product/solution from the
to be submitted as per
VMS OEM shall be cloud-enabled and
Annexure-10-
support MeitY empanelled cloud service
Declaration of Non-
provider platform to host the proposed
Blacklisting– All
solution stack.
Members of JV/
iv. The proposed product/solution from the
Consortium from the
VMS OEM shall have scalable

Page 152 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

architecture (Horizontal and vertical) to authorised signatory

cater minimum 7 Lakh+ cameras of respective OEM.
licenses in a single project.
v. The proposed VMS OEM shall have
technical support center in India directly
or through their authorized partner.
vi. The proposed product/solution from the
VMS OEM shall have integrated more
than one (1) M-NVR/NVR/VRU (system
software) of different make.
vii. Security Verification Certification - The
Video Management Software shall have
security features which can be
deployed meeting all the parameters
applicable to software for security,
vulnerabilities, etc. with relevant and
equivalent safeguards along with
“SAFE TO HOST CERTIFICATE” as
per the latest OWASP Top 10 from
STQC (Ministry of Electronics &
Information Technology) only for testing
and issuing the certificate / clearance.
viii. The OEM shall submit a self-declaration
certificate declaring that their firm is not
banned/blacklisted by Central
Govt./PSU/State Govt. as on the
closing date of the tender
(original/extended).
Integrated i. The ICCC OEM shall have minimum (i) The certificate
Command & installation experience of five (5) issued by the CA as
Control Center ICCC including surveillance projects per (Annexure-13-
(ICCC) in Central/State Govt. Project Experience
Department/Organization/ of the OEM) clearly
Autonomous body/PSU/Semi-Govt. specifying Project
Organization/Local Body/Authority or name, Purchase
a Public Listed Company in India Order/workorder
(having average annual Turnover of number along with
Rs.500 Crore & above)” during last date of Work
five (05) financial years & current Order/Purchase
financial year ending last day of Order, Details of the

Page 153 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

month previous to the one in which project where ICCC is

the tender is invited. supplied, type of
ii. The proposed ICCC solution shall be integrations, type of
cloud enabled and support MeitY client, which are
empanelled cloud service provider meeting the Relevant
platform to host the proposed solution Project Experience
stack. criteria.

iii. The proposed product/solution from

the ICCC OEM shall have integrated (ii) Undertaking by the
at least six (6) applications mentioned respective OEM for
below in one (1) project in deployment on MeitY
Central/State Govt. empanelled cloud as
Department/Organization/ per the Annexure-38-
Autonomous body/PSU/Semi-Govt. MeitY empanelled
Organization/Local Body/Authority or Cloud.
a Public Listed Company in India
(having average annual Turnover of (iii) Undertaking by the
Rs.500 Crore & above)” during last respective OEM for
five (05) financial years & current integration of ICCC
financial year ending last day of with the other
month previous to the one in which applications as per the
the tender is invited. Annexure-41-
a. IP CCTV cameras Integration of ICCC
b. Public cloud for video with other
streaming & storage applications.
c. M-NVR/NVR/VRU connected
on SIM/eSIM. (iv) Proof of having
d. Facial Recognition Solution technical support
e. Video Analytics office in India as per
(Edge/Central) Annexure-37- OEMs
f. GIS Maps Technical Support in
g. GPS or GPS enabled Mobile India
Application
h. Integration with different (v) Undertaking by the
application databases respective OEM
i. Panic Buttons / Emergency complying to the
Call Box Security Verification
j. IOT Sensors / NVR / VRU Certification criteria as
k. Public Address System / per Security

Page 154 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

Variable Messaging System Verification

l. Mobile application for video Certification
and data streaming
m. Body Worn Cameras (vi) Self-Declaration
regarding blacklisting
iv. The proposed ICCC OEM shall have to be submitted as per
technical support center in India Annexure-10-
directly or through their authorized Declaration of Non-
partner. Blacklisting– All
Members of JV/
v. Security Verification Certification- The Consortium from the
Integrated Command & Control authorised signatory
Software shall have security features of respective OEM.
which can be deployed meeting all
the parameters applicable to software
for security, vulnerabilities, etc. with
relevant and equivalent safeguards
along with “SAFE TO HOST
CERTIFICATE” as per the latest
OWASP Top 10 from STQC (Ministry
of Electronics & Information
Technology) only for testing and
issuing the certificate / clearance.
vi. The OEM shall submit a self-
declaration certificate declaring that
their firm is not banned/blacklisted by
Central Govt./PSU/State Govt. as on
the closing date of the tender
(original/extended).
Facial i. The Face Recognition Algorithm vendor (i) Latest NIST
Recognition shall have participated and have published report.
Solution established in the Face Recognition
Algorithm Evaluation conducted by (ii) Undertaking by the
NIST (National Institute of Standards respective OEM for
and Technology, U.S. Department of deployment on MeitY
Commerce) or from any Government empanelled cloud as
Test Labs authorized for it. The per the Annexure-38-
benchmark / latest performance FRVT MeitY empanelled
test results of current calendar year with Cloud.
respect to the closing date of tender

Page 155 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

(original/extended) or last 1 preceding

year, the performance efficiency of the
algorithm shall be within the top 25 (iii) Proof of having
ranked algorithms of the FRVT (1: N) technical support
test results with FNIR (N=1.6M, T=O, office in India as per
Rank=1). Annexure-37- OEMs
Technical Support in
ii. The proposed FR solution shall be India
cloud enabled from Day 1 and support
MeitY empanelled cloud service (iv) Undertaking by the
provider platform to host the proposed respective OEM
solution stack. complying to the
Security Verification
iii. The proposed FR OEM shall have Certification criteria as
technical support center in India directly per Security
or through his authorized partner. Verification
Certification.
iv. Security Verification Certification-
(v) Self-Declaration
The Facial Recognition Software shall regarding blacklisting
have security features which can be to be submitted as per
deployed meeting all the parameters Annexure-10-
applicable to software for security, Declaration of Non-
vulnerabilities, etc. with relevant and Blacklisting – All
equivalent safeguards along with Members of JV/
“SAFE TO HOST CERTIFICATE” as Consortium from the
per the latest OWASP Top 10 from authorised signatory
STQC (Ministry of Electronics & of respective OEM.
Information Technology) only for testing
and issuing the certificate / clearance.

v. The OEM shall submit a self-declaration

certificate declaring that their firm is not
banned/blacklisted by Central
Govt./PSU/State Govt. as on the
closing date of the tender
(original/extended).

Declaration The OEM shall submit a self-declaration Self-Declaration

regarding certificate declaring that their firm is not regarding blacklisting
blacklisting banned/blacklisted by Central Govt./PSU/State to be submitted as per
Govt. as on the closing date of the tender Annexure-10-

Page 156 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

(original/extended). Declaration of Non-

[Note: This clause is applicable for all OEMs
Blacklisting– All
providing software solutions such as but notMembers of JV/
limited to solutions like Video Summarization &
Consortium from the
Forensic Image Enhancement applications] authorised signatory
of respective OEM.
Table 14:CCTV Surveillance OEM Qualification Criteria

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

Enterprise i. The EMS OEM shall have minimum (i) & (ii) The certificate
Management installation experience of three (3) issued by the CA
System (EMS) projects of surveillance projects in the (Annexure-13-
last 5 years in Central/State Govt. Project Experience of
Department/Organization/ the OEM) clearly
Autonomous body/PSU/Semi-Govt. specifying Project
Organization/Local Body/Authority or name, Purchase
a Public Listed Company in India Order/workorder
(having average annual Turnover of number along with
Rs.500 Crore & above)” during last date of Work
five (05) financial years & current Order/Purchase
financial year ending last day of Order, Details of the
month previous to the one in which project where EMS is
the tender is invited. supplied, type of
ii. The OEM of EMS Solution shall have integrations, type of
been operational for at least one (1) client, which are
project of minimum 10000 nodes meeting the Relevant
licenses in Central/State Govt. Project Experience
Department/Organization/ criteria.
Autonomous body/PSU/Semi-Govt.
Organization/Local Body/Authority or (iii) Undertaking by the
a Public Listed Company in India respective OEM for
(having average annual Turnover of deployment on MeitY
Rs.500 Crore & above)” during last empanelled cloud as
five (05) financial years & current per the Annexure-38-
financial year ending last day of MeitY empanelled
month previous to the one in which Cloud.
the tender is invited.

Page 157 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

OR (iv) Proof of having

The OEM of EMS Solution shall have technical support
been operational for at least two (2) office in India as per
project each of minimum 6000 nodes Annexure-37- OEMs
licenses in Central/State Govt. Technical Support in
Department/Organization/ India
Autonomous body/PSU/Semi-Govt.
Organization/Local Body/Authority or (v) Self-Declaration
a Public Listed Company in India regarding blacklisting
(having average annual Turnover of to be submitted as per
Rs.500 Crore & above)” during last Annexure-10-
five (05) financial years & current Declaration of Non-
financial year ending last day of Blacklisting– All
month previous to the one in which Members of JV/
the tender is invited. Consortium from the
OR authorised signatory
The OEM of EMS Solution shall have of respective OEM.
been operational for at least three (3)
project each of minimum 5000 nodes
licenses in Central/State Govt.
Department/Organization/
Autonomous body/PSU/Semi-Govt.
Organization/Local Body/Authority or
a Public Listed Company in India
(having average annual Turnover of
Rs.500 Crore & above)” during last
five (05) financial years & current
financial year ending last day of
month previous to the one in which
the tender is invited.

iii. The proposed EMS solution shall be

cloud enabled and support MeitY
empanelled cloud service provider
platform to host the proposed solution
stack.

iv. The proposed EMS OEM shall have

technical support center in India
directly or through their authorized

Page 158 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Application Supporting
Minimum OEM Qualification Criteria
Type Documents

partner.

v. The OEM shall submit a self-

declaration certificate declaring that
their firm is not banned/blacklisted by
Central Govt./PSU/State Govt. as on
the closing date of the tender
(original/extended).
Table 15:EMS Qualification Criteria

9.5. Technical Evaluation Criteria

# Technical Evaluation Parameters Artifacts to be Provided

A. Project Understanding
Bidder to submit the technical solution document Write up as part of the
covering the following aspects: Technical Proposal. (Max
a) Level of understanding of the Scope of Work 15 pages)
and all aspects of this project
b) Solution proposed meets the functional
1.
requirements defined in the bid document.
c) Overall Project Implementation Approach
and how timelines can be met.
d) Vendor Management Plan
e) Risk Mitigation Plan /Strategy/SLA
Write up (Max 5 pages)
as well as Compliance to
the Requirements
2. Service Delivery approach (including helpdesk)
provided in the Tender
Document Part II for
Helpdesk
Write up (Max 2 to 3
3. Quality Assurance Plan & Methodology Pages) for the Proposed
Quality assurance plan
Write up (Max 2 to 3
4. Business Continuity Plan (BCP) Pages) for the Proposed
BCP.
B. Compliance to Functional Requirement
1. a) Video Management System Compliance to the

Page 159 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Technical Evaluation Parameters Artifacts to be Provided

b) Integrated Command and Control Center. Functional Requirement
c) Enterprise Management System Specifications as per the
d) Facial Recognition Solution Format provided in the
e) Video Summarization Tender document.
f) Forensic Application
g) Mobile application
h) Underline Infrastructure (Cloud Hosting
Platform)
C. Integration of Systems
Technical Write up (max
4 to 5 pages) detailing the
1. Integration of respective applications within CVMS approach and
methodology for
successful integration.
a. Technical Write up (max
4 to 5 pages) detailing
the approach and
methodology for
successful integration.
Integrations with the edge devices in Coaches, b. Provide Compliance to
2.
Locomotives, EMU & MEMU the Integration
parameters as provided
in Annexure-6-
Integration of the
Edge Devices
Parameters
a. Technical Write up
(max 4 to 5 pages)
detailing the approach
and methodology for
successful integration.
Integration with Indian Railways / CRIS
3. b. Provide Compliance to
applications
the Integration
parameters as
provided in Annexure-
4-Integration of the
Applications of CRIS
Technical Write up (max
4 to 5 pages) detailing the
4. Other Government applications approach and
methodology for
successful integration.

Page 160 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Technical Evaluation Parameters Artifacts to be Provided

D. Capacity Planning and Change Management
CVs of the Resources
being deployed as per
Certified resources for the proposed CVMS
1. format provided in
Solution and Cloud Hosting Platform
Annexure-14-CV of Key
Personnel Proposed
Write up (max 4 to 5
pages) detailing the
Approach Methodology for Capacity Planning and approach and
2.
Change Management methodology for Capacity
Planning and Change
Management
Bidders need to provide
the Unpriced bill of
Quantity with clearly
specifying the
Make/Model, quantities,
E. Unpriced Bill of Material etc as per format
provided in Annexure-15-
Undertaking for
Unpriced Bill of
Quantity of this tender
document.
Bidders need to provide
the proof of the OEM’s
authorisation

Annexure-19-Long Term
Maintenance Supportand
F. Product Support from OEM’s
Post implementation
support (as per
Annexure-37- OEMs
Technical Support in
India)

Compliance to Technical
Parameters for the CSP
Compliance to Technical Evaluation
G. as mentioned in Section
Parameters for the CSP
Technical Evaluation
Parameters for the CSP
Compliance to Technical
Compliance to Technical Use Cases listed
H. Use Cases listed under
under the Proof-of-Concept Plan
the PoC plan as per

Page 161 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Technical Evaluation Parameters Artifacts to be Provided

Section Proof of
Concept
Set of Documents
Submission of all the Undertakings and
I. provided in Annexure-7-
Certifications listed in the “Bidders checklist”
Bidder’s Checklist
J. Technical Presentation
Tech presentation shall include Project Technical Presentation
Understanding covering aspects: (Max Time allocation for
a) Level of understanding of the Scope of Work Presentation is 60
and all aspects of this project minutes) to Tender
b) Overall Project Implementation Approach Evaluation Committee
and how timelines can be met. followed by Q & A
c) Vendor Management Plan Session.
1.
d) Risk Mitigation Plan /Strategy/SLA
e) Solution proposed meets the functional
requirements defined in the bid document.
f) Dependencies on any third party or CRIS
g) Business Continuity Plan
h) Capacity Planning and Change
Management
Note: Bidders fulfilling all the parameters mentioned in the Technical Evaluation
Criteria above only shall be permitted to conduct the Proof-of-Concept.
Table 16:Technical Evaluation Criteria

9.6. Technical Evaluation Parameters for the CSP

The CSP shall also be able to meet the following requirements at the time of bid as
well as also to be available during project delivery period:

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
1. Cloud providers
shall offer
instances that
Compute instances – provide a baseline
Burstable performance level of CPU
performance with
the ability to burst
above the

Page 162 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
baseline.
2. Resize virtual cores, CSP shall provide
memory, storage GUI options to
seamlessly specify and modify
server
configuration
(CPU, memory,
storage)
parameters
seamlessly.
3. Provision multiple Cloud service must
concurrent instances offer self-service
provisioning of
multiple instances
concurrently either
through a
programmatic
interface (API/CLI)
or through a
management
console.
4. Auto Scaling support Cloud service shall
be able to
automatically
increase the
number of
instances during
demand spikes to
maintain
performance and
decrease capacity
during lulls to
reduce costs.
5. Backup Capability CSP shall have its
centralized backup
service to take
backup of various
resources
including compute,

Page 163 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
object storage and
block storage, DB.
The backup
service shall have
automated restore
testing facility for
periodic evaluation
of backup and it
restore point and
time.
6. Instance failure recovery Cloud service must
be architected in
such a way to
automatically
restart instances
on a healthy host if
the original
physical host fails.
7. Highly scalable, high- Cloud provider
performance container shall offer Its highly
management service scalable, high-
performance
container
management
service.
8. Network traffic logging - Log Cloud service shall
traffic flows at network support capturing
interfaces information about
the IP traffic going
to and from
network interfaces.
9. Auto-assigned public IP Cloud service shall
addresses be able to
automatically
assign a public IP
to the instances.
10. Subnets within private Customer shall be
network able to create one
or more subnets

Page 164 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
within private
network with a
single Classless
Inter-Domain
Routing (CIDR)
block.
11. Configure proxy server Cloud service shall
(NAT service instance) at support NAT
network level service instances
that can route
traffic from
internal-only
instances to the
Internet.
12. Multiple VPN Connections Cloud service shall
per Virtual Network support creating
multiple VPN
connections per
virtual network
13. Health checks - monitor the Cloud service shall
health and performance of support health
application checks to monitor
the health and
performance of
resources.
14. Encryption using provider Cloud service shall
managed keys support encryption
of data on
volumes, disk I/O,
and snapshots
using industry
standard AES-256
cryptographic
algorithm.
15. Encryption using customer Cloud service shall
managed keys support encryption
using customer
managed keys.
16. Content and streaming CSP shall have

Page 165 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
services media and content
related services
offering including
but not limited to
Content delivery
network, managed
video streaming
and media
transcoding
services
17. Highly available storage Cloud service shall
be highly available
object storage that
shall be
redundantly stored
across fault
domains on MeitY
empanelled
physically separate
multiple data
centers.
Additionally, object
storage shall
support versioning
and WORM
capability.
18. Managed relational Cloud provider
database service shall offer a
service that makes
it easy to set up,
operate, and scale
a relational
database in the
cloud all major
DBs including
MySQL,
PostgreSQL, SQL
server, Oracle and
MariaDB

Page 166 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
supporting
synchronous
replication and
automatic failover
19. Asynchronous replication Cloud service shall
with low latency across support
multiple data centers Asynchronous
replication of a
primary database
to a standby
replica in a
separate MeitY
empanelled data
center to provide
data redundancy,
eliminate I/O
freezes, and
minimize latency
spikes during
system backups.
20. Point in time restore Cloud service shall
support restoring a
DB instance to a
specific date and
time.
21. Encryption at rest Cloud service shall
support encryption
using the industry
standard AES-256
encryption
algorithm to
encrypt data.
22. Control access to your cloud Cloud provider
resources at a granular level shall offer fine-
grained access
controls including,
conditions like time
of the day,
originating IP

Page 167 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
address, use of
SSL certificates, or
authentication with
a multi-factor
authentication
device.
23. Utilize multi-factor Cloud service shall
authentication (OTP) when support multi-
accessing cloud resources factor
authentication.
MFA requires
users to prove
physical
possession of a
hardware or virtual
MFA device by
providing a valid
MFA code.
24. Audit of all action on keys Cloud service shall
support auditing
with features such
as what request
was made, the
source IP address
from which the
request was made,
who made the
request, when it
was made, and so
on.
25. Automatically records a Cloud service shall
resource’s configuration automatically
when it changes record a resource
configuration when
it changes and
make this
information
available.
26. Receive notification of a Cloud service shall

Page 168 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
configuration change notify every
configuration
change so
customers can
process these
notifications
programmatically.
27. Supported OS Cloud Service shall
provide natively
available images of
major OS types
including Windows,
Linux, Red hat
Linux, Ubuntu
28. Deployment Mechanism Cloud service shall
support various
deployment
mechanisms,
including a Git
repository, or an
integrated
development
environment (IDE)
such as Eclipse or
Visual Studio.
29. Support for SSL Cloud service shall
connections support SSL/TLS
connections and
certificates
30. 365-day service health Cloud provider
dashboard and SLA history shall offer 365
days’ worth of
publicly available
Service Health
Dashboard (SHD)
history.
31. Monitoring Tools Monitoring tools
that will enable
collection and

Page 169 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
tracking metrics,
collection, and
monitoring log
files, set alarms,
and automatically
react to changes in
the provisioned
resources. The
monitoring tools
shall be able to
monitor resources
such as compute
and other
resources to gain
system-wide
visibility into
resource
utilization,
application
performance, and
operational health.
Shall provide a
consolidated
automated report
of cloud usage
including real time
SLA reports
32. Governance and Able to define
Compliance 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

Page 170 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Specification Details Compliant Supporting

(Y/N) Document(s)
/Proof from
Public Links
on common best
practices or
custom rules (e.g.,
ensure Storage
volumes are
encrypted,
Compute instances
are properly
tagged, and IP
addresses are
attached to
instances) and
continuously
monitor
configuration
changes to the
cloud resources
and provides a
new dashboard to
track compliance
status.
33. Audit Logs Provide Audit Logs
of the account
activity to enable
security analysis,
resource change
tracking, and
compliance
auditing
Table 17:Technical Evaluation Parameter for CSP
10. Proof of Concept
Proof of concept (PoC) will be carried out at location specified by CRIS for Bidders
who will qualify all the above-mentioned parameters listed in Qualification Criteria,
Technical Qualification as prescribed in Section Qualifications Criteria of this
tender document. As a part of the bid evaluation process, it is mandatory for the
Bidder to clear the Proof-of-concept stage to become eligible for financial bid
opening. PoC testing will be conducted after submitting the bid and it shall be

Page 171 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

completed within 15 days after intimation of the same by CRIS to the Bidder(s).
Bidder to demonstrate the solution as per the schedule given by CRIS.

If the Bidder is not able to complete the PoC in the first attempt, then the Bidder shall
be given one more opportunity to complete PoC within seven (07) days after the
failure of the first PoC attempt. No further opportunity shall be given to the Bidder
after the second attempt for all components except FR Solution (for which third
attempt of 7 days shall be given.

10.1. Approach for Proof of Concept (PoC)

i. PoC shall be conducted at the site decided & allocated by CRIS.
ii. Bidder is required to furnish or provide all required hardware, application,
firmware, network, hosting environment, etc. with valid licenses to
demonstrate all requirements of this PoC.
iii. Bidder is required to bring and install edge devices at designated locations
(to be decided by CRIS) during PoC.
iv. CRIS reserves the right to provide additional M-NVR/NVR/VRU for the
PoC required to be integrated by the Bidder during the PoC.
v. These devices/applications are as follows:
a. Edge Devices*
• Eight numbers of IP Dome/Wedge Camera (4 Camera per
VRU/M-NVR & NVR) **.
• One number of VRU/M-NVR (minimum 8 channel) ***.
• One number of NVR (minimum 12 channels) ***.
• Two numbers of Panic buttons.
• Two numbers of Microphones.
b. PoC viewing Environment*.
• Three numbers of workstations each with 3 monitors
▪ Workstation 1 – ICCC User
▪ Workstation 2 – ICCC Supervisor and/or Power User
▪ Workstation 3 – Operator/RPF/GRP User
• One LED display of a minimum of 43” Inches connected to the
workstation.
• 1 Mobile Phone (Android/iOS).
• Tablet (Android/iOS)
• One device, whether it's a mobile phone or tablet, should run on
Android, while the other should operate on iOS.
• FR database of at least 10,000 faces to help validate the
accuracy of the system.

c. Applications (with required sizing during PoC on Cloud)

Page 172 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

• Video Management System (with required licenses for PoC

setup).
• ICCC application (with a minimum of three desktop users and
two mobile/tablet users licenses).
• Enterprise Management System (with required licenses for PoC
setup).
• Video Summarization Software (with two live streams and two
recorded stream licenses).
• Facial Recognition System (with required licenses for PoC
setup).

Note: -
* It is mandatory to arrange edge devices and PoC environment, however, it
will not be part of the evaluation.
**The IP cameras shall be of at least two different makes.
*** The VRU/M-NVR & NVR shall be of different makes. The system software
of VRU/M-NVR/NVR and that of the offered Video Management Software
shall be of different makes.

vi. At the time of PoC, the bidder needs to ensure that the proposed ICCC
application, video management system and enterprise management
system shall be demonstrated as an integrated solution.
vii. The Bidder must ensure that the products, software, and cloud
environment should be of the same make & model/version as quoted in
the bid submitted against this tender.
viii. At the time of PoC, the Bidder must ensure the availability of required
manpower from both the Bidder and respective OEMs.
ix. The bidders shall conduct the Proof of Concept (PoC) by using the offered
Coaches and Locomotives. These Coaches and Locomotives shall be
provided by CRIS. The rail routes and areas for operation shall be
determined through consultation with the CRIS. The Coaches &
Locomotives offered for the PoC for the demonstration, shall be a
accompanied by two observers from CRIS to witness the PoC. The POC
shall be conducted by the bidder at no additional cost to CRIS.
x. The bidder shall provide with an undertaking (Refer to Section Annexure-
27-Declaration for Proof of Concept) before showcasing the capabilities.

Page 173 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

10.2. Proof of Concept Workflow and Use Case

10.2.1. Basic ICCC Setup and Configuration
Acceptance Criteria Complianc Remark
S. Method for Testing
Parameter e Status s
No during PoC
(Yes/No)
Basic System ICCC systems to ICCC systems shall
Capacity show it’s following show the following
capacity: - License Support
a. Maximum Client details through
License Support datasheet or
i. Desktop Client application software:
ii. Mobile Client -
b. No of Users can a. Client
be added. Licenses/Subsc
riptions
i. Desktop
Concurrent
1. Users– 2000
nos.
ii. Mobile
Concurrent
Users – 2000
nos.
b. No of Named
users can be
added.
i. Desktop –
300000 nos.
ii. Mobile –
300000 nos.
Video Management Video Management
System to show it’s System shall show
following capacity: - following Camera /
a. Minimum No. of Chanel Support
Cameras/Chanel details through
supported by datasheet or
2.
application. application software:
b. Minimum No. of -
Cameras/Chanel a. Minimum
supported by Cameras/Chan
each M- el supported by
NVR/NVR/VRU. application –

Page 174 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

S. Method for Testing
Parameter e Status s
No during PoC
(Yes/No)
c. Minimum No. of 7Lakh+ nos.
M- b. Minimum
NVR/NVR/VRU Cameras/Chan
supported by el supported by
application each M-NVR
software. /VRU – 8 nos.
c. Minimum
Cameras/Chan
el supported by
each NVR– 12
nos.
d. Minimum No.
of M-
NVR/NVR/VRU
supported by
application
software –
1,00,000 nos.
Facial Recognition Facial Recognition
Solution to show it’s Solution to shall
following capabilities: show following
- camera and user
a. Minimum No. of license Support
Cameras/Chanel details through
supported by datasheet or
application. application software:
b. Minimum No. of -
Users supported a. Minimum No.
by application. of
3.
Cameras/Chan
el supported by
application –
231176 nos.
b. Minimum load
of 100 new
faces per hour
per coach.
c. Minimum of
User supported
by application

Page 175 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

S. Method for Testing
Parameter e Status s
No during PoC
(Yes/No)
as per Section
Schedule of
Requirement
(SOR)
Enterprise Enterprise
Management System Management
to the following System shall show
capabilities: following VRU/M-
a. Minimum No. of NVR & NVR Chanel
VRU/M-NVR & Support details
NVR supported through datasheet
4.
by application. or application
software: -
a. Minimum No. of
VRU/M-NVR &
NVR supported
by application –
82,000 nos.
Video Summarization Video
System to show it’s Summarization
following capacity: - System to shall
a. Minimum No. of show following
Live / Recorded camera and user
video cameras license Support
supported by details through
application datasheet or
Concurrently - application software:
i. Live Camera -
video a. Minimum No.
5.
ii. Recorded of Live /
Camera video Recorded
b. Minimum of User video channel
supported by supported by
application. application
concurrently -
i. Live /
Recorded
video from
2400
cameras.

Page 176 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

S. Method for Testing
Parameter e Status s
No during PoC
(Yes/No)

b. Minimum of
User supported
by application
as per Section
Schedule of
Requirement
(SOR)
6. User Creation, Bidder must define Successful User
Role definition below user roles with Creation
different functionality with limited access
access: - rights to
a. ICCC User functionalities as
b. ICCC Supervisor mentioned in
and/or Power User subsequent Section
c. Field of PoC and same
Operator/RPF/GR users are logged on
P User different workstation
as follows: -
a. ICCC Operator
on workstation
1
b. ICCC
Supervisor /
power user on
workstation 2
c. Field Operator
(at RPF/GRP
thana desktop
or Mobile
Application) on
workstation 3
7. Setup of Bidder must create Bidder to
Standard Standard Operating demonstrate
Operating procedure for use creation of minimum
Procedure case as mentioned in 2
Section Standard
Operating
Procedures (SOPs)

Page 177 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

S. Method for Testing
Parameter e Status s
No during PoC
(Yes/No)
8. Bidder must Successful
demonstrate sample demonstration of
SOP creation along application of rule
with use of Rule engine and creation
Engine showing of SOP using
following activity of different types of
Section Standard activity as
Operating mentioned.
Procedures (SOPs)
of this tender: -
a. Manual Activity.
b. Automation
Activity.
c. If-Then-Else
Activity.
d. SOP Activity.
9. User Bidder must Successful
Dashboards showcase live running demonstration of
dashboards for live Dashboard as
different types of mentioned.
alerts, incident and
users (ICCC
Operator, ICCC
Supervisor and/or
power user and
Field User) as
described in Section
Dashboard of this
tender document.
Bidder must
demonstrate the
following: -
a. Total Alerts
Generated and
location (M-
NVR/NVR/VRU)
wise along with
True & False
categorization.
b. Incident closed

Page 178 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

S. Method for Testing
Parameter e Status s
No during PoC
(Yes/No)
versus incident
open (with
percentage of
open alerts).
10. Report generation Report shall be
from the dashboard. available.
Table 18: ICCC PoC Use Cases
10.2.2. Incident Management and Workflow
Acceptance Criteria Complianc Remark
Method for Testing
S. No Parameter e Status s
during PoC
(Yes/No)
1. Incident Generation of Alert generated and
Generation
Incident (Automatic can be viewed at
/ Manual) from field ICCC application
components in the software as
following condition: mentioned.
-
a. Automatic
Incident (High
Priority)
Generation
i. Pressing of
Panic Button
in coaches.
ii. Camera
Tamper alert
on blocking
camera field
of
view/camera
tampering.
iii. Device
Health
related alerts
b. Manual
Incident
Generation
Use Case Workflow and Functionality Demonstration user-wise.

Page 179 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

Method for Testing
S. No Parameter e Status s
during PoC
(Yes/No)
2. ICCC The following shall
Operator be achieved: -
a. Receipt of a. Alarm / Alert
a. Automati Alarm / Alert. visible on either
c Incident b. Viewing of pre of following: -
generatio & post 30 i. Alarm / Alert
n seconds window /
bookmarked pane.
video ii. GIS Map.
recording of iii. Pop-up
alert. window
c. Live viewing b. Viewing of pre
and recording & post 30
playback of seconds of
camera video bookmarked
feed (if video recording
required). from alert.
d. Alert type c. Live viewing
definition as and recorded
true or false. video playback
e. Alert Criticality from Video
level definition/ management
change. window / pane.
f. Automatic d. Alert type is
Incident visible as True
creation or False.
g. Incident Type e. Alert criticality
Definition level changed
h. Assignment to against alert.
field operator. f. Incident created
i. Automatic is visible in
notification to Incident
field operator Management
and ICCC window/pane.
supervisor g. Incident type is
through ICCC visible against
application, incident.
SMS/e-mail. h. Assignee / Field
Operator name
available

Page 180 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

Method for Testing
S. No Parameter e Status s
during PoC
(Yes/No)
against incident.
i. Redirecting
Critical
incidents to the
supervisor/pow
er user.
ICCC a. Live viewing Following shall be
Operator and recording achieved: -
b. Automati playback of a. Live viewing
c Incident camera video and recorded
generatio feed (if video playback
n required). from Video
b. Identification management
of Critical window / pane.
activity. b. Not to be
(Manual checked as it is
activity). manual activity.
c. Bookmarking c. Bookmarked
of video. video is visible.
d. Manual d. Incident created
Incident is visible in
creation Incident
e. Incident Type Management
Definition window / pane.
f. Assignment to e. Incident type is
field operator. visible against
g. Automatic incident.
notification to f. Assignee / Field
field operator Operator name
and ICCC available
supervisor against incident.
through ICCC g. Notification sent
application, successfully.
SMS/e-mail.
3. ICCC a. Incident Following shall be
Supervisor viewing and achieved: -
severity a. Changed
change of Severity of
Incident (if Incident is
required). visible against

Page 181 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

Method for Testing
S. No Parameter e Status s
during PoC
(Yes/No)
b. Attaching incident.
supporting b. Required
videos, attachments is
document, visible against
URL to Incident and
incident. can be viewed
c. Re- individually by
assignment of operators.
Incident to c. Assignee / Field
different Field Operator new
Operator (if name available
required). against incident.
d. Escalation of d. Escalation of
Incident (in Incident is to
case of breach next level and
in SOP can be visible
timelines or against
severity Incident.
change of e. Response of
Incident). Field operator is
e. Checking visible against
response of incident and
Field Operator can be edited.
f. Final closure f. Closed status of
of Incident. Incident is
g. Sending visible against
notification to incident as well
all stake as on reports.
holders g. Case closure
through ICCC notification
application, received by
SMS / e-mail. various
h. Report viewing stakeholders.
and analysis of h. Incident
Incident(s). Response
Report viewed
and
downloaded.
4. Field User a. Acknowledge Following shall be
ment of achieved: -

Page 182 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

Method for Testing
S. No Parameter e Status s
during PoC
(Yes/No)
Incident. a. Acknowledged
b. Viewing of status received
Incident videos to ICCC
and On operator and
demand live Supervisor.
video view, b. Incident video
recording can be seen.
video On demand live
playback. camera viewing
c. Forwarding of and recording
incident to playback.
First c. Incident
Responder / forwarded to
field inspection First
operator on Responder.
Mobile d. Video recording
Application. exported in
d. Export of Tamper proof
recorded video format with its
in Tamper video player.
Proof format (if e. Response of
required). First Responder
e. Receipt of is received and
response from can be viewed
First against incident.
Responder / f. Attached
field inspection evidence is
operator visible against
(Mobile incident.
Application) g. Correction /
f. Attaching Editing in
evidence (if response of
any). First Responder
g. Correction / is visible
Addition of/to against
response/com Incident.
ments from h. Completed
field inspection Status is visible
Operator on against
the Incident. Incident.

Page 183 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remark

Method for Testing
S. No Parameter e Status s
during PoC
(Yes/No)
h. Mark
completion /
closure of
incident.
5. First Following shall be
Responder achieved: -
(Mobile User) a. Incident
/ Field Acknowledgem
Inspection ent available at
Operator a. Receipt and field operator
Acknowledge window.
ment of b. Pre & Post 30s
Incident video of
b. Viewing of Incident is
alert video and viewed, or other
other attachment of
attachments to incident is
incident. checked.
c. Fill field c. Field response
response to is visible in
Incident. Field Operator
d. Attach window.
evidence (if d. Attached
any). evidence is
e. Submission of visible in Field
field response. Operator
window.
e. Submission
alert received
by Field
Operator.
Table 19:Incident Management and Workflow PoC Use Cases

10.2.3. Facial Recognition Use case

The bidder shall ensure the facial recognition solution works on both.
• Live video feeds (IP cameras)
• Recorded video feeds (minimum of 5 minutes) from IP cameras, Body-worn
cameras, and mobile handset cameras.

Page 184 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

• Cropped images received from M-NVR/NVR/VRU (minimum of 200).

• Reference images up to 15 years old

The FR solution shall be deployed on a cloud environment and shall be integrated

with the Integrated Command & Control Center application.

Method for Compliance

Acceptance
S. No Parameter Testing Status Remarks
Criteria
during PoC (Yes/No)
a. Configura
tion of
multiple
watchlists FR System
(at least 2 shall allow
watchlists users to
of a create
1. Watchlist different
minimum
watch lists
of 20
for different
users)
use cases.
• Blackli
st
• Whitel
ist
a. Detection a. The
of faces Facial
in the live recognitio
video n solution
feed shall
b. Face detect
Matching and
of a match
person face of a
Detection & with b. Lady
2. matching of
partially wearing
Faces
hidden or burkha
occluded c. A man
faces like wearing a
wearing cap.
dark d. A person
glasses wearing a
and mask.
masks. e. A person
c. Recogniti with

Page 185 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

on of eyeglass
watch- es.
listed f. A person
face wearing
(whiteliste scarf
d or g. A person
blackliste changing
d) its face
d. Matching expressio
of face in n.
low light h. A person
condition with only
s a side
profile
i. A person
with
various
gestures
in front
view/profil
e
FR solution
shall provide
alerts with an
Accuracy
accuracy of
with
3. at least 95%
Mask/face
accuracy
cover
(true
alerts/total
alerts).
For people
Recognition
wearing
Accuracy
masks the
accuracy of
provided
Accuracy alerts shall
4.
without mask be at least
99 %
accuracy
(true
alerts/total
alerts).
FR solution Search/filter/
Search shall allow sort based
5.
Capability the user to on:
search or a. Name,

Page 186 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

filter. b. Date,
c. Range
and
d. Criminal
ID/Numb
er
The interface
shall be Matching
configured face
for users as responses
Web
6. defined in shall be
Interface
Section shown on
Approach for web-based
Proof of applications
Concept.
a. The user
shall be
allowed
to record
7.
The FR a face
Solution shall from the
have Android applicatio
and iOS n.
Mobile
Mobile
Application
Applications b. Users
for Facial shall
Recognition receive
Purposes. all the
8. alerts in
the
mobile
applicatio
n.
Type of
FR Solution
alarms:
shall allow
a. Event
the user to
alerts
9. Notification receive
b. Health
notifications
Alerts
of the
c. Audit log
alarms.
alerts
FR shall
allow users
to share the
Alerts via
10. Integration Email
email
Exchange
SMTP
services

Page 187 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

The FRS
system shall
have android
and mobile
application
for facial
11. Mobile App recognition
purpose.
API shall be
provided for
third-party
app
integration.
Table 20: Facial Recognition PoC Use Cases

10.2.4. Video Summarization

Acceptance Criteria Complianc Remarks
S. Method for Testing
Parameter e Status
No during PoC
(Yes/No)
1. Summarizatio System shall be Two hours of
n of Video able to provide Video summarized
video in less than 2
Summarization for 2 minutes and can
hrs. video in less be viewed and
than 2 mins with exported.
selected objects
highlighted, using
functionalities
mentioned in
Section Video
Summarization of
this tender.
2. Indicative Object Search: the Application able to
Object Search ability to search filter:
through a video a. Filter all men
following wearing blue
parameters: shirts passing
a. Filter all men through the
wearing blue requested time
shirts passing slot.
from a coach b. List of men
from 11 am to wearing a blue
3 pm. shirt and a cap

Page 188 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remarks

S. Method for Testing
Parameter e Status
No during PoC
(Yes/No)
b. Filtering a man c. Filtering all
with a blue women passing
shirt wearing a through the
cap. coach wearing
c. A woman pink attire.
wearing pink
attire moving
from one
vestibule to
other.
Table 21:Video Summarization Use Cases

10.2.5. User Management

Tests to be Acceptance Compliance Remarks
S.
Parameter demonstrated Criteria Status
No
during PoC (Yes/No)
1. User a. Field user Following shall
Management requests to be achieved: -
transfer the a. Evidential
evidential video videos of the
and requests the event
first level requested.
approval from b. Two-stage
the supervisor. authorization
b. The ICCC for obtaining
operator shall evidence for
provide the analysis.
video clip post c. Configuratio
the approval n and
from the demonstratio
supervisor. n of the
approval
matrix.
Table 22: User Management Use Cases

Page 189 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

10.2.6. Enterprise Management System

Tests to be Acceptance Compliance Remarks
S.
Parameter demonstrated Criteria Status
No
during PoC (Yes/No)
3. Enterprise a. Monitoring of the a. Health
Management health parameters
System parameters of of the Edge
the Field Edge Devices
Devices b. Automated
b. Integration generation
between the of the
ITSM tool and trouble ticket
the Monitoring with details
module of the of the
EMS and device, the
Automated change in
Generation of the state of
the Trouble the device.
ticket for the c. Configuratio
Edge device n of the SLA
which has provided by
changed status. CRIS and
c. Configuration of automated
the SLA and calculation
automated of the
Penalty Penalty.
calculation d. Configuratio
d. Configuration of n and
the Escalation demonstratio
Matrix n of the
automated Escalation
generation of Matrix
email.
Table 23: Enterprise Management System Use Cases

10.2.7. Low Bandwidth (Data Handling Management)

Acceptance Criteria Complianc Remarks
S. Method for Testing
Parameter e Status
No during PoC
(Yes/No)

Page 190 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Acceptance Criteria Complianc Remarks

S. Method for Testing
Parameter e Status
No during PoC
(Yes/No)
1. Auto fallback a. Live video of
a. The video shall
of Live video camera shall be
remain
to lower video continuous thecontinuous as
resolution session and per available
shall degrade to
network
lower video bandwidth with
resolution. variable
b. Once network is
resolution/bit
re-connected rate, appropriate
after getting data packet
disconnection at
segmentation or
NVR end any other
system shall alternate
show live video
mechanism.
without b. Automatic live
reopening of viewing and
particular improvement in
camera resolution once
the connectivity
improves
2. Recorded a. Video Recording a. Video shall be
video shall be synced seamlessly
synchronisatio once the synced with
n. network NVR (without
connectivity any duplication
from NVR is or loss of the
available. video)
b. Video fetched b. The video
from the M- doesn’t start
NVR/ NVR/ VRU downloading
shall start from from the start in
the exact point case there is
from there the connectivity loss
recording was with the M-NVR
missed. / NVR / VRU
Table 24:Low Bandwidth (Data Handling Management) Use Cases

Page 191 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

10.2.8. Cloud Hosting Environment

1. Provision the required cloud infrastructure resources in the public MeitY cloud
environment, ensuring compliance with all regulatory and security standards.

2. Integrate the edge devices with the cloud-hosted surveillance solution to

demonstrate end-to-end functionality.

3. Conduct thorough testing and validation of the use cases for demonstration
during the PoC to ensure alignment with CRIS's functional and performance
expectations.

By focusing on above mentioned key use cases, the bidder can effectively
demonstrate the capabilities of the surveillance solution hosted in the public MeitY
cloud environment, highlighting its scalability, security, and performance benefits.

S. Parameter Method for Testing Acceptance Complian Remar

N during PoC Criteria ce Status ks
o (Yes/No)

1. Creation of Self-Provisioning MSI shall log

cloud (VMs of different in and
hosting configurations, demonstrate
environme Storage of the capability
nt for PoC different IOPS, on the
Use-Case etc.) in logically offered
demonstrat isolated cloud. CRIS
ion environment in will evaluate
line with CVMS the
solution use-cases capabilities
mentioned above. on a live
demo on
MSI’s
proposed
cloud.

Page 192 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Parameter Method for Testing Acceptance Complian Remar

N during PoC Criteria ce Status ks
o (Yes/No)

2. Auto Auto scaling to

scaling in 5X of compute Compute Use
compute resources in Case:
real-time • Deploy
without human virtual
intervention: machines
Evaluate on (VMs) or
ability to auto- containers to
scale; ease of host the
configuring the Video
auto-scaling Management
rules, System,
parameters for ICCC
configuring application,
auto-scaling Video
(e.g., Summarizati
min/max/para on Software,
meters on and Facial
which Recognition
threshold Solution.
levels can be • Demonstrate
set/wait time), the
availability of scalability of
multiple auto- compute
scaling resources by
scenarios (e.g., dynamically
based on adjusting the
threshold number of
levels, VMs or
scheduled, containers
recurring). based on
workload
demands.
• Showcase
the ability to
handle
multiple
concurrent
video

Page 193 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Parameter Method for Testing Acceptance Complian Remar

N during PoC Criteria ce Status ks
o (Yes/No)

streams and
processing
tasks
efficiently.

3. Storage Create a 1 TB storage

Tiering and and then extend the Storage Use Case:
autoscaling storage by 10 times in • Utilize cloud
real-time without the storage
human intervention services to
with storage lifecycle store video
configuration to footage,
segregate frequent, application
Infrequent and data, and
Archival data on the system logs.
basis of defined • Showcase
parameter. data
redundancy
and high
availability
features of
cloud
storage to
ensure data
integrity and
availability.
• Demonstrate
seamless
integration
between
storage and
compute
resources for

Page 194 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Parameter Method for Testing Acceptance Complian Remar

N during PoC Criteria ce Status ks
o (Yes/No)

efficient data
processing.
• Demonstratio
n of data
movement
among
Frequent,
Infrequent,
archival on
the basis of
data access.

4 Network Create Virtual Network

Segmentati Network, subnets, Use Cases:
on and network • Configure
connectivity between virtual
edge device and networks,
CVMS solution subnets, and
hosted in Cloud security
environment groups to
isolate and
secure traffic
between
different
components
of the
surveillance
solution.
• Showcase
low-latency
network
connectivity
between
edge
devices,
cloud-hosted
applications,
and end-user
devices.

Page 195 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Parameter Method for Testing Acceptance Complian Remar

N during PoC Criteria ce Status ks
o (Yes/No)

• Implement
traffic
monitoring
and analysis
tools to
ensure
optimal
network
performance
and security.

5 Security Evaluation of security

features features from the Cloud Security
from the CSP to support Use Case:
CSP to security of the • Implement
support application and data Identity and
security of in the cloud. Security Access
the against attacks like Management
application DoS / DDOS, DNS (IAM)
s and data attacks. Perimeter policies to
in the security and control
cloud. availability of features access to
such as Multi-factor cloud
authentication (OTP), resources
Identity & Access based on
Management, Private roles and
Subnets, Data permissions.
Encryption. • Configure
encryption at
rest and in
transit to
protect
sensitive
data stored
in the cloud.
• Implement
network
security
measures

Page 196 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Parameter Method for Testing Acceptance Complian Remar

N during PoC Criteria ce Status ks
o (Yes/No)

such as
firewalls,
intrusion
detection/pre
vention
systems, and
DDoS
protection to
safeguard
against cyber
threats.
• Showcase
continuous
monitoring
and auditing
capabilities
to detect and
respond to
security
incidents in
real-time.

6 Monitoring Dashboard to monitor

Dashboard the cloud services like Monitoring Use
VM/Containers, Case:
Storage, and security • Deploy
services etc. monitoring
and
observability
tools to track
the
performance,
availability,
and health of
cloud
infrastructure
,
applications,
and edge

Page 197 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Parameter Method for Testing Acceptance Complian Remar

N during PoC Criteria ce Status ks
o (Yes/No)

devices.
• Showcase
dashboards
providing
real-time
insights into
resource
utilization,
application
performance
metrics, and
security
events.
• Implement
automated
alerting and
remediation
workflows to
proactively
address
performance
issues and
security
threats.

Table 25:Cloud Hosting PoC Use Cases

11. Project Management Tool (PMT)
As described in the Scope of Work of the bid document, the complete CVMS solution
is being hosted on the Public Cloud and the commercial model specified is on a pay-
per-use model. Further, there are interdependencies with external parties/ other
initiatives of CRIS/IR as specified in Annexure-1- Other CRIS Bid Documents.
Hence, it is very pertinent that the MSI shall use every measure necessary to ensure
that there is absolute control and visibility over the project and its status.

In addition to the SoR line items, the MSI shall also provide a comprehensive Project
Management Tool for entire duration of the contract to ensure thorough monitoring of
project scope delivery, timeline, cost utilization, and optimal resource usage etc.,

Page 198 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

without any additional financial implication to CRIS. The Project Management tool
shall:

i. Deploy a project monitoring tool and capture the project tasks into smaller,
manageable tasks using a Work Breakdown Structure. Define milestones
and set deadlines for each phase of the project.
ii. Input all tasks and milestones into the project monitoring tool and regularly
update progress, completion percentages, and any issues or roadblocks.
iii. Access to the PMT shall be available to all the CRIS/Indian Railways
stakeholders (up to 200 users) for regular review and management.
iv. The PMT should be available to access CRIS/Indian Railways
stakeholders for the project until the final Go-Live is declared by CRIS.
v. The data from the PMT shall be available in an offline mode for the entire
period of the contract.
vi. In addition to the Project Management Tool, the bidders shall also provide
FinOps, or Cloud Financial Management solution to achieve the following
functions and controls:
a. Ensure that there is complete visibility into cloud costs associated with
the Central Video Management System.
b. Ensure that the necessary cloud provider tools to track and analyze
costs are deployed to have complete visibility of the utilization of the
consumption in a real-time basis.
c. Optimize resource utilization on a continuous basis to minimize costs
while meeting performance and functional requirements.
d. Design the Central Video Management System architecture with cost
optimization in mind by considering factors like data storage options,
instance types, and network traffic patterns to minimize costs without
compromising performance.
e. Continuously monitor cloud costs and performance metrics to identify
optimization opportunities.
f. Implement automated alerts and policies to detect and remediate cost
inefficiencies in real-time.
g. Wherever required, the Session timeouts for the inactive users should
be configured for the different systems and applications. The sessions
timeouts should be configured for a minimum of 15 minutes per user.
h. Measures like misuse of user credentials should be avoided including
but not limited to the simultaneous use of the same credentials by
different users to avoid abnormal increase of concurrent users.
i. Implement governance policies and processes for meeting cost
optimization goals by implementing approval workflows for resources
and keep operations costs within the identified budgets.
j. Facilitate PM tool interface (web/mobile) not only to the MSI but also
to the CRIS/IR resources as specified.

Page 199 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

k. Conduct regular reviews of FinOps with continuous monitoring to

manage project finances, assess its utilization, identify any probable
cases of over or underutilization (beyond user configured thresholds)
for better operational control & planning.
l. The FinOps or Cloud Financial Management solution should be
available for the entire period of the Contract of the MSI.
m. The FinOps or Cloud Financial Management solution shall ensure that
during any point in the project, the resources which have been
deployed for the CVMS solution shall not exceed the quantities
mentioned in the Schedule of Requirement (SOR).
n. CRIS is not liable to pay for any component of the CVMS solution
beyond the quantities mentioned in the Schedule of Requirement
(SOR)

12. Project Implementation Timelines

i. Here “D” Stands for the date of the Purchase Order
ii. “D1” stands for the Date of the Final Go-Live.
iii. All deliverables shared by the MSI shall be validated by respective OEMs.

Milestone Estimated
Activity Indicative Deliverable*
Name Timelines
M1 Issuance of Purchase Order to D • Purchase Order to
the Successful Bidder MSI issued by CRIS
M2.a Project Inception Phase D+2 • Inception Report as
• Project Kick-Off and Team Weeks detailed in Inception
Mobilization Phase
• Submission, discussion & • Project Plan using
finalisation of the overall the Project
project plan Management Tool
M2.b Requirement gathering & D+2 • Functional
Design Phase Weeks Requirement
Submission, discussion and Specification (FRS)
finalisation of: document certified
i. Technical Architectures by respective OEMs
ii. Functional Requirement of the solutions
Specifications, • System Requirement
iii. Software Requirement Specification
Specifications, document (SRS)
iv. Low Level Design, certified by
Integration Design (Intra-CVMS, respective OEMs of
Edge Devices, Railways/CRIS the solutions

Page 200 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Milestone Estimated
Activity Indicative Deliverable*
Name Timelines
and Other Government • Complete design
applications & databases) as per architecture
the bid document’s Scope of including:
Work for all respective systems a. Low level design
and applications of CVMS. document
b. Cloud
architecture
(includes server
sizing, detailed
BOQ)
• Integration design
documentation with
specifications
mentioning the
methodology to be
used for integration
(Intra-CVMS, Edge
Devices,
Railways/CRIS and
other Government
applications &
databases) and proof
of proposed
integration methods
used in previous
projects (If available)
M2.c Provisioning of the Cloud D+3 • Copy of Email from
Infrastructure weeks the CSP along with
the MSI’s covering
letter stating the
details of the Cloud
infrastructure
provisioned.
M3 Installation, Configuration, and D+5 • Installation Report
deployment (including web, weeks for all production
mobile application, as systems and
applicable): applications as
• Integrated Command & identified in
Control Center (ICCC) milestone M3 as per
including mobile application. ANNEXURE-43-

Page 201 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Milestone Estimated
Activity Indicative Deliverable*
Name Timelines
• Video Management System Certificate for I&C
(VMS) and Annual Audits.
• Enterprise Management • Certification from
System (including Helpdesk OEM about
& Ticketing) installation &
• Facial Recognition Solution commissioning of
(FR Solution) respective
• Video Summarization production
• Forensic application for application as per
Image & Video enhancement OEM
• Creation of Production and recommendation/
test environments for all the guideline/ industry
applications. leading practices as
• Project Management Tool per ANNEXURE-43-
• Intra-CVMS integration Certificate for I&C
and Annual Audits.
• Self-declaration for
setting up the Test
Environment for
each of the
application modules
as per Annexure-44-
Setting up of the
Test Environment.
M4 Prototype Testing Phase D+8 • Prototype Testing
• Integration with edge devices Weeks1 Report
as per Section Integration
with Edge Devices Note – 1:
• Field testing based on
a. This milestone shall
Sample Size (10 nos.
be considered
Coaches, Locomotives, EMU
completed if the MSI
/ MEMU Installations with
is able to complete
respective edge devices)
the integration with
• Support for Security Audit for
minimum one (1) or
the Prototype infrastructure
actual numbers
offered to the bidder
for integration of the
OEMs (M-
NVR/NVR/VRU) by
CRIS as per defined

Page 202 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Milestone Estimated
Activity Indicative Deliverable*
Name Timelines
SLA
b. The prototype testing
shall be conducted
for each type of edge
equipment as and
when (throughout the
contract period), as
notified by CRIS and
shall be completed
as per the defined
SLA
M5 Integration with Indian D + 11 • Application
Railways, CRIS and other Weeks2 deployment and
Government applications configuration report
• Integration with applications as per the respective
proposed as per the scope of FRS and SRS
work in the bid document. document
• SOPs for incident Note - 2:
management as finalized a. Primary
during requirement gathering applications (as
phase by CRIS & IR defined in Section
Tentative List of
Applications)
which are
required to make
the CVMS
operational.
b. Any additional
applications
provided by CRIS
to the MSI for
integration shall
be completed by
the MSI as per
defined SLA
request for such
Integration.
M6 Develop & configure user D+11 to • Compliance Report
interfaces, SOPs, reports & D+56 by MSI and approval
dashboards as per interface by CRIS

Page 203 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Milestone Estimated
Activity Indicative Deliverable*
Name Timelines
design and parameters agreed • SoPs to be
with CRIS/IR (as and when implemented in
available), EMS configuration ICCC
including SLA monitoring of the
CVMS as well as edge devices,
ticketing etc. as per EMS
functional requirement

Note: The development of user

interfaces, SOPs, Reports &
Dashboards shall be
continuously refined &
customized during the entire
period of the contract and
should not be considered as part
of the Change Management.
M7 User Acceptance Testing D + 13 • User Acceptance
(UAT) for Phase 1 weeks Testing (including
User Acceptance Testing (UAT) performance & load
for Phase I systems and testing) for Phase-1
applications including user with no pending
dashboards as finalized during critical pendency’s.
requirement gathering phase by
CRIS & IR

M8 Capacity Building D+11 to • Training material

• Trainings (including 56 Weeks (with online
manuals) to identified users repository)
• Help/user manuals • Attendance report
• As-Built design documents • As-Built design
documents
M9 Security Audit- VAPT of the D + 16 • VAPT report
Complete CVMS solution hosted Weeks (including closure of
on the Public Cloud. To be snags /
conducted by the MSI. vulnerabilities
highlighted in the
VAPT report)
M10 Phase 1 Go-Live D + 16 • Phase 1 Go-Live
Phase 1 Go-Live (For 10,000 Weeks certificate by CRIS
nos. of cameras mentioned in

Page 204 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Milestone Estimated
Activity Indicative Deliverable*
Name Timelines
the line items 1.1, 1.2, 1.3 & 1.5 Note:
in Section Schedule of
• If the quantity of
Requirement (SOR) as per
10,000 Cameras is
CRIS requirement.
not achieved due to
delays from CRIS,
Includes two (2) weeks of
CRIS may decide to
stabilisation period.
declare the Phase 1
Go-Live with
Note: All milestones prior to M9
deployment of less
should be completed before
than 10,000
declaration of Phase 1 Go-Live.
Cameras with
corresponding
reduction in the
minimum assured
quantity of the
cameras.
• On completion of
one month from the
date of Phase 1 Go-
Live, the minimum
assured payments
as mentioned in the
Section Payment
Terms shall be
released by CRIS.
• CRIS reserve the
right to exclude the
FR solution in the
Phase-1 Go-Live
M11 On-boarding for remaining edge D +16 to • Compliance Report
devices as and when installed 56 Weeks (including
and made operationalised by the integration,
MSI. performance & load
testing) by MSI and
approval by CRIS.
Note: MSI to configure
and commissioned the
cameras as notified by
CRIS and shall be
completed as per the

Page 205 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Milestone Estimated
Activity Indicative Deliverable*
Name Timelines
defined SLA
M12 Security Audit Compliance & D+56 • Security Audit
Project Commissioning: Weeks Acceptance Report
Before issue of Project with no deviation /
commissioning Certificate (On vulnerabilities and
Completion of the milestones Commissioning
M1 to M10), CRIS shall arrange certificate by CRIS
the security audit of CVMS
system as per Clause 3.10 of
the RDSO specification no.
RDSO/SPN/TC/106/2022 Ver.
2.1 read with latest
amendment.

MSI has to provide necessary

documentation & support, carry
out necessary compliances for
the discrepancies / deviations /
vulnerabilities / breaches etc.
identified during the course of
audit/ security clearances and
extend all the requisite support
to successfully complete the
audit/security clearance
activities without any additional
cost to the Railways/CRIS.

And

Final Go-Live shall be issued by

CRIS after completion of all
above milestones.

M13 Project Go-Live (Final) D+56 • Final Go-Live

Weeks Completion
Certificate by CRIS
M14 Operations Phase (Post 8 Years • SLA and
Project Phase 1 Go-Live) Performance
Comprehensive Maintenance of Monitoring (monthly)
the CVMS solutions (After the
final security Audit acceptance

Page 206 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Milestone Estimated
Activity Indicative Deliverable*
Name Timelines
report from STQC and Final Go-
Live of the respective phase)
v. Operation and Maintenance
of applications
vi. SLA and Performance
Monitoring
vii. Logging, tracking and
resolution of issues.
viii. Application enhancement
ix. Patch Updates
Helpdesk services
Table 26:Project Implementation Timelines

* The content and its respective detailing of all the deliverable documents shall be
finalised in consultation and approval by CRIS. All the documents shall be available
in an online repository provided by the MSI with role-based access.

Page 207 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

13. Responsibility Matrix

A broad-level responsibility assignment matrix is given below, where all key activities
are mentioned. Each activity is mapped out every task, milestone or key decision
involved in hosting an application successfully on a cloud environment. Further, it also
covers which roles are Responsible for each action item, which personnel are
Accountable, and, where appropriate, who needs to be Consulted or Informed.
i. CRIS: Customer who has floated the bid document.
ii. MSI: Selected MSI through the bid document.
iii. Field SI System: Integrators to provide the solution at the Field Level.

[R]esponsible: This part oversees completing the task.

[A]ccountable: This party endorses the result of the task.
[C]onsulted: This party needs to be asked for feedback, and feedback needs to be
considered.
[I]nformed: This party needs to be kept up to date with the progress of the plan
development.

Note: N/A refers Not Applicable

# Activity to be performed CRIS MSI Field SI

1 Signing of the Contract R,A R, A I

2 Detailed assessment of the business and IT C R, A I
solution requirement for existing components
and ongoing CCTV projects in Indian railways.
3 Submission of Project Plan C R, A I
4 Submission of the detailed technical C,R R,A C,I
architecture of the CVMS solution in
consultation with all stakeholders
5 Technical training sessions of all systems and C, R R, A N/A
applications of complete CVMS solution to
CRIS Tech Team.
6 Submission of Functional Requirement C R, A I
specification, Software Requirement
specification, HLD, and LLD, as per the bid
document Scope of work for all respective
systems and applications of CVMS.
7 Sizing of ICT Infrastructure and software C R, A C,I
Licenses/Subscriptions for CVMS solution in

Page 208 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Activity to be performed CRIS MSI Field SI

consultation with all stakeholders.

8 Planning for configuration of infrastructure C R, A I

resources including compute, network such as
IP Schema, VLAN Schema, storage, backup
procedures, redundancy, and security zones

9 Provisioning, Configuration, Management and C R, A A,C,I

integration of complete CVMS solution with
field edge devices.
10 Integration of the Intra-CVMS applications, the C R,A N/A
CRIS & Indian Railway applications and the
other Government applications
11 Managed services of cloud infrastructure C R, A I
provisioned to host complete CVMS solution.
12 Management and monitoring (Up-Down status C R, A A,I
and utilization of resources) of complete CVMS
solution systems and applications.
13 Provisioning and management of backup C, I R, A N/A
services as per bid document.
14 Integration of CVMS system with CRIS existing A,C, I R, A I
systems and applications & other applications
including ongoing CCTV projects in Indian
Railways
15 Manage the retention period of event data & C, I R, A N/A
logs as mentioned in the bid document
16 Regular monitoring of backup success, failures C R, A I
and their restoration as per the bid document
17 Provisioning, management, and administration C,I R, A I
for all security services as per the bid
document
18 Implementation and audit of security policies C,I R, A C,I
for CVMS solution
19 Provisioning, enforcement and review of User C, I R, A N/A
Access Management including their roles and
responsibility for all users, groups, and
stakeholders.

Page 209 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Activity to be performed CRIS MSI Field SI

20 Security incident monitoring, management and C, I R, A I

reporting
21 Vulnerability assessment, and penetration C, I R, A I
testing (VAPT) as per the bid document.
22 Perform root-cause analysis on CVMS C, I R, A I
solution-related problems and implement or
recommend effective solutions to prevent their
recurrence as appropriate
23 Unit testing of all respective systems and C, I R, A I
applications of CVMS
24 Load and performance testing of complete C, I R, A I
CVMS solution
25 Planning, Suggesting, and Submitting the C, I R, A C,I
System up-grade plan(s) of CVMS solution as
per the bid document
26 Bi-annual security audit of the CVMS solution C, I R, A C,I
stack hosted on the public cloud
27 Annual security audit as per the RDSO R, A C,I C,I
specifications and guidelines
Table 27:Responsibility Matrix

14. Service Levels

14.1. Service Levels Agreement
Service Level Agreement (SLA) shall become the part of Agreement between CRIS and
the MSI. SLA defines the timely delivery of the deliverables and the correctness of the
same based on the agreed Performance Indicators as detailed in the bid document’s
scope. The MSI must comply with Service Level requirements to ensure adherence to
the Project timelines, quality, functional requirements, and availability of services.

The purpose of this Service Level Agreement (hereinafter referred to as SLA) is to

clearly define the level of services which shall be provided by the MSI to the Authority
for the duration of this Agreement.

Page 210 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

14.2. Measurement of SLA

The SLA metrics provided specify performance parameters such as baseline
performance, lower performance, and breach. All SLA calculations will be done every
month. The SLA also specifies the penalties for lower performance and breach
conditions.

CRIS shall also have the right to conduct, either itself or through any other third-party
entity, an audit/revision of the SLA parameters. The SLAs defined shall be reviewed by
the CRIS on a periodic basis after consulting the MSI, Project Management Consultants
and other experts. All the changes would be made by the CRIS after consultation with
the MSI and might include some corrections to reduce undue relaxation in Service
levels or some corrections to avoid unrealistic imposition of penalties, which are noticed
after the project has gone live.

14.3. Measurements & Targets

14.3.1. Definitions
i. "Uptime" shall mean the period for which the specified services/ systems and
applications with specified technical and service standards are available to
the users. Uptime, in percentage, of any systems and applications shall be
calculated as follows:
Uptime = {1- [Downtime / (Total Time – Maintenance Time)]} * 100
ii. “Downtime” shall be considered as per the service window defined above
and the net impact on operations concerning the time of incident receipt
(helpdesk call/ receipt of alarm generated by management system) – except
during the maintenance window to the extent of impact allowed in Change
Request.
iii. “Incident” refers to any event/abnormalities in the functioning of the CVMS /
specified services that may lead to disruption in normal operations of the
services of CVMS.
iv. “Helpdesk Support" shall mean the center that handles Fault reporting,
monitoring the CVMS, Ticket Management, and related enquiries during this
contract on a 24x7x365 basis.
v. “Response time” is defined as the time between receipt of the incident
(helpdesk call/ receipt of alarm generated by Enterprise Monitoring System)
and when a support team member starts working/attending the incident.
vi. “Resolution Time” shall mean the time taken between the reporting of the
incident/service request/problem at the helpdesk and resolution or escalation
(to the next level or concerned vendor) and reporting back to the end user.

Page 211 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

vii. “Service Window” shall mean the duration for which the services of the
CVMS shall be available. Service window in this case shall be calculated over
a 24x7x365 basis.
viii. “Business Hours” is defined as 24 X 7 X 365 days.
ix. “Root Cause Analysis” is a systematic process used to identify the
underlying cause of problem or incidents causing an unplanned downtime.
x. “Planned downtime” shall mean the downtime which is a pre-defined period
of non-availability of the CVMS services. Service levels and the relevant
penalties are not applicable and are exempted during the Planned
Downtimes.
xi. Planned downtimes shall be pre-approved by CRIS and a cumulative duration
of four (4) hours per quarter shall be permitted either in a single instance or
through multiple instances.
xii. Any planned downtime beyond the cumulative period of four (4) hours in a
quarter shall be considered as “Downtime” as explained above and the
respective penalties as per the severity shall be applicable.
xiii. Permission for planned downtimes must be obtained with a minimum notice
of 7 calendar days in advance.
xiv. If an incident with the highest severity reoccurs within two hours of the
resolution, downtime will be calculated from the time of the first occurrence.
xv. 100% of the calls must be attended to within the stipulated response time.
This shall be measured monthly.
xvi. All SLAs will be measured on a calendar month basis (single/multiple
instances as cumulative) with applicable penalties.
xvii. All reports shall be system-generated.

14.3.2. Service Level Agreement (SLA) – Pre-Phase 1 Go-Live

Penalties applied during the Pre-Phase 1 Go-Live Phase of the Project shall be
deducted from the first bill submitted by the MSI.

Measurement
S. Service Level
Source & Target Level Penalties
No. Objective
Methodology
A. Environment Setup
Setup of Cloud Source: Email Within 3
Environment from CSP Weeks from ₹ 1,00,000/- for each week’s
1.
e.g., Account the signing of delay or part thereof.
creation & Methodology: the contract

Page 212 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Measurement
S. Service Level
Source & Target Level Penalties
No. Objective
Methodology
Basic Infra copy of email
setup for CVMS confirming
solution account
creation along
with
credentials

a. Penalty of ₹2,00,000/- for

delay beyond first week
Phase 1 - Go-
live of CVMS b. Delay beyond second
Source:
solution as D + 3 months (2nd) week: Penalty of ₹
Phase 1 Go-
defined in 3,00,000/- or part thereof
Live
2. Section ‘D’ is the Date
Completion
Payment of signing of
Certificate
Terms, the contract c. Delay beyond fourth (4)
from CRIS
Deliverables & week: Penalty of
Timelines ₹4,00,000/- for each
week’s delay or part
thereof.
B. Integration Services
a. No penalty for integration
Source:
within allowed period of
Monitoring at
Integration of three weeks.
CVMS
CVMS with M- Within 3 b. Penalty of ₹2,00,000/- for
application or
NVR/NVR/VRU weeks of delay of up to one week
Report from
for Coaches, notification by after allowed period.
EMS Tool
Locomotives, CRIS c. Additional Penalty of ₹
1. EMUs & regarding the 3,00,000/- for delay more
Methodology:
MEMUs the availability of than one week and up to
Integration of
first time with the respective two weeks after allowed
CVMS
every OEM of interface for period.
solutions with
the M- integration d. Additional Penalty of
respective
NVR/NVR/VRU. ₹4,00,000/- per week for
OEMs M-
delay more than two
NVR/NVR/VRU
weeks or part thereof

Page 213 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Measurement
S. Service Level
Source & Target Level Penalties
No. Objective
Methodology
after allowed period.
(The above penalties shall
be calculated separately
for each OEM of the M-
NVR/NVR/VRU for which
the integration has been
delayed)
a. No penalty for integration
within allowed period of
One weeks.
Integration of b. Penalty of ₹5,000/- per
CVMS with M-NVR/NVR/VRU for
each Source: delay of up to one week
Subsequent M- Monitoring at after allowed period.
NVR, NVR & CVMS Allowed time is c. Additional Penalty of ₹
VRU for application or within 1 week 7,000/- per M-
Coaches, Report from of notification NVR/NVR/VRU for delay
Locomotives, EMS Tool by CRIS more than one week and
EMUs & regarding the up to two weeks after
2.
MEMUs after Methodology: availability of allowed period.
the first-time Integration of the respective d. Additional Penalty of
integration has CVMS M-NVR, NVR, ₹10,000/- per M-
been solutions with VRU for NVR/NVR/VRU per week
successfully respective integration for delay more than two
completed OEMs M-NVR, weeks or part thereof
with NVR, VRU after allowed period.
respective (The above penalties
OEM. shall be applicable only
for the delayed
Quantities of the M-
NVR/NVR/VRU)
Source: Within 4 a. No penalty for integration
Execution of Weeks of within allowed period of
Primary CRIS /
test cases as notification by four weeks.
3. IR applications
per integration CRIS b. Penalty of ₹1,00,000/- for
& databases
requirements regarding the delay of up to one week
availability of after allowed period.

Page 214 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Measurement
S. Service Level
Source & Target Level Penalties
No. Objective
Methodology
Methodology: the respective c. Additional Penalty of ₹
Integration with interface for 1,50,000/- for delay more
respective integration than one week and up to
applications & two weeks after allowed
databases period.
d. Additional Penalty of
₹2,00,000/- per week for
delay more than two
weeks or part thereof
after allowed period.
(The above penalties shall
be calculated separately
for each application /
database for which the
integration has been
delayed)
a. Penalty of ₹1,00,000/- for
delay beyond first week
b. Delay beyond second
Source:
(2nd) week: Penalty of
Monitoring at
Within 6 ₹1,50,000/- or part
CVMS
Weeks of thereof
Secondary application &
notification by c. Delay beyond fourth (4)
CRIS / IR/ Report from
CRIS week: Penalty of
Other EMS Tool
4. regarding the ₹2,00,000/- for each
Government
availability of week’s delay or part
applications & Methodology:
the respective thereof.
databases Integration with
interface for (The above penalties shall
respective
integration be calculated separately
applications &
for each application /
databases
database for which the
integration has been
delayed)

5. Availability of Manpower during the Implementation Phase

Page 215 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Measurement
S. Service Level
Source & Target Level Penalties
No. Objective
Methodology
Source: No absence. a. No penalty for 100%
Monthly attendance
attendance Refer to b. Absence of manpower
sheet Section will attract a penalty of ₹
Annexure-23- 5000 per day for each
Deployment
Methodology: resource.
of Manpower
Daily
Absence of for detailed
attendance for
6. Project requirements.
all resources
Manager collated in a
template as in
Annexure-35-
Template for
Monthly
Attendance
signed by MSI
& CRIS
Source: No absence. a. No penalty for 100%
Monthly attendance
attendance Refer to b. Absence of manpower
sheet Section will attract a penalty of
Annexure-23- INR 3000 per day for
Deployment
Methodology: each resource.
of Manpower
Absence of Daily
for detailed
Surveillance attendance for
7. requirements.
Solution SME all resources
Or Architect collated in a
template as in
Annexure-35-
Template for
Monthly
Attendance
signed by MSI
& CRIS
Source: No absence. a. No penalty for 100%
Absence of Monthly attendance
Cloud Solution attendance Refer to b. Absence of manpower
8.
SME Or sheet Section will attract a penalty of ₹
Architect Annexure-23- 3000 per day for each
Deployment
Methodology: resource.

Page 216 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Measurement
S. Service Level
Source & Target Level Penalties
No. Objective
Methodology
Daily of Manpower
attendance for for detailed
all resources requirements.
collated in a
template as in
Annexure-35-
Template for
Monthly
Attendance
signed by MSI
& CRIS
Source: No absence. a. No penalty for 100%
Monthly attendance
attendance Refer to b. Absence of manpower
sheet Section will attract a penalty of ₹
Annexure-23- 3000 per day for each
Deployment
Methodology: resource.
of Manpower
Absence of Daily
for detailed
Commissioning attendance for
9. requirements.
Engineer all resources
(Cloud) collated in a
template as in
Annexure-35-
Template for
Monthly
Attendance
signed by MSI
& CRIS
Change in Source: For every a. Penalty of INR 1,00,000
Manpower Monthly Change in for each change in
(applicable only Attendance allocated manpower if changed
for the Key Sheet Manpower within one year of
Resources within a period allocation to the Project.
deployed for Methodology: of one year
10. the project Allocated from the date
implementation manpower of allocation to
phase) should be the project
present in the
role for a
minimum
period of 1

Page 217 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Measurement
S. Service Level
Source & Target Level Penalties
No. Objective
Methodology
Year.

Please refer to
section
Manpower to
be deployed
for the Project
for the details
of the Key
Resources.
Table 28:Service Level Agreement (SLA)-Pre- Phase 1 Go-Live

14.3.3. Service Level Agreement (SLA) – Post Phase 1 Go-Live

All Service levels shall be calculated on a monthly basis and based on the availabilities,
the Penalties shall be calculated.
S. Service Level Measurement Source & Target/Service
Penalty
No. Objective Methodology Level
A. Overall Uptime

1.VMS Solution Source: System-generated Uptime for the For availability

Uptime report from EMS tool VMS solution >= 99% or higher -
(including all 99.9% a. < 99.9% &
services such Methodology: >= 99.5%:
as streaming, Uptime = [1 – {(VMS Penalty of
recording, DB, application and services total INR
administration) downtime - VMS application 3,00,000/-
and services planned b. < 99.5% &
Note: This downtime) / (VMS application >= 99.0%:
penalty shall and services total time)} *100] Penalty of
not be INR
applicable for a Total Time shall be measured 5,00,000/-
period of 60 on a 24x7 basis.
days from the ‘Downtime’ shall be measured For availability
date of Phase 1 from the time the application below 99% -
Go-Live become un-available to the Penalty @ INR
(Milestone – time it becomes fully available 8,00,000/- for
M9). (measured monthly) every 2% (or

Page 218 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
part thereof)
reduction of
availability
below 100%.

2.Other CVMS Source: System-generated Uptime for each For availability

applications report from EMS tool/ Call logs of the CVMS 99% or higher -
(excluding VMS solutions >= a. < 99.9% &
& EMS Uptime) Methodology: 99.9% >= 99.5%:
Uptime = [1 – {(Respective Penalty of
CVMS application total INR 50,000/-
• ICCC downtime – Respective CVMS b. < 99.5% &
• Mobile application planned downtime) / >= 99.0%:
interface (Respective CVMS application Penalty of
• FR Total Time)} *100] INR 75,000/-
• Video
Summarization Total Time shall be measured For availability
• Image & on a 24x7 basis. below 99% -
Video Downtime shall be measured Penalty @ INR
Enhancement from the time each application 1,00,000/- for
• Patch becomes unavailable to the every 2% (or
Managemen time it becomes fully available part thereof)
t interface (measured monthly) reduction of
(refer to availability
Section Note: SLA and penalties shall below 100%.
Patch be calculated separately on
Manageme each respective CVMS
nt) applications

Page 219 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
3.EMS Solution Source: Logs/automated Uptime for the For availability
Uptime scripts/Cloud based Monitoring EMS solution >= 99% or higher -
(including all Service. 99.9% c. < 99.9% &
services such >= 99.5%:
as Network Methodology: Penalty of
Monitoring, Uptime = [1 – {(EMS INR
Server application and services total 3,00,000/-
Monitoring, downtime – EMS application & d. < 99.5% &
Reporting, Services planned downtime) / >= 99.0%:
Dashboards, (EMS application and services Penalty of
Patch total time)} *100] INR
Management, 5,00,000/-
Helpdesk & Total Time shall be measured
Ticketing, on a 24x7 basis. For availability
Configuration ‘Downtime’ shall be measured below 99% -
Management, from the time the EMS become Penalty @ INR
Database un-available to the time it 8,00,000/- for
Monitoring, becomes fully available every 2% (or
Application (measured monthly) part thereof)
Monitoring) reduction of
availability
below 100%.
4.Alert/notification Source: EMS Report Uptime shall be For availability
Services better than 99% or higher -
Methodology: 99.9% a. < 99.9% &
(SMS, Email, Uptime %= [Total Uptime / >= 99.5%:
other user (Total Uptime + Total Downtime Penalty of
interface over )] x 100 INR
web or mobile 1,00,000/-
and any other b. < 99.5% &
integrations >= 99.0%:
with CRIS, Penalty of
Indian Railways INR
and other 1,50,000/-
Government
applications For availability
and services as below 99% -
identified) Penalty @ INR

Page 220 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
2,00,000/- for
Note: For each every 2% (or
service part thereof)
reduction of
availability
below 100%.
B. Backup & restore:

1. Configuration Source: Daily Report from the The success rate Per day INR
Backup (as backup automation system shall be better 10,000 of non-
specified in which is configured to execute than 99% for all availability of
Section the backups as per the the systems & daily backup
Backup established CRIS backup and subsystems
Solution) of policy. of the CVMS
each of the solution both
Systems & Methodology: virtual and
Subsystems of Success Rate (%) = physical.
the CVMS (Total Number of
solution. Successful backups / Total
Number of backup events) x
100

2. Accuracy of the Source: Daily Report from the The success rate Penalty of INR
backup backup automation system shall be 100% 10,000 for each
process, which is configured to execute for all the missing file in
ensuring 100% the daily backup
the backups as per the backups for the
contents of the
target source established CRIS backup CVMS data.
are copied to policy.
the backup
storage Methodology:
Accuracy Rate (%) =
(Total Number of files that have
been backed up from the
source folder/ Total Number of
files that have to be backed up
from the source folder) x 100

Page 221 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level

3. Restoration of Source: Select 10 instances The success rate INR 50,000 per
configuration across different categories of shall be better instances of
(as specified in equipment that shall be than 99% for all failure
Section randomly selected for the categories of
Backup restoration decided by CRIS systems &
Solution) of each quarter. subsystems of
each of the the CVMS
Systems & Methodology: solution both
Subsystems of Success Rate (%) = virtual &
the CVMS (Total Number of physical.
solution. Successful Restoration / Total
Number of Restoration
attempts) x 100

Frequency: Restoration tests

to be conducted once in a
quarter

C. QoS for the CVMS applications

1. Helpdesk Ticket Source: Monitoring report >=95% within 30 For availability

response time generated by the EMS/ Call minutes 95% or higher -
logs a. < 95% & >=
Response Time 93%:
= Average time Methodology: Penalty of
taken to create Performance Rate (%) = [1− ₹50,000/-
a fault / request (Total Number of Requests with b. < 93% & >=
ticket from the Response Time Exceeding 91%:
time of Threshold/Total Number of Penalty of
notification Requests)] ×100 ₹75,000/-
about the
fault/request. Frequency: Monthly For availability
(Only for CVMS below 91% -
solution Penalty @
excluding ₹1,00,000/- for
infrastructure every 2% (or
beyond the part thereof)

Page 222 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
scope of MSI) reduction of
availability
below 95%.
2. Helpdesk Ticket Source: Monitoring report >=95% within 4 No penalty for
closure time generated by the EMS hours closure greater
than 95% of the
Ticket Closure Methodology: tickets.
Time = Average Performance Rate (%) = [1− a. < 95% & >=
time taken to (Total Number of Requests with 93%:
Close the Response Time Exceeding Penalty of
trouble/request Threshold/Total Number of ₹50,000/-
ticket (Only for Requests)] ×100 b. < 93% & >=
CVMS solution 91%:
excluding Penalty of
infrastructure ₹75,000/-
beyond the
scope of MSI) For closure of
tickets below
91% -
a. Penalty @
₹1,00,000/-
for every 2%
(or part
thereof)
reduction in
closure of
tickets below
95%.
3. Incorrect Source: ITSM Tool Report For each A penalty of
Closure of the provided by the EMS incident of INR 10,000/- for
Helpdesk incorrect trouble each incorrect
tickets Methodology: ticket closure. trouble ticket
Analysis of the tickets from closure
each category of the tickets detected.

Page 223 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
4. Data Retrieval from the Public Cloud
a. High Priority Source: Logs from Cloud Data retrieval a. Retrieval
Data Retrieval Service Provider for the High time to fetch from
from the Public Priority Data. the data from Frequent
cloud storage
Cloud as Access
Methodology: Cloud logs- to CVMS
defined in report showing time taken to VM/Container. storage as:
Section Sizing make available first byte of the • Up to 1% of
Parameters for subject data file/video stream. a. Frequent the total
the CVMS Access: <=1 delayed
Solution Percentage of total delayed sec retrieval
retrieval request = requests -
b. In frequent
(Total delayed retrieval
Access: No Penalty
request/Total retrieval request
>=30 sec to • For >1% to
made in a month) *100.
<=1 minute
Total retrieval requests are the <=5% of the
number of requests received by total delayed
the cloud storage in a month retrieval
from the CVMS applications. requests -
Penalty of
0.25% of
monthly
payment for
SOR line
item 1.1)
• For >5% to
<=10% of
the total
delayed
retrieval
requests -
Penalty of
0.5% of
monthly
payment for
SOR line
item 1.1)
• Above >10%
of the total

Page 224 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
delayed
retrieval
requests -
Penalty of
2% of
monthly
payment for
SOR line
item 1.1)

b. Retrieval
from
Infrequent
storage as:
• Up to 1% of
the total
delayed
retrieval
requests-
No Penalty
• For >1% to
<=5% the
total delayed
retrieval
requests-
Penalty of
0.25% of
monthly
payment for
SOR line
item 1.1)
• For >5% to
<=10% the
total delayed
retrieval
requests-
Penalty of
0.5% of

Page 225 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
monthly
payment for
SOR line
item 1.1)
• Above >10%
the total
delayed
retrieval
requests-
Penalty of
2% of
monthly
payment for
SOR line
item 1.1)

b. Normal Priority Source: Logs from Cloud Data retrieval a. Retrieval

Data Retrieval Service Provider for the High time to fetch from
from the Public Priority Data. the data from Frequent
Cloud as cloud storage
Access
defined in Methodology: Cloud logs- to CVMS
Section Sizing report showing time taken to VM/Container. storage as:
Parameters for make available first byte of the • Up to 1% of
the CVMS subject data file/video stream. a. Frequent the total
Solution Access: <=1 delayed
Percentage of total delayed sec retrieval
retrieval request = requests -
b. In frequent
(Total delayed retrieval
Access: No Penalty
request/Total retrieval request
made in a month) *100% >=30 sec to • For >1% to
Total retrieval requests are the <=1 minute <=5% of the
number of requests received by total delayed
the cloud storage in a month Long Term
retrieval
from the CVMS applications. Archival Access:
Within 12 Hours requests -
Penalty of
0.25% of
monthly
payment for
SOR line

Page 226 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
item 2)
• For >5% to
<=10% of
the total
delayed
retrieval
requests -
Penalty of
0.5% of
monthly
payment for
SOR line
item 2)
• Above >10%
the total
delayed
retrieval
requests -
Penalty of
2% of
monthly
payment for
SOR line
item 2)

b. Retrieval
from
Infrequent
storage as:
• Up to 1% of
the total
delayed
retrieval
requests-
No Penalty
• For >1% to
<=5% the

Page 227 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
total delayed
retrieval
requests-
Penalty of
0.25% of
monthly
payment for
SOR line
item 2)
• For >5% to
<=10% the
total delayed
retrieval
requests-
Penalty of
0.5% of
monthly
payment for
SOR line
item 2)
• Above >10%
the total
delayed
retrieval
requests-
Penalty of
2% of
monthly
payment for
SOR line
item 2)

c. Retrieval
from
Archival
storage:

• Up to 1% of

Page 228 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
the total
delayed
retrieval
requests -
No Penalty
• For >1% to
<=5% of the
total delayed
retrieval
requests -
Penalty of
0.25% of
monthly
payment for
SOR line
item 2)
• For >5% to
<=10% of
the total
delayed
retrieval
requests -
Penalty of
0.5% of
monthly
payment for
SOR line
item 2)
• Above >10%
the total
delayed
retrieval
requests -
Penalty of
2% of
monthly
payment for

Page 229 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
SOR line
item 2)

5. Amendment of Source: Closure of SOP >=98% within 48 For availability

SOPs, and Request tickets in report hours 94% or higher -
implementation generated by the ITSM a. < 98% & >=
of the SOPs in Helpdesk tool. 96%:
the Workflow Penalty of
/System Methodology: Performance INR 50,000/-
Rate (%) = [1− (Total Number b. < 96% & >=
of Amendments of SOPs and 94%:
Implementations Requests with Penalty of
Response Time Exceeding INR 75,000/-
Threshold/Total Number of
Requests)] ×100 For availability
below 94% -
Penalty @ INR
1,00,000/- for
every 2% (or
part thereof)
reduction of
availability
below 94%.
6. Creation of new Source: Operational >=98% within For completion
and additional dashboard visible in the EMS two weeks rate 94% or
Dashboards (In higher -
the case of Methodology: Performance a. < 98% & >=
dashboards Rate (%) = [1− (Total Number 96%:
which might of new dashboards Penalty of
need additional Implementations Requests with INR 50,000/-
time to create Response Time Exceeding b. < 96% & >=
the Threshold/Total Number of 94%:
dashboards, Requests)] ×100 Penalty of
CRIS will INR 75,000/-
decide the

Page 230 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
criticality and For availability
may give below 94% -
additional time Penalty @ INR
to implement 1,00,000/- for
the same, final every 2% (or
authority will be part thereof)
CRIS) reduction of
availability
below 100%.
7. Integrations during O&M Phase of the CVMS Project
a. Integration of Source: Within 3 weeks a. No penalty
CVMS with M- Monitoring at CVMS application of notification by for
NVR/NVR/VRU or Report from EMS Tool CRIS regarding integration
for Coaches, the availability of
within
Locomotives, the respective
EMUs & Methodology: interface for allowed
MEMUs the Integration of CVMS solutions integration period of
first time with with respective OEMs M- three weeks.
every OEM of NVR/NVR/VRU b. Penalty of
the M- ₹2,00,000/-
NVR/NVR/VRU. for delay of
up to one
Note: For
OEMs who are week after
being allowed
integrated to period.
the CVMS c. Additional
solution post Penalty of ₹
Phase 1 Go- 3,00,000/-
Live
for delay
more than
one week
and up to
two weeks
after allowed
period.
d. Additional
Penalty of
₹4,00,000/-

Page 231 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
per week for
delay more
than two
weeks or
part thereof
after allowed
period.
(The above
penalties shall
be calculated
separately for
each OEM of
the M-
NVR/NVR/VRU
for which the
integration has
been delayed)
b. Integration of Source: Allowed time is a. No penalty
CVMS with Monitoring at CVMS application within 1 week of for
each or Report from EMS Tool notification by integration
Subsequent M- CRIS regarding
within
NVR, NVR & the availability of
VRU for Methodology: the respective allowed
Coaches, Integration of CVMS solutions M-NVR, NVR, period of
Locomotives, with respective OEMs M-NVR, VRU for One weeks.
EMUs & NVR, VRU integration b. Penalty of
MEMUs after ₹5,000/- per
the first-time M-
integration has
NVR/NVR/V
been
successfully RU for delay
completed of up to one
with week after
respective allowed
OEM. period.
c. Additional
Note: For
Penalty of ₹
OEMs who are
being 7,000/- per
integrated to M-
the CVMS NVR/NVR/V
solution post RU for delay

Page 232 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
Phase 1 or more than
Final Go-Live one week
and up to
two weeks
after allowed
period.
d. Additional
Penalty of
₹10,000/-
per M-
NVR/NVR/V
RU per
week for
delay more
than two
weeks or
part thereof
after allowed
period.
(The above
penalties shall
be applicable
only for the
delayed
Quantities of
the M-
NVR/NVR/VRU)
c. Primary CRIS / Source: Execution of test Within 4 Weeks a. No penalty
IR applications cases as per integration of notification by for
& databases requirements CRIS regarding integration
the availability of
within
Note: For the respective
applications Methodology: interface for allowed
and databases Integration with respective integration period of
which are being applications & databases four weeks.
integrated to b. Penalty of
the CVMS ₹1,00,000/-
solution post for delay of
Phase 1 Go-
up to one
Live
week after

Page 233 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
allowed
period.
c. Additional
Penalty of ₹
1,50,000/-
for delay
more than
one week
and up to
two weeks
after allowed
period.
d. Additional
Penalty of
₹2,00,000/-
per week for
delay more
than two
weeks or
part thereof
after allowed
period.
(The above
penalties shall
be calculated
separately for
each
application /
database for
which the
integration has
been delayed)
d. Secondary Source: Monitoring at CVMS Within 6 Weeks a. Penalty of
CRIS / IR/ application & Report from EMS of notification by ₹1,00,000/-
Other Tool CRIS regarding for delay
Government the availability of
beyond first
applications & the respective
databases Methodology: interface for week
Integration with respective integration b. Delay
Note: For applications & databases beyond

Page 234 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
applications second (2nd)
and databases week:
which are being Penalty of
integrated to
₹1,50,000/-
the CVMS
solution post or part
Phase 1 or thereof
Final Go-Live c. Delay
beyond
fourth (4)
week:
Penalty of
₹2,00,000/-
for each
week’s
delay or part
thereof.
(The above
penalties shall
be calculated
separately for
each
application /
database for
which the
integration has
been delayed)
8. Patch Management

a. Minimum time Source: Report generated by >=100% within 7 No penalty for

for reporting to the Incident Management days of reporting 100% reporting
CRIS of Critical Module of the EMS system. by the respective of Critical and
and high OEM.
High Severity
severity
Methodology: Success Rate Patches within
patches
released by the (%) = (Total Quantity of seven days.
respective patches reported to CRIS
OEMs. within 7 days for release by For rate 98%
OEM / Total Number of patches or higher -
released during the respective a. < 100% &

Page 235 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
month) x 100. >= 99%:
Penalty of
Performance Rate (%) = [1− INR
(Total Number of new Critical 1,00,000/-
and high severity patches b. < 99% & >=
released by the respective
98%:
OEMs with Response Time
Exceeding Threshold/Total Penalty of
Number of patches released by INR
the respective OEMs)] ×100 2,00,000/-

For availability
below 98% -
Penalty @ INR
3,00,000/- for
every 2% (or
part thereof)
reduction of
availability
below 100%.
b. For each Source: Report provided by >=100% within a. No Penalty
instance of the EMS two weeks of applicable
Critical and reporting by the for 100%
High Severity respective OEM.
Methodology: Success Rate implementati
Patches
(%) = (Total Quantity of Critical on of Critical
Note: Subject and High Severity Patches and High
to implemented by the MSI / Total Severity
implementation Number of Critical and High Patches
and testing on Severity Patches released by within two
the test bed the OEM) x 100. weeks
and found to be
(100%)
safe to be
implemented in b. < 99% & >=
the operational 98%:
CVMS stack Penalty of
along with INR 50,000/-
approval from c. < 98% & >=
CRIS. 97.0%:
Penalty of
INR

Page 236 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
1,00,000/-

For patch
application
success rate
below 97% -
Penalty @
INR
2,00,000/-
for every
1% (or part
thereof)
reduction of
completion
below 100%.
c. For each Source: Report provided by >=100% within a. No Penalty
instance of the EMS two months of applicable
Non-Critical reporting by the for 100%
Patches respective OEM.
Methodology: Success Rate implementati
Note: Subject (%) = (Total Quantity of Non- on of Non-
to Critical Patches implemented Critical
implementation by the MSI / Total Number of Patches
and testing on Non-Critical Patches released within two
the test bed by the OEM) x 100. months
and found to be (100%)
safe to be
b. < 99% & >=
implemented in
the operational 98%:
CVMS stack Penalty of
along with INR 25,000/-
approval from c. < 98% & >=
CRIS. 97.0%:
Penalty of
INR 50,000/-

For availability
below 97% -
Penalty @
INR

Page 237 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
1,00,000/-
for every
1% (or part
thereof)
reduction of
completion
below 100%.

9. Loss of Live Source: Report provided by >=98% of the No penalty for

Camera feed at the VMS & EMS configured the feeds
the VMS feeds. received
Methodology: Performance >=98%.
Note: For each Rate (%) = [1− (Total number
instance of loss of Live feeds received / Total For availability
of feeds. Number of Live feeds of 94% or
configured)] ×100 higher -
a. < 98% & >=
96%:
Penalty of
INR 5,000/-
b. < 96% & >=
94%:
Penalty of
INR 10,000/-

For availability
below 94% -
Penalty @ INR
20,000/- for
every 2% (or
part thereof)
reduction of
feed availability
below 100%.

Page 238 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
10. Degraded Source: Report provided by >=99% in a No penalty for
functioning of the VMS/ICCC/Other month. the >=99%.
the VMS , ICCC applications of the CVMS &
or any other EMS For availability
application of of 95% or
the CVMS higher -
solution against Methodology: Performance a. < 99% &
the Rate (%) = [1− (Total number >= 97%:
benchmarked of minutes of degraded Penalty
KPIs. performance / Total Number of of INR
minutes in a month)] ×100 1,00,000/
Note: For each -
instance of b. < 97% &
degradation, for >= 95%:
each Penalty
application of INR
2,00,000/
-

For availability
below 95% -
Penalty @ INR
3,00,000/- for
every 2% (or
part thereof)
reduction of
feed availability
below 100%.

11. Missing the Source: Published calendar of i) On time i) No Penalty

activities of the the PAT. ii) Delay 7 days ii) Penalty if INR
published of target date. 50,000/- for the
calendar for the Methodology: Successful first week of
iii) Delay of
Periodic completion of the events as per delay.
Acceptance the published calendar every week after iii) Delay of
Tests 7 days. 1,00,000/- for
each additional
week of delay
beyond first
week.

Page 239 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
12. Non- Source: Monthly/Quarterly For each Penalty of INR
compliance Audit reports instance of the 1,00,000/- For
detected in the Non-compliance each instance
EMS during Methodology: Random Audit detected in the of non-
monthly audits of the EMS reports with the EMS during the compliance
for accuracy actual logs of the individual monthly audit or detection either
and PAT. systems and applications. PAT. in the monthly
audit or PAT.
13. Change in Source: Monthly Attendance For every Penalty of INR
Manpower Sheet Change in 1,00,000 for
(applicable only allocated each change in
for the Key Methodology: Allocated Manpower within manpower if
Resources manpower should be present in a period of one changed within
deployed for the role for a minimum period year from the one year of
the project of 1 Year. date of allocation allocation to the
Operations to the project Project.
phase) Please refer to section
Manpower to be deployed for
the Project for the details of
the Key Resources.
D. Security and Integrity

1. Security Source: EMS Tool No breach a. Any security

Breaches Methodology: Any incident breach
including data where-in a system is detected will
theft/loss / compromised attract a
unauthorized or any case wherein data theft penalty of ₹1
access. occurs (including internal Crore for
incidents) each
Note: This incident.
penalty shall be b. Also, a Root
applicable from Cause
the date of Analysis
Phase 1 Go- (RCA) to be
Live with no- submitted
relaxation in the within 10
initial 60 days days of
from the date of reporting
Phase 1 Go-
Live

Page 240 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
2. Root-Cause Source: EMS Tool a. Within 24 a. Penalty of
analysis for any Methodology: Submission of hours for the INR
type of security Root-Cause Analysis with first level of 1,00,000/-
breaches. OEMs inputs along with the report for delay for
mitigation methodology. b. Within 2 each
weeks from additional 24
the date of hours on
occurrence of submission
each security of first level
incidence. report
c. Implementatio beyond 24
n of mitigation hours for
measures for each
the security security
incidents incident.
Within two b. Penalty of
weeks to INR
ensure that 3,00,000/- for
they do not each week of
repeat again. delay on
submission of
detailed
report beyond
two weeks for
each security
incident.
c. Penalty of
INR
5,00,000/- for
each week of
delay beyond
two weeks in
implementatio
n of mitigation
measures for
the security
incidents.
3. Periodic Source: Start date of the Bi- i) On time i) No Penalty
security testing annual security audit decided ii) Delay 15 days ii) Penalty if INR
/ Audit during by CRIS in consultation with of target date. 1,00,000/- for
the first week of
O&M period (Bi- the MSI. iii) Delay of
delay.
annual security every month iii) Delay of

Page 241 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
audits) by Methodology: Completion after 30 days. 5,00,000/- for
CERT-in report issued by the CERT-in each week of
empanelled Vender of the Bi-annual audit delay beyond
first week.
vendor report within four weeks from
the date of start of the security
audit.
4. Implementation Source: Report from the MSI, 100% i) No Penalty for
of mitigation confirming the mitigation Implementation 100%
measures of measures that have been of mitigation implementation
Vulnerabilities implemented to address the measures within of the mitigation
detected during vulnerabilities. 30 days from the reports within
the bi-annual date of 30 days from
security audits Methodology: Confirmation completion of the the date of
from the CERT-in empanelled bi-annual completion of
vendor validating the report. security audit. the bi-annual
security audit
ii) Penalty if INR
1,00,000/- for
first week of
delay.
iii) Delay of INR
2,00,000/- for
each week of
delay beyond
first week.
E. Manpower Availability
1. Availability of Source: Monthly attendance No absence. a. No penalty
Resources sheet for 100%
(24x7x365) for Refer to Section attendance
Help Desk Methodology: Daily Annexure-23- b. Absence of
Operators, attendance for all resources Deployment of manpower
ICCC Operators collated in a template as in Manpower for will attract a
& Manager Annexure-35-Template for detailed penalty of ₹
(Helpdesk & Monthly Attendance signed requirements. 2000 per day
ICCC) at CRIS by MSI & CRIS for each
resource.
2. Availability of Source: Monthly attendance No absence. a. No penalty
Project sheet for 100%
Manager during Refer to Section attendance
the O&M Phase Annexure-23-
Methodology: Daily b. Absence of

Page 242 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Service Level Measurement Source & Target/Service

Penalty
No. Objective Methodology Level
attendance for all resources Deployment of manpower
collated in a template as in Manpower for will attract a
Annexure-35-Template for detailed penalty of ₹
Monthly Attendance signed requirements. 5000 per day
by MSI & CRIS for each
resource.
Table 29:Service Level Agreement (SLA) – Post Phase 1 Go-Live
** Total monthly charges mean monthly bill value for the respective month (Excl. Tax)

Note:

i. No Penalties shall be applicable on the MSI for a period of 60 days from the
date of Phase 1 Go-Live.
ii. Any penalties associated with a specific deliverable or milestone shall be
applicable solely to that particular milestone. Subsequent milestones, which
follow sequentially, will not incur penalties.
iii. Bidders need to implement requisite monitoring suits/services in its technical
proposal which needs to be implemented and monitor each SLA on a real-
time basis whose integrated dashboard access to be made available to CRIS.
5 users access needs to be considered by the Bidder.
iv. All SLA reports are to be available on an automated basis and monthly
downloadable reports are to be available which are generated from the
system. Implementation of the SLA monitoring services will be a pre-requisite
for the Phase 1 Go-Live of the system.
v. SLA shall be monitored on a monthly basis and penalties shall be calculated
on a monthly basis. The same will be aggregated and will be deducted from
monthly payments.
vi. During the contract period, MSI shall ensure that system performance is not
degraded due to insufficient infrastructure provisioning. In case any additional
infrastructure is required to meet performance SLAs then the same shall be
provisioned/ supplied by MSI with no cost implication to CRIS.
vii. The payment would be linked to compliance with the SLA metrics as laid
down in the tender.
viii. Planned downtime shall be excluded from the SLA calculation.
ix. In case multiple SLA violations occur due to the same root cause or incident
then the SLA that incurs the maximum penalty would be considered for
penalty calculation rather than a sum of penalties for the applicable SLA
violations

Page 243 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

x. MSI will not be paid by CRIS for the duration for which the services were not
available excluding the planned downtime. The amount will be calculated for
each line item based on the SoR rates. This deduction of non-availability of
services shall be over and above of SLA penalties.
xi. Maximum penalty per month will be capped at 20% of the monthly bill value
for the respective month.
xii. If the penalties exceed more than 10% of the monthly Invoice in three
consecutive months, or the total cumulative penalties accumulate to 10% of
the Total Contract Value of the MSI, CRIS will have the right to invoke the
PBG/Terminate the contract.
xiii. Days: Days are defined as All Working and Non-working days (365 days in a
calendar year).
xiv. 24x7 means three shifts of 8 hours every day. This is applicable for all seven
days of the week without any non-working days.

15. Payment Terms, Deliverables & Timelines

15.1. Payment Terms
Payment Schedule

The table below describes the envisaged payment schedule for the project:

Minimum
Description of Payment Terms
SoR Line Item # Assured
SoR Line Item (Post Phase 1 Go-Live)
Payments
Monthly Payment for the
Yes
count of distinct cameras
Video Table 31:
that are active anytime
Management Minimum
1.1 during the month. The count
System Commitment
of the distinct active cameras
services Charges to be
during the month will be
paid by CRIS
checked through the EMS.
Monthly Payment for the
number of concurrent users
calculated on the basis of Yes
monthly average of daily Table 31:
ICCC
peak of user concurrency. Minimum
1.2 application
The count of the monthly Commitment
services
average of daily peak of user Charges to be
concurrency will be checked paid by CRIS
through the ICCC monthly
reports.

Page 244 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Monthly Payment for the

quantity of concurrent users
calculated on the basis of Yes
monthly average of daily Table 31:
Mobile
peak of user concurrency. Minimum
1.3 application
The count of the monthly Commitment
services
average of daily peak of user Charges to be
concurrency will be checked paid by CRIS
through the ICCC monthly
reports.
Monthly Payment for the
count of distinct cameras on
which the FR Solution is Yes
Facial active anytime during the Table 31:
Recognition month. Minimum
1.4
Solution The count of the distinct Commitment
Services cameras on which the FR Charges to be
Solution is active during the paid by CRIS
month will be checked
through the EMS.
Monthly Payment for the
count of distinct M-
Yes
NVR/VRU/NVRs in a month
Enterprise Table 31:
that are active anytime
Management Minimum
1.5 during the month.
System Commitment
The count of the distinct
Services Charges to be
active M-NVR/VRU/NVRs
paid by CRIS
during the month will be
checked through the VMS.
Yes
Monthly Payment for the Table 31:
Video
number of active users using Minimum
1.6 Summarization
the video summarization Commitment
Services
services Charges to be
paid by CRIS
Yes
Monthly Payment for the Table 31:
Image & Video
number of active users using Minimum
1.7 Enhancement
the image & video Commitment
Services
enhancement services Charges to be
paid by CRIS
2 Storage requirement for Normal Priority Data

Page 245 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Frequent access
storage for 7
Monthly Payment based on
days for all types
2.1 Actual Consumption of No
of data other
Storage
than High Priority
data
Infrequent
access Storage
for 23 days for all
types of data
other than high
priority data
Monthly Payment based on
Note: Data
2.2 Actual Consumption of No
Stored in
Storage
Frequent access
Storage Post 7
days shall be
transferred to
Infrequent
access Storage
Archival / Long-
Term Storage for
180 days for all
types of data
other than high
priority data
Note: Post 30
days (7 days
frequent storage
Monthly Payment based on
+ 23 days
2.3 Actual Consumption of No
infrequent
Storage
storage) the data
shall be
transferred to
Archival/long-
term for retention
for 180 days for
flagged and
bookmarked data
only

3. Providing services for monitoring, operation and troubleshooting as per the

requirement at Command-and-Control Center

Page 246 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Monthly Payment for the

Helpdesk number of Helpdesk
3.1 resources / resources deployed as per No
executives the attendance reports
submitted by the MSI
Monthly Payment for the
Helpdesk Helpdesk Manager per the
3.2 No
Manager attendance reports submitted
by the MSI
4. Exclusively for CRIS Use including managed services (Not part of CVMS
solution)
Monthly Payment as per
Virtual
actual consumption of Virtual
4.1 Machines Type No
Machines based on the
-1
Reports provided by the CSP
Monthly Payment as per
Virtual
actual consumption of Virtual
4.2 Machines Type No
Machines based on the
-2
Reports provided by the CSP
Monthly Payment as per
Object Storage-
actual storage consumption
4.3 Frequent No
based on the Reports
Access (7 days)
provided by the CSP
Object Storage - Monthly Payment as per
Infrequent actual storage consumption
4.4 No
Storage (23 based on the Reports
days) provided by the CSP
Object Storage - Monthly Payment as per
Archival actual storage consumption
4.5 No
Storage (180 based on the Reports
days) provided by the CSP
Monthly Payment as per
Data Transfer-
4.6 actual Data Transfer-Out No
Out Charges
report provided by the CSP.
Monthly Payment as per
Data retrieval
4.7 actual Data retrieval report No
charges
provided by the CSP
5 Change Request man-month charges
Monthly Payment for the
Manpower
number of Manpower
Resource rate for
5.1 Resources deployed as per No
Change
the attendance reports
Management
submitted by the MSI. Refer

Page 247 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

section

Table 30: Payment Schedule

*Consumption / Usage shall be calculated monthly post Phase 1 Go-Live.

Note:

i. Payment will start post Phase 1 Go-live (Refer Section Project

Implementation Timelines)
ii. Paid on a monthly basis in arrears, subject to minimum committed charges,
as per SoR post deduction of applicable penalties (if any) as per SLA.
iii. The Unit of measurement for each item shall be as mentioned in the
Schedule of Requirement (SOR).
iv. Upon submission of the monthly invoice in accordance with the Schedule of
Requirement (SOR) and accompanying stipulated enclosures, 80% of the
payment shall be disbursed within 15 days. The remaining 20% pay-out shall
be made within 60 days upon completion of the audit of the supporting
enclosures.
v. Actual consumption/usage shall be calculated through centralized tools
(ICCC, EMS)
vi. Monthly Charges for respective Schedule of Requirement (SOR) line items
will be calculated by dividing the unit rates mentioned in Schedule of
Requirement (SOR) by 96.
vii. Proportionate payment for a month will be calculated by dividing monthly
rates by 30 days and multiplying the same with the number of days for
services that have been provided in that month for the respective SoR line
item.
viii. Once a service has started, the payment for subsequent months will continue
for those number of unit(s) until that service has been decommissioned by
CRIS through a written instruction to the MSI by giving 30 days prior notice
and the payment reduction will be from subsequent calendar month onwards.
In case, the service for the respective unit(s) restarts the process mentioned
in Point IV of Note Section in Payment Terms shall be followed.
ix. Payment for change request as mentioned in Schedule of Requirement
(SOR) clause 3 & 4 will be defined in the change request work order.

Page 248 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

x. Minimum Committed Charges to be paid by CRIS to MSI will be as follows:

Description of Minimum Assurance

SoR Line SoR line Item Start Date End Date on Cumulative
item
Quantity
T = Phase 1
T + 3 Months 10,000 Cameras
Go-Live
Video T + 3 Months T + 6 Months 50,000 Cameras
1.1 Management
T + 6 Months T + 9 Months 1,00,000 Cameras
System services
T + 9 Months T + 12 Months 1,50,000 Cameras
T + 12 Months onwards 2,00,000 Cameras
T = Phase 1
T + 3 Months 50 Users
Go-Live
ICCC T + 3 Months T + 6 Months 200 Users
1.2 application T + 6 Months T + 9 Months 300 Users
services
T + 9 Months T + 12 Months 400 Users
T + 12 Months onwards 500 Users
T = Phase 1
T + 3 Months 100 Users
Go-Live
Mobile T + 3 Months T + 6 Months 200 Users
1.3 application
T + 6 Months T + 9 Months 300 Users
services
T + 9 Months T + 12 Months 400 Users
T + 12 Months onwards 500 Users
T = Phase 1
T + 3 Months 5000 Cameras
Go-Live
Facial
T + 3 Months T + 6 Months 25,000 Cameras
1.4 Recognition
Solution T + 6 Months T + 9 Months 50,000 Cameras
Services
T + 9 Months T + 12 Months 75,000
T + 12 Months onwards 1,00,000 Cameras
T = Phase 1
T + 3 Months 1000 NVRs
Go-Live
Enterprise T + 3 Months T + 6 Months 5000 NVRs
1.5 Management 10,000 NVRs
T + 6 Months T + 9 Months
System Services
T + 9 Months T + 12 Months 20,000 NVRs
T + 12 Months onwards 30,000 NVRs
1.6 Video T = Phase 1 T + 3 Months 10 Users

Page 249 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Description of Minimum Assurance

SoR Line SoR line Item Start Date End Date on Cumulative
item
Quantity
Summarization Go-Live
Services
T + 3 Months T + 6 Months 20 Users
T + 6 Months T + 9 Months 30 Users
T + 9 Months T + 12 Months 40 Users
T + 12 Months onwards 50 Users
T = Phase 1
T + 3 Months 10 Users
Go-Live
T + 3 Months T + 6 Months 20 Users
1.7 Image & Video
Enhancement T + 6 Months T + 9 Months 30 Users
T + 9 Months T + 12 Months 40 Users
T + 12 Months onwards 50 Users
Table 31: Minimum Commitment Charges to be paid by CRIS

Other Schedule of Requirement (SOR) item(s) shall be paid on the actual basis
of consumption/usage on the respective dates as mentioned in line items 2, 3
and 4 of the Table 30: Payment Schedule above.

xi. In case the actual consumption/usages are higher than the criteria mentioned
in Point IX of Note Section in Payment Terms will continue for those actual
consumption/usages.
xii. Payment will be made by CRIS against valid GST tax invoice. In case of
award of contract, successful Bidder shall issue valid tax invoice to CRIS for
availing proper credit of CGST, SGST, IGST, UTGST. GST will not be
reimbursed in the absence of valid tax invoice.
xiii. For all the taxable supplies made by the vendor, the vendor shall furnish all
the details of such taxable supplies in the relevant returns to be filed under
GST Act.
xiv. If the vendor fails to comply with any of the above, the vendor shall pay to
purchaser any expense, interest, penalty as applicable under the GST Act.
xv. In case of incorrect reporting of the offered services made by the vendor in
the relevant return, leading to disallowance of input credit to purchaser, the
vendor shall be liable to pay applicable interest under the GST Act to the

Page 250 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

credit of purchaser. The same provisions shall be applicable in case of

debit/credit notes.

15.2. Documents to be submitted for Payment Claims

The MSI shall follow the below listed procedure while submitting the monthly invoices to
claim the CVMS services:

i. The MSI shall only invoice for the line items mentioned in the “Schedule of
Requirements.”
ii. The Invoice shall be accompanied with the following artifacts:
a. A detailed report outlining the usage of the CVMS on the public cloud,
including the complete resources utilized for the functioning of the solution
in line with the specifications of the bid document.
b. Reports illustrating the performance metrics of the CVMS, including
uptime, response times, and all the service level agreement (SLA)
adherence.
c. Complete list of the tickets that have been logged with the helpdesk- with
detailed analysis report for the resolution of the tickets and requests
registered with the helpdesk.
d. Incident reports, Root Cause Analysis Reports related to downtimes,
service interruptions, or security breaches during the billing period.
e. Records of any changes made to the Central Video Management System
configuration or setup during the billing period.
f. Satisfactory Performance Certificate from CRIS for each month as per
O&M Phase Performance Certificate.
g. Depending on the specific requirements, the MSI may need to submit any
other documents agreed upon with CRIS.

15.3. Delivery Period Extension

i. The milestones specified in the contract at Section Payment Terms,
Deliverables & Timelines shall be the essence of the contract and these
milestones must be achieved not later than the date so specified. The delivery
period shall be reckoned from the date of issue of Purchase Order. In case
the delivery date falls on a gazetted holiday or is subsequently declared as
such, the purchase order will be deemed to be re-fixed up to the next working
date. In such cases, Modification Advice for extension of delivery period will
not be issued. However, extension of the delivery period may be considered

Page 251 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

in deserving cases where genuine reasons exist. Such extensions of delivery

period may be considered with liquidated damages as per EGCC and Denial
Clause. Accordingly, CRIS shall recover from the vendor as agreed and not
by way of penalty, a sum equivalent to 1/2% (half percent) of the Total Price
of the Project. (including elements of taxes, duties, freight, etc.) which the
vendor has failed to start the service within the period fixed for
Commissioning of the solution (as per the milestones in the Section Payment
Terms, Deliverables & Timelines) in the contract or as extended for each
week or part thereof during which the start of such services may be in arrears
where start of service thereof is accepted after expiry of the aforesaid period,
subject to a maximum of 10% (ten percent) of the value of the delayed start of
service.

ii. Delay in Start of Services: The time allowed for “Start of Services” by the
vendor shall be deemed to be the essence of the contract. In case of delay in
Start of Services as mentioned in the Project Implementation Timelines of
the project on the part of vendor, the Purchaser shall be entitled to recover,
and the vendor shall be liable to pay pre estimated liquidated damage at the
rate of 2% of the total contract value of the CVMS. Provided always that the
entire amount of liquidated damages to be paid under the provision of this
clause shall not exceed 10% of the total contract value. After expiry of 5
months period from the date of default i.e. from the date of start of services as
per Project Implementation Timelines provided in the contract, purchaser
will be at liberty to invoke the Performance Bank Guarantee submitted by the
MSI. The decision of the Purchaser, whether the delay in commissioning has
taken place on account of reasons attributed to the vendor shall be final.

15.4. Statutory Variation Clause (SVC)

Statutory Variation in taxes and duties, or fresh imposition of taxes and duties by
State/ Central Governments in respect of the items stipulated in the contract (and
not the raw materials thereof), within the original delivery period stipulated in the
contract, or last unconditionally extended delivery period shall be to Railways'
account. Only such variation shall be admissible which takes place after the
submission of bid. No claim on account of statutory variation in respect of existing
tax/duty will be accepted unless the tenderer has clearly indicated in his offer the
rate of tax/duty considered in his quoted rate. No claim on account of statutory
variation shall be admissible on account of misclassification by the supplier/
contractor.

Page 252 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

15.5. Completion Period of the Contract

i. The entire project shall be completed by the MSI as per delivery schedule
given in Section Project Implementation Timelines from the date of issue of
PO. In case timeline for currency of contract is extended/revised by CRIS, the
contractor shall have to extend the validity of Performance Bank Guarantee
submitted after the issue of LOA (Letter of Acceptance) accordingly. Final
Go-Live Completion Certificate shall be issued by CRIS based on all
commissioning done by the MSI.

16. Schedule of Requirement (SOR)

S. SOR Description Section in UoM QTYS
No. scope of work
as per bid
document - II
1 Providing services for CVMS setup hosted on Public Cloud with all required
necessary hosting infrastructure, software, application, databases,
integration, managed services (network, security etc.) and respective
systems and applications for successful operations of the CVMS solution as
per bid document-II scope of work (including security audit of the complete
CVMS solution by STQC)
1.1 Video Management System Video Per camera 588,830
services with all required Management
systems, applications and System
services including the hosting
ICT infrastructure (Compute,
Storage for high priority data
only, Network, Security, and
monitoring), Management
Services, Subscriptions,
Licenses, integrations with
the Edge devices and Intra-
CVMS along with required
resources and
customisations as per the bid
document-II for successful
implementation, Operations
and maintenance for 96
months Note: Qty is the
number of camera

Page 253 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. SOR Description Section in UoM QTYS

No. scope of work
as per bid
document - II
1.2 ICCC application services Integrated Per No. of User 2,000
with all required systems , Command &
applications and services Control Center
including the hosting of ICT application
infrastructure (Compute,
Storage, Network, Security
and monitoring),
Management Services,
Subscriptions, Licenses,
alerts management, SOPs ,
dashboarding and
integrations with the Edge
Devices, Intra-CVMS,
Railways/CRIS and Other
Government applications /
resources & all other
required customisation as
per the bid document-II for
successful implementation,
maintenance & operations of
the project for 96 months
Note: For concurrent Users
1.3 Mobile application services Mobile Per User 2,000
with all required systems and application
applications and services
including the hosting ICT
infrastructure (Compute,
Storage, Network, Security,
and monitoring),
Management Services,
Subscriptions / Licenses,
alerts management, SOPs,
dashboarding, required
integrations & customisations
as per the bid document-II for
successful implementation,
Operations for 96 months
Note: For concurrent Users

Page 254 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. SOR Description Section in UoM QTYS

No. scope of work
as per bid
document - II
1.4 Facial Recognition
Facial Per camera 2,31,176
Solution with all required Recognition
systems and applications Solution (FR
and services including the Solution)
hosting ICT infrastructure
(Compute, Storage, Network,
Security, and monitoring),
Management Services,
Subscriptions / Licenses,
alerts management, required
integration with applications /
databases & customisations
as per the bid document-II for
successful implementation,
Operations for 96 months
1.5 Enterprise Management Enterprise Per NVR 81,494
System Services along with Management
observability, logging, SLA System (EMS)
monitoring, penalty
calculation & infrastructure
management with all
required systems,
applications and services
including the hosting ICT
infrastructure (Compute,
Storage, Network and
Security), Management
Services, Subscriptions /
Licenses for the complete
CVMS, Network and Edge
Layers as per the bid
document-II for successful
implementation, Operations,
and maintenance for 96
months

Page 255 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. SOR Description Section in UoM QTYS

No. scope of work
as per bid
document - II
1.6 Video Summarization Video Per user 100
Services with all required Summarizatio
systems, applications and n
services including the hosting
of ICT infrastructure
(Compute, Storage, Network,
Security, and monitoring),
Management Services,
Subscriptions, floating
Licenses, alerts
management, and required
Intra-CVMS integrations and
customisation as per the bid
document-II for successful
implementation maintenance
& operations for 96 months
(Including 2400 nos.
floating Camera
Licenses/Subscriptions)
1.7 Image & Video Forensic Per User 100
Enhancement Services with Application
all required systems, (Image &
applications and services Video
including the hosting of ICT enhancement)
infrastructure (Compute,
Storage, Network, Security,
and monitoring),
Management Services,
Subscriptions, floating
Licenses, and required Intra-
CVMS integrations and
customisation as per the bid
document-II for successful
implementation maintenance
& operations for 96 months
2 Storage requirement for Normal Priority Data

2.1 Frequent access storage for Section Sizing Per Month 48.80
7 days for all types of data Parameters Storage Per PB
other than High Priority data for the CVMS
for 96 months

Page 256 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. SOR Description Section in UoM QTYS

No. scope of work
as per bid
document - II
Solution

2.2 Infrequent access Storage Section Sizing Per Month 160.36

for 23 days for all types of Parameters Storage Per PB
data other than high priority for the CVMS
data for 96 months Solution
Note: Data Stored in
Frequent access Storage
Post 7 days shall be
transferred to Infrequent
access Storage
2.3 Archival / Long-Term Storage Section Sizing Per Month 20.58
for 180 days for all types of Parameters Storage Per PB
data other than high priority for the CVMS
data for 96 months Solution
Note: Post 30 days (7 days
frequent storage + 23 days
infrequent storage) the data
shall be transferred to
Archival/long-term for
retention for 180 days for
flagged and bookmarked
data only
3 Providing services for monitoring, operation and troubleshooting as per the
requirement at Command-and-Control Center
3.1 Helpdesk resources / Annexure- Nos. 5
executives (24x7x365 for 3 23(B) –
shifts) (Cost for 1 resource Operations
for 3 shifts for 96 months) as Phase
per the bid document-II
3.2 Helpdesk manager Annexure- Nos. 1
(24x7x365 for 3 shifts) (Cost 23(B) –
for 1 resource for 3 shifts for Operations
96 months) as per the bid Phase
document-II
4 Exclusively for CRIS Use including managed services (Not part of CVMS
solution). Rates are to be quoted for a period of 96 months.
Note: The following components shall be billed on a Pay per Use Model and the
subscriptions may be activated or deactivated as and when required to optimize
the consumption.

Page 257 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. SOR Description Section in UoM QTYS

No. scope of work
as per bid
document - II
4.1 Virtual Machines Type - 1 Per VM 4
a. 8 nos. vCPU b. 64 GB
RAM c. 1 TB of Block
Storage d. Operating System
- Windows Server Note: Qty
is the number of VM
(Rates to be quoted for 24x7
for 96 months)
4.2 Virtual Machines Type - 2 Per VM 6
a. 8 nos. vCPU b. 64 GB
RAM c. 1 TB of Block
Storage d. Operating System
Enterprise Linux

(Rates to be quoted for 24x7

for 96 months)
4.3 Object Storage- Frequent Per TB 50
Access (7 days)
(Rates to be quoted for 24x7
for 96 months)
4.4 Object Storage - Infrequent Per TB 50
Storage (23 days)
(Rates to be quoted for 24x7
for 96 months)
4.5 Object Storage - Archival Per TB 50
Storage (180 days)
(Rates to be quoted for 24x7
for 96 months)
4.6 Data Transfer-Out Charges Per TB 50
(Rates to be quoted for 24x7
for 96 months)
4.7 Data retrieval charges Per TB 10
(Rates to be quoted for 24x7
for 96 months)
5 Change Request man-month charges

Page 258 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. SOR Description Section in UoM QTYS

No. scope of work
as per bid
document - II
5.1 Manpower Resource rate for Per Resource 1
Change Management in the
CVMS Solution Stack.
To be availed by CRIS in
case any new services that
are required in the
operational CVMS Solution
Stack.

Rates to be quoted for 1

resource for one month with
price validity for 96 months.
Please refer to Section
Change Control
Table 32:Schedule of Requirement (SOR)

Page 259 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17. Instruction to Bidders

17.1. Additional Instruction to Bidders
i. The bids should be submitted in a two-bid packet as per EGCC.
ii. The work of the tender shall be carried out without disturbing the working of
the existing system if any. It shall be the responsibility of each bidder to fully
acquaint himself with all the Central and State Laws and Rules & local factors
which may have any effect on the performance of the contract and price of
the stores. The purchaser shall not entertain any request for clarifications
from the bidder regarding such Central, State laws, Rules and local factors.
Also, no request for change of price shall be entertained after the bidder
submits the offer.
iii. Bidder must provide name, address, email address, dedicated telephone/Fax
number of their person as a single point of contact for coordination with CRIS
along with an escalation matrix.

17.2. Eligible Bidders

i. The Bidders eligible for participating in the bidding process shall be:
a. A business entity incorporated under the Companies Act, 1956/2013 or
Partnership firm registered under Limited Liability Partnerships Act, 2008)
or Partnership firm registered under Indian Partnership Act, 1932
(“Business Entity”)13 or,
b. Joint Venture (JV) is allowed to bid against in this tender. Applicable
conditions for JV Bidders are as per Section Qualifications Criteria.
c. Consortium is allowed to bid in this tender. Applicable conditions for
Consortium Bidders are as per Section Qualifications Criteria.
ii. Any Proposal submitted by a Joint Venture (JV) must comply with the
following additional requirements.
a. Separate identity/name shall be given to the Joint Venture.
b. Number of members in a JV shall not be more than three. Joint Venture
(JV) is allowed with Lead Member shall have at least 51% share in the JV.
Lead Member or Lead Partner of the JV must fulfil minimum 80% of the
Qualifications Criteria with respect to financial turnover and balance
criteria to be fulfilled by other JV members. Relevant project/work
experience criteria are to be met by any of the members of JV.

Page 260 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. In their own interest the tenderers, who form such JV, are advised to
investigate capabilities, availability of resources, experienced personnel,
financial soundness, past experience and concurrent engagements of
constituting partners.
d. A member of JV shall not be permitted to participate either in individual
capacity or as a member of another JV in the same tender.
e. Joint Venture Agreement: Joint Venture of bidders must clearly define
role/scope of store/work of each Partner/Member. Further a Joint Venture
Agreement must accompany the bid and shall clearly define the Lead
Member or Lead Partner of such a JV who will be responsible for timely
completion of work as also during execution of work, if awarded,
coordinate with Purchaser on behalf of the JV, receive payments for the
works executed and be liable for due performance of the Contract in all
respect.
f. Power of Attorney by the other members of the JV in favour of the Lead
Partner/Lead Member is also to be submitted along with the bid. This is
also to be enshrined in JV Agreement signed by the JV Members. The
complete details of the members of the JV, their share and responsibility
in the JV etc. particularly with reference to financial, technical and other
obligations shall be furnished in this JV Agreement. This Agreement shall
be valid during the entire duration of the Contract including the period of
extension, if any and the maintenance period after the work is completed.
g. Authority to form Joint Venture: An Authorization Letter/Copy of Power
of Attorney issued by the concerned Firm/Company/Society/Trust/Entity
etc. in favour of the individual, to sign the Joint Venture Agreement as a
Member of Joint Venture on behalf of the concerned
Firm/Company/Society/Trust/Entity etc. and create liability against the
concerned Firm/Company/Society/Trust/Entity etc.
h. The bid shall be submitted only in the name of the JV and not in the name
of any constituent member. The bid can however be submitted by JV or
any of its constituent member or any person authorized by JV through
Power of Attorney to submit tender.
i. Earnest Money Deposit (EMD) shall be submitted by JV or authorized
person of JV.
j. A copy of Memorandum of Understanding (MoU) duly executed by the JV
members on a stamp paper, shall be submitted by the JV along with the
tender. The complete details of the members of the JV, their share and

Page 261 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

responsibility in the JV etc. particularly with reference to financial,

technical and other obligations shall be furnished in the MoU.
k. Once the tender is submitted, the MoU shall not normally be modified /
altered / terminated during the validity of the tender. In case the tenderer
fails to observe/comply with this stipulation, the full EMD shall be liable to
be forfeited.
l. Approval for change of constitution of JV shall be at the sole discretion of
the CRIS. The constitution of the JV shall not normally be allowed to be
modified after submission of the bid by the JV, except when modification
becomes inevitable due to succession laws etc., provided further that
there is no change in qualification of minimum eligibility criteria by JV after
change of composition. However, the Lead Member shall continue to be
the Lead Member of the JV. Failure to observe this requirement would
render the offer invalid.
m. Similarly, after the contract is awarded, the constitution of JV shall not be
normally allowed to be altered during the currency of contract except when
modification become inevitable due to succession laws etc. and minimum
eligibility criteria shall not get vitiated. Failure to observe this stipulation
shall be deemed to be breach of contract with all consequential penal
action as per contract conditions.
n. On award of contract to a JV, a single Performance Guarantee shall be
submitted by the JV as per tender conditions. All the Guarantees like
Performance Guarantee, Warranty Guarantee shall be accepted only in
the name of the JV and no splitting of guarantees amongst the members
of the JV shall be permitted.
o. On issue of LOA (Letter of Acceptance), the JV entity to whom the work
has been awarded, with the same shareholding pattern as was declared in
the MOU/JV Agreement submitted along with the tender, shall be got
registered before the Registrar of the Companies under 'The Companies
Act -2013' (in case JV entity is to be registered as Company) or before the
Registrar/Sub-Registrar under the 'The Indian Partnership Act, 1932' (in
case JV entity is to be registered as Partnership Firm) or under 'The LLP
Act 2008' (in case JV entity is to be registered as LLP). A separate PAN
shall be obtained for this entity. The documents pertaining to this entity
including its PAN shall be furnished to the Railways before signing the
contract agreement for the work. In case the tenderer fails to
observe/comply with this stipulation within 60 days of issue of LOA,

Page 262 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

contract is liable to be terminated. In case contract is terminated railway

shall be entitled to forfeit the full amount of the EMD and other dues
payable to the Contractor under this contract. The entity so registered, in
the registered documents, shall have, inter-alia, following Clauses:

7. Joint and Several Liability - Members of the entity to which the contract
is awarded, shall be jointly and severally liable to the CRIS for
execution of the project in accordance with General and Special
Conditions of Contract. The members of the entity shall also be liable
jointly and severally for the loss, damages caused to the
Railways/CRIS during the course of execution of the contract or due to
non--execution of the contract or part thereof.
8. Duration of the Registered Entity - It shall be valid during the entire
currency of the contract including the period of extension, if any and
the maintenance period after the work is completed.
9. Governing Laws - The Registered Entity shall in all respect be
governed by and interpreted in accordance with Indian Laws.

p. Authorized Member: Joint Venture members in the JV MoU shall

authorize Lead member on behalf of the Joint Venture to deal with the
tender, sign the agreement or enter into contract in respect of the said
tender, to receive payment, to witness joint measurement of work done, to
sign measurement books and similar such action in respect of the said
tender/contract. All notices/correspondences with respect to the contract
would be sent only to this authorized member of the JV.
q. No member of the Joint Venture shall have the right to assign or transfer
the interest right or liability in the contract without the written consent of
the other members and that of the CRIS in respect of the said
tender/contract.
r. Documents to be enclosed by the JV along with the tender:

10. In case one or more of the members of the JV is/are partnership

firm(s), following documents shall be submitted:
▪ A notarized copy of the Partnership Deed or a copy of the
Partnership deed registered with the Registrar.
▪ A copy of consent of all the partners or individual authorized by
partnership firm, to enter into the Joint Venture Agreement on a

Page 263 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

stamp paper,
▪ A notarized or registered copy of Power of Attorney in favour of the
individual to sign the MOU/JV Agreement on behalf of the
partnership firm and create liability against the firm.
▪ An undertaking by all partners of the partnership firm that they are
not blacklisted or debarred by Railways or any other Ministry /
Department of the Govt. of India from participation in tenders /
contracts as on the date of submission of bids, either in their
individual capacity or in any firm/LLP in which they were / are
partners/members. Any Concealment / wrong information in regard
to above shall make the bid ineligible or shall make the contract
liable for termination under Conditions of Contract.
11. In case one or more members is/are Proprietary Firm or HUF, the
following documents shall be enclosed:
▪ A copy of notarized affidavit on Stamp Paper declaring that his
Concern is a proprietary Concern, and he is sole proprietor of the
Concern OR he who is signing the affidavit on behalf of HUF is in
the position of ‘Karta’ of Hindu Undivided Family (HUF) and he has
the authority, power and consent given by other members to act on
behalf of HUF.
12. In case one or more members of the JV is/are companies, the
following documents shall be submitted:
▪ A copy of resolutions of the Directors of the Company, permitting
the company to enter into a JV agreement,
▪ The copies of MOA (Memorandum of Association) / AOA (Articles
of Association) of the company
▪ A copy of Certificate of Incorporation
▪ A copy of Authorization/copy of Power of Attorney issued by the
Company (backed by the resolution of Board of Directors) in favour
of the individual, to sign the tender, sign MOU/JV Agreement on
behalf of the company and create liability against the company.
13. In case one or more members of the JV is/are LLP firm/s, the following
documents shall be submitted:
▪ A copy of LLP Agreement
▪ A copy of Certificate of Incorporation of LLP
▪ A copy of resolution passed by partners of LLP firm, permitting the
Firm to enter into a JV agreement.

Page 264 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

▪ A copy of Authorization /copy of Power of Attorney issued by the

LLP firm (backed by resolution passed by the Partners) in favour of
the individual, to sign the tender and/or sign the MOU/ JV
agreement on behalf of the LLP and create liability against the LLP.
▪ An undertaking by all partners of the LLP that they are not
blacklisted or debarred by Railways or any other Ministry /
Department of the Govt. of India from participation in tenders /
contracts as on the date of submission of bids, either in their
individual capacity or in any firm/LLP or JV in which they were / are
partners/members. Any Concealment / wrong information in regard
to above shall make the contract liable for termination under
Conditions of Contract.
14. In case one or more members of the JV is/are Society/s or Trust/s, the
following documents shall be submitted:
▪ A copy of Certificate of Registration
▪ A copy of Memorandum of Association of Society/Trust Deed
▪ A copy of Rules & Regulations of the Society
▪ A copy of Power of Attorney, in favour of the individual to sign the
tender documents and create liability against the Society/Trust.
▪ All other relevant documents mentioned in this Clause.

iii. Consortium Bidders:

Consortium is allowed to submit Bids against this tender subject to fulfilment of
following conditions:
a. Number of members in a Consortium shall not be more than three. Lead
Member or Lead Partner of the Consortium shall have at least 51% share
in the Consortium. Lead Member or Lead Partner of the Consortium must
fulfil minimum 80% of the Qualification Criteria with respect to financial
turnover and balance criteria to be fulfilled by other Consortium members.
Relevant Project/ Work Experience criteria is to be met by any of the
members of Consortium.
b. In their own interest the bidders, who form such Consortium, are advised
to investigate capabilities, availability of resources, experienced
personnel, financial soundness, past experience and concurrent
engagements of constituting partners.

Page 265 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. A member of Consortium shall not be permitted to participate either in

individual capacity or as a member of another JV/ Consortium in the same
tender.
d. Consortium Agreement: Consortium of bidders must clearly define role/
scope of store/ work of each Partner/ Member. Further a Consortium
Agreement must accompany the bid and shall clearly define the Lead
Member or Lead Partner of such a Consortium who will be responsible for
timely completion of work as also during execution of work, if awarded,
coordinate with Purchaser on behalf of the Consortium, receive payments
for the works executed and be liable for due performance of the Contract
in all respect. Power of Attorney by the other members of the Consortium
in favour of the Lead Partner/ Lead Member is also to be submitted along
with the bid. This is also to be enshrined in Consortium Agreement signed
by the Consortium Members. The complete details of the members of the
Consortium, their share and responsibility in the Consortium etc.
particularly with reference to financial, technical and other obligations shall
be furnished in this Consortium Agreement. This Agreement shall be valid
during the entire currency of the Contract including the period of
extension, if any and the maintenance period after the work is completed.
e. Authorized Member: Consortium members in the Agreement shall
authorize Lead Member or Lead Partner on behalf of the Consortium to
deal with the tender, sign the Agreement or enter into Contract in respect
of the said tender, to receive payment, to witness joint measurement of
work done, to sign measurement books and similar such action in respect
of the said Tender/ Contract. All Notices/ correspondences with respect to
the Contract would be sent only to this Authorized member of the
Consortium.
f. Authority to form Consortium: A copy of Authorization/ copy of Power of
Attorney issued by the concerned Firm/ Company/ Society/ Trust/ Entity
etc. in favour of the individual, to sign the Consortium Agreement as a
Member of Consortium on behalf of the concerned Firm/ Company/
Society/ Trust/ Entity etc. and create liability against the concerned Firm/
Company/ Society/ Trust/ Entity etc.
g. Joint and Several Liability: Members of the Consortium shall be jointly and
severally liable to the CRIS/ Railways for execution of the project in
accordance with General and Special Conditions of Contract. The
members of the Consortium shall also be liable jointly and severally for the

Page 266 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

loss, damages caused to the Railways/ CRIS during the course of

execution of the Contract or due to non-execution of the Contract or part
thereof.
h. Earnest Money Deposit (EMD) shall be submitted by Consortium or
authorized person of Consortium.
i. Once tender is submitted, Agreement for a Consortium shall not normally
be modified / altered/ terminated during the validity of the tender. In case
the tenderer fails to observe/ comply with this stipulation, the full EMD
shall be liable to be forfeited.
j. Approval for change of constitution of Consortium shall be at the sole
discretion of the CRIS. The constitution of the Consortium shall not
normally be allowed to be modified after submission of the bid by the
Consortium, except when modification becomes inevitable due to
succession laws etc., provided further that there is no change in
qualification of minimum eligibility criteria by Consortium after change of
composition. However, the Lead Member shall continue to be the Lead
Member of the Consortium. Failure to observe this requirement would
render the offer invalid.
k. Similarly, after the contract is awarded, the constitution of Consortium
shall not be normally allowed to be altered during the currency of contract
except when modification become inevitable due to succession laws etc.
and minimum eligibility criteria shall not get vitiated. Failure to observe this
stipulation shall be deemed to be breach of contract with all consequential
penal action as per contract conditions.
l. On award of Contract to a Consortium, a Performance Bank Guarantee
(PWAMCBG) shall be submitted by the Consortium as per tender
conditions. No splitting of Bank Guarantee amongst the members of the
Consortium shall be permitted.
m. If the Bidder is bidding in a consortium, then the Bidder needs to submit
Consortium agreement and Power of Attorney as mentioned in Annexure-
31(B)-Consortium Agreement of this Bid Document.
n. A Bidder or member of JV/ Consortium which has earlier been barred or
blacklisted by CRIS or GOI or any state government or any other
government entity in India from participating in any bidding process shall
not be eligible to submit a Proposal, either individually or as member of a
JV/ Consortium if such bar subsists as on the Proposal Due Date. The
Bidder (all members in case of a JV/ Consortium) shall be required to

Page 267 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

furnish an affidavit as per format provided in Annexure-31 –Agreements

for JV & Consortium.
o. No change in the composition of a JV/ Consortium shall be permitted
unless approved by CRIS in writing.

17.3. Pre-Bid Meeting

i. To clarify and discuss issues with respect to the Project and the bid
document, a Pre-Bid meeting (“Pre-Bid Meeting”) will be held as per the
details provided in IREPS portal.
ii. Prior to the Pre-Bid meeting, the Bidders may submit a list of queries, request
for clarifications and proposed suggestions, if any, as per the format set out in
Annexure-16-Format For Pre-Bid Queries. Bidders must formulate their
queries and forward the same to CRIS prior to the Pre-Bid meeting in terms of
schedule as set out in IREPS Portal.
iii. The Bidder shall certify that the offered solution fully meets the Functional
Design and Technical Requirements. Various design features incorporated in
the solution to fulfil different technical performance requirements shall be fully
explained in the offer. However, in case of deviations, the Bidder must state
the deviations in the deviation tab on the bidding interface of IREPS, and
clearly explain how the solution will still meet the requirements despite the
deviations.
iv. In case of any change in the schedule of Pre-Bid Meeting, the same will be
communicated to Bidders through email and/or by posting on the e-
procurement website specified in the IREPS Portal.
v. Attendance of the Bidders at the Pre-Bid Meeting is not mandatory. CRIS will
endeavour to respond to all queries from all Bidders received till the last date
for submission of queries, irrespective of attendance of the Bidder in the Pre-
Bid Meeting.
vi. No interpretation, revision, or other communication from CRIS regarding the
bid document shall be valid unless it is given in writing. CRIS would upload its
responses to various queries on the IREPS portal.
vii. The queries can be sent to CRIS through email, only at cvms@cris.org.in.

17.4. Preparation and Submission of Proposals

i. Being two packet/bid tender, the instructions for two packet tenders given in
EGCC (Part-I) will be followed.

Page 268 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

ii. The bidder should quote the rates strictly in accordance with the column/fields
provided in the financial rate page of e - tender.
iii. Bidder is required to quote for the full tendered quantity of all the items failing
which his offer shall be treated as unresponsive and ignored without any
reference to him and their EMD shall be forfeited.
iv. Bidders shall provide all required information as per the bid document and in
the specified formats. CRIS reserves the right to reject any Proposal(s) that
is/are not in the specified formats. Proposals shall include Technical Proposal
and Price Proposal as described in this Clause.
v. The Proposals shall consist of ‘Technical Proposal’ and ‘Price Proposal’
comprising the following:
a. Technical Proposal

1. Checklist duly filled in as per the format provided in Annexure-7-

Bidder’s Checklist
2. Details of Bidder (in case of JV/ Consortium, this would need to be
provided for all the members) as per format in Annexure-8- Bidder’s
& Key OEM’s Self Information
3. In case of JV, Power of Attorney, in favour of Lead Member by all
members of the JV/ Consortium as in Annexure-9-Format for Power
of Attorney for Lead Member
4. Affidavit Certifying that the Bidder / Promoter(s)/ Director(s) of Bidder is
not blacklisted/barred as in Annexure-10-Declaration of Non-
Blacklisting
5. Submissions in support of Eligibility criteria Annexure-11-Format for
Providing Eligibility Compliance
6. Details for Technical Evaluation, Project Experience and CVs as per
Annexure-12-Project Experience of the Bidder and Annexure-14-
CV of Key Personnel Proposed respectively.
7. Long Term Support as per

Page 269 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

9. Annexure-19-Long Term Maintenance Support

10. NDA as per Annexure-21-Non-Disclosure Agreement to be signed
by the bidder.
11. In case of JV/ Consortium, Memorandum of Understanding as per the
format attached in Annexure-31(A) - Joint Venture Agreement and
Annexure-31(B)-Consortium Agreement
12. Power of Attorney for signing of the Proposal as in Annexure-47- PoA
for signing of proposal
13. Any other documents required as per any other clause of the bid
document, even if not indicated in the aforesaid Checklist.
vi. All the required information shall be furnished strictly in prescribed formats
only. Any information other than in the prescribed formats shall not be
entertained. The Proposal shall be evaluated based on information furnished
in the prescribed formats. Bidder shall ensure that the Price Proposal or any
price-related information is not included in its Technical Proposal.
vii. The Proposal shall be typed or printed in indelible ink and the Bidder shall
initial each page, along with organisation seal. All the alterations, omissions,
additions, or any other amendments made to the Proposal shall be initialled
by the person signing the Proposal. The Proposal shall contain an index in
the beginning denoting proposal contents and their respective page numbers.
Submission of Proposals
viii. The Proposals shall be submitted, through the IREPS website
(https://www.ireps.gov.in/). Scanned copies of the complete Technical
Proposal (in pdf format, printing, copying, and searching enabled) including
scanned copy of the Bid Security (in pdf format)
ix. The original Bid Security (Demand Draft / Bank Guarantee as per Annexure-
17-Performance Bank Guarantee shall be submitted before the Proposal
Due Date.
x. The procedures outlined in EGCC (Part-I) (available on
https://cris.org.in/crisweb/design1/indexorg.jsp?t=6) for two bid packet
tenders will be adhered to, given that this is a two-bid packet tender.
xi. The Bidder shall quote the rates strictly in accordance with the column/fields
provided in financial rate page of e tender.
xii. Bidder is required to quote for the full tendered quantity for all the items;
failing which his offer for the bid document shall be treated as unresponsive
and ignored without any reference to him and their EMD shall be forfeited.

Page 270 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.5. Validity of Proposals

i. The Proposal shall indicate that it would remain valid for a period not less
than 180 days from the last date of submission. CRIS reserves the right to
reject any Proposal that does not meet this requirement.
ii. Prior to expiry of the Bid Validity Period, CRIS may request the Bidders to
extend the period of validity for a specified additional period. A Bidder may
refuse the request without forfeiting its Bid Security. A Bidder agreeing to the
request will not be allowed to modify its Proposal but would be required to
extend the validity of its Proposal for the period of extension and for extension
of Bid Security comply with Section Validity of Proposals in all respects. A
Bidder refusing the request shall not be eligible to participate further in the
Bidding process.
iii. The Bid Validity Period of the Successful Bidder shall automatically be
extended till the date on which the Agreement is executed and comes into
force, subject to a maximum of [90] days from the original Bid Validity. The
Successful Bidder shall comply with Section Validity of Proposals for
extension of its Bid Security.

17.6. Proposal Due Date

i. The Proposals shall be submitted on or before the Proposal Due Date
mentioned in the IREPS Portal in the manner and form as detailed in the bid
document. The original Bid Security shall be submitted on or before due date
for the same as specified in the IREPS Portal.
ii. CRIS may extend the Proposal Due Date by issuing a Corrigendum.

17.7. Verification of Documents

CRIS reserves the right to verify all statements, information and documents submitted
by the Bidder in response to the bid document. Failure of the CRIS to undertake such
verification shall not relieve the Bidder of its obligations or liabilities hereunder to submit
true and correct information; nor will it affect any rights of CRIS.

17.8. Bidders Responsibility

1. The bidder shall be responsible for any deviation/rejection in PoC of all the
function of the solution due to non-conformity with the specification or
malfunctioning of the solution during PoC and also for the delay due to improper

Page 271 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

recommended standards etc. Any changes during PoC shall be at the

responsibility and cost of the bidder.
2. The Bidders are expected to carefully examine the contents of all the documents
provided. Failure to comply with the requirements of the bid document will be at
the Bidder’s own risk.
3. The bidder shall be solely responsible for procuring, implementing, and
maintaining all necessary software applications, public cloud infrastructure, and
any other requisite services to meet the functional requirements specified in
Part-II of the bid document.
4. In case, Bidder feels that there is any inconsistency or discrepancy in
requirements specified in the Bidding Documents, the Bidder shall bring the
same to the notice of CRIS, on or before Pre-Bid Meeting. In case, any
inconsistency/ discrepancy in any of the requirements is discovered after
submission of the Proposals or execution of the Agreement, CRIS shall reserve
the right to clarify and interpret, which of the requirements shall take
precedence. The decision of CRIS shall be final and binding.
5. It would be deemed that prior to the submission of Proposal, the Bidder has:
a. made a complete and careful examination of the various aspects of the
Project including but not limited to:

1. requirements, and other information set forth in the bid document.

2. all other matters that might affect the Bidder’s performance under the
terms of the bid document.
3. diligent scrutiny of the terms and conditions of the draft Agreement.
4. applicable laws and regulations in force in India and those applicable
to the Project.

b. received all such relevant information as it has requested from CRIS.

c. CRIS shall not be liable for any omission or mistake or error or neglect by
the Bidder in respect of the above.
6. The Bidder’s Staff/Manpower shall have adequate knowledge about the
provisions of the latest rules, acts etc. issued by the Central/State Government,
particularly in reference to the matters which includes labour, worker’s safety,
minimum wages etc.
7. The Bidder’s Staff/Manpower should be adequately trained and proficient in the
responsibility assigned to them.

Page 272 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

8. Bidder shall submit a list of his employees as would be engaged by him for this
work with details including names, address, phone number, age, marital status,
election ID No., etc. Bidder is also responsible for maintaining all mandatory
register and records as required under Contract Labour (Regulation and
Abolition) Act and shall have to produce during the inspection of labour
commissioner and/or as mandated by law.
9. Necessary formalities such as application for gate pass in prescribed format
shall have to be completed in advance before start of the work, for which, details
of contract labour along with their photograph, identity card/driving
license/Aadhar card, etc. as applicable, shall be provided by the bidder. Any
change in their address or changes of contract labour shall be immediately
informed to the gate pass section for correction of gate pass. The gate pass is
normally issued once in three months and frequent changing of gate pass
without any valid reason is not allowed.
10. Details of police verification of all the staff should be submitted by the Bidder to
the consignees. A copy of the same after verification and any other relevant
processing to be endorsed by consignee to CRIS.
11. The Bidder shall keep in force a policy/policy of insurance against all liabilities
and recognized risk in respect of accident to person employed by bidder for the
purpose of carrying out the work under the contract. In respect of all staff
engaged by him, the Bidder shall be responsible against all claims under extant
Laws.
12. The persons engaged by the bidder should be courteous, well-mannered and
well behaved. CRIS reserves the right to ask the Bidder to remove any person if
found to be unsuitable for work or any other ground like bad conduct etc. In such
a situation the Bidder must remove the concerned person and replace a suitable
person forthwith. The person so removed must not be engaged by the Bidder on
any project of CRIS/Railways.
13. It is the sole responsibility of Bidder to observe and abide by the provisions of
various statutory labour laws like Workmen’s Compensation Act, Factories Act,
minimum wage act and other Acts and regulations framed by the
Government/statutory authorities. CRIS shall not be responsible for any violation
of act or regulation by the Bidder or his staff. However, during currency of the
contract, any/all documentary proof to ensure compliance of applicable statutory
and mandatory laws shall be made available by the bidder to the representative
of CRIS.

Page 273 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

14. It shall be the responsibility of the bidder to ensure that only trained staff is
employed, and work permits are issued as per applicable rules and regulations.
15. In sections of the bid document, where the required manpower isn't specified,
the bidder must evaluate the necessary manpower to fulfil the scope of work.
Additionally, they should augment the workforce as needed to ensure timely
delivery of the project scope and meet project deadlines. The augmentation of
the manpower shall not be limited to any specific activity and needs to be met as
and when the project demands. CRIS decision in these matters shall be final to
meet the project demands.
16. The bidder also has to provide additional manpower as specified in the Schedule
of Requirements to ensure that the Change Request requirement of CRIS. The
requirement of the manpower for the change control shall depend on the
duration and extent of the work involved.
17. The bidder shall engage software testers and functional analysts to ensure that
the functional requirements are completely met during all phases of the project.
The functional analysts shall also be used to refine the proposed solution by
analysing the proposed system and propose refinements to be implemented.
18. NDA as per Annexure-21-Non-Disclosure Agreement to be signed by the
MSI.

17.9. CRIS’s Responsibility

1. CRIS shall appoint an official as coordinator for the project.
2. The Edge devices installed in the Coaches, Locomotives, EMU’s and MEMU’s will
be provided by CRIS.
3. Assist and coordinate with CRIS internal stake holders, Indian Railways and other
Government agencies for providing the relevant and additional information
wherever applicable for the integrations.
4. Assist in explaining the Functional Requirement Specifications
5. Provide detailed information on the integrations required with the Indian
Railways applications.
6. Assist in engaging the Subject matter Experts on the Indian Railways
applications to help the Bidder better understand the integration requirements.
7. Provide clarifications on the RDSO specifications wherever applicable to the
CVMS solution.

Page 274 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.10. Clarification Sought by Bidders

Bidders requiring any clarification on the bid document may notify CRIS in writing
by e-mail within such date as specified in the IREPS portal. All correspondence /
enquiries/ request for clarifications shall be submitted in the format as specified in
Annexure-16-Format For Pre-Bid Queries to the Point of Contact from CRIS
specified in the IREPS Portal (https://www.ireps.gov.in/ ) in writing by e-mail and
shall have the following as subject:

Queries/Clarifications regarding the bid document for Selection of Central

Video Management System (CVMS) for the IP-based CCTV Surveillance
System at Public Cloud for the Indian Railways.

CRIS shall endeavour to respond to the queries raised or clarifications sought by

the Bidders. However, CRIS reserves the right not to respond to any query or
provide any clarification, in its sole discretion, and nothing in this clause shall be
construed, taken or read as compelling or requiring CRIS to respond to any query
or to provide any clarification. CRIS may, also on its own, if necessary, issue
interpretations and clarifications to all Bidders. All clarifications and
interpretations issued in writing by CRIS shall be deemed to be part of the bid
document. Verbal clarifications and information given by CRIS, or their
employees, advisors or representatives shall not in any way or manner be
binding on CRIS.

17.11. Deviations
The bidder shall certify that the offered device fully meets the Functional Design and
Technical Requirements. Various design features incorporated in the device to fulfil
different technical performance requirements shall be fully explained in the offer.
However, in case of deviations, the bidder must state the deviations in the deviation
tab on the bidding interface of IREPS, and clearly explain how the equipment will still
meet the requirements despite the deviations.

17.12. Disqualification
Even if the Bidder meets the guidelines as set forth in the bid document, CRIS, at its
discretion, may disqualify any Bidder if:

Page 275 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

i. The Bidder (or any of the member in case of a JV/ Consortium) has been
blacklisted by the Purchaser / any other entity of Government of India or any
state government in India; or
ii. The Bidder has made misleading or false representation in the forms,
statements and attachments submitted.

Page 276 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.13. Functional Compliance Requirement from MSI

Sr.
Functional Description Compliance (Y/N) Cross Reference
No.
1.
2.
3.
4.
5.
Table 33:Function Compliance Requirement from MSI
Note: The MSI shall provide the cross-referencing of each functional requirement
specified in the bid document and align them with the relevant information from
proposed solution/product datasheets, brochures, or URLs of publicly available
information from the respective proposed OEMs or CSPs.

17.14. Modification and Withdrawal of Proposals

i. The Bidder may modify, substitute, or withdraw its Proposal after submission,
provided that written notice of the modification, substitution or withdrawal is
received by CRIS prior to the Proposal Due Date. No Bid shall be modified,
substituted, or withdrawn by the Bidder on or after the Proposal Due Date.
ii. Any alteration/modification in the Proposal or additional information supplied
after the Proposal Due Date, unless the same has been expressly sought for
by CRIS, shall be disregarded. No change in the substance of the Proposal
would be permitted by way of such alteration/modification in the Proposal or
additional information.

17.15. Confidentiality

The Bidding Documents and any other information shared by CRIS related to the
Project shall be confidential information of CRIS.

Page 277 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.16. Clarifications Sought by CRIS

To assist in the process of evaluation of Proposals, CRIS may, at its sole
discretion, ask any Bidder for any clarification with respect to its Proposal. The
request for clarification and the response shall be communicated by letter/ fax/
email. The Bidder in such cases would need to provide the requested
clarification / documents promptly and within 7 calendar days. No change in the
substance of the Proposal would be permitted by way of such clarifications.
17.17. Priority of Clauses
This tender document Part-II, including its Schedules and Annexures,
represents the entire agreement between the Parties as noted in this clause. If
in the event of a dispute as to the interpretation or meaning of this Agreement, it
should be necessary for the Parties to refer to documents forming part of the
bidding process leading to an Agreement, then such documents shall be relied
upon and interpreted in the following descending order of priority:
i. Valid and authorized amendments issued to this tender document Part-II.
ii. This tender document Part-II
iii. Service Levels/SLA
iv. NDA Agreement and Integrity Pact
v. Schedules and Annexures of this Agreement
vi. Letter of Award
vii. The Bid Document Part-II along with subsequently issued
corrigenda/clarifications.
viii. Any other document listed in the Bid Document Part-II as forming part of this
Agreement.
ix. Technical and financial proposal submitted by the Successful Bidder/ Vendor/

MSI, to the extent they along with subsequently issued clarifications furnished
by the Vendor in response to this Bid Document (and the same have been
explicitly agreed-to by CRIS), to the extent they are not inconsistent with any
terms of the Bid Document.
For the avoidance of doubt, it is expressly clarified that in the event of a conflict
between this tender document, Annexures / Schedules or the contents of the Bid
Document, the terms of this Agreement shall prevail over the Annexures /
Schedules and Annexures / Schedules shall prevail over the contents and
specifications of the Bid Document and the Bid Document shall prevail over the

Page 278 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

contents and specifications of the technical and financial proposal submitted by

the Vendor with their clarifications and responses to Bid Document."

17.18. Evaluation Methodology

This is a two-bid packet tender and Bids shall be of two parts namely techno-
commercial and financial. The bid evaluation process shall be as under:

17.18.1. Techno-Commercial evaluation

17.18.1.1. Step I –Commercial responsiveness &Pre-Qualification (PQ)
Criteria
I. CRIS will examine commercial responsiveness for all the bids as first step. Bid shall
comply with mandatory commercial responsiveness requirements i.e., earnest
money. CRIS will examine commercially responsive bids for compliance of
Qualification criteria (Refer Section Qualifications Criteria). Any bid which either is
commercially not responsive or does not meet the qualification criteria shall be
summarily rejected. However, CRIS reserves the right to seek clarification from the
Bidders at the stage of assessing compliance to Qualifications Criteria.
II. Only the bids that are commercially responsive and meet the Qualifications
Criteria shall be considered for technical evaluation. However, CRIS also reserves
the right to seek clarification pertaining to technical evaluation at the stage of
assessing compliance to Qualifications Criteria. This shall not tantamount to such
bids being considered to be fulfilling the Qualifications Criteria.

17.18.1.2. Step II - Technical Evaluation

I. As part of Technical evaluation, the documents sought vide Refer Section
Qualifications Criteria shall be inspected. Bidder is required to do a presentation at
CRIS on the offered solution which shall inter-alia include proposed system
architecture, products offered, skill sets, support services, tie-up with OEMs, project
implementation plan etc.
II. Bidders are expected to submit a complete Proposal in the format and manner
specified in Annexure-7-Bidder’s Checklist. All the required documents and details
must be included. In the absence of the same, leading to material deviation or
reservation, the Proposal is liable to be rejected.
III. Additional features / enhancements offered by the bidder, over and above the once
asked for in the tender, shall not be taken into consideration for evaluation of bids.

Page 279 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

IV. A Proposal shall be considered responsive if it satisfies criteria stated below:

a. It contains the information and documents and, in the form, and manner as
requested in the bid document.
b. It mentions the Bid Validity Period as set out in Validity of Proposals.
c. It provides the information in reasonable detail. (“Reasonable Detail” means that,
but for minor deviations, the information can be reviewed and evaluated by CRIS
without communication with the Bidder). CRIS reserves the right to determine
whether the information has been provided in reasonable detail.
d. There are no inconsistencies between the Proposal and the supporting
documents.
e. It does not affect in any substantial way the scope, obligations, quality,
specifications, standards, rules, controls, and performance of the Project.
f. It does not contain any condition.
V. CRIS reserves the right to reject any Proposal which in its opinion is not responsive
and no request for modification or withdrawal shall be entertained by CRIS in
respect of such Proposals.
VI. Bidders meeting the Technical Evaluation process shall then asked to conduct the
Proof-of-Concept.
VII. Proof of concept (PoC) will be carried out for CVMS Solution for Bidders who will
qualify all the above-mentioned parameters listed in Section Proof of Concept of
this tender document. It is mandatory for the Bidder to clear the Proof-of-concept
stage to become eligible for financial bid opening.

17.18.2. Financial Evaluation of offers

I. Financial bid evaluation will only be done for Bidders which are declared to be
technically suitable.
II. The Financial bids of the bidders who are considered Substantially Technically
Responsive shall be opened at this stage. Financial bid will be opened electronically
on a specified date and time duly notified.
III. Additional features/enhancements of hardware/software components offered by the
bidder, over and above the ones asked for in the tender documents, shall not be
considered for evaluation of bids.
IV. Wherever CRIS finds it necessary to seek clarifications on the bidders offered
financial bid, the bidders shall provide the necessary clarifications within twenty-four
hours from the time CRIS seeks these clarifications. In case no response is

Page 280 of 455

 Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

received, CRIS may reject such bidder’s bids, citing commercially non-responsive
bids.
VII. For the purpose of relative ranking of offers, all-inclusive prices for entire Schedule
of Requirement (SoR) of the tender shall be considered. The Bidder, who has
submitted the lowest Commercial bid, shall be selected as the L1.

17.18.3. E-Reverse Auction (e-RA)

1. This tender is being issued with the stipulation of e-RA on IREPS Portal
(www.ireps.gov.in).
2. Bidder shall be simultaneously required to electronically submit a Techno-
commercial Bid and Financial Bid (Initial Price Offer).
3. Offers found eligible for ordering shall be categorized as ‘Qualified for Bulk
Order for the purpose of RA’.
4. Offers not complying with essential technical & commercial requirements of
the tender shall be declared as ‘Ineligible for award of contract’.
5. Initial Price Offer of only those bidders categorized as ‘Qualified for Bulk
Order’, shall be opened and Initial Price Offers shall be tabulated by IREPS, as
per instructions applicable for electronic tabulation.
6. Please refer User Manual for Vendors (Goods & Services) Version 1.0
available on IREPS website under learning center (user manuals) link.
7. Selection of bidders for conduct of Reverse Auction (e-RA):

Following conditions and procedure shall be followed in selection of bidders for conduct
of Reverse Auction (e-RA):

a. Selection of vendors for Reverse Auction(e-RA) for ordering:

Page 281 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

No. of tenderers No. of tenderers to Remarks

Qualified for be selected for e-RA
Bulk Order

Less than 3 Nil The bids disallowed from participating in the

Reverse Auction(e-RA) shall be the highest
bidder(s) in the tabulation of Initial Price
Offer.
3 to 6 3
In case the highest bidders quote the same
More than 6 50% of vendors rate, the Initial Price Offer received last, as
Qualified for Bulk per time log of IREPS, shall be removed
Order (rounded off to first, on the principle of last in first out, by
next higher integer) IREPS system itself.

Table 34: Selection of vendors for Reverse Auction(e-RA) for ordering

Note: If the number of tenderers qualified for Bulk Order/Award of Contract is less than 3,
RA shall not be done, and tender may be decided on the basis of Initial Price Offer(s).

b. Selection of vendors for Reverse Auction(e-RA):

i. MSEs criteria: All MSEs (Micro & Small Enterprises) found Qualified for award
of Contracts but could not be selected for Reverse Auction as per criteria
stipulated in clause 17.18.3 & 17.18.3 (a) above but are within the range of
15% of lowest Initial Price Offer of the bidder qualified for ordering shall be
permitted to participate in the Reverse Auction irrespective of their inter-se
ranking on the basis of initial Price Offer. Such MSEs shall be over and above
the number of vendors selected for Reverse Auction, as per clause 17.18.3 &
17.18.3 (a) above. The lowest initial price bid shall mean lowest initial price
bid of vendor qualified for ordering. However, in case of all the bidders
qualifying for ordering (before applying elimination criteria) are within MSE
category, this clause shall not apply.
ii. Make in India criteria: All bidders eligible for benefits under Public
Procurement (Preference to Make in India) Order – 2017, found qualified for
award of Contract and are within the specified range of purchase preference,
under the Make in India Policy, of lowest Initial Price offer of the vendor
qualified for ordering shall be permitted to participate in the Reverse Auction,
irrespective of their inter-se ranking on the basis of Initial Price offer. Such

Page 282 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

bidders shall be over and above the number of vendors selected for Reverse
Auction, as per clause 17.18.3 & 17.18.3 (a) above. However, if all the bids
qualified for ordering (before applying elimination criteria) also qualify under
“Make in India Order, 2017” criteria, this clause shall not apply.

c. Lowest initial price bid referred to in sub-clause (b) above shall mean lowest
initial price bid of vendor qualified for ordering.

d. After evaluation of the technical bids and selection of bidders as above, date and
time of start of e-RA shall be communicated to the qualified tenderers selected,
through system generated e-mail to their registered e-mail id. Bidders should
also check the date of e-RA after logging into their account on IREPS. No
representation on account of non-receipt of e-mail shall be entertained.

17.18.4. Procedure for conducting e-RA:

a. Purchaser shall fix the following parameters for e-RA:
i. Initial e-RA period (Initial Cooling off period): This shall be the initial time
interval for e-RA. e-RA shall be open for this duration.
ii. Auto extension period (Subsequent cooling off period): In case any offer is
received in the time period equal to auto extension period before close of initial
e-RA period, the e-RA shall be extended for time equal to auto extension
period from the time of last bid. There shall be no upper limit on number of
auto extensions. When no offer is received in the last auto extension period, e-
RA shall close.
iii. Minimum decrement: Minimum decrement in percentage of value of the last
successful bid.
b. During Reverse Auction (e-RA) period, identities of the participating tenderers will
be kept hidden.
c. Bidders will not be allowed to revise the Taxes & other levies, after submission of
Initial Price bid. Starting point for Reverse Auction (e-RA) shall be the lowest
Initial Price bid of the tenderer eligible for award of contract. During Reverse
Auction (e-RA) process, bidders shall not be allowed to bid a rate higher than the
lowest Initial Price offer. Minimum admissible bid value will be last bid value
minus minimum decrement as specified in Tender Document on IREPS before
starting of e-RA.

Page 283 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

d. Bidders shall not be allowed to withdraw their last offer.

e. L-1 will be defined as the lowest bid obtained after the closure of e-RA.

17.18.5. Applicable important conditions after e-RA:

a. The offers of bidders which were eliminated i.e., not selected for participation in
e-RA in terms of clause 17.18.3 above shall not be considered for any ordering.
All the relevant Policies of Government of India at the relevant time shall be
applicable.
b. On submission of final price offers through Reverse Auction, it shall be construed
that the tenderer has revalidated the original validity of the offer for further ninety
(90) days from the date of e-RA.

17.18.6. Notification
CRIS will notify the Successful Bidder by a letter of award (“Letter of Award” or
“LoA”) that its Proposal has been accepted.

17.18.7. Performance Security

i. The Successful Bidder shall be required to furnish a Performance Security for
a sum equal to [10%] of the Price Proposal Value, in accordance with the
format provided in Annexure-17-Performance Bank Guarantee, prior to the
signing of the Agreement. The Performance Security shall be kept valid till 6
months beyond contract period.
ii. The Performance Security shall be in the form of an irrevocable Bank
Guarantee issued by any Indian Nationalized Bank or a Scheduled Bank, in
favour of “Center for Railways Information Systems”. In case the bank
guarantee towards the Performance Security is issued by any bank outside
New Delhi, the same shall be routed through their branch in New Delhi and
enforceable at New Delhi. For the avoidance of any doubt, ‘Scheduled Bank’
shall mean a Bank as defined under Section 2(e) of the Reserve Bank of
India Act, 1934.
iii. Failure of the Successful Bidder to comply with the requirements above shall
constitute sufficient grounds for the annulment of the LoA, and forfeiture of its
Bid Security. In such an event, CRIS reserves the right to,
a. consider the Bidder with next highest Composite Score as Preferred
Bidder.

Page 284 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

b. take any such measure as may be deemed fit in the sole discretion of
CRIS, including annulment of the Bidding Process

17.19. Contract Period

The contract period shall remain in force up to a period of Eight Years (8) from the date
of Phase 1 Go-Live unless terminated earlier in accordance with the contract terms.
CRIS at its sole discretion may extend the contract up to an additional period of 24
Months with the same terms and conditions. Any such extension shall be binding on the
MSI. The minimum guarantees stipulated in Section Payment Terms shall not be
applicable during the extended period.

17.20. Long Term Support

The Bidder shall ensure that the Original Equipment Manufacturers (OEMs) of the
supplied software and solutions commit to providing comprehensive technical support,
including but not limited to software updates, patches, and troubleshooting assistance,
for the Contract Period from the date of the final acceptance of the delivered products.
The Bidder shall be responsible for including contractual obligations with the OEMs to
guarantee this extended support period. Failure to secure such commitments may result
in disqualification of the bid. The Bidders shall provide Undertakings from each of the
OEMs who are providing software solutions in the bid document as per Annexure-37-
OEMs Technical Support in India.

17.21. Change Control

Note: The Change Control Request can be initiated only after completion of a
period of One year from the date of Phase 1 Go-Live (Refer Section Payment
Terms, Deliverables & Timelines).
This Section describes the procedure to be followed in the event of any proposed
change to the Scope of Work of the Master Systems Integrator (MSI).
CRIS and MSI recognize that change is an inevitable part of delivering services and
that a significant element of this change can be accomplished by re-organizing
processes and responsibilities without any effect on the cost. The MSI shall refer to
the Section Change Management Process to understand under what conditions the
Change Management Process shall be initiated. CRIS will offer all necessary
cooperation in this regard. In the subsequent sections, the activities where change
management is applicable or not applicable are elaborated.

Page 285 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.21.1. Change Management Process

i. Scope of Change Management Process:

Under the Change Management Process, the following types of activities shall
be considered:

ii. Activities for which change management will be considered:

a. Only activities which are already not covered in the scope of work of this
tender document, any subsequent corrigenda or the contract shall be
considered for initiation of Change Management.
b. Activities requiring an effort less than or equal to two-man months, shall
not be considered for initiation of Change Management.

iii. Activities for which change management will not be considered:

a. The requirements outlined in the Bid document Part-II serve as minimum
guidelines and are subject to further detailing during the preparation of the
Requirement gathering phase and the Design phase before implementing
the complete CVMS solution. The MSI is accountable for fulfilling all
technical specifications specified in the Bid document Part-II, including any
necessary adjustments or additions to quantities and specifications. These
modifications during project execution do not require formal change
requests and should be implemented promptly without affecting the project
timeline or budget.
b. Any additional revisions or enhancements needed to align the MSI's
CVMS components and installation procedures with the requirements
outlined in the tender document, ensuring overall facility safety,
functionality, and adherence to industry best practices, will not be
considered as a change order.
c. Revisions or additions resulting from errors, omissions, ambiguities, or
discrepancies in the tender document that were not previously highlighted
by the MSI to CRIS during the bidding process will not be considered as a
change order.
d. Optimizing and fine-tuning the Cloud infrastructure and other components
of the CVMS solution to ensure the expected uptime throughout the entire
contract duration.
e. Any customization or enhancements in CVMS solution stack.
f. Refinements of existing processes.

Page 286 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

g. Establishment of new Standard Operating Procedures and its respective

related workflows and dashboards.
h. Configuration changes.
i. Changes to the Dashboard and any customisation.
j. Documentation revision updates.
k. Establishment of new service levels.
l. Any other activity covered in scope of O&M (refer Operations Phase (Post
Final Go-Live of the Project)).

iv. Change Control Note ("CCN")

a. Change requests in respect of the Scope of work will emanate from MSI
based on specific request from CRIS, based on which the MSI shall
submit a formal change request proposal with all required details and
obtain approval for the change from CRIS. The MSI will complete Part A of
the CCN attached as Annexure-18-Change Control hereto and present it
to CRIS.
b. For arriving at the cost / rate for change, the relevant rates as specified in
Section Schedule of Requirement (SOR) shall apply.

Note: In case of any difference of opinion on these matters, the decision of

CRIS shall be final and binding.

v. Quotation
a. Based on the discussions with CRIS, The MSI shall assess the CCN and
complete Part B of the CCN, in completing the Part B of the CCN the MSI
shall provide as a minimum:

1. A description of the change.

2. A list of deliverables required for implementing the change.
3. A timetable for implementation.
4. An estimate of any proposed change.
5. Relevant acceptance criteria before deployment.
6. An assessment of the value of the proposed change.
7. Material evidence to prove that the proposed change is not already
covered within the Agreement and the scope of work.
b. Prior to submission of the completed CCN to CRIS, the MSI will undertake
its own internal review of the proposal and obtain all necessary internal
approvals. As a part of this internal review process, the MSI shall consider

Page 287 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

the scope of the proposed change in the context of the Agreement and the
scope of work affected by the change and the total effect that may arise
from implementation of the change.
vi. Costs

Each Party shall be responsible for its own costs incurred in the preparation of
CCNs. For discharging any approved work by the MSI as part of approved CCN,
CRIS agrees to pay to MSI the approved amount corresponding to the work as
per the agreed terms.

vii. Obligations

The MSI shall be obliged to implement any proposed changes once approval in
accordance with above provisions has been given, with effect from the date
agreed for implementation and within an agreed timeframe after a formal
Amendment to Purchase Order/Contract is issued by CRIS. The MSI shall not
be authorised to work on a change unless it has been approved by CRIS.

viii. Manpower to be provided for Change Request

For implementation of change management which involves providing manpower for

the enhancement in the CVMS Solution to be availed by CRIS in case of additional
changes or enhancements are required in the Operational CVMS Solution Stack, the
bidder shall be asked to propose the required manpower resources as per the below
guidelines provided in this tender document:

a. Minimum qualifications should be an engineering graduate with

development experience of 10 years in the relevant domain.
b. Candidates should have implemented similar development works
(minimum of 2-3 similar projects). Relevant Project Credentials which may
include Client end references, project details, etc. to be submitted by the
Candidate.
c. Candidates shall be approved by CRIS.

17.22. Miscellaneous
i. Independent Contractor

Nothing in this tender document Part-II shall be construed as establishing or

implying any partnership or joint venture between the Parties to this tender

Page 288 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

document and, except as expressly stated in this tender document Part-II.

Nothing in this tender document Part-II shall be deemed to constitute a Party
as the agent of the other Party or authorizes either Party to:
a. incur any expenses on behalf of the other Party.
b. enter into any engagement or make any representation or warranty on
behalf of the other Party.
c. pledge the credit of or otherwise bind or oblige the other Party; or
d. commit the other Party in any way whatsoever without in each case
obtaining the other Party’s prior written consent.

ii. Sub-contractors

MSI shall normally not be permitted to subcontract. Any other activity may be
subcontracted only with CRIS’s prior written consent. The MSI shall provide
CRIS with a list of all the services planned to be subcontracted, within 30 days
of signing the Agreement. It is clarified that the MSI shall be the principal
employer for all claims arising from the liabilities statutory or otherwise,
concerning any of the subcontractors engaged by it. The MSI undertakes to
indemnify CRIS from any claims on the grounds stated hereinabove.

iii. Assignment
a. All terms and provisions of this Agreement shall be binding on and shall
inure to the benefit of CRIS and its successors and permitted assigns.
b. The MSI shall not be permitted to assign its rights and obligations under
the agreement to any third party.
c. CRIS may assign or novate all or any part of the agreement and the MSI
shall be a party to such novation, to any third party contracted to provide
services to CRIS.

iv. Change in Law

a. "Change in Law” means occurrence of any of the following events after the
Proposal Due Date having an impact on the Project:

1. enactment of any new Indian law.

2. the repeal in whole or in part (unless re-enactment with the same
effect) or
3. modification of any existing Indian law.

Page 289 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

4. the change in interpretation or application of any Indian law by a

judgment of a court of record which has become final, conclusive, and
binding, as compared to such interpretation or application by a court of
record prior to the date of the Agreement.
5. the imposition of a requirement for a permit not required on the date of
the agreement.
6. any order, decision, or direction of a court of record.
7. any other government notification.
8. Provided, however, Change in Law shall not include:
9. coming into effect, after the date of execution of the agreement, of any
provision or statute which is already in place as of the date of
execution of the agreement.
10. non-availability of any spare part, systems, and applications due to
price escalation or otherwise.
b. In the event of a Change in Law, and such change has a material adverse
effect, the MSI shall notify CRIS the nature and the impact of Change in
Law on the Agreement and the Project. Upon receipt of such notice, CRIS
and the MSI will hold discussions and consultations in relation thereof in
good faith to agree to such modifications to the Agreement as may be
acceptable to both the Parties, and in the event any agreement cannot be
reached, the Parties shall follow the Dispute Resolution Procedure as
mentioned in CRIS EGCC.

v. Notices
a. Any notice or other document which may be given by either Party under
the agreement shall be given in writing in person to the authorized
personnel (under acknowledgement) or by speed-post.
b. In relation to a notice given under the agreement, any such notice or other
document shall be addressed to the other Party’s principal or registered
office address.
c. Any such notice or other document shall be deemed to have been given to
the other Party when delivered (if delivered in person) if delivered between
the hours of [9.30 am and 6.00 pm] on working day at the address of the
other Party set forth above, or on the next working day thereafter if
delivered outside such hours, and 7 days from the date of posting (if by
letter).

Page 290 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

d. Either Party to the Contract Agreement may change its address, telephone
number, facsimile number and nominated contact for notification purposes
by giving the other reasonable prior written notice of the new information
and its effective date.

vi. Variations and Further Assurance

a. No amendment, variation or other change to the Agreement shall be valid
unless made in writing and signed by the duly authorised representative of
CRIS.
b. Each Party to the Agreement agrees to enter into or execute, without
limitation, whatever other agreement, document, consent and waiver and
to do all other things which shall or may be reasonably required to
complete and deliver the obligations set out in the agreement.

vii. Severability and Waiver

a. If any provision of the Agreement, or any part thereof, shall be found by
any court or administrative body of competent jurisdiction to be illegal,
invalid, or unenforceable the illegality, invalidity or unenforceability of such
provision or part provision shall not affect the other provisions of the
Agreement or the remainder of the provisions in question which shall
remain in full force and effect. The Parties shall negotiate in good faith in
order to agree to substitute for any illegal, invalid or unenforceable
provision with a valid and enforceable provision which achieves to the
greatest extent possible the economic, legal and commercial objectives of
the illegal, invalid or unenforceable provision or part provision.
b. No failure to exercise or enforce and no delay in exercising or enforcing on
the part of either Party to the agreement of any right, remedy or provision
of the Agreement shall operate as a waiver of such right, remedy or
provision in any future application nor shall any single or partial exercise or
enforcement of any right, remedy or provision preclude any other or further
exercise or enforcement of such right, remedy or provision or the exercise
or enforcement of any other right, remedy or provision.

viii. Compliance with Applicable Law

Page 291 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Each Party to the agreement accepts that its individual conduct shall, to the
extent applicable to its activities, at all times comply with all laws, rules and
regulations of government and other bodies having jurisdiction over the area
in which the Services are undertaken provided that changes in such laws,
rules and regulations which result in a change to the Services shall be dealt
with in accordance with the Change Control Schedule set out in bid
document part-II.

ix. Professional Fees

All expenses incurred by or on behalf of a Party to the agreement, including

all fees of agents, legal advisors, accountants, actuaries etc, employed by
either of the Parties in connection with the preparation and execution of the
agreement shall be borne solely by the Party which incurred them.

x. Ethics

The MSI represents, warrants, and covenants that it has given no

commitments, payments, gifts, kickbacks, lavish or expensive entertainment,
or other things of value to any employee or agent of CRIS in connection with
the agreement and acknowledges that the giving of any such payment, gifts,
entertainment, or other things of value is strictly in violation of CRIS’s
standard policies and may result in cancellation of the agreement.

xi. Entire Agreement

The agreement with all schedules and annexures appended thereto

constitute the entire agreement between the Parties with respect to their
subject matter. Nothing in this clause shall be interpreted to exclude any
liability in respect of fraudulent misrepresentation.

xii. Manpower deployed for the Project

The bidder shall deploy the qualified manpower as stipulated in Annexure-

23-Deployment of Manpower for the respective phases of the project
namely for the Project Phase as well as the Operations Phase of the Project.

Page 292 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

The MSI shall submit the CVs of the manpower being deployed for the
different phases of the project and shall seek approval from CRIS before
deployment within two weeks of the issue of the Purchase Order. CRIS
reserves the right to request a replacement of any manpower found to be not
meeting the project requirements. Such replacements shall be provided by
the MSI within seven (7) working days. This clause is not only applicable for
the manpower deployed for the helpdesk but also for any other type of
manpower that has been deployed by the MSI for the CVMS project.
Wherever required the MSI shall provide additional and adequate manpower
to meet the Milestone timelines of the project.

xiii. Compliance to Regulations

The MSI must comply with all government regulations in India and provide
proof of adherence to CRIS wherever demanded.

17.23. Exit Management/Transition-out-service

1. The Exit management period starts, in case of expiry of contract and/or with
immediate effect on receiving the Notice of termination from CRIS in violation of
terms of contract or failure to perform the Project as per terms of contract.
2. Comprehensive exit Management plan shall be furnished by the MSI before
Phase 1 Go-Live phase in consultation with CRIS. Failure to do so can be a
ground for CRIS to issue notice of termination.
3. Listed below are some of the key responsibilities of the MSI during the exit
management process which shall be delivered at no additional cost to CRIS:
a. Upto six months of the contract period or during the contract period, if any
other agency is identified or selected for performing the Project (as specified
in bid document part II, scope of work), the MSI shall ensure that a complete,
proper and satisfactory handover is made. If any upgrade, is required, the
MSI shall carry out the same at no extra cost to the CRIS.
b. MSI shall be responsible for migration of the Virtual Machine’s, data, content
and any other assets to the new environment provided by CRIS and/or other
nominated agency and ensuring successful deployment and running of the
CVMS solution on the new infrastructure by suitably retrieving all data,
scripts, software, virtual machine images, and so forth to enable mirroring or
copying.

Page 293 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. The format of the data transmitted from the CSP to the Department should
leverage standard data formats (e.g., OVF,VHD...) whenever possible to ease
and enhance portability.
d. MSI shall ensure the compliance of data protection laws and regulations in
force during the data transferring and storage throughout the exit process and
shall comply with terms specified in subpoints 14 and 15 below.
e. MSI shall be responsible for providing the tools for import / export of VMs &
content to the CRIS and/or the other nominated agency/ agencies. The
mechanism and technical requirements for achieving this should be well
documented post consultation from CRIS.
4. As part of the Exit management, the MSI shall develop a detailed handover
document outlining key project details, contact information, and any ongoing or
outstanding tasks which shall be provided to CRIS within period decided by
mutual agreement of MSI and CRIS.
5. The MSI shall ensure to provide the telephonic support of key persons related to
CVMS solution to CRIS and /or nominated agency upto six months after contract
period.
6. The MSI shall also be responsible for all the activities required to training and
transfer the knowledge to the CRIS and/or CRIS nominated agencies to ensure
similar continuity and performance of the Services post expiry of the Contract.
7. The MSI shall organize knowledge transfer sessions to share insights, leading
practices, and critical information with CRIS.
8. The MSI shall re-draft the Exit Management Plan annually thereafter (as may be
required) to ensure that it is kept relevant and up to date and should be approved
by CRIS.
9. During the exit/transition management process, the MSI shall ensure that the
MSI and the CSP addresses and rectifies any of the problems with respect to
migration of CRIS applications and related including installation/reinstallation of
the system software, etc.
10. The ownership of the data generated upon usage of the system, at any point of
time during the contract or expiry or termination of the contract, shall rest
absolutely with CRIS.
11. MSI shall ensure that document details of any third-party integrations, including
APIs, libraries, and services used in the integration are shared with CRIS and/or
other nominated agency by CRIS.
12. The MSI shall share information about security measures implemented in the
Project and provide details on compliance requirements and any measures taken
to meet those standards.

Page 294 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

13. In addition to the Performance Bank Guarantee and liquidated damages, in case
the MSI fails to deliver the obligations as specified under this Exit Management
clause within the stipulated timeframe, CRIS reserves the right to impose an
additional penalty up to 10% of the contract value and or take further measures
such as seek legal recourse, blacklisting the firm, etc.
14. In the event where MSI is non-compliant due to violation of any of the terms of
the bid/contract or violates the applicable law, CRIS reserves the right to issue a
notice for termination of the contract. Under such circumstances, the MSI shall
ensure that all data stored on the Public Cloud is promptly and fully handed over
to CRIS as per the scope elaborated in the Exit Management at no additional
cost to CRIS.
15. Once exit process is completed, MSI shall remove the data, content and other
assets from the cloud environment and terminate the VM, content and data of the
CVMS solution as per stipulations & shall ensure that data cannot be forensically
recovered.
16. MSI/CSP shall not delete any data at the end of the agreement (for a maximum
of 45 days beyond the expiry of the Agreement) without the express approval of
the CRIS. Any cost for retaining the data beyond 45 days shall be paid to the
Service Provider based on the cost indicated in the commercial bid.

17.24. Intellectual Property Rights

The Intellectual Property Rights (IPR) for the Bespoke Software, upon its creation, shall
vest with CRIS. CRIS shall be free to license/sell/deploy the Bespoke Software to any
third party. CRIS grants to the MSI and its sub-contractors for Bespoke Software a
nonexclusive, royalty free license during the Contract Period to exercise such of the
Intellectual Property as the MSI reasonably requires performing their obligations under
the agreement. The MSI agrees and acknowledges that it has no rights to exploit the
Intellectual Property Rights vested in Bespoke Software for any purpose other than for
providing Services under the Agreement.

17.25. Audit, Access & Reporting

The Master System Integrator shall allow access to CRIS or its nominated agencies
to all information which is in the possession or control of the MSI, and which relates
to the provision of the Services for Audit, Access and Reporting.

Page 295 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.25.1. Audit Notice and Timing

i. CRIS or its nominated agency shall conduct routine audits in accordance with
agreed timetable and shall not be required to give the Master System
Integrator any further notice of carrying out such audits (Refer Section
Payment Terms, Deliverables & Timelines).
ii. CRIS or its nominated agency may conduct non-timetabled audits at their
own discretion if they reasonably believe that such non-timetabled audits are
necessary as a result of an act of potential fraud by the MSI, a security
violation, or breach of confidentiality obligations by the MSI. The MSI shall
provide all necessary support to conduct such audits. Any lack of support/
cooperation from the MSI shall be construed as a breach of contract.

17.25.2. Annual OEM Audits

The MSI shall ensure that an annual audit is conducted by each of the OEMs
whose solutions has been provided for the CVMS solution, for their respective
components & software. On completion of the audits, the respective OEMs
should provide an undertaking as per ANNEXURE-43- Certificate for I&C and
Annual Audits validating the operational configuration status / efficiency /
effectiveness of the components & software that are being used for the delivery
of the CVMS solution to CRIS. The annual OEM audits shall be conducted at no
additional cost to CRIS.

17.25.3. Access
The MSI shall provide to CRIS or its nominated agency reasonable access to
employees, sub-contractors, suppliers, agents and third-party facilities,
documents, records, and systems reasonably required for audit and shall
provide all such persons with routine assistance in connection with the audits
and inspections. CRIS shall have the right to copy and retain copies of any
relevant records. The MSI shall make every reasonable effort to co-operate with
them.

17.25.4. Audit Rights

i. CRIS or its nominated agency shall have the right to audit and inspect
suppliers, agents and third-party facilities, documents, records, procedures
and systems relating to the provision of the Services, but only to the extent

Page 296 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

that they relate to the provision of the Services, as shall be reasonably

necessary to verify:
a. the security, integrity and availability of all data processed, held or
conveyed by the Systems.
b. Integrator on behalf of CRIS and documentation related thereto;
c. that the actual level of performance of the services is as per the Service
Level;
d. that the MSI has complied with the relevant technical standards, and has
adequate internal controls in place;
e. the compliance of the MSI with any other obligation under the Agreement.
f. For the avoidance of doubt the audit rights under this Schedule shall not
include (a) access to the MSI’s profit margins or overheads, or (b) any
confidential information relating to the Systems.
g. Integrator’s employees, or (c) minutes of its internal Board or Board
committee meetings including internal audit, or (d) such other information
of commercial-in-confidence nature which are not relevant to the Services
or associated with any obligation under the Agreement.

17.25.5. Records And Information

For the purposes of audit in accordance with this Schedule, the MSI shall
maintain true and accurate records in connection with the provision of the
services and the MSI shall handover all the relevant records and documents
upon the termination or expiry of the Agreement.

17.26. Quality Control Measures

The MSI shall implement quality control measures for all aspects of the project during
the Project implementation phase as well during the subsequent operations phase of
the project. In its proposal, the MSI shall elaborate the complete Quality Control and
assurance measures that shall be implemented during the project as well as during the
operations phase of the project. Quality measures may range across the following areas
but not limited to:

i. Shall clearly define quality criteria for each system and application of the
CVMS solution, including the video management system, command and
control center, facial recognition, video summarization, video forensics, and
enterprise management systems.

Page 297 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

ii. The MSI shall identify the requirements of the CVMS Solution, determining
the quality objectives, and defining the processes and procedures that will be
used to achieve those objectives.
iii. The systematic monitoring and evaluation of the processes and procedures
used to provide the service to ensure that they meet the specified
requirements.
iv. Identification and implementation of improvements to the processes and
procedures used to produce the product or service to increase efficiency,
effectiveness, and customer satisfaction.
v. Based on the requirements, the MSI shall identify the quality objectives that
need to be achieved. These objectives shall be specific, measurable,
achievable, relevant, and time bound.
vi. The MSI shall provide a quality management plan which shall include the
quality planning process, quality assurance process, quality control process,
and continuous improvement process as part of their proposal.
vii. The MSI shall provide a detailed quality management plan post Phase 1 Go-
Live, that outlines the specific processes and procedures that will be used to
achieve the quality objectives. The plan shall include a schedule, roles and
responsibilities, and any necessary resources to meet the quality objectives.
viii. The MSI shall conduct quality checks of the various components of the CVMS
in accordance with the quality plan and submit an outcome report to CRIS on
quarterly basis.

17.27. Termination of the Contract

CRIS reserves the right to cancel the contract placed on the Successful Bidder and
forfeit the Performance Security under the following circumstances:

a. The Selected Bidder commits a breach of any of the terms and conditions of the
contract.
b. CRIS may, without prejudice, to any other remedy for breach of contract, by
written notice of default sent to the vendor terminate the contract in whole or part
thereof if:
i. The vendor fails to deliver any or all of the obligations within the time
period(s) specified in the contract, or any extension thereof granted by the
client.
ii. The vendor fails to perform any other obligation(s) under the contract.

Page 298 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

In case of any change in the statutory laws which shall prohibits performance of
this contract, CRIS shall be within its rights to cancel the contract and refund the
Performance Security.

c. Time is the essence of the Agreement and the delivery dates are binding on the
Implementation Agency, hence if the successful Bidder fails to operationalise the
project or is unable to meet the milestones of the Phase 1 Go-Live or Final Go-
Live as per the timelines prescribed in the bid document part-II and the extension
if any allowed. CRIS reserves its right to cancel the contract.
d. The MSIs ability to survive as an independent corporate entity is threatened or is
lost owing to any reason whatsoever, including inter-alia the filing of any
proceedings for bankruptcy, insolvency or winding up against the MSI or an
appointment of receiver, liquidator, assignee, or similar official against or in
relation to the MSI, any failure by the MSI to pay any of its dues to its creditors,
the institution of any winding up proceedings against the MSI or the happening of
any such events that are adverse to the commercial viability of the MSI.
e. If deductions on account of penalties & liquidated damages exceeds more than
the limits defined for the liquidated damages in this bid document part-II.
f. The MSI or its team has failed to comply with or is in breach or contravention of
any law of the land.
g. MSI is ordered to be wound up by a court of law, except for the purpose of
amalgamation or reconstruction provided that, as part of such amalgamation or
reconstruction, the property, assets and undertaking of MSI are transferred to the
amalgamated or reconstructed entity and that the amalgamated or reconstructed
entity has unconditionally assumed the obligations of MSI under this Agreement
and provided that:
i. the amalgamated or reconstructed entity in the opinion of the
Purchaser has the technical capability and operating experience
necessary for the performance of its obligations under this contract;
and
ii. the amalgamated or reconstructed entity has, in the opinion of the
Purchaser, the financial standing to perform its obligations under this
contract; and
iii. this Agreement remains in full force and effect;

Page 299 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.28. Documentation
The bidder shall be responsible for the creation / updation of documents pertaining to
various activities outlined in the tender document, including but not limited to the
requirement gathering phase, design phase, development phase, implementation
phase, Proof-of-concept, UAT, PAT, O&M phase, trainings, multiple versions of SoPs,
and any other relevant documentation required throughout the contract period and
providing copies of the same to all stakeholders. The bidder shall ensure that version
control mechanisms are implemented and maintained for each type of document
created.

Furthermore, all documents shall be stored on a central repository hosted on the same
public cloud platform. The central repository shall be subject to Role-Based Access
Control (RBAC) measures to manage and control access to the documents.

The bidder shall be responsible for maintaining these documents for the entire duration
of the contract period. Upon completion or termination of the contract, the bidder shall
ensure that all documents are handed over to CRIS as part of the exit management
process.

Page 300 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.29. Make In India

1. Only ‘Class-I local supplier’ and ‘Class-II local supplier’, as defined

under the Order No.-P-45021/2/2017-PP (BE-II) dt.4th June 2020
issued by Ministry of Commerce and Industry & reiterated by Railway
Board Order No.-2020/RS (G)/779/2 dt.12.06.2020 as read with Order
No.-P-45021/2/2017-PP (BE-II) dated September 16, 2020 of Ministry
of Commerce and Industry & reiterated by Railway Board Order no.-
2020/RS (G)/779/2/Pt.1 dt.25.09.2020, along with subsequent
instructions in this regard which have been issued till closing of this
tender, shall be eligible to bid in this tender. OM No.-P-
45021/102/2019-BE/II/Part(1)(E-50310) dt 04/03/2021 of Ministry of
Commerce and Industries & reiterated by Railway Board Order No.-
2020/RS (G)/779/2-Pt-I dt.17.05.2021 shall also be applicable.
2. ‘Class-I local supplier’ means a supplier or service provider, whose
goods, services or works offered for procurement, meets the local
content requirement of minimum 50%.
3. ‘Class-II local supplier’ means a supplier or service provider, whose
goods, services or works offered for procurement, meets the local
content requirement of minimum 20% but less than that prescribed for
‘Class-I Local Supplier’.
4. ‘Non local supplier’ means a supplier or service provider, whose
goods, services or works offered for procurement, has local content
less than that prescribed for ‘Class-II Local Supplier’. Any offer
submitted by ‘Non local supplier’ against this tender shall not be
considered and summarily rejected.
5. The margin of Purchase Preference to ‘Class-I local supplier’ shall be
20%. ‘Class-II local supplier’ and ‘Non local supplier’ shall not be
eligible for any Purchase Preference in this tender.
a) The Subject tender is not divisible in nature and the ‘Class-I
local supplier’ shall get purchase preference over ‘Class-II
local supplier’. ‘Class-II local supplier’ will not get any
purchase preference.
b) The procedure for Purchase Preference to be followed in this
tender shall be as per Para-3A(c) of the aforesaid Order
No.P-45021/2/2017-PP (BE-II) dated September 16, 2020.

Page 301 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c) Verification of Local Content: The bidders are required to

furnish required Certificate as defined in Para-9 of Order
No.P-45021/2/2017-PP (BE-II) dated September 16, 2020.
Submission of the requisite Certificate for verification of
Local Content is mandatory.

6. Definitions of various terminologies w.r.t. Public Procurement

(Preference to Make in India) Order-2017 shall be as per various
Orders issued by Ministry of Commerce and Industry &/or reiterated by
Railway Board from time to time..

17.30. Land Border with India Compliance

Bidders shall read Clause 34 & its sub-Clauses and Clause 35 & its sub-Clauses of
EGCC (available on https://cris.org.in/crisweb/design1/indexorg.jsp?t=6) very
carefully and will submit the certificate for Compliance regarding restrictions on
procurement from a Bidder of a country which shares a land border with India and on
subcontracting to contractors from such countries, as per

Page 302 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Annexure-26-Certificate Land Border with India along with their Bid/Offer.

In Clause regarding Land Border Sharing mentioned in CRIS EGCC (available on

https://cris.org.in/crisweb/design1/indexorg.jsp?t=6) clause no 34, OM
NoF.18/37/2020-PPD dt 08/02/2021, OM No F.12/1/2021- PPD(Pt) dt 02/03/2021,
OM No. F.7/10/2021-PPD dated 08.06.2021 and F.7/10/2021-PPD dated
23.02.2023) of Ministry of Finance, Government of India is to be read and compiled
along with existing condition.

The Bidder shall abide by the restrictions for the active components & applications
proposed in the project, mentioned under Rule 144 (xi) of the General Financial
Rules (GFRs), 2017 and its following amendments mentioned below: -

i. Order (Public Procurement No. 1) issued vide F.6/18/2019- PPD dated

23.07.2020,
ii. Order (Public Procurement No. 2) issued vide F.6/18/2019-PPD dated
23.07.2020,
iii. Order (Public Procurement No. 3) issued vide F.6/18/2019-PPD dated
24.07.2020, Office Memorandum (OM) No. F.18/37/2020-PPD dated
08.02.2021, OM No. F.12/1/2021-PPD(Pt.) dated 02.03.2021, OM No.
F.7/10/2021-PPD dated 08.06.2021.
iv. Order (Public Procurement No. 4) issued vide F.7/10/2021-PPD dated
23.02.2023) by the Ministry of Finance, Government of India

Page 303 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

17.31. Consignee & Address

Consignee will be the CPE/CTCH.

S. N Consignee Email/Landline No.

1 CPE/CTCH,

CRIS,

Chanakyapuri,

New Delhi -110021.

Table 35: Consignee & Address

17.32. Support from CRIS
CRIS shall assist the Bidder in the following areas during the tenure of the project:

i. Provide detailed information on the integrations required with the Indian

Railways applications.
ii. Provide detailed information on the SOPs/Workflows/Dashboards etc.
iii. To engage with Field SI’s to resolve any coordination issues.
iv. Any other assistance stipulated in the tender/ contract conditions for
successful execution of the project.

Page 304 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18. Annexures

18.1. Annexure-1- Other CRIS Bid Documents

1. Coaches
To enhance security for passengers at Coaches, which is a major means of
transportation, IR intended to install Internet Protocol (IP) based Closed Circuit
Television (CCTV) Surveillance System at Coaches of Indian Railways. A total of
44,038 Coaches are to be fitted with CCTV cameras and CRIS has been entrusted
with the work of providing IP based Surveillance System with Video analytics,
Panic Buttons and Facial recognition system on entry/exit doors at Train Coaches.
Number of Cameras in each Coach is to be installed as per drawing given in
RDSO specification and requirement of IR.

The RDSO applicable Specifications for the Closed-Circuit Television Surveillance

System (CCTVSS) Coaches:

- RDSO/SPN/TC/106/2022 Version 2.1 - IP Based Closed Circuit Television

(CCTV) Surveillance System in Coaches of Indian Railways
- Any Subsequent applicable amendments

Title Tender No.

Supply, Installation & Commissioning of IP-based
Closed Circuit Television Surveillance System
(CCTVSS) in Coaches as per RDSO Specification
01235357
RDSO/SPN/TC/106/2022, Version 2.1 with
amendment no. 1 or latest with 03 years warranty
followed by 05 years CAMC
Table 36: Bid Document for Coaches
The Bidder shall review /understand above mentioned Bid Document along with
Corrigendum documents for further understanding and sizing of the field devices
involved for integration.

2. Locomotives
To enhance safety of train operation, IR intended to install Crew Voice and Video
Recording System (CVVRS) at Locomotives of Indian Railways to be integrated
with Railway Driver Assistance System (RDAS). Cameras will be provided inside
the cab for tamper proof video and voice recording of crew for post event analysis.

Page 305 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

External side/outside cameras will be provided on front and back to capture real
time events for post event analysis by the concerned department of IR.

The RDSO applicable Specification for the Crew Voice & Video Recording System
(CVVRS) for the Locomotives:

- RDSO Specification No. RDSO/2015/EL/SPEC/0118 (Rev.1)-2019 along

with Amendment No.1 issued on 29-03-2022 and Amendment No.2 issued on
20-01-2024 and Amendment No. 3 issued on 15.02.2024 or latest for Crew
Voice & Video Recording System for Electric & Diesel Locomotives.
- Any Subsequent applicable amendments

Title Tender No.

Supply, Installation, Testing & Commissioning of
Crew Voice & Video Recording System
01235356
(CVVRS) integrated with Railway Driver
Assistance System (RDAS) in Locomotives
Table 37: Bid Document for Locomotives
The Bidder shall review /understand above mentioned Bid Document along with
Corrigendum documents for further understanding and sizing of the field devices
involved for integration.

3. EMU/MEMU
To enhance security for passengers in these Coaches, the CCTVSS systems are
planned to be implemented in the EMU/ MEMU passenger Coaches as well as the
Passenger area of the Driving Motor Coach

AND

To enhance safety of train operation CVVRS with/ without RDAS are planned to be
implemented in the Driver Cabin of the EMU/ MEMU Coaches.

Key project highlights are mentioned below/:-

# Category Quantity RDSO Specifications

Part-A (For • CCTVSS - Closed Circuit CCTVSS
passenger area of Television Surveillance RDSO/SPN/TC/106/2022
EMU/ MEMU System Version 2.1 - IP-Based
Coaches) o 8388 EMU/ MEMU Closed-Circuit Television

Page 306 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Category Quantity RDSO Specifications

Coaches along with (CCTV) Surveillance
Video Analytics, Panic System in Coaches of
Button and Facial Indian Railways
Recognition on
entry/exit doors.
2 Part-B (For DMC – Driving Motor Coach, CVVRS with/without
Driving Motor comprise of the Driver cabin & the RDAS
Coaches Passenger area. RDSO Specification No.
including CVVRS • CVVRS - Crew voice & Video RDSO/2015/EL/SPEC/0118
system in driver Recording System (Rev.1)-2019 along with
cab area & o 175 DMC – Driver Amendment No.1 issued on
CCTVSS system Cabin 29-03-2022 and
in the passenger ▪ 50 Driver Cabin Amendment No.2 issued on
area of such with RDAS 20-01-2024 and
Coaches) ▪ 125 Driver Cabin Amendment No. 3 issued
with provisioning on 15.02.2024 or latest or
of RDAS in the latest for Crew Voice &
near future Video Recording System
• CCTVSS - Closed Circuit for Electric & Diesel
Television Surveillance Locomotives
System
o 175 DMC – Passenger CCTVSS
Area along with Video RDSO/SPN/TC/106/2022
Analytics, Panic Button Version 2.1 with
and Facial Recognition amendment No. 1 or latest -
on entry/exit doors. IP-Based Closed-Circuit
Television (CCTV)
Surveillance System in
Coaches of Indian Railways
Table 38: Key project highlights for EMU/MEMU
The details about the project are mentioned in detail in below mentioned bid
document:-

Title Tender No.

“Supply, Installation & Commissioning of IP based 01245066

Page 307 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Title Tender No.

Closed Circuit Television Surveillance
System (CCTVSS) in EMU/MEMU Coaches as per
RDSO Specification RDSO/SPN/TC/106/2022,
Version 2.1 with amendment No.1 or latest with 03
years Warranty followed by 05 years Comprehensive
Annual Maintenance Contract (CAMC)”
AND
Crew voice & Video Recording System (CVVRS)
integrated with/without Railway Driver Assistance
System (RDAS) in Driver Cabs of Driving Motor
Coaches to RDSO
Specification No. RDSO/2015/EL/SPEC/0118 (Rev.1)
issued on 29-03-2022, Amendment No.2 issued on 20
on 15.02.2024 and Amendment No. 3 issued or latest
with 03 years Warranty followed by 05 years
Comprehensive Annual Maintenance Contract
(CAMC)”

Table 39: Bid Document for EMU/MEMU

The Bidder shall review /understand above mentioned Bid Document along with
Corrigendum Documents (if any) for further understanding and sizing of the field
devices involved for integration.

4. Network Connectivity at the edge devices

The Edge devices installed in Coaches, Locomotives, EMUs, and MEMUs are equipped
with two types of Network interfaces namely 5G (with auto-fallback to 4G) SIMs (2 Nos.)
and Wi-Fi. The edge devices are also capable of categorizing the data based on the
configured priorities. The edge devices also have the capability to be configured with
QoS parameters which shall dynamically allocate network bandwidth based on the
category of the data. The Edge devices shall have the capability of pushing the
captured video content and the alerts through the 2 nos. bonded SIMs and also through
the Wi-Fi interface as when the Edge devices connect with a Wi-Fi network. The CVMS
will have the capability of accepting and storing the data received from the Edge
devices both from the 5G (with auto-fallback to 4G) SIMs with auto-fallback to 4G as
well as the Wi-Fi (if available) networks.

Page 308 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.2. Annexure-2-Edge Layer or Field Equipment

Bidders are advised to refer to Section Project Vision & Objective of this bid
document, which elaborates the vision and objectives of the project. Additionally,
Bidders are directed to consult Annexure-1- Other CRIS Bid Documents, specifically
to gain insights into the Edge equipment being procured through the other Bid
Documents. A comprehensive understanding of these sections is essential for Bidders
to align their proposals with the overarching goals of the project and to ensure
compatibility with the Edge equipment procurement strategies outlined in related Bid
Documents.
This annexure provides a detail of the functions expected from the edge equipment.
Bidders are instructed to carefully review this information as the Centralized Video
Management System (CVMS) proposed in response to this Request for Proposal (Bid
Documents) must be meticulously designed to seamlessly interface with and support
the specified functions of the edge equipment. The alignment of the CVMS with the
outlined functions is crucial for the successful integration and optimal performance of
the overall system.
The M-NVR/NVR/VRU shall send alerts of the panic button(s), and video analytics such
as camera tampering, FR, RDAS, etc. on a real-time basis over a 5G (with auto-fallback
to 4G) network. The CVMS shall be able to access the following information/video feeds
from the M-NVR/NVR/VRU from Coaches, Locomotives, EMUs & MEMUs:
1. Continuous live streaming of the Cameras (single view/multi-view – static/guard tour)
2. On-demand live streaming of the Cameras (single view and multi-view – static/guard
tour)
3. On-demand playback of video specific to the defined timestamp for the Cameras
(single view and multi-view – static/guard tour)
4. On-demand playback (from primary/archived storage) of flagged/bookmarked video
(including respective metadata)
5. Health monitoring status as well as alerts (on crossing user-defined thresholds) for
the field devices
6. Facial Recognition based on the cropped images received from field M-
NVR/NVR/VRU
7. Panic Button, RDAS, Camera Tampering alerts on 5G (with auto-fallback to 4G)
network from edged devices to CVMS.
8. Integration mentioned in the Annexure-4-Integration of the Applications of CRIS
of this bid document.

Page 309 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

9. Patch management of edge devices and CVMS solution.

10. Receiving of video/data over true bandwidth bonding/aggregation utilizing the
SIM/eSIM cards from multiple field MSPs
11. Receiving of business-critical data (such as alert/alarm/event information) over any
other non-critical data transmission (such as health alerts). Alarm notifications shall
be routed to one or more respective recipients. Priority levels for alerts shall be
clearly defined in the order of their urgency.
12. CVMS on Cloud must facilitate the required support for appropriate handshaking
between M-NVR/NVR/VRU and Cloud CVMS for queue management in case of
Connectivity loss. CVMS shall be able to resume the recording (video and audio)
based on the availability of network connectivity without any duplication or loss of the
video and metadata.

Indicative architecture is shown in the below figure.

Fig: Illustrative Architecture

The M-NVR/NVR/VRU shall send alerts & recorded videos through 5G (with auto-
fallback to 4G) for providing post event Analysis. The CVMS shall be able to access the
following information/video feeds from the M-NVR/NVR/VRU:
1. On-demand playback of video specific to the defined timeline for the Cameras
(single view and multi-view – static/guard tour)
2. On-demand playback (from primary/archived memory) of flagged/bookmarked video
(including respective metadata)
3. Facial Recognition based on the images received from field M-NVR/NVR/VRU and
run FR on recorded videos of the cameras.
4. Receiving of business-critical data (such as alert/alarm/event information) over any
other non-critical data transmission (such as health alerts). Alarm notifications shall

Page 310 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

be routed to one or more respective recipients. Recipients shall be assigned a

priority level that prioritizes the order of reception of an alarm.
5. CVMS at Cloud must facilitate the required support for appropriate handshaking
between M-NVR/NVR/VRU and Cloud CVMS for queue management in case of
Connectivity loss. CVMS shall be able to resume the recording (video and audio)
based on the availability of network connectivity without any duplication or loss of the
video and metadata.
6. Integration mentioned in the Annexure-4-Integration of the Applications of CRIS
of this bid document.
7. Video Summarization and image enhancement tool at cloud level.
Indicative architecture is shown in the below figure.

Fig: Illustrative Architecture

Page 311 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.3. Annexure-3-Network Layer

Refer to the illustrative connectivity architecture mentioned at (Fig: CVMS System
Architecture Section High-level Architecture). The network connectivity interfaces the
edge equipment to the Public Cloud hosted CVMS. The network layer would be
responsible to provide the feasible methods of connectivity to the edge equipment
namely the CCTVSS solution installed in the Coaches, EMUs and MEMUs and the
CVVRS solution installed in the Locomotives and Driving Motor Cabin of the EMU and
MEMUs. The clauses below provide a brief snapshot of the Network interfaces and the
connectivity types used by the edge devices. The 5G (with auto-fallback to 4G) based
Mobile network connectivity are being planned by the Indian Railways through different
Tenders Annexure-1- Other CRIS .

1. The Network Video Recorders in the Locomotives, Coaches, EMUs, and MEMUs
will be equipped with two M2M SIM/eSIM supporting 5G (with auto-fallback to
4G) SIM/eSIM (From two different Mobile Service Providers) based connectivity
and Wi-Fi as per the stipulated RDSO Specifications and NVR shall have the
provision to enable/disable Wi-Fi connectivity through the CVMS/Central server
on cloud.
2. In the CCTVSS, whenever the Panic button is pressed by a passenger or the
Indian Railway staff, the alert signal along with the recorded video content on a
real-time basis needs to be sent to the Integrated Command and Control Center.
3. Similarly, in the CVMS, alerts triggered by video analytics & RDAS, include the
type of alert and recorded video content need to be sent on a real-time basis to
the Integrated Command and Control Center (ICCC). The CVMS is planned to be
hosted on the Public Cloud.
4. The 5G (with auto-fallback to 4G) interface shall serve as the primary channel for
transmitting alerts and related video content to the CVMS hosted on the Public
Cloud. Each 5G (with auto-fallback to 4G) SIM/eSIM is planned to be configured
with a static private IP address, facilitating NVRs/VRUs/m-NVRs to connect to a
Private Access Point Name (APN) configured by the Mobile Service Provider
(MSP).
5. The connectivity established through the Dual 5G (with auto-fallback to 4G) SIMs
shall be also aggregated, which means the NVRs/VRUs/m-NVRs shall
simultaneously leverage the bandwidth available through both the SIMs to push
the events/alerts and the video contents to the CVMS hosted in the Public Cloud.
6. The private APN is used to provide a secure and isolated communication
channel for the NVRs/VRUs/m-NVRs to the CVMS applications of CRIS hosted

Page 312 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

on the Public Cloud. MPLS backhaul links shall be provided by MSP to route the
traffic from SIMs to Public Cloud, ensuring secure end-to-end connectivity
between NVRs/VRUs/m-NVRs and the Public cloud.
7. While the 5G (with auto-fallback to 4G) SIM/eSIM-based connectivity is used as
the primary connection at Stations / Yards / Car Sheds to connect to the Public
Cloud, the Wi-Fi connectivity whenever available shall be used for pushing the
recorded video content from the NVRs to the CVMS hosted on the Public Cloud.
8. The NVRs/VRUs/M-NVRs installed in Coaches, Locomotives, EMUs, and
MEMUs shall utilize SIM/eSIM connectivity as the primary means to transmit
events and associated video content to the Central Video Management System
(CVMS).

Page 313 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.4. Annexure-4-Integration of the Applications of CRIS

The given below are the list of CRIS applications being part of the tentative integration
with CVMS setup and will be integrated before Phase 1 Go-live. During the requirement
gathering phase, CRIS will share the priority and timeliness of the integration with below
mentioned application, however all the required integration to be completed before
Phase 1 Go-Live of the overall CVMS solution. The below mentioned list is not
exhaustive, further application and database details will be shared during the
requirement gathering and design phase.

S.No Application Reference Application Name

Name
1 CVMS Central Video Management System
2 ICMS Integrated Coaching Management System
3 NTES National Train Enquiry System
4 PRS Passenger Reservation System
5 RSMS RPF Security Management System
6 HHT Hand held Terminal
7 GIS Geographical Information System
8 COA Control Office Application
9 CMS Crew Management System
10 CMM Coaching Maintenance Module
11 SLAM Software for Locomotive Asset Management
12 RailMadad IR Grievance Redressal Portal
13 HRMS Human Resource Management System
14 NATGRID National Intelligence Grid
Table 40: Integration of the Applications of CRIS

Specifications for CVMS Integration with CRIS Backend Systems

General Specifications
i. The Bidder shall provide all relevant integration services and integrate the
service from CRIS applications after finalization with CRIS in the Requirement
Gathering & Design phase.
ii. The CVMS system shall support integrations with the latest technology,
preferably API-based integration (E.g., JSON) with existing CRIS backend
systems

Page 314 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

iii. The assured delivery of alerts and data from CVMS to other CRIS
systems/other systems shall be ensured.
iv. Mobile Applications
a. The integration shall be facilitated with the required Mobile Applications of
CRIS and newly developed as part of CCTV Project scope.
b. All the incoming integration from CVMS to CRIS systems have to integrate
through existing API gateway of CRIS.

Tentative DFDs For integrations

Page 315 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Tentative Integrations and Data Flow

# Scope of integration From To Frequency

System System
1. Coach Integrations including EMUs/MEMUs
a. Data of camera, edge Edge CVMS Fetch mapping on
device mapping on coaches Devices device installation
b. Video, facial images from Edge CVMS On need
coaches to CVMS device
c. Panic button alerts Edge CVMS On panic button press
device event
d. Video related to the panic Edge CVMS On event
button device
e. Live stream data on request Edge CVMS On requirement
device
f. Train profile ICMS CVMS On requirement
g. ETA to plan action required NTES CVMS On requirement
on alert

Page 316 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Scope of integration From To Frequency

System System
h. Passenger details for a train PRS CVMS On requirement
service
i. CRPF Thana, Criminal data RSMS CVMS One time & on update
j. Facial recognition alert CVMS RSMS On event
k. Panic button alert details CVMS HHT On event
l. GPS location for provided CVMS RTIS On Requirement
coordinates
m. Coach maintenance CMM CVMS On event
information for installation
and repair work
n. Public grievance received to CVMS RailMadad On event
be sent to RailMadad for
processing as per already
set workflow
o. The resolution update of RailMadad CVMS On update
public grievances received
from CVMS to be sent back
to CVMS system.
p. Failure of device details CVMS OEM On failure
system
q. Failure resolution details OEM CVMS On resolution
System
2. Loco Integrations
a. Data of camera, edge Edge CVMS Fetch mapping on
device mapping on coaches Devices device installation
b. Alerts of Driver behaviour CVMS SLAM On event
Unauthorised access,
Unusual crowd
c. Live stream request CVMS Edge On requirement
devices on
a Loco
d. Live stream data Edge CVMS On requirement
devices
e. Train profile COA CVMS On requirement
f. ETA to plan action required NTES CVMS On requirement
on alert
g. Assigned Crew details for CMS CVMS On every crew
Locos assignment
h. Video stream for a filed FIR CVMS RSMS On requirement

Page 317 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Scope of integration From To Frequency

System System
i. GPS location for provided CVMS RTIS On Requirement
coordinates
j. Loco maintenance SLAM CVMS On event
information for installation
and repair work
k. Failure of device details CVMS OEM On failure
system
l. Failure resolution details OEM CVMS On resolution
System
Table 41: Tentative Integrations and Data Flow
Sample Use cases for Locomotives.

A. Online event alerts at Locomotive and transferring message

RDAS Camera shall generate Audio/ video alerts to loco pilots based on exceptional
event detected during the journey and video footage of the camera around the incident
duration beginning from 0.5 minute prior to 0.5 minute after the incident along with
message shall be sent to central CVMS through NVR device for post analysis.
Following are the exceptional events not limiting to be defined for generating alerts and
video clips:

1. Railway Driver Assistance System (RDAS) – Enhancement in Safety:

RDSO vide letter No. EL/0.1.3/Driver dated 10.11.23 has issued revised
specifications incorporating RDAS for enhancement of Train safety.
Alertness of the Loco Pilots is one of the important considerations for safe
running of trains. Drowsiness/ lack of alertness threatens the rail safety and may
cause severe loss of Railway property as well as human lives.
To monitor the loco pilots for improving his alertness, RDAS will be able to
detect the drowsiness/lack of alertness nature of the loco pilot and alert him
immediately. RDAS will capture images as a video stream through a camera,
detect the face and localizes the eyes and other face parameters. All the face
parameters & responses of loco pilot are then analysed for detection of
drowsiness/lack of alertness. Based on the result, the loco pilot will be alerted
through an alarm system.

Page 318 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Use cases of RDAS are as follows:

i. Eye Drowsiness detection
ii. Yawning detection
iii. Distracted detection
iv. Phone call detection
v. Smoking detection
vi. No driver detection
vii. Headphone detection
viii. Camera covered.
ix. Any other loss of concentration symptoms
User: Loco Pilot

B. Post facto analysis of video at CVMS

1. Railway Driver Assistance System (RDAS) – Enhancement in Safety:

Video footage of the RDAS received at Central server shall identify the train based
on the NVR id and its mapping with the Loco number and transmit the alert to the
concerned users as per workflow defined during design phase of the
implementation.

User: Chief Loco Inspector of Loco Pilot, Divisional Loco Controller

2. Reduction in Accidents and Signal Passing At Danger (SPAD) Cases:

Post event analysis of action taken by the crew on the following parameters will
facilitate in reduction of Signal Passing At Danger (SPAD) cases:
• Calling out signal aspect
• Hand gesture
• Engineman-ship & Driving skills
• Emergency brake Value (RS value) operation by ALP during SPAD etc.
Sometimes SPAD took place on account of Loco pilot engaged in packing of his
belongings while approaching train at destination. Unusual Event recorded by
Front/Rear View ( One on top of each cab) Cameras:

Page 319 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

There are around 11000 cases of Man Run Over and 21000 of Cattle run over
during 2023-24 (till 11-12-2023)
Provision of front /Rear camera will assist in post event analysis of following
unusual events:
• Trespassing:
• Miscreant activities on track / LC gates
• Operation of points (track diversion points)
• Obstruction on track
• Signal aspect depending on visibility
User: Divisional Loco Controller

3. Unusual Event recorded by Roof Cameras:

There are 596 cases of OHE failures during 2023-24 which caused failure of
locomotive in block section on account of Panto-OHE entanglement and severe
disruption of traffic. Provision of Roof camera will assist in post event analysis of
following unusual events:
• Panto entanglement
• Foreign objects like cloth, tree branch, kite thread etc. on OHE.
• Panto defect
• OHE defect
• Panto flashing & Panto – OHE interaction
User: Divisional Loco Controller

4. Unusual Event recorded by Side walls cameras (Two on each side

wall):
It will lead to post event analysis of for following unusual events:
• Miscreant activities
• Stone pelting
• Disturbance to coaches / wagon
User: Divisional Loco Controller
5. Reduction in Accidents and Signal Passing At Danger (SPAD) Cases:
Post event analysis of action taken by the crew on the following parameters will
facilitate in reduction of Signal Passing At Danger (SPAD) cases:

Page 320 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

• Calling out signal aspect

• Hand gesture
• Engineman-ship & Driving skills
• Emergency brake Value (RS value) operation by ALP during SPAD etc.
Sometimes SPAD took place on account of Loco pilot engaged in packing of his
belongings while approaching train at destination. Unusual Event recorded by
Front/Rear View ( One on top of each cab) Cameras:
There are around 11000 cases of Man Run Over and 21000 of Cattle run over
during 2023-24 (till 11-12-2023).
Provision of front /Rear camera will assist in post event analysis of following
unusual events:
• Trespassing:
• Miscreant activities on track / LC gates
• Operation of points (track diversion points)
• Obstruction on track
• Signal aspect depending on visibility
User: Chief Loco Inspector of Loco Pilot, Divisional Loco Controller

6. Unusual Event recorded by Roof Cameras:

There are 596 cases of OHE failures during 2023-24 (till 11-12-2023, which
caused failure of locomotive in block section on account of Panto-OHE
entanglement and severe disruption of traffic. Provision of Roof camera will
assist in post event analysis of following unusual events:
• Panto entanglement
• Foreign objects like cloth, tree branch, kite thread etc on OHE.
• Panto defect
• OHE defect
• Panto flashing & Panto – OHE interaction
User: Divisional Loco Controller

7. Unusual Event recorded by Side walls cameras (Two on each side

wall):
It will lead to post event analysis of for following unusual events:

Page 321 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

• Miscreant activities
• Stone pelting
• Disturbance to coaches / wagon
User: Divisional Loco Controller

Sample Use cases for CCTV Camera in Coaches

1. Use Case 1: Incident alert
• User: Travelers on train
• Flow: Panic button shall be pressed to initiate the use case. Once a panic button
is pressed the attached VRU/M-NVR shall send the alert to the central server
and also upload the video footage of the camera around the panic button (in my
view all camera footage shall be uploaded) for the duration beginning from 1
minute prior to 1 minute after the press of panic button.
• Central server shall identify the train based on the VRU/M-NVR id and its
mapping with the physical coach and transmit the alert to the concerned party (in
my view current RailMadad flow shall be followed for transmission of alerts to the
concerned).
• Alternate Flow: If network connection is not available at the time VRU/M-NVR
shall wait for the network connection and resume the process as soon as the
network becomes available.
• Pre-Condition: VRU/M-NVR shall be mapped to the coach, panic button shall be
in working condition
• Post condition: Further use case of live video streaming may be initiated on the
request of concerned authority. Alerts generated shall be available for analysis
and further necessary action.

2. Use Case 2: On-demand live streaming

• User: Authorized person to view the live streaming e.g. RPF personnel etc.
• Flow: Footage for a particular coach of a train shall be requested by the user
through the central command center. System shall connect with the identified
VRU/M-NVR and list out the cameras available in the coach. User shall select
the camera for footage live-streaming. System shall connect with the desired
camera through VRU/M-NVR and present the live streaming.

Page 322 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

• Alternate Flow: User may request for past footage streams (usually delayed due
to network outage or delay in attending the incident), in this case VRU/M-NVR
shall stream the stored video.
• Pre Condition: VRU/M-NVR is available over the internet. User has the proper
authentication and authorization for viewing.
• Post condition: Further use cases of video download and archival may be
initiated on the request of concerned authority. Proper logging of such access is
stored in the database for audit requirements.

3. Use Case 3: On-demand video download and archival

• User: Authorized RPF personnel or authorized person by RB.
• Flow: Footage for a particular coach of a train can be requested by the user
through the central command center within 30 days of the recording. System
shall connect with the identified VRU/M-NVR and list out the cameras available in
the coach. User shall select the camera/cameras for footage, and provide the
time duration for footage including the retention period for the footage. System
shall connect with the desired cameras through VRU/M-NVR and download the
video on the central server. User may update the retention period for the footage
in the future. Downloaded footage shall be stored in encrypted format so that
only authorized user can view the footage and footage id is generated. User shall
tag the video for future retrieval.
• Alternate Flow: None.
• Pre-Condition: VRU/M-NVR is available over the internet. User has the proper
authentication and authorization for viewing.
• Post condition: Footage shall be available for viewing or downloading by the
authorized person. All requests are properly logged in the database for audit.

4. Use Case 4: On-demand video access and download

• User: Authorized RPF personnel or authorized person by RB.
• Flow: User search/request for footage with footage id/tag within the retention
period. System shall provide the videos associated with the search. User may
choose to view or download the video file.
• Alternate Flow: None.
• Pre-Condition: Video is available on the central server and the user has the
proper authorization.

Page 323 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

• Post condition: All requests are properly logged in the database for audit.

5. Use Case 5: CCTV camera status monitoring.

• User: Depot user and user of command center.
• Flow: System shall present the current status of all the installed cameras,
VRUs/M-NVRs, working condition of cameras and VRUs/M-NVRs. Users shall
have the option to view the status of cameras by coach/train search..
• Alternate Flow: Tampering alerts shall be generated by the VRUs/M-NVRs and
the same shall be communicated in form of SMSs, emails and system alerts to
the concerned defined users.
• Pre Condition: Cameras and VRUs/M-NVRs are mapped with the coach.
• Post condition: None.

6. Use Case 6: Facial Recognition Solution

• User: Concerned RPF thana.
• Flow: Cameras installed on doorways shall be able to identify the faces in video
frames and send it to the central server in required format for facial recognition
and matching within the specified facial database. If any positive match is found
then alerts shall be generated and sent to the concerned RPF thana for
necessary action.
• Alternate Flow: System may also be configured to transmit the footage from the
camera to the central server.
• Pre Condition: Target facial recognition database is available with proper
tagging for identification and alert generation.
• Post condition: Alert sent to the concerned and footage for specified duration is
available on the central server.

Sample Use cases for RPF

1. Use case 1: Passenger Luggage Thefts, Robbery, Snatching
• User: Concerned RPF thana.
• Flow: Cameras installed inside coaches shall detect faces and the cropped faces
shall be sent to the central server in required format for facial recognition and
matching within the specified facial database. If any positive match is found then

Page 324 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

alerts shall be generated and sent to the concerned RPF thana for necessary
action.
• Alternate Flow: System may also be configured to transmit the footage from the
camera to the central server.
• Pre Condition: Cameras and VRUs/M-NVRs are mapped with the coach.
• Post condition: Alert sent to the concerned and footage for specified duration is
available on the central server.
2. Use case 1: Post-incident investigations by different security agencies
• User: Concerned RPF thana.
• Flow: Cameras installed inside coaches shall record and store the footage in
M-NVR / NVR / VRU to be uploaded to the cloud. Video summarization
application in CVMS shall be used to summarize the lengthy video to provide
a shorter/concise video (2 hours to 2 minute) for faster investigation.
• Alternate Flow: System may also be configured to transmit the footage from the
camera to the central server.
• Pre Condition: Cameras and VRUs/M-NVRs are mapped with the coach.
• Post condition: None

Page 325 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.5. Annexure-5-Format for Compliance of Functional Requirements

# Section # Description of the Parameter Compliance Details of any
(Yes/No) Artifact
Provided in
Support of
Compliance
1
2
3
Table 42: Format for Compliance of Functional Requirements

Page 326 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.6. Annexure-6- Integration of the Edge Devices Parameters

Undertaking from Bidder for Integration of the Edge Devices Parameters
To,
The Managing Director

CRIS, Chanakyapuri,
New Delhi – 110021.

Ref: Tender No....................................................................

We, <<name of the Bidder>>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the Public
Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We, _____________________who are established and reputable manufacturers of the

proposed Software applications <Name of Applications> and <Software Version>.

Note: In case of multiple models, insert device details and compliance for each model as
per the proposed solution.

We hereby confirm that we comply to the below mentioned use cases and will integrate
proposed system to be established in Coach/Loco/EMU’s/MEMU’s with CVMS.

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
1. Video Continuous live Yes Yes Yes
Streaming streaming of the
(Live) on H.265 Edge Cameras
(single view/multi-
view – static/guard
tour) with the CVMS
and ICCC
application on the
public cloud as per

Page 327 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
the requested
parameters of the
feed (such as –
specific video
resolution, frame
rate, etc.) as per
available network
bandwidth
supporting variable
resolution/bit rate,
appropriate data
packet
segmentation or
any other alternate
mechanism.
On-demand live Yes Yes Yes
streaming of the
Edge Cameras
(single view and
multi-view –
static/guard tour)
with the CVMS and
ICCC application on
the public cloud as
per the requested
parameters of the
feed (such as –
specific video
resolution, frame
rate, etc.) as per
available network
bandwidth
supporting variable

Page 328 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
resolution/bit rate,
appropriate data
packet
segmentation or
any other alternate
mechanism.
2. Video On-demand Yes Yes Yes
Streaming playback of video
(Playback and specific to the
Archival) on defined timeline for
H.265 the Cameras (single
view and multi-view)
of edge devices
with the CVMS and
ICCC application on
the public cloud as
per the requested
parameters of the
feed (such as –
timeline, video
resolution, frame
rate, etc.) and
available network
bandwidth
On-demand Yes Yes Yes
playback (from
primary/archived
memory) of
flagged/bookmarke
d video (including
respective
metadata) for the
Cameras (single

Page 329 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
view and multi-view)
with the CVMS and
ICCC application on
the public cloud as
per the requested
parameters of the
feed (such as –
bookmark ID,
event/alarm type,
timeline, video
resolution, frame
rate, etc.) and
available network
bandwidth
3. Video Interoperability for Yes Yes Yes
Compression Compressing and
De-Compressing
the videos in an
interoperable and
open standards
compliant
compression format
(H.265) for
transmission from
and/or stored in the
M-NVR/NVR/VRU
with the
CVMS/ICCC at
Cloud for reducing
the upload
bandwidth.
4. Alerts and Receive and Push Yes Yes Yes
Alarms / alarms/events along

Page 330 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
Events with automated on-
demand live video
streams with pre-
and post-recording
(as defined and
configured by the
end-user) along
with date, time, and
geo-location details
with the CVMS on
Public Cloud as per
the defined SOPs
Alert Types: Refer Yes Yes Yes
to Point 5 for
details.
Alarm/Event Types: Yes Yes Yes
Press of a panic
button, video
analytics triggers
(such as camera
tampering, offline,
RDAS defined
analytics, etc.) at
the camera as well
as M-
NVR/NVR/VRU
level
5. Health Receive, configure, Yes Yes Yes
Monitoring (To and display the
be integrated health monitoring
with edge status as well as
devices and alerts (on crossing
central EMS user-defined

Page 331 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
hosted on thresholds) for the
public cloud) field devices but not
limited to the
following:
xi. Device status Yes Yes Yes
(online/offline/fa
ult), Uptime and
Downtime
(device as well
as network),
Port status,
temperature
status
xii. System Yes Yes Yes
information –
make, model,
version, serial
no., and MAC
ID
xiii. Network Yes Yes Yes
Health – IP
address,
latency,
bandwidth
utilization
(aggregation as
well as
individual links),
SIM/eSIM
(both) network
strength,
availability of
data network

Page 332 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
and mode

xiv. Resource Yes Yes Yes

Utilization –
CPU and GPU,
RAM/memory,
SSD/Storage,
Recording,
disk/module
removal
xv. Audit Logs – Yes Yes Yes
access to audit
logs, alarms,
and SNMP
traps
xvi. Device Yes Yes Yes
configuration,
firmware/patch
update (camera
and M-
NVR/NVR/VRU
)
xvii. Video quality Yes Yes Yes
and jitters
monitoring (as
feasible)
xviii. GPS/NTP for Yes Yes Yes
time
synchronization
xix. User Yes Yes Yes
authentication
and access
logs

Page 333 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
xx. SLA Yes Yes Yes
monitoring (as
per terms of the
bid document)
6. Remote v. Support for M- Yes Yes Yes
Configuration NVR/NVR/VRU
and Camera
level
configuration
but not limited
to as follows:
vi. Camera Image, Yes Yes Yes
resolution,
frames,
compression,
BLC, WDR,
NTP, Audio, IR,
streams, and
other general
and network
settings.
vii. NVR general Yes Yes Yes
configuration
such as NTP,
reboot,
streams, zoom,
network, and
other general
settings.
viii. Wi-Fi Access Yes Yes Yes
general
configuration
such as band

Page 334 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
change, SSID
etc.
7. Interoperability Receiving of Yes Yes Yes
with MSP video/data over true
bandwidth
bonding/aggregatio
n utilizing the
SIM/eSIM cards
from multiple MSPs
Receiving of Yes Yes Yes
video/data over
fallback utilizing the
SIM/eSIM cards
from multiple MSPs
Automated video Yes Yes Yes
management for
transmission &
receiving as per the
available network
bandwidth in
aggregation as well
as fallback mode
Quality of Service Yes Yes Yes
(QoS): CVMS must
facilitate & receive
the prioritization of
high priority data
(such as
alarm/event
information, health
alerts) over any
other normal priority
data transmission

Page 335 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
(such as transfer of
all recorded video
feeds on NVR to the
CVMS)
CVMS at Cloud Yes Yes Yes
must support for
appropriate
handshaking
between M-
NVR/NVR/VRU and
Cloud CVMS for
queue management
in case of
connectivity loss.
CVMS shall be able
to resume and start
receiving the
recording (video
and audio) based
on the availability of
network connectivity
without any
duplication or loss
of the video and
metadata.
8. Face Detection Support to receive Yes No Yes
new faces (with
minimum 70x70
pixels) in CVMS on
Public Cloud
without
compromising the
quality of data as

Page 336 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
captured at the
source i.e., Camera.

9. Scalability and CVMS shall support Yes Yes Yes

Upgrades Horizontal
scalability of edge
devices (such as
the addition of
cameras or other
devices at unutilized
channels or
Input/Output ports,
feasible module
upgrades) as well
as Vertical
scalability of edge
devices (such as
work in coordination
with another M-
NVR/NVR/VRU) for
any expansion or
upgrades in future,
if required.
10. Device Automated Yes Yes Yes
Discovery discovery of device
(camera as well as
M-NVR/NVR/VRU)
at CVMS
11. Authentication Role-based user Yes Yes Yes
and Encryption authentication to
protect privacy and
data integrity

Page 337 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
Encryption (AES Yes Yes Yes
128/256),
transmission &
receiving of
Secured video and
data as per the
defined
specifications and in
compliance with M-
NVR/NVR/VRU
requirements such
as transmission on
HTTPS, TLS 1.2 or
above, etc.
12. Firmware Facilitate firmware Yes Yes Yes
Update and patch upgrades Yes Yes Yes
(on demand or
scheduled)
13. Backup and Back-up of device Yes Yes Yes
restore configurations and
data on demand
(manual) as well as
scheduled
(automated) as
configured by the
end user
Restore device Yes Yes Yes
configurations and
data on demand
(manual) by the
end-user
14. Open Compliance with Yes Yes Yes
Standards ONVIF standard for Yes Yes Yes

Page 338 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Integration Details of the Coaches Loc EMUs, Complian

No Parameter Parameter os MEMU ce (Y/N)
s
interoperability
between M-
NVR/NVR/VRU (for
outward Video/data
transmission) and
CVMS application
on profiles as
required as part of
the defined
functional and
integration
requirements.
15. Audio Continuous and on- No Yes Yes
Streaming demand audio
streaming of the
Cameras with the
CVMS and ICCC
application on the
public cloud as per
the requested
parameters (such
as – specific audio
parameters etc.) as
per available
network bandwidth
supporting variable
resolution/bit rate,
appropriate data
packet
segmentation or
any other alternate
mechanism.
Table 43: Integration of the Edge Devices

Page 339 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Your faithfully,

Note:

a. This letter of authority shall be on the Letter-Head of the manufacturing concern

and shall be signed by a person competent and having the power of attorney to
bind the manufacturer.

b. This letter of undertaking shall be counter sign by the authorized signatory of the
Bidder.

Page 340 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.7. Annexure-7-Bidder’s Checklist

# Section Details Applicable to Complied Docum
Heading (Yes/ No) ent
page
Refere
nce no.
1. Company Certificate of Sole/Lead Bidder &
Existence Incorporation / All Members of JV/
Copy of Article Consortium
of Association to
be submitted by
providing the
details in
Annexure-11-
Format for
Providing
Eligibility
Compliance
2. Joint Venture Joint Venture or
or Consortium Consortium
Agreement (If Agreement (If
applicable) applicable) to be
submitted as per
Annexure-31(A)
- Joint Venture
Agreement Or
as per
Annexure-
31(B)-
Consortium
Agreement
3. Company GST Certificate, Sole/Lead Bidder &
Supporting PAN Card to be All Members of JV/
Document submitted by Consortium
providing the
details in
Annexure-11-
Format for

Page 341 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
Providing
Eligibility
Compliance
4. Financial CA Certificate/ Sole/Lead Bidder &
Turnover Certified audited All Members of JV/
copies of Consortium
Balance
Sheets/Profit &
Loss Accounts/
Annual Reports
of last three
financial years
to be submitted
by providing the
details in
Annexure-11-
Format for
Providing
Eligibility
Compliance
5. Project/ Work Copy of PO and Sole/Lead Bidder &
Experience of Project All Members of JV/
the bidder and Certificates as Consortium
the OEM. per Annexure-
12-Project
Experience of
the Bidder and
Annexure-13-
Project
Experience of
the OEM

Page 342 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
6. STQC Proof of Sole/Lead Bidder
Certifications applying to
STQC / Security
verification
certificate from
STQC as per
Pre-qualification
to be submitted
by providing the
details in
Annexure-11-
Format for
Providing
Eligibility
Compliance &
Security
Verification
Certification
7. Self- Self-Declaration Sole/Lead Bidder &
Information to as per Table 44: OEM’s
be submitted Bidder's
by Bidder & Checklist
Key OEM
Annexure-8-
Bidder’s & Key
OEM’s Self
Information
8. Make in India Declaration/Certi Sole/Lead Bidder
ficate as per
Annexure-36-
Local Content
as per Make in

Page 343 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
India Policy as
applicable
9. Land Border Self-Declaration Sole/Lead Bidder
Sharing as per
Annexure-26-
Certificate
Land Border
with India
10. Project Office Proof/willingness Sole/Lead Bidder
in Delhi / of Project
NATIONAL Office at New
CAPITAL Delhi /
REGION NATIONAL
CAPITAL
REGION as per
Annexure-28-
Declaration for
Project Office
11. Quality Self-attested Sole/Lead Bidder/
Certifications with Company Members of JV/
Seal on the Consortium
Copy of Valid
ISO 9001:2015,
ISO 27001, ISO
20000 and
CMMI-Level 3
12. Long Term Declaration from From each OEM
Maintenance respective whose solution is
from OEM and OEMs whose being proposed for
backend solution is being the CVMS solution
Support from proposed by the stack.
OEM bidder as per Applicable for
Annexure-19- Sole/Lead Bidder

Page 344 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
Long Term
Maintenance
Support
and Annexure-
20-Undertaking
from OEM For
Backend
Support
13. Valid License Self - Sole/Lead Bidder
Undertaking Declaration by for all the OEM’s
the Bidder’s being proposed
Annexure-29-
Undertaking for
Valid License
for Software
14. BOM/BOQ Authorization Sole/Lead Bidder
authorization letter from for all the OEM’s
respective being proposed
OEMs, as per
Annexure-15-
Undertaking for
Unpriced Bill of
Quantity
15. Support Customer Sole/Lead Bidder
offices in India support offices for all the OEM’s
covering the being proposed
entire country,
as per
Annexure-37-
OEMs
Technical
Support in India

Page 345 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
16. Declaration for Declaration for Sole/Lead Bidder
Proof of Proof of
Concept Concept to be
submitted as per
Annexure-27-
Declaration for
Proof of
Concept
17. Technical Details of Sole/Lead Bidder
manpower Manpower and
Compliance as
per Annexure-
23-Deployment
of Manpower
and CVs of the
deployed
manpower as
per Annexure-
14-CV of Key
Personnel
Proposed
18. Undertaking Undertaking From each OEM
from OEM for from OEM for whose solution is
backend backend support being proposed for
support as per the CVMS solution
Annexure-20- stack.
Undertaking
from OEM For
Backend
Support
19. Undertaking Undertaking to From each OEM
from the be provided by whose solution is
OEMs for the OEM of the being proposed for

Page 346 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
compatibility Software the CVMS solution
of their applications stack.
solution to which are being
function in proposed for the
MeitY CVMS solution
empanelled Stack hosted on
Cloud the cloud
Annexure-38-
MeitY
empanelled
Cloud
20. Undertaking Undertaking to From the OEM
by OEM for be provided as providing the Video
VMS software per the Management
to meet Annexure-39- System Solution
scalable Undertaking for
architecture VMS scalable
architecture.
21. Undertaking Undertaking to From the OEM
by OEM for be provided as providing the Video
Integration of per the Management
the VMS with Annexure-40- System Solution
more than Integration of
One NVR the VMS with
more than One
NVR
22. Undertaking Undertaking to From the OEM
from OEM for be provided as providing the ICCC
the integration per the Solution Provider
of ICCC with Annexure-41-
other Integration of
applications ICCC with
other
applications.
23. CSP’s Submission of To be provided by
Authorization the CAF as per the CSP.

Page 347 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
Form (CAF) Annexure-30-
CSP’s
Authorization
Form (CAF)
24. Non- Declaration of Sole/Lead Bidder
Blacklisting Non-Blacklisting & for all the OEM’s
Declaration as per being proposed
Annexure-10-
Declaration of
Non-
Blacklisting
25. Total Total Sole/Lead Bidder
Responsibility Responsibility
Certificate as
per Annexure-
25-Total
Responsibility
Certificate
26. Anti-Collusion Anti-Collusion Sole/Lead Bidder
Undertaking Certificate as
per Annexure-
22-Anti-
Collusion
Certificate
27. Past Project Details Sole/Lead Bidder
Experience as per
Annexure-8-
Bidder’s & Key
OEM’s Self
Information
28. Performance PBG as per Sole/Lead Bidder
Bank Annexure-17-

Page 348 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
Guarantee Performance
Bank
Guarantee
29. Non- NDA signed by Sole/Lead Bidder
Disclosure- bidder as per
Agreement Annexure-21-
Non-Disclosure
Agreement
30. IPR Undertaking By Respective
Undertaking from OEM as OEM’s
per Annexure-
24-Undertaking
from OEM for
IPR
31. Compliance to Respective Respective OEMs
RDSO OEM to share & Sole/Lead Bidder
Technical & compliance of
Functional technical &
Specifications functional
for ICCC & FR specifications
Solution specified by
RDSO for this
tender
document as per
Annexure-5-
Format for
Compliance of
Functional
Requirements
32. Compliance to Respective Respective OEM
integration use OEM and Bidder and Bidder

Page 349 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
case to share the
requirement compliance to
integration use
case
requirements as
per Annexure-
4-Integration of
the
Applications of
CRIS
33. Certificate to Certificate as For Annexure-9-
be per Annexure- Format for Power
submitted/uplo 9-Format for of Attorney for
aded by Power of Lead Member
Tenderer Attorney for Sole/Lead Bidder &
along with the Lead Member For All Members of
Tender And Annexure- JV/
Documents 47- PoA for Consortium/Partne
signing of rship/Society, etc.
proposal
And for Annexure-
47- PoA for
signing of
proposal for
Sole/Lead Member
34. Compliance to Self-Declaration Sole/Lead Bidder
Design from the OEM
Consideration on their
s to be company letter
provided by head elaborating
the Bidder as the design

Page 350 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Section Details Applicable to Complied Docum

Heading (Yes/ No) ent
page
Refere
nce no.
well as the considerations
respective while proposing
OEMs for the solution for
specifications the CVMS
and functional Solution Stack
requirements. as per
Annexure-5-
Format for
Compliance of
Functional
Requirements
35. Format for the Certificate to be Sole/Lead Bidder
Certificate to submitted by the
be submitted/ bidder as per
uploaded by Annexure-42-
Bidder Certificate to
be submitted
by Tenderer
36. Undertaking Undertaking to Sole/Lead Bidder
for seeking be provided as and the CSP.
written per the
permission Annexure-45-
from CRIS for Undertaking to
making any be provided by
changes to the the Bidder &
CVMS CSP
Solution
Table 44: Bidder's Checklist

Page 351 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.8. Annexure-8- Bidder’s & Key OEM’s Self Information

I. Bidders Proposal number and date:

II. Name and address of the Bidder:

III. Turnover of last 3 financial years:

IV. Collaboration, if any:

V. Name and address of the officer to whom all references shall be made regarding
this tender enquiry. His/her telephone, mobile, fax and email.

VI. Any other point tenderer may like to specify.

Name/designation:

Company name/address:

Seal:

Signature:

Date:

Page 352 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.9. Annexure-9-Format for Power of Attorney for Lead Member

(On Non–judicial stamp paper of requisite value)
(To be executed by all the Members of the Joint Venture/ Consortium)
Power of Attorney

Whereas the Centre or Railway Information Systems, New Delhi (CRIS); an

Organization under the Ministry of Railways, Government of India (“the Authority”) has
invited Bids from interested parties for the Tender No……………….……. for “Name of
the Work: ………………………………………………” (the “Project”).

Whereas (1) M/s…………….………………., (2) M/s…………………….…………… and

(3)
……………….………………………. (Collectively the "Consortium") being Members of
the Consortium are interested in bidding for the Project in accordance with the terms
and conditions of the Bidding Documents and other connected documents in respect of
the Project, and

Whereas, it is necessary for the Members of the Consortium to designate one of them
as the LEAD MEMBER with all necessary power and authority to do for and on behalf of
the Consortium, all acts, deeds and things as may be necessary in connection with the
Consortium's bid for the Project and its execution.

NOW, THEREFORE, KNOW ALL MEN BY THESE PRESENTS

We, (1) M/s ………………………….…….………………. having our Registered Office at

……….………………., (2) M/s.………………….………. having our Registered Office at
…………………….………... and (3) M/s.…………. ….……………. having our Registered
Office at ……………….……….….………………. (hereinafter collectively referred to as
the “Principals”) do hereby irrevocably designate, nominate, constitute, appoint and
authorize M/s………………….…………. having its Registered Office
at……………………..., being one of the Members of the Consortium, as the LEAD
MEMBER and true and lawful Attorney of the Consortium (hereinafter referred to as the
“Attorney”). We hereby irrevocably authorize the Attorney (with power to sub-delegate)
to conduct all business for and on behalf of the Consortium and any one of us during
the bidding process and, in the event the Consortium is awarded the Contract, during
the execution of the Project and in this regard, to do on our behalf and on behalf of the
Consortium, all or any of such acts, deeds or things as are necessary or required or
incidental to the pre-qualification of the Consortium and submission of its bid for the
Project, including but not limited to signing and submission of all applications, bids and
other documents and writings, participate in bidders and other conferences, respond to

Page 353 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

queries, submit information/documents, sign and execute contracts and undertakings

consequent to acceptance of bid of the Consortium and generally to represent the
Consortium in all its dealings with the Authority, and/or any other Government Agency
or any person, in all matters in connection with or relating to or arising out of the
Consortium's bid for the Project and/or upon award thereof till the Agreement is entered
into with the Authority.

AND hereby agree to ratify and confirm and do hereby ratify and confirm all acts, deeds
and things done or caused to be done by our said Attorney pursuant to and in exercise
of the powers conferred by this Power of Attorney and that all acts, deeds, and things
done by our said Attorney in exercise of the powers hereby conferred shall and shall
always be deemed to have been done by us /Consortium.
IN WITNESS WHEREOF WE THE PRINCIPALS ABOVE NAMED HAVE EXECUTED

THIS POWER OF ATTORNEY ON THIS ……………DAY OF …………. 2024.

For & on behalf of For & on behalf of For & on behalf of

Name of Company: Name of Company: Name of Company:

Signature: Signature: Signature:

Name of Signatory: Name of Signatory: Name of Signatory:

Designation: Designation: Designation:

Address: Address: Address:

Page 354 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

WITNESSES:

1. …………………………………………….

2. ………………………………………………

Enclosures:

Resolution/Power of Attorney of each of the Consortium Members:

i. Authorizing Execution of the Consortium Agreement, and

ii. Appointing the authorized signatory for such purpose.

Page 355 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.10. Annexure-10-Declaration of Non-Blacklisting

To be submitted by Sole/Lead/JV/ Consortium members, OEMs and CSPs.

<<To be submitted on INR. 100 stamp paper and duly notarized, to be submitted by
Sole/Lead/JV/ Consortium members, OEMs and CSPs >>

Date: ___________

To,
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Dear Sir,

We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”.

In response to the Tender Ref. No. ___________________________________ dated

_______________ for “Selection of Master System Integrator for the Central Video
Management System (CVMS) on the Public Cloud for the IP-based CCTV Surveillance
System for the Indian Railways”, as an owner/ partner/ Director of
_________________________, I/ We hereby declare that presently our Company/ firm
___________________is having unblemished record and is not declared ineligible for
corrupt and fraudulent practices either indefinitely or for a particular period by any
Central or State or Local Government, Autonomous or Statutory or Constitutional
Bodies, Central or State Public Sector Enterprises.

We further declare that presently our Company/ firm ___________________is not

blacklisted or debarred and not declared ineligible for bankruptcy or reasons other than
corrupt and fraudulent practices by any Central or State or Local Government,
Autonomous or Statutory or Constitutional Bodies, Central or State Public Sector
Enterprises on the date of Bid Submission.

Page 356 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

If this declaration is found to be incorrect then without prejudice to any other action that
may be taken, my/ our security may be forfeited in full and the tender if any to the extent
accepted may be cancelled.

(Signature of the Authorized representative of Sole/Lead/JV/ Consortium members,

OEMs and CSPs.)

Printed Name
Designation
Seal Date:
Place: Business Address:

Page 357 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.11. Annexure-11-Format for Providing Eligibility Compliance

<eligibility criteria to be pasted here><finalized QC will be added>

Supporting
Sl Reference /
Criteria Documents to be Provided
No Page #
Submitted
1.
2.
3.
4.
5.
Table 45: Format for Eligibility Compliance

Page 358 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.12. Annexure-12-Project Experience of the Bidder

Statement of Project Experience during Last Five Years and Outstanding Current
Orders

(To be submitted Chartered Accountant of the bidder)

To,
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Tender Document No. ; Tender Title: __________________

This is to certify that [Bidder's Legal Name], having its registered office at [Bidder's
Address], is a certified and registered entity with this Certification Authority.

This is to further certify that [Bidder's Legal Name] has successfully completed the
following projects, demonstrating competence and expertise in the specified domains:

The Certification Authority has conducted a thorough examination of the bidder's project
experience and is satisfied with the information provided.

Note to Bidder: Bidder must fill in this form to prove conformance to Experience and
Past Performance in Section Qualifications Criteria. Mention contracts in which Bidder
is or has been a party, whether as a Prime Bidder or JV/Consortium bidder, affiliate,
associate, subsidiary, Subcontractor, or any other role. The list below is indicative only.
Scanned Attested copies of completion/performance certificates from the Officer-in-
Charge for each work should be annexed in the support of information furnished. You
may attach more documents as required to showcase your past performance. Additional
details not covered elsewhere in your bid in this regard.

Contracting Contract Type of Scope of The total Status as

Entity – Name Title, Client Work in value of the on date ----
and Address Number and Contract order
Date

Page 359 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Table 46: Project Experience of the Bidder

……………………..
(Signature with date)
………………………..
(Name and designation)
Duly authorized to sign bid for and on behalf of
……………………………………….
[name & address of Chartered Accountant and seal of company]

Page 360 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance for the Indian Railways

18.13. Annexure-13-Project Experience of the OEM

Statement of Project Experience during Last Five Years and Outstanding
Current Orders

(To be submitted Chartered Accountant of the bidder)

To,
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Tender Document No. ...….; Tender Title:

This is to certify that [OEM’s Legal Name], having its registered office at [OEM’s
Address], is a certified and registered entity with this Certification Authority.

This is to further certify that [OEM’s Legal Name] has successfully completed the
following projects, demonstrating competence and expertise in the specified domains:

The Certification Authority has conducted a thorough examination of the OEM’s

project experience and is satisfied with the information provided.

Note to OEM: OEM must fill in this form to prove conformance to Experience and Past
Performance in Section Qualifications Criteria. Mention contracts in which OEM is or
has been a party, whether as a Prime Bidder or JV/Consortium bidder, affiliate,
associate, subsidiary, Subcontractor, or any other role. The list below is indicative
only. Scanned Attested copies of completion/performance certificates from the Officer-
in-Charge for each work should be annexed in the support of information furnished.
You may attach more documents as required to showcase your past performance.
Additional details not covered elsewhere in your bid in this regard.

Contracting Contract Type of Scope of The total Status as

Entity – Name Title, Client Work in value of the on date ----
and Address Number and Contract order
Date

Table 47: Project Experience of the OEM

Page 361 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance for the Indian Railways

……………………..
(Signature with date)
………………………..
(Name and designation)
Duly authorized to sign bid for and on behalf of
……………………………………….
[name & address of Chartered Accountant and seal of company]

Page 362 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance for the Indian Railways

18.14. Annexure-14-CV of Key Personnel Proposed

1. Name of the Staff
2. Current Designation
in the Organization
3. Proposed Role in the
Project
4. Proposed
Responsibilities in
the Project
5. Date of Birth
6. Education ▪ Degree / Diploma, College, University, Year of
Passing
▪ Degree / Diploma, College, University, Year of
Passing
7. Summary of Key
Training and
Certifications
8. Language Language Reading Writing Speaking
Proficiency

9. Employment Record
(For the total From / To:
relevant experience)
Employer:

Position
Held:

From / To:

Employer:

Position
Held:

From / To:

Employer:

Position
Held:

10. Total No. of Years of

Work Experience

Page 363 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance for the Indian Railways

11. Total No. of Years of

Experience for the
Role proposed
12. Highlights of relevant assignments handled and significant accomplishments
(Use following format for each project) – Please mention all assignments that are
relevant for marking of profiles.
Name of
assignment or
project:

Year:

Location:

Client:

Main project
features:

Positions held:

Activities
performed:

Name of
assignment or
project:

Year:

Location:

Client:

Main project
features:

Positions held:

Activities
performed:

13. Expert’s contact information:

e-mail:
phone:

Page 364 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance for the Indian Railways

Certification:
I, the undersigned, certify that to the best of my knowledge and belief that:
• This CV correctly describes my qualifications and my experience.
• I was not part of the team who wrote the Scope of Work for this Bid
Document.
I understand that any wilful misstatement described herein may lead to my
disqualification or dismissal, if engaged.

Name
Signature:
Date:
Table 48: CV of Key Personnel Proposed

Page 365 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance for the Indian Railways

18.15. Annexure-15-Undertaking for Unpriced Bill of Quantity

Undertaking for Providing the Complete Unpriced Bill of Quantity for the
systems and applications proposed in the solutions.

To,
The Managing Director
CRIS, Chanakyapuri,
New Delhi – 110021.

Ref: Tender No....................................................................

Dear Sir,

We, <<name of the Bidder>>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the Public
Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We, <Name of the bidder> who are participating in the Bid Document published by
CRIS “Selection of Master System Integrator for the Central Video Management
System (CVMS) on the Public Cloud for the IP-based CCTV Surveillance System
for the Indian Railways ” do hereby confirm that we are offering the following systems
and applications in response to meet the requirements and specifications stipulated in
the Bid Document:
a. Complete list of the Software applications for the CVMS Solution
b. Complete list of the Resources provisioned on the Public Cloud
c. Any other Component supplied for the overall CVMS Solution

for all the software’s and tools proposed in the solutions offered for the Tender No:
__________________________________ furnish the complete Bill of Material (BoM)/
Bill of Quantity (BoQ) of offered products.
Software Applications
# Name of the Make License Year of Qty
Applications Version Release
a.
b.
…
Table 49: List of Software Applications

Systems Provisioned on the Public Cloud

# Cloud Configuration Software License Year of Qty
Resource Type Version Release
Type

Page 366 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance for the Indian Railways

a.
b.
…
Table 50: List of Systems Provided on Public Cloud

Any other Component

# Component Details of the Software License Year of Qty
Type Configuration Type Version Release
a.
b.
…
Table 51: List of Any Other Equipment

We further declare that at the time of Phase 1 Go-Live or Post Final Go-Live or anytime
during the contract period if there are any components or systems or applications that
are required to meet the functional requirements of the CVMS solution, the same shall
be provided by us without any additional cost to CRIS.

Your faithfully,

Note: This letter of authority shall be on the Letter-Head of the Bidder and shall be
signed by a person competent and having the power of attorney to bind the Bidder.

Page 367 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.16. Annexure-16-Format For Pre-Bid Queries

To

The Managing Director,

Center for Railway Information System,
Chanakyapuri
New Delhi - 110021

Dear Sir,

Subject: Queries/Clarifications regarding the bid document for Selection of Master

System Integrator for the Central Video Management System (CVMS) on the Public
Cloud for the IP-based CCTV Surveillance System for the Indian Railways .

Dear Sir,

We, <<name of the Bidder/OEM>>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the
Public Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We hereby submit our request for clarifications / suggestions on the provisions of the
above-referred Bid Document, as per the following:

Page Number of tender Clause Clarification

# Clause Number
document Description Sought/query
1.
2.
3.
4.
Table 52: Format for Pre-Bid Queries
Signature:

Name:

Designation:

Contact Phone:

Contact Email:

Date:

Page 368 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.17. Annexure-17-Performance Bank Guarantee

PROFORMA OF BANK GUARANTEE FOR 10% OF CONTRACT VALUE FOR

CONTRACT PERFORMANCE CUM WARRANTY CUM ANNUAL MAINTENANCE
CONTRACT GUARANTEE BOND

Ref………

Date…………

Bank Guarantee No…………

To

Managing Director,

Centre for Railway Information Systems,

Chanakyapuri,

New Delhi – 110021

Against contract vide Advance Acceptance of the Tender

No…………………………………… dated…………….covering the services of
……………………………………………………………………………………………………
….…..(hereinafter called the said `contract’) entered into between the MD/CRIS
(hereinafter called the CRIS) and ……………………………...(hereinafter called the
‘contractor’) this is to certify that at the request of the Contractor
1. We……………………….. Bank Ltd., are holding in trust in favour of the MD/CRIS,
the amount of …………………………………………………………(write the sum
here in words) to indemnify and keep indemnified the MD/CRIS against any loss or
damage that may be caused or likely to be caused to or suffered by the MD/CRIS
because of any breach by the Contractor of any of the terms and conditions of the
said contract and/or the performance thereof. We agree that the decision of the
MD/CRIS, whether any breach of any of the terms and conditions of the said
contract and/or in the performance thereof has been committed by the Contractor
and the amount of loss or damage that has been caused or suffered by the
MD/CRIS shall be final and binding on us and the amount of the said loss or
damage shall be paid by us forthwith on demand and without demur to MD/CRIS.
2. We ………………………………………….Bank Ltd., further agree that the
guarantee herein contained shall remain in full force and effect during the period
Page 369 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

that would be taken for satisfactory performance and fulfilment in all respects of the
said contract by the Contractor i.e. till……………………(viz. The date up to 06
months after the last date of the Annual Maintenance Contract) and shall continue
to be enforceable for another 6 months i.e. up to ………. Herein called the ‘said
date’ and that if any claim accrues or arises against us, ………………………….
Bank Ltd., by this guarantee before the said date, the same shall be enforceable
against us …………… Bank Ltd.) provided that notice of any such claim has been
given to us …………………. Bank Ltd., by CRIS before the said date. Payment
under this letter of guarantee shall be made promptly upon our receipt of notice to
that effect from MD/CRIS.
3. It is fully understood that this guarantee is effective from the date of the said
contract and that we ………...………. ………… Bank Ltd., undertake not to revoke
this guarantee during its currency without the consent in writing of CRIS.
4. We undertake to pay to CRIS any money so demanded notwithstanding any
dispute or disputes raised by the Contractor in any suit or proceeding pending
before any Court or Tribunal relating thereto our liability under this present being
absolute and unequivocal. The payments so made by us under this bond shall be a
valid discharge of our liability for payment there under and the Contractor shall
have no claim against us for making such payment.
5. We………………………Bank Ltd., further agree that the CRIS shall have the fullest
liberty, without affecting in any manner our obligations hereunder to vary any of the
terms and conditions of the said contract or to extend time of performance by the
Contractor from time to time or to postpone for any time or from time to time any of
the power exercisable by CRIS against the said contractor and to for bear or
enforce any of the terms and conditions relating to the said contracts and
we………………..….Bank Ltd., shall not be released from our liability under this
guarantee because of any such variation or extension being granted to the said
Contractor or for any forbearance and/or omission on the part of CRIS or any
indulgence by CRIS to the said Contractor or by any other matter or thing what –
so-ever, which under the law relating to sureties, would, but for this provision have
the effect of so releasing us from our liability under this guarantee.
6. CRIS shall be at liberty, from time to time, to grant or allow extension of time or
give other indulgence to the said contractor or to modify the terms and conditions
of the contract with the said contractor without affecting or impairing this guarantee
or our liability hereunder.
7. We ……………………………………………………… Bank Ltd. Further agree that
the guarantee herein contained shall not be affected by any change in the
constitution of the said contractor or the Bank.
8. We ……………………………………………………… Bank Ltd. Further agree that
the guarantee herein contained shall remain in full force and effect during the
period that would be taken for the performance of the said Agreement and that it
shall continue to be enforceable till all the dues of CRIS under or by the said
Agreement have been fully paid and its claims satisfied or discharged or till
…………………………………… CRIS certifies that the terms and conditions of the
Page 370 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

said Agreement has been fully and properly carried out by the said Contractor(s)
and accordingly discharges this Guarantee unless demand or claim under this
guarantee is made on us in writing on or before the ………………………………..we
shall be discharged from all liability under this Guarantee thereafter.

Date……………………..

Signature……………….

Place…………….. Name……………

Witness…………….

(Designation)

(Bank’s Common Seal)

Bank Address:

Telephone No.:

Fax No.

E-Mail Address:

Page 371 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.18. Annexure-18-Change Control

Change Control Note: CCN Number:
Part A: Initiation
Title:
Originator: MSI (___________________________________________________)
Approver: CRIS
Date of Initiation:
Details of Proposed Change
(To include reason for change and appropriate details/specifications. Identify any
attachments as A1, A2, and A3 etc.)
Impact:
Deliverables:
Timetable:
Charges: (for implementation including a schedule of payments)
a. Man-months Required

b. Total Cost involved

c. Other Relevant Information: (including value-added and acceptance

criteria)

Initiated by: Date:

Name:
Signature:
Received by CRIS: Date:
Name:
Signature:

Part B: Evaluation (by CRIS)

(Evaluation comments from CIRS)

Final Decision by CRIS:

a. Deliverables:

b. Man-Months:

c. Solution:

d. Costing:

e. Timelines:

Authorized by:
Name: Date:
Signature:
Part C: Authority to Proceed
Page 372 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Implementation of this CCN as submitted in Part A, in accordance with Part B is: (tick
as appropriate)
Approved Rejected Requires Further Information:

For CRIS and its nominated Agencies For MSI

Signature Signature
Name Name
Title Title
Date Date
Table 53: Format for Change Control

Page 373 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.19. Annexure-19-Long Term Maintenance Support

PROFORMA FOR “LONG TERM MAINTENANCE SUPPORT”
(To be signed by the Sole/Lead/Consortium Bidder as well as the OEM’s)
To,
Managing Director, CRIS, Chanakyapuri,
New Delhi – 110021.
Tender No. ______________

(Applicable for Lead Bidder/OEM directly participating in the tender)

We, <<name of the OEM/Bidder >>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the
Public Cloud for the IP-based CCTV Surveillance System for the Indian Railways”

I/We <<Name of the OEM>> Hereby confirm that we have read specifications & tender
conditions of Tender No. … and accept that the requirement of Long-Term
Maintenance Support for the complete contract period and shall be met by us directly
or through our subsidiary in India. I/We shall provide services as per terms and
conditions pertaining to Long Term Maintenance Support of tender document.

OR

Applicable for Authorized Distributor/Partner of OEM

I/We …………………………………………………………………. hereby confirm that we

have read specifications & tender conditions of Tender No.… and accept that the
requirement of Long-Term Maintenance for the contract period, shall be met by
Authorized Distributor/Partner of OEM. However, if Authorized Distributor/Partner fails
to fulfil the support obligation due to any unforeseen circumstances, the same shall be
provided by us directly or through our subsidiary in India for the mentioned/remaining
period at the quoted prices by the bidder. I/We have gone through the requirement
mentioned in the Tender Document and shall provide services as per terms and
conditions pertaining to Long Term Maintenance Support of tender document.

Signature of witness: Signature of Firm’s

(Authorized Officer) Seal
…………………

………………….
Note: Please Strike out whichever is not applicable.

Page 374 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.20. Annexure-20-Undertaking from OEM For Backend Support

Undertaking from OEM for backend support for the contract period

Dated : _
To,
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.
Tender Reference:
Dear Sir,

We, << Name of the OEM>> who are established and reputable manufacturers of
(name and description of goods) do hereby authorize M/s << Name of the MSI>> our
authorized Business partner and service provider to submit a bid, and sign the
contract with you for software applications manufactured by us against your above
mentioned tender. We will provide the backend support including software upgrades
and ensure availability of spares for the contract period.

We shall be providing our service support to M/s________________from our

Technical Support center(s) located at remote site across India. We assure you that
in the event M/s______________is not being able to fulfill its obligations as service
provider of our products, we would continue to provide OEM warranty/ATS services
through alternate available arrangements.

Yours faithfully

(OEM, Signature, Name, designation, Contact information)

Note: This letter of authority shall be on the letterhead of the manufacture and shall
be signed by a person competent and having the power of attorney to legally bind the
manufacturer / service provider.

Page 375 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.21. Annexure-21-Non-Disclosure Agreement

NON-DISCLOSURE AGREEMENT

THIS NON-DISCLOSURE AGREEMENT (this “Agreement”) is entered into on _______

by and between the undersigned parties on the date specified below:

Centre for Railway Information System incorporated /registered under the Companies
Act,1956/2013/ the societies registration Act,1860 having its registered/corporate office
at Chanakyapuri, New Delhi – 110021 (hereinafter referred to as “Consignee” which
expression shall unless repugnant to the context or meaning thereof, includes its
successors, administrators and permitted assigns) of the first part.

And

Name incorporated/registered under the…. ….. Name of the Act having its
registered/corporate office at ……………… (herein referred to as “Vendor” which
expression shall unless repugnant to the context or meaning thereof ,includes its
successors, assigns, administrators, liquidators and receivers)of the second part

WHEREAS both the Party possess certain confidential proprietary

information; and

AND

WHEREAS, in connection with the pursuit, evaluation and/or feasibility of

a business relationship, and/or the consummation of a transaction
(collectively, the “Business Purposes”) between the two parties hereto,
including their affiliates, subsidiaries, stockholders, partners, co-venture,
trading partners, employees and other organizations (hereinafter referred
to as Affiliates), confidential proprietary information of one Party may
become available to the other Party.

AND

WHEREAS both the Parties desire to prevent the unauthorized use and
disclosure of its confidential proprietary information.

Page 376 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

NOW THEREFORE, in consideration of these premises and for other good and
valuable consideration, Receipt of which is hereby acknowledged, the parties agree as
follows:

i. “Confidential Information”. For purposes of this Agreement, Confidential

Information shall mean all strategic and development plans, financial condition,
business plans, co-developer identities, data, business records, customer lists,
project records, market reports, employee lists and business manuals, policies and
procedures, information relating to processes, technologies or theory and all other
information which may be disclosed by one Party or to which the other Party may be
provided access to by the disclosing Party or others by this Agreement, or which is
generated as a result of, incidental to or in connection with the Business Purposes,
which is not generally available to the public.
ii. Non-disclosure Obligations. The Receiving Party promises and agrees to receive
and hold the Confidential Information in confidence. Without limiting the generality of
the foregoing, the Receiving Party further promises and agrees:
a. to protect and safeguard the Confidential Information against unauthorized
use, publication, or disclosure.
b. not to use any of the Confidential Information except for the Business
Purposes.
c. not to, directly or indirectly, in any way, reveal, report, publish, disclose,
transfer, or otherwise use any of the Confidential Information except as
specifically authorized by the Disclosing Party by this Non-Disclosure
Agreement.
d. not to use any Confidential Information to unfairly compete or obtain
unfair advantage vis-a-vis Disclosing Party in any commercial activity
which may be comparable to the commercial activity contemplated by
the parties in connection with the Business Purposes.
e. to restrict access to the Confidential Information to those of its officers,
directors, and employees who need such access to carry out the Business
Purposes.
f. to advise each of the persons to whom it provides access to any of the
Confidential Information, that such persons are strictly prohibited from
making any use, publishing or otherwise disclosing to others, or permitting
others to use for their benefit or to the detriment of the Disclosing Party,
any of the Confidential Information, and, upon Request of the Disclosing
Party, to provide the Disclosing Party with a copy of a written agreement
to that effect signed by such persons.
g. to comply with any other reasonable security measures requested in
writing by the Disclosing Party.
h. to refrain from directly contacting or communicating by whatsoever means
to the Source(s) of Information without written consent of the Disclosing
Party.

Page 377 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

i. to undertake not to disclose any names and their particulars to third

parties without the written consent by the Disclosing party.
iii. Exceptions. The confidentiality obligations hereunder shall not apply to Confidential
Information which:
a. is, or later becomes, public knowledge other than by breach of the
provisions of this Agreement; or
b. is in the possession of the Party with the full right to disclose before its
receipt from the Disclosing Party, as evidenced by written records; or
c. is independently received by the Receiving Party from a third party, with
no restrictions on disclosure.
iv. Return of Confidential Information. The Receiving Party agrees, upon termination
of the Business Purposes or upon the written request of the other Party, whichever
is earlier, to promptly deliver to the other Party all records, notes, and other written,
printed, or tangible materials in the possession of the Receiving Party, embodying or
about the Confidential Information.
v. No Right to Confidential Information.
a. The Receiving Party hereby agrees and acknowledges that no license,
either express or implied, is hereby granted to the Receiving Party by the
other Party to use any of the Confidential Information.
b. The Receiving Party further agrees that all inventions, improvements,
copyrightable works and designs relating to machines, methods,
procedures, practices, compositions, or products of the other Party directly
resulting from or relating to the Confidential Information and the right to
market, use, license and franchise the Confidential Information or the
ideas, concepts, methods or practices embodied therein shall be the
exclusive property of the other Party, and the Receiving Party has no right
or title thereto.
vi. No Warranty. The Disclosing Party has not made and will not make any
representation or warranty as to the accuracy or completeness of its Confidential
Information or any other information provided to the Receiving Party, and the
Receiving Party agrees that the Disclosing Party shall have no liability resulting from
the use of the Confidential Information or such other information.
vii. No Commitment. The disclosure of Confidential Information does not and is not
intended to, represent a commitment by the Disclosing Party to enter into any
business relationship with the Receiving Party or with any other entity. If the Parties
desire to pursue business opportunities, they will execute a separate written
agreement to govern such business relationship.
viii. Compelled Disclosure. If the Party faces legal action to disclose Confidential
Information received under this Agreement, then the Party shall promptly notify the
other Party so that it may have the opportunity to intervene and contest such
disclosure and, upon request, shall cooperate with the other Party in contesting such
a disclosure. Except in connection with failure to discharge the responsibilities
outlined in the preceding sentence, neither Party shall be liable in damages for any
disclosures under such legal action.
Page 378 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

ix. Losses. The Receiving Party agrees to indemnify the other Party against any
losses, damages, claims, or expenses incurred or suffered by the other Party as a
result of the Receiving Party’s breach of this Agreement.
x. Communication: The two parties agree that the communication between the parties
is considered delivered to the other party if transmitted by fax or electronic means
with proof of sending machine. All notices under this Agreement shall be deemed to
have been duly given upon the mailing of the notice, post-paid to the addresses
listed above, or upon the facsimile transmission, to the party entitled to such notice
at the facsimile number set forth below or by e mail.
xi. Counterparts. Either the original or copies of this Agreement, may be executed in
counterparts, each of which shall be an original as against any party whose
signature appears on such counterpart and all of which together shall constitute the
same instrument.
xii. Term and Termination. This Agreement shall commence on the date of signing of
this agreement written below. The Receiving Party’s right to use the Confidential
Information in connection with the Business Purposes shall continue in effect until
the period of three year from the date above or the other Party provides the
Receiving Party with written notice of termination of such right, whichever is earlier.
Notwithstanding the foregoing, the Receiving Party’s obligations concerning the
Confidential Information hereunder shall continue in full force for at least five years
from the termination date and/or effect until further notice from the other Party.
xiii. Remedies. The Receiving Party understands and acknowledges that any disclosure
or misappropriation of any of the Confidential Information in violation of this
Agreement may cause the Disclosing Party irreparable harm, the amount of which
may be difficult to ascertain and, therefore, agrees that the Disclosing Party shall
have the right to apply to a court of competent jurisdiction for an order restraining
any such further disclosure or misappropriation and for such other relief as the
Disclosing Party shall deem appropriate. Such right of the Disclosing Party shall be
in addition to Remedies otherwise available to the Disclosing Party at law or in
equity.
xiv.Entire Agreement. This Agreement embodies the entire understanding between the
parties respecting the subject matter of this Agreement and supersedes any prior
negotiations, correspondence, understandings and agreements between the parties
respecting the subject matter of this Agreement. This Agreement shall not be
modified except by a writing duly executed on behalf of the party against whom such
modification is sought to be enforced. Shall any provisions of this Agreement be
found unenforceable, the remainder shall still be in effect.

xv. No Waiver. The failure of either Party to require performance by the other Party of
any provision of this Agreement shall in no way affect the full right to require such
performance at any time thereafter.

Page 379 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

xvi.Successors and Assigns. This Agreement shall be binding on Party’s

Representatives, permitted assigns, and successors of the Parties and shall inure to
the benefit of Representatives, assigns and successors of the Parties.
xvii. Governing Law. This Agreement shall be governed by and construed by the
laws of India.
xviii. Jurisdiction: Courts in New Delhi only shall have jurisdiction.
xix.Modification: This Agreement constitutes the sole understanding of the parties
about this subject matter and may not be amended or modified except in writing
signed by each of the parties to the Agreement.

Legal Address of the Parties:

Party A: Party B:

Page 380 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.22. Annexure-22-Anti-Collusion Certificate

[Certificate shall be provided by Sole Bidder/ Lead Member of JV/ Consortium and on
company letter head]

Date: _____________

To,

Managing Director

CRIS, Chanakyapuri,

New Delhi – 110021.

Subject: Anti-Collusion Certificate in response to the “Selection of Master System

Integrator for the Central Video Management System (CVMS) on the Public Cloud for
the IP-based CCTV Surveillance System for the Indian Railways ”

Ref: The Bid Document No. ___________dated ___________

Dear Sir,

We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”

We hereby certify and confirm that in the preparation and submission of our Bid for
Selection of Master System Integrator for the Central Video Management System
(CVMS) on the Public Cloud for the IP-based CCTV Surveillance System for the
Indian Railways ”, against the bid document issued by Authority, we have not acted in
concert or collusion with any other Bidder or other person(s) and also not done any
act, deed, or thing, which is or could be regarded as anti-competitive. We further
confirm that we have not offered nor will offer any illegal gratification in cash or kind to
any person or organization in connection with the instant bid.

(Authorized Signatory of the Lead Bidder)

Printed Name
Page 381 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Designation

Seal

Date:

Place:

Business Address:

Page 382 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.23. Annexure-23-Deployment of Manpower

18.23.1. Annexure-23(A) - Project Implementation Phase
Technical Manpower Requirement for Project Implementation Phase

Bidder to provide the following minimum resources during the implementation phase
and these listed manpower shall be stationed at CRIS designated office premise
location, and the location shall be shared with the MSI.

Numbers of Minimum Qualification &

# Description Man Months
resources Experience

B.E./ B. Tech plus MBA with

1 No. (At Full time during
Project Manager 10 years of experience of
1. CRIS HQ in implementation
(SPoC) handling IT/ICT/ Surveillance/
New Delhi) period
Networking large project

B. Tech/B.E./Diploma in
Surveillance 1 No. (At electronics & communication Full time during
2. Solution SME Or CRIS HQ in with 10 years of experience implementation
Architect New Delhi) in Surveillance period
Projects/Industry with
Expertise in VMS & ICCC
B.E./ B. Tech with 10 years
1 No. (At of experience of handling Full time during
Cloud Solution Cloud implementation
3. CRIS HQ in implementation
SME Or Architect projects with certification in
New Delhi) period
Public Cloud Platforms
proposed for this project.
B. Tech/B.E./Diploma in
As per electronics & communication
Commissioning Full time during
Project with 6 years of experience in
4. Engineer implementation
timeliness Surveillance
(Surveillance) period
requirement Projects/Industry with
Expertise in VMS & ICCC
B. Tech/B.E. with relevant
Commissioning As per experience of 6 Years of Full time during
Engineer Project handling Cloud
5. implementation
(Cloud) timeliness implementation projects with period
requirement certification in Public Cloud
Platforms.
Facial As per B. Tech/B.E. in electronics &
Recognition Project communication with 10 years On need basis
6.
Solution (FR) timeliness of experience in Surveillance
Expert requirement Projects/Industry with

Page 383 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Numbers of Minimum Qualification &

# Description Man Months
resources Experience

Expertise in FR (OEM
certification for the proposed
FR in this proposed project)
B. Tech/B.E./Diploma
As per Graduation with relevant
Database Project experience of 10 Years of
7. On Need Basis
Architect timeliness experience in designing
requirement database for large scale
project
As per B. Tech/B.E./Diploma
Enterprise
Project Graduation with relevant
8. Management On Need Basis
timeliness experience of 6 Years of
System (EMS)
requirement large-scale project
Expert
experience in EMS
B. Tech/B.E./Diploma
As per Graduation with relevant
Project experience of 10 Years of
9. IT/ Cyber On Need Basis
timeliness large-scale project
Security Expert
requirement experience in IT/Cyber
security

B. Tech/B.E./Diploma
As per Graduation with relevant
Project experience of 10 Years of
10. Developer On Need Basis
timeliness Software development
requirement experience

As per B. Tech/B.E./Diploma
Project Graduation with relevant
11. Tester experience of 5 Years of On Need Basis
timeliness
requirement Software testing experience

Table 54: Manpower for Project Implementation

Page 384 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.23.2. Annexure-23(B) –Operations Phase

Manpower Requirement for Project Operations Phase

Bidder to provide the following minimum resources during the Project Operations phase
and these listed manpower shall be stationed at CRIS designated office premise
location, and the location shall be shared with the MSI.

# Description Numbers of Minimum Man Billable

resources Qualification & Months as per
Experience SoR

1. Project Manager 1 No. (At CRIS B.E./ B. Tech/ MBA Full time No
(SPoC) HQ in New with 10 years of during
Delhi) experience of O&M
handling IT/ICT/ period for
Surveillance/ the entire
Networking or duration
similar sized large of the
and complex Project
projects

2. Surveillance 1 No. B.Tech/B.E./Diplo On-Need No

Solution SME Or ma in electronics & Basis for
Architect communication the entire
with 10 years of duration
experience in of the
Surveillance Project
Projects/Industry
with Expertise in
VMS & ICCC

3. Cloud Solution 1 No. B.E./ B. Tech with On-Need No

SME Or 10 years of Basis for
Architect experience of the entire
handling Cloud duration
implementation of the
projects with Project
certification in
Public Cloud
Platforms.
4. O&M Engineer 2 No. B. Tech/B.E./ Full time No
(Surveillance) Diploma in during
electronics & O&M

Page 385 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Description Numbers of Minimum Man Billable

resources Qualification & Months as per
Experience SoR

communication period for

with 6 years of the entire
experience in duration
Surveillance of the
Projects/Industry Project
with Expertise in
VMS & ICCC
5. O&M Engineer 1 No. B. Tech/B.E. with Full time No
(Cloud) relevant during
experience of 6 O&M
Years of handling period for
Cloud the entire
implementation duration
projects with of the
certification in Project
Public Cloud
Platforms.
6. Facial As per Project B. Tech/B.E. in On-Need No
Recognition timeliness electronics & Basis for
Solution (FR) requirement communication the entire
Expert with 10 years of duration
experience in of the
Surveillance Project
Projects/Industry
with Expertise in
FR (OEM
certification for the
proposed FR in
this proposed
project)
7. Database As per Project B. On-Need No
Architect timeliness Tech/B.E./Diploma Basis for
requirement Graduation with the entire
relevant duration
experience of 10 of the
Year of experience Project
in designing
database for large
scale project

Page 386 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Description Numbers of Minimum Man Billable

resources Qualification & Months as per
Experience SoR

8. Enterprise 1 no. B. Full time No

Management Tech/B.E./Diploma during
System (EMS) Graduation with O&M
Expert relevant period for
experience of 6 the entire
Year of large-scale duration
project experience of the
in EMS Project

9. IT/ Cyber As per Project B.Tech/B.E./Diplo On-Need No

Security Expert timeliness ma Graduation Basis for
requirement with relevant the entire
experience of 10 duration
Year of large-scale of the
project experience Project
in IT/Cyber security
10. ICCC Operator 2 nos. x 3 Any Graduation Full time No
Shifts = 6 nos. with minimum 2 during
per day years of CCTV O&M
period for
Surveillance
the entire
experience, duration
experienced in of the
using the ICCC Project
application and
should have
completed ICCC
OEM training
(OEM Training
Completion
Certificate to be
provided).
11. Helpdesk As per the bid Any Diploma / Full time Yes
Executive document Graduation with during
Requirement Experience of at O&M
least 6 months in a period for
Contact Center, or the entire
in technical duration
helpdesk support of the
service. Project

Page 387 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Description Numbers of Minimum Man Billable

resources Qualification & Months as per
Experience SoR

12. Helpdesk As per the bid Graduation with 8 Full time Yes
Manager/Superv document years of during
isor Requirement experience in O&M
Surveillance/ ICT period for
Projects the entire
duration
of the
Project

13. Database As per the bid Graduation with a Full time No

administrator document minimum of 8 during
Requirement years of O&M
period for
experience in
the entire
administrating duration
databases as per of the
the DB solutions Project
proposed for this
Project.
14. Developer As per the bid B.Tech/B.E./Diplo On-Need No
document ma Graduation Basis for
Requirement with relevant the entire
experience of 10 duration
Year of large-scale of the
project experience Project
in Software
Development
relevant to the
solution deployed
in the CVMS stack
15. Tester As per the bid B.Tech/B.E./Diplo On-Need No
document ma Graduation Basis for
Requirement with relevant the entire
experience of 5 duration
Year of large-scale of the
Testing experience Project

Table 55: Manpower for Project Operations Phase

Page 388 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.24. Annexure-24-Undertaking from OEM for IPR

Undertaking from OEM for Intellectual Property Rights

To,
The Managing Director

CRIS, Chanakyapuri,
New Delhi – 110021.

Ref: Tender No....................................................................

Dear Sir,

We, _____________________who are established and reputable manufacturers of

__________________________________(name and description of goods) do hereby
confirm that we are the genuine manufacturers of the
__________________________________(name and description of goods) and have
our own manufacturing setups and IPR for the hardware(s) / software(s), and do not
have 3rd party manufacturing arrangements with any company blacklisted in India or
abroad due to proven backdoor access and data vulnerability, or for any other reason.

We shall indemnify the Railways/ CRIS from and against all Third-Party claims of
infringement of patent, trademark/copyright or industrial design rights arising from the
use of the above-mentioned products or systems supplied by us and related services or
any part thereof.

We agree to defend the Railways/ CRIS against claims, lawsuits, or legal actions
brought by third parties that allege the products or systems and related services, or any
part thereof infringe on intellectual property rights or other legal rights.

We agree to indemnify Railways/ CRIS for losses, damages, costs, and expenses
incurred as a result of the legal claims or actions arising from the infringement of
intellectual property rights related to the products or systems and related services or
any part thereof.

We also hereby confirm that the Intellectual Property Rights (IPR) of all the
manufactured final product and source code of all software including firmware, etc. does
not reside in countries sharing land borders with India and is registered with the
Competent Authority of Government of India.
Page 389 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

We hereby confirm that the latest Public Procurement Policy & other related orders
issued by Government of India are being followed.

Your faithfully,

(Authorised Signatory)

Name of the OEM :

Place :

Date :

Company Seal :

Note: This letter of authority shall be on the Letter-Head of the manufacturing concern
and shall be signed by a person competent and having the power of attorney to bind
the manufacturer.

Page 390 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.25. Annexure-25-Total Responsibility Certificate

(To be provided on the Company letterhead of the Sole Bidder/ Lead Member of JV/
Consortium)

Date: ___________

To,

Managing Director

CRIS, Chanakyapuri,

New Delhi – 110021.

Subject: Self Declaration of Total Responsibility in response to the “Selection of

Master System Integrator for the Central Video Management System (CVMS) on the
Public Cloud for the IP-based CCTV Surveillance System for the Indian Railways ”

Ref: Bid Document No. ________________dated___________

Dear Sir,

We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”.

This is to certify that we undertake the total responsibility for the defect free operation
of the proposed project, solution and any or all systems and applications thereof as
per the requirement of the Bid Document for the duration mentioned in the the bid
document or during any extensions provided by the Department.

(Authorized Signatory)

Signature:

Name:

Designation:

Address:

Seal:

Date:

Page 391 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.26. Annexure-26-Certificate Land Border with India

Certificate from Bidder for compliance (to be uploaded/attached alongwith their
Bid/Offer)

I have read the clause/Para regarding restrictions on procurement from a Bidder of a

country which shares a land border with India and on sub-contracting to contractors
from such countries.

(a). I certify that M/s (name of Bidder)is not from such a country and will
not sub-contract any work to a contractor from such countries unless such contractor
is registered with the Competent Authority. I also certify that M/s will not offer any
products/services of entity from such countries unless such entity is registered with
the Competent Authority.

Or

(b) I certify that M/s (name of Bidder) is from such a country and
has been registered with the Competent Authority. I also certify that M/s has
products/services of entity from such countries and these entity/entities are also
registered with the Competent Authority. I also certify that M/s has sub-
contracted some work to a contractor from such countries and that such contractor is
registered with the Competent Authority.

I hereby certify that M/s (name of Bidder) fulfills all requirements in this regard and is
eligible to be considered.

I hereby acknowledge that in the event of acceptance of my bid on above certificate

and if the certificate is found to be false at any stage, the false certificate would be a
ground for immediate termination of contract and further legal action by the Law.

(Signature & Name of Authorized person of the Bidder)

Name & address of the Bidder with stamp

Note:
1. Give certificate for either (a) or (b)
2. Where applicable, evidence of valid registration by the Competent Authority
shall be attached/uploaded alongwith the bid/offer
3. Bidders are advised to attach/upload the certificate duly signed by
authorized person of the Bidder and duly stamped alongwith their Bid/Offer.

Page 392 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.27. Annexure-27-Declaration for Proof of Concept

Date:

To

Managing Director,

CRIS, Chanakyapuri,

New Delhi – 110021.

Sub: Undertaking for complying with Proof-of-Concept Requirements for the tender no.
…………………..

Dear Sir,

We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”, and have carefully gone through the Section of Proof of Concept
contained in the Bid Document-II. Please find mentioned below, the details of the
applications that have been demonstrated during the Proof-of-Concept.

1. Name of The Bidder

2. Date of POC
3. Architecture Document Number/Version
4. Details of the applications that have been
demonstrated during the Proof-of-Concept
a. <Name of the Applications> <details of the applications>
b. <Name of the Applications> <details of the applications>
5. Version of the applications demonstrated
a. <Name of the Applications> <Version details>
b. <Name of the Applications> <Version details>

Further, We <<name of the undersigned Bidder>> accept the scenarios/Use cases

that have to be demonstrated through the Proof of Concept. We also hereby confirm
that we shall supply a similar version or a higher version of the applications which
have been demonstrated during the Proof-of-Concept.

I certify that I am a competent officer in my company to make this declaration.

Yours Sincerely,

(Authorized Signature)

Page 393 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Name of the Bidder :

Place :

Date :

Company Seal :

Page 394 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.28. Annexure-28-Declaration for Project Office

<<To be provided on the letterhead of the Bidder >>

Date:

To

Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking for operating project office in Delhi NATIONAL CAPITAL REGION
Dear Sir,
We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”.
We <<name of the undersigned Bidder>> having project office at
_______________________________________ (complete address In National
Capital Region) and operating in India from last <Insert no of years > years as on bid
publishing date.
OR
We <<name of the undersigned Bidder>> shall establish project office at New Delhi
within one month from the date of issuance of LoI.

I further certify that I am competent officer in my company to make this declaration.

Yours Sincerely,

(Authorized Signature)

Name of the Bidder :

Place :

Date :

Company Seal :

Page 395 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.29. Annexure-29-Undertaking for Valid License for Software

Undertaking for Valid License for Software and Tools supplied for the Project.

To,
The Managing Director

CRIS, Chanakyapuri,
New Delhi – 110021.

Ref: Tender No....................................................................

Dear Sir,

We, <<name of the OEM >>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the Public
Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We, _____________________who are established and reputable manufacturers of

__________________________________(name and description of software’s and
Tools) do hereby confirm that for all the software’s and tools proposed in the solutions
offered for the Tender No:__________________________________ are licensed and
these licensed software’s and tools have a perpetual license with a right to use the
software indefinitely by the tendering authority and its authorised users.

Your faithfully,

Note: This letter of authority shall be on the Letter-Head of the OEM and shall be
signed by a person competent and having the power of attorney to bind the OEM.

Page 396 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.30. Annexure-30-CSP’s Authorization Form (CAF)

<Tender specific original signed copy on CSP’s Letterhead>

To
Managing Director,
Centre For Railway Information System,
Indian Railway

Ref: Authorization for Participation in the bid document of the Centre For Railway
Information System titled "Selection of Master System Integrator for the Central
Video Management System (CVMS) on the Public Cloud for the IP-based CCTV
Surveillance System for the Indian Railways ”

Dear Sir,

It is certified that we, M/S ………………………………… <Registered name of the CSP

and its communication address>, having cloud services facilities in India at
…………………………………………………………… <Cloud Location(s)>, do hereby
authorize M/s ………………………… <Registered name of the Bidder (MSI) and its
communication address> to participate and submit a bid against the bid document as
referred above.

We hereby confirm that the cloud solution and services offered by the mentioned
partner are fully complying to the requirements mentioned in the bid document.

Yours faithfully,

________________________
Name & Designation of the
Authorized Signatory of the CSP

Date:

Page 397 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.31. Annexure-31 –Agreements for JV & Consortium

18.31.1. Annexure-31(A) - Joint Venture Agreement
(On Stamp Paper of appropriate value)

This Joint Venture Agreement is executed at on this ……………………. day of

………. 2024.
BETWEEN
M/s.............................…………………………………………. having its Registered
Office at ………………………………………………………. acting through its
………………………, duly authorized (hereinafter referred to as the “LEAD MEMBER”
which expression unless excluded by or repugnant to the subject or context be
deemed to mean and include its successors in interest, legal representatives,
administrators, nominees and assigns) of the ONE Part;
AND
M/s.............................………………………………………….having its Registered
Office at ……………………………………………………. acting through its
………………………, duly authorized (hereinafter referred to as the “PARTICIPANT
MEMBER” which expression unless excluded by or repugnant to the subject or context
be deemed to mean and include its successors in interest, legal representatives,
administrators, nominees and assigns) of the OTHER Part
AND
M/s.............................………………………………………….having its Registered
Office at ……………………………………………………. acting through its
………………………, duly authorized (hereinafter referred to as the “PARTICIPANT
MEMBER” which expression unless excluded by or repugnant to the subject or context
be deemed to mean and include its successors in interest, legal representatives,
administrators, nominees and assigns) of the OTHER Part
WHEREAS Centre or Railway Information Systems, New Delhi; an Organization
under the Ministry of Railways, Government of India (hereinafter referred to as “CRIS”)
has invited bids vide its Tender No…………………… for the “(NAME OF WORK)”
(hereinafter referred to as the “Project”) in terms of the tender documents issued for
the said purpose and the eligibility conditions required that the applicants bidding for
the same shall meet the conditions stipulated by CRIS for participating in the bid by
the Joint Venture for handling the Project for which the tender has been floated by
CRIS.
AND WHEREAS in terms of the Bid Documents the parties jointly satisfy the
eligibility criteria laid down for a Bidder for participating in the bid process by forming a
Joint Venture between themselves.

Page 398 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

AND WHEREAS the parties hereto have discussed and agreed to form a Joint
Venture for participating in the aforesaid bid and have decided to reduce the agreed
terms to writing.
NOW THIS Joint Venture Agreement hereby WITNESSES:
1. That in the premises contained herein the LEAD MEMBER and the
PARTICIPANT MEMBERS having decided to pool their technical know-how,
working experiences and financial resources, have formed themselves into a
Joint Venture to participate in the tender process for Name of
Work…………………………………. in terms of the Tender
No…………………………. invited by CRIS.
2. That the members of the Joint Venture have represented and assured each
other that they shall abide by and be bound by the terms and conditions
stipulated by CRIS for awarding the tender to the Joint Venture so that the Joint
Venture may take up the aforesaid Name of
Work:…………………………………. in case the Joint Venture turns out to be
the successful Bidder in the bid being invited by CRIS against Tender
No…………………………. for the said purpose.
3. That the members of the Joint Venture have satisfied themselves that by
pooling their technical know-how and technical and financial resources, the
Joint Venture fulfils the prequalification/ eligibility criteria stipulated for a Bidder,
to participate in the bid for the said tender process for Name of
Work:…………………………………. in terms of the Tender
No………………………….invited by CRIS
4. That the Joint Venture have agreed to nominate LEAD MEMBER as the
common representative who shall be authorized to represent the Joint Venture
for all intents and purposes for dealing with the Government and for submitting
the bid as well as doing all other acts and things necessary for submission of
Bid Documents such as Tender Application Form etc., Mandatory Information,
Financial Bid, etc., and such other documents as may be necessary for this
purpose.
5. That if any change in the membership of the Joint Venture be required to be
made by the members of the Joint Venture, the same shall be done with the
consent of CRIS subject to the conditions as may be stipulated by them in this
regard.
6. That in case to meet the requirements of Bid Documents or any other
stipulations of CRIS, it becomes necessary to execute and record any other
documents amongst the members of the Joint Venture, they undertake to do
the needful and to participate in the same for the purpose of the said project.
7. That it is clarified by and between the members of the Joint Venture that
execution to this Joint Venture Agreement by the members of the Joint Venture
does not constitute any type of partnership for the purposes of provisions of the
Page 399 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Indian Partnership Act and that the members of the Joint Venture shall
otherwise be free to carry on their independent business or commercial
activities for their own respective benefits under their own respective names
and styles. This Joint Venture Agreement is limited in its operation to the
specified project.
8. That the Members of the Joint Venture undertake to specify their respective
roles and responsibilities for the purposes of implementation of this Joint
Venture Agreement and the said Project, if awarded to the Joint Venture, to
meet the requirements and stipulations of CRIS.
9. The Joint Venture formed will not be subject to alteration with regard to change
in constituting firms and/or reorientation of roles. Any changes, if proposed by
Joint Venture to take advantage of certain developments during evaluation
stage will render the bid liable to be REJECTED.
10. All Partners of the Joint Venture shall be jointly and severally liable to CRIS for
the execution of the entire contract in accordance with its terms.
11. The distribution of responsibilities in execution of Work and the percentage
participation amongst various Partners of the Joint Venture for wok against
Tender No…………………………. invited by CRIS shall be as under:
S. Name of Role Distribution of % Participation in
No. the Responsibilities in the Project (in
Member Execution of Work terms of Price)
1. Lead Member Minimum 51%
2. Participant Member
3. Participant Member
Total 100%
Table 56: Distribution of Responsibilities in a Joint Venture
12. Power of Attorney by all members of the Joint Venture in favour of the Lead
Member is also enclosed.

IN FAITH AND TESTIMONY WHEREOF, THE PARTIES HERETO HAVE SIGNED

THESE PRESENTS ON THE DATE, MONTHS AND YEAR FIRST ABOVE WRITTEN

Signed, Sealed & Signed, Sealed & Signed, Sealed &

Delivered For & on behalf Delivered For & on behalf Delivered For & on behalf
of of of

Name of Company: Name of Company: Name of Company:

Page 400 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Lead Member Participant Member Participant Member

Signature: Signature: Signature:

Name of Signatory: Name of Signatory: Name of Signatory:

Designation: Designation: Designation:

Address: Address: Address:

WITNESSES:
1…………………………………………….
2………………………………………………

Page 401 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.31.2. Annexure-31(B)-Consortium Agreement

(On Stamp Paper of appropriate value)

This Consortium Agreement is executed at on this ……………………. day of ……….

2024.

BETWEEN

M/s.............................…………………………………………. having its Registered

Office at ………………………………………………………. acting through its
………………………, duly authorized (hereinafter referred to as the “LEAD MEMBER”
which expression unless excluded by or repugnant to the subject or context be
deemed to mean and include its successors in interest, legal representatives,
administrators, nominees and assigns) of the ONE Part.

AND

M/s.............................…………………………………………. having its Registered

Office at ……………………………………………………. acting through its
………………………, duly authorized (hereinafter referred to as the “PARTICIPANT
MEMBER” which expression unless excluded by or repugnant to the subject or context
be deemed to mean and include its successors in interest, legal representatives,
administrators, nominees and assigns) of the OTHER Part

AND

M/s.............................…………………………………………. having its Registered

Office at ……………………………………………………. acting through its
………………………, duly authorized (hereinafter referred to as the “PARTICIPANT
MEMBER” which expression unless excluded by or repugnant to the subject or context
be deemed to mean and include its successors in interest, legal representatives,
administrators, nominees and assigns) of the OTHER Part

WHEREAS Centre or Railway Information Systems, New Delhi; an Organization under

the Ministry of Railways, Government of India (hereinafter referred to as “CRIS”) has
invited bids vide its Tender No…………………… for the “(NAME OF WORK)”
(hereinafter referred to as the “Project”)in terms of the tender documents issued for the
said purpose and the eligibility conditions required that the applicants bidding for the
same should meet the conditions stipulated by CRIS for participating in the bid by the
Consortium for handling the Project for which the tender has been floated by CRIS.

AND WHEREAS in terms of the bid documents the parties jointly satisfy the eligibility
criteria laid down for a bidder for participating in the bid process by forming a
Consortium between themselves.

Page 402 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

AND WHEREAS the parties hereto have discussed and agreed to form a Consortium
for participating in the aforesaid bid and have decided to reduce the agreed terms to
writing.

NOW THIS Consortium Agreement hereby WITNESSES:

1. That in the premises contained herein the LEAD MEMBER and the
PARTICIPANT MEMBERS having decided to pool their technical know-how,
working experiences and financial resources, have formed themselves into a
Consortium to participate in the tender process for Name of Work:
………………………. in terms of the Tender No…………………………. invited
by CRIS.
2. That the members of the Consortium have represented and assured each other
that they shall abide by and be bound by the terms and conditions stipulated by
CRIS for awarding the tender to the Consortium so that the Consortium may
take up the aforesaid Name of Work: ………………………………. in case the
Consortium turns out to be the successful bidder in the bid being invited by
CRIS against Tender No…………………………. for the said purpose.
3. That the members of the Consortium have satisfied themselves that by pooling
their technical know-how and technical and financial resources, the Consortium
fulfils the prequalification/eligibility criteria stipulated for a bidder, to participate
in the bid for the said tender process for Name of Work: …………………. in
terms of the Tender No…………………………. invited by CRIS.
4. That the Consortium have agreed to nominate LEAD MEMBER as the common
representative who shall be authorized to represent the Consortium for all
intents and purposes for dealing with the Government and for submitting the bid
as well as doing all other acts and things necessary for submission of bid
documents such as Tender Application Form etc., Mandatory Information,
Financial Bid, etc., and such other documents as may be necessary for this
purpose.
5. That if any change in the membership of the Consortium be required to be
made by the members of the Consortium, the same shall be done with the
consent of CRIS subject to the conditions as may be stipulated by them in this
regard.
6. That in case to meet the requirements of bid documents or any other
stipulations of CRIS, it becomes necessary to execute and record any other
documents amongst the members of the Consortium, they undertake to do the
needful and to participate in the same for the purpose of the said project.
7. That it is clarified by and between the members of the Consortium that
execution to this Consortium Agreement by the members of the Consortium
does not constitute any type of partnership for the purposes of provisions of the
Indian Partnership Act and that the members of the Consortium shall otherwise
be free to carry on their independent business or commercial activities for their
own respective benefits under their own respective names and styles. This
Consortium Agreement is limited in its operation to the specified project.
Page 403 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

8. That the Members of the Consortium undertake to specify their respective roles
and responsibilities for the purposes of implementation of this Consortium
Agreement and the said Project, if awarded to the Consortium, to meet the
requirements and stipulations of CRIS.
9. The Consortium formed will not be subject to alteration with regard to change in
constituting firms and/or reorientation of roles. Any changes, if proposed by
Consortium to take advantage of certain developments during evaluation stage
will render the bid liable to be REJECTED.
10. All Partners of the consortium shall be jointly and severally liable to CRIS for
the execution of the entire contract in accordance with its terms.
11. The distribution of responsibilities in execution of Work and the percentage
participation amongst various Partners of the Consortium for wok against
Tender No…………………………. invited by CRIS shall be as under:

S. Name of the Role Distribution of % Participation in

No Member Responsibilities the Project (in
in terms of Price)
Execution of
Work
1. Lead Member Minimum 51%

2. Participant
Member

3. Participant
Member

Total 100%

Table 57: Distribution of Responsibilities in a Consortium

12. Power of Attorney by all members of the Consortium in favour of the Lead
Member is also enclosed.

IN FAITH AND TESTIMONY WHEREOF, THE PARTIES HERETO HAVE SIGNED

THESE PRESENTS ON THE DATE, MONTHS AND YEAR FIRST ABOVE WRITTEN

Signed, Sealed & Signed, Sealed & Signed, Sealed &

Delivered Delivered Delivered
For & on behalf of For & on behalf of For & on behalf of

Page 404 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Name of Company: Name of Company: Name of Company:

LEAD MEMBER PARTICIPANT MEMBER PARTICIPANT MEMBER

Signature: Signature: Signature:

Name of Signatory: Name of Signatory: Name of Signatory:

Designation: Designation: Designation:

Address: Address: Address:

Page 405 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.32. Annexure-32-SLA of the Coaches

1. Camera Failure: Where data-feed/Health monitoring feed from any one or more
Cameras is not received in the Central Video Management System (CVMS) for
more than 30 minutes due to reasons attributable to the vendor, such cases
shall be considered as ‘Camera Failure’. If on monthly basis, the number of
such ‘Camera Failure’ exceeds 2.0% of the total number of Cameras
commissioned in a particular Group, it shall attract a penalty as defined in
‘Camera Failure’ item of the Clause 10.2 - titled “Penalties”. ‘Month’ for the
purpose of calculating ‘Camera Failures’ means ‘Calendar Month’. For
calculating percentage of Camera Failures in a particular month, the total no. of
Cameras will be the no. of Cameras in that particular Group that have been
commissioned till the last date of previous month.
2. If the number of Camera failures exceeds 2.0% in a month, it shall attract
penalty as defined in ‘Camera Failure’ item of the Clause 10.2 - titled
“Penalties”.
3. In case of multiple failures of a particular camera on a particular calendar day,
the penalty for such failures shall not be imposed more than once. Also, such
multiple failures of a particular camera on a particular calendar day will be
counted only once for calculating monthly failures during a particular month.
4. In case of hardware or software failure, the repair/replacement must be done by
the end of next calendar day (i.e. 0:00 hours to 24:00 hours), subject to the
availability of Coach for a minimum 4 (Four) hours period. If the Bidder fails to
repair/replace the defective component(s) by the end of next calendar day (i.e.
0:00 hours to 24:00 hours), it shall attract penalty as defined in ‘Penalty on
failure of Repair/Replacement Services on Time’ item of the Clause 10.3 - titled
“Penalties”.
5. The Bidder shall perform Root Cause Analysis of all failures - a detailed
technical analysis report on the root cause and steps taken for avoiding such
recurrence of such failure from bidder shall be submitted within 07 working days
from the date of availability of coach to bidder. Bidder is bound to take
necessary preventive / corrective measures, etc. based on CRIS/Railways
advice.
6. In case of “Other than camera failures”, penalties shall be applicable as per
Clause no. 10.2 and Clause no. 10.3.1.
7. In case of multiple instances of “Other than camera failures” of a particular
device on a particular calendar day, the penalty for such failures shall not be
imposed more than once. Also, such multiple instances of “Other than camera
failures” of a particular device on a particular calendar day will be counted only
once for calculating monthly failures during a particular month.

Penalties
1. Penalties shall be calculated on the basis of ‘Camera Failures’. Penalties shall
be deducted from the instalment of the amount due for payment under this
contract. In case penalties exceed the invoice amount, the bidder shall have to
Page 406 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

deposit the due penalty amount within 7 days from the date of issue of demand
letter. In case the bidder does not deposit the penalty amount within stipulated
time, CRIS reserves the right to recover the due amount as under:
a. From subsequent bills or any other bill pertaining to this contract,
b. From any other pending bills of the bidder in CRIS/Railways,
c. From PWAMCBG furnished for this contract or any other contract
awarded by CRIS/Railways.
d. Penalties specified under amended clause 10.2 and 10.3.1 on account of
breach in SLAs shall be applicable only after expiry of period of one (01)
month after original/refixed delivery period for milestone M4(a) for first 10
number of coaches under amended clause 16.3.

However, the failures detected & reported by Railways / CRIS shall be eligible for
imposition of penalty specified under amended clause 10.2 & 10.3.1 on account of
breach in SLAs even before integration with CVMS.

Penalties shall be as per table given below:

Page 407 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Failure Penalties
1. Camera Failure Rs.1000/- per Camera Failure for
failure rate between exceeding 2% &
upto 4% per month

Rs.2000/- per Camera Failure for

failure rate greater than 4% per month
2. Failure to replace/repair faulty Penalty as per Clause 10.3 will be
Camera to make its data-feed imposed in case vendor fails to
available (subject to the availability replace/repair faulty Camera to make
of Coach for a minimum 4 (Four) its data-feed available (subject to the
hours period) availability of Coach for a minimum 4
(Four) hours period)
3. Other than Camera Failure like:- Rs.250/- per deficiency for failure rate
between exceeding 2% & upto 4% per
● Panic button faulty / non- month
operational/ damaged
● Strobe light and buzzer / hooter
faulty / non-operational/
damaged Rs.500/- per deficiency for failure rate
● If Storage provisioning is not in greater than 4% per month
line with the user requirement
specified in the RDSO
specification & bid document. Penalty as per clause 10.3 will be
● SIM cards / eSIM not provided imposed in case of vendor fails to
from two different service replace/repair deficiency.
providers
● Signage’s not provided or
maintained (subject to the availability of Coach for
● Handheld terminal provided are a minimum 4 (Four) hours period)
not maintained or faulty
● Video feed resolution not in line
with the RDSO specification &
contract..
● Defect/malfunctioning/insulation
puncturing etc. of
wires/cables/other components
● Unforeseen events due to poor
assets maintenance attributable
to the contractor
(subject to the availability of Coach
for a minimum 4 (Four) hours
period)
4. In case of the failure of the installed Penalty as per amended clause 10.3 will
components as part of CCTVSS be imposed in case of vendor fails to
system is due to reported rectify the issue within the stipulated
vandalism/theft/fire/ accident etc,.,
Page 408 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Failure Penalties
then contractor will be provided 7- buffer period of 7 days after notification
day of buffer period to rectify the for the same by the nominated authority
issue & make faulty component of Railway/CRIS.
operational and ensure compliance
of amended clause 2.2.4 of this
Document. However, if the
contractor is not able to rectify the (subject to the availability of Coach for
issue within seven days of buffer a minimum 4 (Four) hours period)
period even after making coach
available for minimum 4 hours in the
said period, penalty as stated shall
be applicable.

Penalty on failure of Repair/Replacement Services on time

Penalties as per telescopic rate mentioned below will be imposed.

Type of Failure Duration of Deduction/Penalties Deduction/Penalties

as defined in Repair/ during Warranty during CAMC Period*
Clause-9 Replacement* Period*
Camera Failure More than 1 day @Rs.250/- per day or @Rs.50/- per day or part
& up to 7 days part thereof thereof

Camera Failure More than 7 days @ Rs.500/- per day @ Rs.100/- per day or part
or part thereof thereof beyond 7 days in
beyond 7 days in addition to above
addition to above deduction/Penalty.
deduction/ Penalty.
Other than More than 1 day @Rs.50/- per day or @Rs.10/- per day or part
Camera Failure & up to 7 days part thereof thereof

(New)
Other than More than 7 days @ Rs.100/- per day @ Rs.20/- per day or part
Camera Failure or part thereof beyond thereof beyond 7 days in
7 days in addition to addition to above
(New) above deduction/ deduction/Penalty.
Penalty.
*Only those Calendar Days shall be considered for deductions/penalties when Coach
has been made available to vendor for a minimum 4 (Four) hours period.

Note:
In case there is spill-over of the failure from Warranty Period to CAMC or from one
CAMC year to next CAMC year, the Deduction/Penalty as per the applicable rates for
that period.
Page 409 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

The overall penalties annually during Warranty Period shall be capped to 10% of the full
contract value (exclusive of CAMC) including taxes, duties etc. for that Group. This is in
addition to LD.

However, the penalties during CAMC period for a particular year shall not exceed the
CAMC charges payable for that year or 5% per annum of item 1 of SoR of that Group,
whichever is higher.

In case the total penalty exceeds the maximum limit, CRIS reserves the right to treat the
unsatisfactory performance as breach of contract and take necessary action as per the
conditions of contract, including forfeiture of the R-PWAMCBG.

SLA for Breach in Provisioning of Technical Manpower during Implementation

and Warranty & CAMC Phase

Note – This SLA for Technical Manpower Breach is applicable over & above SLAs
mentioned in Clause 9 & 10 of the Bid Document part-II (as amended).

Definition Vendor is required to propose the CVs of the required technical manpower
(as mentioned in Annexure C & D of this corrigendum). It is vital that such
manpower is available to PURCHASER /End User Department onsite and
performs as per the scope of work specified in this RFP. The current SLA
breach shall specify penalty amount for non-availability of these manpower.
Service Level Availability of the required manpower should be 100%, as per Railway
Requirement working days.
Measurement of The following instances would be considered as SLA non-compliances:
Service Level • Non-availability of proposed manpower as proposed by the Bidder
Parameter in the technical proposal
• · Availability of manpower which do not meet the minimum required
qualification
Penalty for For every SLA non-compliance reported and proved, there shall be a
Nonachievement penalty as given below:
of
SLA Team Member Penalty
Requirement Project In • Penalty of Rs 1,500/- per day of non-availability
charge for 7 days
• Penalty of Rs. 3,000/- per day of non-
availability after 7 days
Subject Matter • Penalty of Rs 1,500/- per day of non-availability
Expert for 7 days
• Penalty of Rs. 3,000/- per day of non-
availability after 7 days
Field Executive • Penalty of Rs 500/- per day of non-availability
for 7 days
• Penalty of Rs. 1,000/- per day of non-
availability after 7 days
Note: - Any change of Technical Manpower deployed on the project during the project
implementation phase or in the warranty & CAMC phase is subject to approval by
CRIS.

Page 410 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.33. Annexure-33-SLA of Locomotives

1. Camera/Microphone Failure: Where data-feed/Health monitoring feed from any
one or more Cameras is not received in the Central Video Management System
(CVMS) for more than 30 minutes due to reasons attributable to the vendor,
such cases shall be considered as ‘Camera/microphone Failure’. If on a
monthly basis, the number of such ‘Camera/microphone Failure’ exceeds 2.0%
of the total number of Cameras commissioned in a particular Group, it shall
attract a penalty as defined in ‘Camera/microphone Failure’ item of the Clause
6.6 - titled “Penalties”. ‘Month’ for the purpose of calculating
‘Camera/microphone Failures’ means ‘Calendar Month’. For calculating
percentage of Camera/microphone Failures in a particular month, the total no.
of Cameras will be the no. of Cameras in that particular Group that have been
commissioned till the last date of previous month.
2. If the number of Camera/microphone Failures exceeds 2.0% in a month, it shall
attract penalty as defined in ‘Camera/microphone Failure’ item of the Clause
6.6 - titled “Penalties”. In case of multiple failures of a particular camera on a
particular calendar day, the penalty for such failures shall not be imposed more
than once. Also, such multiple failures of a particular camera on a particular
calendar day will be counted only once for calculating monthly failures during a
particular month.
3. In case of hardware or software failure, the repair/replacement must be done by
the end of next calendar day (i.e., 0:00 hours to 24:00 hours), subject to the
availability of Loco for a minimum 4 (Four) hours period. If the Bidder fails to
repair/replace the defective component(s) by the end of next calendar day (i.e.,
0:00 hours to 24:00 hours), it shall attract penalty as defined in ‘Penalty on
failure of Repair/Replacement Services on Time’ item of the Clause 6.6 - titled
“Penalties”.
4. The Bidder shall perform Root Cause Analysis of all failures - a detailed
technical analysis report on the root cause and steps taken for avoiding such
recurrence of such failure from bidder shall be submitted within 07 (seven)
working days from the date of availability of locomotive to bidder. Bidder is
bound to take necessary preventive / corrective measures etc. based on
CRIS/Railways advice.
5. In case of “Other than camera failures”, penalties shall be applicable as per
Clause No. 6.6.2 and Clause No.6.6.3.
6. In case of multiple instances of “Other than camera failures” of a particular
device on a particular calendar day, the penalty for such failures shall not be
imposed more than once. Also, such multiple instances of “Other than camera
failures” of a particular device on a particular calendar day will be counted only
once for calculating monthly failures during a particular month.

Page 411 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Penalties
1. Penalties shall be calculated on the basis of ‘Camera/microphone Failures’.
Penalties shall be deducted from the instalment of the amount due for payment
under this contract. In case penalties exceed the invoice amount, the bidder
shall have to deposit the due penalty amount within 7 days from the date of
issue of demand letter. In case the bidder does not deposit the penalty amount
within stipulated time, CRIS reserves the right to recover the due amount as
under:
a. From subsequent bills or any other bill pertaining to this contract,
b. From any other pending bills of the bidder in CRIS/Railways,
c. From PWAMCBG furnished for this contract or any other contract
awarded by CRIS/Railways.
d. Penalties specified under amended clause 6.6.2 and 6.6.3 on account of
breach in SLAs shall be applicable only after expiry of period of one (1)
month after original/refixed delivery period for milestone M2(a) for first 10
numbers of Locomotives under amended clause 6.12.6.
2. However, the failures detected & reported by Railways/CRIS shall be eligible for
imposition of penalties specified under clause 6.6.2 and 6.6.3 on account of
breach in SLAs even before integration with the CVMS.

Penalties shall be as per table given below:

SN. Failure Penalties

1 Camera Failure Rs.1000/- per Camera Failure for failure

rate exceeding 2% & up to 4% per
month.

Rs.2000/- per Camera Failure for failure

rate greater than 4% per month

2 Failure to replace/repair faulty Penalty as per Clause 6.6.3 will be

Camera to make its data-feed imposed in case vendor fails to
available (subject to the availability replace/repair faulty Camera to make its
of Loco for a minimum 4 (Four) data-feed available (subject to the
hours period) availability of Loco for a minimum 4
(Four) hours period)

3 Failure of Field trial If the system fails to come up to the

guaranteed performance in field trial, the
bidder, within a period of three (03) days
(within the overall period of milestone
under clause no. 6.12) shall take any
Page 412 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

SN. Failure Penalties

and all corrective measures and

resubmit the system for another ‘Field
Trial’. All modifications, changes,
corrective measures, labour etc. shall be
at the cost of the bidder. However, the
milestone S4 under clause 6.12.6 i.e.,
submission of detailed report by vendor
on performance of CVVRS etc., should
be completed within the time schedule
mentioned under this clause. If the
system fails to reach the guaranteed
performance even after the second Field
Trial, the Purchaser shall be free to take
any action as he deems fit against the
bidder.

4
Other than Camera Failure like: Rs.250/- per deficiency for failure rate
between exceeding 2% & up to 4%
• Microphone faulty / non-
operational/ damaged per month
• If Storage provisioning is not in
line with the user requirement
specified in the RDSO Rs.500/- per deficiency for failure rate
specification & Contract. greater than 4% per month
• SIMs not provided from two
different service providers.
• Handheld terminal provided are Penalty as per clause 6.6.3 will be
not maintained or faulty. imposed in case of vendor fails to
• Video feed resolution not in line replace/repair deficiency.
with the RDSO specification &
Contract
• Defects/Malfunctioning/Insulation
Puncturing etc. of wires/
cables/other components.
• Unforeseen events due to poor
assets maintenance attributable
to the contractor

5
In case of the failure of the Penalty as per clause 6.6.3 will be
installed components as part of imposed in case of vendor fails to
CVVRS with RDAS system is rectify the issue within the stipulated
due to reported buffer period of 7 days after

Page 413 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

SN. Failure Penalties

vandalism/theft/fire/accident etc., notification for the same by the

then contractor will be provided nominated authority of
7-day of buffer period to rectify Railways/CRIS.
the issue & make faulty/missing
component operational & ensure
compliance of 2.3.14 of Bid
Document Part – II. (Subject to the availability of
However, if the contractor is not locomotive for a minimum 4 (Four)
able to rectify the issue within hours period)
seven days of buffer period even
after making locomotive available
for minimum 4 hours in the said
period, penalty as stated shall be
applicable

18.33.1. Penalty on failure of Repair/Replacement Services on time

Penalties as per telescopic rate mentioned below will be imposed.

Type of Duration of Deduction/Penalties Deduction/Penalties
Failure as Repair/ during Warranty during CAMC Period*
defined in Replacement* Period*
Clause-6.5
Camera More than 1 day & @Rs.250/- per day or @Rs.50/- per day or part
Failure up to 7 days part thereof thereof

Camera More than 7 days @ Rs.500/- per day or @ Rs.100/- per day or part
Failure part thereof beyond 7 thereof beyond 7 days in
days in addition to addition to above
above deduction/ deduction/Penalty.
Penalty.
Other than More than 1 day & @Rs.50/- per day or @Rs.10/- per day or part
Camera up to 7 days part thereof thereof
Failure
Other than More than 7 days @ Rs.100/- per day or @ Rs.20/- per day or part
Camera part thereof beyond 7 thereof beyond 7 days in
Failure days in addition to addition to above
above deduction/ deduction/Penalty.
Penalty.

Page 414 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

*Only those Calendar Days shall be considered for deductions/penalties when

Locomotive has been made available to vendor for a minimum 4 (Four) hours period.

Note:

In case there is spill-over of the failure from Warranty Period to CAMC or from one
CAMC year to next CAMC year, the Deduction/Penalty as per the applicable rates for
that period.

The overall penalties annually during Warranty Period shall be capped to 10% of the full
contract value (exclusive of CAMC) including taxes, duties etc. for that Group. This is in
addition to LD.

However, the penalties during CAMC period for a particular year shall not exceed the
CAMC charges payable for that year or 5% per annum of item 1 of SoR of that Group,
whichever is higher.

In case the total penalty exceeds the maximum limit, CRIS reserves the right to treat the
unsatisfactory performance as breach of contract and take necessary action as per the
conditions of contract, including forfeiture of the PWAMCBG.

SLA for Breach in Provisioning of Technical Manpower during Implementation

and Warranty & CAMC Phase

Note – This SLA for Technical Manpower Breach is applicable over and above the
SLAs mentioned in the above table.

Definition Vendor is required to propose the CVs of the required technical manpower
(as mentioned in Annexure E & F of this the RFP and all its corrigendum). It
is vital that such manpower is available to PURCHASER /End User
Department onsite and performs as per the scope of work specified in this
RFP. The current SLA breach shall specify penalty amount for non-
availability of these manpower.
Service Level Availability of the required manpower should be 100%, as per Railway
Requirement working days.
Measurement of The following instances would be considered as SLA non-compliances:
Service Level • Non-availability of proposed manpower as proposed by the Bidder
Parameter in the technical proposal.
• Availability of manpower which do not meet the minimum required
qualification
Penalty for Non- For every SLA non-compliance reported and proved, there shall be a
achievement of penalty as given below:
SLA
Requirement Team Member Penalty
Project In charge • Penalty of Rs 1,500/- per day of non-
availability for 7 days
• Penalty of Rs. 3,000/- per day of
non-availability after 7 days

Page 415 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Subject Matter • Penalty of Rs 1,500/- per day of non-

Expert availability for 7 days
• Penalty of Rs. 3,000/- per day of
non-availability after 7 days

Field Executive • Penalty of Rs 500/- per day of non-

availability for 7 days
• Penalty of Rs. 1,000/- per day of
non-availability after 7 days

Note: - Any change of Technical Manpower deployed on the project during the project
implementation phase or in the warranty & CAMC phase is subject to approval by
CRIS.

Page 416 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.34. Annexure-34-SLA of the EMU/MEMU

1. Camera Failure: - Where data-feed/Health monitoring feed from any one or more
Cameras is not received in the CVMS for more than 30 minutes due to reasons
attributable to the vendor, such cases shall be considered as ‘Camera Failure’. If
on monthly basis, the number of such ‘Camera Failure’ exceeds 2.0% of the total
number of Cameras commissioned in a particular Group, it shall attract a penalty
as defined in ‘Camera Failure’ item of the clause 10.3 - titled “Penalties”. ‘Month’
for the purpose of calculating ‘Camera Failures’ means ‘Calendar Month’. For
calculating percentage of Camera Failures in a particular month, the total no. of
Cameras will be the no. of Cameras in that particular Group of which integration
commissioning has been done till the last date of previous month.
2. In case of multiple failures of a particular camera on a particular calendar day, the
penalty for such failures shall not be imposed more than once. also, such multiple
failures of a particular camera on a particular calendar day will be counted only
once for calculating monthly failures during a particular month.
3. In case of hardware or software failure, the repair/replacement must be done by
the end of next calendar day (i.e., 0:00 hours to 24:00 hours), subject to the
availability of EMU/MEMU for a minimum 4 (Four) hours period. If the vendor fails
to repair/replace the defective component(s) by the end of next calendar day (i.e.,
0:00 hours to 24:00 hours), it shall attract penalty as defined in ‘Penalty on failure
of Repair/Replacement Services on Time’ item of the clause 10.3 & 10.4 - titled
“Penalties”.
4. The Vendor shall perform Root Cause Analysis of all failures - a detailed technical
analysis report on the root cause and steps taken for avoiding such recurrence of
such failure from vendor shall be submitted within 07 working days from the date of
availability of coach to vendor. Vendor is bound to take necessary
preventive/corrective measures, etc. based on CRIS/Railways advice.
5. In case of “Other than camera failures”, penalties shall be applicable as per Clause
no. 10.3 and Clause no. 10.4. In case of multiple instances of “Other than camera
failures” of a particular device on a particular calendar day, the penalty for such
failures shall not be imposed more than once. Also, such multiple instances of
“Other than camera failures” of a particular device on a particular calendar day will
be counted only once for calculating monthly failures during a particular month.
6. In case of breach in providing technical manpower during implementation, warranty
and CAMC phases, penalties shall be imposed as mentioned in this section.

Page 417 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Penalties

1. Penalties shall be calculated on the basis of ‘Camera Failures’. Penalties shall

be deducted from the instalment of the amount due for payment under this
contract. In case penalties exceed the invoice amount, the vendor shall have to
deposit the due penalty amount within 7 days from the date of issue of demand
letter. In case the vendor does not deposit the penalty amount within stipulated
time, CRIS reserves the right to recover the due amount as under:
a. From subsequent bills or any other bill pertaining to this contract.
b. From any other pending bills of the vendor in CRIS/Railways.
c. From PWAMCBG furnished for this contract or any other contract
awarded by CRIS/Railways.
2. Penalties specified under clause 10.3 & 10.4 on account of breach in SLAs
shall be applicable only after expiry of period of one (1) month after
original/refixed delivery period for milestone M4(a) for first 10 no. of coaches
under clause 16.3(a) for CCTVSS and milestone M2(a) under clause 16.3(b) for
CCTVSS and CVVRS for first 10 no. of DMC coaches.
3. However, the failures detected & reported by Railways/CRIS shall be eligible for
imposition of penalties specified under clause 10.3 & 10.4 on account of breach
in SLAs even before integration with the CVMS.
4. Penalties shall be as per table given below:
a. For CCTVSS including those in DMC coaches in which CVVRS has also
been installed in the Driving Cabs:-

# Failure Penalties

1 Camera Failure Rs.1000/- per Camera Failure for failure

rate between exceeding 2% & up to 4% per
month
Rs.2000/- per Camera Failure for failure
rate greater than 4% per month

2 Failure to replace/repair faulty Camera to Penalty as per Clause 10.4 will be

make its data-feed available (subject to imposed in case vendor fails to
the availability of Coach for a minimum 4 replace/repair faulty Camera to make its
(Four) hours period) data-feed available (subject to the
availability of Coach for a minimum 4
(Four) hours period)

Page 418 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Failure Penalties

3 Other than Camera Failure like: - Rs.250/- per deficiency for failure rate
between exceeding 2% & up to 4% per
● Panic button faulty/non- month
operational/damaged

● Strobe light and hooter

faulty/non-operational/damaged Rs.500/- per deficiency for failure rate
greater than 4% per month

4 ● If Data Storage provisioning is not in

line with the user requirement
Penalty as per clause 10.4 will be imposed
specified in the RDSO specification &
in case of vendor fails to replace/repair
bid document.
deficiency.
● Working SIM cards/eSIM not provided
(Subject to the availability of Coach for a
from two different service providers.
minimum 4 (Four) hours period)
● Signage’s not provided or maintained.

● Handheld terminal provided are not

maintained or faulty.

● Video feed resolution not in line with

the RDSO specification &contract.

● Defect/malfunctioning/insulation
puncturing of wires/cables/other
components.

● Unforeseen events due to poor assets

maintenance attributable to the
vendor.

(Subject to the availability of Coach for

a minimum 4 (Four) hours period)
5 In case of the failure of the installed Penalty will be imposed as per clause 10.4
components as part of CCTVSS system is in case of vendor fails to rectify the issue
due to reported within the stipulated buffer period of 7 days
vandalism/theft/fire/accident, the vendor after notification for the same by the
will be provided 7-day of buffer period to nominated authority of Railway/CRIS.
rectify the issue & make faulty component
operational and ensure compliance of (Subject to the availability of Coach for a
clause 2.5.4 of Bid Document Part-II. minimum 4 (Four) hours period)
However, if the vendor is not able to rectify
the issue within seven days of buffer period
even after making coach available for
minimum 4 hours in the said period,
penalty as stated shall be applicable.

Page 419 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

b. CVVRS

# Failure Penalties
1 Camera Failure Rs.1000/- per Camera Failure for failure
rate exceeding 2% & up to 4% per
month.
Rs.2000/- per Camera Failure for
failure rate greater than 4% per month
2 Failure to replace/repair faulty Penalty as per Clause 10.4 will be
Camera to make its datafeed imposed in case vendor fails to
available (subject to the availability of replace/repair faulty Camera to make
Coach for a minimum 4 (Four) hours its data-feed available (subject to the
period) availability of Coach for a minimum 4
(Four) hours period)
3 Failure of Field trial If the system fails to come up to the
guaranteed performance in field trial,
the vendor, within a period of three (03)
days (within the overall period of
milestone under clause no. 16.5) shall
take any and all corrective measures
and resubmit the system for another
‘Field Trial’.
All modifications, changes, corrective
measures, labour etc. shall be at the
cost of the vendor. However, the
milestone S4 under clause 16.3(b) i.e.,
submission of detailed report by vendor
on performance of CVVRS etc., should
be completed within the time schedule
mentioned under this clause. If the
system fails to reach the guaranteed
performance even after the second
Field Trial, the Purchaser shall be free
to take any action as he deems fit
against the vendor.

Page 420 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Failure Penalties
4 Other than Camera Failure like: - Rs.250/- per deficiency for failure rate
between exceeding 2% & up to 4%
• Microphone faulty/non-
per month
operational/damaged
• If Storage provisioning is not in line
with the user requirement specified Rs.500/- per deficiency for failure rate
in the RDSO specification & greater than 4% per month
Contract.
• SIMs not provided from two
different service providers. Penalty as per clause 10.4 will be
• Handheld terminal provided are imposed in case of vendor fails to
not maintained or faulty. replace/repair deficiency.
• Video feed resolution not in line
with the RDSO specification &
Contract
• Defects/Malfunctioning/Insulation
Puncturing etc. of
wires/cables/other components.
• Unforeseen events due to poor
assets maintenance attributable to
the vendor
5 In case of the failure of the installed Penalty as per clause 10.4 will be
components as part of CVVRS imposed in case the vendor fails to
with/without RDAS system is due to rectify the issue within the stipulated
reported vandalism/theft/fire/accident buffer period of 7 days after notification
etc., then vendor will be provided 7 for the same by the nominated authority
days of buffer period to rectify the of
defect & make faulty/missing Railway/CRIS.
component operational & ensure
compliance of 2.5.4 of Bid Document
Part – II. (Subject to the availability of Coach for
a minimum 4 (Four) hours period)
However, if the vendor is not able to
rectify the issue within seven days of
buffer period even after making
Coach available for minimum 4 hours
in the said period, penalty as stated
shall be applicable.

c. Penalty on failure of Repair/Replacement Services on time

Penalties as per telescopic rate mentioned below will be imposed.

Type of Failure Duration of Deduction/Penalties during Deduction/Penalties

Page 421 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

as defined in Repair/ Warranty Period* during CAMC Period*

Clause-9 Replacement*

More than 1 day @Rs.250/- per day or @Rs.50/- per day or

Camera Failure
& up to 7 days part thereof part thereof

@ Rs.500/- per day or @ Rs.100/- per day

part thereof beyond 7 or part thereof
More than 7
Camera Failure days in addition to beyond 7 days in
days
above addition to above
deduction/Penalty. deduction/Penalty.

Other than
More than 1 day @Rs.50/- per day or part @Rs.10/- per day or
Camera
& up to 7 days thereof part thereof
Failure

@ Rs.100/- per day or @ Rs.20/- per day or

Other than part thereof beyond 7 part thereof beyond 7
More than 7
Camera days in addition to days in addition to
days
Failure above deduction/ above
Penalty. deduction/Penalty.
*Only those Calendar Days shall be considered for deductions/penalties
when Coach has been made available to vendor for a minimum 4 (Four)
hours period.

Note:
a. In case there is spill-over of the failure from Warranty Period to CAMC,
proportionate Deduction/Penalty will be levied as per the applicable rates
for the respective period.
b. The overall penalties annually during Warranty Period shall be capped to
10% of the full contract value including taxes, duties etc. This penalty is
distinct from and is in addition to any LD applicable in terms of the
contract.
c. However, the penalties during CAMC period for a particular year shall not
exceed the CAMC charges payable for that year or 5% per annum of
item 1 each group of SoR of that Group, whichever is higher.
d. In case the total penalty exceeds the maximum limit, CRIS reserves the
right to treat the unsatisfactory performance as breach of contract and
take necessary action as per the conditions of contract, including
forfeiture of the R-PWAMCBG.

Page 422 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

SLA for Breach in Provisioning of Technical Manpower during

Implementation and Warranty & CAMC Phase

Note – This SLA for Technical Manpower Breach is applicable over and above
the SLAs mentioned in this section.

Definition Vendor is required to propose the CVs of the required

technical manpower (as mentioned in Annexure-36 & 37). It
is vital that such manpower is available to PURCHASER
/End User Department onsite and performs as per the
scope of work specified in this tender. The current SLA
breach shall specify penalty amount for non-availability of
these manpower.

Service Level Availability of the required manpower should be 100%, as

Requirement per Railways working days.

Measurement of The following instances would be considered as SLA non-

Service Level compliances:
Parameter
• Non-availability of proposed manpower as proposed
by the Bidder in the technical proposal.
• Availability of manpower which do not meet the
minimum required qualification

Penalty for For every SLA non-compliance reported and proved, there
Nonachievement shall be a penalty as given below:
of SLA
Requirement Team Penalty
member

Project In • Penalty of Rs 1,500/- per day

charge of nonavailability for 7 days
• Penalty of Rs. 3,000/- per day
of nonavailability after 7 days

Subject • Penalty of Rs 1,500/- per day

Matter of nonavailability for 7 days
Expert • Penalty of Rs. 3,000/- per day
of nonavailability after 7 days

Field • Penalty of Rs 500/- per day of

Executive nonavailability for 7 days
• Penalty of Rs. 1,000/- per day
of nonavailability after 7 days

Note: - Any change of Technical Manpower deployed on the project during the
project implementation phase or in the warranty & CAMC phase is subject to
approval by CRIS.

Page 423 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.35. Annexure-35-Template for Monthly Attendance

Template for Capturing Monthly Attendance of the CVMS Bidders team

Date - __/__/__

To

The Managing Director

Center for Railway Information Systems

Chanakyapuri, New Delhi – 110021.

Subject: Attendance Report for the Month of ____________ for the Year______.

Sir,

We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”.

Enclosed please find the attendance for the personnel who have been deployed for
the Central Video Management System Project.

S.No Name of the Designation Location Total No. No of Remarks

Personnel Working days
Days in attended
the
month
1.
2.
3.
4.
5.
…
Table 58: Format for Monthly Attendance of Manpower
Thanking You.

Seal & Authorised Signature of the Bidder

Page 424 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.36. Annexure-36- Local Content as per Make in India Policy

Declaration/ Certificate for Local Content as per Make in India Policy

(To be submitted with Technical Bid)

{Shall be provided by Statutory Auditor or Cost Auditor of the Company (in the case of
Companies) or from a practicing Cost Accountant or practicing Chartered Accountant
(in respect of Suppliers other than Companies) on Letter Head}

To,
Managing Director,
CRIS, Chanakyapuri
New Delhi.

Sub.: Declaration/ Certificate for Local Content

Ref.: CRIS’ Tender No…………………………. Closing Date:
for………………………………………………………………………….
……………………………………………………………………………..

Dear Sir/ Ma’am.

We hereby certify the percentage of Local Content in the Products &

Services offered by …………………………………………… (Name of Bidder) having
registered Office at ……………………………………………………………. (Address of
Registered Office of Bidder) against the above-referred tender invited by CRIS as
under:

Percentage of Local Content …. % (Only …………. Percent)

Type of Supplier as per PPP-MII Policy Class-I Supplier /
Class-II Supplier /
Non-Local Supplier
(Strike-out which is not applicable)

Name, Designation & Signature of Signatory:

Stamp:
Date:
Place:
UDIN:

Page 425 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.37. Annexure-37- OEMs Technical Support in India

Undertaking by OEM for Providing Technical Support in India

<<To be provided on the letterhead of the OEM>>

Date:

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking for Providing Technical Support from office location in India

Dear Sir,

We, <<name of the OEM>>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the
Public Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We M/s <<name of the OEM>>, having registered office at

_______________________________________ (complete address along with city,
town, district, and PIN code).

We hereby confirm that our/Subsidiaries/Authorized Distributors/Partners technical

support office is located at _______________________________________ (complete
address along with city, town, district, and PIN code) and the Technical Support is
provided from this office as per the following business hours:

Days of working:
Start & End time:

Or

We shall be providing technical support through M/s.________________from their

technical support center located at _______________________________________
(complete address along with city, town, district, and PIN code) and the Technical
Support is provided from this office as per the following business hours:

Days of working:
Start & End time:

Page 426 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

We assure you that in the event M/s______________is not being able to fulfill its
obligations as technical support provider for our products, we would continue to
provide OEM Technical Support through alternate available arrangements.

The Technical Support will be available during entire duration of the contract.

I further certify that I am competent officer in my company to make this declaration.

Yours Sincerely,
(Authorized Signature)
Name of the OEM:
Place:
Date:
Company Seal:

Page 427 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.38. Annexure-38- MeitY empanelled Cloud

Undertaking by CSP/OEM for Deployment of the CVMS Solution on a MeitY
empaneled Cloud
<<To be provided on the letterhead of the OEM on an Annual basis>>
Date:

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking by CSP/OEM for Deployment of the CVMS Solution on a MeitY

empaneled Cloud

Dear Sir,

We, <<name of the CSP>>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the
Public Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We M/s <<name of the OEM>>, having registered office at

_______________________________________ (complete address along with city,
town, district, and PIN code).

We hereby confirm that the software solutions offered by us namely, the [Name of the
Products and their Model Numbers] for the project “Central Video Management
System (CVMS) on the Public Cloud for the IP-based CCTV Surveillance System for
the Indian Railways” are public cloud deployable and support deployment on MeitY
empaneled Cloud Service Providers platforms.

I further certify that I am competent officer in my company to make this declaration.

Yours Sincerely,
(Authorized Signature)
Name of the OEM:
Place:
Date:
Company Seal:

Page 428 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.39. Annexure-39-Undertaking for VMS scalable architecture.

Undertaking by OEM for VMS software to meet scalable architecture.
<<To be provided on the letterhead of the OEM>>
Date:

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking by OEM on the VMS software meeting scalability architecture

requirement

Dear Sir,

We, <<name of the OEM>>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the
Public Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We M/s <<name of the OEM>>, having registered office at

_______________________________________ (complete address along with city,
town, district, and PIN code).

We hereby confirm that the Video Management System software solution offered by
us namely, the [Name of the Products and their Model Numbers] for the project
“Central Video Management System (CVMS) on the Public Cloud for the IP-based
CCTV Surveillance System for the Indian Railways” is designed to meet the scalable
architecture and is capable of catering to a minimum of 7 Lakh+ cameras.

Yours Sincerely,
(Authorized Signature)
Name of the OEM:
Place:
Date:
Company Seal:

Page 429 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.40. Annexure-40- Integration of the VMS with more than One NVR
Undertaking by OEM for Integration of the VMS with more than One NVR
<<To be provided on the letterhead of the OEM>>
Date:

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking by OEM for the integration of the VMS software with more
than one NVR

Dear Sir,

We, <<name of the OEM>>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the
Public Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We M/s <<name of the OEM>>, having registered office at

_______________________________________ (complete address along with city,
town, district, and PIN code).

We hereby confirm that the Video Management System software solution offered by
us namely, the [Name of the Products and their Model Numbers] for the project
“Central Video Management System (CVMS) on the Public Cloud for the IP-based
CCTV Surveillance System for the Indian Railways” has been integrated and tested
with the following NVRs:

S.No Make of the NVR Model No of the NVR Remarks

1.
2.
3.
Table 59: List of NVR
Yours Sincerely,
(Authorized Signature)
Name of the OEM:
Place:
Date:
Company Seal:

Page 430 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.41. Annexure-41- Integration of ICCC with other applications.

Undertaking by OEM for the Integration of the ICCC application with other
applications
<<To be provided on the letterhead of the OEM>>
Date:

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking by OEM for the Integration of the ICCC application with other
applications.

We, <<name of the OEM>>, having read and examined in detail all the bidding
documents in respect of “Tender No. __________________________ for Selection of
Master System Integrator for Central Video Management System (CVMS) on the
Public Cloud for the IP-based CCTV Surveillance System for the Indian Railways”.

We M/s <<name of the OEM>>, having registered office at

_______________________________________ (complete address along with city,
town, district, and PIN code).

We hereby confirm that the Integrated Command and Control software solution offered
by us namely, the [Name of the Product and the Model/Version Number] for the
project “Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways” have been integrated with
the following applications in Central/State Govt. Department/Organization/
Autonomous body/PSU/Semi-Govt. Organization/Local Body/Authority or a Public
Listed Company in India (having average annual Turnover of Rs.500 Crore & above)”
during last five (05) financial years & current financial year ending last day of month
previous to the one in which the tender is invited:

S. Description of Application Yes / No

No
1. IP CCTV cameras
2. Public cloud for video streaming &
storage
3. M-NVR/NVR/VRU connected on
SIM/eSIM
4. Facial Recognition Solution
5. Video Analytics (Edge/Central)

Page 431 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

S. Description of Application Yes / No

No
6. GIS Maps
7. GPS or GPS enabled mobile
applications
8. Integration with different application
databases
9. Panic Buttons or Emergency Call Box
10. IOT Sensors / NVR / VRU
11. Public Address System or Variable
Messaging System
12. Mobile application for video and data
streaming
13. Body Worn Cameras
Table 60: List of Integration of ICCC with other applications
Yours Sincerely,
(Authorized Signature)
Name of the OEM:
Place:
Date:
Company Seal:

Page 432 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.42. Annexure-42- Certificate to be submitted by Tenderer

FORMAT FOR THE CERTIFICATE TO BE SUBMITTED/ UPLOADED BY BIDDER

ALONG WITH THE TENDER DOCUMENTS

I……………………………… (Name and designation) ** appointed as the

attorney/authorized signatory of the tenderer,

M/s_____________________________ (hereinafter called the tenderer) for the

purpose of the Tender documents for the work of
____________________________________________ as per the tender
No.____________ of ________(CRIS)**, do hereby solemnly affirm and state on the
behalf of the tenderer including its constituents as under:

1. I/we the tenderer (s) am/are signing this document after carefully reading the
contents.

2. I/We the tenderer(s) also accept all the conditions of the tender and have
signed all the pages in confirmation thereof.

3. I/we hereby declare that I/we have downloaded the tender documents from
Indian Railway website www.ireps.gov.in. I/we have verified the content of the
document from the website and there is no addition, no deletion or no alteration
to the content of the tender document. In case of any discrepancy noticed at
any stage i.e., evaluation of tenders, execution of work or final payment of the
contract, the master copy available with CRIS Administration shall be final and
binding upon me/us.

4. I/we declare and certify that I/we have not made any misleading or false
representation in the forms, statements, and attachments in proof of the
qualification requirements.

5. I/We also understand that my/our offer will be evaluated based on the
documents/credentials submitted along with the offer and same shall be
binding upon me/us.

6. I/We declare that the information and documents submitted along with the
tender by me/us are correct and I/we are fully responsible for the
correctness of the information and documents, submitted by us.

7. I/we certify that I/we the tenderer(s) is/are not blacklisted or debarred by
Railways or any other Ministry / Department of Govt. of India from participation
in tender on the date of submission of bids, either in individual capacity or as a
HUF/member of the partnership firm/LLP/JV/Consortium/Society/Trust.
Page 433 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

8. I/we understand that if the contents of the certificate submitted by us are

found to be forged/false at any time during process for evaluation of tenders, it
shall lead to forfeiture of the Bid Security and may also lead to any other action
provided in the contract including banning of business for a period of up
annexure-42to two years. Further, I/we (insert name of the
tenderer) **_____________and all my/our constituents understand that my/our
offer shall be summarily rejected.

9. I/we also understand that if the contents of the certificate submitted by us are
found to be false/forged at any time after the award of the contract, it will lead
to termination of the contract, along with forfeiture of EMD and Performance
cum Warrantee Bank Guarantee and may also lead to any other action
provided in the contract including banning of business for a period of upto two
years.

10. I/We have read the clause regarding restriction on procurement from a Bidder
of a country which shares a land border with India and certify that I am/We
are not from such a country or, if from such a country, have been registered
with the competent Authority. I/We hereby certify that I/we fulfil all the
requirements in this regard and am/are eligible to be considered (evidence of
valid registration by the competent authority is enclosed)

SEAL AND SIGNATURE

OF THE TENDERER

Place:

Dated:

**The contents in Italics are only for guidance purpose. Details as appropriate are to
be filled in suitably by tenderer.

Page 434 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.43. ANNEXURE-43- Certificate for I&C and Annual Audits

Part-1

Undertaking for Installation and Commissioning for Systems and Applications

supplied by the bidders.

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking for Installation, Configuration & Deployment for Systems and
Applications certified by the bidder

Sir,

We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”.

We hereby declare that the below mentioned Software application(s) has been
successfully installed/configured as per the Milestone M3 and the following are the
details:

# Name of Softwar Year Qty of Details of Remarks

the e of Licenses/Subscripti Integratio and
Software Version Releas ons allocated n Observatio
Applicati e completed ns (if any)
on with other
applicatio
ns
1
2
3

We hereby declare that the under mentioned cloud infrastructure resources have been
allocated for the installed applications.

Cloud Infrastructure resources allocated for each application

# Name of the Cloud Configuration Quantity Remarks
Application Resource details of the
Page 435 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Type Resource
allocated for
the
application
a.
b.
…

We hereby confirm that the above-mentioned Software applications have been

successfully installed, commissioned and integrated as per milestone M3 as
mentioned in Section Project Implementation Timelines. The installed applications
have been enabled with the required quantity of Licenses/Subscriptions as mentioned
above and shall be fully supported for the entire period of the contract.

Authorised Signatory
Seal and Signature of the Tenderer

Note: This Certificate has to be provided for each Software application OEMs whose
solution is being supplied for the CVMS solution.

Page 436 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Part – 2

Certificate for Installation and Commissioning for Systems and Applications

certified by OEM.

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Certificate for Installation and Commissioning for Systems and

Applications certified by OEM.

Sir,

We hereby declare that the below mentioned Software application(s) has been
successfully installed/configured by us as per the Milestone M3 as mentioned in
Section Project Implementation Timelines and the following are the details:

Details of
Name of Integratio
Year Remarks
the Softwar Qty of n
of and
# Software e Licenses/Subscripti completed
Releas Observatio
Applicati Version ons allocated with other
e ns (if any)
on applicatio
ns
1
2
3

We hereby certify that the under mentioned required cloud infrastructure resources
have been allocated for the installed applications.

Cloud Infrastructure resources allocated for each application

# Name of the Cloud Configuration Quantity Remarks
Application Resource details of the
Type Resource
allocated for
the
application
a.
b.
…
We hereby certify that the above-mentioned Software applications have been
installed, configured, commissioned and integrated into the overall CVMS

Page 437 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

solution as per the Milestone M3 as mentioned in Section Project

Implementation Timelines and solution design approved by us. The installed
applications have been allocated with the OEM recommended Cloud
Infrastructure resources to function and meet the load requirements of the
applications and also enabled with the required quantity of
Licenses/Subscriptions as mentioned above and shall be fully supported for the
entire period of the contract.

Authorised Signatory
Seal and Signature of the OEM

Note: This Certificate has to be provided for each Software application OEMs whose
solution is being supplied for the CVMS solution.

Page 438 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Part – 3

Certificate for the Annual Audit of the CVMS Solution conducted by OEM.

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Certificate for the Annual Audit of the CVMS Solution conducted by OEM.

Sir,

We hereby declare that the below mentioned Software application(s) has been
successfully audited by us:

Details of
the
Name of
Softwa Year Applicatio Remarks
the Qty of
re of ns to and
# Software Licenses/Subscripti
Versio Releas which our Observatio
Applicati ons allocated
n e Software ns (if any)
on
has been
integrated.
1
2
3
…

We hereby certify that the under mentioned required cloud infrastructure resources
have been allocated for the installed applications.

Cloud Infrastructure resources allocated for each application

Configuration
details of the
Cloud
Name of the Resource
# Resource Quantity Remarks
Application allocated for
Type
the
application
1
2
3
…

Page 439 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

We hereby certify that the above-mentioned Software applications have been audited
by us. The installed applications have been allocated with the OEM recommended
Cloud Infrastructure resources and have also been configured as per our approved
design and recommended best practices to meet the functionalities of the use cases of
CRIS.

Authorised Signatory
Seal and Signature of the OEM

Note: This Certificate has to be provided for all the Software application OEMs
annually whose solution is being used for delivering the CVMS solution to CRIS on an
Annual Basis.

Page 440 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.44. Annexure-44- Setting up of the Test Environment

Undertaking format for the completion of setting up of the Test Environment

To

Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking for the completion of setting up of the Test Environment for
the CVMS applications.

Sir,

We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”.

We hereby declare that the Cloud Infrastructure of the test environment for the below
mentioned Software application(s) has been successfully installed/configured and the
following are the details:

Cloud Infrastructure resources allocated for each application

Configuration
details of the
Cloud
Name of the Resource
# Resource Quantity Remarks
Application allocated for
Type
the
application
a.
b.
…
Table 61: Testing Environment Setup
Authorised Signatory
Seal and Signature of the Tenderer

Page 441 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.45. Annexure-45-Undertaking to be provided by the Bidder & CSP

(To be Provided by the MSI and CSP on their Company Letterheads)
To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking for seeking written permission from CRIS for making any changes
to the CVMS Solution Stack
.
Sir,

We, <<name of the undersigned Bidder>>, having read and examined in detail all the
bidding documents in respect of “Tender No. __________________________ for
Selection of Master System Integrator for Central Video Management System (CVMS)
on the Public Cloud for the IP-based CCTV Surveillance System for the Indian
Railways”.

We <Name of the Organisation> hereby declare that:

1. We shall not make any changes, additions, or deletions to any part of the
CVMS without the prior written consent of CRIS.
2. In the event that requires changes to the CVMS configuration or data, we shall
submit a detailed request to CRIS, outlining the proposed changes and their
justification.
3. On CRIS’s approval of the request, we shall implement the changes in
accordance with the approved plan only.
4. We shall retain a complete backup of the configuration or data for ensuring
restoration without any data loss or service getting affected.
5. We shall ensure that the backup is stored securely and is accessible to CRIS
upon request.
6. We shall be responsible for any costs associated with the restoration of the
CVMS.
7. In the event of data loss or service disruption resulting from unauthorized
changes we shall be we shall be responsible for repaying to CRIS the
necessary damages, including but not limited to:
a. The cost of restoring the data or service to its pre-incident state.
b. The cost of any third-party services required to mitigate the impact of the
data loss or service disruption.
c. The cost of any lost revenue or business opportunities resulting from the
data loss or service disruption.

Authorised Signatory
Seal and Signature of the Tenderer
Page 442 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.46. Annexure-46-Security Verification Certification

Undertaking by OEM for the Security Verification Certification
<<To be provided on the letterhead of the OEM>>
Date:

To
Managing Director,
CRIS, Chanakyapuri,
New Delhi – 110021.

Sub: Undertaking by OEM for the Security Verification Certification

Dear Sir,

We have carefully gone through the Terms & Conditions contained in the tender No.
______________”. We M/s ___________________ (Name of the OEM) having
registered office at _______________________________________ (complete
address along with city, town, district, and PIN code).

We hereby confirm that the [Name of the Software Solution] complies to the security
features to meet the security assurance requirements as per Relevant clauses / paras
applicable for security, vulnerabilities, etc. as specified by RDSO.

Yours Sincerely,
(Authorized Signature)
Name of the OEM:
Place:

Dated:

Date:
Company Seal:

Page 443 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.47. Annexure-47- PoA for signing of proposal

(On Non–judicial stamp paper of requisite value)
(The stamp paper to be in the name of the company who is issuing the power of
attorney)
Power of Attorney

We, Mr. or M/s.______ (name of the firm or company with address of the registered
office) hereby constitute, appoint and authorize Mr. or Ms.______ (Name and
residential address) who is presently employed with us and holding the position of
______, as our Attorney to do in our name and our behalf all or any of the acts, deeds
or things necessary or incidental to our bid document for the Project _____ (name of
the Project), including signing and submission of the bid document response,
participating in the meetings, responding to queries, submission of information or
documents and generally to represent us in all the dealings with Client or any other
Government Agency or any person, in connection with the works until culmination of
the process of bidding till the Project Agreement is entered into with ____________
(Client) and thereafter till the expiry of the Project Agreement.
We hereby agree to ratify all acts, deeds and things lawfully done by our said Attorney
pursuant to this power of attorney and that all acts, deeds, and things done by our
aforesaid Attorney shall and shall always be deemed to have been done by us.
(Add in the case of a JV/ Consortium)
Our firm is a member or Lead Bidder of the JV/ Consortium of ___________,
_________ and
___________.
Dated this the _____ day of ______ 2024.

IN WITNESS WHEREOF WE THE PRINCIPALS ABOVE NAMED HAVE EXECUTED

THIS POWER OF ATTORNEY ON THIS …………………. DAY OF…………………….

For …………………
(Signature)
……………………..
(Name & Title)

For ……………………..
(Signature)
……………………..
(Name & Title)

For ……………………..
(Signature)
……………………..
(Name & Title)
Page 444 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

Witnesses:
1.
2.
(Notarized)

Note:
The mode of execution of the Power of Attorney shall be in accordance with the
procedure, if any, laid down by the applicable law and the charter documents of the
executant (s).Each of the JV/ Consortium Members shall submit for verification the
extract of the charter documents and documents such as a board or shareholders’
resolution/power of attorney in favour of the person executing this Power of Attorney
for the delegation of power hereunder on behalf of the JV/ Consortium Members.

Signature and Name of authorized signatory)

___________
(Signature and Name in block letters of all the remaining partners of the firm Signatory
for the Company)

Seal of firm Company

Witness 1: Witness 2:

Notes:
1. To be executed by all the members individually.
2. The Mode of execution of the power of attorney shall be in accordance with the
procedure, if any laid down by the applicable law and the charter documents of the
executant(s) and when it is so required the same shall be under common seal
affixed in accordance with the required procedure.

Page 445 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.48. Annexure-48- Completion & Performance Certificates

18.48.1. Phase 1 Go-Live Completion Certificate
To Whomsoever it may Concern

<< Please Note that this is an indicative template and CRIS may decide to change the contents of the
template at a later date>>

This is to certify that the Central Video Management System (CVMS) project, as
outlined in the Tender document Part-II "Selection of Master System Integrator for the
Central Video Management System (CVMS) on the Public Cloud for the IP-based
CCTV Surveillance for the Indian Railways" has been successfully implemented by the
Master Service Integrator.

Project Details:

Project Name: Central Video Management System Implementation

Project Phase: Phase 1 Go-Live

Client: Center for Railway Information Systems

Duration: [Start Date] to [End Date]

Scope: Implementation of CVMS on the Public Cloud for IP-based CCTV Surveillance

Achievements:

a. The project was completed within the specified timeline. Yes No

b. MeitY empanelled public cloud environment setup is completed to host
complete CVMS solution which include below application configurations::
i. Cloud infrastructure Yes No

ii. Video Management System (VMS) Yes No

iii. Integrated Command and Control Center Yes No

application (ICCC)
iv. Enterprise Management System (EMS) Yes No

v. Facial Recognition Solution (FR) Yes No

vi. Video Summarization Yes No

vii. Forensic Application (Image & Video) Yes No

b. On-boarding of 10,000 Cameras (If the quantity of 10,000 Cameras is

not achieved due to delay from CRIS, CRIS may decide to declare the
Phase 1 Go-Live with deployment of less than 10,000 Cameras with

Page 446 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

corresponding reduction in the minimum assured quantity of the

cameras). Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

c. Completion of the primary integration as defined in the Section:

Integrations of Systems. Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

d. Completion of the Security audit by a CERT-in empanelled agency and

addressing all the vulnerabilities detected during the security audit.
Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

e. Completion of the User Acceptance Tests. Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

f. Designing and implementation of SOPs. Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………
Page 447 of 455
Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

g. Implementation and integration of the mobile app with the CVMS solution
stack. Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

h. Completion of other integrations like Email Server and SMS server.

Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

i. Configuration of the Service levels in the EMS for both the CVMS
solution stack and the Edge devices. Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

i. s for the identified Systems and applications for the CRIS

identified stake holders. Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

Authorised Signatories:

[Designation]:

Date: [Date of Issuance]

Page 448 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.48.2. Final Go-Live Completion Certificate

To Whomsoever it may Concern

<< Please Note that the this is an indicative template and CRIS may decide to change the contents of
the template at a later date>>

This is to certify that the Central Video Management System (CVMS) project, as
outlined in the Tender document Part-II "Selection of Master System Integrator for the
Central Video Management System (CVMS) on the Public Cloud for the IP-based
CCTV Surveillance for the Indian Railways" has been successfully implemented by the
Master Service Integrator.

Project Details

Project Name: Central Video Management System Implementation

Project Phase: Phase 1 Go-Live

Client: Center for Railway Information Systems

Duration: [Start Date] to [End Date]

Scope: Implementation of CVMS on the Public Cloud for IP-based CCTV

Surveillance
Achievements:
a. Completion of the integration of the Edge devices planned under the CVMS
project as mentioned in the Annexure-2-Edge Layer or Field Equipment
Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

b. Completion and operationalisation of the primary and secondary integrations

defined in the Section: Integrations of Systems. Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

Page 449 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

…………………………………………………………………………………

…………………………………………………………………………………

c. Completion of the Security audit and addressing all vulnerabilities detected

through security audit of the complete CVMS solution stack as per RDSO
specification (RDSO/SPN/TC/106/2022 Version 2.1 or latest amendment).
Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

Authorised Signatories:

[Designation]:

Date: [Date of Issuance]

Page 450 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.48.3. O&M Phase Performance Certificate

Monthly Performance Certificate

To Whomsoever it may Concern

<< Please Note that the this is an indicative template and CRIS may decide to change the contents of
the template at a later date>>

This is to certify that [Bidder's Name] has demonstrated Satisfactory performance in the
Operations of the Central Video Management System (CVMS) on the Public Cloud for
Center for Railway Information Systems.

The bidder has successfully hosted, operated and managed applications :

a. Video Management System (VMS), Yes No

b. Integrated Command and Control Center (ICCC), Yes No
c. Facial Recognition, Yes No
d. Video Summarization, Yes No
e. Forensic application (Image & Video enhancement) Yes No
f. Enterprise Management System integrated with Helpdesk application.
Yes No

Compliance to Performance Metrics:

a. The CVMS system has consistently maintained high uptime and reliability.
Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

b. The Integrated CVMS platform consisting of the VMS, ICCC, Facial

Recognition, and other applications have been operational satisfactorily.
Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

Page 451 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

c. Timely resolution of incidents and proactive management of system issues.

Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

d. Adherence to security protocols and industry standards ensuring data integrity

and confidentiality. Yes No

Comments……………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

…………………………………………………………………………………

Authorised Signatories:

[Designation]:

Date: [Date of Issuance]

Page 452 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

18.49. Annexure-49-Abbreviations
# Name Description
1 CIF Common Intermediate Format
2 AD Active Directory
3 AMC Annual Maintenance Contract
4 AOA Articles of Association
5 API Application Programming Interface
6 APN Access Point Name
7 APT Advanced Persistent Threat
8 BLC Backlight Compensation
9 BOM Bill of Materials
10 BOQ Bill of Quantity
11 CAPEX Capital Expenditure
12 CCTVSS Closed Circuit Television Surveillance System
13 CORS Cross-Origin Resource Sharing
14 COTS Commercial Off the shelf
15 CPU Central Processing Unit
16 CRIS Centre for Railway Information Systems
17 CSP Cloud Service Provider
18 CVMS Central Video Management System
19 CVVRS Crew Voice & Video Recording System
20 DDoS Distributed Denial of Service
21 DNS Domain Name System
22 DP Delivery Period
23 EMD Earnest Money Deposit
24 EMS Enterprise Management System
25 FAT Factory Acceptance Test
26 FIFO First In First Out
27 FR Facial Recognition
28 FRS Functional Requirement Specifications
29 FW Firewall
30 FY Financial Year
31 GCC General Condition of Contract
32 GOI Government of India
33 GPS Global Positioning System
34 GPU Graphics Processing Unit
35 GSM Global System for Mobile Communication
36 GUI Graphical User Interface
37 HTTPS Hypertext Transfer Protocol Secure
38 HSM Hardware Security Modules
39 IaaS Infrastructure as a Service
40 ICCC Integrated Command and Control Center

Page 453 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Name Description
41 IDAM Identity and Access Management
42 IOC Indicators of Compromise
43 IP Internet Protocol
44 IPR Intellectual Property Rights
45 IPS Intrusion Prevention System
46 IR Indian Railways
47 IREPS Indian Railways e-Procurement System
48 ISO International Organization for Standardization
49 IT Information Technology
50 JV Joint Venture
51 KMS Key Management Services
52 LD Liquidated Damages
53 LDAP Lightweight Directory Access Protocol
54 LOA Letter of Acceptance
55 MAC Media Access Control
56 MFA Multi-Factor Authentication
57 MeitY Ministry of Electronics and Information Technology
58 M-NVR Mobile Network Video Recorder
59 MOA Memorandum of Association
60 MoU Memorandum of Understanding
61 MPLS Multiprotocol Label Switching
62 MSEs Micro and Small Enterprises
63 MSI Master System Integrator
64 MSP Mobile Service Provider
65 NGFW Next-Generation Firewall
66 NDA Non-Disclosure Agreement
67 NPV Net Present Value
68 NAVIC Navigation with Indian Constellation
69 NTP Network Time Protocol
70 NVR Network Video Recorder
71 OEM Original Equipment Manufacturer
72 ONVIF Open Network Video Interface Forum
73 OS Operating System
74 PAM Privileged Access Management
75 PaaS Platform as a Service
76 PIM Privileged Identity management
77 PKI Public Key Infrastructure
78 PO Purchase Order
79 PoC Proof Of Concept
80 POI Person of Interest
81 PSU Public Sector Undertaking

Page 454 of 455

Central Video Management System (CVMS) on the Public Cloud for the IP-
based CCTV Surveillance System for the Indian Railways

# Name Description
82 PTZ Pan, Tilt, and Zoom
83 QoS Quality of Service
84 QC Qualification Criteria
85 RAM Random Access Memory
86 RBAC Role-based Access Control
87 RCA Root Cause Analysis
88 RDAS Railway Driver Assistance System
89 RDSO Research Design and Standards Organisation
90 Bid Document Request for proposal
91 RITES Rail India Technical and Economic Service
92 RTC Real-Time Computer
93 RTSP Real-Time Streaming Protocol
94 SAT Site Acceptance Testing
95 SaaS Software as a Service
96 SDD System Design Document
97 SDK Software Development Kit
98 SHD Service Health Dashboard
99 SIEM Security Information and Event Management
100 SIM/eSIM Subscriber Identity Module/embedded Subscriber Identity Module
101 SLA Service Levels Agreement
102 SOR Schedule of Requirement
103 SOAR Security Orchestration, Automation and Response
104 SNMP Simple Network Management Protocol
105 SRS Software Requirement Specification
106 SSL Secure Sockets Layer
107 SSO Single Sign On
108 STQC Standardisation Testing and Quality Certification
109 TC Test Certificate
110 TLS Transport Layer Security
111 UID Unique Identifier
112 VAPT Vulnerability Assessment and Penetration Testing
113 VLAN Virtual Local Area Network
114 VM Virtual Machine
115 VMS Video Management System
116 VPC Virtual Private Cloud
117 VPN Virtual Private Network
118 VRU Video Recorder Unit
119 WAF Web Application Firewall
120 WDR Wide Dynamic Range
121 Wi-Fi Wireless Fidelity
122 WORM Write Once Read More
Table 62: Abbreviations
Page 455 of 455