By Frank Dravis, Senior Consultant
We have a banking client that is grappling with how to get a single view of their customers from the nine major types of systems they have and the myriad of subsystems. You’ll recognize those systems as you probably have them yourself: Billing, Product, Agent, G/L, Call Center, etc. When you first approach the problem there is a tendency to think, “Oh, this is a data warehouse problem. The bank wants to get a 360 degree view of their customers.”
But the problem is that our client’s challenges and issues go deeper. Yes, a data warehouse would achieve one objective of their goals, getting customer data from heterogeneous systems loaded onto a common platform, but the problem is more multidimensional.
A main component of the solution is customer master data management, otherwise known as Customer Data Integration (CDI). CDI solutions automate the harmonization and integration of customer data from operational systems. Unlike a data warehouse, CDI guarantees that the data is cleansed and that business rules are applied before the customer data is stored on the CDI hub.
However, for the CDI system to function effectively it cannot do so in isolation. The rules it needs to apply should be defined. Enter data management. Data management is the practice of implementing rules and policies on data. It is all about building systems and processes to ensure consistent application of data quality, data integration including ETL and federation, metadata management, security, access, etc. Moreover, data management establishes the framework and culture for the original source systems to turn into target systems when the CDI solution serves as the system of record or reference and sends data back. Yes, for those of you who have implemented a successful MDM system, you have some form of functioning data management effort.
But unless senior management at the bank is willing to engage in sanctioning the right business rules, security and access policies, and corporate definitions, neither CDI nor data management will work. Thus data governance is a critical component of the bank’s long term data integration success. Understand, that data governance comes in big and little forms, such as the more operational policy of “the parts data mart shall attain a quality score of 82% in within the next six months.” At the bank, data governance policies serve as crucial guidance to business, IT, and their data stewards.
So the next time you see one of those star-like diagrams with disparate data sources all feeding towards the customer center, consider there is a multi-dimensional view of that diagram: MDM, data management, and data governance.
Frank Dravis is a senior consultant with 21 years of experience in enterprise information management (EIM) and data quality solutions design, implementation, and consulting. He specializes in data integration, data quality, and data governance solutions, advising key clients and industry vendors.
Comments