Over a decade ago, I published A Brief History of PLM, tracing the evolution of Product Lifecycle Management (PLM) through the parallel digital transformations of engineering (from CAD and PDM) and manufacturing (from MRP to ERP). At that time, my focus was largely on cataloguing the capabilities and processes that had shaped the discipline—how each generation of tools helped teams manage complexity and control product data across their respective domains.
Ten years later, my perspective has matured. PLM has grown far beyond its engineering roots. What once centered on data and systems now centers on connectivity and cognition—how people, data, and processes interact across an increasingly intelligent ecosystem. This is at least the aspiration and trajectory of travel. PLM is shifting from being an engineering repository to the backbone of enterprise orchestration: a means of achieving timely and accurate impact assessment across the innovation lifecycle.
This revised edition reflects that shift in thought—looking not only at technological milestones but at how the evolving mindset around integration, lifecycle thinking, and data intelligence continues to redefine innovation itself.
1960s–1970s: MRP and Early CAD—The Birth of Digital Enterprise
The journey begins in the mid-20th century with the emergence of Material Requirements Planning (MRP) systems. Designed to automate production scheduling and inventory control, MRP replaced manual calculations with computational precision. Joseph Orlicky’s Material Requirements Planning (1975) made the concept mainstream, demonstrating dramatic gains in manufacturing efficiency through better data management.
Simultaneously, engineering began its own digital revolution with the first Computer-Aided Design (CAD) systems. Drafting moved from paper to screen, enabling storage, reuse, and sharing of digital product data. For the first time, product information became a structured digital asset—although design and production remained distinct, disconnected silos.
1980s: PDM and MRP II—Managing Complexity
By the 1980s, the growing volume of design data demanded better control. Product Data Management (PDM) systems emerged to manage CAD files, revisions, and engineering changes—formalizing traceability and configuration control.
In parallel, MRP evolved into MRP II (Manufacturing Resource Planning), expanding its reach to labor and machine scheduling. These developments laid the foundation for Enterprise Resource Planning (ERP), integrating manufacturing with procurement, finance, and logistics.
Progress was evident, but integration was not. Design engineers worked in PDM; planners worked in MRP II. Information exchange was slow and often manual—a challenge that would define the next chapter.
1990s: The Rise of PLM and Cross-Functional Integration
The 1990s introduced a new concept: Product Lifecycle Management. Popularized by CIMdata and early pioneers such as Dassault Systèmes, PLM sought to unify all product-related data—from concept to delisting and disposal—within a single framework.
Building upon PDM, PLM introduced structured workflows, approvals, and Bill of Materials (BOM) management. It also encouraged cross-functional collaboration between R&D, manufacturing, quality, and service. At the same time, ERP systems matured and spread enterprise-wide, becoming the backbone for business operations.
Organizations began to see the need to connect Science/R&D/engineering (PLM) with the wider enterprise (ERP), including procurement, finance, asset management, compliance, etc. Stage-gate methodologies provided structure for cross-departmental collaboration. Yet, despite progress, integration remained largely aspirational—limited by fragmented databases and incompatible data models.
2000s: Digital Lifecycle Orchestration and the Extended Enterprise
The 2000s marked a turning point. PLM platforms such as Siemens Teamcenter, PTC Windchill, and Dassault Systèmes ENOVIA started to integrate not only with CAD and ERP but also with CRM and MES systems. The idea of a single source of truth gained traction.
A change in a design model could now, in principle, trigger updates across purchasing, production, and service domains. Supplier collaboration portals extended PLM into the broader value chain, fostering co-design and early supplier involvement.
The internet era accelerated these shifts. Web-based tools allowed distributed teams to collaborate on shared models and workflows. However, many integrations remained batch-based—overnight data transfers rather than real-time connections.
Even so, PLM was becoming more than a system for engineers; it was the connective tissue of the digital ecosystem.
2010s: The Digital Thread and Twin Revolution
As products became smarter, software-defined, and interconnected, the digital thread emerged as a unifying vision. It links every product artifact—mechanical and electrical designs, software modules, recipes, formulations, and specifications—into a seamless flow. This thread enables traceability, insight, and collaboration across both physical and virtual lifecycles.
Digital twin became a natural extension: dynamic virtual models that simulate, monitor, and predict real-world behavior. IoT, cloud computing, and AI connect these twins to actual product performance, allowing continuous optimization and learning across hardware, software, and consumables alike. PLM evolved from document management to intelligent lifecycle orchestration, supporting complex, hybrid products and services.
For the first time, the digital and physical worlds were not merely aligned—they were continuously connected.
2020s: Convergence, Circularity, and Cognitive PLM
The 2020s bring a convergence of IT, OT, and ET—integrating engineering, operations, and enterprise systems into real-time, intelligent ecosystems. Modern PLM is no longer just a repository; it is the backbone of digital enterprise orchestration.
Engineers can visualize field data from sensors, software logs, or production lines directly within PLM dashboards. Operators follow AR-guided workflows generated from the latest digital twin. Recipes and specifications are managed alongside CAD models and software modules, ensuring traceability, compliance, and alignment across the enterprise.
Artificial Intelligence accelerates innovation. Generative design explores thousands of alternatives. Predictive analytics optimize supply chains and production. Cognitive data threads connect structured and unstructured data, enabling organizations to learn from every iteration, adapt designs, and anticipate changes proactively.
Sustainability is becoming integral: lifecycle management includes carbon tracking, recycling, and reuse, feeding insights back into product development. The pandemic further proved that cloud-based, collaborative PLM infrastructures are essential, not optional.
From Control to Cognition
A decade ago, PLM discussions focused on control, integration, and ensuring a single source of truth. Today, the frontier is contextual intelligence: systems and people interpreting data to make informed, timely decisions.
Those that fail to learn from history are doomed to repeat it.
Commonly attributed to Winston Churchill
The evolution of PLM underscores this truth: organizations that cling to siloed, 1990s-era practices risk repeating past inefficiencies, while those that embrace integration, digital threads, and cognitive systems can leap forward in innovation.
The emerging cognitive data thread bridges not just systems, but understanding. It connects design, operations, service, and sustainability data into actionable insights. Through cross-functional analytics, organizations can learn from past product performance, adapt designs on the fly, and anticipate issues before they occur.
The next decade will likely see this convergence deepen: AI, ML, product, procurement, SKU financial performance, and sustainability analytics blending into unified decision frameworks. Innovation will become measurable—no longer about outputs alone, but about the return on innovation: the efficiency, resilience, and value generated across the full product lifecycle.
If the last decade was about digitizing the lifecycle, the next will be about understanding and optimizing it. That, perhaps, is the truest legacy of PLM’s evolution—and the real beginning of cognitive enterprise transformation, where impact, insight, and return on innovation define success.
PDM: Still the Product Foundation
Even in a software- and recipe-defined world, PDM remains essential. It governs engineering content—CAD, software, recipes, and specifications—ensuring traceability, configuration control, and structured collaboration. PDM handles the what of product information; PLM orchestrates the how, when, and why across the enterprise.
Strong PDM practices are critical. Without them, cognitive PLM cannot deliver a true single source of truth or actionable intelligence. In hybrid, multi-domain products, PDM ensures that all contributors—from mechanical engineers to formulators to software developers—work from the same authoritative data set.
What are your thoughts?
Disclaimer: articles and thoughts published on v+d do not necessarily represent the views of the company, but solely the views or interpretations of the author(s); reviews, insights and mentions of publications, products, or services do neither constitute endorsement, nor recommendations for purchase or adoption.
About the Author
