Shawshank Redemption for the Digital Thread
Socrates once suggested that marrying a good PLM system makes you happy; otherwise, you become a philosopher. With an ERP system, however, you are always a philosopher. Murphy later postulated that even if you are happy today, it is only a temporary condition. More recently, Dr. House insinuated that eventually, everybody lies, dies, and migrates – provided, of course, they have something left to migrate from.
For thousands of years, engineering and manufacturing were geographically removed from the front lines. This changed roughly a century ago when Western military thinkers began exploring the use of air power for strategic bombing. These ideas were put into practice during WWII with varying success and remained central to Cold War planning. Yet, it was the rise of drone warfare that made such attacks truly sudden, massive, inexpensive, and often unattributable. Industrial and research facilities, along with their associated data centers, have become high-value, “juicy” targets. Indeed, considering the last decade’s global move to the cloud, it now makes calculated sense to go directly after the transcontinental cables and major regional hubs of AWS or Oracle.
Paradoxically, after years of proselytizing for the elimination of engineering and manufacturing information silos, digital thread champions like Dassault Systèmes, Siemens, and PTC have created infrastructure silos of their own: massive, highly visible “Digital Warehouses” that any $500 FPV drone or $20,000 Shahed can now find on Google Maps. A customer tenant is pinned to a specific geographic region for data residency and latency reasons. If an entire AWS region goes dark or the transcontinental cables are severed, that tenant is effectively offline. There is still no automatic “failover” that lets an engineer in Paris seamlessly keep working on a Singapore-based server if the European hub is being violently “reformatted.” Here, a legitimate European push for sovereign deployments within each country’s national borders may actually play a cruel joke, making them significantly more vulnerable compared to those spanning the vast, politically unified American landscape.
Furthermore, regarding the ongoing friction between the United States and various European nations: while the “spouses” may eventually reconcile and continue living together reasonably peacefully, there is a distinct possibility of a “friendly” divorce – or a total breakdown of the relationship. This raises existential, binary questions. Will AWS centers in Europe remain operational if the geopolitical bridge snaps? Will Boeing still be able to use CATIA if the Atlantic becomes a digital wall?
Speaking of Boeing and other aerospace and defence companies, when they started their long-term archiving initiatives, the “messy divorce” scenario was hardly in their thoughts. Nowadays, a combination of AP242 (STEP and JT) and PDFs constitutes a major pillar of any engineering and manufacturing survival strategy; the increasing proficiency of artificial intelligence tools in processing PDF-based technical documentation only reinforces this approach. In this regard, both cloud-based and locally deployed LLMs (notably those from China) appear to be making legacy OCR software increasingly obsolete. Consequently, reading about European concerns that PDFs need to go away because they are not sufficiently accessible feels as Mr. Bean-style comical as European defence projects stipulating requirements for carbon neutrality.
The artificial intelligence wave also offers a solution to one of the major challenges companies face when planning an escape from their respective “PLM Shawshanks”: the staggering loss of productivity caused by the need to retrain users. By shifting a significant portion of user interaction from a highly proprietary vendor UI/UX to a natural language interface operated in plain English, we dramatically reduce the dependency on system-specific operational routines. The future for many applications, such as PLM, is indeed a chat window. Moreover, it can be argued that the increasing proficiency and quality of the code generated by Claude and its competitors allows the previously trapped customers to maintain their own reliable, easily migratable, and cheaply maintained user interfaces running on top of the PLM vendors’ applications.
A proper setup of an MCP in the engineering and manufacturing environment further breaks the cognitive link between users and various proprietary systems. Chat-based interfaces become the principal method of communication with systems using various APIs. Text becomes the “glue,” linking disparate systems together. This is conceptually similar to the earlier age of network connectivity via adapters, routers, and cables – simply another layer of abstraction. For example, MCP for 3DEXPERIENCE becomes invaluable in managing materials, tolerances, and standards across different frameworks.
Naturally, Murphy is lurking in the shadows, and corporate AI governance boards are rightly worried about the rollout of their AI initiatives. Implementing MCP or OpenClaw without robust security is equivalent to handing car keys to a child: a direct invitation to the kind of catastrophic scenarios seen in recent global hacks. The unified data layer of modern digital thread systems is an enormous soft underbelly for anyone breaching the application fence.
Yet the solution is rather straightforward. Technically speaking, a resilient security setup in our context encompasses on-premises deployments, protected skills libraries, prompt monitoring, proper authentication, and the generation of GVT tokens for specific credentials. Add regular hygiene in the form of zero-trust security, software supply chain security and validated containers, and you should be well-set for the upcoming fireworks.
In addition to his eternal marriage advice and his prophetic dislike of democracy, Socrates famously suggested that knowing thyself is a prerequisite to everything else. One of the greatest advantages of the AI age is that it provides a rich toolset to comprehend one’s business, technical, and application environment and then act better and faster than was ever possible in human history. In that happy spirit, and temporarily keeping Murphy on a leash, we follow the last line from the Dr. House series: Enjoy Yourself!
