Automated Cable Specimen Preparation System for IS 10810 and IS 7098 Compliance.

The receipts 🧾

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

1. Exhibit A

   IS 10810 and IS 7098 are paid BIS documents, so obtaining the exact dimensional tolerances you are being asked to meet has a cost and access barrier — sort this out before you start

2. It gets worse

   Innovation scope is close to zero because the standard fixes the output and the description fixes the mechanism, so a panel looking for novelty will find execution quality and nothing else

3. Still reading?

   Cutting depth precision on PVC and XLPE without deforming the insulation is genuinely difficult, and a 3D-printed blade carriage will flex enough to miss the tolerance the whole machine exists to hit

4. And the finisher

   The machine must handle multiple cable types and diameters automatically, so demonstrating on one cable size answers a much easier problem than the one stated

The damage report 📉

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

• Feasibility

  3/5

  Buildable. Not comfortably. There is a week in here you have not planned for yet.

  A demonstrator with stepper-driven rollers, clamps, a blade carriage and an optical diameter sensor is genuinely buildable for tens of thousands of rupees, but hitting the dimensional tolerances that IS 10810 actually demands for insulation thickness and dumbbell specimens with student-fabricated mechanics is much harder than making the mechanism move, and the standards themselves sit behind BIS paywalls.

• Innovation scope

  2/5

  Nothing here is new. Your only edge is execution — and execution is also everyone else's only edge.

  The machine architecture is dictated module by module — roller feed, adjustable clamps, programmable-depth blades, diameter sensor, PLC and HMI, automated ejection — and the output geometry is fixed by the Indian Standards, so almost every design decision has already been made for you.

• Clarity

  5/5

  The ask is unambiguous, which quietly removes your favourite excuse.

  Every module is named with its function, the standards and their relevant parts are cited, the existing manual process is described step by step, and the safety requirements are stated, so there is essentially nothing to interpret.

• Acceptance potential

  3/5

  Middle of the pack. This statement will not win the room for you — you will have to.

  A physical machine with a claim a judge can measure in the room and a field almost nobody will enter are real advantages, but the standard prescribes the entire output and the description prescribes the mechanism, so there is very little for a panel to reward beyond precise execution.

• Effort

  Heavy

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

  A precision mechanical build with a feed mechanism, a blade carriage with programmable depth, a sensing loop, ejection and waste handling, plus PLC control and an HMI, is a full mechatronics project where fabrication tolerance rather than code will set your schedule.

• Demo-ability

  Easy

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

  Almost uniquely on this portal, a judge can verify your claim on the spot — put a caliper on the specimen your machine just made and check it against the dimension the standard requires, which is far stronger than any dashboard.

• 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 50–120 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 judge can measure your output with a caliper against a published standard dimension, which turns your claim into a verifiable fact rather than an assertion — very few statements allow this
• The published standards remove requirement ambiguity entirely, so no time is lost deciding what correct means
• Test lab automation attracts almost no hackathon entries, so a working machine has very little to compete against