Poka Yoke prevents an error or detects it immediately through product design, device, sequence, or process rule. In maintenance, the strongest control prevents incorrect assembly or makes the deviation evident before the asset returns to service.
The XV-42 Poka Yoke starts from one defined error: the sealing ring accepts reverse assembly and visual inspection may miss it. The solution must prevent, immediately expose, or detect the error before release without creating excessive force, a new hazard, or dependence on perfect attention.
When Poka Yoke in Maintenance is the right tool
Use it when a known error can occur during selection, assembly, connection, measurement, or recording, while the current process relies mainly on memory, attention, or late inspection. Before the first workshop, define the decision object, observed period, technical approver, comparison condition, and official source of record.
A common misuse is renaming training, warnings, or a generic checklist as Poka Yoke, creating an easy-to-bypass control, and failing to test new risk, delay, or failure modes introduced by the device. That behavior generates activity but does not establish changed condition. A method closes only when the decision enters the correct workflow and returns with reviewable evidence.
Minimum inputs before application
- Technical object: equipment, functional location, system, family, or workflow with an unambiguous boundary.
- Condition: expected function, observed deviation, consequence, time, and operating context.
- History: notifications, orders, confirmations, materials, measurements, and technical documents for the period.
- Decision rule: target, scale, hypothesis, internal criterion, or acceptance condition approved before results are known.
- Governance: technical owner, executors, approvers, dependencies, deadline, and authority to reopen the conclusion.
The XV-42 sealing-ring assembly analysis starts by accepting what history does not yet prove. If correct and reverse attempts, force, time, marks, lot, and functional test is missing, the team opens a bounded collection task with a source, owner, and due condition. The gap receives no estimated score or reconstructed narrative; it explicitly limits what Poka Yoke can support.
Maintenance application steps
| Stage | Technical work | Required output | SAP PM handoff |
|---|---|---|---|
| Describe the error | Separate human action, enabling condition, and asset effect. | Error mode and occurrence point. | FMEA and order history bound frequency and consequence. |
| Seek physical prevention | Modify fixture, geometry, connector, packaging, or sequence to accept only the correct condition. | Orientation-fixture prototype. | Physical change follows engineering and change control. |
| Create immediate detection | Where full prevention is impractical, make the deviation visible or block progress before the next stage. | Objective checkpoint. | The order operation requires evidence before final testing. |
| Test the control | Run correct and incorrect attempts and assess ergonomics, time, bypass, and new risks. | Validation report including control failures. | The pilot is identified in the order and does not automatically change the population. |
| Standardize and monitor | Update task list, instruction, kit, training, and exception response, then verify recurrence. | Approved version and D+180 indicator. | PM Run can deliver instruction and record work over SAP PM, but does not design the device. |
Poka Yoke separates reasoning from execution for the XV-42 sealing-ring assembly. Hypotheses and criteria remain in the analysis record. Physical work, inspection, and tests use an order; a new symptom uses a notification; a recurring change reaches a task list or plan only after the proper technical approval.
Complete industrial case: reversed seal-ring assembly on valve XV-42
Every person, asset, duration, quantity, and outcome in the XV-42 sealing-ring assembly is didactic. The values demonstrate a completed Poka Yoke application without representing a PM Run customer, industry reference, regulatory threshold, or performance promise. A plant reusing the structure must replace its scales and criteria.
Across 120 valve-overhaul orders, four required rework because a visually symmetric ring was installed in the wrong orientation. Final inspection did not always detect the deviation before the leak test.
Case baseline
| Data | Didactic value | Interpretation |
|---|---|---|
| Orders reviewed | 120 | Didactic six-month sample |
| Rework from wrong orientation | 4 | Initial rate of 3.3% |
| Additional time per rework | 3.5 h | Removal, cleaning, reassembly, and retest |
| Detection before final assembly | 1 of 4 | Three errors reached testing |
Case target: prevent reversed installation, detect every exception before assembly closure, and complete 180 orders with no recurrence from the same error mode.
The target combines blocked errors, escapes, added time, and test compliance and requires representative lots, suppliers, tools, lighting, and technicians. This construction prevents completed activity from being reported as improvement while the mechanism remains untested. A result outside the reference condition stays inconclusive even after its calendar due date.
Decision produced by the method
Engineering approved a fixture that accepts the ring only in the correct orientation and a visible confirmation mark before closure. The checklist remained evidence but was no longer the primary barrier. The task list now requires the fixture and an exception record when the part does not fit.
The Poka Yoke decision for the XV-42 sealing-ring assembly is to adopt the fixture, retain the functional test, and review design after a supplier change. The record identifies the changed element, what remains, the release owner, and the return condition. Planning schedules it only after material, skill, access, duration, and acceptance are confirmed.
Indicator and verification window
Primary indicator: orientation errors and detected near-errors per 100 orders, supported by cycle time and fixture deviations.
Case calculation: Error rate = confirmed incorrect assemblies ÷ applicable orders × 100. Near-errors are tracked separately so control activation is visible.
Window: bench validation before use, review of the first 20 orders, D+90, and final assessment after 180 orders or six months.
Technical closure of the XV-42 sealing-ring assembly order confirms accepted work, while effectiveness depends on representative lots, suppliers, tools, lighting, and technicians. Review uses blocked errors, escapes, added time, and test compliance and stays open when exposure is insufficient. This state prevents a temporary absence of deviation from becoming proof of control.
Limits and neighboring methods
Limits: Poka Yoke does not replace competence, FMEA, required inspection, or change management. Not every error can be physically prevented. Reject a device that creates force, contamination, or false acceptance.
Neighboring methods: FMEA anticipates the failure mode, Five Whys and RCA investigate events, checklists guide sequence, and 5S organizes resources. Poka Yoke owns prevention or immediate detection of the specific error.
Method selection follows the question raised by the XV-42 sealing-ring assembly. FMEA prioritizes modes, 5S controls location and condition, and Jidoka stops on abnormality. Poka Yoke releases the fixture after it blocks reverse assembly without added force or obstruction of correct work; FMEA and 5S remain linked to mode priority and physical control of the device.
Error mechanism, device requirements, and escape validation
The XV-42 error is insertion of the sealing ring in reverse orientation. The team separates the assembly error, a component defect, and an inspection escape. This distinction determines whether control must prevent insertion, expose orientation, or detect the condition before release.
Physical prevention is preferred. A visual mark helps but can fail under poor light, dirt, or color-perception differences. A removable fixture can be bypassed. A functional test detects later. Each option is evaluated against a specific escape path.
The fixture must accept compliant lots, work with planned tools, avoid unsafe force, and allow correct assembly. Its condition must be inspectable. Supplier or geometry changes trigger requalification rather than silent continuation.
Validation deliberately attempts correct and reverse assembly across technicians, shifts, tools, lighting, and component lots. The record includes blocks, escapes, time, and effort. One successful bench attempt cannot release the control.
| Qualification stage | Correct attempts | Reverse attempts | False blocks | Escapes | Maximum effort | Added time |
|---|---|---|---|---|---|---|
| Bench, nominal condition | 24 of 24 completed | 24 of 24 blocked | 0 | 0 | 48 N against a 55 N internal limit | 18 s median |
| Gloves, reduced lighting, two lots | 12 of 12 completed | 12 of 12 blocked | 0 | 0 | 52 N, within the limit | 24 s median |
| First 20 orders after release | 20 correct final assemblies | 2 initial reverse presentations blocked before insertion | 0 | 0 | 50 N maximum recorded | 21 s median per order |
The two blocks in the first 20 orders are recorded as near-errors, with no completed reverse assembly. The fixture passed controlled release because correct attempts had no false block, every reverse attempt was stopped, effort remained below 55 N, and added time stayed within the 30 s internal limit. Monitoring continues through 180 orders to challenge wear, lot changes, and attempted bypass.
An escape stops the order before equipment release, segregates the component, and returns the instruction to engineering. Near-errors are counted separately because they show control activation and may reveal fixture degradation.
The notification preserves the original deviation; the order installs and tests the fixture; confirmation records the result; the instruction receives approval. PM Run returns evidence to SAP PM but does not design the device or validate ergonomics.
- Can the device be bypassed?
- Does it obstruct correct assembly?
- Did representative lots and technicians pass?
- Does a supplier change trigger requalification?
From approved device to execution standard
The fixture enters the maintenance order as a required resource with inspection and functional test. Its link to causal analysis explains the exact error mechanism it controls.
PM Run Mobility can return result, note, and image to SAP PM. Physical validation remains with engineering. An escape, wear mark, or usability problem opens a notification and pauses rollout.
Audit samples orders across lots and technicians. Error prevention is read with assembly time and force so a local reduction does not hide ergonomic cost.
The fixture receives an owner, inspection frequency, storage location, and damaged-condition route. A device unavailable during urgent work cannot be credited as an effective standard.
Supplier change, drawing revision, or tool substitution triggers requalification. The instruction identifies that trigger so knowledge survives personnel changes.
Additional control questions
Validation includes degradation: wear, dirt, minor damage, and time pressure. The device should fail visibly or prevent continuation. A fixture that silently loses function creates false confidence and increases escape consequence.
The control plan names the inspector, condition record, storage point, and approved contingency. Unqualified improvisation is prohibited. When the device is unavailable, the order follows a validated alternative or remains blocked.
Escape review distinguishes device failure, bypass, wrong component, and missed functional test. Each path leads to a different design or governance response, so all events cannot be grouped as operator error.
Periodic challenge deliberately attempts the wrong orientation under supervision. This confirms that wear or process change has not opened a new route around the prevention mechanism.
Device history includes drawing, revision, compatible supplier, and qualification result. The work instruction identifies the valid version so an obsolete fixture cannot remain in use after geometry changes. Storage and inspection records make availability and condition auditable.
Effectiveness uses both prevented errors and escapes. A high number of blocks may reveal upstream component or instruction problems; zero blocks may mean the error disappeared or the device was not used. Review samples orders and technician feedback before interpreting either result.
The qualification protocol defines sample size, dimensional range, authorized tools, personal protective equipment, lighting, and acceptance before attempts begin. Correct assemblies must remain possible without abnormal force, while reverse attempts must stop before damage. Every escape receives immediate containment and a design review. The team retains representative components and records the limits used during qualification. A later lot near those limits may trigger additional testing even when it is formally within specification. Periodic inspection checks wear surfaces, identification, storage damage, and unauthorized modification. Technicians can report difficulty without being treated as noncompliant, because usability problems often precede bypass. The instruction lists approved contingency when the fixture is unavailable and prohibits unqualified substitutes.
Fixture release includes controlled drawing, physical identification, and the component set used for qualification. The plan distinguishes a correct block, false block, escape, and device damage because each event requires another response. A correct block counts as prevention; a false block examines tolerance; an escape stops release and reopens engineering; damage removes the fixture from service. Sustainment sampling includes urgent orders, where time pressure increases bypass risk. Technicians can report force or difficulty without being treated as the cause. Review seeks degradation before the mechanism again permits reverse orientation, and the instruction names the exact supplier, geometry, or tool changes that trigger requalification.
Technical sources
- ASQ, Mistake Proofing, a primary or neutral reference for the method.
- SAP Help Portal, Maintenance Order.
