Data Paradigms in PDM

Before the advent of database-driven data management systems, Windows folders were the primary means of indicating the status of a file. We've all encountered the labyrinthine structure of folders attempting to bring some order to complex engineering data. Folder names like "New Items," "Do Not Delete," "Project 1," "Released," "Ready To Be Released," and "Obsolete" are not uncommon. Engineers and designers, known for their creativity, often employ these folder names to define a product's status. However, as imaginative as they may be, relying solely on folder names to manage data status eventually reaches its limits, often resulting in data loss, which can be the catalyst for companies to invest in a comprehensive data management system like SolidWorks PDM.

Curiously, it's worth noting that when companies implement a PDM vault, they frequently replicate the same naming chaos within PDM's folders. However, this need not be the case.

Data management via folders results in a spaghetti soup of folder names

In PDM, the data paradigm fundamentally shifts away from the concept of determining a file's status based on the folder in which it's stored. Instead, the paradigm should revolve around understanding the file's role within a product or its usage within the vault. Is it a subsystem within a larger system? Is it a purchased part? Is it a component of a project tailored for a specific client? Is it source controlled item? This perspective, centered on the file's purpose and function, is a fundamental departure from the traditional folder-based approach to data management. Using the outdated paradigm of folder-based management within PDM is a recipe for what is shown in the image above.

Transitioning from well-established data management methods when designing a new PDM vault can be challenging. The array of tools within the database can initially seem overwhelming and applying them effectively may pose difficulties. However, grasping the intricacies of each aspect of PDM's features and comprehending how they interconnect is crucial for a PDM vault architect. This understanding empowers the architect to meet every requirement of the enterprise efficiently and effectively.