Software System to check compliance of Packaged Commodities under Legal Metrology(Packaged Commodities) Rules, 2011 by scanning products, images and labels.
Ministry of Consumer Affairs, Food & Public Distribution
Good pick. Genuinely. Now sit down, because the judges are going to try anyway — and this is what they will try.
Strong pick. Statutory rules define correctness for you, training data is a supermarket away and any judge can test it with the packet in their hand — just do not dodge the font-size-in-millimetres problem, because that is the only part of this that is actually hard and therefore the only part that distinguishes you. Roughly 120–290 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
Font size is the requirement everyone will skip because it is the only genuinely hard part — converting character height in pixels to millimetres on a curved, glossy, foil packet needs real geometry, and a team that reports every other check but fingers-crosses this one has dodged the interesting problem
It gets worse
The Rules prescribe font size relative to the principal display panel area, so you need the package's real dimensions, which means either a reference object in frame or a declared pack size — decide which and make it part of the workflow
Still reading?
Reflective foil, curved bottles and multilingual labels break scene text detection in ways that flat cardboard test images will never reveal
And the finisher
Declaring a real product non-compliant has legal consequences for a manufacturer, so false positives matter far more than false negatives here and your system should be built to abstain rather than guess
The damage report
Every score this statement earned, and what each one actually costs you.
Feasibility
4/5Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.
Training material is limitless and free — every packaged product in any shop is a sample — and the compliance criteria are not a matter of judgement but a published statutory rule set you can encode exactly, which is a far better position than the usual case of inventing your own definition of correct.
Innovation scope
3/5Mildly interesting. The novelty will not carry the room; the build has to.
What must be checked is fixed by the Rules and the functional requirements are enumerated, but how you solve the genuinely hard part — recovering real-world millimetre font height from a photograph of a curved or crumpled package — is completely undetermined and is where the actual engineering lives.
Clarity
5/5The ask is unambiguous, which quietly removes your favourite excuse.
Fully specified: the mandatory declarations are named, the checks are enumerated including font size and placement, the report formats, repository, role-based access and dashboard are all listed, and the statement links the governing rules so the definition of compliance is external and unambiguous.
Acceptance potential
4/5Strong footing before you have written a line. Try not to waste it.
An underrated gem — unlimited free training data, a statutory definition of correctness that removes all requirement ambiguity, a demo that works on anything a judge produces, and a legal metrology enforcement domain that essentially no team will gravitate toward.
Effort
HeavyHeavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.
Text detection and OCR on curved reflective packaging, a rule engine encoding the 2011 Rules, a metric font-size estimation pipeline, report generation, a searchable repository and an enforcement dashboard is five components, and the font-size geometry alone will absorb more time than the OCR.
Demo-ability
EasyEasy to demo — and so is everyone else's. Working is the floor here, not the achievement.
A judge can hand you an arbitrary product from their own pocket and check your verdict against the packet in their hand, which makes this one of the very few statements where the demo is both instant and independently verifiable.
The demo they will have already seen
Somewhere around 120–290 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.
- Correctness is defined by a published statutory rule set rather than by your judgement, so you cannot be accused of choosing a convenient definition of compliance and the Rules are linked in the statement itself
- Training data is effectively unlimited and free — one trip to a supermarket produces hundreds of labelled samples across every packaging type you will encounter
- The demo works on any product a judge produces, which is a far stronger position than a curated test set you prepared
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.