Al-Powered Underground Mine Safety, Monitoring and Rescue System.

The receipts 🧾

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

1. Exhibit A

   Radio does not pass through rock, so a robot that works on Wi-Fi in a corridor has not addressed the core deployment constraint — this is the question that ends most submissions in this category and it needs a real answer, tether or relays

2. It gets worse

   Methane atmospheres require intrinsically safe certified instrumentation; an MQ-series sensor on a breadboard is not merely uncalibrated, it is an ignition source in exactly the environment it is meant to enter

3. Still reading?

   You cannot access an underground coal mine, so every environmental claim rests on a corridor analogue and a judge from the mining sector knows exactly how different those are

4. And the finisher

   Locating trapped workers is stated as a capability but never specified — thermal signature, audio, RF beacon and gas-mask transponder are entirely different systems and the statement picks none

The damage report 📉

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

• Feasibility

  2/5

  You have picked a fight with physics, procurement, or both. One of them always wins.

  The blocking problem is communications, not mobility — radio does not penetrate rock, so live telemetry from inside a mine needs a tether, a leaky feeder or self-deploying relays, none of which are trivial; on top of that, gas detection certified for a methane atmosphere is intrinsically safe instrumentation rather than a hobby sensor, and thermal imaging at usable resolution remains expensive.

• Innovation scope

  4/5

  There is something genuinely new here. Do not bury it under another dashboard.

  The statement leaves the platform choice explicitly open between a ground rover and an aerial drone and specifies capabilities rather than architecture, so the locomotion, the communications strategy and the autonomy level are genuinely yours to determine.

• Clarity

  3/5

  Clear enough to start, vague enough to drift. Write the scope down and stop reinterpreting it weekly.

  The capability set is described readably but nothing is quantified — no operating range, no gas thresholds, no endurance requirement, no statement of how communications are expected to work underground, which is the single question the whole design hinges on.

• Acceptance potential

  2/5

  The numbers do not like you. Bring something the numbers cannot see.

  Search-and-rescue robots are a perennial hackathon entry that never survives contact with the actual environment, and here the two hardest requirements — through-rock communications and certified gas sensing in an explosive atmosphere — are precisely the ones every team will quietly substitute with a Wi-Fi link and an MQ-series sensor.

• Effort

  Heavy

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

  A rugged mobile platform, a multi-sensor payload, thermal and low-light imaging, an underground communications chain and a surface control station with mapping is five substantial subsystems, and the communications alone will consume more time than the robot.

• Demo-ability

  Hard

  Near impossible to show working in five minutes, which is roughly five minutes more than you get.

  The defining environment is a collapsed, flooded or gas-filled underground tunnel and no part of that is reproducible — a smoke-filled corridor shows a robot driving in the dark, which is not the same claim, and the trapped-worker detection cannot be evidenced at all.

• 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 450–500 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 explicitly allows either a ground rover or an aerial platform, which is unusual latitude and lets you pick the form factor you can actually build well
• A physical robot is a strong prop in a room full of screens, and teleoperating it through a dark obstacle course is engaging even when it does not prove the underground claim
• Jharkhand as a T3 sponsor with real DGMS-recorded mine incidents means the motivation is concrete and locally verifiable