Presentation on theme: "Metadata Solutions Architect"— Presentation transcript:
1 Metadata Solutions Architect Metadata Use CasesYou Can UseForDAMA ChicagoBob DeinMetadata Solutions ArchitectAllen Systems GroupAugust 15, 2012
2 About ASG Software Solutions Founded in 1986 by Arthur L. Allen, President & CEO1,300 employees in over 80 offices worldwideMore than 3,400 customers worldwide$400 million in revenue annuallySolutions to meet metadata, infrastructure/ops management and cloud challengesExpertise in implementing metadata and data governance solutions85% of Fortune 500 companies rely on ASG productsCopyright® 2011 Allen Systems Group, Inc.
3 Banking Insurance Financial 10/18/2010Top Rochade CustomersBankingInsuranceFinancialASG-Rochade Sales Support Library
4 Top Rochade Customers (cont.) 10/18/2010Top Rochade Customers (cont.)Oil and GasolinePharmaceuticalAuctionsHealth CareRetailSoftwareMarket ResearchHotelsAirlinesProfessional ServicesTelecommunicationsMarket ResearchASG-Rochade Sales Support Library
5 Top Rochade Customers (Government) 10/18/2010Top Rochade Customers (Government)Defense Finance and Accounting Service (DFAS)ASG-Rochade Sales Support Library
6 Data Governance and Information Management Challenges Problems Governing & Managing DataCost of MisunderstandingLack of standards– no global codes, definitions or data format existsApplication specific definitions – term definitions differ across divisions and LOBNo single source of truth – unless vetted its not trusted.No ownership / governance for the problem – system and process “work-arounds” are created.Difficult to find and understand data reliance on key knowledge workers.Root Cause Analysis-data quality issues are time consuming to understand and verify.Expensive missteps - Action is taken - only to find out later that information was wrong or incompleteHigher costs – unclear change impact and creation of redundant processes and informationSlow response – lack of information clarity slows decision process and agility for mergers and regulatory initiatives (HIPAA, Sarbanes Oxley, Basel II)Productivity loss – those who don’t understand data burden the few that do
7 Solving the Problem of Information Metadata is theDNAof information technologyWho?What?How?When?Where?Why?Makes information usable:Supports consistent use of terminologyDescribes how information can be used, combined, and sharedOptimizes value of existing IT investment:Enables broad re-use of informationEstablishes knowledge base of information and assetsProtects corporate reputation:Prevents inappropriate exposure and use of informationProvides “evidence” for governance and compliance purposesMinimizes cost of information usage:Reduces need for users to question informationMinimizes time spent reconciling “inconsistent” informationReduces storage costs due to creation and maintenance of redundant data and complexityMaking info usable consists of achieving common ground, a cross-functional understanding of the same element.this allows for re-using the element, combining and sharing it across LOB’sSave time and money by re-using this information instead of starting from scratch and re-visiting previously made business decisions.Centralize your data facts in to one vetted, trusted source.Provide a means for auditing and “evidence” that IT knows where the information came from and what happened to it along the wayMinimize the cost of usage by providing a central repository for Root cause analysisReconcile inconsistent information be supported across the IT landscape and reduce storage costs due to the redundant information and subsequent complexity surrounding how information is being used today.
10 10 Reasons Why Metadata Solutions Fall Short Lack of Commitment – “Tell me again why we need this?..”Poorly Defined Scope – “Rome wasn’t built in a day..”Poorly Defined Requirements – “What does it do for me?..”Poor Communication – “meta what?..”Reorgs & Personnel Changes - “It’s who, not what you know..”Lack of Business Relevance – “It’s like Google right?..”Lack of IT Relevance – “Our new ETL tool does that..”DIY Mentality – “Don’t buy one, I can build that..”High Level of Complexity – “I don’t get it..”Poor User Experience – “Where’s the app?..”Run time stats
11 How Use Cases Can Make a Difference Lack of Commitment – “Now that’s a compelling business case..”Poorly Defined Scope – “That’s all it needs to do for now..”Poorly Defined Requirements – “That’s what it needs to do for us..”Poor Communication – “A picture is worth a thousand words..”Reorganization & Personnel Changes – “Great story, now I get it!..”Lack of Business Relevance – “I’ll use this every day!..”Lack of IT Relevance – “This will make us better, faster, cheaper..”DIY Mentality – “OK, maybe we shouldn’t build that..”High Level of Complexity – “Now I get it..”Poor User Experience – “That was easy..”Run time stats
12 Use Cases 101Use Case - defines a goal-oriented set of interactions between external actors and the system under consideration (e.g. DMBOK Goals & Activities).initiated by a user with a particular goal in minddescribes the sequence of interactions between actors and the systemcaptures who (actor) does what (interaction) with the system, for what purpose (goal)System – a mechanism that an actor interacts with in order to achieve a goal (e.g. DMBOK Tools)Actor - party outside the system that interacts with the system (e.g. DMBOK Suppliers, Participants and Consumers)Input/Output – description/illustration of what actors contribute/receive from the system (e.g. DMBOK Inputs & Deliverables)Scenario - an instance of a use case representing a single path through the use case. Use Cases usually have many scenarios.Run time stats
13 Example Metadata Use Case: Reporting/Analytics ScenarioAn authorized business user accesses the Business Metadata Repository. The system validates the user credentials and provides access. Business user searches the Repository for particular business terms or keywords. In addition simple and effective reporting and analytical tools are also available. The results of the search or a requested report should be displayed with an option to print or to export to a recognized output format (e.g. CSV).Sample dataThe following table suggests a possible data that can be used as part of this Use Case:#Data elementValueComments1Search keyword“Revenue”The system should display all business terms that contain the requested keyword2Report parametersAll business terms within a category, e.g. Finance ManagementThe system should display all business terms with the requested category in a list format3Export parametersCSV fileThe system should generates a CSV file that contains the contents of the reportRun time stats
14 Metadata Use Case Contexts CorporateConceptual / LogicalPhysical /DeployedFinanceSalesLine ofBusiness MgrRevenueBusinessIT DeptApp DevBusinessAnalystDBANote: Automated discovery, relationship mapping, and lineage of the physical context.
17 Full Contextual Representation = Governance CorporateFinanceGovernanceConceptual / LogicalPhysical /DeployedContextual Domain(s)/Group(s)SalesCompliance Standards /MeasuresDefinition /Description /Value DomainLine ofBusiness MgrModelsRevenueBusinessIT DeptReportProcess(Appl / ETL / etc)App DevBusinessAnalystDatabase / Table / View /ColumnDBANote: Automated discovery, relationship mapping, and lineage of the physical context.
18 Metadata Use Case: Desktop Metadata Accessibility ScenarioAn authorized user highlights some text (a single word or a combination of words) while on a Windows desktop or in any of the applications (e.g. Microsoft Word, PowerPoint, browser, etc.) and uses a combination of function keys to retrieve and view the Business Term definition from the Business Metadata Repository. The Business Term definition is displayed in a pop-up window (as in IBM’s BG Anywhere).Sample dataThe following table suggests a possible data that can be used as part of this Use Case:Run time stats#Data elementValueComments1Business Term nameHighlighted word on a desktop, e.g. “Revenue”2Business Term definitionBusiness Term definition, name and short descriptionAdditional attributes may be retrieved from a pop-up window
19 Metadata Use Case: Desktop Metadata Accessibility CorporateFinanceSalesLine ofBusiness MgrA large part of the ASG goal in future product development surrounds “actionable” information. Receiving the information at your fingertips from any desktop application and any level/location within the organization.In this manner the the certified business definitions are pervasive and aligned with the businessApp DevBusinessAnalystDBACustomApp
20 Metadata Use Case: Desktop Metadata Accessibility CorporateHighlight the business term “Revenue”FinanceSalesLine ofBusiness MgrApp DevBusinessAnalystDBACustomApp
22 All Information Available Via Intuitive Search Get quick definitions and related business concepts……drill down for availability of detailed context, metrics, and implementations…link directly to the metaGlossaryFor full details
23 Metadata Use Case: Governance Workflow ScenarioAn authorized user (in a role of Author), say Data Steward, enters a Business Term in the Business Metadata Repository. The system validates Author’s identity and saves the Business Term definition in “CREATED” status. Author submits the new Business Term definition for approval. The status is changed from “CREATED” to “SUBMITTED.” A notification of the new submitted term is sent to all users granted the Approver role. An approver receives a notification vie , enters Business Metadata Repository and reviews and approves the new Business Term. The system creates a production version of the term with status “APPROVED”. Other users of the Business Metadata Repository can view only those Business Terms that have “APPROVED” status.Sample dataThe following table suggests a possible data that can be used as part of this Use Case:Run time stats#Data elementValueComments1Business Term definitionAttributes of Business Term2Business Term statusCREATED SUBMITTED APPROVEDSee Use Case steps for status changes
24 Metadata Use Case: Governance Workflow Financial ControllerVP of FinanceDir of Acctg /ComplianceGovernanceProcessNew Business Term DefinitionIT ArchitectQuality MgrMembershipGovernanceMgrBusiness GlossarySolutionBusiness AnalystIT Architect
25 Metadata Use Case: Governance Workflow Financial ControllerVP of FinanceDir of Acctg /ComplianceGovernanceProcessAutomatic NotificationIT ArchitectQuality MgrMembershipGovernanceMgrBusiness GlossarySolutionBusiness AnalystIT Architect
26 Metadata Use Case: Governance Workflow Financial ControllerGovernanceProcessIT ArchitectApprove New TermQuality MgrMembershipGovernanceMgrBusiness GlossarySolutionBusiness AnalystIT Architect
27 Metadata Use Case: Governance Workflow Financial ControllerDir of Acctg /ComplianceGovernanceProcessVP of FinanceIT ArchitectMembershipApprove New TermQuality MgrAuto Notify SubscribersGovernanceMgrAuto Notify SubscribersBusiness GlossarySolutionBusiness AnalystAuto Notify SubscribersAuto Notify SubscribersIT Architect
28 Metadata Use Case: Business/Technical Metadata Integration ScenarioBusiness and technical metadata resides in the Business Metadata Repository. An authorized user (in a role of Author), say Data Architect, edits a Business Term in the Business Metadata Repository and links it to a technical metadata object (e.g. Table or Column). The system creates a working version of the Business Term change with “MODIFIED” status. Author submits the Business Term alignment change for approval. The status is changed from “MODIFIED” to “SUBMITTED.” A notification of the submitted term change is sent to all users granted the Approver role. An approver receives a notification vie , enters Business Metadata Repository and reviews and approves the Business Term alignment change. The system creates a production version of the term with status “APPROVED”. Other users of the Business Metadata Repository can view only those Business Terms that have “APPROVED” status.Sample dataThe following table suggests a possible data that can be used as part of this Use Case:#Data elementValueComments1Business Term definitionBusiness Term attributes, such as Name, Short Description, Long Description, etc.2Technical Metadata definitionsTechnical metadata elements, such as entities, attributes, tables, columns, records, fields, etc.3Business Term StatusMODIFIED SUBMITTED APPROVEDSee Use Case steps for status changesRun time stats
29 Metadata Use Case: Business/Technical Metadata Integration Financial ControllerDir of Acctg /ComplianceGovernanceProcessVP of FinanceIT ArchitectQuality MgrMembershipGovernanceMgrBusiness GlossarySolutionExt Docs, URLs, etc.Business AnalystApplicationsETLBI ReportsDatabasesDWMetadata RepositoryModelsIT Architect
30 Metadata Use Case: Business/Technical Metadata Integration Financial ControllerVP of FinanceDir of Acctg /ComplianceGovernanceProcessIT ArchitectQuality MgrMembershipGovernanceMgrBusiness GlossarySolutionMetadata RepositoryBI ReportsDatabasesDWExt Docs, URLs, etc.Business AnalystAlignment of “Customer Name” to DB/table/columnApplicationsETLBI ReportsDatabasesDWMetadata RepositoryModelsIT Architect
31 Metadata Use Case: Business/Technical Metadata Integration Financial ControllerVP of FinanceDir of Acctg /ComplianceGovernanceProcessAutomatic NotificationIT ArchitectQuality MgrMembershipGovernanceMgrBusiness GlossarySolutionMetadata RepositoryBI ReportsDatabasesDWExt Docs, URLs, etc.Business AnalystApplicationsETLBI ReportsDatabasesDWMetadata RepositoryModelsIT Architect
33 Metadata Use Case: Business/Technical Metadata Integration Global Business DefinitionValid ValuesCodeDESC3Haz of Lead Coverage: exp only7Lead Law/Lead Liability9Cover for Haz, Full Policy LimitsPhysical Deployment: the where and how is it used in our IT Systems
34 Metadata Use Case: Integration With Technical Metadata Business Term definitions, stewards and where this certified term is used in the IT environment
35 Good Use Cases are Crucial to Metadata Projects: ConclusionsGood Use Cases are Crucial to Metadata Projects:Pre-Requisite for trial and evaluation of metadata solutionsAn efficient means of capturing functional metadata requirements (Requirements & Relevance)Promotes user involvement (Commitment)User and goal oriented (Commitment & Relevance)Specifies all the different ways to use the metadata solution (Scope)Written in an easy-to-understand structured narrative (Simplicity & Communication)Help close the gap between functional requirements and testing (Quality)Represent the solution benefits supporting a metadata business case (Commitment, Communication & Relevance)Run time stats
38 25+ Years of Data Management experience Why ASG ?The Data Warehousing Institute’s Best Practice Award in the category of “Data Governance”25+ Years of Data Management experienceRecognized leader in the management of metadata for data, process, and technologyHundreds of the world’s largest organizations trust ASG for solutions to help manage their data