Complexities: Sharing, Security and Visibility Across Domains
Posted by 
Share this Post
By identifying the complexities of your MDM implementation, you can chart a map to ensure you reach your goals
Most MDM implementations are built with a single data hub that cross-references the records loaded from multiple source systems. In a number of scenarios, all records cannot be placed in a single database, and even the creation and maintenance of a single index that cross-references all records may not be an option.
For instance, when MDM is implemented for multiple countries, country-specific regulations may prevent the storage and processing of their country data in the databases maintained in other countries.
Similarly, different branches of government are not allowed to store their data in the systems managed by other organizations or agencies. For example, healthcare (patient) information cannot be placed in the same database as Social Security information.
Even when formally defined regulations do not exist, operational realities and risks associated with a placement of data managed by multiple agencies in a single data base (the MDM data hub) can be significant.
This drives non-traditional MDM designs with multiple data hubs. These designs may rely on dynamic cross-data hub processes and information exchanges. This type of non-traditional implementation represents additional challenges that may result in extra costs.
The MDM management team should be able to recognize and articulate requirements for multiple regulatory domains that restrict data sharing and storage of data from multiple domains in a single data hub.
Data Security and Visibility Requirements
Most MDM data hubs contain sensitive information about enterprise customers and products. Therefore, there is a traditional set of data security and eligibility requirements expected for the majority of MDM data hubs. It is common that an MDM data hub must support role-based security access and audit capabilities.
For some implementations, data security and visibility requirements are more stringent than for others. For instance, for wealth management organizations, multiple teams of financial advisors operate under the umbrella of a single financial services company. Thousands of financial advisory teams serve their clients with only limited data sharing as required by the nature of this business.
Advanced needs for data security, visibility and eligibility in these organizations create significant complexities that become a factor driving the complexity of the MDM program overall and the initiative’s cost.
As you build your MDM roadmap, make sure to discuss the level of complexity you’re facing, and the necessary security parameters, as you share information across multiple domains.
This is part of a series, Building an MDM Roadmap. For other posts and a complete index, view the Table of Contents.
2 Responses »
Trackbacks
Leave a Response
Entries(RSS)
Very useful article. Thanks for sharing this information about consequences of keeping the data at single database and importance of maintaining separate database for different organization.