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
15 April, 2015

Engineering and manufacturing software industry is well known by very high barrier to entry. It is related to specific professional...

6 May, 2021

Modern cloud technologies are a foundation of SaaS business, which in a nutshell means turn software products into digital services....

5 August, 2015

Products are getting more complex. Sensors, connected devices, cloud software – you can see these elements in almost every hardware product nowadays. Which...

28 March, 2018

I shared my thoughts how collaboration technologies and product development can make a dent into current PLM development trajectories. Digital...

5 July, 2016

New technologies can redefine existing usage patterns. One of the biggest pains when you run you application on the desktop...

24 May, 2013

Product data is one of my favorite topics. People in product development and manufacturing organizations are surrounded by digital data...

10 July, 2018

Back two decades ago, CAD and PLM vendors were competing with ERP for attention of corner suite owners – CIOs...

22 September, 2010

Yesterday, I attended COFES Russia / isicad 2010 forum in Moscow. My presentation on the forum was about my view...

2 May, 2013

Engineers hate PDM. It is an axiom known to all people touching engineering and manufacturing software. Nobody gets up in...

Blogroll

To the top