A web dashboard for drilling engineers that shows nearby wells on a map, searches old reports using AI, and warns about drilling risks.
Oil India Limited · Software
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.
Map Visualization Interface
Displays nearby wells on a geospatial map within a user-defined radius.
Document Extraction Engine
Uses OCR, NLP, and data analytics to extract and structure information from historical reports and PDFs.
Searchable Knowledge Repository
Provides a searchable database of past drilling events, lessons learned, and operational challenges.
Risk Prediction Models
Identifies potential drilling risks like mud losses or stuck pipe based on historical offset well behavior.
Real-Time Alert System
Generates real-time alerts and recommendations when current operations approach depths with known risks.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The evaluators will check whether your platform can successfully ingest unstructured historical reports using OCR and NLP, display spatial well data on a map, and accurately generate predictive risk alerts based on offset well data.
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.
Sample PDF reports or datasets to train the OCR and NLP models?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Specific thresholds or definitions for what constitutes high risk?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Integration protocols for connecting to the existing eRTMAC system?
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.
Each one is quoted from a gap in the brief, not a guess about your team.
No dataset provided
The description depends on real data, and the organisers have not attached a dataset link.
Needs data you may not get
The solution relies on historical well completion reports, daily drilling reports, and internal databases from Oil India Limited that students do not possess.
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.
User Dashboard
Presents information through a user-friendly interface for field and office personnel.
The brief asks for map visualization interface. How would you build that?
Decoded from SIH26121 itself — Displays nearby wells on a geospatial map within a user-defined radius. The brief asks for it by name.
The brief asks for document extraction engine. How would you build that?
Decoded from SIH26121 itself — Uses OCR, NLP, and data analytics to extract and structure information from historical reports and PDFs. The brief asks for it by name.
The brief asks for searchable knowledge repository. How would you build that?
Decoded from SIH26121 itself — Provides a searchable database of past drilling events, lessons learned, and operational challenges. The brief asks for it by name.
The brief asks for risk prediction models. How would you build that?
Decoded from SIH26121 itself — Identifies potential drilling risks like mud losses or stuck pipe based on historical offset well behavior. The brief asks for it by name.
The brief asks for real-time alert system. How would you build that?
Decoded from SIH26121 itself — Generates real-time alerts and recommendations when current operations approach depths with known risks. The brief asks for it by name.
The brief asks for user dashboard. How would you build that?
Decoded from SIH26121 itself — Presents information through a user-friendly interface for field and office personnel. 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 evaluators will check whether your platform can successfully ingest unstructured historical reports using OCR and NLP, display spatial well data on a map, and accurately generate predictive risk alerts based on offset well data.
This is the evaluator read for your problem statement, decoded from the brief's own wording.