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 March, 2014

The history of databases and database management systems knows many periods. Most of us developed strong association between database management systems...

11 October, 2012

Globalization is a reality of today’s manufacturing environment. It is no unusual to have even small companies distributed across the...

30 May, 2011

Let’s talk about PLM software development today. Rewind pre-Web 2.0 and pre- iPhone era. Life was simlpe. After SolidWorks finally...

20 April, 2009

In one of my previous posts, I already discussed PLM process management: Should PLM develop its own process tools?. In...

23 December, 2015

Excel is the world’s number 1 tool for PLM and BoM management. Excel is beloved by engineers for its simplicity, flexibility...

25 June, 2015

The era of mass production is near the end. The demand for mass customization is coming. We can see signs...

29 July, 2009

Thinking in loud. I’m looking over many user interfaces of PLM systems and reading “Don’t make me think“. Why every...

1 April, 2014

04/01/2014. Newton, MA via @afjplmnews. ENOVIA – the collaborative innovation application brand of Dassault Systemès enables your innovators to benefit from...

23 July, 2013

Touch interface is changing the way we work and think. You can see it everywhere these days. Engineers are not...

Blogroll

To the top