A dashboard for MOIL planners that uses satellite and geological data to map manganese reserves, predict production shortfalls, and recommend corrective mining actions.
Ministry of Steel · MOIL Ltd. · Software
Signing in saves it for your whole team, so 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.
Reserve Mapping Module
Combines surface satellite inputs like soil moisture and vegetation index with sub-surface geological data to map manganese reserves.
Shortfall Prediction Engine
Analyses equipment downtime, weather conditions, and blasting delays to forecast potential production shortfalls.
Corrective Action Recommender
Generates actionable recommendations such as adjusting mine schedules, optimizing blasting, or redeploying equipment.
Interactive Planning Dashboard
Displays mapped reserves, predicted shortfall risks, production trends, and recommended actions in a unified interface.
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 combines satellite data like soil moisture and land temperature with geological records. They will assess whether the dashboard successfully predicts shortfall risks from constraints like equipment downtime and provides actionable recommendations like schedule adjustments.
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.
Format and source of MOIL geological and sub-surface survey data?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Historical logs for equipment performance and blasting delays?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Target prediction accuracy or acceptable error threshold?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Preferred satellite data sources or APIs?
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 reserve mapping module. How would you build that?
Decoded from SIH26009 itself: Combines surface satellite inputs like soil moisture and vegetation index with sub-surface geological data to map manganese reserves. The brief asks for it by name.
The brief asks for shortfall prediction engine. How would you build that?
Decoded from SIH26009 itself: Analyses equipment downtime, weather conditions, and blasting delays to forecast potential production shortfalls. The brief asks for it by name.
The brief asks for corrective action recommender. How would you build that?
Decoded from SIH26009 itself: Generates actionable recommendations such as adjusting mine schedules, optimizing blasting, or redeploying equipment. The brief asks for it by name.
The brief asks for interactive planning dashboard. How would you build that?
Decoded from SIH26009 itself: Displays mapped reserves, predicted shortfall risks, production trends, and recommended actions in a unified interface. 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 combines satellite data like soil moisture and land temperature with geological records.
This is the evaluator read for your problem statement, decoded from the brief's own wording.
Show me this working: they will assess whether the dashboard successfully predicts shortfall risks from constraints like equipment downtime and provides actionable recommendations like schedule adjustments.
This is the evaluator read for your problem statement, decoded from the brief's own wording.
Each one is quoted from a gap in the brief, not a guess about your team.
Needs data you may not get
The solution requires internal MOIL data like drilling results, equipment performance, and production records, but no dataset is provided.
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.