Over decades, manufacturers have invested heavily in tools such as CAD, PLM, ERP, and MES, with the hope that digital transformation initiatives could establish authoritative product definition across the enterprise.
Yet despite those investments, a critical flaw remained.
The digital thread does not primarily break between systems.
It breaks at file export.
Every day, authoritative product definition leaves governed enterprise systems — through native CAD exports, neutral formats like JT and STEP files, PDFs, screenshots, and countless other derivatives. That content is then shared across engineering teams, suppliers, manufacturing operations, service organizations, aftermarket teams, and an expanding ecosystem of enterprise applications.
Manufacturers worked within that operating model because it reflected the technological realities of that time. Today, as products become more complex and more people, processes, and applications depend on product definition, that operating model's flaw may be the industry's biggest issue.
Where Governance Actually Breaks
Most digital thread discussions focus on system-to-system integration — how CAD, PLM, ERP, and MES exchange data. Those connections matter, but they're rarely where governance actually fails.
Governance breaks the moment product definition leaves the authoritative system. Every file export — JT, STEP, PDF, screenshot, PowerPoint slide — creates a copy that exists outside the revision control, configuration management, and lifecycle processes that made it authoritative in the first place. That copy travels through email, shared drives, and chat. And the familiar questions begin:
- Is this the latest revision?
- Who has it?
- Has it been shared outside approved channels?
- What happens when the design changes?
These aren't edge cases. They're the predictable consequences of file-based distribution.
How File Distribution Became the Default
File-based workflows became the industry's operating model for a practical reason: they worked given the constraints of the time. Native CAD and PLM environments weren't built to serve every downstream user. Large assemblies were slow to load, bandwidth was limited, and engineering workstations weren't practical for suppliers, manufacturing, or service teams.
Lightweight formats made it possible to distribute product definition to downstream users. Over time, processes were built around those workflows, and what started as a workaround became the default.
The problem is no longer getting information out of PLM. The problem is what happens to governance once it leaves.
Why the Model Is Breaking Down
The pressures on file-based distribution aren't new individually. Together, they're exposing the limits of an architecture that was never designed for today's scale.
Products are more complex. Supplier ecosystems are more global. Operational lifecycles are longer. And more enterprise applications now depend on authoritative product definition than ever before.
Every additional file copy is another point where revision control, traceability, and configuration integrity can diverge. Organizations respond by adding more process — more validation, more controls, more oversight. But those efforts treat the symptom. Every exported file still creates a copy that must be secured, tracked, and managed independently of the source.
The result: it becomes increasingly difficult to know who has the latest version, where it's been shared, and whether downstream teams are making decisions from authoritative information. More process cannot fix an architectural limitation.
The Architectural Shift
The response emerging across the industry isn't more process around file distribution. It's a different architecture.
Instead of distributing copies of product definition, organizations extend governed access from systems of record directly to the users and applications that need it. PLM and CAD remain authoritative. What changes is how downstream users reach that source — through a secure access layer that stays connected to it rather than receiving a static copy of it.
This doesn't replace existing enterprise systems. It extends their governance model to wherever product definition is consumed.
What This Looks Like in Practice
We call this a governance-preserving 3D access layer, but what it means in practice is simpler than it sounds.
Rather than exporting derivative geometry, the system streams a live, interactive view while maintaining a connection to authoritative product definition in systems of record. What travels across the network is a rendered image stream, not geometry. Users can interact with the model, rotating it, isolating components, accessing metadata, without a copy of the geometry ever leaving the governed environment.
The model stays in PLM. The governance stays intact.
This isn't a future concept. It's operating at enterprise scale today:
- 350,000 users
- 500,000+ daily sessions
- 60,000+ PLM changes per day
- 12 million+ streamed frames per month
Looking Ahead
The next phase of the digital thread won't be defined by moving more product definition to more places. It will be defined by ensuring it stays governed wherever it goes.
The architecture to do that already exists.
COMMENTS