Skip to content
SIH Buddyby Ganeev Singh
Dev

🔥 Roast My Pick · SIH26062

Integrated Polar Expedition Logistics and Asset Management System

Ministry of Earth Sciences (MoES)

Brutal72/100

Bold. Let us find out precisely how bold, in the order a panel will find out.

Proceed with caution. An exciting setting wrapped around ordinary inventory software with no data behind it — if you take it, make the stowage sequencing and depletion-against-resupply forecasting genuinely clever, because otherwise this is a CRUD portal with penguins on the login page. Roughly 70–170 teams are expected to go here.

The receipts

Every red flag on this statement, in full. These are the four places it bites.

  1. Exhibit A

    Logistics and inventory portals are among the most repeatedly built projects at hackathons, and the shape will be immediately familiar to any panel

  2. It gets worse

    Five domains with no priority in a 144-character statement means every team defines a different scope and most will ship five thin modules

  3. Still reading?

    No expedition data is public, so every consignment, consumption rate and personnel record is invented, and depletion forecasts over made-up consumption prove nothing

  4. And the finisher

    There is no visible moment in this product — without the depletion projection staged carefully, the demo is a tour of CRUD screens

The damage report

Every score this statement earned, and what each one actually costs you.

  • Feasibility

    4/5

    Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

    Nothing here requires data or hardware — planning, tracking, inventory and personnel records are ordinary application work — and the resupply cycle and station operations are documented publicly enough to make the domain model plausible rather than invented.

  • Innovation scope

    5/5

    There is something genuinely new here. Do not bury it under another dashboard.

    At 144 characters the statement names five domains and stops, prescribing no architecture, no workflow, no data model and no interface, so the entire product definition is yours.

  • Clarity

    1/5

    Nobody is sure what is being asked, quite possibly including the people who asked it.

    One sentence listing five functional areas with no artifact, no user, no data, no scale and no success criterion — the shortest specification for the broadest scope anywhere in this range.

  • Acceptance potential

    2/5

    The numbers do not like you. Bring something the numbers cannot see.

    This is an inventory and logistics portal, one of the most frequently submitted shapes at any hackathon, with no data behind it and five equally weighted domains that guarantee shallow coverage — the Antarctic setting is interesting but the software underneath is not.

  • Effort

    Heavy

    Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

    Five domains — planning, cargo, inventory, personnel, emergency — each with its own data model and screens is a wide surface area, and there is no natural core because the statement names all five as equals.

  • Demo-ability

    Medium

    Demoable, if you rehearse it. Nobody rehearses it.

    The indent-to-inventory chain is followable and the depletion projection is a decent moment, but the product is forms and tables and there is nothing here a judge experiences rather than reads.

  • Data

    None supplied

    No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

    Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen

Somewhere around 70–170 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives

The ground worth standing on when the questions start.

  • The once-a-year resupply constraint is what makes this different from ordinary inventory software — depletion forecasting against a hard deadline with no possibility of an emergency order is a genuine and specific problem
  • Zero data, hardware or model risk means a team will certainly finish something working
  • The Toys and Games theme label means anyone browsing logistics or operations themes will not see this statement

None of that means do not pick it. It means do not walk into that room having heard any of this for the first time from a judge.

Full analysis ↗Roast another

The framing is a joke. The findings are not — they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.