Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Building a strong Data Management capability with TOGAF and ArchiMate

9,421 views

Published on

This is the deck that I used for my presentation at the EAM conference in 2013. It gives a high-level overview of the need for a solid data management capability before giving and overview of how enterprise architecture methods can be used to build this capability.

Published in: Technology, Business
  • Be the first to comment

Building a strong Data Management capability with TOGAF and ArchiMate

  1. 1. Building a strong data management capabilitywith TOGAF® and ArchiMate®
  2. 2. Dr. Bas van Gils2+31-(0)6-484 320 88b.vangils@bizzdesign.nlhttp://linkedin.com/in/basvghttp://blog.bizzdesign.comhttp://www.twitter.com/basvg“Life is and will ever remain an equation incapable of solution, but it contains certain known factors.”--Nikola Tesla (1935)
  3. 3. Agenda• Why data management matters• Setting the scene:– Introduction TOGAF– Introduction ArchiMate• Using TOGAF and ArchiMate asinstruments to build a strongdata management capability• More informationComicsfrom:http://www.datagovernance.com
  4. 4. WHY DATA MANAGEMENT MATTERS
  5. 5. Does this sound familiar?Delivering answers to anintelligence questiontakes several days. Weneed the answer today!We do not have a single,unified view of ourcustomer or our productsWe don’t trust ourintelligence data. Qualityhas been an issue toooften in the past.Tracing customercomplaints, late orders,defective parts isextremely hard for us
  6. 6. 6Data Management:NoSQL, Big Data, BI, Business Policy/ Rules, MDM, Meta-data, DataWarenhouseStrategic Management:Business ModelCanvas, Innovation, BusinessIntelligence, business model
  7. 7. Data as an asset- Jill Dyché, IRM UK 2013 MDM/DG keynote “Big Data and Data Asset Management”
  8. 8. Map out the enterprise[Master] Data Management programs cause change: todata, to systems, to business process, to people and tothe enterprise. An organization should map out theirorganization to identify the data, systems, process andpeople affected by the initiative and how they will beaffected.-- Whitepaper “Why MDM projects fail and what this means for big data” by Entity
  9. 9. INTRODUCTION TOGAF AND ARCHIMATE
  10. 10. Ingredients of an EA framework10View-pointsRepository, Reference ModelsProcess LanguageArchiMateTOGAF
  11. 11. ArchiMate + TOGAF11
  12. 12. Capability based planning12
  13. 13. Applying ArchiMate® 2.0Baseline Target13
  14. 14. USING TOGAF AND ARCHIMATE AS INSTRUMENTS TOBUILD A STRONG DATA MANAGEMENT CAPABILITY
  15. 15. Framework for Data Management• Many frameworks have beenproposed for DM– Focus on an aspect of DM– Focus on tooling for DM– Focus on a process for DM– ...• This presentation is based on theDAMA DMBOK framework– Integrated approach to DM– Easy to align with the OpenGroupstandards for Enterprise Architecture
  16. 16. Building a DM capability using EA methodsTOGAF provides a structuredmethod for effectivelyrealizing a business vision:• start with a business vision forthe data management capbility• develop baseline & targetarchitecture• incremental realizationCapability based planning is akey ingredient for succesfulenterprise-wide change• DMBOK Elements map onaspects of the DM capability• Provides a basis forroadmapping: what goes first?ArchiMate is the language ofchoice for enterprise-levelmodeling• High level modeling within &across domains• Basis for analysis &visualization• Aligned with TOGAF & DMBOK
  17. 17. Data governance• Integral, enterprise widegovernance is key to success• The role of the data steward iscrucial: s/he is responsible fordata quality in a specific subjectarea• Data stewards co-ordinate theirwork in a data council which isjointly responsible for theinformation landscape
  18. 18. Information versus data• Several Entities are pertinent in thecontext of a Subject Area• Several systems may manage DataObjects that realize (part of) theinformation that is pertinent tothese Entities• In terms of decomposition:– At the architecture level wework with Business Objects andData Objects– These may be refined in an ERDdiagram at the design level
  19. 19. Master Data Management (MDM)• Many organizations have to jugglewith disparate administrations ofkey entities• Having an integral overview ofthese entities is key to businesssuccess• MDM is the discipline of providingthis integrated view. There aremany (IT) patterns to realize thisgoal. In modern architectures itoften ties in with SOA
  20. 20. Business Intelligence & Data Warehousing• Transaction systems directlysupporting business processesmaintain data at a low level ofgranularity• Business Intelligence is a query,analysis, and reporting capability ofthe organization that providesinsight in historical and aggregateddata of the organization• A data warehouse (EDW) is atechnical environment that enablesBusiness Intelligence
  21. 21. Meta-data management• Meta-data is often defined as“data about data”.• A distinction must be madebetween– Business meta-data– Technical meta-data• Everything that we model aboutdata can be seen as meta-data:– Properties– Documentation– Relations to other objects
  22. 22. OverviewStewardship of aninformation areaDecomposition of aninformation area in entitiesMastering of dataobjects in an MDMenvironmentData movement to anEDW environment forBI products such asfinancial reports,production reports,governance logs etc.Data Object counterpartsof entities are stored ininformation systems
  23. 23. Switching between visualizations
  24. 24. Alignment with the business, strong datagovernance, and grip on the informationlandscape enables the organization to getanswers quicker.Master Data Management (MDM)helps the organization to define asingle unified view of key EntitiesCentral meta data management (businessdefinitions, links to processes, lineage insystems) and strong governance results inincreased trust in data quality.Data issues often lurk underbusiness issues. A model-basedapproach covering all related enterprise-issues will enable the organization tohandle these issues effectivelyProblem solved?Delivering answers to anintelligence questiontakes several days. Weneed the answer today!We do not have asingle, unified view of ourcustomer or our productsWe don’t trust ourintelligence data. Qualityhas been an issue toooften in the past.Tracing customercomplaints, late orders,defective parts is extremelyhard for us
  25. 25. Both the information landscape, system landscape, and organization /governance structure around data management are highly complex.This complexity is managed by using ArchiMate modeling withBiZZdesign ArchitectTake AwayData management is not a project; it is a continuous process. Thiscapability will contribute to sustainable business success.An architecture-approach will help the organization to build a strongdata management capability.Organizations are increasingly dependent on quality data / informationto run their business. Therefore: data management is a business issue.
  26. 26. ©BiZZdesign. All rights reserved.BiZZdesign and BiZZdesign logos are registered trademarks of BiZZdesign Company.

×