Safe and Efficient Operation of Mine Vehicles in Fog and Low-Visibility Conditions in Open Cast Iron Ore Mines.

The receipts 🧾

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

1. Exhibit A

   You cannot reproduce dense fog at haul-road scale, so whatever you show on stage will be a scaled analogue and judges will discount the claim accordingly

2. It gets worse

   Automotive LiDAR and decent thermal cameras cost more than most college project budgets in total, and the cheap thermal modules have resolution too low for obstacle classification at range

3. Still reading?

   No public dataset of fogged mine haul roads exists, so any perception model is trained on synthetic fog applied to clear-weather footage, which is exactly the circular setup that collapses under questioning

4. And the finisher

   Nine candidate technologies including digital twin and full autonomy invites teams to promise a system architecture and deliver one sensor on a breadboard

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 capability genuinely depends on sensors most teams cannot buy — automotive LiDAR and usable-resolution thermal cameras run into lakhs, mining radar more still — and there is no public dataset of fogged haul-road scenes, nor any way for a student team to get onto an active Bailadila haul road to collect one.

• Innovation scope

  5/5

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

  The description lists nine candidate technologies with 'may leverage' and specifies outcomes rather than a solution, so the entire architecture — sensing modality, autonomy level, whether it assists or intervenes — is left completely open to you.

• Clarity

  3/5

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

  The problem context is excellent and quantified down to 3–5 metre visibility and 37 MTPA of affected production, but the deliverable itself is never defined — a menu of technologies and a list of desired outcomes is not a specification, and two teams could build entirely unrelated things and both be responsive.

• Acceptance potential

  2/5

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

  The need is real and the openness is attractive, but the sensors are out of reach, the conditions cannot be reproduced and there is no fog haul-road data to train on, which means most submissions will be a Peltier-cooled toy and a slide deck of what the real system would do.

• Effort

  Heavy

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

  Sensor integration and calibration, perception under degraded visibility, sensor fusion, a V2V link, an in-cab HMI and a control room platform is a large systems-engineering effort, and most of the schedule goes to making unfamiliar hardware talk to each other.

• Demo-ability

  Hard

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

  The defining condition is dense fog on a mine haul road with 100-tonne dumpers, and no fog machine in a corridor with a scaled vehicle reproduces the scattering behaviour, the distances or the stakes — the demo cannot prove the claim it is making.

• 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 50–120 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.

• Innovation scope is genuinely maximal — the statement asks for outcomes, not a design, so an unconventional approach cannot be marked down as non-compliant
• NMDC has quantified the loss precisely, which means the business case writes itself and you never have to argue that the problem matters
• Mining hardware is unfamiliar territory for most teams, so the number of serious entries will be small and a competent submission stands out