Best Practice for Implementing a Centrally Authored EBX MDM

[Frank P]

Hello,

Currently managing a MDM implementation (centrally

authored MDM) and was wondering about the Best Practices for replicating the

MDM data into downstream apps. We are talking about Suppliers being creating centrally and replicated in around a 30 of apps.

Some of those apps are transactional and therefore any

change to a supplier (creation / update / deactivation / etc.) has to be

propagated in real-time.

The goal is to ‘decouple’ as much as possible the MDM

Repository from the apps and guarantee scalability as we interface new apps.

I am interested in any Best Practice documents

presenting IT architecture, dos and don’ts; pitfall to avoid, governance

schemes of the MDM and interfaced applications, etc.

In particular, how the reconcile the need for a core

model in the MDM Repository (common data model, common workflows, common data

governance) with the specificities of each interfaced applications, and how to

keep the MDM repository in sync w/ the downstream apps w/out compromising

performance and operational constraints (typically data require fast

replication for transactional systems).

Thanks in advance for any insights … need some

detailed papers, no marketing XP Bs 😉

Regards,

Frank