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
27 January, 2021

Unless you lived under the rock for the last several years, you’ve heard about SaaSification. This funny term was changing...

14 December, 2011

Mobile becomes more and more important in our everyday life. “You don’t have to be at your desk to make...

27 September, 2017

Photo credit: Tesla Robot Dance by Steve Jurvetson It is hard to argue about value proposition behind “PLM projects”. PLM story...

30 August, 2026

Engineering organizations have become extraordinarily good at keeping data. CAD files are stored. BOMs are managed. Revisions are controlled. Changes...

27 October, 2017

Single version of truth is a mantra sold by most of enterprise software vendors. PLM is included. I think, PLM...

2 May, 2018

Cloud PLM debates are over. Every single PLM vendor can do it today. Even, Siemens, which is a very conservative...

14 June, 2013

We love word “disruptive”. It is so nice and tasty. However, very often, we use it without thinking twice what...

15 March, 2018

One size doesn’t fit all. It is very true when it comes to anything related to manufacturing and engineering. Every...

8 January, 2019

Digital Transformation seems to be one of the most popular buzz everywhere these days. You can hear it everywhere in...

Blogroll

To the top