January 17, 2025
IpX Director of Enterprise Systems and Processes
As of January 2025, it’s clear that no PDM (Product Data Management) or PLM(Product Lifecycle Management) software has yet been developed to manage and release datasets independently of item revisions. Let’s explore why these systems are still structured around item revisions rather than enabling independent dataset lifecycle management.
Modern PLM systems trace their origins back to early PDM systems. Initially, PDM systems were designed to centralize essential product data, such as CAD files, engineering drawings, and technical documents. This centralization helped teams manage revisions, control access, and maintain consistency across product data. Key features included version control, secure storage, and CAD/document management—capabilities focused on supporting design teams’ workflows.
As organizations grew and products became more complex, the limitations of PDM systems became apparent. Companies required systems that could not only store and manage data but also connect it with specific workflows and processes. Some PDM systems began integrating basic workflow capabilities, linking data with engineering change management (ECM) processes. This integration standardized how updates, changes, and approvals were managed.
However, as products advanced through design into manufacturing, quality assurance, and supply chain workflows, traditional PDM systems faced limitations. To meet cross-functional needs, many providers evolved their solutions into more comprehensive PLM systems. These systems expanded access to product information across departments like manufacturing, procurement, sales, and customer support, supporting the full product lifecycle.
Despite these advancements, most PLM systems remain structured around item revisions rather than datasets. Each dataset in a product’s design has its own lifecycle, which may not align with the timeline of the overall item revision. However, current PLM systems do not easily accommodate this granularity, treating datasets as inherently tied to the item revision itself.
This approach presents significant challenges. Teams working on specific datasets often need to manage and track revisions independently of the overall item. Yet, without tools designed to handle these scenarios, managing datasets separately becomes cumbersome and error prone.
This item-revision-centric approach becomes particularly problematic when systems aren’t electronically connected or standardized. Uncertainty about which dataset revisions to use for production can arise, especially in industries where regulatory requirements demand traceability for safety and incident investigations.
ERP(Enterprise Resource Planning) systems often rely on item revisions to ensure consistency and traceability. This reliance further reinforces the need for item-revision-centric processes, even when a more granular approach to dataset management might be beneficial.
As industries evolve, there is a growing demand for PLM systems that can flexibly manage datasets independently of item revisions. Such capabilities would enable organizations to adopt a more granular approach to dataset lifecycle management, ensuring better alignment with project timelines and workflows.
However, this transition has yet to be fully realized. The prevailing approach remains centered on item-revision-based control, underscoring the legacy mindset that continues to shape PDM and PLM systems today.
As we look to the future, a shift toward dataset-centric systems could transform how companies manage product data, offering greater flexibility and efficiency across the product lifecycle. Until then, organizations must navigate the challenges of managing datasets within the constraints of item-revision-centric systems.
Thomas Miller is the Director of Enterprise Systems and Processes at IpX with more than 14 years of experience in enterprise systems, business processes, IT/Cyber Security, and software development within the aerospace, automotive and manufacturing industries. Thomas holds a bachelor's degree is Computer Technology with an applied area of manufacturing, a Six Sigma Black Belt for the North American region, and a CM2- Comprehensive certification.
