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
7 September, 2018

Cloud technologies are trending. But engineers are still on the fence to decide about how to move to the “cloud...

14 May, 2010

Are you familiar with the term “Continues Partial Attention“? I found it as a very compelling to what is going...

30 May, 2016

Back in the old days, CAD system was a tool to design product. PDM was a tool too to manage...

30 April, 2010

I’m continuing to hear comments about importance of Open Source for PLM. It comes to me multiple ways during the...

26 July, 2010

When I’m thinking about any PLM project, I can clearly see the step when data available in the organization need...

4 December, 2018

Cloud PDM is the topic I’ve been following for some time. Check my articles about cloud PDM here. One of...

23 January, 2014

Collaboration is not a new buzz in engineering domain. CAD and PLM companies are using this term already few decades...

16 July, 2009

In the past, I had chance to discuss many of the available MOSS 2007 features and capabilities on PLM Think...

17 September, 2022

Manufacturing companies today are under pressure to deliver high-quality products at a lower cost, and quickly adapt to changes in...

Blogroll

To the top