A software system that uses real-time data and machine learning to dynamically forecast train arrival times for passengers and railway staff.
Ministry of Railways · 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.
Data Integration Pipeline
Collects live train location feeds, operational parameters, and historical delay records.
Machine Learning Model
Calculates and continuously updates train arrival times using historical and real-time data.
Prediction API
Exposes endpoints for external systems to retrieve up-to-date arrival forecasts.
Control Room Dashboard
Displays live train tracking and delay predictions for internal staff monitoring.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check if your machine learning model actually improves over static schedules using real-time data, and whether your system provides functional APIs for dashboards and displays.
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.
Exact data schemas for train feeds?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Required accuracy threshold for ETA predictions?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Specific cloud or on-premise infrastructure requirements?
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.
Needs data you may not get
The system requires live GPS tracking data, signal aspects, and operational data from Indian Railways which students cannot easily access.
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.
The brief asks for data integration pipeline. How would you build that?
Decoded from SIH26028 itself — Collects live train location feeds, operational parameters, and historical delay records. The brief asks for it by name.
The brief asks for machine learning model. How would you build that?
Decoded from SIH26028 itself — Calculates and continuously updates train arrival times using historical and real-time data. The brief asks for it by name.
The brief asks for prediction api. How would you build that?
Decoded from SIH26028 itself — Exposes endpoints for external systems to retrieve up-to-date arrival forecasts. The brief asks for it by name.
The brief asks for control room dashboard. How would you build that?
Decoded from SIH26028 itself — Displays live train tracking and delay predictions for internal staff monitoring. 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 jury will check if your machine learning model actually improves over static schedules using real-time data, and whether your system provides functional APIs for dashboards and displays.
This is the evaluator read for your problem statement, decoded from the brief's own wording.