USING COLLIBRA OPERATING MODELS TO ACCELERATE TIME … · USING COLLIBRA OPERATING MODELS TO...
Transcript of USING COLLIBRA OPERATING MODELS TO ACCELERATE TIME … · USING COLLIBRA OPERATING MODELS TO...
1 | ©Collibra 2017©2017 Collibra Inc
USING COLLIBRA OPERATING MODELS TO ACCELERATE TIME TO VALUEJump start your data governance projects
Ram Naresh PrattiCOE
Date
2 | ©Collibra 2017
Session Overview
• What are the key components of Collibra operating model?
• What are the reference asset models?
• How a standardized asset lifecycles looks like?
• How to visualize data governance framework?
• What’s our recommendations?
3 | ©Collibra 2017
Why Do We Need Operating Models?
• A bizarre multiplicity of names for industry standard concepts
• Inbuilt concepts, which have no real world equivalent
• Real world concepts, which are not captured in the model
• The inability to expand to other use cases because it is very specialized and rigid
• The loss of metadata when assets are migrated
• The loss of knowledge with new people
Issues that we can avoid
4 | ©Collibra 2017
What Are the Drivers for Usage?
• Common and consistent terminology• Simple and self-service• Flexible• Maximized for speed
Easier
• Meet future use case needs • Improved and timely
Faster
• Available for download from Marketplace• Reduce manual design and configuration steps• Reusable components
No Cost
5 | ©Collibra 2017
What Are the Benefits?
• Less risky
• Predefined scope• Well-defined
maturity steps
Rapid implementation• Reduced effort
• No need to reinvent the wheel• Provides a “straw man”• Eliminate communication
challenge
6 | ©Collibra 2017
• How can you tell what a “bad” model is if you don’t know what is actually meant to be?
• How do you know you are going in the right direction?
• How do you know that you are using the same terminology?
• How can you pinpoint what’s missing?
The Operating Model Is the Heart of Data Governance
Blueprints to build a roadmap
Stewards,Users Use cases
Operatingmodel
Changemanagement
ITsystems
7 | ©Collibra 2017
It’s All About Discipline
• Involve the right people at the right time to define the right operating model
• Define appealing traceability diagrams
• Differentiate enterprise vs local needs
• Promote standardization
• Maintain accuracy, consistency, and appropriate use
Guidelines for success
8 | ©Collibra 2017
Collibra Operating Model Components
• Asset Model/Meta Model • Asset Lifecycle
• Structure Collaboration
• Stewardship Process Automation
• Communities and Domains
• Users and Permissions
Collibra Operating Model
Structure OrganizationExecution & Monitoring
Asset Types Attribute Types
Relation Types
Complex Relation Types
Articulation Score
CalculationsRole Types
Validation Rules Issue Types
Status Types
Workflow Definitions
Root Communities
Domain Types
Settings and Customization
Users and Groups
10 | ©Collibra 2017
Business Dimensions
Governance Assets Data Assets
Technology AssetsAsset
Business Dimensions
Business Dimension
Business Process
Data AssetGovernance
Asset
Business Asset
groups
Data CategoryLine of
Business
classifies
is associated with
produces, consumes
system of {record, source, use, candidate source}
produces,consumes
categorizes
categorizes
RegionContext
Business Dimension
Asset
Value
Product
is associated with
Technology Asset
Code Value
Code Setallowedvalue set
11 | ©Collibra 2017
Business Semantic Glossary (Ontology/Taxonomy)
Rulebook
Business Dimensions
Technology Assets
Glossary
Acronym
Technology Asset
Business Asset
Business Term
has acronym
Business Dimension
classifies
has synonym
system of {record, source, use, candidate source}
groups
Business Rule
governed by fact typeco-role
rolespecializes, preferred ,
simple
12 | ©Collibra 2017
Report Catalog
APPLICATION INVENTORY
BUSINESS DIMENSIONS
Regulatory Domain
Code List
Report Attribute inventory
Report Attribute Inventory
Data Dictionary
Report CatalogRegulator
Data Element
Report Attribute
Asset
Business Dimension
Regulation
Code Value
Code Set
consists
allowed value set
Report
ScheduleReport
RowColumn
Data Point
Data Point
Asset
Business Dimension
Assigned Value
ContextReport
Cell
Defines
is metric for
Imposes
Allowed Value Set
contains
Technology Asset
source system,candidate source
regulates groups
Business Process
Line of Business
is associated withproduces,consumes
Touch Point
Control controls
accesses
13 | ©Collibra 2017
Policy Manager
Rule Book
Policy Domain
ISSUE MANAGEMENT
Asset
Policy
Rule
applies to uses
Standard is enforced by
includes
BUSINESS SEMANTIC GLOSSARY
Business Term
Compliance Metric
is executed by
Compliance Issue
is violated by
impacts
groupsrelated to
Business Process
Line of Business
is associated with
is necessary for
Data Category
Regionis associated with
related to
classifiescauses
BUSINESS DIMENSIONS
15 | ©Collibra 2017
Solution Model- Accelerators Applied
DATA LINEAGE (Def)
DATA LINEAGE (IMPL)
BUSINESS SEMANTIC GLOSSARY
is represented by
Business Term
Data Element
Column
DATA SHARING AGREEMENTS
Data Setcontains
REFERENCE DATA
Code Setallowed value set
DATA QUALITY
Data Quality Rule
complies to
is executed by
Data Quality Metric
governed by
is implemented by
is classified by
Business Dimension
POLICY MGMT.
Standard applies
ACCOUNTABLITY MGMT
ReportAttribute
is derived from
DATA HELPDESK
Data Issueis impacted by
Field Mapping
Field Mapping
source
target
sourcetarget
LOGICAL DATA DICTIONARY
PHYSICAL DATA DICTIONARY
REPORT CATALOG
Role
Responsibility
Accountable/Responsible
assigned to
23 | ©Collibra 2017
Responsibility Assignment
RACI
Asset
is responsible for
Role Assignment
Responsibility
involved in
Business Dimensions
Business Process
Data Category
Line of Business
Region
Product
is associated with
impacts
is accountable for,is responsbile for,is informed about,
is consulted for
classified by
controls
governed by
Governance Asset
groups
25 | ©Collibra 2017©2017 Collibra Inc
STOP WORRYING ABOUT OPERATING MODELS AND
START FOCUSINGON ADOPTION
26 | ©Collibra 2017
Tips for Success
• Don’t compromise
• Change into your own vocabulary
• Extend as needed
• Reuse as much as you can
• Exploit the emerging use case models
27 | ©Collibra 2017
Recommended Practices
• Divide and conquer
• Pick a use case
• Limit system area in scope
• Start with 2 or 3 assets – Not over complicated or simple– Use them as poster child for promotion activities
• Keep refining the content– Add more complex assets
• Sell it to other business areas• Learn and experiment with emerging use cases
28 | ©Collibra 2017
Takeaways
• Try to use what we have on marketplace instead of designing something new
• You must ALWAYS start small!
• Find the business hot button and propose to solve it
• Tag a business goal to your initiative
• Know that terminology is very important to people
• Involve the end users as soon as possible