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
25 March, 2015

I attended PI Congress in Dusseldorf last month. During the conference I had a chance to share my thoughts about...

3 December, 2009

Common definition of the process: “a set of activities leading to the desired outcome.” Despite such a simple and straightforward...

1 October, 2011

If you developed or implemented PDM or PLM system, you probably know that definition of users, groups and roles are...

12 August, 2010

Scaling up is a tough problem. I want to talk today and PLM Software scalability in unusual aspects – business...

1 July, 2020

I’m learning more about Teamcenter X. If you missed my previous article, please check it out here – What did...

26 January, 2013

Data. Conversion. Interoperability. Translation. The discussion about these topics is endless in CAD/PLM world. Customers are looking for interoperability between...

10 November, 2014

Engineering.com article by Verdi Ogewell earlier today is introducing a next step of PLM vs. ERP battle for ownership of...

31 October, 2019

PTC acquired Onshape last week. Check this link for the PTC press release and more information. I’ve been following media,...

9 July, 2012

When it comes to “cloud PLM”, the discussion about “security” is almost inevitable. This is one of the top concerns...

Blogroll

To the top