MDM programs are generally designed to provide the data needed by a cross-section of applications or for data that can utilize its workflow capabilities for its origination and updates. It's an approach usually not taken for data needed by a single application, although it may be done as a set-up for future applications.
Part of the MDM manifesto must include how teams will source its data. Over 75% of the post-implementation requests of MDM will be around this question.
In order to acquire the data, it must be mapped to the data structures of the target application. Who does this? The MDM team, the application team, a separate integration team, or a separate architecture team?
Regardless, all new projects should meet with MDM Leadership in a very early phase of their project to determine:
- Data available in MDM that should be used in the project
- Data not available in MDM that should be sourced by the MDM team for the project (and other projects)
- Data that the project is generating that the MDM team should source into MDM
- Time and resource estimate for the MDM team contribution
Data not in MDM that needs to be may be done in 1 of 2 ways:
- MDM (the MDM team usually) can source the data from its origination point or a third party system
- MDM can update or add to its workflow environment, which incorporates manual entry of the information at the right point
Posted January 29, 2011 9:45 AM
Permalink | No Comments |