A web platform that lets managers track expedition planning, cargo, inventory, personnel movement, and emergency responses for polar missions.
Ministry of Earth Sciences (MoES) · National Centre for Polar andOcean Research (NCPOR) · 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.
Expedition Planning Module
A dashboard for scheduling and organizing polar expedition activities.
Cargo Tracking System
A tool to monitor the location and status of cargo shipments.
Inventory Management
A database to keep track of available supplies and equipment.
Personnel Movement Tracker
A feature to log and monitor the travel and location of team members.
Emergency Response System
An interface to log, alert, and manage emergency situations during missions.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
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 expedition planning module. How would you build that?
Decoded from SIH26062 itself — A dashboard for scheduling and organizing polar expedition activities. The brief asks for it by name.
The brief asks for cargo tracking system. How would you build that?
Decoded from SIH26062 itself — A tool to monitor the location and status of cargo shipments. The brief asks for it by name.
The brief asks for inventory management. How would you build that?
Decoded from SIH26062 itself — A database to keep track of available supplies and equipment. The brief asks for it by name.
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 official description is only 144 characters, so we have held back the evaluator read and the risk flags rather than guess at them.
The brief asks for personnel movement tracker. How would you build that?
Decoded from SIH26062 itself — A feature to log and monitor the travel and location of team members. The brief asks for it by name.
The brief asks for emergency response system. How would you build that?
Decoded from SIH26062 itself — An interface to log, alert, and manage emergency situations during missions. 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.