Design and Development of Innovative Hand-Spinning Equipment for Enhancing Khadi Artisan Productivity and Income

The receipts 🧾

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

1. Exhibit A

   Three of the four required deliverables are documents, not hardware, and a team that ships a beautiful prototype with no comparative evaluation or cost-benefit analysis has answered one quarter of the statement

2. It gets worse

   Yarn quality claims need count, twist per inch and evenness measurement, which requires textile testing equipment your college may not have — arrange lab access before you commit

3. Still reading?

   KVIC has iterated on charkha design for decades including the New Model and solar charkha programmes, so 'why has this not already been done' is a fair and difficult question

4. And the finisher

   No target numbers are given at all, so you are setting your own success criteria and a sceptical judge can simply disagree with your benchmark

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.

  This is mechanical design in wood, bearings, spindles and belts with a bill of materials in the low thousands, no data to source, no model to train, and a reference device that KVIC sells openly for you to benchmark against.

• Innovation scope

  4/5

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

  The statement fixes only that the device stay manually operated and improve on ergonomics, productivity and cost — the entire mechanism, drive arrangement and form factor are yours to invent, which is unusually free for a hardware statement.

• Clarity

  3/5

  Clear enough to start, vague enough to drift. Write the scope down and stop reinterpreting it weekly.

  The objectives and the four required deliverables are clearly stated, but there is not a single target number anywhere — no hanks per hour, no weight ceiling, no cost cap, no yarn count — so you have to define what success means and then argue for your own benchmark.

• Acceptance potential

  4/5

  Strong footing before you have written a line. Try not to waste it.

  Genuinely underrated — mechanical design attracts almost no hackathon teams, the demo is physical and directly comparative, and the theme is filed under Blockchain and Cybersecurity so nobody looking for textiles, MSME or hardware will find it.

• Effort

  Heavy

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

  A fabricated mechanical prototype through several iterations plus three separate written deliverables — comparative evaluation, deployment framework and cost-benefit analysis — means three quarters of what is asked for is study work that hardware teams routinely leave until the last night.

• Demo-ability

  Easy

  Easy to demo — and so is everyone else's. Working is the floor here, not the achievement.

  A physical device producing real yarn beside a real charkha is a directly comparative demo a judge can operate themselves, which is about as strong a demonstration format as exists.

• 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 35–75 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 theme mislabel is extreme — a charkha design problem filed under Blockchain and Cybersecurity will be invisible to every team that browses by theme
• Almost no SIH team picks pure mechanical design, so the competitive field for this statement is likely to be tiny
• A New Model Charkha is purchasable from KVIC outlets, giving you a real baseline to measure against rather than a claimed improvement over an imagined device