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

PLM and MDM – How to start right?

PLM and MDM – How to start right?
olegshilovitsky
olegshilovitsky
18 August, 2009 | 2 min for reading

Product Lifecycle Management and Master Data Management. I had chance to raise this issue few months ago in my post Will Master Data Management Work for PLM? Few days ago, interesting publication from Gartner about their research in area of MDM and, more specifically, about overlap between MDM and PLM. Andrew White together with Marc Halpern published paper called “Interfacing of PLM and MDM for cross enterprise needs”. The conclusion made by Andrew in his blog article is simple – use a right tool for the right job.
In more detailed way, they explained PLM itself as a not mature software category in comparison to ERP, SCM, CRM etc. With lack of maturity and unclear agreed position and usage of MDM, PDM, PLM prevented earlier exploration of intersection between these domains.

gartner-mdm-white

Now, I’d like to come back to my initial question – how to start right? What is my concern about approach “right tool for right job”? As soon as we speak about corporate and enterprise data and product IP/Knowledge, I think this approach may not work. Today’s enterprise is very siloed, information span across multiple systems – engineering, manufacturing, procurement, supply chain. As soon as a system identify in the particular functional domain, it will not create major conflicts. I see relatively simple approach to position PDM as a system to manage design and engineering data only together with Master Data Management. However, when we come to PLM approach, I see definitely conflict of interest. In my view PLM and MDM strategy has similarity in their approaches to create “single point of truth” in organization.

So, what I see as a possible PLM/MDM strategy? I think, MDM strategy and infrastructure, can provide possible foundation for managing of non-transactional data for product development. This data can be accumulated by MDM and saved for future usage. Today’s PLM implementations are mostly focused around product development, so such MDM infrastructure can be good asset PLM can use to achieve long term data retention and other data management needs. At the same time, such approach can bring significant investment into both PLM and MDM systems and probably can be acceptable only by large enterprises.

I’m interested in discussion, if you had any experience with MDM and PLM system co-existence.
Best regards,
Oleg

Recent Posts

Also on BeyondPLM

4 6
13 September, 2017

In the old manufacturing days, engineering activity was very much disconnected from manufacturing. Long development cycle provided enough luxury and...

25 March, 2015

I’m in Warwick today getting prepared for Develop3D Live conference, which will be tomorrow. The full conference agenda is here....

10 January, 2012

Integration is an important topic in PLM. Few days ago, I was reading Aras’ blog – Understanding of integration and...

22 April, 2013

The last decade was all about 2.0. To me, 2.0 trend was about how to re-think existing norms and behaviors,...

28 June, 2018

Manufacturing is transforming. New business models, new products, new technologies. Manufacturing is becoming decentralized and connected. PLM companies are swimming...

20 April, 2017

Cloud PLM adoption is on the top of minds for software vendors and PLM researchers. Catch up on the topic...

20 September, 2019

The weekend is coming and this is a time for some PLM dramas. Engineering.com and Verdi Ogewell is usually not...

7 August, 2020

Unless you lived under the rock for the last few years, you’ve heard about Digital Twin. Wikipedia article gives a...

30 October, 2014

Enterprise IT adoption cycle diagram made by Simon Wardley made me feel sad and funny at the same time. I found...

Blogroll

To the top