A web and mobile platform connected to low-cost wireless sensors that detects ground movement over underground coal mines and sends early warning alerts.
Ministry of Coal · Coal India Limited · Hardware
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.
Sensor Node Hardware
Build low-cost smart sensor nodes using readily available hardware like Arduino, ESP32, or Raspberry Pi.
Wireless Mesh Network
Connect sensor nodes using a wireless mesh communication network such as LoRa, Zigbee, or Wi-Fi mesh.
AI Anomaly Detection
Implement machine learning models to identify abnormal deformation patterns and predict subsidence zones.
GIS Dashboard
Create an interactive web or mobile dashboard with GIS visualization for live deformation maps and risk zones.
Early Warning Alerts
Configure an automated notification system that sends alerts through SMS, email, or app notifications.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check if your prototype uses low-cost hardware like ESP32 or Arduino, demonstrates wireless mesh communication between nodes, uses AI for anomaly detection, and includes a GIS-based dashboard with automated alerts.
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 historical subsidence datasets for model training?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Specific thresholds for tilt, vibration, and displacement that constitute an emergency?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
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 sensor node hardware. How would you build that?
Decoded from SIH26025 itself — Build low-cost smart sensor nodes using readily available hardware like Arduino, ESP32, or Raspberry Pi. The brief asks for it by name.
Each one is quoted from a gap in the brief, not a guess about your team.
Needs physical hardware
Listed as a hardware problem statement, so a working demo needs physical components you have to source yourself.
No dataset provided
The description depends on real data, and the organisers have not attached a dataset link.
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.
The brief asks for wireless mesh network. How would you build that?
Decoded from SIH26025 itself — Connect sensor nodes using a wireless mesh communication network such as LoRa, Zigbee, or Wi-Fi mesh. The brief asks for it by name.
The brief asks for ai anomaly detection. How would you build that?
Decoded from SIH26025 itself — Implement machine learning models to identify abnormal deformation patterns and predict subsidence zones. The brief asks for it by name.
The brief asks for gis dashboard. How would you build that?
Decoded from SIH26025 itself — Create an interactive web or mobile dashboard with GIS visualization for live deformation maps and risk zones. The brief asks for it by name.
The brief asks for early warning alerts. How would you build that?
Decoded from SIH26025 itself — Configure an automated notification system that sends alerts through SMS, email, or app notifications. 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: the jury will check if your prototype uses low-cost hardware like ESP32 or Arduino, demonstrates wireless mesh communication between nodes, uses AI for anomaly detection, and includes a GIS-based dashboard with automated alerts.
This is the evaluator read for your problem statement, decoded from the brief's own wording.