Request for Proposal For Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt - 2

31.3 Document checklist for technical Bid

31.4 Format to share Bidder’s Particulars

31.5 Format to share Bidder details

31.6 PQ: Format for Declaration by the bidder for not being Blacklisted / Debarred

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

31.7 PQ and TQ: Financial Capability Statement

31.8 PQ and TQ: Similar work experience

31.9 PQ : Self-Declaration – Not insolvent

31.10 PQ: Self-Declaration – Not convicted in any criminal offense

31.11 PQ-6: MAF

31.12 Affidavit

31.13 PQ: Self Certification by Bidder and OEM

31.14 TQ: Curriculum Vitae of Project Team

31.15 Commercial Bid Cover Letter

31.16 Bank Guarantee format for EMD

31.17 Format for Performance Bank Guarantee

32. Abbreviations & Definitions

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

The information contained in this Request For Proposal (“RFP”) whether subsequently provided to the service

providers, (“service provider/System Integrators”) verbally or in documentary form by Smart City Ahmedabad

Development Limited (henceforth referred to as “SCADL” in this document) or any of its employees or advisors,

is provided to service provider on the terms and conditions set out in this RFP document and any other terms

and conditions subject to which such information is provided. This RFP document is not an agreement and is

not an offer or invitation to any party. The purpose of this RFP is to provide the service providers or any other

person with information to assist the formulation of their operational plan. This RFP includes statements, which

reflect various assumptions and assessments arrived at by SCADL in relation to this scope. This RFP document

does not purport to contain all the information each service provider may require. This RFP document may not

be appropriate for all persons, and it is not possible for the Chief Executive Officer, SCADL and their employees

or advisors to consider the objectives, technical expertise and particular needs of each service provider. The

assumptions, assessments, statements and information contained in the RFP documents, may not be complete,

accurate, adequate or correct. Each service provider must therefore conduct its own analysis of the information

contained in this RFP and to seek its own professional advice from appropriate sources. Information provided

in this RFP document to the service provider is on a wide range of matters, some of which may depend upon

interpretation of law. The information given is not intended to be an exhaustive account of statutory

requirements and should not be regarded as a complete or authoritative statement of law. SCADL accepts no

responsibility for the accuracy or otherwise for any interpretation of opinion on law expressed herein. SCADL

and their employees and advisors make no representation or warranty and shall incur no liability to any person,

including the service provider under law, statute, rules or regulations or tort, the principles of restitution or

unjust enrichment or otherwise for any loss, cost, expense or damage which may arise from or be incurred or

suffered on account of anything contained in this RFP or otherwise, including the accuracy, reliability or

completeness of the RFP, and any assessment, assumption, statement or information contained therein or

deemed to form part of this RFP or arising in any way in this Selection Process. SCADL also accepts no liability

of any nature whether resulting from negligence or otherwise howsoever caused arising from reliance of any

Bidder upon the statements contained in this RFP. SCADL may in its absolute discretion, but without being

under any obligation to do so, can amend or supplement the information in this RFP. The issue of this RFP

document does not imply that SCADL is bound to select a service provider or to appoint the Selected operator

(as defined hereinafter), for implementation and SCADL reserves the right to reject all or any of the service

provider or proposals without assigning any reason whatsoever. The service provider shall bear all its costs

associated with or relating to the preparation and submission of its RFP proposal including but not limited to

preparation, copying, postage, delivery fees, expenses associated with any demonstrations or presentations

which may be required by SCADL or any other costs incurred in connection with or relating to its Bid. All such

costs and expenses will remain with the service provider and SCADL shall not be liable in any manner

whatsoever for the same or for any other costs or other expenses incurred by a service provider in preparation

for submission of the RFP proposal, regardless of the conduct or outcome of the selection process.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

3. Notice Inviting Proposal and Necessary Instruction

Proposals in prescribed format are invited by SCADL from eligible parties for this RFP.

SITC of Dashcam along with AI based solution for surveillance of

1. Scope of Work

Municipal Infrastructure.

Rs. 18,000 /- (Rs. Eighteen Thousand Only)

Tender submission In the form of Demand Draft in Favor of “Smart City Ahmedabad

2. Cost Development Limited” drawn on any scheduled / nationalized bank

and payable at Ahmedabad.

Rs.80,00,000/- (Rs. Eighty lakh rupees Only) Demand Draft in Favor

of "Smart City Ahmedabad Development Limited" drawn on any

scheduled bank and payable at Ahmedabad

EMD in the form of bank guarantee with validity of 180 days from the

EMD (bid Security /

3. Security deposit)

last date of bid submission in Favor of "Smart City Ahmedabad

Development Limited" from

• All Nationalized banks including the public sector banks - IDBI Ltd.

• Private sector banks - AXIS Bank, ICICI Bank and HDFC Bank

PBG/SD will 5% of contract value.

Chief Executive Officer (CEO),

Smart City Ahmedabad Development Limited, Command and Control

4. Office issuing RFP

Centre, Opp. Divan Ballubhai School, Nr. Sanskar kendra, Paldi,

Ahmedabad-380007

5. Contract Period 3 years of Operation & Maintenance period + Implementation Period

6. Bid validity days 180 days from the last date of submission of bids

The tender can be downloaded from below websites.

https://ahmedabadcity.gov.in

7. Issue of Tender

https://smartcityahmedabad.com

https://nprocure.com

Bidders shall have to post queries by email to

8. Queries by email [email protected], [email protected] on or before

12/05/2026 up to time 1600 Hrs

Pre-bid will be held on 12/05/2026 at 15:00 PM at

Smart City Ahmedabad Development Limited, Command and Control

Centre, Opp. Divan Ballubhai School, Nr. Sanskar kendra, Paldi,

Ahmedabad-380007

Proposal due date (last

Tender should be submitted before 08/06/2026 up to 1600 Hrs.

10. date & time of Tender Bidder shall upload their bids on https://www.nprocure.com/

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Complete duly signed RFP & proposal in sealed envelope with relevant

details may be submitted to reach at following address before

Smart City Ahmedabad Development Limited, Command and Control

Centre, Opp. Divan Ballubhai School, Nr. Sanskar Kendra, Paldi,

Ahmedabad-380007

Technical Qualification documents will be opened on

Date & Time of opening 08/06/2026 at 18:00 Hrs in the presence of bidders’ representatives.

12. of Tender Qualified bidders would be subsequently informed

later about the date, time and venue for price bid opening.

Chief Executive Officer (CEO),

Contact persons Smart City Ahmedabad Development Limited, Command and Control

13. (For any Clarifications) Centre, Opp. Divan Ballubhai School, Nr. Sanskar Kendra, Paldi,

Ahmedabad-380007

Relaxation to Micro & Small Enterprises:

1. The firms registered under MSE are exempted from submitting the Earnest Money Deposit (EMD).

2. If a bidder falls under MSE, then a copy of the registration certificate must be provided to SCADL along

with the proposal. Further, the bidder must keep SCADL informed of any change in the status of MSE.

MSE certificate must clearly mention the products / services asked in this tender, then only MSE

exemption shall be accepted. SCADL will have final rights to accept or reject the registration certificate

based on mentioned products / services.

4. Introduction and background

Ahmedabad is one among forefront in implementation of smart initiatives for urban development projects.

Under Smart City Mission, Ahmedabad has implemented several projects namely, Integrated Transport

Management System (ITMS), City Surveillance project, e-Challan, Smart Anganwadi, Smart Public Toilet,

Digital Payment and establishment of Integrated City Command and Control Centre with several e-Governance

As per the GoI guidelines, Ahmedabad Municipal Corporation (AMC) has formed a Special Purpose Vehicle

(SPV) as Smart City Ahmedabad Development Limited (SCADL) for the implementation of projects under the

smart city mission. SCADL executes the task of project design, tender preparation, bid process management,

selection, and on-boarding of implementation agency. SCADL work closely with user departments from AMC

and other government departments in implementation and operationalization of various smart city projects.

Ahmedabad was selected among the first 20 Smart Cities in India under the Smart Cities Mission of the Ministry

of Housing and Urban Affairs considering the proposals submitted by the Ahmedabad Municipal corporation.

A Special Purpose Vehicle (SPV) was formed in 2016 under the mission guidelines and was named as Smart City

Ahmedabad Development Limited (SCADL). It carries the end-to-end responsibility for vendor selection,

implementation, and operationalization of various Smart City Projects.

The objective was to promote sustainable and inclusive cities that provide core infrastructure and give a decent

quality of life to its citizens, a clean and sustainable environment and application of Solutions. Most of the ICT

initiatives proposed and being implemented by Ahmedabad city have been identified with a predominant

objective to improve public safety and surveillance, traffic management, public services quality, emergency

response and real time tracking of municipal services.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

4.1 Objective of RFP

SCADL/ AMC envisions to identify and monitor its municipal infrastructure for quick

action through deployment of dashcams. The Scope of work for this RFP is categorized into

(i) Identification of Use Cases (ii) SITC of Dashcams/Camera (iii) AI Based software

Application and dashboard iv) Manpower (v) NMS (vi) VMS

AMC/SCADL envisions leveraging the extensive route coverage of AMTS/AMC vehicle fleet

by deploying state-of-the-art AI-powered dashcams to create a mobile municipal

surveillance platform that:

a. AUTOMATES detection of civic and infrastructure issues across 5000+ km of city

streets daily without requiring static camera infrastructure at every location.

b. GENERATES automated complaint tickets in AMC's Citizen Complaint Redressal

System (CCRS) for civic use cases, enabling immediate departmental action.

c. GENERATES e-Challans for traffic violations, with provision to add additional

violations in future including all the traffic related use cases mentioned in the tender.

d. STORES video footage of an event for 90 days on cloud for review, investigation,

evidence, and advanced analytics.

e. ENABLES real-time monitoring and remote triggering of live footage from ICCC

(Integrated Command and Control Centre) when required.

f. BUILDS a comprehensive city analytics platform for safety, surveillance, and data-

driven urban governance.

The specific objectives of this project are:

a. Deploy latest technology Full HD AI-enabled dashcams on 1000 AMTS/AMC vehicles

with all required fixtures, safety covers, and direct power connection from bus

b. Implement AI-based automated detection for 20 predefined use cases (10 Priority 1 +

10 Priority 2) covering civic administration, road infrastructure, traffic violations,

sanitation, and public safety.

c. Enable real-time edge analytics for minimum 10 use cases (Priority 1) directly on the

dashcam/edge device.

d. Establish automated workflow integration with: AMC CCRS system for civic complaint

ticket generation, E-Challan system for traffic violation processing, ICCC for

centralized monitoring and live feed access

e. Deploy cloud-based storage and analytics platform with 30-day continuous video

footage retention, 90-day event video clip retention, Full project duration retention for

all logs and metadata

f. Design optimized connectivity architecture using: Built-in SIM for live event

transmission and remote live streaming from ICCC, Depot-based Wi-Fi for bulk data

offloading, Minimum data pack to optimize costs while ensuring full functionality

g. Implement complete system within 6 months of contract signing.

h. Operate and maintain the entire solution for 3 years post go-live.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

4.2 Envisaged outcome of the project

Manual inspections Automated AI-based detection

Reactive complaint-based Proactive issue identification

Partial city coverage 5000+ km comprehensive coverage

Verbal/photo reports GPS-tagged video evidence

Manual challan issuance Automated e-Challan generation

Periodic surveys Daily continuous monitoring

Subjective assessments Data-driven analytics

Siloed departmental info Integrated command centre view

Delayed response Near real-time incident creation

4.3 Project Area

The project covers the entire road network of Ahmedabad city traversed by AMTS/AMC

buses, spanning:

• Total road network coverage: 5000+ km

• All AMC zones and wards

• Arterial roads, collector roads, and internal streets

• Major junctions and intersections

• Commercial and market areas

• Residential neighbourhoods

• Industrial zones

• Suburban and peripheral areas

• BRTS corridors (where applicable)

Unlike static camera-based surveillance requiring infrastructure at fixed points, this project

leverages the natural movement of public transport buses across the city to achieve

comprehensive and repetitive coverage:

• Each bus covers its designated route multiple times daily

• Fleet collectively covers 5000+ km of streets

• Multiple passes over same streets enable detection of

• new, recurring, and resolved issues

• Coverage naturally extends as routes evolve

5. Scope of Work

The selected System Integrator (SI) shall be responsible for the complete end-to-end design,

supply, installation, testing, commissioning, integration, operation, and maintenance of the

AI-based dashcam solution for municipal infrastructure surveillance across 5000+ km of

streets of Ahmedabad city.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

ALL responsibilities related to project execution shall be of the vendor / SI. The Authority

shall facilitate coordination with AMTS/AMC departments, provide access to buses and

depots, and provide integration endpoints for CCRS and E-Challan systems.

The scope is divided into the following major components:

A. Hardware Supply & Installation

B. AI Software & Analytics

C. System Integration & Workflow Automation

D. Cloud Infrastructure & Storage

E. Network & Connectivity

F. Dashboard, VMS & NMS

G. Implementation & Go-Live

H. Operation & Maintenance (3 Years)

I. Training & Knowledge Transfer

J. Exit Management & Handover

The use cases mentioned below are to be run in Dashcam by the successful bidder. This

section deals with all use cases along with their bucket-wise bifurcation of the use cases and

detailed functional requirements. The use cases are categorized into two sections as below:

1. Priority 1 (P1) use cases

2. Priority 2 (P2) use cases

Bidder to accordingly design the solution. Priority 1 use cases shall be available readily with

the Bidder and to be shown as part of POC. Below is the detailed list for uses cases basis

priority. SCADL will provide all relevant available data required for system development and

integration. The system must meet the defined accuracy standards for each of these use case,

including detection accuracy, false positive limits, and performance during both day and

night conditions. The 1-meter sizing parameter may be treated as indicative for system

design; however, the detection logic must consistently meet the prescribed performance

5.1.1 Use Cases under Priority List

Sr.no Function Name of Use Case List Name

1 Civic Administration Detection of garbage on road List

2 Civic Administration Detection of Water Logging List

Detection of two-wheelers riding without

4 Traffic Detection of vehicles driving on wrong side. List

Detection of Potholes, damaged Manhole

5 Civic Administration

Cover and Open Manhole List

Detection of Faded Road Markings (Zebra

6 Civic Administration

crossing, Road median, Signages) List

7 Civic Administration Detection of C&D Waste List

8 Civic Administration Detection of Cattle on road List

Detection of Damaged Paver, Pavement,

9 Civic Administration Curbs, Curbs, Curb stones and Dividers on

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Sr.no Function Name of Use Case List Name

Detection of Broken Street Lights and

10 Civic Administration

Traffic Lights List

5.1.2 Use Cases Under Priority List

Sr.no Function Reframed Name List Name

11 Civic Administration Detection of Electrical Wires Jumble List

Detection of Damaged/Rusted/Tilted

12 Civic Administration

Detection of Damaged and Hidden Traffic

13 Civic Administration

14 Civic Administration Detection of broken road edges List

Detection of Illegal Stalls (Stall detection

15 Civic Administration

16 Civic Administration Detection of construction in progress List

17 Civic Administration Detection of Person Sleeping on Footpath List

Detection of Spitting and Red & Yellow

18 Civic Administration

Spots on the street List

Detection of Road Crack and Surface

19 Civic Administration

20 Civic Administration Detection of Parking encroachments List

Note: For details of each of the use case and related detection, refer to the explanation

given in the RFP. Please note that some of the use cases are either combined or removed

from the priority list. However, price discovery has been kept in case SCADL wants to

increase the scope considering the requirement in the future.

5.2 SITC of Dashcams/Camera

The successful bidder will be responsible for installing dashcam across AMTS, BRTS (Bus

Rapid Transit System), public transportation, and any corporation vehicles. The dashcam

viewpoints shall be positioned to capture all use cases from a single vehicle, with one

camera focused on the centre of the road. Additionally, the cameras should be adaptable for

use in other vehicles to increase coverage of the city area.

The dashcam shall have edge computing capabilities or be equipped with a separate Local

Processing Unit (LPU) at the edge, along with a software solution to automatically capture

events and issues occurring on the road while the vehicle is moving through the city.

1. The successful bidder will be responsible for supply, installation, testing,

commissioning, and maintenance of 1000 nos. of dashcam of latest technology meeting

all technical specifications defined under this and that are to be deployed for the entire

contract duration period.

2. When these dashcam installed in the public transportation vehicles go about their usual

designated routes, the feed captured from dashcam to be further analysed to identify

events/use cases.

3. The dashcam was installed to have anti-tampering and anti-theft design. The dashcam

should be installed with protective covers to avoid against physical damage, to protect

against anti-theft and unauthorized access.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

4. Preferred configuration (Built-in Features): The Authority prefers dashcams with

maximum built-in features as shown below.

a. Built-in edge AI processing capability for minimum 10 use cases (Priority 1)

b. Built-in SD card slot with minimum 512 GB MicroSD card

c. Built-in 1 nos. of data SIM card slots

d. Built-in battery backup of minimum 2 hours

e. Built-in GPS with G-Sensor

f. Built-in Wi-Fi, Bluetooth connectivity

g. Built-in WDR, HDR, IR Night Vision

h. Built-in ANPR capability

Note: Bidders proposing dashcams with all features built-in will have a natural

advantage in competitive pricing under QCBS evaluation since no additional

external accessories or infrastructure will be required, reducing overall project

5. Alternative Configuration: If some of the preferred built-in features are not configured,

The Dashcam can have a separate LPU as an external accessory to compute AI

capabilities at edge such that the AI Application would be deployed on the edge device

a. External SD card enclosure (if built-in slot unavailable)

b. External SIM card router/module (if built-in slots unavailable)

c. External power bank / battery backup unit (if built-in battery unavailable)

Note: all external accessories shall be:

• Supplied, installed, and maintained by the bidder at their own cost

• Included in the bid price

• Securely mounted within the bus with anti-tamper mechanisms

• Covered under the same warranty and SLA as the dashcam

• Compatible with the proposed dashcam without any performance degradation

6. Hybrid analytics mode: In case the proposed dashcam is not capable of performing

edge-based AI analytics for the required use cases, the bidder MAY propose a Hybrid

Analytics Mode comprising:

i. Deployment of a Local Processing Unit (LPU) – military-grade or industrial-

grade rugged computing device – installed inside the bus for edge analytics,

ii. Data centre/cloud-based analytics for use cases that cannot be processed at the

All costs of LPU procurement, installation, power connection, integration, and

maintenance SHALL BE borne entirely by the bidder and included in the bid price.

Note: Bidders choosing hybrid mode must ensure that:

• Edge analytics (on LPU or camera) covers minimum 10 P1 use cases in real-time

• Cloud/data centre analytics covers remaining use cases

• All SLA requirements on accuracy and latency are met regardless of analytics mode

• Total solution cost remains competitive under QCBS

7. Dashcam Installation: Installation of dashcams on 1000 designated AMTS/AMC buses

as per approved mounting design and orientation for optimal use case coverage.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

a. Installation shall be carried out in coordination with AMTS depot management

without disrupting bus operations.

b. Installation shall be done in 4 batches of 250 buses each, completing all

installations within updated timeline.

c. Each installed dashcam must pass an acceptance test including i. Video quality

verification, ii. GPS accuracy check, iii. SIM connectivity test, iv. Wi-Fi

connectivity test at depot, v. Edge AI detection demo (at least 2 use cases), vi.

Battery backup test, vii. Power connection stability test, viii.SD card read/write

test, ix. Safety cover integrity check

d. Bidder shall secure mounting with vibration-resistant assembly,

e. Installation of protective safety cover over the camera to prevent vandalism,

tampering, dust, and accidental damage,

f. Direct power connection from the AMTS bus battery (vehicle electrical system)

with proper voltage regulation, fuse protection, and surge protection,

g. Installation of 512 GB MicroSD card in each dashcam,

h. Installation and activation of SIM cards

i. Configuration and calibration of AI models on device,

j. GPS and connectivity testing,

k. Installation of any external accessories (if proposed) including SD card

enclosure, SIM router, power bank, LPU.

8. Sim Cards compatibility: The dashcam shall be equipped with SIM card compatibility,

allowing for the insertion of SIM cards. The bidder will supply the SIM cards at the time

of deployment. It is the bidder's responsibility to select and purchase a data plan for the

SIM card from the telecom service provider, in order to ensure that events are captured

on the centralized server without any interruption.

a. SIM card registration with usage plan and a memory card that is to be used in

Dashcam/Cameras & manpower for SIM card registration etc. must be

provided by the bidder. Bidder will have to pay for the SIM card registration

cost & plan cost. The SIM card to be registered (in name of SCADL) under the

number of dashcam/Camera provider itself, and the selected bidder will be

required to pay monthly/quarterly/yearly plan cost to the service provider

without any additional cost to SCADL.

9. Power Connection for Dashcam: The SI shall liaise with the light and transport dept. of

AMC for integration of power connections for the dashcam and LPU across

transportation vehicles. If the power output of the transportation vehicle exceeds the

power requirement of the dashcam/Cameras and LPU, then the bidder shall be

responsible for arranging appropriate power adjustment or regulation mechanisms to

ensure compatibility.

a. The vendor shall furnish all required power cables and accessories (3- pin

power socket, car charger etc.) essential for powering the dashcam and LPU.

These accessories shall be compliant with relevant safety and quality standards.

10. Necessary Coordination for Installation: SI shall coordinate with concerned authorities

/ municipalities / Bus drivers for installation of Dashcam and LPU.

a. The successful bidder is expected to coordinate with authorities for necessary

permissions, approvals, and follow-ups for the installation of

dashcam/Cameras and LPU devices in the respective public transport vehicles.

However, AMC will provide adequate assistance/support as and when required.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

b. The Public transport vehicles/ AMC /Police department owned vehicles where

dashcam & LPU are to be installed will be decided by SCADL/AMC authorities

before installation.

11. The successful bidder to ensure that no damage occurs to the property of Ahmedabad

municipal corporation/ public transport vehicles/Police department vehicles during or

post installation of the dashcam & LPU. If any damage occurs the concerned charges

will be recovered from the bidder. In case dashcam/Camera is faulty, it is the

responsibility of the bidder to take important data backup of that device.

12. Dismantling & Reinstallation of Dashcam/Cameras and LPU: In case of dismantling

and reinstallation of dashcam/Cameras and LPU from one vehicle to other vehicle is

required due to whatsoever reason, it is the responsibility of successful bidder to

execute the task of dismantling and Reinstallation on request of authority. Bidder

needs to provide the quotation for re-installation of the hardware to new buses to be

re-commissioned in one go. This will not be included in bid amount and should be

defined by bidder at the time of bid.

13. Data Collection: These dashcam transfer the necessary real time video feed on demand

basis to centralize server (at bus depot through Wi-Fi)

5.3 AI Based Application, Analytics & Storage Solution

5.3.1 Approach for Use case Implementation

1. The successful bidder should develop an AI Based application solution that is to be

hosted on cloud server. Cloud service provider shall be MeitY empaneled and hosted

based in India.

2. MeitY guideline for Cyber security measures shall be meet while hosting the proposed

solutions on cloud.

3. The successful bidder shall procure necessary software licenses and maintain the AI

Application for project duration.

4. All licenses supplied by the bidder for the purpose of this project shall be perpetual in

nature and shall be in the name of AMC / SCADL and this will be entirely during

operation and maintenance for the entire duration of the contract.

5. The storage solution for footage captured through dashcam shall include local SD card

for full video and all generated event on cloud.

6. The cloud-based VMS must offer functionality to view both real-time video feeds and

recorded footage from the local SD card.

7. For recorded video, the VMS should allow users to specify a date and time range for

8. The cameras will send alert video of events including pre and post alert video of 5 sec

each i.e. total 10 seconds video for respective use case, and same will be stored in the

centralized servers on cloud for post processing as per the project scope.

9. Retention period for event videos on cloud shall be maximum of 90 days. These videos

shall be stored for first in - first out (FiFo) basis.

10. Retention period for continuous video shall be maximum of 30 days. These videos

shall be stored for first in first out (FiFo) basis.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

11. The cloud storage solution should be scalable to accommodate future retention or

capacity needs, ensuring flexibility and compliance with operational requirements.

The proposed AI application shall seamlessly capture all events detected through

dashcam and LPU while maintaining optimal performance, even when the full

quantity of dashcam specified in the RFP is deployed and integrated.

12. The system must ensure that performance does not degrade under maximum load

conditions. Additionally, it shall support the automatic upload of, snapshots, and

event-based clips to the cloud, with secure data transmission through encrypted

channels using HTTPS, SSL, and TLS protocols.

13. Platform & Operations: The AI application shall be an open-architecture, highly

scalable platform integrating dashcams/cameras, LPUs, VMS, and other video

analytics systems deployed at the edge as per the MSI solution. It will support live

viewing, concurrent playback, and multi-view switching with search options by date,

time, alert sequence, and bookmarks. Comprehensive logging-including system, audit,

alert, and event logs— shall be maintained with export capability. Secure

authentication, password policies, and configurable auto-logout functionalities shall

be implemented to prevent unauthorized access. Role-based access control will govern

user privileges across both web and mobile platforms. Historical transactions for

alarms and incidents shall be retained for at least 90 days.

14. Alarm Management: The application shall manage alarms generated automatically

by AI detections at edge and device health monitoring and allow manual alarm

creation by operators. Alarms will appear in a unified notifications pane, and pop-up

alerts. Each alarm shall include pre- and post-event video clips (10 seconds each), with

options for live view and recorded playback. Operators can classify alerts as

True/False, adjust criticality levels, and initiate incident creation. Alarm de-

duplication shall be there to prevent flooding for recurring events. Notifications will

be sent via in-app, SMS, and email to concerned officials.

15. Escalation & Correlation: The system shall support configurable escalation based

on severity and priority, with auto-escalation timers for critical incidents. Event

correlation will combine multiple alerts from different sensors based on time, location,

and attributes to improve situational awareness.

16. The 20 use cases defined in Section 7 shall be implemented in two phases:

Phase 1 – Priority 1 (p1): 10 Use Cases

• To be implemented, tested, and achieving ≥80% accuracy before Go-Live

(within 6-month implementation period)

• Based on realistic implementation feasibility

• Must include edge analytics capability on dashcam/LPU

• Forms the basis for initial CCRS ticket and e-Challan integration

Phase 2 – Priority 2 (p2): 10 Use Cases

• To be developed AFTER Go-Live during the O&M period

• Shall be deployed as soon as each use case is ready and achieves required

• Development timeline: Within first 6 months of O&M period

• Uses data collected from Phase 1 deployment for training

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

5.3.2 Event Flooding, Throttling & Prioritization Controls

The system shall include mandatory safeguards to prevent event flooding due to

excessive detections, repetitive triggers, or abnormal AI behaviour.

The solution shall support:

(a) Event Throttling:

Automated rate-limiting to restrict the number of events generated per device per

minute based on configurable thresholds.

(b) Priority-Based Event Handling:

Critical events (e.g., traffic violations, safety hazards) shall always be given highest

priority over low-severity civic events; non-critical events may be queued or delayed.

(c) Duplicate & Near-Duplicate Suppression:

Automatic merging or suppression of multiple similar events detected within a short

timeframe at the same location.

(d) Bandwidth Safeguards:

Intelligent control to avoid network congestion—priority upload for high-severity clips,

deferred upload for non-critical civic events, and batching of low-priority events.

(e) Storage Protection:

Local device storage shall maintain minimum reserved space to ensure no critical event

clips are lost due to storage saturation.

(f) Cloud Load Protection:

System shall prevent overload by applying batching, queueing, and intelligent

scheduling of event uploads when cloud throughput is high.

(g) Alert Generation:

System shall generate alerts to NMS when event flooding is detected, throttling is

triggered, or when storage/bandwidth thresholds are reached.

5.3.3 Edge based analytics

The solution shall support two analytics execution modes, depending on the nature

of the use case:

(a) Strict Edge-Only Analytics Mode

• Applicable for traffic enforcement and challan-generating use cases

• Entire detection, validation, evidence generation, and confidence assignment shall

occur at the edge (dashcam/LPU)

• No dependency on cloud classification shall be permitted prior to ticket or challan

(b) Edge Pre-Filtering with Cloud Classification Mode

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

• Applicable for select civic and infrastructure monitoring use cases

• Initial detection, motion filtering, and candidate event generation shall occur at the

• Final classification, confidence scoring, and severity determination may be performed

The bidder shall clearly indicate the execution mode for each use case as per the

classification defined in this RFP.

Upon detection of any incident:

i. Generated an event log with unique incident ID

ii. Captured a video clip of maximum 10 seconds (5 sec pre-event + 5 sec post-

iii. Recorded GPS coordinates (latitude, longitude) of detection

iv. Recorded timestamp (date, time to seconds)

v. Classified the incident by use case type

vi. Assigned confidence score

vii. Stored event log and video clip on SD card

viii. Transmitted event log to cloud/CCRS/E-Challan via SIM (if real-time

transmission was enabled)

Edge analytics continued functioning even when network connectivity was unavailable

(offline mode). All events were queued and synced when connectivity restored.

5.3.4 Cloud analytics & Storge requirements

1. Priority 2 use cases and any supplementary analytics were processed on cloud

infrastructure.

2. Cloud analytics processed the video footage uploaded from dashcams after buses

returned to depots.

3. Processing was completed within 24 hours of data receipt to enable timely reporting

4. Cloud analytics platform handled batch processing of footage from 1000+ dashcams

Data Storage Estimation

Sr. No. Parameter Value

1 Number of dashcams

2 Recording hours per day 10-12 hours

3 Video resolution Full HD 1920×1080 @ 25 fps

4 Video compression H.265

5 Estimated bitrate 6-8 Mbps

6 Data per camera per day ~27-36 GB

7 Total daily data (1000 cameras) ~27-36 TB

8 SD card capacity 512 GB

9 SD card rolling retention ~14-19 days

10 Monthly data to cloud ~810 TB - 1.08 PB

11 30-day cloud video storage ~810 TB - 1.08 PB

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Event clips per camera per day

12 50-200 events

13 Event clip size (10 sec @ 8 Mbps) ~10 MB per clip

14 Daily event clip volume (1000 cameras) ~500 GB - 2 TB

15 90-day event clip storage ~45-180 TB

5.3.5 Cloud hosting

1. ALL software solutions (AI analytics engine, centralized dashboard, VMS, NMS,

databases, and any other application) shall be hosted on MeitY-approved/empanelled

cloud infrastructure.

2. Cloud infrastructure must be located within India and comply with data sovereignty

3. Minimum server specification:

• 8 vCPUs, 32 GB RAM (scalable as needed)

• SSL/TLS certificates for all applications and APIs

• High availability with automated failover

4. Cloud architecture shall be designed by the bidder to minimise cost while ensuring NO

functional requirement is compromised. The bidder must optimize:

• Compute resources (right-sizing, auto-scaling)

• Storage tiers (hot, warm, cold/archive)

• Data transfer and bandwidth

• License utilization

Cost optimization approach must be detailed in the technical proposal.

5.3.6 Data storage & retention policy

The following data retention policy shall be strictly adhered to:

Sr. No. DATA TYPE RETENTION ON CLOUD

1 Continuous video footage (all cameras) 30 days

Event/incident video clips (10 sec

Event/incident logs (metadata, GPS, Entire project duration

time, classification, score) (Implementation + 3 years O&M)

Vehicle logs (route, GPS trail, Entire project duration

operational data) (Implementation + 3 years O&M)

System logs (NMS, application logs, Entire project duration

audit trails) (Implementation + 3 years O&M)

Entire project duration

6 CCRS tickets & E-Challan records

(Implementation + 3 years O&M)

Entire project duration

7 Dashboard analytics and reports

(Implementation + 3 years O&M)

1. Storage tires shall be implemented:

• HOT STORAGE: Recent data (0-7 days) for active queries

• WARM STORAGE: Medium-term data (8-30 days)

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

• COLD/ARCHIVE STORAGE: Event clips (31-90 days) and historical logs

(beyond 30 days)

2. Automated lifecycle policies shall manage data migration between storage tiers and

deletion after retention period

3. The bidder must present a detailed storage sizing and cost optimization strategy in

their technical proposal.

5.3.7 AI model requirements

1. Minimum detection accuracy: ≥ 80% for each use case

2. False positive rate: ≤ 20%

3. Detection Rate: The percentage of correctly detected valid events shall be ≥ 85%.

4. True Positive Rate (TPR) + True Negative Rate (TNR): Combined correct

classification performance (positive + negative cases) shall be ≥ 90%.

5. False Positive Rate (FPR): Incorrect detections flagged as events shall not exceed 5%.

6. False Negative Rate (FNR): Missed valid events shall not exceed 5%.

7. AI models were trained on local (Ahmedabad-specific) datasets to account for local

8. Continuous model improvement through retraining using project-generated data

9. Model versioning and performance audit trail maintained

10. The bidder was responsible for all costs of AI model development, training, testing,

5.3.8 CCRS ticket generation (civic use cases)

a) For every civic use case detection (garbage, pothole, broken streetlight, etc.), the system

automatically generated a complaint ticket in AMC's CCRS system.

b) Ticket included:

i. Incident type/category

ii. GPS location with mapped address

iii. Date and time of detection

iv. Evidence: 10-second video clip + snapshot image

v. Bus number and route information

vi. AI confidence score

vii. Priority/severity classification

c) CCRS integration was through APIs provided/coordinated by AMC/SCADL.

d) Duplicate detection logic was implemented to prevent multiple tickets for the same issue

detected by different buses on the same route.

5.3.9 E-challan generation (Traffic Violations)

a) For traffic violations, the system generated e-Challans automatically through integration

with the designated traffic enforcement system.

b) INITIAL TRAFFIC USE CASES:

i. Triple riding on two-wheelers

ii. Riding without helmet

iii. Wrong-side driving

iv. No parking violations

c) FUTURE TRAFFIC USE CASES: Additional traffic violations could be added in future as

per Authority's requirements.

d) E-Challan included:

i. Violation type

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

ii. Vehicle registration number (via ANPR)

iii. GPS location of violation

iv. Date and time

v. Evidence: Video clip + snapshot with visible number plate

vi. Bus/camera ID for audit trail

Integration with RTO/Traffic Police e-Challan system was developed by the SI with

coordination from AMC/SCADL.

5.4 System Integration & Workflow Automation

5.4.1 Mandatory integrations

The SI shall develop and maintain integrations with:

1. AMC CCRS SYSTEM

• Automated civic complaint ticket generation

• Status tracking and closure workflow

• Two-way API for status updates

• Duplicate detection and merging logic

2. E-CHALLAN SYSTEM

• Automated traffic violation challan generation

• ANPR-based vehicle identification

• Evidence attachment (video + image)

• Integration with RTO for vehicle owner details

3. ICCC (INTEGRATED COMMAND AND CONTROL CENTRE)

• Event feed on ICCC screens

• Ability to trigger live video streaming from any

• dashcam via SIM connectivity

• Vehicle tracking on GIS map

• Incident escalation workflows

4. ANY OTHER SYSTEMS as directed by the Authority during the contract period.

b. The bidder must coordinate and provide all necessary support for integration with

NIC, Vahan-RTO, and CCRS systems. SCADL will facilitate coordination with the

respective third-party system owners as needed.

c. If any delays are caused by third parties, the bidder submit evidence of such delays,

which will be considered for penalty exemption.

5.4.2 API development

1. ALL API development, testing, deployment, and maintenance shall be the SOLE

RESPONSIBILITY of the SI.

2. APIs must be RESTful, well-documented (Swagger/Open API), secured (HTTPS,

OAuth 2.0), and version controlled.

3. AMC/SCADL/NIC shall provide necessary access, credentials, and technical

documentation for endpoint systems.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

4. The SI shall maintain APIs and adapt to any changes in endpoint system versions

during the contract period.

5.5 Network & Connectivity

5.5.1 5.5.1 Dashcam SIM connectivity

1. Each dashcam shall be equipped with 1 nos. SIM cards

2. SIM data packs shall be provisioned with minimum data allocation optimized to

a. Event log transmission: Event metadata (incident type, GPS, timestamp,

confidence score) transmitted to CCRS and E-Challan systems during bus

b. On-demand live video streaming: When triggered from ICCC, live video

feed from any specific dashcam can be streamed in real-time via SIM

c. Device management: Remote device monitoring, configuration, and OTA

firmware updates via NMS.

3. The bidder shall design the 5G data plan to MINIMISE COST while ensuring all above

functionalities. The bidder must

a. Estimate monthly data consumption per dashcam considering operational

b. Propose optimal data plan with justification

c. Implement data usage monitoring and alerts

4. All SIM procurement, activation, and data plan costs for the entire contract period

shall be included in the bid price.

5.5.2 Depot wi-fi infrastructure

1. The bidder shall design, supply, install, and commission Wi-Fi infrastructure at all

designated AMTS/AMC bus depots for automated video data offloading.

2. DESIGN REQUIREMENTS

a. Wi-Fi infrastructure shall be designed AS PER PROJECT REQUIREMENT to

support complete data offloading from all buses parked at each depot during

overnight hours

b. Coverage must extend to all bus parking areas within the depot where

dashcam-equipped buses are parked Network capacity must support

simultaneous data sync from all buses present at the depot.

3. TECHNICAL SPECIFICATIONS:

c. Enterprise-grade Wi-Fi 6 (802.11ax) or better

d. Sufficient Access Points for complete coverage

e. Managed Wi-Fi with centralized controller

f. Wired backbone (Gigabit Ethernet or better)

g. Network security (WPA3, VLAN segregation)

4. BROADBAND / LEASED LINE:

h. High-speed broadband or leased line connectivity at each depot for cloud data

i. Bandwidth to be designed as per data offloading requirements (see calculations

in technical proposal)

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

j. Redundant connectivity recommended

5. AUTOMATED DATA OFFLOADING

k. When a bus enters the depot Wi-Fi zone, the dashcam shall AUTOMATICALLY

detect the network and initiate data transfer to cloud

l. Transfer priority: Event clips first, then continuous footage

m. Incremental/differential sync to avoid re-uploading already transferred data

n. Transfer status monitoring on NMS dashboard

o. Retry and resume for interrupted transfers

6. All depot Wi-Fi infrastructure costs including equipment, installation,

broadband/leased line, and maintenance shall be included in the bid price.

The successful bidder is expected to create a dashboard with the below mentioned features

and functionalities.

1. The dashboard shall be accessible through a web-based interface on

Desktop/Laptop/Mobile (Android & iOS).

2. The dashboard shall include secure login credentials for authorized users minimum

500 no’s and expandable to 1000 no’s, which will be provided to various concerned

AMC departments. The bidder must ensure that the dashboard supports role-based

access control (RBAC, minimum 5 roles: - Super Admin, Administrator /

Department Head, Operator / Control Room Staff, Field Supervisor, Viewer /

Auditor), allowing permissions to be assigned based on user roles and

responsibilities. Access should be provided to a minimum number of officials as

defined by SCADL, with support for up to 100 concurrent sessions. Each role shall

have clearly defined privileges for viewing, editing, and managing data.

3. The events identified through dashcam/Camera & LPU shall be recorded in the

dashboard after processing and upload during depot-wise video offloading. Live

streaming shall not be used for regular operations.

4. The dashboard should be able to show all the violations/detections (as per use case

list) on Google Map, with a time-filter option ranging from 1 hour to 1 year, with

daily, weekly, monthly, quarterly, and yearly views.

5. The reports shall display date and time of event, location including latitude &

longitude, navigation link, event description, 10-second video clip of the event, image

of the detected event, captured source (Dashcam/Camera), Department, Status, and

Seen Time. Each 10-second clip shall include visual tags/bounding boxes for

6. The dashboard/Camera shall generate alerts whenever depot video upload from any

dashcam/Camera fails, is incomplete/corrupted, or is repeatedly unsuccessful. Alerts

shall also be generated in case of suspected theft attempts, device tampering, and

SD-card/storage corruption. In case of no network connectivity during field

operations, the dashcam/Camera shall store event video clips on the SD card and

upload them to the central server at the depot during scheduled offloading.

7. On-demand review: For exceptional needs, a “Live Stream Trigger” feature shall be

available as part of the telecom service plan at no additional cost, limited to

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

instances per camera per month with carry-forward of unused instances. This does

not change the default depot-offload operation.

8. Each department/ward/zone will have designated login credentials. Upon login, the

dashboard interface displays only events related to the relevant

department/ward/zone. A filter option shall allow users to select wards/zones as

9. The dashboard shall include a feature allowing the admin to transfer an event from

one department/ward to another.

10. The system shall provide a user-friendly interface for seamless event browsing within

the designated department/ward/zone.

11. The SI shall provide dashboard login access to minimum 500 users, expandable to

1000 users, with minimum 100 concurrent sessions. Each user shall have a unique

login credential.

12. The bidder shall implement role-based access control (RBAC) to manage user

13. System administrator access shall be provided to SCADL/AMC, enabling visibility of

events across all departments.

14. Department heads and employees shall be provided with controlled, role-based

access aligned with the access rights defined by the Authority.

15. An edit option shall be available in the Reports module, allowing department heads

and employees to update permitted fields. Each event record shall include a Status

column (Attended/Resolved) and a Seen Time field.

16. When a user updates the Status column, the system shall automatically record Seen

17. The dashboard shall generate daily, weekly, monthly, and yearly reports with export

options including PDF, Excel, and CSV.

18. Events shall remain stored and viewable on the dashboard for a minimum of

19. The bidder shall ensure that images and video clips displayed on the dashboard and

reports maintain clarity and are not distorted.

20. Reports shall allow filters based on wards, zones, event type, department, source

(Dashcam/Camera), and Status. Duplicate events shall be deduplicated and not

shown multiple times.

21. The dashboard shall display Google Maps integrated view for visualization of use

cases based on zone, department, and source. Daily coverage maps and heatmaps

shall be supported and refresh once offloaded data is processed.

22. The dashboard shall generate weekly analytical insights, including ward-wise and

zone-wise hotspots and frequently occurring event patterns.

23. Daily coverage maps shall show the routes covered by dashcams.

24. Daily heatmaps shall visualize zone and ward-level status using color coding based

on number of events.

25. The dashboard shall update reports, Google Maps, coverage maps, and heatmaps in

real time post-processing of depot-offloaded data to enable timely decision-making.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

26. A sample report shall contain the following columns:

Date Location 10-se

Event Auto-Mappe Seen

& (with Ward– c Imag Sourc Departme Statu

# Descripti d Tim

Tim Navigatio Zone Video e e nt s

on Department e

The columns C1–C8 show information captured/fetched from Dashcams. Column C9 shall

be auto-filled based on department-event mapping. Column C10 shall be entered by the

department head/employees, and Column C11 shall be generated by the system.

27. Department-wise event mapping details will be provided by SCADL prior to

implementation.

28. The dashboard shall capture all events observed through dashcams while ensuring

optimal performance even at full system load.

29. The system shall ensure that duplicate events are not displayed on the dashboard.

30. The ownership of all hardware/software developed, customized, configured, or

procured as part of the project shall remain with AMC/SCADL. All software licenses

shall be perpetual and in the name of AMC/SCADL.

31. All licenses supplied by the bidder shall be perpetual in nature and shall remain valid

during the entire contract period.

32. The system shall provide published APIs for integration with external systems

including command-and-control systems and incident management systems using

open standards (REST/HTTP/HTTPS).

33. The bidder shall publish APIs for integration with third-party systems including but

not limited to police applications, RTO databases (Vahan, Sarathi), and government

applications as required.

34. SCADL requires integration of all municipal events detected on the dashboard with

the CCRS application. Once field officers close a case on CCRS, the dashboard shall

update the event’s status automatically.

35. The selected bidder shall coordinate with all relevant authorities, agencies, and

system owners for any third-party integration required for the project.

36. The selected SI shall design, develop and deploy the Dashboard, VMS, and NMS as

new applications under this project. The SI shall provide the entire source code of the

Dashboard, AI Application, VMS, NMS, backend services, APIs, and other

applications to SCADL at the end of the contract period without any additional cost.

The SI shall migrate the complete system from cloud to SCADL data centre or to the

infrastructure of a new SI and shall provide all required training to SCADL for

smooth operation post-handover. The application stack shall be cloud/on-prem

neutral and container-ready to avoid vendor lock-in and to support future use-case

additions (e.g., parking duration, payment/penalty status, traffic/safety analytics).

37. The dashboard should be mobile friendly.

5.7 SOURCE CODE & IPR:

The Authority allows a COTS (Commercial Off-The-Shelf) + Customisation solution model for the

proposed system.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

The solution shall comprise:

• A core platform (COTS / proprietary software), and

• Mandatory custom-developed layers created specifically for this project.

IP Ownership shall apply only to the custom-developed components, and not to the entire proprietary

5.7.1 SOFTWARE DEVELOPED UNDER THIS PROJECT:

The following components, if specifically developed, customized, or configured

for this project, shall be the exclusive intellectual property of the Authority

• Custom workflows and business logic

• Custom configuration files and operational policies

• Use-case specific AI configurations, rule sets, and classifiers

• Custom dashboards, reports, and visualizations developed for AMC/SCADL

• Custom API layers, middleware, and integration connectors developed for CCRS,

E-Challan, ICCC, or any other Authority systems

• Custom data models, mappings, and event schemas

The bidder shall provide complete source code, configuration artefacts, deployment

instructions, and technical documentation for the above custom-developed

components at the end of the contract or upon exit, whichever is earlier.

5.7.2 EXEMPTION FOR PROPRIETARY OEM AND THIRD-PARTY

An exemption from the above source code submission requirement shall be granted for

proprietary software platforms that are not developed under this project and have been

supplied through an OEM or third-party licensor. This includes but is not limited to

commercially available Video Management Systems (VMS), Network Management

Systems (NMS), database engines, operating systems, dashcam firmware (OEM base

firmware), AI inference runtime engines, cloud platform services, and any COTS

(Commercial Off-The-Shelf) software. For all such proprietary components, the bidder

shall instead provide valid and transferable licenses in the name of the Authority for the

full contract period, complete API documentation, integration specifications, admin-

level access credentials, and a written undertaking from the OEM or licensor confirming

continued support and license validity. The bidder shall clearly identify all proprietary

components in the Technical Proposal with OEM name, product name, version, and

license type, distinguishing them from project-developed components. Any proprietary

component not disclosed at the bid stage but later identified during the project shall be

treated as project-developed software and the source code submission requirement shall

For avoidance of doubt, core COTS / proprietary platforms, including but not

• Dashcam OEM firmware

• Proprietary AI inference engines

• Commercial VMS, NMS, or analytics platforms

• Database engines and underlying operating systems

shall NOT be subject to source code transfer.

However, the bidder shall ensure:

• Perpetual transferable licenses in the name of AMC/SCADL

• Full admin-level access

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

• API access and documentation

• Configuration export capability

• Continued operability after contract expiry or SI transition

5.8 NMS (Network Management System)

1. The Successful Bidder shall design, develop and maintain a new Network Management

System (NMS) as part of the overall solution. The NMS shall be built specifically for

this project and shall not rely upon or integrate with any existing NMS tools of

2. The bidder shall have the base NMS product available on Day 1 and shall develop,

enhance, and customize all additional features, dashboards, API integrations,

workflows, ticketing, and reporting modules as required in the Scope of Work (SoW).

3. The Bidder shall develop and customize the NMS / Ticket & Incident Creation and

Monitoring System, hosted on Cloud, ensuring complete integration with the

Dashboard, VMS, and LPU device ecosystem.

4. The NMS shall be configured to automatically discover all Dashcams / LPUs integrated

with the Video Management System (VMS). Auto-discovery must operate

continuously based on network availability and must not rely on live streaming.

5. The NMS shall support discovery using SNMPv2/v3, ICMP, LLDP, API-based

discovery, and any other open protocol required for complete device visibility. The

system shall poll all Dashcam/Camera and LPU IP addresses at regular intervals to

determine health, uptime, connectivity, and operational availability.

6. The NMS shall support customizable alert rules, including ability to define operational

time windows (e.g., bus operation 09:00 AM–09:00 PM). Alerts for Dashcams/LPUs

going UP/DOWN must only be triggered within defined operational hours, as per

AMC/SCADL requirements.

7. The NMS shall provide full incident lifecycle management, including ticket creation,

assignment, escalation, status tracking, updates, field-level comments, closure

triggers, and audit logs from opening to fulfilment to closure.

8. The Dashcam/Cameras and LPUs discovered in NMS shall scale to the full quantity

procured under this RFP. The bidder shall provide sufficient number of NMS licenses

to monitor all devices, with no limitation or incremental licensing cost during the

contract period.

9. The NMS shall present reports through a secure web interface and shall support

exports in PDF, Excel, and CSV formats.

10. The bidder shall provide NMS view-only and administrative login access to

SCADL/AMC for viewing device status, uptime/downtime trends, incident progress,

fault history, ticket SLA compliance, and related analytics.

11. All NMS software licenses provided by the bidder shall be perpetual in nature and

registered in the name of AMC/SCADL.

12. The Successful Bidder shall provide, at minimum, the following reports:

• New Dashcam/Camera & LPU Installation Reports – Weekly, Monthly

• Hardware Breakdown SLA Reports – Weekly, Monthly

• Device-Level Incident Reports – Weekly, Monthly

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

5.8.1 Minimum Functional Requirements of the NMS

Operational Time-based Alerts

• The NMS shall allow SCADL/AMC to define operational hours for each

Depot/Vehicle cluster. For example, if buses operate from 09:00 AM to 09:00

PM, the NMS must raise UP/DOWN alerts only within this window unless

otherwise configured.

Alerts and Alarms

• Device Down / No Feed Detection

• When any Dashcam/Camera or LPU:

a. stops responding to polls,

b. fails to upload depot-offload data as scheduled,

c. or shows no heartbeat for a defined interval,

The NMS shall immediately raise an alert indicating:

1. device name,

3. time since down,

4. depot/ward/zone mapping,

5. probable cause (network, power, storage, tamper indicator, etc.).

Comprehensive Alarm Console The NMS interface shall:

• Display all alarms and alerts in real time

• Allow filtering (new alerts, critical alerts, device category, depot,

ward/ zone, LPU/Dashcam type)

• Support SNMP traps, ICMP polls, and API-triggered fault events

• Enable priority-wise alarm classification (Critical, Major, Minor)

• Provide alert notifications through Email, SMS, and Push

Additional Mandatory Requirements:

A. Integration & APIs

o The NMS shall expose open REST/HTTPS APIs for integration with the Dashboard,

VMS, and any SCADL systems.

o The SI shall provide API documentation, sandbox access, versioning, and schema

o The SI shall coordinate with all relevant agencies for integration mandates by

B. Security & Compliance

o All communication must be encrypted (TLS 1.2+).

o RBAC must be enforced with user activity audit logs.

o The NMS shall undergo annual CERT-IN VAPT, with closure of findings mandatory.

C. Scalability & Architecture

o NMS must handle 100% of devices planned in RFP with no performance

o Architecture must be cloud/on-prem neutral and container-ready (Docker/K8s or

o No proprietary locking; open standards only.

D. Ownership & Exit Management

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

o At contract end, the bidder shall hand over the complete source code of the NMS,

including backend, frontend, API services, deployment scripts, and documentation.

o Bidder shall fully support migration to SCADL Data Centre or to a new SI.

5.9 VMS (Video Management System)

1. The Successful Bidder shall design, develop, and deploy a new Video Management

System (VMS) as part of the overall solution. The bidder shall not reuse, extend, or

integrate any existing VMS application of SCADL/AMC. The VMS must be developed

as a dedicated module aligned with the Dashboard and NMS architecture.

2. The VMS shall support ingestion, secure storage, cataloguing, indexing, search,

playback, retrieval, and archival of video clips and images uploaded by

Dashcams/Cameras and LPUs during depot offload cycles.

3. The VMS shall not depend on real-time video streaming for routine operations. It

shall operate fully on event based video uploads, primarily the 10-second event clips

generated by Dashcams/LPUs. Any “Live Stream Trigger” initiated through telecom

services shall be handled as an exceptional request and not as a continuous video

4. The VMS shall integrate seamlessly with the Dashboard and NMS, enabling event-

level correlation such as:

o Event timestamp

o 10-second video clip

o Device ID / Depot / Zone / Ward mapping

o AI tags (bounding boxes, classification)

o Event status, incident ID, or ticket ID

5. The VMS shall store all event-based video clips for a minimum retention period of

days, aligned with dashboard retention. Clips must remain retrievable with no

degradation in quality.

6. The VMS shall maintain a device-wise, depot-wise, and zone-wise video upload

tracker, showing:

o Last successful depot upload time

o Number of clips uploaded

o Missing uploads / incomplete uploads

o Tamper alerts or storage corruption alerts (as sent by NMS)

o Health summary of all devices

7. The VMS shall support role-based access control (RBAC), enabling SCADL/AMC to

define user groups for viewing, downloading, or exporting stored video.

Administrative roles shall be capable of creating event-video linkages and auditing

8. The VMS must support playback of video clips directly within the Dashboard UI,

allowing authorized users to view the clip without downloading. The player must

o Frame-by-frame view

o Bounding box overlays

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

o AI-tags rendering

o Playback speed controls

9. The system shall maintain an Audit Log capturing all playback, view, download, and

deletion activities performed by users, with timestamps and user details.

10. The VMS shall expose open REST/HTTPS APIs for:

o Uploading video clips from Dashcams/LPUs during depot sync

o Retrieving video clips by device ID, event ID, time, location, or tag

o Sharing video metadata with Dashboard and NMS

o Integration with CCRS, Vahan/Sarathi, Police systems and any other agencies

as required by SCADL

11. The SI shall provide API documentation, versioning, payload schemas, sandbox/test

environment, and necessary support for integration with all external systems.

12. The VMS shall provide advanced search capabilities including:

o Device ID / Depot / Zone / Ward

o Event type / AI detection tag

o Ticket/Incident ID (if linked)

o License plate number (if ANPR integrated)

13. All video clips shall be associated with metadata including:

o Device Source

o Event category and AI tags

o File size and checksum

o Upload status (successful, partial, failed)

14. The VMS shall support checksum integrity validation to detect partial uploads,

corrupted files, or tampering of video media.

15. The VMS shall maintain a health monitoring dashboard summarizing:

o Total clips received

o Total clips missing

o Failed uploads

o Devices not uploading for configured intervals

o Devices that repeatedly show corruption alerts

o Depot connectivity health

16. The Successful Bidder shall ensure that the VMS supports export of video clips in

standard formats (MP4/H.264/H.265) and downloadable along with associated

metadata (CSV/PDF).

17. All video storage and retrieval shall be performed via a secure cloud-based

architecture unless otherwise directed by SCADL. If SCADL requires migration to on-

premises data centre in future, the bidder shall support full migration as part of exit

18. All VMS modules, services, libraries, microservices, and APIs must be developed in a

cloud/on-prem neutral and container-ready architecture (Docker/Kubernetes or

equivalent), ensuring no vendor lock-in.

19. The bidder shall provide a perpetual license for the complete VMS application, in the

name of SCADL, covering all modules developed under this project.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

20. The SI shall hand over the entire source code of the VMS application at the end of the

contract period, including backend, frontend, API engine, video processing modules,

CI/CD workflows (if any), infrastructure-as-code (if any), and complete

21. The SI shall provide SCADL/AMC with VMS administrative login access, including:

o User management

o Storage monitoring

o System health reports

o API usage logs

o Configuration of video retention policies

22. The VMS shall provide the following mandatory reports (Weekly & Monthly):

o Total Clips Received

o Missing/Failed/Corrupted Uploads

o Depot-wise Upload Summary

o Device-wise Upload Health

o Storage Utilization Summary

o ANPR-linked Events (if applicable)

23. The VMS shall comply with all security requirements, including TLS encryption,

RBAC, audit logging, password policies, and annual CERT-IN VAPT with mandatory

closure of findings.

24. The VMS shall integrate completely with the NMS for device health visibility, missed

upload alerts, corruption detection, uptime/downtime reports, and system-generated

25. The VMS shall integrate completely with the Dashboard for event playback, evidence

storage, event tagging, department allocation, and status closure workflows.

5.10 Responsibility Matrix (Responsible, Accountable, Consulted,

Activity SI AMC/SCADL AMTS ICCC /

(Bidder) Police

Solution design & architecture R, A C I I

Dashcam procurement & R, A I I -

Dashcam installation on buses R, A I C -

Safety cover & power R, A I C -

Depot Wi-Fi infrastructure R, A C C -

Broadband/leased line at depot R, A C C -

Cloud infrastructure setup R, A I - I

Dashboard, VMS, NMS R, A C - I

AI model development & R, A I - -

CCRS API integration R, A C - C

E-Challan API integration R, A C - C

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Activity SI AMC/SCADL AMTS ICCC /

(Bidder) Police

ICCC integration R, A C - C

SIM procurement & data plans R, A I - -

User Acceptance Testing R A C C

Training of Authority staff R, A C I I

Operation & maintenance (3 R, A C C I

Dashcam R, A I C -

dismantling/reinstallation

Annual cybersecurity audit R, A I - I

Bus availability for installation I C R, A -

Depot access for Wi-Fi I C R, A -

CCRS system access & C R, A - C

E-Challan system access & docs C R, A - C

ICCC access & coordination C R, A - C

Approvals & sign-offs C R, A I I

R = Responsible (Does the work)

A = Accountable (Owns the outcome)

C = Consulted (Provides input)

I = Informed (Kept updated)

Note: ALL responsibilities related to project execution shall be of the SI/Vendor. The

Authority (AMC/SCADL) shall facilitate access, coordination, and approvals.

6. Other Important details

a. Definition of Licenses:

Where SCADL has used license-related terms in the RFP, bidders shall ensure that AMC/SCADL is

granted a perpetual right to use all licensed components, including software solutions (NMS, VMS,

mobile app, AI application, and dashboard), for minimum 500 users expandable to 1000 users. The

solution shall allow a minimum of 100 concurrent login accesses for internal officers (SCADL, AMC,

Police), including administrative access and analytics dashboard, without any additional cost to

AMC/SCADL. Considering the scope of the project and involvement of multiple authorities, bidders

may propose a higher number of concurrent users to ensure operational efficiency.

b. Proof of Concept (POC):

1. For POC, the bidder shall provide and install dashcam/camera and LPU in 1 vehicle and operate

along the designated 3 km stretch for the POC.

2. For POC purposes, SCADL will facilitate the required permission to install dashcam/Camera

and LPU in 1 vehicle on 3 km stretch.

3. The bidder should install dashcam/Camera in any of the vehicle which will be suggested by

SCADL. Once the vehicle starts moving along its usual route, the bidder should record the

events for a duration of 1 hour. The bidder is expected to find the use cases as mentioned in TQ-

3 of section 8.2 of this RFP. The events captured for that duration are to be shown in form of

reports (either on any dashboard, excel, pdf) containing details such as Event identified,

location, date & time stamp of the event occurrence, video clipping and image captured.

4. The event reports submitted by the bidder to be created in near real-time manner by the AI

based application.

5. For any damages/accidents occur during the time of POC, SCADL to be indemnified and the

consequences are to be borne by the bidder.

6. Marks to all bidders for TQ- 4 will be provided through this POC.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

7. The bidder will bear the cost of POC testing, SCADL will not reimburse the cost of POC testing

to the bidders.

7. Operation & Maintenance

During the contract period defined under this RFP, the Successful Bidder shall be

responsible for end-to-end Operations and Maintenance of the complete Dashcam-based

Intelligent Monitoring System. O&M activities shall commence from Day-1 following the

completion of Supply, Installation, Testing and Commissioning (SITC) of the dashcams.

The Successful Bidder shall maintain all system components, hardware, software, network,

cloud resources, AI modules, and applications at performance levels above the benchmarks

specified in the RFP.

The Bidder shall ensure that all applications are architected and instrumented such that

uptime, performance, and availability can be continuously measured, monitored, and

reported throughout the O&M duration.

The Bidder shall always ensure availability of all required application hardware and

software as per SLA norms.

7.1 Scope of Work during O & M

7.1.1 Hardware Maintenance

1. Quarterly preventive maintenance of all Dashcams.

2. Corrective maintenance and fault-resolution as per SLA timelines.

3. Replacement of faulty Dashcams from bidder-maintained buffer stock.

4. SD card health monitoring and replacement as required.

5. Battery health diagnostics and replacement.

6. Inspection and replacement of camera safety covers.

7. Dismantling and re-installation of Dashcams on a pro-rata basis when buses are

retired, rerouted, replaced, or under maintenance.

8. Ensuring continuous availability of all required hardware components as per SLA.

8. Training & Knowledge Transfer

1. The Successful Bidder shall provide comprehensive training to Authority personnel covering the

following groups:

• Technical Team: System administration, cloud management, application configuration,

and backend operations.

• Operations Team: End‑to‑end usage of Dashboard, VMS, and NMS modules.

• Field Staff: Dashboard application usage, incident verification, evidence capture, and

field‑level workflows.

• Management / Decision Makers: Analytics, reporting dashboards, KPI interpretation, and

performance monitoring.

2. A minimum of three (3) rounds of structured training shall be conducted during the

implementation phase, covering functional, technical, and administrative aspects of the system.

3. The Bidder shall conduct annual refresher training sessions during the O&M period for all user

groups to ensure continued proficiency and onboarding of newly assigned staff.

4. The Bidder shall prepare and provide complete user manuals and documentation, including:

i. User guides for Dashboard, VMS, and NMS

ii. Technical and administrative manuals

iii. SOPs for incident management, ticketing, and verification

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

iv. Quick reference guides and FAQs

v. Training presentations and recorded sessions

9. Exit Management & Handover

9.1 Purpose and Applicability

1. This clause governs Exit Management on expiry or termination of the Master

Service Agreement, the Project Implementation, and/or the Operation & Management

2. In case of termination of the Project Implementation and/or O&M, the Parties shall

mutually confirm the period during which this Exit Management Schedule will apply;

the obligations herein shall remain in force throughout the agreed exit period.

3. Each Party shall ensure that its associated entities and subcontractors fulfil their

respective obligations under this Exit Management Schedule.

9.2 Exit Trigger and Notice

1. Exit Management shall be initiated by written notice from the Authority and shall

continue for the duration specified in the notice, subject to the minimum support

defined in 6.6(f) below.

9.3 Cooperation and Information Access during Exit

During the Exit Management Period:

a. The SI shall provide the Authority or its nominated agency reasonable access to

information required to define the then-current mode of operation of the services.

b. On the Authority’s reasonable request, the SI shall provide access to, and copies of,

all information prepared or maintained under this Agreement relating to any

material aspect of the services, including service delivery and performance data; the

Authority shall be entitled to copies of all such information. The SI shall also provide

reasonable access to relevant employees and facilities for knowledge transfer.

9.4 Confidential Information, Security and Data

a. From the commencement of Exit Management, the SI shall supply to the Authority or

its nominated agency: service information and performance data (including that of

subcontractors), documentation related to intellectual property, subcontractors, all

current and updated data necessary for transition in a format nominated by the

Authority, and all other information reasonably required to transition the services to

the Authority or a Replacement SI.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

b. Before expiry of the Exit Management Period, the SI shall deliver all updated

materials referenced above and shall retain no copies except a single archival copy, if

legally permissible.

9.5 Transfer/Novation of Certain Agreements

a. Upon request, the SI shall effect assignments, transfers, licenses or sub-licenses in

favor of the Authority or the Replacement SI in relation to equipment lease,

maintenance or service agreements between the SI and third-party vendors, to the

extent reasonably necessary to ensure continuity of services post-transition.

9.6 Handover Deliverables

At contract completion or termination, the SI shall ensure:

a. All hardware assets are handed over in working condition.

b. Complete software source code transferred (excluding proprietary third-party AI

models not created under this contract).

c. All data (including videos, images, logs, configurations, tickets, analytics, reports, audit

trails) are transferred to the Authority’s designated systems/platforms in open,

Authority-nominated formats.

d. Administrative credentials and access (all environments cloud, applications,

databases, storage, CI/CD, monitoring, domains, certificates, repositories, API gateways)

are transferred.

e. Complete documentation and knowledge transfer (architecture diagrams, data

flow, runbooks, SOPs, deployment scripts, API specs, network & security configs, test

cases, acceptance reports).

f. Transition support for a minimum of 3 months post-handover to the Authority or

Replacement SI.

g. AI model license (if any third-party licenses used) remain valid until their stated

expiry, license artefacts and keys are transferred to the Authority as permissible.

h. Cloud data migration to the Authority’s designated platform/tenant (including object

storage, databases, backups, logs, metrics, dashboards) with verified integrity and

9.7 General Obligations of the SI during Exit

a. Provide all information reasonably necessary to enable a seamless handover to the

Authority or Replacement SI.

b. Any information or asset in the possession or control of the SI’s affiliated entities or

subcontractors shall be deemed to be in the SI’s possession or control for the purpose of

this Schedule, and the SI shall procure the same.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

c. Commit adequate resources to comply with this Exit Management Schedule.

9.8 Exit Management Plan (EMP)

a. The SI shall submit an Exit Management Plan within 90 days from the Effective

Date, covering at least: a detailed transfer program; continuity plans to ensure

uninterrupted services during transition; communication plans with

subcontractors/staff/suppliers/customers/third parties; (if applicable) segregation of

networks and security tasks at termination; and provision of contingent support to

the Authority and Replacement SI for a reasonable period after transfer (not less than the

minimum defined in 6.6(f)).

b. The EMP shall be reviewed and re-drafted annually to remain current and relevant,

and shall be presented to and approved by the Authority/nominated agency.

c. On termination or expiry, the Parties shall comply with the latest approved EMP.

d. The terms of payment include the costs of the SI complying with this Exit Management

Schedule, payments during Exit shall be as per the Terms of Payment Schedule.

9.9 Knowledge Transfer (KT)

a. The SI shall conduct structured KT sessions to ensure the Authority’s teams

(administration, operations, field, and management) can operate, support, and further

transition the system independently. This includes walkthroughs of architecture,

configurations, security, APIs, deployment/rollback, backup & recovery, monitoring &

alerting, and operational runbooks.

b. All KT artefacts (manuals, QRGs, session recordings) shall be delivered in soft copy and

9.10 Compliance, Security and IP

a. The SI shall return or destroy (as directed) confidential information, retaining only a

single archival copy if legally required.

b. IP created under the contract shall be transferred per contract terms, third-party

proprietary components (e.g., external AI models) are excluded, but all rights, binaries,

configurations, and licenses procured for the project shall be novated or assigned to the

Authority to the extent legally permissible.

9.11 Service Continuity and Best Efforts

a. During the Exit Management Period, the SI shall use best efforts to maintain service

quality and ensure no material degradation of services until handover is complete.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

10. Manpower deployment

Successful bidder will have to deploy below mentioned minimum manpower for entire contract duration at

Ahmedabad location.

Designation Qty Roles & Responsibilities Desired Qualification

i) Supervise the entire project/resources

· BE /B. Tech with MTech/MBA

on regular basis during implementation

& O&M Phase and co-ordinate with the

Minimum 8 Years of Experience

authority nominated by AMC/SCADL.

in large scale ICT/IT/ITES

ii) Will ensure that everything is getting

Project Manager infrastructure projects.

1 implemented as per the agreed plan and

SLAs. Preparing MIS Reports, etc.

Relevant Experience: Minimum

iii) Coordination with their field

Years of experience as a

manpower for fault resolution, project

project manager of large-scale

implementation, coordination other

CCTV and Analytics Projects.

stakeholders etc.

. Act on any critical issues.

. Coordinate with various departments

and stakeholders for necessary . Graduate in Any stream

Field permissions . 4+ years’ work experience in

Coordinator (On 2 . Should have entire end-end knowledge similar field.

site) regarding the dashcams ’ status.

1. All resources as mentioned in above table to be available with BIDDER from start of Installation period

2. The Project manager shall be available for discussion, meeting and working jointly with AMC/SCADL team

during implementation and O&M phase.

3. Leave of 2 days apart from government leave is allowed in a month during implementation Phase. For

absence of more than 2 days in a month, Penalty of INR 1,000 per day will be levied per resources for not

keeping required Manpower.

11. Functional Specifications

1. Full HD dashcam of 1920 x 1080 resolution and Micro SD card of 512 GB shall be used

for achieving the project objective under this tender.

2. Each dashcam will be running for minimum 10 hours a day for continuous surveillance

3. Each dashcam shall generate data as below.

o Event Video Clips: Short duration clips (minimum 5 seconds pre-event and

5 seconds post-event i.e. a total of 10 seconds) generated by AI analytics on

detection of predefined use cases.

o Metadata and Telemetry: GPS coordinates, timestamp, device health

status, event logs, and sensor data associated with video events.

o Firmware and AI Model Updates: Bi-directional data exchange to support

OTA updates and configuration changes.

4. Bidder shall consider the amount of data being generated through each of these

dashcams with the assumptions below.

Sr. No. Parameter Value

1 Video Bitrate 8 Mbps

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Sr. No. Parameter Value

2 Data generated per hour / camera 3.6 GB

3 Operating hours per day 10 hours

4 Data generated per day / camera 36 GB

5 Number of dashcams

6 Total data generated per day 36 TB

7 MicroSD card size per camera 512 GB

Bidder shall keep necessary space for the edge-based analytics of selected priority use cases.

11.1 Video Summarization

The system shall include a Video Summarization module capable of automatically

generating condensed, event‑centric summaries from the recorded video footage uploaded

during depot offload. The summarization engine shall identify key motion segments, object

activities, and AI‑detected events, and produce a compressed visual timeline that enables

faster review by AMC/SCADL officials. The module shall support search and filtering based

on time range, event type, device ID, and location metadata, and must operate without

degrading performance of primary analytics workflows. All summarization outputs shall be

accessible through the Dashboard and VMS interfaces and shall comply with the project’s

data retention and security requirements.

12. Data Transmission to Cloud

1. Bidder shall ensure secure, reliable, and efficient transmission of dashcam video

footage, event clips, and analytics metadata from edge devices (dashcams/LPUs) to

the cloud infrastructure for storage, processing, and monitoring.

2. Bidder shall accordingly design the transmission triggers and schedules.

3. For Event-Driven Upload: By default, video clips corresponding to detected

incidents or triggers will be uploaded to the cloud in real-time for priority 1 use cases

and in near real-time for priority 2 use cases to enable prompt action. If due to

threshold the events are not able to be pushed to the cloud in real-time, then they

should be pushed to the cloud during depot offload.

4. For Scheduled Bulk Upload: Continuous or buffered footage stored locally on

MicroSD cards will be batch-uploaded during scheduled windows via Wi-Fi/P2P

network at depot as and when the vehicle reaches depot.

5. For Fallback Mechanism: In case of network unavailability, data is retained locally

until re-connection; automatic retry logic must be implemented. At the same time,

NMS & VMS alerts shall be generated requiring resolution of network unavailability.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

6. For accuracy & confidence handling: Events detected with high confidence shall

be transmitted in priority over continuous stream uploads to optimize bandwidth

12.1 Data Storage on Cloud

• The entire solution is required to be deployed on the cloud. No on premises

infrastructure including servers, storage, networking equipment, smart racks, or

passive cabling—is required under this RFP.

• Accordingly, the bidder is not expected to replicate cloud level scalability, redundancy,

or availability through any on premises setup, as the solution will operate fully in the

cloud environment.

• Continuous Video Data: Depending on solution design, either full continuous video

streams should be transmitted for cloud storage or advanced analytics.

12.2 Network Connectivity and Seamless Data Transmission Mechanism

Use of 5G cellular connection on SIM-enabled devices for uploads during bus running

Automatic switching to Wi-Fi/P2P/Broadband networks at vehicle depot or designated

locations for bulk data transfer shall be enabled for transmission of data to cloud.

Bidder shall also Seamless handover and multi-network support to ensure continuous

data flow without loss.

13. Technical Specifications

Sr. No. Parameter Minimum Specification

1 Video Resolution Full HD 1920×1080 @ 25 fps or better

2 Video Compression H.265 (HEVC) or better

Built-in high-capacity edge processor (refer to

LPU Specifications in below section for

specifications) for real-time analytics of

3 Edge AI Processing

cases. Alternatively: Military/industrial-

grade rugged LPU at bidder's cost

4 RAM ≥2 GB DDR3 or higher

5 HDR HDR Compatible

Built-in MicroSD slot, minimum 512 GB card

6 Storage supplied. Alternatively: External SD card

enclosure at bidder's cost

1 SIM Card slot mandatory, good to have 2 nos.

built in 5G SIM card slots.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Sr. No. Parameter Minimum Specification

Alternatively: External 5G SIM router/module

at bidder's cost. The proposed dashcam shall

have a minimum of 1 (one) built-in SIM card

slot supporting 4G/5G connectivity as

Built-in battery ≥3000 mAh, minimum 2 hours

standby, 4 hours continuous operation.

8 Battery Backup

Alternatively: External power bank at

9 Field of View ≥110° wide-angle (Horizontal)

802.11 b/g/n/ac or better for depot

11 Bluetooth 2.0 or better

Integrated with G-Sensor, collision detection,

5-10V DC (USB) or direct connection to vehicle

13 Power Supply battery system (12V/24V with voltage

14 Operating Temperature 0°C to 70°C

15 Humidity Up to 95% non-condensing

Camera + mounting assembly must form

16 Vibration Resistance

vibration-resistant unit

17 Electronic Image Stabilization Required

18 WDR Wide Dynamic Range – Supported

19 Night Vision IR illuminators for low-light detection

20 IR Cut-Off Lens Required to reduce glare and flaring

Must read license plates with headlights ON

21 ANPR Capability

and in low light

Continuous recording with automatic

22 Loop Recording

Auto-detection of stationary/parked state to

23 Parking Sensor

pause unnecessary monitoring

Physical emergency button triggering alert on

25 Audio Microphone – Supported, Speaker – Supported

Adhesive / Bolted / Suction mount (vibration

Protective enclosure/housing to prevent

27 Safety Cover

vandalism, tampering, dust

28 Operating System Custom Linux-based OS or Android

ISO 9001, ISO 20000, ISO 27001, BIS, IS

29 Certifications

30 Warranty 3 years comprehensive on-site

Progressive scan CMOS, minimum 2 MP

31 Image Sensor

32 Video Bitrate Configurable: 2 Mbps to 14 Mbps

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Sr. No. Parameter Minimum Specification

Built-in IR LEDs for night vision, minimum

33 IR / Night Vision

10m effective range

Support for OTA (Over-the-Air) AI model

34 Ai Model Update update without requiring physical access to

AI inference must operate completely offline

(without network connectivity). All 10 P1 use

35 Offline Operation

cases must run on-device without cloud

Built-in GNSS receiver supporting GPS /

GLONASS / BeiDou (minimum GPS + one

additional constellation) with Horizontal

accuracy ≤2.5 meters (CEP 50%) in open sky

and Minimum update rate of 1 Hz (1 position

USB 2.0 or higher (Type-A or Type-C) is

37 Bluetooth mandatory. RJ-45 is desirable but not

Should have USB 2.0 or higher (Type-A or

Type-C). Optionally desirable: RJ-45 Ethernet

port (10/100 Mbps) for diagnostics, firmware

flash, and external accessory connection.

13.2 Specifications for external accessories

If the proposed dashcam does not have built-in features, the bidder must specify external

accessories meeting the following:

• External SIM Router/Module (If Dashcam/LPU Has No Built-in SIM slot)

• External Power Bank / Battery Backup (If Dashcam Has No Built-in Battery)

• External SD Card Enclosure (If Dashcam Has No Built-in SD Slot)

ALL external accessories must be included in the bid price and covered under the same

warranty and SLA.

13.3 Vehicle Power Connection Kit

• Bidder shall provide DC-DC converter 24V to 12V/5V, automotive fuse, TVS surge

protector, reverse polarity protection, 3m shielded cable, weatherproof connectors,

ignition sense wire for vehicle power connection.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

13.4 Local Processing Unit (LPU)

Point Technical Specification

The LPU shall be a vehicle-mounted edge compute unit that

executes real-time analytics for all Priority-1 use cases on

1 Purpose/Role dashcam streams, generates events, and transmits data securely to

the cloud VMS/Dashboard; centralized-only processing is not

≥8 cores processor, suitable for concurrent real-time inference and

secure transport on up to 3× 1080p streams.

Integrated GPU/NPU/AI accelerator sized to run ≥8 use cases

3 AI Acceleration

per camera concurrently, at 1080p without frame drops.

≥ 32 GB RAM to support multiple models, buffering, encryption,

and management agents in parallel.

Hard enabled Linux-based OS or Android OS, compatible with

5 Operating System

open standards and security hardening/VAPT requirements.

Must ingest RTSP streams from dashcams and support ONVIF

6 Stream Ingest & Interop where applicable, northbound integration via published

HTTP/HTTPS REST APIs to VMS/Dashboard/ICCC.

7 Codec Support Decode H.264/H.265 video

For each detection, create/upload 10-second clip, with

8 Event Clip Handling store-and-forward queuing if uplink is unavailable; continuous

recording stays local on camera SD (7-day loop).

4G/5G-compatible uplink (integrated or via tether) with policy to

9 Networking - Cellular send events over cellular and defer bulk sync to depot Wi-Fi where

802.11 b/g/n (or better) Wi-Fi for depot sync/admin access and

10 Networking - Wi-Fi / LAN

≥1× GbE port for service/maintenance and in-bus wiring.

Expose SNMP/ICMP health (up/down, CPU, memory, storage,

11 Manageability / NMS last-event time) for the NMS and SLA dashboards, support

incident/ticket linkage.

All northbound communications (events, images, clips, logs) shall

12 Security - Transport use HTTPS with TLS, device must support secure authentication

and align with RBAC enforced at platform.

Generate and retain system, audit, alert, and event logs locally

13 Security - Auditability with time sync and forward to the cloud platform, support annual

CERT-IN VAPT remediation.

Operating temperature 0 °C to 80 °C, ≤95% RH

14 Environmental non-condensing, vibration/shock-resistant vehicle-grade

Compact, lockable, in-cabin mount with anti-tamper features; ≥1×

15 Form-Factor / I/O USB for service/modem, status LEDs or software indicators for

field diagnostics.

Attach GPS (Lat/Long) from dashcam feed to every event for

Beat Mapping, or separate vehicle GPS integration required.

Implement on-edge de-duplication heuristics

17 De-duplication

(camera/vehicle/time/geo) to minimize duplicate events

Must support integration with ICCC/VMS/NMS/CCRS via

18 published APIs for live view, playback pointers, incident creation,

(ICCC/CCRS/VMS)

and status sync (closed/resolved).

19 Image Sensor Progressive scan CMOS, minimum 2 MP (1920×1080)

20 Video Bitrate Configurable: 2 Mbps to 14 Mbps

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Point Technical Specification

Built-in IR LEDs for night vision, minimum 10m

21 IR / Night Vision

effective range

Support for OTA (Over-the-Air) AI model update

22 AI Model Update

without requiring physical access to camera

AI inference must operate completely offline (without

23 Offline Operation network connectivity). All 10 P1 use cases must run on-

device without cloud dependency.

Built-in GNSS receiver supporting GPS / GLONASS /

BeiDou (minimum GPS + one additional constellation)

24 GPS Module with Horizontal accuracy ≤2.5 meters (CEP 50%) in

open sky and Minimum update rate of 1 Hz (1 position

Minimum 1 built-in physical SIM card slot supporting

5G/4G and auto-switch. Active-Standby or Dual Active

mode. Automatic failover from SIM 1 to SIM 2. Remote

25 (if dashcam does –

SIM activation/deactivation, APN Configuration, data

not have sim card slot)

usage monitoring via NMS. (Additional SIM at the

bidder's discretion and cost)

Built-in Bluetooth 4.2 or higher (BLE support) for local

diagnostics, configuration, and accessory pairing

Should have RJ-45 Ethernet port (10/100 Mbps

minimum) and Minimum 1 × USB 2.0 or higher (Type-A

or Type-C) for diagnostics, firmware flash, and external

accessory connection

Built-in microphone for ambient audio recording. Noise

cancellation preferred. Built-in speaker for: Audio

alerts/warnings, SoS acknowledgement tone. Minimum

The two SIM card slots provided in the Dashcam/LPU are not intended to operate in

active dual-SIM mode simultaneously. However, in scenarios where the Successful Bidder

identifies specific geographical pockets or route segments with intermittent or

low-coverage network zones, the Bidder may configure the secondary SIM as an alternate

connectivity option to ensure maximum uptime and optimized network availability,

without compromising system performance or SLA requirements.

13.5 Cloud Storage

Point Specifications

The solution must be hosted on a MeitY-empanelled

cloud provider, hosted within India.

Cloud hosting must comply with MeitY cybersecurity

Cybersecurity guidelines, including secure architecture, encryption, IAM,

Standards audit mechanisms.

CSP should be ‘Safe To Host’ Certified

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

Point Specifications

The bidder must conduct annual VAPT (Vulnerability

Assessment & Penetration Testing) by a CERT-IN

3 Cybersecurity

certified agency for the entire solution (cloud backend,

dashboard, database). Must fix all vulnerabilities found.

The cloud shall host: AI Application, Dashboard, Cloud

4 VMS, and Open-Source NMS as part of the integrated

Cloud platform must support open-architecture design,

Open-Architecture enabling interoperability via ONVIF, RTSP,

Requirement HTTP/HTTPS APIs, REST APIs for external system

The cloud must expose published APIs for integration

6 API Integrations with ICCC, CCRS, RTO/Vahan, e-GujCop, and other

Cloud backend must handle maximum dashcams specified

7 Scalability in RFP, future expansion, additional use cases, and

increased storage requirements.

Cloud platform must support complete incident lifecycle,

8 escalation matrix, closure workflows, SLA dashboards, and

integration with NMS problem/ticketing.

Data Cloud platform must ensure encrypted transmission of

9 Transmission event snapshots, metadata, logs, and manage secure

Security uploads from LPUs.

13.6 Broadband Connectivity at Bus Depot

Providing network connectivity is not a part of bidder’s scope. However, Bidder shall

ensure that each of the bus depots must have broadband connectivity with

minimum requirements as mentioned below.

Bidder should inform the SCADL/AMC in case required broadband

connectivity is not available at the depot. SCADL/AMC shall arrange the

same as and when required.

Specification Parameter Requirement / Specification

Broadband Network Type Dedicated Fiber Optic Leased Line / Ethernet over Fiber/

Connectivity Broadband

Latency < 10 ms end-to-end within depot network

Network ≥ 95% SLA guaranteed uptime

Redundancy Dual redundant internet links for failover

Protocols Support for Layer 2/Layer 3, VLAN tagging, QoS

Network SNMP-based monitoring, alerts, remote diagnostics

Scalability Upgradeable to 4 Gbps or higher as needed

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

13.7 Power Connectivity of Dashcams

1. Dashcams shall be powered directly from the vehicle’s electrical system, typically the

12V or 24V DC supply available in buses.

2. Power should be drawn in a manner that does not interfere with vehicle operation or

violate manufacturer warranties.

3. Dashcams must support a 5V to 10V DC power input range, commonly delivered via

USB (Type-A or Type-C) or dedicated power connectors compatible with vehicle wiring

4. Power input should include over-voltage, under-voltage, and reverse polarity

protection to safeguard the dashcam electronics.

5. Dashcams shall be equipped with an internal battery backup of minimum 3000 mAh

capacity or equivalent, providing at least 4 hours of continuous operation in case of main

6. The battery should enable safe shutdown procedures or continued recording during

power interruptions.

7. Cameras should support smart power management to handle vehicle ignition status

(on/off), enabling automatic startup and shutdown synchronized with vehicle power

8. The Bidder shall provide a dedicated power bank (battery backup unit) for each

dashcam unit to ensure uninterrupted operation during periods when the vehicle's main

power supply (vehicle battery) is switched off.

9. The power bank must have a minimum capacity of 10,000 mAh or higher, capable of

providing at least 7 hours of continuous dashcam operation, including video recording,

AI analytics, and data transmission as applicable.

10. The Bidder shall be responsible for the maintenance, replacement, and warranty of

the power bank throughout the contract period.

11. Power cabling and connectors must meet automotive-grade standards for vibration

resistance, temperature range (0° to 50°C or as specified), and electromagnetic

compatibility (EMC).

All wiring should follow vehicle safety protocols and be protected against accidental

disconnection or shorts.

Aspect Specification

Power Supply 5–10 V DC from vehicle battery (12V/24V system)

Input Interface USB power (Type A/C) or dedicated automotive connectors

Protection Features Over-voltage, under-voltage, reverse polarity, surge protection

Battery Backup Minimum 3000 mAh; ≥4 hours continuous operation

Power Management Auto on/off with vehicle ignition; parking mode with low power

Wiring & Connectors Automotive-grade, vibration and temperature-resistant

Compliance Automotive EMC/EMI standards

Note: The AI system shall maintain required detection accuracy under the following mandatory

• Vehicle moving at 20–40 km/h

• Daylight, low-light, street-light, and headlight glare conditions

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

• Mixed lighting (shadow/glare transitions)

• Mild vibration typical of bus movement

14. Standards & Safety Compliance

The bidder shall ensure that all hardware, installation practices, vehicle integrations,

power kits, and operational processes comply with applicable national standards and

government guidelines, including the following:

(a) BIS Standards

• Compliance with IS 13252 (Part-1): IT Equipment – Safety Requirements

• Compliance with relevant BIS standards for automotive-grade electronics, power

accessories, connectors, and wiring

• All supplied components must be BIS-certified wherever applicable

(b) MeitY Guidelines

• Compliance with MeitY cloud security framework for hosting, encryption,

authentication, data isolation, and cyber-security requirements

• Conformance to MeitY’s guidelines for data handling, retention, audit, and cyber

(c) MoRTH (Ministry of Road Transport & Highways) Guidelines

• Installation inside vehicles shall comply with MoRTH vehicle-safety notifications

• Mounting of dashcams, LPUs, wiring and power kits must not obstruct driver view,

dashboard indicators, OEM vehicle systems, or violate AIS/CMVR guidelines

• Cable routing and accessory placement must comply with MoRTH safety norms for

in-vehicle electronics and retrofitting

(d) Power & Electrical Safety

• Automotive-grade DC-DC converters, fuses, surge protectors, reverse-polarity

protection, and wiring rated for bus/vehicle environment are mandatory

• All electrical assemblies must comply with IEC/BIS safety requirements for

vehicular installations

(e) Fire Safety & Insurance

• All equipment installed shall comply with fire-retardant material requirements as

per BIS and automotive standards

• Vendor must ensure that installation does not void the vehicle’s insurance or violate

• Any claims arising due to installation defects shall be the responsibility of the bidder

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

(f) Installation Safety Certification

• Vendor shall issue a post-installation safety compliance certificate for every vehicle,

confirming adherence to BIS/MeitY/MoRTH requirements.

15. Project Design Overview

15.1 System Architecture

Vehicle / edge layer

Component Detail

DASHCAM Full HD 1920×1080, 30 fps, GPS, SIM, Battery, Safety Cover

10 Priority 1 Use Cases, Real-time De revised RFP tection on

LOCAL 512 GB MicroSD – Continuous video (~14 days rolling), Event logs,

STORAGE 10-sec clips

Direct from AMTS bus battery (with voltage regulator + surge

This is the data capture and primary intelligence layer deployed inside each AMTS/AMC

A. Dashcam Unit:

• Latest technology Full HD (1920×1080) camera recording continuously at 25 fps

during bus operational hours (approximately 10-12 hours/day)

• Equipped with wide-angle lens (≥110°) for maximum road coverage

• HDR/WDR and IR night vision for varied lighting conditions

• Electronic image stabilization to counter vehicle vibrations

• ANPR capability for reading vehicle registration plates

• Built-in GPS with G-sensor for precise location tagging and collision detection

• SoS emergency button for driver-triggered alerts

• Parking sensor to detect stationary state and optimize recording/analytics

B. Edge AI Processing

• Built-in AI processor within the dashcam (preferred) OR military/industrial-grade

rugged LPU installed inside the bus

• Processes video in real-time for 10 Priority 1 use cases

• Generates incident detections with GPS, timestamp, video clip (10 sec), snapshot, and

confidence score

• Operates independently — does not require network connectivity for detection

• Events queued locally when offline, synced when connected

C. Local Storage

• 512 GB MicroSD card (built-in slot or external enclosure)

• Stores continuous video footage in rolling/loop recording mode (~14 days retention at

Full HD 8 Mbps bitrate)

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

• Stores event logs and 10-second incident video clips

• Data persists until successfully uploaded to cloud

D. Connectivity Modules

• Data SIM card slots (built-in or external module) for cellular connectivity Wi-Fi

(802.11 b/g/n/ac or better) for depot data offloading

• Bluetooth or better for local diagnostics

E. Power System

• Primary: Direct connection to AMTS bus battery system, (12V/24V) with voltage

regulator, fuse protection, and surge protection circuitry

• Backup: Built-in battery (≥3000 mAh, 6 hours standby, hours continuous) or external

power bank ensures dashcam operates even during bus engine-off periods at depot for

data offloading

F. Physical Protection

• Protective safety cover/housing installed over the dashcam

• Anti-tamper mechanisms to prevent unauthorized removal

• Vibration-resistant mounting assembly

• Dust and splash protection suitable for bus environment

15.2 Connectivity Layer

CHANNEL PURPOSE

Event log to CCRS, Event log to E-Challan system, Live

1 Data SIM streaming on ICCC demand, Backup data sync (if Wi-Fi

fails), Device management and OTA updates

Full video footage upload to cloud, Automatic detection

DEPOT Wi-Fi when bus enters depot, Priority: events first then

(802.11ax) continuous footage, Incremental/differential sync, Retry

3 Broadband / Leased Line

This layer handles all data communication between the vehicle layer and the cloud platform

Two Distinct Connectivity Channels:

Channel 1: Sim Connectivity

Purpose: On road (bus running) event transmission and on-demand live streaming

a) Event Log Transmission

• When an incident is detected by edge AI, the event metadata (incident type, GPS

coordinates, timestamp, confidence score, thumbnail image) is immediately transmitted

to the cloud platform via SIM

• Event data is lightweight (~50-200 KB per event)

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

• Enables near real-time CCRS ticket creation and

• E-Challan generation

b) On-Demand Live Video Streaming (Iccc Triggered)

• ICCC operators can request live video feed from any specific dashcam at any time

• Live stream initiated via SIM connectivity

• Used for real-time monitoring, incident investigation, or emergency response

• Streaming at reduced resolution/bitrate to optimize data consumption

c) Device Management

• Remote monitoring, configuration, and OTA firmware updates via NMS

• Heartbeat signals for device health monitoring

• SIM data usage monitoring

d) Data Pack Optimization:

• SIM data plans shall be provisioned with MINIMUM data allocation optimized for the

above functions

• Primary data transfer (bulk video) happens via depot Wi-Fi — SIM is NOT the primary

bulk transfer channel

• Estimated monthly data per dashcam:

o Event metadata: ~100-500 MB/month (varies by route)

o Live streaming (on-demand): ~1-3 GB/month (estimated)

o Backup sync: Variable

o Device management: ~50-100 MB/month

• Bidder must design and propose optimal data plan with justification in technical

Channel 2: Depot Wi-Fi Connectivity (Bulk Data Transfer)

Purpose: Automated bulk video footage offloading when bus is at depot

a) Automatic Network Detection

• When bus enters depot Wi-Fi zone, dashcam automatically detects and connects to the

designated Wi-Fi network

• Authentication via pre-configured WPA3 credentials

• Connection established without manual intervention

b) Prioritized Data Upload

• Upload sequence:

o Priority 1: Event video clips (10 sec each) not yet uploaded

o Priority 2: Event logs and metadata not yet synced

o Priority 3: Continuous video footage (oldest first)

• Ensures most critical data reaches cloud first

c) Incremental / Differential Sync

• Only data NOT already uploaded (via SIM or previous Wi-Fi session) is transferred

• Deduplication logic prevents re-uploading same data

• Checksum verification ensures data integrity

d) Transfer Management

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

• Retry and resume for interrupted transfers

• Transfer progress tracking on NMS dashboard

• Bandwidth throttling to prevent network congestion

• Scheduled transfer windows to balance load across buses

Depot Wi-Fi Infrastructure:

• Enterprise-grade Wi-Fi 6 (802.11ax) Access Points

• Coverage: All bus parking areas within each depot

• Capacity: Simultaneous data sync from all buses parked

• Backbone: Gigabit Ethernet or better wired network

• Uplink: High-speed broadband / leased line to cloud

• Security: WPA3, VLAN segregation, MAC filtering

• Management: Centralized Wi-Fi controller

15.3 Cloud Platform Layer (MeitY-Empanelled CSP, India-hosted)

COMPONENT DETAILS

P2 Use Cases, Cloud analytics, Model training, Batch

2 MANAGEMENT Playback, Search, Export, Live stream relay

1000+ device monitoring, SIM data, OTA, SLA

DATABASE & 30 days video, 90 days clips, 3.5 yrs all logs, Tiered

STORAGE storage

GIS Mapping, Event Management, Analytics, Reports,

5 CCRS Status, E-Challan View, Fleet Health, Live

Streaming, Admin Panel

6 API LAYER REST APIs (HTTPS, OAuth 2.0)

This layer hosts all software applications, AI processing, data storage, and management

systems on MeitY-empanelled cloud infrastructure within India.

A. AI Analytics Engine

• Processes Priority 2 use cases using video footage uploaded from dashcams

• Batch processing pipeline handling footage from 1000+ dashcams daily

• AI model training and retraining infrastructure

• Model versioning, A/B testing, and performance tracking

• Scalable compute resources (GPU/CPU) for analytics workloads

B. Video Management System (VMS)

• Manages all video data from 1000+ dashcams

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

• Video ingestion pipeline for depot-uploaded footage

• Live stream relay from dashcams (via SIM) to dashboard/ICCC

• Video playback, search (by time, location, event, vehicle)

• Video export with chain-of-custody watermarking

• Support for H.265/H.264 formats

• ONVIF and RTSP protocol compatibility

C. Network Management System (NMS)

• Monitoring of all 1000+ dashcams

• Device health: online/offline, battery, storage, SIM status

• Depot Wi-Fi infrastructure monitoring

• SIM data usage tracking per device

• Data sync status monitoring (per bus, per depot)

• OTA firmware and software update management

• Automated alerting for failures and anomalies

• SLA compliance tracking and reporting

D. Database & Storage

Designed with cost-optimized tiered storage architecture:

• Hot Storage (Days 0-7):

o Recent continuous video footage

o Recent event clips and logs

o Active dashboards and queries

o High-performance, high-cost storage

• Warm Storage (Days 8-30):

o Continuous video footage approaching retention limit

o Moderate access frequency

o Balanced performance and cost

• Cold / Archive Storage (Days 31-90):

o Event video clips (10-sec) beyond 30 days

o Infrequent access, retrieval acceptable with slight delay Low-cost archive

• Persistent Storage (Entire Project Duration):

o All event/incident logs and metadata

o Vehicle logs (route, GPS trail, operational data)

o System logs, audit trails, application logs

o CCRS ticket records and E-Challan records

o Dashboard analytics and reports

o Lightweight data, relational/NoSQL databases

• Automated Lifecycle Management:

o Policies auto-migrate data between tiers based on age

o Autodeletion of continuous video after 30 days

o Autodeletion of event clips after 90 days

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

o Logs and metadata retained until project completion

o All policies auditable and configurable

E. Centralized Ai Dashboard

o Web-based responsive application

o GIS-mapped real-time event and vehicle visualization

o Role-based access (1000 users, 100 concurrent)

o Event lifecycle management

o CCRS ticket tracking view

o E-Challan tracking view

o Analytics, heatmaps, trend analysis, reports

o Fleet health monitoring

o Admin and configuration module

o RESTful API layer for all integrations

o Secured via HTTPS, OAuth

o Well-documented (Swagger/Open API)

o Connects to CCRS, E-Challan, ICCC, and future systems

15.4 Integration & User Layer

SYSTEM FUNCTION

1 AMC CCRS SYSTEM Auto ticket generation for civic issues

2 E-CHALLAN SYSTEM Auto challan generation for traffic violations

3 ICCC Event feed + live video trigger

4 RTO / TRAFFIC POLICE Traffic enforcement integration

5 FUTURE SYSTEMS Expandable for future integrations

AHMEDABAD Ultimate Beneficiaries

This layer connects the dashcam platform with AMC's existing systems and end users.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

15.5 AMC CCRS INTEGRATION

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

15.6 E Challan Integration

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

15.7 ICCC integration

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

15.8 Use Case Output Specification

For every incident detected (civic or traffic):

Incident packet:

• Incident ID – System-generated unique ID

• Use Case Type – Classification label

• Domain – Civic / Traffic / Infrastructure

• GPS Coordinates – Latitude, Longitude

• Reverse Geocode – Road name, area, zone, ward

• Timestamp – Date + Time (seconds precision)

• Video Clip – 10 seconds (5 pre + 5 post)

• Snapshot Image – High-res still frame

• Confidence Score – AI detection confidence (%)

• Bus / Vehicle ID – AMTS bus number

• Route ID – Bus route number/name

• Camera ID – Dashcam unique identifier

• Priority / Severity – Critical / High / Medium / Low

• Status – New → Assigned → In Progress → Resolved → Closed

Additional fields for traffic violations

• Vehicle Reg. No. – Via ANPR

• Vehicle Type – Two-wheeler / Car / Auto / etc.

• Violation Code – As per Motor Vehicle Act

• Evidence Quality – Sufficient / Insufficient flag

• Civic Issues → AMC CCRS (auto-ticket generation)

• Traffic Violations → E-Challan System (auto-challan generation)

• All Events → Centralized Dashboard + ICCC feed

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal

Infrastructure. Attempt -

15.9 Workflow of Entire System

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

16. Pre-Qualification Criteria

The bidder must possess the requisite experience, strength and capabilities in providing services necessary to meet the

requirements as described in this document. The bids must be complete in all respects and should cover entire scope of work as

stipulated in the bid document. This invitation to bid is open to all bidders who qualify the eligibility Criteria as given below.

Sr No Description Minimum Requirement Documentary Proof

1.1 Consortium is allowed for participation in this tender. Consortium a) Original or Notarized Copy of

should be of maximum of two (2) parties. consortium partnership with

1.2 Collectively they should meet the aggregate requirement for clearly defined stake and scope of

financial, experience and technical capability described in this each partner.

PQ 1 Consortium

document for eligibility. b) Undertaking by lead SI of

consortium to be sole responsible

for execution of work defined in

RFP and meeting the performance

2.1 The bidder (whether sole or all consortium partners) should be an a) Copy of certification of

Indian firm. incorporation issued by

2.2 The bidder should be registered under the Companies Act 1956/2013 competent authority/ Registration

in India or a Limited Liability Partnership Firm under Limited Certificate/ Shop & Establishment

Liability Partnership Firm Act 2008 or as a proprietorship firm at the certificate

PQ 2 Legal Entity time of the bidding b) Copy of PAN card

2.3 The bidder should have a registered number of, GST, Income Tax / c) Copy of GST registration

Pan number d) Copy of purchase orders showing

2.4 The bidder should be in operation in India for a period of minimum 3 at least 3 years of operations OR

years. Certified true copy of balance

sheet and P&L statements for last

Financial 3.1 The bidder (whether sole or consortium partners combined) should a) Copy of audited Balance Sheet,

PQ 3 audited Profit & Loss statements

Capability have average annual turnover of at least Rs. 7.5 Cr from

IT/ITES/Telecom projects from last three audited financial years for each of the last 3 financial

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr No Description Minimum Requirement Documentary Proof

ending 31 March 2025, i.e. (FY 2022-23, FY 2023-24 and FY 2024- years as on 31st March

3.2 The bidder must have positive net worth as of the last financial year b) Certificate from the statutory

as on 31 March 2025. auditor / Charted Accountant

3.3 The bidder who wishes to submit the financial capability of on-going (CA) clearly specifying the

FY 2025-26; the last three FY for consideration will FY 2023-24, FY annual turnover for each of the

2024-25 and FY 2025-26. last 3 financial years as on 31st

3.4 In case of consortium -: March 2025. Original or

- The lead bidder and consortium partner together shall meet Notarized Copy should be

the aggregate average annual turnover of Rs. 7.5 Crores from submitted for evaluation.

IT/ITES/Telecom projects in last 3 financial years ending

March 2025, i.e. i.e. (FY 2022-23, FY 2023-24 and FY 2024- c) For on-going financial year, CA

25). certificate is required for FY

- The proportion of the lead bidder and consortium partner 2025-26 at the time of bid

should not be less than 50% and 25%, respectively, of the submission. And the final audited

requirement for average annual turnover in the last 3 financial balance sheet with audited profit

years. & loss statement shall be

submitted when the audit is

Similar Work: In case of Completed project –

The bidder (whether sole or as a consortium) should have experience in Copy of work order/LOI/LOA/ Copy

supply/ installation of camera-based AI analytics and surveillance

of Signed Contract And

systems within the last seven years for a Government entity (ULBs /

State / Central Govt. / PSUs / Govt. SPVs / Reputed Private Entity). Completion/Go-Live/Experience

Bidder’s Certificate from client

Experience - 1 Eligibility shall be met through any one of the following:

a. One project ≥ ₹20 Cr; or In case of ongoing projects -

b. Two projects ≥ ₹13 Cr each; or

c. Three projects ≥ ₹10 Cr each Copy of work order/LOI/LOA And

Copy of Signed Contract and

In case of consortium:

• The Lead Bidder and Consortium Partner(s) may collectively meet the Performance /Go-Live/Experience

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr No Description Minimum Requirement Documentary Proof

experience requirement. Certificate from client And

• Similar work experience with project values may reside with different Certificate from the client mentioning

consortium members and shall be considered jointly. the amount of physical and financial

The Bidder (whether sole or both members of a consortium jointly) progress

should have experience in supplying/installing, or maintaining AI based

video analytics solutions for surveillance projects within last seven

years. These projects must be for government entities such as Urban Bidder to submit the project details as

Local Bodies, State Government, Central Government, PSUs, or per format given in the RFP

Government SPVs or reputed private entity.

To qualify under this criterion, the Bidder (whether sole or both

members of a consortium jointly) must have completed at least four (4)

projects that include video analytics use cases deployed on

Additionally, the Bidder (sole or any one consortium partner) should

have experience in at least five (5) of the following twenty (21) use cases

PQ 5 from multiple projects:

1. Detection of Red-Light Violation (RLVD) with Automatic

Number Plate Recognition (ANPR)

2. Detection of garbage on road

3. Detection of Waterlogging

4. Detection of two-wheelers riding without Helmet

5. Detection of vehicles driving on wrong side.

6. Detection of Potholes, damaged Manhole Cover and Open

7. Detection of Faded Road Markings (Zebra crossing, Road

median, Signages)

8. Detection of C&D Waste

9. Detection of Cattle on road

10. Detection of Electrical Wires Jumble

11. Detection of Damaged Paver, Pavement, Curbs, Curbstones and

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr No Description Minimum Requirement Documentary Proof

Dividers on road

12. Detection of Damaged/Rusted/Tilted Gantry

13. Detection of Broken Street Lights and Traffic Lights

14. Detection of Damaged and Hidden Traffic Signages

15. Detection of broken road edges

16. Detection of Illegal Stalls (Stall detection only)

17. Detection of construction in progress

18. Detection of Person Sleeping on Footpath

19. Detection of Spitting, Red & Yellow Spots on street

20. Detection of Road Crack and Surface Damage

21. Detection of Parking encroachments

The Bidder (whether sole or consortium members jointly), should Copies of valid certificates in the

PQ 6 Certification possess at least two (2) certificates from below mentioned, valid at the name of the bidding entity

time of bidding):

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr No Description Minimum Requirement Documentary Proof

i. ISO 38505 for Data transmission/handling/governance

ii. Cloud Security Alliance (CSA) STAR Certification - Level 2 or

iii. ISO 27701 for establishing, implementing, maintaining, and

improving a Privacy Information Management System (PIMS)

iv. ISO 27001 for Information Security Management System

v. CMMI - Process Level 3 or above

The Bidder (whether sole or lead bidder of consortium), should have at Certificate from HR head confirming

PQ 7 Manpower least 25 technical employees on its payroll at the time of bidding, having compliance.

experience in surveillance project/software design/development

testing/maintenance activities.

i. The bidder should have own or should have assured access to the

required items asked in this RFP document in full working order,

and must demonstrate that, based on known commitments, they

will be available for use in the proposed contract.

ii. OEM Partnership Certificate – SI should submit Authorization Authorization Letter from OEM at

letter from OEM (camera, server, storage, networking, required company’s letter head signed by

software and other items mentioned in BoQ of this RFP). authorized signatory in format

iii. SI should submit a certificate from OEM ensuring technical described in RFP

PQ 8 OEM Partnership support as well as supply of the required product / spares for along with necessary copy of

entire contract duration.

iv. SI should submit a certificate from OEM confirming presence in certificate for Network Service

India either directly or through channel partner(s) as on the date Provider

of release of tender.

v. SI should submit a certificate from OEM confirming compliance

with performance criterion described in this tender.

vi. SI should submit a certificate from OEM confirming not have

been blacklisted by any State / Central Government Department

or Central/State Public Sector.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr No Description Minimum Requirement Documentary Proof

The Bidder (whether sole or both partner of consortium) and OEMs),

10.1 Not have been blacklisted by Central Government / Any State

Government / PSU in India as on the date of bid submission.

10.2 Not be insolvent, in receivership, bankrupt or being wound up, not

have its affairs administered by a court or a judicial officer, not have its Self-declaration duly signed and

PQ 9 Mandatory stamped by the authorized signatory

Undertaking business activities suspended and must not be the subject of legal

proceedings for any of the foregoing reasons. in in format described in RFP.

10.3 Not have their directors and officers convicted of any criminal

offence related to their professional conduct or the making of false

statements or misrepresentations as to their qualifications to enter into a

procurement contract within a period of three years preceding the

commencement of the procurement process or not have been otherwise

Copies of any two of the following:

The Bidder (whether sole or lead bidder of consortium), should have an Property Tax/ Electricity/ Telephone

office in Gujarat Bill/ VAT/ CST Registration / Lease

Bidder’s office or agreement.

should set up offices in Gujarat in 45 days from the award of Work Or

Order Undertaking to open Office in

The Performa for undertaking is

The lead bidder, consortium partner and OEMs are required to submit

PQ enclosed with bid Format in Section

Land Border the undertaking as per the Department of Expenditure, Government of

11 14.17 for Bidder & OEM.

India guidelines on procurement dated 23.07.2020 to confirm that, all the

The lead bidder & consortium partner

quoted product Make under this bid are not from a country which shares

is required to submit the undertaking

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr No Description Minimum Requirement Documentary Proof

a land border with India or, of if from such a country, quoted on non-judicial stamp of Rs 300/- for

product/OEM have been registered with competent authority. all quoted products and for OEM on

their company letter head

i. The age of the project will be counted from the date of the Go-Live/Completion up to the RFP release date.

ii. If the project went live more than 7 years ago as on RFP release date and is currently in the Operation & Maintenance phase, it will be

considered. However, the relevant documents to be submitted to ascertain the claim.

iii. The SI or consortium members may include prior experience of projects where they were part of a consortium or joint venture, provided

these projects meet the similar work definition and project value requirements, supported by client documents.

iv. OEM experience will not be considered for eligibility.

v. The lead bidder and all consortium partners will be jointly and severally responsible for project execution and must individually demonstrate

relevant experience as per the Pre-Qualification criteria.

vi. For ongoing projects, only those with more than 40% physical or financial progress of the awarded work will be considered.

vii. Completed Project means all deliverables are supplied, installed, tested, commissioned, and accepted by the client with a 100% Go-

Live/Completion Certificate.

viii. The Bidder must attach valid documents in support to their Pre-Qualification as mentioned above. Without proper supporting documents,

the bid proposals are liable to be rejected.

ix. For all cited projects under Bidder’s experience criteria; the Bidders shall have to submit work order with complete BoQ, contract

agreement, go-live / completion certificate, proof for O&M as documentary evidence against each of the project.

x. SCADL reserves the right to check/validate the authenticity of the information provided in the bidder’s proposal.

xi. The bidder needs to provide contact detail (email & phone number) of senior official from end client to verify WO / citation details.

xii. SCADL (or the nominated party) reserves the right to check/validate the authenticity of the information provided in the Pre-qualification

and Technical evaluation criteria.

xiii. For all resource CVs provided under manpower details, profiles will only be considered if they are on company payrolls as of the bid

submission date.

xiv. The Bid Evaluation Committee (BEC) may invite each bidder to make a presentation may require written clarifications from the bidders

to clarify ambiguities and uncertainties arising out of the evaluation of the Bid documents.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

xv. The bidder should submit authorization certificate of Original Equipment Manufacturer (OEM) (or multiple OEMs) specific to the bid.

The bidder should have a support agreement/arrangement for services including supply of spare parts etc. which includes the post-sales

support activities for the entire project period.

xvi. The bidder cannot be part of multiple bids. Only an OEM / Product Company can be part of multiple consortiums (if the firm is not

participating as a Lead Bidder), if bidding ONLY as the Solution provider for the respective Product / Solution.

xvii. In case of any change in eligibility criteria during bidding stage, it is bidder’s responsibility (all consortium partners in case of consortium)

to bring any change to Purchaser notice if there is a change in the status of the bidder during bidding stage, with reference to any of the

above-mentioned criteria for eligibility.

xviii. If the project is ongoing and has not completed the implementation phase or has not been declared Go-Live, then in that case the mandatory

minimum components mentioned in the criteria need to be operational and the bidder has to share the completion certificate of the claimed

completed component from the client or proof of payment to confirm the progress of the project.

xix. In case of a consortium, applicant consortia shall have a valid Memorandum of Understanding (MoU) / Consortium Agreement among all

the members signed by the CEO / Country Head /Authorized Signatories of the companies dated prior to the submission of the bid. The

MoU / Consortium Agreement shall clearly state the composition of the consortium who shall be the Lead bidder, the complete description

of the partner and Roles & Responsibilities of the partner. The consortium bid submitted without valid MoU / Consortium Agreement shall

be treated as non-responsive. The contract shall be signed with the Lead Bidder with mentioning name of the consortium partner, and the

Lead Bidder shall be single Point of Contact for this Project. PBG shall be submitted by the Lead Bidder. The payments for the said project

shall be released only in the name of Lead Bidder.

xx. The lead Bidder shall be solely responsible for any failure and liable to the authority for the execution of the entire project / SoW in

accordance with the terms & conditions of the bid document and a statement of this effect shall be included in the MoU / Consortium

Agreement/ Contract.

xxi. In case at any point of time after issue of WO to successful bidder, the details provided are found to misrepresent any facts or documents

or any piece of information provided, then bidder, consortium partner, OEM(s) shall be disqualified and blacklisted. In such situation, the

successful bidder will have to provide the new solution of new OEM as per the requirement of the RFP at no extra price within one month

subject to levy of a penalty of 5% of the total project cost of respective items of BOQ for concerned OEM.

xxii. Bidders are required to submit documentary evidence of their projects, performance, and experience issued by both the contracting client

and the end client to enable assessment of the actual performance of the bidder, consortium partners, and OEMs on this project. During

evaluation, AMC/SCADL may request additional documents from bidders if such evidence is not included in their proposals, and bidders

must submit these within the stipulated timeframe.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

During the evaluation of the Bid, SCADL reserves the right to enquire / seek additional documents / justification to further understand the

Bidder’s submission against various qualification criteria. Such communication shall be at the discretion of SCADL. No claim from any of the

Bidder in this regard shall be entertained for any of the reasons(s) pertaining to the bid evaluation.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

17. Technical Qualification Criteria

Sr. Evaluation Marking Guideline Documentary Proof

New Criteria Max. Marks

The bidder (whether sole or both

partners of a consortium jointly)

should have experience in the

supply/ installation of camera-

based AI analytics and

surveillance systems, in India

over the last seven years for a

government entity (Urban Local • Similar The Bidder -

Bodies, State Government, projects with cumulative In case of Completed project –

Central Government, PSUs, or

values of more than 20 Copy of work order +

Government SPVs or reputed

Cr: 5 Marks Completion Certificates from

private entity).

• Similar client mentioning the values for

functionalities implemented.

Experience of Under this criterion, multiple projects with cumulative

Bidder - I similar projects will be values of: More than 30 In case of ongoing projects -

considered for value aggregation Cr: 10 Marks Work order + Certificate from the

• Similar projects with client mentioning the values for

(All conditions, including the

Cumulative values functionalities implemented +

requirement for supporting

of More Performance certificate of the

documents defined in the PQ

Bidder from the client

table, apply to eligible projects. than 40 Cr: 15 Marks

Bidders must submit a self-

declaration of marks obtained

under this criterion on their

letterhead, along with

documentary evidence issued by

the contracting client clearly

specifying compliance)

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr. Evaluation Marking Guideline Documentary Proof

New Criteria Max. Marks

The bidder (whether sole or both The Bidder -

partners of a consortium jointly) In case of Completed project –

must have experience in camera- Copy of work order +

based AI analytics and Completion Certificates from

surveillance systems within the client mentioning the values for

last seven years. These projects functionalities implemented.

should have been executed for

government entities such as In case of ongoing projects -

Urban Local Bodies, State Work order + Certificate from the

Government, Central • Minimum 5 Use Cases – client mentioning the values for

Government, PSUs, or 6 Marks functionalities implemented +

Government Special Purpose Performance certificate of the

Vehicles (SPVs) or reputed • 6-9 Use Cases – 10 Bidder from the client

private entity.

Marks will be allotted based on • 10-11 Use Cases –

TQ 2 the bidder’s prior experience with

Bidder - II Marks

the maximum number of use

cases from the list below, • 12-14 Use Cases –

demonstrated across multiple

projects. Marks

• 15 or more Use Cases –

1. Detection of Red Light

Violation (RLVD) with 20 Marks

Automatic Number Plate

Recognition (ANPR)

2. Detection of garbage on

3. Detection of Waterlogging

4. Detection of two-wheelers

riding without Helmet

5. Detection of vehicles

driving on wrong side.

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr. Evaluation Marking Guideline Documentary Proof

New Criteria Max. Marks

6. Detection of Potholes,

damaged Manhole Cover

and Open Manhole

7. Detection of Faded Road

Markings (Zebra crossing,

Road median, Signages)

8. Detection of C&D Waste

9. Detection of Cattle on road

10. Detection of Electrical

11. Detection of Damaged

Paver, Pavement, Curbs,

Curbstones and Dividers on

12. Detection of

Damaged/Rusted/Tilted

13. Detection of Broken Street

Lights and Traffic Lights

14. Detection of Damaged and

Hidden Traffic Signages

15. Detection of broken road

16. Detection of Illegal Stalls

(Stall detection only)

17. Detection of construction in

18. Detection of Person

Sleeping on Footpath

19. Detection of Spitting, Red

& Yellow Spots in street

20. Detection of Road Crack

and Surface Damage

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr. Evaluation Marking Guideline Documentary Proof

New Criteria Max. Marks

21. Detection of Parking

The bidder (whether sole or both

partners of a consortium jointly)

should have experience in

supply/ installation/

maintaining dashcam or

In case of Completed project –

LPU/edge analytics in moving

Copy of work order +

vehicle with AI based video

Completion Certificates from

analytics solutions, within the

client mentioning the values for

last seven years. These projects • 1 to 2 Projects – 5 Marks

Bidder’s functionalities implemented.

should have minimum value of • 3 to 4 Projects – 10 Marks

TQ 3 Experience -

Rs. 50 lakhs and should have • 5 or more Projects – 15 In case of ongoing projects -

been executed for government Marks Work order + Certificate from the

entities such as Urban Local

client mentioning the values for

Bodies, State Government Special

functionalities implemented +

Purpose vehicles (SPVs) or

Performance certificate of the

reputed private entity.

Bidder from the client

Marks will be allotted based on

the bidder’s prior experience with

the number of projects executed

OEM for Dashcams

• OEM Partnership Certificate

The bidder must submit an OEM in the format specified in the

partnership certificate in the • 250 to 500 Dashcams – RFP.

OEM format specified in the RFP. 2.5 Marks • LOI/LOA/WO/PO/Contract

Capability - 1 • More than 500 Dashcams Order and Completion

The proposed OEM should have – 5 Marks certificate from the client for

experience in supplying successful completion of the

Dashcams for surveillance order

within the last seven years. These

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr. Evaluation Marking Guideline Documentary Proof

New Criteria Max. Marks

projects should have been

executed for government entities

such as Urban Local Bodies, State

Governments, Central

Government, PSUs, or

Government Special Purpose

Vehicles (SPVs) or reputed

private entity.

Marks will be allotted based on

the OEM’s prior aggregate

experience demonstrated across

multiple projects.

(All conditions, including the

requirement for supporting

documents defined in the PQ

table, apply to eligible projects.

Bidders must submit a self-

declaration of marks obtained

under this criterion on their

letterhead, along with

documentary evidence issued by

the contracting client clearly

specifying compliance)

▪ Submission of MAF

OEM – Technical Capability • Submission of MAF of each

from proposed OEMs as

BoQ components as per RFP

per RFP requirement –

It is mandatory to submit – 5 Marks

TQ 5 compliance of MAF 5 • For each additional relevant

(Manufacturer Authorization functionality as mentioned

(Marks will be deducted

Form) as per RFP format - under the criteria for

proportionately for missing

Dashcams, all the Hardware proposed camera and video

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr. Evaluation Marking Guideline Documentary Proof

New Criteria Max. Marks

components proposed in the analytics over and above RFP

solution. requirement – 1 Mark for

Not Submitting the MAF may

lead to zero marks under this

Bidder is expected to propose

technical solutions and products

which have Maturity and Global

standings / Solutions proposed as

per relevant reports from Gartner

/ IDC (Top 5 / Leader quadrant).

This capability will be evaluated

through the documents submitted

by the bidder and presentation

made to the bid evaluation

As part of bid evaluation, the PQ

qualified bidders need to

undertake a demonstration cum

seven days and night pilot of

Proof of Concept (PoC) &

• For 1st to 10th use cases:

Demonstration of Offered

Proof of 2 Marks for each use

Solution and Products. Live demonstration with required

TQ 6 Concept case

1. Detection of garbage on road •

(POC) For 11th to 21st use cases

2. Detection of Waterlogging

3. Detection of two-wheelers

riding without Helmet

4. Detection of vehicles driving

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr. Evaluation Marking Guideline Documentary Proof

New Criteria Max. Marks

5. Detection of Potholes,

damaged Manhole Cover and

6. Detection of Faded Road

Markings (Zebra crossing,

Road median, Signages)

7. Detection of C&D Waste

8. Detection of Cattle on road

9. Detection of Electrical Wires

10. Detection of Damaged

Paver, Pavement, Curbs,

Curb stones and Dividers on

11. Detection of

Damaged/Rusted/Tilted

12. Detection of Broken Street

Lights and Traffic Lights

13. Detection of Damaged and

Hidden Traffic Signages

14. Detection of broken road

15. Detection of Illegal Stalls

(Stall detection only)

16. Detection of construction in

17. Detection of Person Sleeping

18. Detection of damaged

19. Detection of Road Crack and

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of Municipal Infrastructure. Attempt -

Sr. Evaluation Marking Guideline Documentary Proof

New Criteria Max. Marks

20. Detection of Parking

1. Understanding of Scope

The SI shall prepare a

of Work and Project

presentation on the technical

implementation plan–

proposal to be submitted for this

project. The Bid Evaluation

Committee will evaluate the

Network & data centre -

TQ 7 Presentation 2 Mark 10 Presentation to BEC

The bidder shall prepare a

3. Proposed GUI of the

presentation on the technical

dashboard & Reporting

proposal to be submitted for this

Structure – 2 Marks

project. The Bid Evaluation

4. Demo of delivered

Committee will evaluate the

solutions under

presentation. The presentation

submitted project

should include mentioned points.

experiences - 5 Marks

RFP for Selection of Agency for the SITC of Dashcam along with AI based solution for surveillance of

Municipal Infrastructure. Attempt -

18. On-Field Testing – Proof of Concept

As part of the bid evaluation process the Bid Evaluation Committee (BEC) appointed by

AMC/SCADL shall evaluate the proposed solution of SIs as per the Criteria defined in

following table. The participating SIs will have to submit testing report subject to the scrutiny

by SCADL / AMC officials. The on-site field test shall be carried out for min one (1) day and

submit the report to SCADL / AMC officials to validate the submitted test reports. All

charges for such on-site testing shall have to be borne by the bidder. All bidders will have to

prove that the entire ecosystems of the proposed solution are complying with the mentioned

Technical and Functional specifications as mentioned in the RFP. SCADL reserves the right

to extend the PoC period if satisfactory results are not achieved.

The bidder shall deploy 1 dashcam (exact make and model as proposed in bid) on 1 bus

identified by the Authority. The bidder shall demonstrate a functional cloud dashboard, video

management system, accessible to the Authority throughout the PoC. All PoC costs including

hardware, SIM, cloud, installation, travel, and removal shall be borne entirely by the bidder.

• Hardware Performance - Video quality (day/night/glare), mounting stability, GPS

accuracy, battery backup duration test, SoS button response, build quality

• AI Use Case - Accuracy ANPR accuracy on minimum 50 plates (target 85%+), Pothole

detection on pre-mapped locations (target 80%+), Traffic violation detection precision

(target 75%+), 2 bidder-chosen use cases

• Connectivity and Transmission - 4G/5G upload reliability (target 95%+), store-and-

forward test with deliberate disconnection, GPS tracking at 30-second intervals

• Software and Dashboard - Dashboard usability and page load under 3 seconds, video