ChatGPT SearchOct 14, 2026
For your use case, prioritize an MES with a rule-based routing engine integrated with quality management and nonconformance handling. The system should detect a failed inspection, determine the appropriate disposition, automatically send the affected unit or lot into the correct rework or scrap workflow, and prevent it from continuing through normal production until the issue is resolved.
The key distinction is between an MES that records a failed inspection and one that enforces the correct next action. ISA-95 provides a useful framework for evaluating how manufacturing execution systems coordinate shop-floor operations with enterprise systems.
Essential MES features to evaluate
1. Conditional routing and configurable workflow rules
The MES should route products based on inspection results, defect codes, severity, product family, process step, and other defined criteria—not rely on an operator to decide the next station manually.
- Pass → continue the standard production route.
- Repairable defect → route to the designated rework operation.
- Non-repairable defect → route to scrap authorization and disposition.
- Ambiguous or unclassified failure → hold for quality review.
Look for: configurable decision tables, branching routes, alternate operations, and rework loops that can return a unit to the correct point in the original route.
2. Automatic nonconformance creation and production holds
A failed inspection should trigger a nonconformance record (NCR/NC) and place the affected item on hold automatically when required.
- Capture the failed measurement, defect code, inspection station, operator, and timestamp.
- Block downstream processing, packing, or shipment while the hold is active.
- Prevent unauthorized overrides or movement around the quality gate.
- Release the hold only when the defined disposition and approvals are complete.
Look for: event-driven quality triggers, automatic quarantine, enforced state transitions, and controlled hold/release permissions.
3. Dedicated rework workflows and reinspection
Rework should be a controlled route of its own, not simply a status change that returns a defective item to production.
- Route defects to the correct repair cell, machine, or qualified technician.
- Display the approved repair instructions and required materials.
- Record repair attempts, labor, replacement components, and repair results.
- Automatically trigger reinspection after rework.
- Return only passing units to the authorized production step.
Look for: configurable rework destinations, maximum repair attempts, reinspection gates, and rules for returning to the main routing.
4. Controlled scrap disposition
Scrap handling needs its own workflow, with safeguards against accidentally scrapping good material or returning rejected items to production.
- Define scrap eligibility by defect type, severity, or failed repair attempts.
- Require quality or supervisor authorization when appropriate.
- Record scrap quantities, reason codes, material consumption, and financial impact.
- Update inventory and work-order quantities and prevent scrapped units from being processed or shipped.
- Support partial-lot scrap when only some units in a batch fail.
Look for: disposition-specific permissions, electronic approvals, inventory integration, and serialized or lot-level scrap transactions.
5. End-to-end traceability and audit trails
Every routing decision should be explainable after the fact.
- Link inspection results and nonconformance records to the serial number, lot, work order, and applicable process revision.
- Track all rework loops, scrap decisions, approvals, and retest results.
- Preserve the history when a lot is split between rework, scrap, and acceptable production.
- Record who or what initiated each action, when it happened, and why.
Look for: unit- and lot-level genealogy, timestamped audit trails, revision control, and electronic records that can be retrieved for audits.
6. Integration with inspection equipment, QMS, and ERP
Automatic routing only works reliably if the MES receives trustworthy inspection data and keeps other systems synchronized.
- Collect results from test equipment, scanners, gauges, and automated inspection systems.
- Integrate with QMS workflows for nonconformance, corrective action, and approvals.
- Synchronize scrap quantities, material inventory, and production order status with ERP.
- Support reliable retries and duplicate-event handling when systems or networks fail.
Look for: documented APIs or industrial interfaces, equipment connectivity, event logging, and clear ownership of quality and inventory records. ISA-95 is a useful integration reference.
7. Exception monitoring and quality analytics
Supervisors should be able to see whether the routing rules are working and where defects are accumulating.
- Alerts for failed inspections, unresolved holds, and overdue dispositions.
- Dashboards for rework rate, scrap rate, first-pass yield, and repeat defects.
- Analysis by defect type, machine, station, shift, and product.
- Escalation when a defect recurs or exceeds a defined threshold.
Look for: real-time alerts, configurable escalation rules, and reports that connect quality outcomes to the production operations that caused them.
Example: How the ideal workflow should behave
Inspection result received
Measured value, pass/fail, defect code
MES evaluates routing rules
Record nonconformance and apply the required hold
Pass
Continue normal route
Rework
Repair, then reinspect
Scrap
Authorize and record
All paths retain traceability. Reworked units must pass the required reinspection before release.
How to evaluate MES vendors
Use a live demonstration rather than accepting a feature checklist. Ask the vendor to configure and run these scenarios in a test environment:
| Test scenario | What the MES must demonstrate |
|---|---|
| Automatic defect routing | A specific defect code sends a unit to its designated rework station without manual dispatch. |
| Mandatory hold | A failed unit cannot advance to the next operation or shipping. |
| Failed reinspection | A repaired unit that fails again follows the configured retry, escalation, or scrap rule. |
| Partial-lot disposition | A batch of 100 units can send 10 to rework, scrap 5, and continue 85, with quantities reconciled. |
| Authorization controls | Operators cannot perform restricted scrap or release actions without the required approval. |
These scenarios reflect routing, partial processing, disposition, and traceability capabilities documented in manufacturing execution systems, including SAP's MES guidance and modern quality-management workflows.
Which capabilities should be non-negotiable?
MES vendor checklist
of selected
[Copy checklist]
My recommendation: Give the greatest weight to the routing engine, enforced quality holds, and the ability to configure defect-specific rework and scrap dispositions without custom code. The most important proof is that the MES controls what physically happens next—not just that it logs what went wrong.
Sources cited in this answer9
- isa.orgISA-95 Standard: Enterprise-Control System Integration
- vechr.comQuality, Traceability & Genealogy | VECHR MES
- hegongsoft.comRockPlus MES Manufacturing Execution System - Work Orders, Process Control, Error-proofing & Traceability | Hegong Software
- vechr.comRecipe, Routing & Process Design
- synesisintl.comProduction Work Orders — Synesis MES
- help.sap.comSAP Manufacturing Execution