All engineering software vendors publish case studies about successful clients and projects. Good case studies help others understand the specific value a software product or service can be. But what about projects that nobody wants to talk about?

Two recent articles here have discussed the business value of legacy data, and how to decide what data is worth putting into the new PDM.

• Understanding the Business Value of Legacy Data, Part 1
• Understanding the Business Value of Legacy Data, Part 2

Today I want to tell you about an engineering legacy data project that will never make it into a case study. They say experience is the best teacher, when it comes to failure I think it is better to observe it second hand than to experience it directly.

By the way, I know this is a guest post for Synergis, but this case does not involve Synergis Software or any of its customers. I am going to be intentionally vague to avoid embarrassing those involved and to avoid violating confidentiality agreements.

In the first article in this series, I introduced the importance of clear thinking about legacy data when installing a product data management (PDM) system. I spent time recently talking to Todd Cummings, VP of Technology, about his nearly 20 years of experience helping companies of all sizes install and use Synergis Adept. One of the first things he told me was “If you haven’t worn that gift tie for several years, then it’s time to donate it to the Salvation Army.” Apply the idea to legacy data, Todd said, not as a hard-and-fast rule but “as more of a healthy challenge: don’t assume legacy data should automatically be put into the PDM/EDM system.”

It is all about the business value of the information. Todd advises clients to make business value the lens through which they review legacy data. If data created 10 years ago is still accessed by your field engineers and support team, it stays in.  When it comes to some projects—not all data is valuable. Every business is different.

When a company invests in a new product data management (PDM) system like Synergis Adept, one of the first agenda items is (or should be) to decide what to do with legacy data (product/project information created in the past and not in active current use). When engineering information is first created it is always of high value. But over time, value diminishes. The rate of value decay varies by company. So, how important is it to make older engineering data a part of the new PDM?

Some companies want to sidestep the question. On one hand, some will think the best choice is to only use the new PDM system with current projects. On the other hand, some will think the way forward is to put everything into the PDM. Both of these choices are based on overly simplistic assumptions about the value of data.

There is economic value in connecting people to information; improve the connections and you increase the value of the information.

Consider the analogy in which your manufacturing or construction project is a ditch, and data inside your files is water that will flow through that ditch. What sort of tool are you using to move the dirt and prepare for the water, shovels or backhoes? I would submit that Windows Explorer is the equivalent of a shovel, and product data management (PDM) software is the backhoe. Product Data Management (PDM) moves a lot of data fast. And it does much more than that. PDM also improves access, reuse, sharing, record keeping, and security that affect data files.

After digging the ditch, you have a nice place to store data. But that place to store data is not a static repository. It is a moving river, where data flows freely. Data is created by CAD users, deposited into the river, and then flows downstream to manufacturing shop floors, documentation departments, and customers, and other consumers of the data.

When your data management metaphor is a river, you can gain valuable insights into managing the data in your organization. These four V’s demonstrate things about the rivers of data that can help you understand and solve some of the data problems in your organization.