A lightweight, portable, and ergonomic manually operated hand-spinning system prototype that rural Khadi artisans can use to increase their productivity and income.
Ministry of MSME · Coordination Section · 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.
Hardware Prototype
Design and build a physical manually operated hand-spinning system that is lightweight, portable, and ergonomic.
Comparative Evaluation
Test and compare the new system against existing Charkha systems for yarn quality, productivity, effort, and cost.
Deployment Framework
Prepare a plan for field trials, artisan adoption, and vendor development in the Khadi sector.
Economic Assessment
Conduct a cost-benefit analysis and create a scalability roadmap for large-scale implementation.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check whether the physical prototype is actually lightweight, portable, and ergonomic while improving yarn quality and productivity over existing Charkha systems.
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.
Exact weight limits for portability?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Target cost of manufacturing?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Specific yarn quality metrics like count and strength?
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 hardware prototype. How would you build that?
Decoded from SIH26020 itself: Design and build a physical manually operated hand-spinning system that is lightweight, portable, and ergonomic. The brief asks for it by name.
The brief asks for comparative evaluation. How would you build that?
Decoded from SIH26020 itself: Test and compare the new system against existing Charkha systems for yarn quality, productivity, effort, and cost. The brief asks for it by name.
The brief asks for deployment framework. How would you build that?
Decoded from SIH26020 itself: Prepare a plan for field trials, artisan adoption, and vendor development in the Khadi sector. The brief asks for it by name.
The brief asks for economic assessment. How would you build that?
Decoded from SIH26020 itself: Conduct a cost-benefit analysis and create a scalability roadmap for large-scale implementation. 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 check whether the physical prototype is actually lightweight, portable, and ergonomic while improving yarn quality and productivity over existing Charkha systems.
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.
No measurable target
The description asks for improved productivity, efficiency, and ergonomics without defining numerical targets for them.
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.