Jig Design #04: Mechanical Poka-Yoke — Blocking Wrong Loading by Geometry Before Reaching for Sensors
A sensor can detect a workpiece loaded the wrong way round. But an asymmetric pin can make a reversed workpiece impossible to fit into the jig in the first place.
That is the spirit of poka-yoke: make the error impossible, or make it obvious right at the source before it turns into a defective product. ASQ defines mistake proofing as a device or method that either makes it impossible for an error to occur, or makes the error immediately obvious once it has occurred.
In jig design, the best solution rarely starts with the PLC. It starts with understanding which errors are possible, then changing the geometry, the sequence or the interface until the wrong action simply has no path.
1. Separate mistake, defect and detection
Three ideas worth keeping apart:
- Mistake: the wrong action, for example loading the workpiece reversed.
- Defect: the non-conforming result, for example a hole drilled on the wrong face.
- Detection: finding the mistake or the defect.
If the system only detects after machining, it reduces escapes but does not prevent the defect from forming. Poka-yoke is stronger when it acts at the source:
- Do not allow reversed loading.
- Do not allow the clamp to close if the part is not properly seated.
- Do not allow the cycle to run when a component is missing.
- Do not allow the part to be removed before a mandatory step is complete.
The aim is not to remove people from the process, but to remove the situations in which a small slip can have a large consequence.
2. Start from the flowchart and the failure modes
Do not think about poka-yoke by looking at the jig in isolation. Draw the flow from picking up the workpiece to handing it to the next operation:
- Identify the model.
- Pick the correct part.
- Load it in the correct orientation.
- Bring the part into contact with every locator.
- Clamp.
- Confirm the conditions.
- Perform the operation.
- Confirm completion.
- Release and remove the part.
- Move it to the correct tray or operation.
At each step, ask:
- What can a person or a robot do wrong here?
- Does that mistake create a defect immediately, or only create the conditions for one?
- Where does the system detect it today?
- Can the cause be removed through geometry or sequence?
- If it cannot be prevented, can it be detected before an irreversible value-adding operation?
ASQ suggests tracing back from the error to its source, then considering elimination, replacement and facilitation before moving on to detection.
3. A hierarchy of solutions: prevent first, warn later
A practical order for jigs:
Level 1 — Remove the opportunity for error
Example: use the same bolt for every position with the same function, eliminating the step of choosing between two nearly identical types.
Level 2 — Allow only the correct action
Example: an asymmetric geometric key so the part can only enter one way.
Level 3 — Block the cycle when conditions are wrong
Example: a sensor confirms all components are present and the PLC refuses to close the main clamp.
Level 4 — Warn clearly
Example: a light and a buzzer signal the wrong model, but a person still has to act.
Level 5 — Instructions or labels
Example: arrows, colours and work instructions.
Labels and colours are useful, but they depend on attention, lighting, language and training. When a simple geometric key will do the job, it is usually the more durable line of defence.
4. Geometric keys against reversed loading
A part that looks symmetric on the outside but is functionally asymmetric is very easy to load backwards.
Ways to create asymmetry:
- One locating pin with a different diameter.
- An asymmetric distance between two pins.
- A round pin combined with a diamond pin in a distinct position.
- A groove or notch that appears on one side only.
- A stepped stop face.
- A pocket outline that only matches in the correct orientation.
- One corner chamfered differently from the other three.
The key has to be "strong" enough that a wrongly oriented part cannot even sit approximately in place. If the wrong part still enters partly and the clamp can force it, the solution may damage the part or the jig.
Test with parts at the tolerance extremes, with burrs and in a worn condition. The margin separating correct from incorrect must be larger than the total variation that can occur.
5. Preventing the wrong model
Two models with similar shapes are a common source of error. Do not rely on a file name, a tray colour or memory.
Mechanical solutions:
- A different pin pattern per model.
- Model change blocks with their own keying.
- A pocket profile that recognizes one unique feature.
- A go/no-go stop that checks a length or a height.
- Connectors or nests that cannot be cross-mated.
- Model change parts held captive so they cannot be fitted in the wrong position.
On a multi-model jig, avoid leaving a "hybrid" setup that can still be assembled. If the jig needs three blocks for model A and three for model B, design it so blocks from different models cannot coexist on the jig, or so the system recognizes the combination.
A model sensor is only worth something when the logic compares it with the production order and locks the cycle. "There is a sensor" whose signal only appears on the HMI is not a complete poka-yoke control.
6. Preventing missing components
A missing washer, O-ring, spring or small insert can be hard to see once the assembly is closed.
Preferred solutions:
- Design the assembly so that a missing component makes the correct height or stroke unreachable.
- Use kitting pockets with one position per component.
- Use a gauge that confirms stack height.
- Use a one-by-one dispensing mechanism.
- Use optical, proximity or load/force-signature sensing where mechanics are not enough.
- Lock the next step until the condition is confirmed.
Do not simply count sensor state changes if one component can trigger the sensor twice. The logic has to be tied to the cycle state, with a clear reset.
7. Confirming the part is fully seated on the locators
A part can be the right model and the right way round and still sit skewed because of a chip or a burr.
Mechanical solutions:
- Relief around supports and at intersecting corners.
- Chip escape grooves.
- Guiding chamfers.
- Inspection windows.
- A pre-clamp that pushes the part onto the datums before the main clamp.
Detection solutions:
- An air check at the datum.
- Distance sensing.
- A mechanical switch in a position that chips cannot easily fool.
- Comparing clamp stroke against a window.
A clamp-stroke sensor does not prove the part is seated. The clamp can close fully with no part present, or when the pad is worn. Measure the state that is genuinely related to the error.
8. Go/no-go built into the jig
A jig feature can both locate and check a minimum condition:
- A pin that only enters if the hole is present and within a positional zone.
- A stop that only lets the clamp close if the length is within range.
- A profile block that detects the wrong part family.
- A stepped gauge that distinguishes two conditions.
But take care:
- A precision locator should not be used as a forced gauge if it wears easily.
- Go/no-go features need control limits and a calibration method.
- Never let the operator increase force to "push it through".
- There must be a way to tell a part defect from a chip or a damaged jig.
If a pin takes an impact every time a wrong part arrives, it is a wear item and has to be designed as replaceable.
9. Facilitation: make the right action easier than the wrong one
Not every poka-yoke needs a hard block. Making the correct action feel more natural also reduces errors:
- A funnel that is generous at the entry and precise at the end.
- A handle on the correct side to suggest the orientation.
- A centre of gravity that lets the part settle into the right attitude.
- Component trays laid out in assembly order.
- Tool positions that follow the work flow.
- A clamp that can only be reached once the part is fully loaded.
Good design does not ask the operator to "be more careful" across thousands of cycles. It uses geometry and sequence to reduce cognitive load.
10. A sensor is only useful when the logic reacts
For every sensor, define:
- What does it measure?
- Is the normal state ON or OFF?
- Which signals are checked before the cycle starts?
- What happens when the sensor does not change state?
- How long is the timeout?
- Can it be bypassed, who is allowed to, and how is the bypass recorded?
- How is the sensor tested during maintenance?
Sensors have their own failure modes:
- A misaligned bracket.
- A broken or short-circuited cable.
- Oil or chip contamination.
- Seeing the background by mistake.
- Sensing the jig instead of the part.
- A signal held over from the previous cycle.
Design the diagnostics so that a lost signal, an implausible signal or a signal that never changes all become visible. A sensor that is "always ON" should not let the machine run indefinitely.
11. Mechanical poka-yoke and safety interlocks are not the same thing
Quality poka-yoke prevents product or process errors. A safety interlock protects people from a hazard.
A pin that prevents reversed loading does not replace:
- Guarding.
- Door interlocks.
- A safety stop circuit.
- Protective devices at pinch points.
- Machine risk assessment.
Conversely, a safety sensor does not necessarily check the correct model or a complete set of components. The two systems can share information in a suitable architecture, but their requirements, integrity levels and validation are different.
12. Design against bypassing
Poka-yoke usually gets bypassed when it:
- Produces too many false alarms.
- Slows the cycle down.
- Is hard to clean.
- Does not support a new model.
- Fails with no spare available.
- Does not explain why the machine stopped.
To reduce bypassing:
- Choose simple, stable solutions.
- Give error messages that name the condition that was not met.
- Design fast but controlled recovery.
- Track fault frequency and downtime.
- Keep replacement parts available.
- Involve operators and maintenance in the review from the start.
If a poka-yoke frequently rejects good parts, the problem is not "undisciplined operators"; the system may simply not be capable enough.
13. Poka-yoke has to survive model changes
When the product changes:
- Does the feature used as the key still exist?
- Can the new model accidentally pass through the old pocket?
- Does the recipe logic map to the right sensors?
- Are the change parts identified?
- Is the validation documentation updated?
- Can old and new models be mixed on the line?
Manage poka-yoke as a design characteristic with a revision. Every ECN affecting shape, dimensions, material or assembly sequence needs an impact assessment against the poka-yoke.
14. Prove the poka-yoke with challenge tests
Do not test only one good part. Prepare a set of challenge samples:
- A part in the correct orientation.
- A reversed part.
- The most similar wrong model.
- Each critical component missing in turn.
- A part not fully seated.
- A blocked sensor or a lost signal.
- A wrongly fitted change part.
- Parts at the tolerance extremes.
For each situation, record:
- Did the system prevent it?
- At what point was it detected?
- What state did the machine go to?
- Did the message support correct recovery?
- Could it be continued by forcing or bypassing?
Challenge tests should be repeated after repairs, sensor replacements, model changes and at an appropriate maintenance interval.
15. Indicators to track after deployment
A good poka-yoke still needs data:
- The number of genuine errors prevented.
- The number of false alarms.
- Escapes.
- Recovery time.
- The number of bypasses.
- Failures and component life.
- Models or shifts with an unusual frequency.
If the number of prevented errors is high, the poka-yoke is protecting the customer while the root cause remains. That data should trigger process improvement, rather than turning the poka-yoke into a permanent patch over a weak design step.
16. A design process for jig poka-yoke
Step 1 — Choose the priority errors
Based on severity, frequency, current detectability and the point at which the defect forms.
Step 2 — Find the source of the error
Identify the action, condition or interface that allows the mistake to happen.
Step 3 — Try elimination first
Delete the step, combine components, or change the product or process design.
Step 4 — Create a geometric key
Make the wrong state impossible to fit or impossible to bring to the working position.
Step 5 — Add detection where needed
Measure a characteristic tied directly to the error, not a weak proxy.
Step 6 — Define the reaction
Blocking, warning, recovery, bypass rights and logging.
Step 7 — Challenge test
Test good parts, wrong parts, tolerance extremes and failures of the poka-yoke itself.
Step 8 — Manage the life cycle
Periodic checking, calibration, wear-part replacement and reassessment on every change.
17. Review checklist
Errors and their sources
- Specific failure modes are described.
- The point where a mistake becomes a defect is identified.
- Priorities reflect risk and the cost of an escape.
Solutions
- Eliminating the step or condition was attempted first.
- Geometry takes priority over colour, labels and warnings.
- The wrong state cannot be forced into the jig.
- Sensors measure a condition directly related to the error.
- Cycle blocking and recovery logic are clearly defined.
Robustness
- Chips, oil, wear, impact and tolerances are accounted for.
- Diagnostics cover stuck sensors and lost signals.
- Change parts and recipes cannot create a hybrid combination.
- Spares and a post-maintenance test method exist.
Validation
- Challenge tests cover correct, reversed, wrong-model and missing-component cases.
- Tolerance extremes and poka-yoke failures were tested.
- Bypassing is controlled and recorded.
- Indicators exist for false alarms, prevented errors and escapes.
Conclusion
The best poka-yoke is the one that makes the wrong action physically unreasonable. A notch, an offset pin or an asymmetric pocket can be more reliable than a whole chain of sensors and logic.
Where mechanics cannot prevent the error completely, detect it at the source and block it before the defect forms. Then challenge test both the real errors and the failure of the poka-yoke itself, and manage it as a characteristic with a life cycle.
Design should not require people to be perfect. It should make an ordinary slip incapable of becoming a defective product.
View all MINATA technical articles