A blog by Oleg Shilovitsky
Information & Comments about Engineering and Manufacturing Software

Legacy data can torpedo your PLM implementation

Legacy data can torpedo your PLM implementation
Oleg
Oleg
27 May, 2016 | 3 min for reading

curate-data-mess

To select PLM system can be a complicated project. But let’s imagine the moment you’ve made a choice and decided about PLM strategy, vendor and products. So, you might think, the tough part of the job is over. Here is the thing… You have one significant problem to overcome. Legacy data.

The problem is not specific for PLM. There are things you should not expect your computer system to do. Don’t expect computer and PLM system to clean the mess in your company. Even best data management and search technologies cannot do it. The mess must be organized before you can attempt to computerized it and bring PLM system to manage data and processes. If you don’t do it, you will wind up with “computerized mess”.

Razorleaf article The hidden cost of a free PLM migration brings excellent examples of problems you can face when migrating data between to PLM systems – wrong location of files, duplicated data, broken files, wrong indication of relationships. In the example from the article, four types of mistakes in legacy data cost $230,000 in service fees to handle during legacy data import.

The following passage is my favorite:

The fact of the matter is, the reason data loads are expensive and time consuming is not because there are no data load experts or that there are no good tools to help with data loads.  The reason they are expensive and time consuming is the data is complex, sometimes inaccurate, varied and often even undiscovered.  You see, if the data was 100% known, 100% consistent and 100% standard, we’d be happy to load it for free. It would probably take us an hour to setup and kick-off, and the good will that we would receive would make it worth our effort.  But it never happens like this. Never.

It made me think about fundamental disconnect between PLM vendors and customers in the way technology is built and implemented. Customers are unaware about how messy is legacy data. On the other side, vendors are not paying much attention to develop tools and technologies to cope with legacy data problem. The problem is hard to solve, but I wanted to share some ides how to improve the situation.

Legacy data quality assessment tools

Imagine data assessment tool you can run to provide a quantified assessment of your existing data. To develop such tool is not easy, but doable. You will get a rank of data quality. As soon as you can get this number, you can apply it to the cost of PLM project. Better data quality can discount PLM project cost.

PLM data modeling

Most of PLM products demand data cleansing to be made before importing the data. Data storage is cheap these days. To import data and later on to clean and organize it can be an interesting alternative. It requires re-thinking of PLM system and architecture, which can be a challenge for existing systems.

What is my conclusion? Legacy data is tough and complex problem. It can easy torpedo your PLM implementation by bringing an additional cost to implementation. Planning it upfront is a good idea. To develop data quality assessment tool can be an interesting opportunity for service companies such as Razorleaf. In the future PLM architectures with flexible data organization capable to resolve data conflicts and other problems can win over older dinosaurs. Just my thoughts…

Best, Oleg

Want to learn more about PLM? Check out my new PLM Book website.

Disclaimer: I’m co-founder and CEO of openBoM developing cloud based bill of materials and inventory management tool for manufacturing companies, hardware startups and supply chain.

Recent Posts

Also on BeyondPLM

4 6
22 June, 2012

Transformation is coming to many places these days. Look how the internet, mobile, cloud (and not only…) transformed our world....

13 November, 2021

For the last two decades, PLM was developed in the well-established business strategy, product, and technology discipline. A lot can...

30 January, 2015

We live in the era of changes. Think about the impact open source software (OSS) made on the software industry...

17 April, 2009

Last week I discussed the option of having a new PLM format. http://plmtwine.com/2009/03/31/should-plm-20-come-with-a-new-plm-format/. My conclusion is that the new PLM...

30 March, 2016

The Congress on the Future of Engineering Software (COFES 2016) is coming next week. Traditionally, COFES is a great opportunity to...

1 July, 2023

In the fast-paced world of manufacturing business, staying ahead of the competition requires efficient management of product development, manufacturing, and...

10 November, 2010

I spent my yesterday on Dassault Systems Customer conference (DSCC 2010). I had a chance to talk with DS executives...

30 April, 2018

Time ago, I published an article saying Aras PLM lines up against Windchill, Enovia and Teamcenter. Here is the conclusion...

28 May, 2012

The following twitter message from @raykurland of TechniCom, NJ market research and consulting firm woke me up during the long Memorial...

Blogroll

To the top