Tracks observed motor rotation in Hand and Auto per equipment ID, and says whether the fix is a drive parameter or physical leads — before anyone opens the MCC. Runs entirely offline; the matrix persists in this browser via localStorage.
No equipment added yet.
How the Verdicts Are Derived
The one insight that saves the rework
Physical wiring affects Hand and Auto identically — the same three leads feed the same motor either way. So if rotation differs between Hand and Auto, wiring cannot be the cause: one of the two references is inverted in software (drive parameter, PLC output sign, or a reversed run command). Only when rotation is wrong in both modes is it a lead swap — and then the fix is swapping any two of the three phases at the MCC.
Verdict table
Hand Reverse / Auto Forward → software conflict. Do not touch leads; find the inversion (commonly a drive “reverse enable”/“direction” parameter or an inverted reference).
Hand Forward / Auto Reverse → software conflict on the Auto path (PLC/SCADA reference sign or drive terminal mapping).
Reverse in both → hardware: swap two physical leads at the MCC, then retest both modes.
Forward in both → verified; move on.
Anything Untested → incomplete; no verdict issued on partial data.
Reminder of why it matters: a three-phase centrifugal machine running backward delivers roughly half flow and head and often sounds nearly normal — it gets missed.
Test discipline
Bump-test rotation at low speed with the coupling/drive train ready for it; some machines (screw pumps, some gearboxes) must never run backward even briefly — check the O&M first.
Verify direction against the rotation arrow on the casing, not against what “looks right.”
After any lead swap or parameter change, retest both modes — that's the whole point of the matrix.
References
The drive manufacturer's parameter manual — direction/reference parameters (governing document for the software side).
Motor and driven-equipment O&M — rotation arrow and reverse-rotation restrictions.