A manufacturing rework instruction system should do more than turn a paper traveler into a screen. It must connect nonconformity identification, containment, approval of a controlled instruction, execution evidence, reinspection, and quality release to the same product, lot, or serial number. This guide helps teams evaluating a system for a Thai plant or a multi-site operation define requirements and divide responsibilities among MES, QMS, and ERP.
Define rework before choosing software
The terminology matters. ISO 9000:2026 defines nonconformity as non-fulfilment of a requirement and rework as action on a nonconforming product or service to make it conform to requirements. It distinguishes repair, which makes an item acceptable for its intended use but does not necessarily restore conformity to the original requirements. A concession permits use or release of an item that does not conform to specified requirements. Corrective action addresses causes to prevent recurrence; it is distinct from fixing the affected item.
Keep rework, repair, sorting, scrap, and concession as separate dispositions in the application. Record the disposition, decision maker, applicable specification revision, affected units, and inspection requirement. The standard does not prescribe this particular software architecture. The point is to make the organization’s approved quality process executable and auditable. Our general work-instruction guide addresses routine instructions; here the focus is on exceptional units and the authority to return them to production.
The gaps between a defect record and a released product
A failed inspection may be recorded in one sheet while a hold tag is attached to the part and a supervisor receives a message. ERP might still show available inventory, and MES might still allow the next operation. In another case, quality approves a disposition but the technician opens an obsolete drawing. A third gap appears when reinspection results are filed without a link to the original nonconformity. These failures cannot be solved by faster data entry alone.
Prioritize three gates: hold the physical item and its digital record together; display only an approved instruction for the identified unit; require reinspection and quality release before normal flow resumes. At hold creation, define what blocks MES progression and ERP allocation. At the station, scan the unit and compare it with the instruction scope. Equipment interlocks depend on the machine, controls, and safety design; a tablet warning alone should not be described as a guaranteed physical stop. The quality-hold management guide examines containment. This article follows the additional work and decisions needed to lift a hold.
Design a six-state workflow
Define the states before configuring screens: nonconformity decision, hold, disposition approval, rework in progress, awaiting reinspection, and quality release or further disposition. A state controls allowed actions, not just the label shown to a user. An unapproved proposal is a draft, not a shop-floor instruction. A reworked unit is not automatically cleared for downstream production.
| State | Accountable role | Minimum evidence | Exit condition |
|---|---|---|---|
| Nonconformity | Inspection and quality | Unit ID, measured value, criterion, time | Define affected scope |
| Hold | Quality and stores | Reason, quantity, location, affected IDs | Choose disposition |
| Approved disposition | Authorized quality and engineering | Instruction revision, specification, risk, approval | Release controlled instruction |
| Rework in progress | Authorized operator | Person, time, materials, machine, actual values | Complete defined operations |
| Awaiting reinspection | Independent inspection | Method, criterion, result, inspector | Accept or return for disposition |
| Quality release | Authorized quality owner | Approval, time, precise scope, shipping status | Update MES and ERP |
Define reverse transitions as well. A failed reinspection returns the unit to hold and creates another disposition attempt without overwriting the first. If a drawing changes mid-job, decide explicitly whether a unit already started under the old revision may continue or must stop and receive a newly approved instruction. A date-based revision switch alone cannot explain what happened to work in process. Emergency paper procedures also need a deadline and authorization for later entry.
From failed inspection to a correctly scoped hold
Do not assume that one failed measurement always affects one serial number. The affected scope may include a lot, consecutive output since the last known good check, parts sharing a material batch, or an entire setup. Review detection point, last good result, material lots, tool and fixture, machine, and production window. A system can suggest candidates, but it should retain the reason and person behind the final scope decision.
A held unit may already have moved to another store, been allocated to an order, or been sent to a subcontractor. The user therefore needs movement history and current location, not only an ID. If identification ends at lot level, the organization cannot later prove serial-level rework. Specify in the RFP the actual granularity supported by current barcodes, data-matrix codes, containers, and labels.
From approval to controlled execution
A rework instruction should identify the product and applicable drawing, steps, tools, replacement materials, tolerances, prohibited actions, visual aids, and post-work checks. Freeze the approved revision; require the operator to scan the unit and open only the currently applicable version. An unrestricted edit after approval destroys the ability to reconstruct the instruction used. A revision should record its reason, affected units, and treatment of work already completed under an earlier version.
An operator who encounters unexpected damage must be able to stop and request a new decision instead of clicking Complete. A convenient comment box must not silently transfer disposition authority to the station. For plants with unstable networks, choose by quality risk whether an approved instruction can be cached and evidence queued offline or whether work must stop. Test what happens when a cached revision becomes obsolete.
From reinspection to release
Separate completion of physical work from the decision that the item conforms. Reinspection evidence should include method, equipment and calibration status where applicable, measured value, criterion, inspector, time, unit ID, and instruction revision. For destructive or sample-based testing, retain both sample and population IDs. If reinspection fails, add a second attempt under the same nonconformity history rather than erasing the first.
A passing test is not necessarily a quality release. An authorized person may also have to review other open holds, customer approvals, inventory status, and shipping documentation according to the organization’s procedure. State whether release covers one serial, container, or lot, and notify MES and ERP with the same identifier. Record the approver’s role and delegated authority when headquarters and the Thai plant use different approval structures.
Model the instruction as linked events and versions
Define product or lot ID, nonconformity ID, hold ID, disposition ID, instruction-revision ID, execution ID, reinspection ID, and release ID. The model should support several units under one nonconformity and several attempts on one unit. Searching by lot and date is insufficient when the same unit is reworked again that day. Preserve previous values, author, time, approval, version, and affected ID instead of storing only the current status. Use timestamps with time-zone information when decisions cross Thailand and Japan. Specific electronic-signature and retention obligations depend on contracts, sector rules, and company procedures; set them for the actual operation rather than claiming a universal requirement.
The GS1 Global Traceability Standard provides a framework of Critical Tracking Events (CTEs) and Key Data Elements (KDEs). Applied as an engineering method, hold, rework, reinspection, and release become events whose object, place, time, actor, and result need defined data fields. GS1 does not itself supply a plant’s rework approval workflow. It helps the team document identifiers and event data consistently.
Keep master data and transaction history distinct
Item definitions, routes, equipment, inspection characteristics, and qualifications are master data. A hold, instruction approval, operation, measurement, and release are transactions. A template may be master data, but the approved unit-specific instruction must retain the revision applied at execution. A link to a drawing that can be replaced without a revision record is insufficient; record document ID and version, and consider a controlled snapshot or integrity check.
At multilingual plants, structure step IDs, tolerances, and prohibitions as language-neutral data. Maintain reviewed Japanese, English, Thai, or other display text against the same approved steps. If one translation remains unapproved, block execution in that language. Pictures reduce reading burden but should not be the sole carrier of units, torque direction, or safety-critical prohibitions.
Divide ownership among MES, QMS, and ERP
One common architecture makes QMS authoritative for nonconformity, disposition approval, and quality release; MES authoritative for dispatch and execution; and ERP authoritative for inventory, cost, and order allocation. Existing systems may justify a different assignment. Decide one writer for each state and the direction in which the update is propagated.
| Event | Possible origin | Receiver and action | Failure behavior to test |
|---|---|---|---|
| Nonconformity and hold | QMS or MES | MES blocks next step; ERP restricts stock | Physical item stays held if notification fails |
| Approved instruction revision | QMS | MES shows unit-specific instruction | Invalidate old cache |
| Rework start and finish | MES | QMS receives evidence | Suppress duplicate event ID |
| Reinspection result | QMS or inspection system | MES receives retry or release-pending state | Reject pass without required readings |
| Quality release | QMS | MES resumes route; ERP lifts restriction | Detect and retry partial updates |
The OPC Foundation’s OPC UA ISA-95 common object model describes exchange of material, equipment, physical assets, personnel, and roles across enterprise and manufacturing operations. It can guide data naming and granularity, but does not define your disposition authority. The OPC UA for Machine Tools use cases address job parts, time, and machine state. Such equipment data can corroborate when and where work occurred; it cannot by itself prove that a disposition was approved or a quality hold may be lifted.
Set reconciliation rules before choosing an interface
Before debating API versus file transfer, map ERP item and lot IDs to MES serials and operations and QMS nonconformity IDs. Retain parent-child relationships when lots are split or merged. For outsourced work, define how location, execution responsibility, and inspection responsibility change. A repeated quality-release message after a network outage must not move stock twice; process it idempotently by event ID. Run reconciliation to detect QMS showing released while ERP remains held, and give authorized staff a repair path. Any exceptional manual release needs a reason and later review.
Write failure scenarios into the RFP
ISO’s explanation of ISO 9001 lists documented information, monitoring and measurement, performance evaluation, and improvement among QMS elements. An RFP should ask how instruction revisions and measurement results feed evaluation. The official description of ASQ’s manufacturing ISO 9001 guide says it addresses what is required, why, implementation tips, and questions to assess conformity. Turn those prompts into vendor questions for your own disposition process.
A checklist saying “electronic traveler,” “barcode,” and “MES integration” does not show how a supplier handles a real exception. Supply a sample nonconformity and ask vendors to demonstrate its entire path. Compare license, device, machine connectivity, integration, localization, migration, and support costs separately. Ask which site-specific dispositions and approval rules are configurable and which require custom development.
Core requirements include unit and lot identification, workflow and inventory hold, disposition approval, frozen instruction revisions, qualification checks, actual materials and machine data, numeric reinspection, controlled release, repeated disposition, audit history, retry, and reconciliation. Test gloved use, connectivity loss, photo evidence, available languages, and screen responsiveness on the target shop floor. Derive response targets from actual concurrency and the plant network rather than copying unsupported benchmark numbers.
FAT and SAT acceptance scenarios
Factory Acceptance Testing (FAT) checks configured screens, transitions, rights, and interfaces in the supplier environment. Site Acceptance Testing (SAT) checks the same scenario IDs on actual devices, barcodes, networks, machines, and connected systems at the plant. State expected system status, evidence, and notification for each test so a pass is observable.
| Scenario | Expected outcome |
|---|---|
| Scan a held unit at a normal station | Block start and show hold reason |
| Open an unapproved or old instruction | Refuse start and show approved revision |
| Try to record work against another unit | Detect ID mismatch |
| Fail reinspection after completed rework | Return to hold with another attempt ID |
| Pass reinspection without release approval | Keep MES and ERP restrictions |
| Lose and retry a release message | Reconcile state; avoid duplicate update |
| Use unapproved translation or stale offline cache | Block except under defined contingency procedure |
Add scenarios for the product’s own safety and customer requirements. Demand a demonstration of partial failure between systems, not only the smooth path.
Reconcile legacy rework tickets before migration
Define the migration population by physical items whose disposition, reinspection, or release remains open at cutover, rather than by the total count of historical tickets. Quality should list open paper and spreadsheet records, while stores and production verify the actual location, quantity, and label of each item. If ERP held stock, MES progression, and QMS nonconformity records disagree, classify each discrepancy before loading data. Copying the same unverified value into all three systems can make an incorrect state appear reconciled.
For every open ticket, capture the source ticket number, product and lot or serial ID, hold start time, current location, disposition, approved instruction revision, work already performed, inspections still due, and authorized release owner. Return illegible handwritten entries or unidentified units to a quality owner as exceptions; do not fill gaps by guesswork. An item already reworked but awaiting reinspection must not reappear as “not started.” Map old states to new ones and preserve the reason and person behind each conversion.
In a migration rehearsal, reconcile counts of physical items, held stock, and unfinished dispositions as well as ticket records. Deliberately include units with several tickets, split lots, outsourced work, and instructions awaiting revision approval. Set a temporary input freeze at cutover and record later changes as a delta. If release status is inconsistent after migration, do not assume the unit can ship; route it to the designated quality authority.
Acceptance tests for changing instruction revisions and inspection criteria
Beyond the basic “old revision cannot be opened” test, reproduce an in-progress revision change in both FAT and SAT. If a new tolerance is issued after some steps were done under the old instruction, determine whether the application stops work or requires a documented approval to move to the new version. Preserve completed work under the old revision and link the reason and time of transition. Test whether a stale offline completion may be accepted when the device reconnects.
For reinspection, test boundary values: a value exactly at the limit, a value entered in the wrong unit, an instrument past its calibration due date, and a missing required characteristic. Observe both the pass/fail engine and approval screen. If the system converts units, retain original and converted values; if a value is corrected manually, show the before and after values and reason. Product-specific rules vary, so include anonymized real inspection characteristics and decision logic in the RFP.
Release tests should include a unit that passes reinspection but has another open hold, a lot of which only some units pass, and a unit released in QMS whose ERP notification is delayed. The expected outcome is not a blanket release. State the exact units to release, those still blocked, and the final MES and ERP status for each case. Check allocation and shipping screens after a partial release to verify the full operational control chain.
Pilot one product family and measure the right things
Start with a product family where rework occurs often enough to learn but methods can be standardized. Map the real process with quality, production, engineering, IT, and stores. Inspect actual paper sheets and spreadsheets, including where oral approval or ID re-entry occurs. Hidden exceptions will reappear outside the application after go-live if they are omitted from the design.
Useful pilot measures include accuracy of hold scope, use of approved instructions, linkage between work and reinspection, synchronization of release state, and traceability of repeated attempts. Compare before and after periods only when product mix and inspection rules are comparable. Do not claim a measured defect reduction based solely on two unlike periods. Define time and cost measures before collecting them; the most direct early benefit is often completeness and visibility of the process record.
Before cutover, migrate open holds and have quality reconcile every still-held unit. Historic paper forms may remain archived, but unresolved items cannot be omitted. State whether paper or the application is authoritative during parallel operation, and document contingency recording and shift-level responsibility.
Common design failures
A single Complete-and-Release button collapses work and quality authority. A PDF attachment without structured unit ID, revision, approval, and readings cannot drive control or reliable search. Omitting replacement-material lots breaks later scope analysis. Keeping reinspection criteria only in prose prevents a separate inspector from applying a controlled criterion and recording the measured result. Treating an HTTP acknowledgement as a completed inventory update ignores downstream processing failures. Launching Thai instructions before technical review may alter tool names, tolerances, or prohibited actions. Each issue should become an RFP requirement and an acceptance scenario.
Build a credible business case
Include devices, labels, connectivity, integrations, approval design, localization, training, and support alongside license fees. Measure present time spent re-entering data, locating held goods, recovering work tickets, finding audit evidence, and resolving unauthorized flow. Evaluate hard-to-price quality risk separately. Any payback calculation should show assumptions for case volume, product scope, and improvement rate in low, expected, and high scenarios. An MES extension may fit a small single-plant operation; a QMS-led design may fit a multi-site approval structure. Choose by decision ownership, ability to block work, and inventory release control, not a vendor label.
FAQ: digital rework instructions and reinspection history
Can we eliminate paper as soon as we digitize the rework ticket?
Only after identification, approval, execution, reinspection, release, and outage procedures work end to end. Check any contractual or internal retention requirements. A PDF alone cannot stop a held unit or prevent use of an obsolete revision.
Should rework, repair, and concession share an approval route?
Not automatically. ISO 9000:2026 distinguishes their purposes. The decision evidence and authority may differ, especially when an item remains outside original requirements. Define routes against actual specifications and customer obligations.
What should a reinspection record contain?
Start with unit ID, instruction revision, characteristic, method, criterion, measured value, instrument, inspector, timestamp, result, and link to any repeat attempt. For sampling, retain sample and population IDs. Final mandatory fields depend on the product and customer requirements.
Should the rework ticket live in MES or QMS?
Quality approval in QMS and controlled dispatch plus execution in MES is one pattern. Assign authoritative updates for every state based on existing systems and teams, and define ERP stock and costing impacts. Avoid two systems independently changing the same disposition.
What matters most in RFP, FAT, and SAT?
Test that a held unit cannot advance, an unapproved instruction cannot start, completed rework cannot self-release, failed reinspection retains history, and an integration fault becomes visible. Run the sequence with representative plant data.
Conclusion
Select a rework system by working backward from the conditions for quality release. Define the affected unit, approval authority, instruction revision, actual work, reinspection evidence, and final release. Link each event with shared identifiers and assign authoritative ownership across QMS, MES, and ERP. Test stale revisions, network outages, failed reinspection, and partial interface failures before go-live.
If your Thai plant is mapping a paper traveler to existing MES, QMS, and ERP, TOMAS TECH can help review an anonymized case and define states, approval points, and interface fields while requirements are still being prepared. Contact us.
Sources
- ISO 9000:2026, Quality management — Fundamentals and vocabulary: terminology for nonconformity, rework, repair, concession, and release.
- ISO, ISO 9001 explained: the QMS framework and documented information.
- ASQ, Cracking the Case of ISO 9001:2015 for Manufacturing: official description of the manufacturing implementation guide.
- GS1, Global Traceability Standard: traceability events and data elements.
- OPC Foundation, OPC UA Common Object Model: ISA-95: manufacturing and enterprise information exchange.
- OPC Foundation, OPC UA for Machine Tools, Part 1, Use Cases: job, part, time, and machine-state use cases.
