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
18 December, 2012

Our digital and real lives are getting more and more connected. Think about our web experience these days. Mobile devices,...

11 February, 2010

Recent presentation on SolidWorks World 2010 about evolution of PLM drove me to think about what is the future of...

24 October, 2014

The number of SaaS businesses is growing these days. You probably had a chance to read my CAD, PLM and...

21 August, 2020

Omne Trium Perfectum. Friday is a special day and I’m always trying to make Friday blog special. I’ve been thinking...

11 August, 2021

I took a break last week from blogging while spending my family vacation time on Cape Cod. It was also...

5 December, 2017

Nobody is buying PLM. PLM projects are usually “sold” to customers. And this is not an easy job. Many of...

6 February, 2013

I’m on the road in Europe this week. Europe met me with snow in Zurich and not very reliable internet...

3 August, 2010

Collaboration is a widely used term, and I found it sometime even overused. Collaborative development, Collaborative PDM, Collaborative PLM, Collaborative...

4 November, 2017

Lot of things is already written about PLM implementations. In my view, PLM implementations are still holding the top complexity...

Blogroll

To the top