Development of an AI-enabled Low Cost Real Time Mine Subsidence Monitoring, Prediction and Early Warning System for Underground Coal Mines in India

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   No dataset of real subsidence deformation signatures exists for you to train on, so the prediction and severity estimation half is learned from tilted sand and must be presented as detection with trending rather than validated forecasting

2. It gets worse

   The description literally contains the author's own note naming 'Wireless Surface Mesh Network for Real Time Subsidence Detection' as the innovation hook, which means every team reads the same intended answer and submissions will converge

3. Still reading?

   Real subsidence develops over months at millimetre scale while your bench test moves centimetres in seconds, so sensor resolution and drift over long deployments are questions your demo cannot address

4. And the finisher

   Node-to-node calibration consistency across ten identical units is tedious and is where uncalibrated meshes produce nonsense deformation fields that look like signal

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  4/5

  Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

  Uniquely among hardware statements this one specifies its own affordable bill of materials — the description names Arduino, ESP32 and Raspberry Pi, and MPU6050 tilt sensors, accelerometers, strain-based crack sensors and LoRa mesh radios together cost a few hundred rupees per node, so a genuine multi-node network is within a student budget.

• Innovation scope

  3/5

  Mildly interesting. The novelty will not carry the room; the build has to.

  The architecture is handed to you in unusual detail — the mesh topology, the sensor types, the hardware platforms and even the intended differentiator are all named — so your originality is confined to the deformation analytics and the node power and packaging design.

• Clarity

  5/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  This reads closer to a design document than a problem statement: it specifies the sensing modalities, the network protocols, the hardware platforms, the four detection targets, the five AI tasks and the full output stack, and even leaves in the author's own note identifying the intended innovation hook.

• Acceptance potential

  4/5

  Strong footing before you have written a line. Try not to waste it.

  An unusual combination — hardware that is actually affordable, a specification precise enough that you cannot misread it, a physically honest demo, and a hardware category that thins the field — with the main drag being that the sponsor has pre-announced the intended innovation so most entries will look alike.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  Multiple sensor nodes to build and calibrate identically, mesh networking firmware with power management, a deformation analytics layer, GIS visualisation, alerting and offline sync is six workstreams, and node-to-node calibration consistency is a slow, unglamorous grind teams underestimate.

• Demo-ability

  Easy

  Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

  Ground tilt is one of the few geotechnical phenomena you can genuinely reproduce on a table — a sand tray with a lowering section produces real deformation that your real sensors really detect, so the demo is honest rather than staged.

• Data

  None supplied

  No 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 65–150 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 statement names the hardware platforms and calls the solution student prototype friendly, which is a rare and explicit signal that the sponsor expects something buildable rather than aspirational
• Per-node cost of a few hundred rupees means you can build eight or ten nodes and demonstrate a genuine mesh rather than two devices calling themselves a network
• Ground tilt is physically reproducible on a bench, so your sensors detect real deformation and the demo does not rely on simulation