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

PLM Definition and ERP Implementation Patterns

PLM Definition and ERP Implementation Patterns
Oleg
Oleg
15 October, 2011 | 2 min for reading

Product development and manufacturing is very different from company to company. Therefore, I’m not surprised anymore when I see multiple ways companies are defining what is Product Lifecycle Management. Some time ago, I started to gather these definitions in order to share with the readers of my blog. I was reading Aras’ blog and watching Nexteer presentation by David Lien and Bob Lipscomb about strategies, selection and implementation process of Aras PLM.

PLM Definition – Nexteer.

PLM is a global system that manages the complete set of product and process definition data, information, business processes, and the roles of peoples assigned with with a product through all stages from its creation to retirement.  The PLM system is the central information hub for everyone associated with a given product, streamlining product and process development and facilitating communication among those working with a product.

You can watch the following presentation to see more about PLM implementation at Nexteer, which I found very interesting

http://www.youtube.com/watch?v=VRNATYojq_Q

PLM and ERP Implementation Patterns

The presentation made me think about the pattern of “singularity” in PLM implementation. I call it ERP-pattern. Look on the following slide. The idea of customer to centralize all data related to product and processing isn’t very new. This is so called “single point of truth” implementation is still very popular.

At the same time, future explanation about keeping PDM implementation and synchronizing between PLM, PDM and ERP shows some weakness. To move all data to a single place is very complicated process. To make it in steps is probably a viable strategy. Keeping PDM and ERP “as is” just a confirmation of that.

What is my conclusion? Manufacturing clearly wants to optimize product development processes across the enterprise. The single point of truth is leveraging the simplicity of SQL-database experience for the last 20 years. At the same time, centralization and replication of data are complicated and expensive processes. Managing phased implementation creates a set of new problems related to the ability to maintain the data transformation and synchronization within the time. I’m interested to know your opinion. Do you see any alternatives the singularity in PLM? Just my thoughts…

Best, Oleg

Recent Posts

Also on BeyondPLM

4 6
8 December, 2010

Navigate your browser to the following link. GSA is moving to Google Apps. According to the Google blog, US GSA...

12 November, 2023

We live in a digital world. It doesn’t matter what we do and what business we are in, getting information...

7 March, 2018

CIMdata announced new research completion about PLM Status and trends. A quick note about it can be found here. A...

28 June, 2021

Back in the old days of enterprise software, the discussion about best of breed vs single vendor was very popular....

21 July, 2009

In the early beginning of the Internet in the late 80s of 20th Century, MIT professor Tom Malone started to...

12 March, 2020

Earlier last week, I attended the PTC Onshape Product Development Cloud Forum. Check out my article here () if you...

18 December, 2022

Integration was a big deal for manufacturing companies implementing PLM systems for a very long time. It is very rare...

13 July, 2012

Design and engineering world are changing fast these days. 20 years ago, the objective of CAD and other engineering software...

4 May, 2017

In the past department stores were build around the idea that consumers will come to the store for inspiration and...

Blogroll

To the top