A mobile application and testing system that lets dairy farmers assess feed and silage quality, detect contamination, and receive instant advisories offline in rural areas.
Ministry of Fisheries, Animal Husbandry & Dairying · Department of Animal Husbandry & Dairying · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Mobile User Interface
A multilingual mobile application for farmers to view feed analysis results and advisories.
Feed Quality Engine
An AI component to predict nutritional value and detect adulteration or toxins.
Storage Monitoring Module
A system to track silage conditions like pH, moisture, and spoilage indicators.
Offline Data Sync
A local storage and synchronization mechanism to work without active internet in rural areas.
Cloud Dashboard
A cloud platform for monitoring feed quality data and traceability.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
Evaluators will check if the solution provides results within minutes, works offline in rural areas, supports multiple languages, and keeps costs low for farmers.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
Exact hardware specifications for portable testing devices?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Required accuracy thresholds for nutritional prediction?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Specific languages that must be supported?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Acceptable cost limits for farmers?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Each one is quoted from a gap in the brief, not a guess about your team.
No measurable target
The text states the solution should be low cost and fast, but gives no exact numerical targets for cost or accuracy.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
The brief asks for mobile user interface. How would you build that?
Decoded from SIH26111 itself — A multilingual mobile application for farmers to view feed analysis results and advisories. The brief asks for it by name.
The brief asks for feed quality engine. How would you build that?
Decoded from SIH26111 itself — An AI component to predict nutritional value and detect adulteration or toxins. The brief asks for it by name.
The brief asks for storage monitoring module. How would you build that?
Decoded from SIH26111 itself — A system to track silage conditions like pH, moisture, and spoilage indicators. The brief asks for it by name.
The brief asks for offline data sync. How would you build that?
Decoded from SIH26111 itself — A local storage and synchronization mechanism to work without active internet in rural areas. The brief asks for it by name.
The brief asks for cloud dashboard. How would you build that?
Decoded from SIH26111 itself — A cloud platform for monitoring feed quality data and traceability. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: evaluators will check if the solution provides results within minutes, works offline in rural areas, supports multiple languages, and keeps costs low for farmers.
This is the evaluator read for your problem statement, decoded from the brief's own wording.