Usually, the system of record for aerospace NCRs should be the system that controls the formal quality workflow end to end: initiation, review, disposition, approvals, linked evidence, revision history, and closure. In many plants, that is the QMS or a dedicated nonconformance workflow tied to MRB and CAPA controls.
It should not be chosen just because a system is already widely deployed. ERP, MES, and PLM each hold important facts related to a nonconformance, but that does not make them the authoritative NCR record.
The authoritative NCR record should be the place where you can reliably show:
If a system cannot maintain those controls consistently, it is a poor choice for system of record even if it is convenient for operators.
QMS: Often the best fit for the authoritative NCR record because it is built around controlled quality workflows, approvals, evidence, and closure discipline.
MES: Often the best place to detect and capture nonconformance at the point of execution, attach shop-floor context, and stop or reroute work. It is frequently a system of entry, not the final system of record.
ERP: Usually important for inventory impact, material holds, costing, and financial disposition. It is rarely the best place to govern the complete NCR lifecycle on its own.
PLM: Useful when the issue is tightly tied to product definition, change impact, and design authority, but typically not sufficient by itself for shop-floor NCR control and closure.
In practice, aerospace plants often need all four to participate. The question is not which system contains some NCR data. The question is which one is authoritative when records conflict, approvals are challenged, or evidence must be reconstructed months or years later.
In a brownfield environment, the right answer is usually coexistence, not replacement. Many aerospace manufacturers run legacy QMS, ERP, MES, and PLM platforms from different vendors, with custom integrations and long-validated processes. Replacing everything so NCRs live in one new platform often fails because of qualification burden, validation cost, downtime risk, integration complexity, and the need to preserve traceability across long equipment and product lifecycles.
A more realistic approach is to define one authoritative NCR master record and then synchronize only the data each adjacent system truly needs. For example, MES may create the initial event, QMS may own disposition and approvals, ERP may enforce stock status and financial impact, and PLM may receive design-change feedback.
If you are deciding which system should be authoritative, use criteria like these:
If the answer is no on several of those points, it should probably not be the system of record.
Those problems are usually governance and integration problems, not just software problems.
So, the practical answer is: use the QMS or dedicated NCR quality workflow as the system of record in most cases, unless another platform demonstrably provides stronger control of approvals, evidence, traceability, and closure in your environment. MES, ERP, and PLM should usually remain connected systems of entry, execution, material control, or design context rather than the sole authoritative NCR record.
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.