An AI-powered web system that helps railway operators automatically plan and schedule maintenance blocks across departments to maximize train asset availability.
Ministry of Railways · 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.
Data Integration Module
Collects maintenance records, defects, and overdue tasks from TMS, SMMS, TDMS, and train corridor data from the Control Office Application.
AI Prioritization Engine
Applies algorithms to rank maintenance tasks by urgency, criticality, and impact on asset availability.
Block Schedule Optimizer
Generates coordinated multi-department maintenance schedules that minimize downtime and fit within train timetables.
Multiple Time Horizon Planner
Outputs both weekly and monthly block plans to support short-term and long-term scheduling needs.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check whether your system successfully integrates data from multiple specified railway systems like TMS, SMMS, and TDMS, and whether it generates optimized weekly and monthly block schedules using AI.
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.
API specifications or sample data formats for TMS, SMMS, TDMS, and Control Office Application?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Specific rules for multi-department coordination conflicts?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Exact output format required for the block schedules?
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 data integration module. How would you build that?
Decoded from SIH26027 itself: Collects maintenance records, defects, and overdue tasks from TMS, SMMS, TDMS, and train corridor data from the Control Office Application. The brief asks for it by name.
The brief asks for ai prioritization engine. How would you build that?
Decoded from SIH26027 itself: Applies algorithms to rank maintenance tasks by urgency, criticality, and impact on asset availability. The brief asks for it by name.
The brief asks for block schedule optimizer. How would you build that?
Decoded from SIH26027 itself: Generates coordinated multi-department maintenance schedules that minimize downtime and fit within train timetables. The brief asks for it by name.
The brief asks for multiple time horizon planner. How would you build that?
Decoded from SIH26027 itself: Outputs both weekly and monthly block plans to support short-term and long-term scheduling needs. 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 whether your system successfully integrates data from multiple specified railway systems like TMS, SMMS, and TDMS, and whether it generates optimized weekly and monthly block schedules using AI.
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 prompt requires integration with internal systems like TMS, SMMS, TDMS, and COA which students cannot 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.