1 / 20

Master Data Management (MDM)

Master Data Management (MDM). ARKANSAS BLUE CROSS BLUE SHIELD. RSFOX@ARKBLUECROSS.COM. (501) 396-4160. Tuesday 9/25, 8:40 - 9:20. Robert Fox - Data Architect, Arkansas Blue Cross Blue Shield.

clarence
Download Presentation

Master Data Management (MDM)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Master Data Management (MDM) ARKANSAS BLUE CROSS BLUE SHIELD RSFOX@ARKBLUECROSS.COM (501) 396-4160 Tuesday 9/25, 8:40 - 9:20

  2. Robert Fox - Data Architect, Arkansas Blue Cross Blue Shield 17 years of data architecture and warehousing experience in the finance, telecom, and health insurance industries. Installed over 50 data warehouses worldwide, some loading more than 4.5 terabytes of new transactional data per day. Guest lecturer in information management masters degree programs at 3 universities. Speaker at national conferences for Oracle, Fidelity, and MDM-CDI.

  3. Abstract – MDM is bigger than you think • Master Data Management (MDM) is critical to effective managing the information assets of your company. Unfortunately, however, the meaning of the term Master Data Management has become more limited in scope over time. • To understand the full scope of MDM, you must ask yourself two questions: • What is “master data”? • What all is involved in “managing” it? • How you answer these two questions determines whether your MDM program is a departmental or enterprise solution, and whether you are managing the information or managing a process. • This presentation will propose a framework for MDM that is broad in terms of both data and functionality.

  4. Why is Information Important?The Evolution of Competition • The Land Grab • Acquiring unclaimed customers • Investment in infrastructure, name recognition, and geographic territory • The Killer App • Stealing customers from the competition by offering new and better products and services • Investment in software development • The Information War • Stealing and retaining customers from the competition by knowing more about the customer and giving them individually customized treatment • Investment in business intelligence, customizable offerings

  5. First: What is “Master Data”? Application-specific, non-duplicated, non-shared data … Data duplicated in multiple apps App A App B App C App Z Other Data shared with enterprise There seem to be three different definitions: Master Data is all the data, everywhere. Master Data is just the data that is duplicated in multiple applications. Master Data is any data that is exposed outside of an application, whether it is duplicated or not.

  6. Second: What does it mean to “manage” data?

  7. First Generation IT Architecture Application A Application B Application Z … … … … Customer Product Reporting Customer Product Reporting Customer Product Reporting Data Data Data Business Logic Business Logic Business Logic User Interface User Interface User Interface • Monolithic applications with proprietary, embedded data • Custom point-to-point integration • Very little ability to establish enterprise architecture

  8. Modular 3 Tier Client/Server DB DB Server DB Data Access Data Access Business Logic Presentation App Server Business Logic Client Presentation The Evolution of Data Architecture 5 Tier SOA Monolithic DB Server Custom Data DB Data Access Services App Server Custom Application Business Services Integration Bus Web Server Presentation Client

  9. Effective MDM cannot be a component of application development Traditional Location of Information Management Responsibility Emerging Location of Information Management Responsibility IT IT Application Development Technology Systems Technology Systems Information Management Application Development Information Management 2 Make sure your MDM program has the authority to be effective

  10. Three legs on the IT “stool” Financial View Profitability Now Investment for the Future $ $ Business View Customer Value Operational Efficiency Strategic Planning Increase Revenue Reduce Expense Grow the Company IT View Application Information Technology (How?) (What?) (Where?) The goal of IT is to support the business. The goal of the business is to make money.

  11. MDM Components

  12. Customer Data Integration (CDI) App A CDI App B App C 1. Analytical CDI 2. Synchronization CDI 3. System of Record CDI WH App

  13. MDM Components:Enterprise Logical Data Model Party Claim Product • DB Design • SOA Services • Mapping Sources • Defining System of Record • Define Stewards • Global Dictionary • Standard Terms • Document Bus. Relationships Member Claim Drug Name Header Demographic ServiceLine Risk Adjustment Provider Payment NPI Specialty Diagnosis Clinic Procedure Location

  14. Data Standards • No duplicate data • SoA same as SoR unless proven untenable • Only one warehouse • All data is owned by the enterprise, not individuals or departments • Data storage and transmission must comply with security standards • Services used by multiple applications must use data structures derived from the enterprise data model • All data structures must be documented • All new data structures must be derived from enterprise data model • Data quality should be addressed at the point of entry into corporate network • Information should be as accurate and current as possible • Data access should always be directed to the SoA • The data model should drive the choice and architecture of applications, and should be based in turn on business requirements • Any exceptions should go through Data Governance

  15. Dimensions of Data Quality for an Analytical Repository • INTEGRITY – does the data accurately reflect the source system? • VALIDATION – is the data valid for the field? • VERIFICATION – is the data actually true? • BALANCING – does the data compare to other systems (i.e. GL)? • AUDITING – Are there outlying values?

  16. Software Development Life Cycle (SDLC) Project Pipeline Business Requirements Escalation Process Data Quality Project Supervisors Senior Leadership Team Executive Sponsor Architectural Approach Resource Assignment Technical Design Project Process Waiver Process Design Review Development Standards Review Board Standards Committee Executive Sponsor Unit Testing/ QA Testing Code Review System/User Testing Implementation 4 Develop an SDLC and infrastructure to support it

  17. Business Intelligence:Closing the loop Customers, accounts, inventory, payments, activity, products… DATA Profitability, Churn Propensity, Customer segment… BUSINESS INTELLIGENCE INFORMATION KNOWLEDGE RESPONSES Recommend product X, sign up for ePay, Offer free upgrade… DECISION/ACTION

  18. Maturity Model For Business Intelligence 5 Real-Time Decisioning 4 Batch Campaigns 3 Enriching with 3rd-party data 2 Modeling, Scoring, and Segmentation 1 Enterprise Reporting

  19. Summary • Figure out what “Master Data Management” means in your organization • Think larger than the warehouse. • Make sure your program is empowered with authority to be effective within the enterprise. • Develop a functional area framework and assign responsibilities • Develop efficient MDM strategies for each functional area: Software development process, standards and waivers, aging and archiving, data quality, data delivery, security, etc. • Always remember that you work for the business!

  20. Questions?

More Related