An Engagement Model for Master Data Consumers

Transcription

1 An Engagement Model for Master Data Consumers David Loshin Knowledge Integrity, Inc. 1

2 What is Master Data? Master data encompasses the models represening the core business enity objects used in the different applicaions across the organizaion, along with their associated metadata, aoributes, definiions, semanics, roles, connecions, and taxonomies. Examples include: Customers Products Parts Vendors Employees Suppliers LocaIons EnIty concepts are idenified in relaion to the business context 2

3 The Master Data Environment A Master Data Environment provides a set of services enabling data consumers with accessibility to a composite view of uniquely idenifiable eniies Requirements are solicited from data producers and data consumers for providing or using master data: CollecIng source informaion about eniies Resolving enity ideniies Indexing enity data Establishing connecions among source data records associated with uniquely idenified eniies IngesIng data from the sources into the master data environment Project planning for consuming applicaions to integrate the consumpion of master data 3

4 Mistaken Perceptions of Master Data Typical pitches for master data management use plaitudes to moivate adopion: Golden record 360 view of the customer Single source of truth These concepts are somewhat misleading: IntegraIon into a single golden record implies transformaions that may be inconsistent with operaional use MDM, by its very nature, cannot be a source except under very constrained circumstances Truth, from a business process and applicaion perspecive, is malleable Dependencies on structure, intent, semanics, and context cannot be ignored 4

5 Multi- Domain Master Data Use Business Func=ons MarkeIng Purchasing/ Materials Sales Customer Support Manufacturing Fulfillment ForecasIng AccounIng/ Finance IT Human Resources R & D Business En==es Customers Vendors Suppliers Employees Parts 2015 Knowledge Integrity, Inc (301) Products 5

6 Criteria for Usability Model completeness IdenIty resoluion Conformance consistency Master data services Process of engagement Methods of integraion Profiles capturing shared master aoributes IdenIfying aoributes selected for indexing Algorithms for similarity and matching Methods of implementaion Structural consistency SemanIc consistency List of master data events Inventory of services SolicitaIon of interest Requirements, design, develop, deploy Provision of master data ConsumpIon of master data 6

7 MDM Engagement Model Stages in transiioning an opportunity into a producion implementaion for Data consumers Data producers EvaluaIon will help determine if there is a need for applicaion data provision or applicaion integraion Iden'fy Opportunity Ini'al Evalua'on Facilitate Requirements Analysis Data Governance Cos'ng Model Development Plan Tes'ng Produc'onaliza'on, O & M 7

8 Initial Evaluation An iniial discussion between the business process owners and the MDM team to assess suitability, consider scope, and clarify roles and responsibiliies Understand the Business Process IdenIfy Master Domains Specify Use Cases Review Performance Metrics IniIal Scope DeterminaIon IntegraIon planning may indicate the business process incorporates data producers, data consumers, or both 8

9 Sample MDM Usage Scenarios Use Context Example IdenIty resoluion and registraion IdenIty resoluion and registraion IdenIty management as a service RelaIonship and hierarchy linkage RelaIonship and hierarchy linkage Data quality OperaIonal workflow AnalyIc workflow OperaIonal or AnalyIc OperaIonal workflow AnalyIc workflow Informing synchronizaion and quality within the master catalog ValidaIng that a customer aoemping to enroll in a markeing promoion is eligible to paricipate Linking payments to vendors to idenify where vendors have been paid more than once for providing the same item Providing a unique enity idenifier that links all employee records across benefit applicaions Determining where physicians are associated with muliple hospital organizaions SupporIng reporing of rolled- up metrics associated with regional sales by customer type Publishing updated material item data as records are modified 9

10 Facilitating Requirements Analysis Consuming business process owners provide the requirements for using the MDM shared services: Data requirements FuncIonal requirements Performance criteria User acceptance criteria TesIng plajorm and data needs Accessibility For publishers, the MDM team provides an Interface Control Document (ICD) The MDM team examines whether the exising integraion paoerns are sufficient or if there is a need for customizaion or addiional services Performance ExpectaIons Business Rules Access paoerns AddiIons to Services Stack Requirements Analysis Data IntegraIon CustomizaIon Needs Auxiliary Processing 10

11 Requirements Analysis: Access Patterns The Business Process owners evaluate how their applicaions seek to use the master data The MDM team will share MDM usage paoerns to help drive the analysis process Examples include: Direct queries via MDM tool interface ( inspector ) Direct queries using SQL Federated/Virtualized access BI Tools Web services Extracts Real Ime or batch? 11

12 Data Governance System of record Have the systems of record been idenified? Is the master data environment the system of record? Authorship and oversight How are new items added to the MDM system? SynchronizaIon How frequently is master data entered into the MDM system? How frequently is the master data synchronized with the consumer systems? Stewardship workflows What happens when an issue with the source data needs to be resolved? Responsibility for Data Quality 12

13 Costing Model Enterprise stakeholders subsidize the development of shared services Business data consumers benefit in the use of shared services via their investment Costs include: Design and development staffing Dev/Test resources AmorIzaIon of services costs Chargeback models O & M plan Currently: Consumer costs require new money Producer costs may be covered under exising budgets Development cosing ConsumpIon cosing $ O & M Plan and cosing 13

14 Development & Deployment Detailed planning and execuion of development tasks and costs Details regarding use of data integraion tools, development, implementaion Agreement to specificaion and project plan Resourcing & staffing 14

15 Testing Unit tests Full tests User acceptance ProducIon Development and tesing plajorms that scale with real applicaion performance sizing Scalable data test plan (ensure accessibility or create data lab or generate test data) Simplify migraion into producion 15

16 Productionalization and O & M ProducIonalize using standard deployment framework: Hardware plajorm Database plajorm IdenIty resoluion tool/techniques Data integraion tools Data virtualizaion tools Rendering engine Business intelligence/reporing ProducIonalizaIon Move to designated producion environments OperaIons & Maintenance: General MDM OperaIons General System Maintenance Periodic Review and Revision of Business Rules 16

17 Performance Criteria and Measures Criterion Persistence Volume TransacIon Volume Index size User Load Query Response Time Refresh Cadence Ease of deployment Time to value Batch size Result set size Descrip'on of Measure The amount of data and number of eniies that can be managed within the profile repository and index. The number of master data transacions per Ime period. The extent to which the index can grow. The number of simultaneous interacive and system users. The speed at which queries are saisfied The Ime period in which the master index is updated. How simple it is for users to adopt the use of the master data environment. How quickly a prospecive consumer can adopt the use of the master data environment. The number of batch transacions that must be saisfied in a Imely manner. The maximum number of records to be returned from a search. 17

18 Developing the Roadmap and Plan Clearly explain the engagement cycle with the prospecive customer Devise common deployment paoerns ahead of Ime to speed Ime to value Specify how funcional requirements address performance expectaions Provide template cost model, interoperability model, and integraion plans for the prospecive consumer 18

19 Developing the Roadmap and Plan Clearly explain the engagement cycle with the prospecive customer Devise common deployment paoerns ahead of Ime to speed Ime to value Specify how funcional requirements address performance expectaions Provide template cost model, interoperability model, and integraion plans for the prospecive consumer 19

20 Questions & Suggestions integrity.com If you have quesions, comments, or suggesions, please contact me David Loshin