Yes. A digital thread can often be built without replacing current MES or ERP systems. In regulated brownfield environments, coexistence is usually the practical path because full replacement can create qualification burden, validation cost, downtime risk, integration complexity, and traceability disruption. The hard part is not the label “digital thread”; it is making trusted links between engineering, planning, execution, quality, maintenance, and records without weakening control of the existing systems.
This usually means building an integration and data governance layer around the systems already in place. MES may remain the system of execution. ERP may remain the system of financial, inventory, purchasing, and planning record. PLM may remain the source for product definition and engineering change. QMS may remain the controlled environment for nonconformance, CAPA, audit, and document workflows. The digital thread connects these records so users can trace what was planned, what was built, what changed, what was inspected, and what evidence supports release or review.
What has to be true for this to work
A digital thread without replacement depends on data readiness and integration discipline. If part numbers, serial numbers, lot records, routings, work orders, inspection characteristics, document revisions, and equipment identifiers are inconsistent, the thread will be fragile. The first failure mode is usually not software capability. It is poor master data and unclear ownership.
Common prerequisites include:
- Clear system-of-record decisions for product definition, routings, work orders, quality records, inventory, and maintenance history.
- Stable identifiers for parts, serials, lots, operations, tools, documents, and inspection characteristics.
- Validated interfaces between MES, ERP, PLM, QMS, maintenance systems, and data platforms where applicable.
- Audit trails and version control that preserve who changed what, when, why, and under which approval.
- Change control for integrations, data mappings, workflow rules, reports, and automated decisions.
What should not be assumed
Do not assume that connecting systems automatically creates a usable digital thread. Point-to-point integrations can move data while still leaving gaps in context, revision control, genealogy, or inspection evidence. Dashboards can show status without proving traceability. Data lakes can store records without resolving which record is authoritative.
It is also risky to assume that every legacy system can support the needed interface quality. Some older MES or ERP installations have limited APIs, custom data structures, undocumented workflows, or manual workarounds that are now part of the validated process. In those cases, the digital thread may need phased coverage, supplemental controls, or a middleware layer rather than a direct integration everywhere.
Where replacement may still be needed
Replacement may be justified when a system cannot support required traceability, cybersecurity, availability, data integrity, or operational control. But in aerospace-grade and similarly regulated environments, replacing MES or ERP is rarely a casual modernization step. It can trigger revalidation, retraining, migration risk, customer notification, audit exposure, and production disruption.
For that reason, many programs start by connecting high-value threads first, such as engineering change to work instruction, work order to inspection result, serial genealogy to nonconformance, or supplier certificate to receiving and release. This reduces scope while exposing whether the underlying data and process controls are strong enough.
The practical answer
A digital thread can be built on top of existing MES and ERP systems, but it has to be treated as a controlled operating architecture, not an integration project alone. The outcome depends on system capability, data quality, validation approach, process ownership, and how well changes are governed over time. It can improve traceability and visibility, but it does not by itself guarantee compliance, audit outcomes, or process performance.