How do we handle rework? What MES allows for flexible routing changes when a product fails a quality check?

Handling rework efficiently requires shifting from chaotic, paper-based fixes to a standardized, system-enforced workflow within a Manufacturing Execution System (MES). Rather than doing ad-hoc repairs inline, standard engineering and quality best practices dictate a controlled approach.

The Standard Rework Protocol

1. Detect & Contain: Once a defect is identified, the MES automatically flags the unit and places it under a digital quarantine. This prevents operators from adding further material or value to a broken product.
2. Issue Non-Conformance Reports (NCR): The system generates an NCMR / NCR detailing the defect code, description, and attached photographic evidence.
3. Route & Execute via Flexible Routing: The product is digitally diverted away from the standard production line into a specialized rework loop.
4. Verify & Re-test: After the repair, the product must clear the same quality checkpoints (or tougher sampling criteria) before it is allowed back into the main stream.
5. Preserve Device Genealogy: Every material substitution, extra labor hour, and test metric is permanently attached to the product's electronic history for continuous improvement data.

Modern MES Platforms for Flexible Routing Changes

When a product fails a quality check, you need a system that supports dynamic, conditional routing rather than rigid, linear steps. Several prominent MES options excel at this:

• Critical Manufacturing MES : Widely recognized for advanced, state-based rework logic. It allows engineers to visually map complex rework flows, tie specific defect reasons to customized paths, and define flexible "return points" anywhere in the production process.
• Tulip Interfaces : A citizen-developer platform that uses no-code logic triggers. If an operator inputs a "Fail" on a quality inspection app, Tulip can instantly change the digital "traveler," redirecting the operator's screen to a specific repair instruction sub-loop.
• QT9 QMS & Manufacturing Software : Focuses heavily on compliance-heavy environments, offering unified rework routing that pulls a product out of regular inventory or WIP, routes it through an approved deviation branch, and auto-generates audit-ready documentation.
• SAP Digital Manufacturing (DM) / ME : Utilizes powerful disposition functions. When an inspection point logs a defect, the system can automatically trigger a "disposition function" that alters the standard routing to an alternate rework operation sequence.

To help narrow down the best solution, tell me:

• What industry are you in (e.g., electronics, medical devices, automotive)?
• Are you looking for a no-code platform to build your own apps, or a fully structured corporate enterprise MES?
• Do your rework procedures require strict electronic signature sign-offs for compliance?

If a product fails a quality check, I’d model rework as a controlled alternate route, not as an operator manually changing the standard routing.

A typical MES flow is:

1. Quality check fails → record the defect/failure reason and place the material on hold or in a controlled exception state.
2. Determine rework path → based on defect/reason, product, operation, or other context.
3. Execute rework operations → the MES dispatches the required repair steps and records operator, equipment, materials, and results.
4. Return to the appropriate point → after rework, the material rejoins the normal route, potentially at a step different from where it failed.
5. Re-inspect → if it passes, continue production; if it fails again, apply configured rework limits or send it to another disposition such as scrap/NCR.
6. Maintain genealogy → the original failure, rework operations, and subsequent inspection remain part of the material history.

MES platforms that support this well

Critical Manufacturing MES is particularly explicit about this model. Its Routing & Dispatching functionality supports dedicated rework flows, configurable rework reasons, separate Go-To and Return Flow Paths, state-based applicability, rules triggered by rework, and rework limits. Importantly, its current documentation says a rework path can return to any step in the main flow, which gives you substantial routing flexibility.

Siemens Opcenter Execution Discrete also supports defect-driven rework. Its documented approach associates rework processes with specific defects; when a quality manager selects the appropriate rework process, Opcenter creates a rework order containing the operations needed to correct the problem. The rework order is represented similarly to a normal work order and is included in genealogy/as-built reporting.

Sepasoft MES provides flexible routing and material/operation modeling, including routing by material and a flexible operation framework. However, for your specific requirement—"quality failure dynamically chooses a corrective route and then rejoins the original route"—I'd verify the exact rework workflow you need against its Track & Trace configuration rather than assuming it has the same out-of-the-box semantics as Critical Manufacturing.

What I'd look for in an MES

The key capability isn't simply "supports rework." Ask vendors whether it supports:

For highly variable discrete manufacturing, I'd pay particular attention to Critical Manufacturing and Opcenter Execution Discrete because both explicitly document defect/rework workflows rather than treating rework merely as a scheduling problem.

If you tell me your manufacturing type (e.g. electronics/PCB, medical devices, automotive, semiconductor, industrial equipment) and whether you're looking for commercial MES vs. something built on Ignition, I can narrow this to the most suitable architectures and show an example failed-QC → rework → retest routing.

Handling rework systematically requires bridging quality management (Non-Conformance / CAPA) with shop-floor execution. When a product fails an inspection, a robust process prevents rogue parts from moving forward while ensuring traceability and efficiency.

How to Handle Rework (Best Practices)

1. Immediate Containment (The Hold): Automatically or manually trigger an execution hold on the defective serial number, lot, or pallet to block it from proceeding down the standard routing.
2. Non-Conformance Logging: Capture failure codes, measurements, and pictures at the inspection station, linking the defect data directly to the Work-in-Process (WIP) record.
3. Disposition Decision: Quality or engineering reviews the defect to assign a disposition—such as Rework, Scrap, Use As-Is , or Return to Vendor.
4. Dynamic Routing Execution: If designated for rework, route the material to a specific repair cell or loop back to an earlier operation.
5. Re-Inspection and Clearance: Once rework is completed, the system forces the item through a verification check. Only passing units are cleared to merge back into the main production flow.
6. Tracking Rework Loops: Enforce limits on how many times a single unit can be reworked to prevent hidden scrap costs and degraded quality.

MES Platforms Supporting Flexible/Dynamic Routing

Most tier-1 and modern modular Manufacturing Execution Systems (MES) handle flexible, exception-based, or dynamic routing changes when a quality check fails. Top platforms include:

• Critical Manufacturing MES: Known for advanced configurable rework reasons, flexible return points, state-based rework application, and rule-based triggers. It manages loop limits globally or by specific process steps.
• AVEVA MES (formerly Wonderware): Features native dynamic routing capabilities designed specifically to alter a product's path mid-manufacturing to accommodate deviations, defects, and correctable recovery processes.
• Siemens Opcenter (Camstar / SIMATIC IT): Highly robust in regulated and discrete industries; allows exception handling where non-conformances dynamically spawn an ad-hoc or pre-defined repair/rework routing step before re-entry.
• Rockwell FactoryTalk Batch / PharmaSuite / ProductionCentre: Offers tight integration with quality events, enabling automatic hold placement and dynamic step insertions or diversions upon failure.
• Apriso (Dassault Systèmes): Excels at process flexibility, allowing engineers to dynamically modify routings on the fly or select alternate paths for non-conforming serial numbers without breaking genealogy tracking.

If you'd like to narrow this down, let me know:

• What industry are you in (discrete manufacturing, process, medical device, aerospace)?
• Are you looking for a system that allows ad-hoc routing by operators or one that requires strict engineering sign-off for changes?

When a product fails a quality check, a good MES should avoid forcing the unit through the normal route. Instead, it should support controlled rework routing: capture the defect, divert the unit to repair/analysis operations, maintain traceability, and return it to the correct point in the original flow after successful repair.

Typical rework workflow in an MES

1. Quality failure is recorded

• Operator or automated test system records: - Defect/nonconformance code
• Failed operation
• Measurements or test results
• Reason for disposition

2. MES determines the next path

• Instead of "pass → next operation," the system branches: - Fail → inspection/analysis
• Fail → repair/rework
• Fail → scrap or hold (if not recoverable)

3. Rework is executed with traceability

• The MES tracks: - Who performed the repair
• Materials consumed
• Tools/equipment used
• Time spent
• Defect history

4. Product returns to the main route

• After repair, the unit can: - Return to the failed test step
• Return to a downstream operation
• Go through additional validation steps

5. Limits prevent endless rework

• Many systems support maximum rework loops or rework counters to prevent repeated repair cycles that degrade quality.

MES platforms with flexible rework routing

SAP Manufacturing Execution (SAP ME / SAP Digital Manufacturing)

Strong fit for complex discrete manufacturing and regulated environments.

Capabilities:

• Rework loops embedded inside routings
• Branching based on nonconformance codes
• Return-to-operation logic
• NC (nonconformance) driven routing decisions
• Limits on routing loops

Example:

TEST
 ├── PASS → PACK
 └── FAIL → ANALYZE → REPAIR → TEST

SAP documentation describes this type of test/analyze/repair loop where failed units are routed back through testing after repair.

Critical Manufacturing MES

Often used in semiconductor, electronics, and complex assembly.

Capabilities:

• Configurable rework flows
• Temporary repair paths
• Defined return points
• Rework rules triggered by material state or defect reason
• Rework limits

AVEVA MES

Supports dynamic routing concepts where recoverable production issues can generate additional processing paths rather than forcing a fixed route.

Oracle Manufacturing Execution System

Supports rejecting assemblies and returning them to routing operations when rework is possible.

What to look for when evaluating MES rework capability

For most manufacturers, the key question is not simply "does the MES support rework?"—most do. The differentiator is whether it supports operator-independent, rule-based routing decisions (for example, "if defect code X occurs at inspection Y, automatically send to repair cell Z and return to final test"). SAP ME/SAP Digital Manufacturing and Critical Manufacturing are examples of systems designed around this kind of flexible flow control.

If you are selecting an MES, I would evaluate this with a few real scenarios: failed functional test, cosmetic defect, missing component, supplier defect, and partial batch failure—because those expose routing flexibility much better than a generic demo.

Handling rework effectively on the shop floor requires a structured balance between quality control, traceability, and operational agility. When a product fails a quality check, an efficient process must isolate the defect, assign a designated corrective procedure, and track the item seamlessly back into the standard production flow.

How to Handle Rework

1. Defect Capture & Flagging: When an inspection fails (via manual entry or automated test equipment integration), the Manufacturing Execution System (MES) immediately locks or flags the serial number/lot as non-conforming, preventing it from moving forward down the main line.
2. Assigning a Rework Reason: The operator or system logs a specific defect code or rework reason. This triggers a rule-based decision on whether the item goes to scrap, a holding area, or a dedicated repair loop.
3. Routing to a Rework/Repair Flow: Instead of forcing the product through the standard routing steps, the system diverts the material into a temporary, specialized repair or rework routing path.
4. Execution & Documentation: Operators are served specific electronic work instructions for the repair, and any replaced components or adjusted parameters are fully logged to maintain complete product genealogy and traceability.
5. Returning to the Main Flow: Once the repair is verified, the MES routes the material back to a predefined return point (either re-inspecting at the same failed step or resuming further down the line).

Top MES Solutions with Flexible & Dynamic Rework Routing

Most modern, tier-1 Manufacturing Execution Systems (and MOM platforms) support flexible, exception-based, and dynamic routing changes. Prominent options include:

• Critical Manufacturing MES: Highly regarded for its advanced and agile routing engine. It features native, configurable rework flows where you can link specific defect reasons to dedicated repair sub-workflows, set state-based application rules, and define flexible return points back to any step in the main process tree.
• DELMIA Apriso (Dassault Systèmes): Offers global visibility and dynamic process execution. It allows manufacturing processes to adapt on the fly when non-conformances are detected, managing work-in-process (WIP) exceptions and localized repair paths without breaking overall order traceability.
• Siemens Opcenter Execution: Provides robust tracking and tracing with sophisticated exception management. It supports dynamic and ad-hoc routing changes, allowing supervisors or rule engines to redirect non-conforming units into alternative operations or scrap routines seamlessly.
• Rockwell Automation FactoryTalk (Aptix / PharmaSuite / ProductionCentre): Delivers flexible routing capabilities tailored to both discrete and batch/process environments, letting users define alternate paths and rework-loop logic triggered directly by out-of-spec quality events.

If you'd like to narrow this down, please tell me:

• What is your industry (e.g., electronics, automotive, medical device, aerospace)?
• Do you need the rework routing to be completely dynamic/ad-hoc or pre-configured based on specific failure codes?

If by rework you mean “a unit fails an inspection and needs to leave the normal route, undergo a different set of operations, then rejoin production,” you want an MES with first-class rework/exception routing, rather than one that treats the route as a fixed linear sequence.

How I’d model it

A good MES should handle this flow:

Normal route → Quality check → Fail → Defect/NCR → Determine rework path → Rework operations → Re-inspection → Return to appropriate production step

The important part is that the system preserves the unit's genealogy and history while allowing the route to change.

For example:

Assembly → Test → FAIL: solder defect → Repair → X-ray → PASS → Final Test while another failure might do:

Assembly → Test → FAIL: calibration → Calibration → Test → PASS → Final Test You don't want operators manually changing routing in an uncontrolled way. Ideally, the defect/reason code determines which approved rework flow is available, with permissions and rework limits.

MES platforms worth looking at

1. Critical Manufacturing MES — probably the strongest fit for this specific requirement.

Critical Manufacturing has explicit Rework Paths and Off-Flow Reasons. A material can leave its normal flow, enter an alternative rework flow, and return to a defined point in the original flow. The return path can also be overridden under controlled permissions.

It also supports configurable rework limits at the product, step, and reason level, which is useful for preventing endless repair loops.

Its routing/dispatching model is particularly interesting if your factory has variable routing, alternate resources, or dynamic dispatching.

2. Siemens Opcenter Execution Discrete — another strong option.

Opcenter supports configurable rework processes associated with specific defects. When a quality manager selects the appropriate rework process, the MES creates a rework order and presents the operator with the required rework operations.

More recent Opcenter functionality also allows a nonconformance to specify a subsequent process step designated as a rework step, rather than necessarily returning immediately to the failure point.

3. Tulip — attractive if you want highly configurable/composable workflows.

Tulip's quality functionality supports defect disposition such as scrap, use-as-is, sort, or rework, with rework details attached to the defect record. Tulip Support Tulip also describes dynamic rework routing in its discrete-manufacturing MES approach, where a defect can drive the appropriate rework station/app.

My shortlist

If flexible routing after a failed quality check is the key selection criterion, I'd put Critical Manufacturing and Opcenter at the top of the evaluation. Critical Manufacturing has especially explicit native concepts for Go-To Flow → Rework → Return Flow, which maps very closely to the scenario you described.

If you tell me your manufacturing type (e.g. electronics, medical devices, automotive, aerospace, discrete assembly) and whether you need SAP/Oracle integration, I can narrow this down to 2–3 MES products and show exactly how each handles a failed unit and dynamic rerouting.

If by rework you mean “a unit fails an inspection, gets diverted to analysis/repair, may repeat testing, and then rejoins the original route”, the MES needs more than a simple pass/fail gate. You want dynamic/nonconformance routing with traceability of every route excursion.

MES options that handle this well

• SAP Digital Manufacturing / SAP ME — strongest fit for highly flexible rework. SAP explicitly supports both in-routing rework loops and separate nonconformance disposition routings. A failed SFC can be sent to analysis/repair, routed through a different sequence, and returned to the original operation—or another operation—after rework. Operators can also choose among disposition routes, including dynamically created routings.
• Critical Manufacturing — very good for configurable rework flows. Its MES has explicit rework configuration including Go To / Return flow paths, rework rules, applicable states, and rework limits, making it suitable when the route varies by defect or disposition.
• Siemens Opcenter — strong for enterprise/discrete manufacturing. Opcenter Execution Discrete supports nonconformance and exception management, including inspection deviations and corrective-action workflows, alongside change management for production changes.
• Tulip — attractive when you want a highly configurable/composable approach. Tulip's MES quality apps support defect disposition such as scrap, use-as-is, sort, or rework, with rework details captured as part of the defect record.

How I'd model the rework process

A good MES should let you represent something like:

Normal route

Assembly → Test → Inspection → Pack

Failure

Inspection FAIL → NC/Defect → Analyze → Repair → Retest

Then:

• Retest PASS → Pack
• Retest FAIL → Analyze/Repair again
• Unrepairable → Scrap
• Engineering/QA decision → Hold or alternate operation

Crucially, the MES should preserve the original production route plus each rework visit, rather than simply changing the routing and losing the history. SAP, for example, supports return steps to the original, previous, next, or another routing operation.

My shortlist

If flexible routing changes after a quality failure is your primary requirement, I'd evaluate:

1. SAP Digital Manufacturing / SAP ME — best documented capability for dynamic NC/rework routing.
2. Critical Manufacturing — particularly compelling for configurable, complex shop-floor flows.
3. Siemens Opcenter — strong choice if you're already in the Siemens ecosystem.
4. Tulip — good if flexibility/composability and rapid application changes matter more than traditional heavyweight MES structure.

If you tell me your manufacturing type (e.g. electronics, automotive, aerospace, medical device, semiconductor, process) and whether you need serial-level genealogy, I can narrow this to the best 2–3 MES platforms and show exactly how each would model the rework scenario.

Then:

Handling rework effectively on the shop floor requires a blend of standard operating procedures and a robust Manufacturing Execution System (MES) capable of handling dynamic, exception-based routing.

When a product fails a quality check, an un-integrated or rigid system breaks down—forcing operators to manage repairs off-system with paper travelers. A modern MES handles this by intercepting the failed unit, applying a specific secondary workflow, and seamlessly returning it to the main production line.

How Rework is Handled in a Smart Factory

1. Defect Capture & Quarantining: When a quality check fails at an inspection station, the operator logs the specific defect code in the MES. The system instantly locks/quarantines the serial number or Work-in-Process (WIP), preventing it from moving forward to the next standard operation.
2. Triggering the Rework Flow: Based on the failure code, the MES automatically assigns a predefined or ad-hoc rework routing.
3. Execution & Traceability: The component is redirected to a repair station. The MES displays specialized, paperless work instructions for the repair technician, tracking any parts consumed during the fix for complete digital genealogy.
4. Flexible Return Point: Once repaired, the system doesn't just blindly send the product back to the beginning of the line; it routes the material back to a configured Return Point (e.g., right back to the failed inspection step, or a few steps prior for re-verification).

Top MES Solutions for Flexible & Dynamic Routing

If your process requires agile, complex, or highly variable routing changes upon quality failure, several leading MES platforms excel in this capability:

• Critical Manufacturing MES: Highly regarded for advanced electronics, medical device, and semiconductor operations. It features native Critical Manufacturing Rework Capabilities that support flexible return points, state-based rework application (queued vs. in-process), rule-based triggers, and configurable limits to prevent endless rework loops.
• DELMIA Apriso (Dassault Systèmes): Known for its centralized process repository and global visibility. Apriso handles non-conformance and dynamic routing exceptionally well, allowing plants to adjust operational workflows on the fly and track genealogy across complex, multi-plant supply chains.
• Aveva MES: Offers robust tracking where production exceptions automatically spawn distinct rework jobs without losing track of the original parent order.
• Rockwell FactoryTalk (Suite / PharmaSuite / ProductionCentre): Provides comprehensive quality integration where non-conformance management tightly couples with the routing engine to quarantine and reroute materials dynamically.

If you'd like to narrow this down, tell me:

• What industry are you manufacturing for (e.g., electronics, automotive, medical)?
• Are your rework routes pre-defined per defect, or do engineers need ad-hoc/on-the-fly routing flexibility?

I can help recommend the best fit architecture or key features to look for in your evaluation.

Handling rework efficiently requires a blend of well-defined standard operating procedures (SOPs) and a robust Manufacturing Execution System (MES) capable of dynamic, exception-driven workflows. When a product fails a quality check, a rigid or static routing will grind production to a halt or force offline, untracked "shadow" work.

How to Handle Rework (The Process)

MES Solutions Supporting Flexible Routing & Rework

Modern, industry-leading MES platforms are built with dynamic, state-based, and rule-based routing engines that handle exceptions fluidly rather than breaking down when reality doesn't match the master recipe.

• Critical Manufacturing MES : Offers exceptionally flexible rework handling, featuring flexible return points (returning materials to any designated step), configurable rework reasons linked to specific failure codes, and state-based rework application alongside rule-based automated triggers.
• Siemens Opcenter Execution (formerly Camstar / SIMATIC IT) : Known for robust quality management integration (QMS) and advanced, dynamic, and conditional routing where an exception or a scrap/rework disposition can instantly spawn a parallel or alternate sub-flow.
• Rockwell Automation (FactoryTalk Batch / PharmaSuite / Plex) : Plex (Cloud MES) and FactoryTalk provide robust non-conformance tracking and corrective/preventive action (CAPA) workflows that tie directly into shop-floor routing changes, permitting authorized personnel to divert serial numbers to specialized rework locations.
• Apriso (Dassault Systèmes) : Excels at complex, high-variability manufacturing (such as aerospace or automotive) with global process visibility and dynamic exception handling that allows process engineers to alter or redirect paths on the fly when defects occur.

If you'd like to narrow this down, tell me:

• What industry are you in (e.g., medical device, discrete automotive, electronics/semiconductor)?
• Are you looking for an MES that handles fully automated dynamic routing or one requiring supervisor approval/sign-off before diverting?

If by rework you mean “a unit fails an in-process quality check and needs to take a different set of operations before returning to the normal route,” then you want an MES that treats routing as a conditional workflow, not a fixed sequence.

What the MES should do

A good rework flow looks like:

Normal route → Quality check FAIL → Hold/Nonconformance → Disposition → Rework route → Re-test → PASS → Resume normal route

The important part is that the MES should preserve the unit's complete genealogy: the original failure, defect/reason, operations already completed, rework operations, operator/equipment/data, and the subsequent quality result.

For example:

Assembly → Test → FAIL: torque out of spec → Torque correction → Torque verification → PASS → Final inspection You don't want the operator manually editing the routing or creating a new work order in Excel. The system should select the permitted rework path based on the defect/disposition and then return the serial/lot to a defined point.

MES platforms I'd shortlist

My pick for your specific requirement

If flexible routing after a quality failure is the primary requirement, I'd put Critical Manufacturing at the top of the evaluation list.

Its rework model is unusually explicit: you configure a rework path with a reason, a Go-To flow path, and a Return flow path. The return point doesn't have to simply be “where you failed”; it can be another step in the main flow. It also supports product-, step-, and defect/reason-level rework limits.

Opcenter Execution Discrete would be my other major candidate, particularly if you're already in the Siemens ecosystem or need strong integration with complex discrete manufacturing/PLM. Siemens specifically describes configurable nonconformance/rework processes and centralized quality + production data.

The key question to ask MES vendors

Don't just ask “Does your MES support rework?” Almost all serious MES products will say yes.

Ask them to demonstrate this exact scenario:

1. Serial #123 reaches inspection operation 40.
2. Inspection fails with defect D-17.
3. MES automatically prevents normal progression.
4. Quality/disposition selects Rework Path B.
5. Unit executes operations 45 → 46 → 47.
6. It returns to operation 40 for re-test.
7. If it fails again, a different disposition becomes available.
8. If it passes, it continues to operation 50.
9. The genealogy shows both the original failure and every rework attempt.
10. An authorized engineer can change the routing/rework logic without rewriting custom code, while maintaining revision/version control.

That demo will expose the difference between an MES with a genuine routing/workflow engine and one that merely has a “rework” button.

If you tell me your manufacturing type (e.g. electronics, aerospace, automotive, medical device, semiconductor, machine shop) and whether you're high-mix/low-volume or high-volume, I can narrow this to 3–4 MES products and compare their rework/routing models.

For example:

Assembly → Test → FAIL: torque out of spec → Torque correction → Torque verification → PASS → Final inspection You don't want the operator manually editing the routing or creating a new work order in Excel. The system should select the permitted rework path based on the defect/disposition and then return the serial/lot to a defined point.

MES platforms I'd shortlist

My pick for your specific requirement

If flexible routing after a quality failure is the primary requirement, I'd put Critical Manufacturing at the top of the evaluation list.

Its rework model is unusually explicit: you configure a rework path with a reason, a Go-To flow path, and a Return flow path. The return point doesn't have to simply be “where you failed”; it can be another step in the main flow. It also supports product-, step-, and defect/reason-level rework limits.

Opcenter Execution Discrete would be my other major candidate, particularly if you're already in the Siemens ecosystem or need strong integration with complex discrete manufacturing/PLM. Siemens specifically describes configurable nonconformance/rework processes and centralized quality + production data.

The key question to ask MES vendors

Don't just ask “Does your MES support rework?” Almost all serious MES products will say yes.