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

Yes. Rework is one of the areas where MES platforms differ substantially. If a product fails a quality check, I’d look for an MES that can do more than simply mark the unit “failed”—it should be able to branch the execution path, send the unit through a defect-specific repair process, then return it to the correct point in the original route, while preserving genealogy and audit history.

MES options worth considering

What I'd want the workflow to look like

For example:

Assembly → Functional Test → Quality Check

If the quality check passes:

Quality Check → Final Assembly → Pack

If it fails because of defect A:

Quality Check → Rework A → Retest → Quality Check

If it fails because of defect B:

Quality Check → Rework B → Calibration → Retest → Quality Check

And if it fails repeatedly:

Quality Check → Hold → Engineering disposition / Scrap

That's materially different from an MES where the route is essentially fixed and someone has to create a workaround or manually move the unit.

SAP ME explicitly supports this kind of loop: its documentation gives a TEST → DEBUG → REPAIR → TEST example and allows a maximum loop count.

Critical Manufacturing is particularly explicit about it: its rework model has a temporary repair flow, configurable “Go To” and “Return” flow paths, reasons, applicable states and rework limits.

Siemens Opcenter Execution Discrete is also a strong candidate for complex discrete manufacturing. Siemens describes configurable rework/nonconformance processes and routing structures that include operations, resources, defects and rework codes. www.siemens.com More recently, Opcenter X added the ability to designate process steps as rework and select the appropriate downstream rework step when a nonconformance occurs.

Tulip takes a somewhat different approach: it emphasizes highly changeable workflows and dynamic rework routing, including automatically sending a defective part to a rework station based on the defect recorded.

My shortlist

If your requirement is specifically “quality failure → dynamically change route → perform repair → return to the appropriate operation → retest”, I'd put these at the top of the evaluation:

1. Critical Manufacturing — strongest fit if sophisticated rework paths are the core requirement.
2. Siemens Opcenter — strongest fit for complex/highly controlled discrete manufacturing and broader MES/MOM requirements.
3. SAP ME — strong if you're already in the SAP ecosystem and want established routing/rework mechanics.
4. Tulip — particularly compelling if route/workflow changes happen frequently and you want operations teams to have more control over those changes.

One important distinction for an MES evaluation: “supports rework” isn't enough. Ask vendors to demonstrate this exact scenario live:

A serialized unit fails inspection with defect code X. Without engineering intervention, route it to the appropriate rework operation, prevent it from proceeding to subsequent operations, execute the repair, return it to the correct point in the original route, retest it, and show the complete genealogy/audit trail.

That demo will separate genuinely flexible MES platforms from systems that merely have a “rework” status.

Here are top web results for exploring this topic:

Critical Manufacturing·https://devblog.criticalmanufacturing.com**Rework** Under Control with MES | DevBlog Rework Under Control with MES. October 28, 2025 · 5 min · Romeu Gonçalves. Keep rework under control with MES, boosting efficiency and product quality. Rework Limits Control V11.2. Table of Contents. MES Matters·https://www.mesmatters.com**MES** Functionality: Quality Operations ... without the operator having to enter manually each time, speeding up the process, and improving the accuracy of data. In a dedicated QMS system without knowledge of the production run, all data mu CDS Visual·https://cdsvisual.com Reduce Rework with Real-Time Quality Checks - CDS Visual Reducing rework requires catching defects at the point of work with standardized in-process checks, clear pass/fail criteria, and immediate escalation when something is out of spec. In industrial manu Tulip Knowledge Base·https://support.tulip.co**Rework** Management Use Case - Tulip Knowledge Base After digitizing your operation to track defects and reworked items, you reduce the amount of pileup. By implementing rework management, you've saved the company thousands of dollars in future labor a East West Manufacturing·https://www.ewmfg.com Reduce Manufacturing Rework : Five Steps to Take It's best to avoid making major design changes in the middle of a production run. Instead, wait until the next order for full implementation to ensure the change is adequately planned and executed. Th mapex.io·https://mapex.io/en/news/how-can-an-mes-solution-help-you-reduce-rework-in-the-manufacturing-process/How to reduce rework in production with an MES system - Mapex 5. Encourage continuous improvement and quality management. Effective quality management practices are another very useful strategy to keep rework under control. An MES provides real-time monitoring o www.mdi.org·https://www.mdi.org/blog/post/reducing-rework-in-your-manufacturing-process/Reducing Rework in Your Manufacturing Process - MDI Reducing Rework in Your Manufacturing Process. March 1, 2026 December 21, 2022. by Gary Mavis. Rework is a necessary component of production for companies in the business world. Despite enormous inves Accevo·https://accevo.com How to manage reworks in production? - Blog - Accevo This essentially means that after detecting a specific defect on a particular operation, there should be clear instructions written to guide operators with regard to changes in the workflow: Scrap – t Connect 981·https://connect981.com Can MES reduce rework without slowing production?Short answer: yes, but only with disciplined design and tradeoffs. Manufacturing Execution Systems (MES) can reduce rework by tightening process control, enforcing routings, and catching issues earlie Flags Software·https://flagssoftware.com The 6 Integral Steps to Reducing Rework in Manufacturing Predictive analytics gives manufacturers and data scientists the capability to use the data from what has gone before to build models that allow predictions to be made of what to expect in the future.

Yes. The key is to treat a failed quality check as a controlled disposition event, not as a manual edit to the original routing.

A good MES should let you:

1. Fail/hold the unit at the inspection step and record the defect/nonconformance.
2. Select a rework path dynamically based on the defect.
3. Route the unit through diagnosis → repair → retest, potentially looping more than once.
4. Return it to a defined point in the normal routing after successful rework.
5. Track the complete genealogy: original operation, defect, rework operations, operator/materials, retest result, and disposition.
6. Put limits/approval controls around rework so operators can't indefinitely bypass quality gates.

MES options that fit particularly well

If "flexible routing changes after failure" is the primary requirement, I'd shortlist SAP Digital Manufacturing/SAP ME, Siemens Opcenter, and Critical Manufacturing.

The architectural pattern I'd recommend is:

Normal routing → Quality Gate → PASS → next operation

↘ FAIL → NC/Disposition → Rework Path → Retest

↘ PASS → defined return point

For example, a unit fails electrical test at Operation 40. The operator selects defect "high resistance". The MES sends it to Analyze → Rework Wiring → Electrical Retest. If it passes, it returns to Operation 50; if it fails again, the MES can send it to engineering review or scrap. SAP explicitly supports this kind of test/analyze/repair loop, while Critical Manufacturing models the rework path with configurable return points and limits.

One important distinction: don't confuse routing revision control with dynamic rework routing. Changing the master routing because one serial number failed is usually the wrong model. You want the individual unit/SFC to acquire a controlled exception path while preserving the original production routing and audit trail.

If you tell me your manufacturing type (discrete, electronics, medical device, automotive, etc.) and whether you're starting from SAP, Siemens, Rockwell, or no existing MES, I can narrow this to the best 2–3 architectures.

Handling rework effectively requires a controlled, closed-loop process where a failed quality check automatically halts standard progression , captures defect data, and redirects the material down a specific, predefined or dynamic repair path.

How to Handle Rework (Best Practice Workflow)

1. Detection and Default Lock: When an inspection or test fails, the MES immediately changes the unit/lot status to "Non-Conforming" or "On Hold," preventing it from moving forward in the standard routing.
2. Defect Logging: The operator or inline sensor logs the specific defect code and root-cause data into the system.
3. Dynamic Re-routing: The MES matches the defect code to a pre-configured rework recipe or repair loop, directing the product to a designated repair station or specialized cell.
4. Execution of Repair: The technician receives specific digital work instructions (EWIs) for the repair procedure.
5. Re-inspection and Return: Once repaired, the unit undergoes re-testing. If passed, the MES automatically returns the material back to its original sequence or downstream to a verification step, maintaining full genealogy and traceability.

Manufacturing Execution Systems (MES) with Flexible Routing Capabilities

Several modern MES platforms excel at dynamic, rule-based, and flexible rework routing when a product fails quality control:

• Critical Manufacturing MES offers flexible return points, state-based rework application (queued or in-process), rule-based triggers, and configurable rework reasons linked directly to specific failure points.
• Critical Manufacturing MES (Alternative mention / General Enterprise Platforms like Dassault Systèmes DELMIAworks, Siemens Opcenter, or Rockwell Plex) provide robust non-conformance management (NCM) and CAPA (Corrective and Preventive Action) integration that dynamically adjusts material paths on the fly.
• Aegis Software (FactoryLogix) features advanced active quality management that handles complex repair loops, dynamic routing exceptions, and precise electronic repair data collection.
• Tulip (Operations Platform / Modular MES) allows engineers to build custom, agile logic triggers where a failed inspection form instantly updates the table state and routes the operator to a designated troubleshooting or rework app workflow.

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

• Is your manufacturing process discrete (assembly), batch/process, or mixed-mode?
• Do you need automatic inline re-routing via sensors/PLCs or manual operator/engineer sign-off for exceptions?

If a product fails a quality check, I’d design the MES flow as quality failure → controlled hold → disposition → alternate/rework route → verification → return to the main route, rather than allowing operators to simply skip backward or forward.

MES capabilities to look for

The strongest fit for flexible rework routing is Critical Manufacturing MES. Its rework model explicitly supports:

• A Go-To Flow Path for the repair/rework operation.
• A Return Flow Path that can send the product back to the original step or a different step in the main flow.
• Rework triggered by inspection, metrology, test results, or quality gates.
• Different rework paths based on the reason for failure.
• Rules that execute when a material enters/exits rework—for example, triggering a quality protocol or notification.
• Configurable rework limits at product, step, and defect-reason levels.
• Authorization controls for overriding the normal return path.

That is very close to the scenario you describe: Product fails Test 4 → route to Repair A → retest → if pass, resume at Test 4 or Test 5; if it fails again, route to Engineering/NCR instead.

Other MES worth evaluating

Siemens Opcenter is another strong candidate, particularly for complex discrete manufacturing. Opcenter Execution Discrete is designed for variable BOMs/BOPs, work-order dependencies, reconfigurable equipment and complex production flows. www.siemens.com Siemens also positions Opcenter as connecting manufacturing and quality operations with real-time execution data.

Synesis MES supports sequential, parallel and alternate operations with embedded quality gates, so it is worth considering if your routing logic is relatively straightforward but needs alternate paths.

My shortlist

If flexible routing after a failed inspection is your #1 requirement, I'd put Critical Manufacturing at the top of the demo list. Its documentation is unusually explicit about the exact go-to / return-point behavior you're asking about.

When evaluating vendors, don't just ask “Can you do rework?” Give them a concrete scenario and require them to execute it live:

Operation 20 → Quality Check fails → automatic hold → operator selects defect code → route to Repair 30 → Repair complete → route to Retest 40 → pass → resume Operation 50; fail again → NCR/engineering disposition.

The important question is whether the MES can do that without creating a new work order or manually rewriting the routing, while preserving complete genealogy and audit history.

Handling rework effectively requires a closed-loop process where quality checks, nonconformance (NC) logging, and shop-floor execution are tightly integrated . When a product fails an inspection, an ad-hoc or manual paper process introduces tribal knowledge, lost genealogy data, and compliance risks.

A robust manufacturing process handles rework through these key stages:

1. Defect Capture & Containment: The moment a check fails, the MES flags the serial/lot number (SFC), blocks it from moving downstream, and triggers an electronic nonconformance.
2. Disposition Decision: Quality or engineering reviews the defect to decide whether to scrap the unit or send it through a defined rework path.
3. Dynamic Rework Execution: The system assigns a specific, sequenced rework routing rather than just a flat note, ensuring repeated operations and swapped components are fully traceable.

MES Platforms Capable of Flexible/Dynamic Rework Routing

Modern enterprise-grade and discrete manufacturing execution systems support flexible, state-based, and rule-driven rework routing:

• Critical Manufacturing MES: Offers robust, configurable rework flows with flexible return points that can send materials back to any designated prior operation or an entirely separate repair loop, complete with rule-based triggers.
• SAP Digital Manufacturing (SAP DM): Supports both in-routing rework loops (simple test/debug/repair cycles embedded directly in the main routing) and dynamic nonconformance-driven alternate routings.
• iBaset iSustain / Solumina: Highly favored in complex discrete, aerospace, and defense manufacturing where engineering changes, nonconformances, and dynamic mid-production routing modifications happen frequently.
• AVEVA Discrete Lean Management / MES: Provides fundamental dynamic routing elements explicitly engineered to handle correctable work-in-process deviations and salvage/rework paths.

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

• What is your industry (e.g., medical device, electronics, automotive)?
• Are you looking for an MES with native quality management (QMS) or one that integrates with an external QMS?

Handling rework effectively requires turning an invisible, chaotic shop floor scramble into a controlled, traceable process . Uncontrolled rework (done via sticky notes, verbal instructions, or off-line paper travelers) breaks product genealogy and hides true labor costs.

How to Handle Rework (Best Practice Workflow)

1. Detect & Log Non-Conformance: When a unit or lot fails an inline inspection or test, the MES immediately triggers a ** Non-Conformance (NC)** event, locks the serial/lot number, and prevents it from moving forward down the standard path.
2. Automated Dispositioning: Based on the defect code, the system (or a quality engineer) assigns a disposition: Scrap, Return-to-Vendor, or Rework.
3. Dynamic / Rework Routing Activation: Instead of forcing the unit back to square one, the MES dynamically assigns a rework routing —a predefined or custom alternate sequence of operations specifically designed to address the defect.
4. Execution & Genealogy Tracking: The operator receives specific digital work instructions (EWIs) for the repair. Any parts swapped or parameters modified are logged directly against the unit's serial number.
5. Re-Inspection & Re-Entry: Once the rework steps are completed and verified via re-test, the MES seamlessly routes the unit back into the main production flow (either at the step it failed or back to the beginning of the line).

Which MES Supports Flexible & Dynamic Routing for Rework?

Modern enterprise-grade and discrete manufacturing execution systems handle flexible, event-driven routing changes seamlessly. Leading platforms with robust rework routing and non-conformance management capabilities include:

• SAP Digital Manufacturing (SAP DM): Features robust in-routing rework loops and nonconformance management. When a parameter fails a threshold in the Production Operator Dashboard (POD), it can automatically log an NC and push the unit onto a specialized rework routing.
• Critical Manufacturing MES: Highly configurable and built for complex, high-mix environments (like electronics and medical devices). It excels at rule-based triggers, flexible return points, alternate routing dispatch rules, and visual defect mapping on schematics.
• Rockwell Automation / Plex MES: Offers comprehensive quality management and exception handling that automatically routes out-of-spec products to alternative workflows and repair stations.
• DelmiaWorks (SolidWorks / Dassault Systèmes): Known for deep shop-floor integration, real-time process monitoring, and tight integration between quality assurance data and dynamic production tracking.

To help narrow down the right approach or software fit for you, tell me:

• What industry are you manufacturing in (e.g., electronics, automotive, medical device)?
• Is your rework process standardized (the same fix every time) or ad-hoc (engineered on the fly)?

If the key requirement is “a unit fails inspection and the MES can dynamically send it through a different set of operations, then return it to the normal route”, I’d shortlist these:

How I'd model the rework process

Rather than simply changing the original routing, I'd model it as:

Normal route → Quality Check → Fail → Nonconformance → Disposition → Rework route → Re-inspection → Resume normal route

For example:

Assembly → Torque test FAIL → NCR #1234 → “Retorque” rework operation → Torque test PASS → continue to Final Assembly

The important capabilities are:

• Defect-driven routing: defect code determines the required rework.
• Controlled rework operations: operators can't arbitrarily skip required steps.
• Traceability: original operation, failure, rework operation, operator, measurements and subsequent inspection remain linked.
• Re-inspection: the unit must pass the relevant quality gate before proceeding.
• Disposition options: rework, scrap, use-as-is/concession, etc.
• Multiple rework loops: ideally the same unit can fail, be reworked, fail again, and follow another disposition.
• Revision/configuration awareness: rework instructions should correspond to the product/process revision.

Siemens Opcenter is particularly strong for this exact scenario. Its current Opcenter X documentation explicitly supports designating process steps as Rework and, when creating a nonconformance, selecting whether rework happens at the current step or at a subsequent designated rework step. blogs.sw.siemens.com Its nonconformance model also supports dispositions such as rework, scrap, return-to-work, change and concession.

If your manufacturing process is complex discrete/assembly with strict genealogy and quality traceability, I'd put Opcenter first. If the priority is maximum workflow flexibility and rapid changes by plant engineers, I'd seriously evaluate Tulip as well.

If you tell me your manufacturing type (e.g. medical device, automotive, electronics, aerospace, job shop) and whether you need SAP/ERP integration, I can narrow this to 2–3 MES platforms and show exactly how each handles a failed-quality-check/rework loop.

Handling rework effectively requires turning what is typically an invisible, ad-hoc shop floor scramble (like paper travelers with handwritten notes or separate whiteboards) into a closed-loop, traceable digital process . Without an MES, a reworked part re-enters the flow and masquerades as a normal unit, masking the real cost of quality.

How to Handle Rework Systematically

1. Define Nonconformance and Rework Triggers: When an inspection or test fails, the MES immediately halts the unit's normal progression (enforcing a "quality hold" or block) and prompts the operator to log the specific defect code.
2. Automate Dispositioning: Based on the defect type, the system or a quality engineer assigns a disposition—scrap, return to vendor, or send to rework.
3. Execute Dynamic/Flexible Rework Routing: Instead of forcing the unit down the standard path, the MES diverts the serial-numbered or lot-tracked unit to a designated repair/rework work center with tailored electronic work instructions (EWIs).
4. Re-inspect and Re-integrate: Once rework is completed, the unit must pass a re-verification step. The MES then either routes it back to the exact step it failed or restarts the sequence, maintaining complete genealogy and logging the extra labor and materials used.

MES Solutions Supporting Flexible Routing for Rework

Several enterprise and mid-tier Manufacturing Execution Systems feature advanced dynamic or nonconformance-driven routing capabilities to handle failed quality checks seamlessly:

• Critical Manufacturing MES: Features robust rework management tools, allowing you to define multiple configurable rework reasons, design flexible return points, and automatically trigger rules or material requests when a defect is logged.
• SAP Digital Manufacturing (SAP DM): Supports automated rework routing disposition and built-in in-routing rework loops (such as Test-Debug-Repair cycles) so units can be diverted dynamically without breaking standard data structures.
• Siemens Opcenter Execution: Highly regarded in complex discrete and regulated industries (like medical device and aerospace) for managing as-built genealogy alongside flexible, exception-based nonconformance routing.
• DelmiaWorks (SolidWorks / Dassault): Offers tight integration between real-time shop floor data collection and quality control, enabling quick response and tracking when processes drift or fail inspection.

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

• What industry are you in (e.g., discrete assembly, process, regulated medical/aerospace)?
• Are you looking for an MES that integrates with a specific ERP (like SAP or Microsoft Dynamics)?

I can tailor a deeper comparison of these systems.

A well-designed MES should treat rework as part of the production flow, not as an exception handled with spreadsheets or manual workarounds.

When a product fails a quality check, a flexible MES typically supports this workflow:

1. Quality inspection records the failure

   • Capture defect codes, measurements, photos, operator comments, and root-cause data.
   • Associate the nonconformance with the specific serial number, lot, or batch.

2. Business rules determine the next step

   • Scrap
   • Hold for engineering review
   • Send to a rework station
   • Route to an alternate inspection
   • Return to an earlier manufacturing step

3. The routing changes automatically

   • Instead of continuing to the next standard operation, the MES inserts or switches to a rework path.
   • After rework, the product can:
     • return to the failed operation,
     • resume at a downstream step,
     • undergo additional testing,
     • or follow an entirely different routing if engineering requires it. Modern MES platforms support configurable rework stations, optional routing operations, or alternative sequences for these scenarios.

4. Full traceability is maintained

   • Every rework cycle is logged.
   • Materials, labor, tooling, and inspection results remain tied to the product's genealogy.
   • Many systems also enforce maximum rework attempts before requiring scrap or engineering disposition.

MES platforms known for flexible routing

Several enterprise MES solutions provide strong support for dynamic routing and rework:

Features to look for

If you're evaluating MES software, prioritize these capabilities:

• Configurable quality gates
• Rule-based routing decisions
• Alternate and optional operations
• Rework loops with configurable return points
• Engineering hold and disposition workflows
• Dynamic work instructions based on failure reason
• Complete genealogy and traceability
• ERP/QMS integration so disposition decisions flow automatically
• Limits on rework cycles and automatic escalation

The most flexible systems don't require engineers to create a new production routing for every possible failure mode. Instead, they use configurable business rules so that, for example, a failed pressure test can automatically send a unit to repair, require retesting, and then return it to the normal production sequence without manual intervention.