[sixdimensional]

I am not 100% sure, but here is my theory. Master data management is the superset, covering tools and systems designed to manage data from many domains. Originally, ERP and large enterprise systems were where the “master” records were stored.

In recent years there has been some backlash against ERP systems, e.g. Oracle. Also, master data management was seen negatively in an increasingly federated system world - one with the Bezos mandate, microservices, reduced centralization, etc.

I’ve seen a general unbundling and remarketing of enterprise solutions in ways to make them more palatable to the newer generations.

Therefore, to escape the legacy image, ERP -> master data management -> product data management -> product information management.

I think it has to do with the evolution from big centralized systems to federated/distributed/independent but interconnected ones, and the corresponding branding/marketing changes over time. Especially to avoid terms seen as “legacy”.

The marketing might be a bit short sighted, but that is an opinion. Maybe the branding sells more copies, and for most of these companies that is all that matters.

[Rochus]

Don't forget that Product Lifecycle Management (PLM, of which PDM is a primary area) is a discipline by itself, even covered by a couple of big standards (e.g. the famous ISO 10303 series for product data representation and exchange). PLM usually has it's own information systems (not identical with the ERP systems) which manage all product-related data including CAD/CAM files. PLM systems are used in the product development process whereas ERP systems are used in the production and order delivery process.

[sixdimensional]

I couldn't forget it if I'm honest, I have to use an Oracle PLM product daily! :)

The overlap between PLM and MDM and PIM seems to be an area of complexity.

Do you think there is a clear direction here? Seems there is some overlap, but both are still needed as well as integration between these systems - since PLM usually doesn't master parties, financial data, etc. but rather engineering/manufacturing design item data.

[Rochus]

Apparently the terminology has evolved since I studied the subject; I'm not familiar with current trends; some of the terms seem rather to be vendor specific marketing jargon for a subset or cross-section of PLM, ERP and CRM functions, or to mix up methodologies and supporting software.

[OpenPIM]

Thanks for the good explanation. And PIM systems are used in conjunction with ERP systems to manage product-related data and then exchange that data across different sales channels.

[OpenPIM]

From my opinion ERP is completely different here. ERP usually store product IDs and other operational product information. When PIM/PDM is focused only on product data and usually guys from marketing team is working a lot with PIM. PIM is considered part of MDM, because MDM solutions can work in different areas like customers, addresses, etc. While PIM is only for products, so we can call it Product MDM.

[sixdimensional]

In the world before centralized MDM systems which were independent of their other enterprise operational/transactional systems, some organizations treated the data in their core enterprise systems as "master files" (I'm talking about quite a while ago).

"The concept of master files was transferred to some corporate computers as early as the 1960s and gained popularity during the 1970s and 80s when computers became more abundant. Master files contain essentially the same descriptive data – such as names, addresses, and basic summary information – as master data. Master files continue to be used as a part of some system databases and were a precursor to master data." [1]

[1] https://www.dataversity.net/a-brief-history-of-master-data/