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
31 March, 2009

I’ll start with a disclaimer. I understand that to start a “format discussion” is at least as dangerous as starting...

21 October, 2013

Shake-ups are not a surprise these days. It happens all the time and especially in technological fields. The last decade...

29 June, 2016

One of the news that caught my attention yesterday was Autodesk announcement to acquire CADSoft Eagle PCB design tool from...

13 January, 2012

Remember my post few weeks ago about PLM highway? Boston is certainly a place where you can see a concentration of...

5 January, 2016

Almost hundred years ago Henry Ford started to build River Rouge factory. That was a giant plant that literally took...

10 November, 2010

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

29 June, 2010

My post Open vs. Closed PLM Debates last week and related Fortune CNN Money Blog article by Jon Fortt –...

13 July, 2012

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

7 September, 2017

PLM business has a clear potential to grow. The last two weeks demonstrated that some investors have strong believe in...

Blogroll

To the top