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
1 November, 2016

It has been Halloween night yesterday. This is a time to bring something spooky and scary to my blog. What’s...

27 January, 2009

I’d like to open a series of discussions related to business intelligence and PLM. I had a chance to speak...

26 March, 2025

This week, I’m heading to the 2025 CIMdata PLM Market & Industry Forum in Ann Arbor, Michigan. Note, the Futuristic...

7 September, 2009

Reading Vuuch post “Do Opposite Attract in Business Process?”, I decided to go future and think about opposites in PLM....

16 March, 2013

Last week I posted about changing faces of product development following PI Congress in Berlin. One of the conclusions I’ve...

24 February, 2009

Lately, I’ve seen a growing number of applications introducing the idea of real-time collaboration online on the same document. This...

23 December, 2014

I’m following Facebook search development effort. Maybe you had a chance to read my earlier post about that – Why...

9 February, 2009

I think that PLM in general as well as most other enterprise systems are very non-user friendly. My simple conclusion...

19 October, 2018

Agreement is a hard when it comes to PLM. Ask 3 people about what is PLM and you most probably...

Blogroll

To the top