« @ SOA | BPM Symposium in San Antonio, Texas | Main | @ SOA | BPM Symposium: Ryan Gates, Appian »



Feed You can follow this conversation by subscribing to the comment feed for this post.


Hi Steve,I see MDM as a tool to improve data iegrtnity. If you ask any Financial or Business executive data iegrtnity is always been high on their list of areas of improvement.Many decision makers fail to see the ROI of MDM, even though independent studies have seen yields of $800K to $1M of GM improvement for ever $1B in sales volume in Organizations that deploy MDM. It may be hard to visually percieve this, but when you think of all the re-work, delays, out of stocks,or shrinkage that are incurred when a PO manages to get through the system with corrupt or innacurate core data, It is easy to see the roadbumps that are incurred throughout the procurement to pay process.MDM also doesn't have to be a formal packaged software. It can be executed with sound logic and business processes, that support all alike attributes living in one place, and not replicating data attributes accross multiple databases. Enjoyed the read. Industry leaders are embracing and executing MDM. They see and fell the value.Thanks,Mark


MDM is about mastering a intofmarion based on the operational/functional needs of the business. Not organizing db tables. It requires a technical component as a backbone or tool to support business drivers that are enforced through data governance.Internal departments slant the same data all the time for many different reasons but, getting intofmarion from disparate data sources is one of the issues (local data sources). Integration is another. Silos are developed because its built into integration patterns. Business gets lost at this point. They don't want to hear technical jargon regarding large number of integration mappings, translations, or sequences. They want one place to see a customer, order, product, finance, asset, etc. MDM simplifies it for business when presented as multi-domain masters.In my designs business does have a place in driving multiple domain mastering since they define customer, product, services, finance, and assets for one simple reason: a need for a common voice to its customer and partners that translates to revenue. Most companies don't do that today very well and it cost money. My recommendation to business when discussing multi domain MDM is envision it as a shared intofmarion as a service (IaaS) component relative to the very domain required at the point of need (like up-selling, ordering, customer interactions, product development, etc). Extract those intofmarional needs from a single source be it customer (party model based), product (dev-to-runtime based), financial (code based) and more. Who defines these requirements? Technical people? I think not. MDM starts from a functional business need and cascades to IT portfolio. Just as most technical solutions do in today's business world. The maturity of an organization to handle MDM becomes a matter for the business to resolve. Not IT.


Nicely put, Tod. I think most people in both bussneis and IT think that once the MDM platform is implemented, they're done but as you point out, that's when the fun starts!


I have to admit I am very impressed with the quality of your blog. It is certainly a pleasure to read as I do enjoy your posts.


Muito obrigado por escrever isto, era incrivelmente informativo e disse-me uma tonelada

The comments to this entry are closed.