"Legacy Data"

Legacy data can torpedo your PLM implementation

Legacy data can torpedo your PLM implementation

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…

Share
3 reasons why PLM cannot drain product data swamp

3 reasons why PLM cannot drain product data swamp

The amount of data around us is growing. The same applies to engineering and manufacturing companies. Our ability to collect data is astonishing. But we are failing to bring the right data in the right form and at the right time to people. Product lifecycle management software is often recognized…

Share
Who will take on PLM legacy data?

Who will take on PLM legacy data?

Legacy data it painful. Speak to anybody in the business of PDM/PLM implementation and they will tell you that importing existing (aka legacy) data is complicated, time consuming and after all very expensive task. It can easy cut your implementation profits and to increase project time. In past, I was…

Share
PLM Migration and Product Data Rock-n-Roll

PLM Migration and Product Data Rock-n-Roll

I read The PLM State: PLM Migration, No Data Left Behind on Zero-Wait State blog. Read it and make your opinion. Stephen Porter is discussing a very important topic of data migration. I found it interesting. This is my favorite passage: …leaving data behind is not necessarily a bad thing…

Share
PLM and Legacy Data

PLM and Legacy Data

When I’m thinking about any PLM project, I can clearly see the step when data available in the organization need to be loaded into the system. This step is often underestimated from different standpoints: ability to gather and load information, availability of data definitions, availability of APIs and system performance….

Share