Where is ADM in your MDM Roadmap?

The three-letter acronym ADM stands, in a data management context, for Application Data Management.

Well, besides from that ADM is part of the word roADMap I see more and more signs of that the line between master data and other application data is blurring and Application Data Management will be part of the MDM roadmaps around.

The difference – and the intersection – between Master Data Management (MDM) and Application Data Management was examined here on the blog some time ago in the post called MDM vs ADM.

The pros and cons of seeing master data as something separate from any other data was also discussed in the post Master Data or Shared Data or Critical Data or What?

As also put forward then, I think it is useful to look at the data within the whole Enterprise Information Management (EIM) theme in lens of what is specific to your enterprise and what you have in common with other enterprises. Master data will typically be the data you share – or could share – with other enterprises, not at least your business partners.

In what degree do you find it useful to separate master data and other data in a MDM and/or ADM roadmap?

ADM MDM

MDM vs ADM

The term Application Data Management (ADM) has recently been circulating in the Master Data Management (MDM) world as touched in The Disruptive MDM List blog post MDM Fact or Fiction: Who Knows?

Not at least Gartner, the analyst firm, has touted this as one of two Disruptive Forces in MDM Land. However, Gartner is not always your friend when it comes to short, crisp and easy digestible definitions and explanations of the terms they promote.

In my mind the two terms MDM and ADM relates as seen below:

ADM MDM.png

So, ADM takes care of a lot of data that we do not usually consider being master data within a given application while MDM takes care of master data across multiple applications.

The big question is how we handle the intersection (and sum of intersections in the IT landscape) when it comes to applying technology.

If you have an IT landscape with a dominant application like for example SAP ECC you are tempted to handle the master data within that application as your master data hub or using a vendor provided tightly integrated tool as for example SAP MDG. For specific master data domains, you might for example regard your CRM application as your customer master data hub. Here MDM and ADM melts into one process and technology platform.

If you have an IT landscape with multiple applications, you should consider implementing a specific MDM platform that receives master data from and provides master data to applications that takes care of all the other data used for specific business objectives. Here MDM and ADM will be in separated processes using best-of-breed technology.