A multi-robot simulation and dashboard that lets autonomous mobile robots coordinate paths locally without a central server.
Bharat Electronics 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.
Decentralized Network Stack
Implement a peer-to-peer communication protocol where robots share localization data locally without a central server.
Multi-Agent Path Planning
Implement algorithms for edge hardware to handle dynamic conflict resolution and collision avoidance at narrow intersections.
Task Allocation and Rerouting
Automatically reassign pickup points or change paths when a robot encounters a blocked aisle.
Fleet Dashboard
Create a lightweight monitoring user interface that visualizes the entire fleet's real-time positions and battery status.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will test for zero inter-robot collisions and a minimum 20% reduction in total task completion time compared to traditional stop-and-wait methods.
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.
Specific dimensions or layout of the warehouse environment?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
The exact simulation platform or physics engine to use?
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 decentralized network stack. How would you build that?
Decoded from SIH26123 itself — Implement a peer-to-peer communication protocol where robots share localization data locally without a central server. The brief asks for it by name.
Each one is quoted from a gap in the brief, not a guess about your team.
No specific user named
The description specifies the software modules and simulation requirements but never names the human operator or warehouse worker who uses the dashboard.
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 multi-agent path planning. How would you build that?
Decoded from SIH26123 itself — Implement algorithms for edge hardware to handle dynamic conflict resolution and collision avoidance at narrow intersections. The brief asks for it by name.
The brief asks for task allocation and rerouting. How would you build that?
Decoded from SIH26123 itself — Automatically reassign pickup points or change paths when a robot encounters a blocked aisle. The brief asks for it by name.
The brief asks for fleet dashboard. How would you build that?
Decoded from SIH26123 itself — Create a lightweight monitoring user interface that visualizes the entire fleet's real-time positions and battery status. 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 test for zero inter-robot collisions and a minimum 20% reduction in total task completion time compared to traditional stop-and-wait methods.
This is the evaluator read for your problem statement, decoded from the brief's own wording.