City-Wide AI Engine for Multi-Camera ANPR Trajectory Tracking and Urban Traffic Analytics
Bharat Electronics Limited
Reasonable choice. The scoreboard liked it. The scoreboard is not the one asking questions on the day.
Worth considering. The trajectory view is the memorable part, so build that and the fuzzy plate matching that makes it robust — but be careful about the ninety percent claim, because stating a number invites being tested against it. Roughly 180–410 teams are expected to go here.
The receipts
Every red flag on this statement, in full. These are the four places it bites.
Exhibit A
The description commits you to over ninety percent accuracy across motion blur, weather, angles and damaged plates — quote that figure and a judge will hand you the hardest cases to prove it
It gets worse
There is no real multi-camera network available, so the cross-camera linking is demonstrated on a simulated deployment you constructed yourself
Still reading?
City-wide vehicle tracking is a surveillance capability, and a judge may reasonably ask about access control, retention and misuse — have an answer rather than being surprised
And the finisher
It overlaps the ANPR and tracking portion of SIH26124 from the same organisation, so be ready to explain why a dedicated engine is the better answer
The damage report
Every score this statement earned, and what each one actually costs you.
Feasibility
3/5Buildable. Not comfortably. There is a week in here you have not planned for yet.
Plate detection and recognition have public Indian datasets and strong open models, but the description's stated bar of over ninety percent accuracy across motion blur, poor weather, angled shots and damaged plates is a demanding target, and you have no real multi-camera network so the trajectory half runs on simulated deployments.
Innovation scope
3/5Mildly interesting. The novelty will not carry the room; the build has to.
Plate recognition is a mature commodity task and trajectory linking is straightforward once reads exist, so your creative room is mainly in handling uncertain and partial reads when reconstructing a journey.
Clarity
5/5The ask is unambiguous, which quietly removes your favourite excuse.
The description names three core functionalities, specifies the accuracy threshold and the adverse conditions it must hold under, and enumerates the four expected platform components, leaving the requirement unusually precise.
Acceptance potential
3/5Middle of the pack. This statement will not win the room for you — you will have to.
The trajectory reconstruction is genuinely valuable and demos beautifully, but you have committed to a stated ninety percent accuracy figure that a BEL judge will ask you to evidence on hard cases, and without a real camera network the cross-camera half is demonstrated on a deployment you invented.
Effort
MassiveA semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.
A robust recognition engine, a cross-camera linking system and a full analytics layer are three substantial builds, and reaching the stated accuracy on degraded plates alone consumes serious time.
Demo-ability
EasyEasy to demo — and so is everyone else's. Working is the floor here, not the achievement.
Watching a vehicle's journey assemble itself across a city map from scattered camera reads is immediately compelling and needs no explanation.
Data
None suppliedNo dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.
Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.
The demo they will have already seen
Somewhere around 180–410 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.
What survives
The ground worth standing on when the questions start.
- The trajectory reconstruction across a map is a strong, distinctive visual that separates this from the many plain plate-reader submissions
- Fuzzy matching on partial or misread plate strings is a real technical contribution that makes trajectories robust where exact matching would fail
- The accuracy bar is stated, so you have a defined target and a clear structure for your evaluation section
Nothing here is fatal. It is just the list of places this statement pushes back, and you now get to push there first.
The framing is a joke. The findings are not — they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.