A deployable ocean-bottom sensor released from a research vessel that researchers use to detect and map metal-rich seabed deposits.
Ministry of Earth Sciences (MoES) · National Centre for Polar andOcean Research (NCPOR) · Hardware
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.
Deployment Mechanism
A release and retrieval system for dropping the sensor from a research vessel to the ocean floor.
Metal Detection Unit
Sensor hardware capable of identifying seafloor metal deposits like polymetallic nodules and crusts.
Data Recording System
An onboard storage or transmission module that records sensor readings during underwater surveys.
Mapping Interface
Software that processes sensor data to generate maps of seabed mineral deposits.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The evaluators will check if the sensor is low-cost, deployable from a research vessel, and capable of detecting metal-rich seabed deposits like polymetallic nodules or crusts.
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.
What depth the sensor must operate at?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
What specific metal detection technology or frequency to use?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
What constitutes low-cost in monetary terms?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
How the data is retrieved after deployment?
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 deployment mechanism. How would you build that?
Decoded from SIH26064 itself: A release and retrieval system for dropping the sensor from a research vessel to the ocean floor. The brief asks for it by name.
The brief asks for metal detection unit. How would you build that?
Decoded from SIH26064 itself: Sensor hardware capable of identifying seafloor metal deposits like polymetallic nodules and crusts. The brief asks for it by name.
The brief asks for data recording system. How would you build that?
Decoded from SIH26064 itself: An onboard storage or transmission module that records sensor readings during underwater surveys. The brief asks for it by name.
The brief asks for mapping interface. How would you build that?
Decoded from SIH26064 itself: Software that processes sensor data to generate maps of seabed mineral deposits. 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 evaluators will check if the sensor is low-cost, deployable from a research vessel, and capable of detecting metal-rich seabed deposits like polymetallic nodules or crusts.
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 physical hardware
Listed as a hardware problem statement, so a working demo needs physical components you have to source yourself.
Needs data you may not get
The problem requires deep-ocean testing and deployment from a research vessel which students cannot access.
No specific user named
The description only mentions the vessel survey context without naming the specific operator role.
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.