FAQ

Should NCRs be created inside MES or a separate QMS?

In most regulated manufacturing environments, the formal NCR should be owned by the QMS, while the MES should capture the shop-floor event and enforce execution controls such as holds, rework steps, segregation, and operator instructions. The exception is a validated MES with mature QMS functionality that has been explicitly designated as the NCR system of record. What matters is not the application label, but which system provides controlled workflow, traceability, approvals, audit history, and integration with the rest of the quality process.

A nonconformance report is usually more than a defect note from production. It may require material review, disposition, customer notification, engineering review, corrective action, effectiveness checks, and retained evidence. Those activities often sit naturally in a QMS because they cross production, quality, engineering, suppliers, and sometimes customers. If the MES creates an uncontrolled parallel record, the plant can end up with two versions of the truth.

Common operating model

A practical model is for the MES to create or initiate the nonconformance at the point of detection, then pass the formal NCR into the QMS or link to an NCR record created there. The MES remains responsible for execution impact: stopping the job, blocking shipment, routing rework, collecting additional inspection results, and preventing use of suspect material.

The QMS remains responsible for the quality record: NCR numbering or master reference, disposition workflow, MRB approvals, CAPA linkage, customer or supplier communication where applicable, and retained audit evidence. This model works only if status, disposition, part identifiers, serial or lot numbers, and revision context are synchronized reliably.

When MES can own the NCR

MES can be the NCR system of record if it has the required quality controls and the organization has validated that use. Typical prerequisites include controlled workflows, role-based approvals, electronic signatures where required, immutable audit trails, attachment and evidence control, disposition management, CAPA or RCCA linkage, reporting, record retention, and change control.

This is site-specific. Some MES platforms include strong nonconformance management. Others only record defects or exceptions. Calling a defect screen an NCR process does not make it suitable for regulated quality records.

Where split ownership fails

The risky pattern is creating NCRs independently in both MES and QMS without a clear system of record. Common failure modes include mismatched NCR numbers, unresolved material status, missing disposition evidence, rework performed before approval, ERP inventory not reflecting quality hold status, and CAPA records that cannot be traced back to the production event.

Brownfield plants are especially exposed to this. MES, ERP, PLM, QMS, inspection systems, and maintenance systems often have overlapping part, serial, routing, and revision data. Full replacement is usually unrealistic because of qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, change control, and long equipment lifecycles. A controlled integration pattern is usually more credible than trying to force all NCR activity into one new platform.

Key integration points

  • MES: defect capture, operator context, work order, operation, machine, tooling, serial or lot traceability, rework execution, and production hold enforcement.
  • QMS: formal NCR workflow, MRB disposition, CAPA linkage, approvals, audit evidence, and quality record retention.
  • ERP: inventory status, scrap transactions, cost impact, shipment blocks, and material availability.
  • PLM: product definition, revision context, engineering changes, and approved technical data.
  • Maintenance or EAM systems: equipment-related defects, calibration issues, and asset work orders when equipment condition contributed to the nonconformance.

The decision should be documented in the quality system architecture: which system is authoritative for the NCR, which systems may initiate it, how IDs and statuses are synchronized, and what manual controls remain. Without that clarity, the tool choice becomes a compliance and traceability risk rather than an operational improvement.

Related Blog Articles

Get Started

Built for Speed, Trusted by Experts

Whether you're managing 1 site or 100, Connect 981 adapts to your environment and scales with your needs—without the complexity of traditional systems.

Get Started

Built for Speed, Trusted by Experts

Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.

{ "@context": "https://schema.org", "@type": "BreadcrumbList", "@id": "https://connect981.com/faqs/should-ncrs-be-created-inside-mes-or-a-separate-qms#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Connect 981", "item": "https://connect981.com/" }, { "@type": "ListItem", "position": 2, "name": "FAQs", "item": "https://connect981.com/faqs/" }, { "@type": "ListItem", "position": 3, "name": "Should NCRs be created inside MES or a separate QMS?", "item": "https://connect981.com/faqs/should-ncrs-be-created-inside-mes-or-a-separate-qms" } ] }