Solar-Powered Smart Mini Cold Storage System for Fresh Vegetables in North Eastern Region (NER)
Ministry of Development of North Eastern Region (MDoNER)
Reasonable choice. The scoreboard liked it. The scoreboard is not the one asking questions on the day.
Worth considering. The physical demo advantage is real and the field is thin, but this device already exists commercially, so your differentiation has to be a specific cost or terrain claim you can defend with numbers, not the cold box itself. Roughly 50–110 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
Ecozen's Ecofrost and similar solar cold rooms are commercially deployed across India already, and 'why is yours better than a product farmers can buy today' is the first question you will get
It gets worse
Component lead times for a compressor, insulation panels and a battery bank can eat weeks, and a team that starts procurement late ships a Styrofoam box with a Peltier chip that barely reaches 15 °C
Still reading?
Thermoelectric cooling is tempting because it is cheap and it will not hold a vegetable-storage setpoint against ambient heat load, which is a failure judges recognise instantly
And the finisher
The description asks for weather resistance, modularity and low maintenance, none of which a bench prototype demonstrates, so have the design answer ready even though you cannot show it
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.
A demonstration-scale chamber with a DC compressor, a 200–300 W panel, a battery and ESP32 instrumentation is genuinely buildable on a student budget, but it is a fabrication project with insulation, refrigeration and power-electronics sizing all needing to be right, and any full-size unit is far beyond both budget and lead time.
Innovation scope
2/5Nothing here is new. Your only edge is execution — and execution is also everyone else's only edge.
The description dictates the energy source, the storage medium, the monitored parameters, the alert conditions and the form factor, and solar cold rooms are an established commercial product category, so you are re-engineering a known device rather than inventing one.
Clarity
4/5The ask is unambiguous, which quietly removes your favourite excuse.
It names the crops, the power architecture, the monitored variables, the three alert conditions and the deployment sites, though it never specifies target temperature bands, capacity in kilograms or a cost ceiling, which are the three numbers that would actually constrain the engineering.
Acceptance potential
3/5Middle of the pack. This statement will not win the room for you — you will have to.
The physical prototype is a real advantage and the hardware category thins the field, but Ecozen, CoolCrop and others already sell exactly this at scale, so you will be asked what your unit does that a deployed commercial product does not.
Effort
HeavyHeavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.
Chamber fabrication, insulation, refrigeration loop, solar and battery sizing, control firmware, sensing, alerting and a display interface is a full hardware build where component lead times, not coding speed, set the schedule.
Demo-ability
EasyEasy to demo — and so is everyone else's. Working is the floor here, not the achievement.
A physical box that is measurably cold, with a live temperature trace and an audible alarm, is one of the few demos a judge can verify with their own hand, and physical props consistently outperform screens on stage.
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 50–110 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.
- You can bring the actual working artifact into the room, which is the single strongest demo asset available at any hackathon and something no software PS can match
- The theme is filed under Smart Vehicles, so teams browsing Agriculture or Clean Energy will not surface this PS at all
- The alert conditions are enumerated in the description, so your firmware requirements are fixed and cannot be criticised as arbitrarily chosen
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.