A web and mobile platform for field officials and authorities to monitor North East logistics, track essential supply vehicles, predict route disruptions, and receive offline-capable alerts.
Ministry of Development of North Eastern Region (MDoNER) · 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.
AI Route Prediction Engine
Predicts route disruptions like landslides or floods using weather data and suggests alternate routes with estimated delays.
GIS Accessibility Dashboard
Visualizes district connectivity status, supply chain bottlenecks, disaster routes, and vehicle movement on interactive maps.
GPS Vehicle Tracking System
Tracks vehicles transporting essential goods in real time and updates delivery progress across remote corridors.
Field Reporting Mobile App
Allows local authorities to upload geo-tagged incident reports, road updates, and photos with offline data synchronization.
Multilingual Alert System
Generates automated notifications for blocked roads, high-risk corridors, and delivery delays in multiple regional languages.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check for AI-driven route prediction and alternate route suggestions based on weather and terrain disruptions. They will also test GIS dashboard mapping, GPS tracking integration, and field reporting with offline data synchronization for low-network areas. Multilingual notification capability is also explicitly required.
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.
Which specific weather APIs or transport databases to integrate with?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Which local languages must be supported for multilingual notifications?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
The target prediction accuracy metric for route disruptions?
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 ai route prediction engine. How would you build that?
Decoded from SIH26002 itself: Predicts route disruptions like landslides or floods using weather data and suggests alternate routes with estimated delays. The brief asks for it by name.
The brief asks for gis accessibility dashboard. How would you build that?
Decoded from SIH26002 itself: Visualizes district connectivity status, supply chain bottlenecks, disaster routes, and vehicle movement on interactive maps. The brief asks for it by name.
The brief asks for gps vehicle tracking system. How would you build that?
Decoded from SIH26002 itself: Tracks vehicles transporting essential goods in real time and updates delivery progress across remote corridors. The brief asks for it by name.
The brief asks for field reporting mobile app. How would you build that?
Decoded from SIH26002 itself: Allows local authorities to upload geo-tagged incident reports, road updates, and photos with offline data synchronization. The brief asks for it by name.
The brief asks for multilingual alert system. How would you build that?
Decoded from SIH26002 itself: Generates automated notifications for blocked roads, high-risk corridors, and delivery delays in multiple regional languages. 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 for AI-driven route prediction and alternate route suggestions based on weather and terrain disruptions.
This is the evaluator read for your problem statement, decoded from the brief's own wording.
Show me this working: they will also test GIS dashboard mapping, GPS tracking integration, and field reporting with offline data synchronization for low-network areas.
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.
No measurable target
The description requires AI-based disruption prediction and delay estimation but specifies no measurable target accuracy or performance benchmark.
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.