Automated High-Current Short-Circuit Test System for IEC 60898-1:2015 MCB Compliance.

The receipts 🧾

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

1. Exhibit A

   Generating 10,000 A requires a purpose-built short-circuit laboratory; this is not a budget problem you can engineer around and attempting it improvised is a serious safety hazard

2. It gets worse

   IEC 60898-1:2015 prescribes every parameter, so innovation scope is effectively zero and the panel has nothing to reward beyond execution

3. Still reading?

   The standard itself is a paid BIS or IEC document, so even reading the full specification you are being asked to implement has a cost and access barrier

4. And the finisher

   A scaled low-current mock-up does not demonstrate breaking capacity testing at all, and presenting one as if it did invites the most damaging kind of question

The damage report 📉

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

• Feasibility

  1/5

  You have picked a fight with physics, procurement, or both. One of them always wins.

  A 10,000 A short-circuit test facility does not exist on a college campus and cannot be built on one — the source transformer, the switched impedance banks and the containment are industrial capital equipment costing crores, and generating fault currents of that magnitude without a purpose-built lab is genuinely dangerous rather than merely difficult.

• Innovation scope

  1/5

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

  IEC 60898-1:2015 fixes every test parameter — the current values, the power factors, the test sequences, the tolerances and the pass criteria — so there is no design freedom at all; the standard is the specification and your job would be compliance, not invention.

• Clarity

  5/5

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

  Exceptionally precise — it names the breaker configurations, the current rating range, the peak test current, the impedance module, the measured quantities and the control architecture, leaving nothing about the machine open to interpretation.

• Acceptance potential

  1/5

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

  A genuinely poor pick and worth saying plainly — the core capability is unbuildable and unsafe outside a purpose-built test lab, and the standard removes every trace of innovation freedom, so the best possible submission is a control system attached to equipment that will never exist.

• Effort

  Massive

  A semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.

  A high-current source, automated switched R and XL banks, a universal test station with arc containment, a high-speed data acquisition system, PLC control, an HMI and a compliance reporting layer is a capital equipment build that instrument manufacturers deliver over many months.

• Demo-ability

  Hard

  Near impossible to show working in five minutes, which is roughly five minutes more than you get.

  The defining condition is a 10,000 A fault and it cannot be reproduced at any scale that means anything — a low-current mock-up with the same control logic demonstrates the automation but proves nothing about the test the statement exists to perform.

• 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 65–150 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 standard removes all requirement ambiguity — if you can access the equipment, exactly what to build and to what tolerance is fully defined
• The control, acquisition and automated reporting layer is genuinely buildable at low current and is a legitimate contribution if you are candid that you are demonstrating the automation rather than the test
• Almost no team will attempt this, so a submission from a college with a genuine high-power electrical lab would be close to unopposed