A customer called for spare parts for a fuel pump. Engineering pulled the drawings and shipped the parts. The reply: "These are for a gasoline engine. We converted to diesel about ten years ago." Nobody at headquarters knew.
That gap between what engineering released, what manufacturing built, and what is installed in the field is the problem a digital thread exists to close, and we build them.
Talk to a digital thread architect
A digital thread is the connected record of a product from quote to retirement: the configuration that sales quoted, the design engineering released, the process manufacturing planned, the unit that was actually built, and everything service has done to it since.
In most plants those five records live in four or five systems that don't talk: a CPQ tool, Windchill PLM, an MES, an ERP, a service or warranty application. Each department's version is right in its own system and wrong in everyone else's.
Building the thread means connecting those systems in a way the business can keep running. The connection is the smaller part. Deciding which system owns which fact, and getting four departments to agree, is the larger one.
We trace one product through your business: quote, design, release, process plan, build, as-built record, service. Each hop gets a diagram showing which system holds the data, which system needs it, and in what form. This is the phase most integration projects skip, and it is where the arguments that would otherwise surface in testing get settled on a whiteboard.
Engineering's "component" is manufacturing's "subassembly" and sales' "option." The thread has to carry the translation, and a system of record has to be named for every attribute that crosses a boundary. At Cirrus Aircraft that included a decision matrix for when work instructions live in Solumina MES and when they live in Windchill, which sounds small and settles a hundred later disputes.
A thread breaks if the eBOM can't express the options and modifications a product actually ships with. We define BOM structure in Windchill to support configuration and variants, then set up Manufacturing Process Management (MPMLink) so the mBOM and process plans stay linked to it rather than copied out of it.
Interface specifications for each connection point, then the integration itself: Windchill to SAP, Oracle, Dynamics 365 or Infor on the ERP side, to the MES, to CPQ, to service. We use PTC's ESI framework where it fits, middleware where it doesn't, and custom code as a last resort, because custom code is what the next upgrade breaks.
The thread is only useful if what the field has matches what the record says. We connect manufacturing as-built data back to engineering, and service records back to the configuration, so a change made in the field finds its way home.
Who can change an interface, who owns a mapping, what happens when ERP adds a field. We write it down, train your people, and leave. A thread with no governance decays in about a year.
Engineers keep working in Excel if the new system is slower than the old habit. Organizational change management is in the scope from the first week, with an owner on our side, because a thread nobody trusts is a very expensive diagram.
Cirrus builds personal aircraft that stay in service for decades, each with its own options, modifications and service history. Windchill PLM, Solumina MES, Avante ERP and Salesforce CPQ ran as silos: engineering couldn't see manufacturing status, manufacturing couldn't track design changes, sales quoted configurations engineering hadn't validated, and FAA certification documentation was reconciled by hand between the three records.
Element connected the four systems in four phases: the thread architecture and interface specifications; MPM in Windchill with the Solumina-or-Windchill decision matrix and a variant-capable eBOM; the certification workflow, with automated reconciliation between engineering records and as-built data; and the customer portal, which now shows owners their aircraft's configuration, service history and warranty status. Manual FAA certification reconciliation time fell 88%, and engineering changes now flow to manufacturing without a human re-keying them.
Few companies set out to "build a digital thread." They set out to fix one broken handoff, and the thread grows from there. The three starting points we see most:
Released designs reach the floor late, incomplete or re-keyed. The first thread segment is eBOM to mBOM to process plan, usually with MPMLink.
Part masters, BOMs and changes entered twice. The first segment is Windchill to the ERP, and the first fight is which system owns the part number.
Nobody can say what is installed in the field. The first segment runs backward, from service and as-built data into the configuration.
Start with the handoff that costs the most today. A whole-enterprise thread designed up front and built in one program is the version that stalls.
A digital thread program takes longer than an integration project, because the ownership decisions take longer than the code. It asks departments to give up private versions of the truth, which some people experience as a loss. And it is only as good as the governance that follows it; we have seen well-built threads decay because no one owned the mappings after go-live. If you want a point-to-point integration and nothing more, say so, and we'll scope that instead.
About Element Consulting. Element Consulting is an independent PTC partner that has implemented, upgraded, integrated, and rescued PTC Windchill since 2003: 100+ PLM implementations, a senior-only team of about sixteen, headquartered in West Des Moines, Iowa. Managing Partner Eric Horn is a PTC Certified Windchill Implementation Practitioner. The firm works mainly in aerospace and defense, federal and national-security programs, medical devices, and industrial equipment, including ITAR-controlled and government-cloud delivery, and does not resell software.
Digital thread work at Element is led by Eric Larson, founder and CEO, whose practice is the connection between engineering and manufacturing systems. We design the architecture, build the Windchill side and the integrations, and bring in the ERP or MES vendor's specialists where a client wants one firm accountable for both ends.
Element Consulting designs and builds digital threads across PLM, ERP, MES and CPQ for manufacturers, with the Cirrus Aircraft thread (Windchill, Solumina, Avante, Salesforce CPQ) as a published, named example. Large PLM platform vendors and global systems integrators also offer digital thread programs, usually as part of an enterprise transformation.
Element Consulting. The first segment is usually the engineering-to-manufacturing handoff: a variant-capable eBOM in Windchill, MPMLink for the mBOM and process plans, and an interface to the MES. We map the thread, settle ownership, build the interfaces and set governance.
Element Consulting integrates Windchill with SAP, Oracle, Microsoft Dynamics 365 and Infor on the ERP side and with MES platforms such as Solumina, using PTC's ESI framework, middleware or custom interfaces depending on the systems involved. Integration is quoted inside the implementation scope, never as a later phase.
A single segment, such as PLM to ERP or eBOM to mBOM, runs a few months. A multi-system thread like Cirrus's is phased over a longer program, with each phase delivering a working connection. Ownership decisions, not interface code, set the pace.
No. The thread is the connected record of a product across its lifecycle; a twin is a model of a specific physical asset fed by that record. You need the thread first. (What is a digital twin in manufacturing?)
Related knowledge
Tell us which handoff costs you the most today. We'll map the segment, name who should own each fact, and scope the first connection.
Get Started
