real-world data governance: metadata & data governance

1

Copyright © 2012 Robert S. Seiner – KIK Consulting & Educational Services / TDAN.com

Non-Invasive Data Governance™ is a trademark of Robert S. Seiner & KIK Consulting

Twitter at #RWDG 1



Twitter at #RWDG 1


Non-Invasive Data Governance™ is a trademark of Robert S. Seiner & KIK Consulting Twitter About This Webinar at #RWDG

1



Robert S. Seiner KIK Consulting & Educational Services – KIKconsulting.com

The Data Administration Newsletter – TDAN.com

Real-World Data Governance Metadata & Data Governance

Monthly Webinar Series Hosted by Dataversity Robert S. Seiner – KIK Consulting / TDAN.com

July 19, 2012 – 2:00 p.m. EST

2



Twitter at #RWDG 2



Twitter at #RWDG 2



2



• Real-World Data Governance – Monthly Webinar Series

– August 16, 2012 – Master Data Management & Data Governance – 2pm EST

– September 20, 2012 – Business Glossaries & Data Governance – 2pm EST

– October to December to be announced shortly.

– Register On-Line at Dataversity.Net

Real-World Data Governance Upcoming Webinars

3



Twitter at #RWDG 3



Twitter at #RWDG 3



3



• The relationship between Metadata and Data Governance can be considered a two-way street.

• Metadata, as data about the people associated with the data, is a natural by-product of an effective Data Governance program.

• And metadata itself must be governed in order for that metadata to add value to business and technical opportunities.

Metadata & Data Governance Abstract

4



Twitter at #RWDG 4



Twitter at #RWDG 4



4



• How can we leverage this relationship to quickly and efficiently improve the management of data?

• How can we enable our organization to view Metadata and Data Governance side-by-side as complimentary teammates in the effort to manage data as a valued corporate asset?

• The answers to these questions

may not be as difficult as you think …

Metadata & Data Governance Abstract

5



Twitter at #RWDG 5



Twitter at #RWDG 5



5



Metadata & Data Governance Don’t Let This Happen to You

Typical 2-Way Street?

Typical Accident?

Typical Reaction?

6



Twitter at #RWDG 6



Twitter at #RWDG 6



6



• Top Avoidable Mistakes (in no specific order) :

– Lack of Executive & Strategic Level Understanding & Support

– Lack of Program Accountability & Responsibility

– Lack of Definition of Best Practices as a Target Behavior

– Lack of Critical Analysis of Present Environment

– Inability to Select & Follow Suitable Approach

– Lack of Planning and Ability to Support Meaningful Initiatives

– Framework of Roles & Responsibilities

– Making Data Governance & Data Quality Optional

– Lack of Focus on Communications

– Improper Expectations of the Data Quality & Data Governance Solution

– Failure to Stay Iterative and Incremental in the Approach

Metadata & Data Governance Considerations for Setting Expectations

7



Twitter at #RWDG 7



Twitter at #RWDG 7



7



DATA GOVERNANCE & STEWARDSHIP

META-DATA MANAGEMENT

Metadata is a by-product and an enabler to improved Data Governance.

Governing Through Metadata

Metadata Governance

Governance must be applied to meta-data as the discipline of managing meta-data.

7

Metadata & Data Governance The Relationship – One Way

8



Twitter at #RWDG 8



Twitter at #RWDG 8



8



• Governance – Execution of Authority, Responsibility & Accountability

• Stewardship – Formalizing Accountability – Formal – Recorded – Informal – Not Recorded – “People Just Know” – or do they?

• Identifying Data Stewards rather than Assigning Data Stewards

• “Writing it down” rather than “Best Guess”. Formal rather than Informal.

• Key Component of a Non-Invasive Data Governance™ Program

• Why is it important to “write it down”?

8

Metadata & Data Governance Metadata as a By Product

9



Twitter at #RWDG 9



Twitter at #RWDG 9



9



• Tribal Knowledge Vs. Formal Knowledge

• Identify & Record the People that Have Responsibility for: – Defining the Data/Metadata Is Necessary to operate the Business

• Are they associated with a specific area of the organization? • Is there ever more than one person who has the responsibility? • How do you know who to contact with questions about:

– Origin – Validity – Location – Accessibility, …

• Just because you know who to contact, do other people? – Producing the Data/Metadata Is Necessary to operate the Business – Using the Data/Metadata that is Necessary to operate the Business

9


10



Twitter at #RWDG 10



Twitter at #RWDG 10



10



• Ask yourself these questions: – Could these people be the Data/Metadata Stewards? – How could we benefit by knowing who these people are? – Does it make sense to record who these people are? – Is this information about the Stewards meta-data?

• This information is a by-product and results of the

Stewardship aspect of Non-Invasive Data Governance™.

10


11



Twitter at #RWDG 11



Twitter at #RWDG 11



11




• “Having this information has greatly improved our ability to communicate efficiently & effectively.” Client 2008

• “Non-Invasive is the way to go … However, let me warn you …

At some point we just may need the stick.” Client 2007

• “How many stewards will we need and how long will we need them for?”

Client 2006

11

12



Twitter at #RWDG 12



Twitter at #RWDG 12



12



Metadata & Data Governance Data About People in Data/Metadata Governance Roles

• Further Description of Data/Metadata Governance Metadata – Conceptual Data/Metadata Governance Metadata Meta-Models – Selecting the “Right” Metadata to Manage

• Where do we store the Data/Metadata Governance Metadata

• Data/Metadata Governance Metadata Tools – Common Data Matrix – Data Steward Repository

12

13



Twitter at #RWDG 13



Twitter at #RWDG 13



13




13

Person Id (PK)

Person Name

Contact Info

Include “Unassigned”

Business Unit

Code

Subject

Matter

PersonData Level

Code

Project Code

Data

Steward

Type Code

Steward Link

(Relationship)

Position Link

(Relationship)

Person Id (FK)

Position Code (FK)

Business Unit Code (FK)

Business Unit Code (PK)

Business Unit Name

Steward Type Code (PK)

Steward Type Desc

DD-Data Definer

DP-Data Producer

DU-Data User

SS-System Steward

Data Level Code (PK)

Data Level Desc

DM-Data Model

ENT-Entity

ATR-Attribute

DB-Database

TBL-Table

COL-Column

Project Code (PK)

Project Name

IMS-IMS

WAFR-WAFR

CHAZ-CHAZ

Position

Code

Person Id (PFK)

Position Code (PFK)

Business Unit Code (PFK)

Data Name (PFK)

Data Level Type Code (PFK)

Steward Type Code (PFK)

Data Name (PK)

Data Level Type Code (PFK)

Subject Matter Code (FK)

Subject Matter Code (PK)

Subject Matter Name

Position Code (PK)

Position Name

Position Grade

ISDM

Integration

ISDM Task Number (PK)

Stewards Type Code (PFK)

ISDM

Task

ISDM Task Number (PK)

ISDM Task Desc

14



Twitter at #RWDG 14



Twitter at #RWDG 14



14




DOMAINS

ORGANIZATIONS

STAKEHOLDERS

14

15



Twitter at #RWDG 15



Twitter at #RWDG 15



15



Enterprise

Perspective


16



Twitter at #RWDG 16



Twitter at #RWDG 16



16



Operational Level

Operational Data Stewards (existing)

Data Definers, Producers, Users

These people are presently defining,

producing and using data as part of their

jobs. Recording of the Operational Data

Stewards will be an important enabler of

improved communications, coordination

and cooperation among stewards.

Tactical Level

Data Domain Stewards

Per assigned Subject Areas

Data Steward Coordinators

One per Business Unit

Strategic Level

Data Governance CouncilData Governance Sponsors Group

or Group of similar participation. One person, plus

alternate, for each Business Unit represented & IT.

Consider financial services & human resources.

Executive Level

Data Steering CommitteeSenior-most level knowledge of the program.

Leverage existing business structure as possible.

If no structure exists, utilize an IT Steering Committee

or an executive founded board or council.

Operational Level - Business Unit Specific

Strategic -

Enterprise

Tactical Level - Cross Business Unit

Executive

Non-Invasive Data Governance™ Operating Modelof Roles & Responsibilities

Escalation / A

pproval Path

Dat

a G

ove

rnan

ce P

rogra

m T

eam

(D

GPT)

IT S

ubje

ct R

esourc

e Exp

erts

Data Governance Program Team

Data Governance Team ManagerResponsible for Administering the Program,

facilitating use of the Data Governance Council,

communicating program components and value to the Organization.

Advisory assistance from other levels.

IT Subject Resource Experts

System/Data Resource ExpertsIT Staff including Application

Development, Data Design,

Security, and other Data

Resource Management.

Com

munication

16

Metadata & Data Governance Roles & Responsibilities

17



Twitter at #RWDG 17



Twitter at #RWDG 17



17



• Where Do We Start – Define Data Domains

• Customer Data

• Product Data

• Vendor Data

• Material Data

• Financial Data

• Human Resource Data

• Transaction Data

• Research Data

• Shared Data

• Note that this is a sample list that of what companies use.

• Beyond this they break the domains into “aspects of customer”, “aspects of product”, … very particular to each company.

17

Metadata & Data Governance Metadata as a By-Product of a Data Governance Program

18



Twitter at #RWDG 18



Twitter at #RWDG 18



18




• Where Do We Start – Define Metadata Domains

• Data Definition Metadata

• Data Production Metadata

• Data Usage Metadata

• Privacy, Security, Compliance Metadata

• Business Rule Metadata

• Hardware Metadata

• Software Metadata

• Technology Metadata

• Vendor Metadata

• Note that this is a sample list that of what companies use.

• Beyond this they break the domains into “aspects of definition meta-data”, “aspects of production meta-data”, … very particular to each company.

18

19



Twitter at #RWDG 19



Twitter at #RWDG 19



19



• Where Do We Start – Define Organization Units

• The Organizational Units can be pulled from an organizational chart or they can be determined by Company, Division, Department, Team, …

• If the Organizational Units are defined by the Company it is often left to the Company to determine how granular they want to get with their units.

• It is not uncommon for organizational units to use different levels (some at the departmental level and some at the division level).

• Once the definition of units have been completed, the most senior level manager of that lowest granularity group identifies a logical person to help manage the stewards in their group.

19


20



Twitter at #RWDG 20



Twitter at #RWDG 20



20



• How Do We Populate the Stakeholder of the CDM? – Naturally! That is the Non-Invasive way!

• By the Metadata Steward Coordinator • Through project management • Through recall of past projects • Through existing committees & working groups

20


21



Twitter at #RWDG 21



Twitter at #RWDG 21



21



• How Do We Populate the Stakeholder of the CDM? – Metadata Steward Coordinator

• The Metadata Steward Coordinator often has the responsibility of identifying the operational meta-data stewards for their business unit by meta-data domain.

• This may require the coordinator to research and inventory the data that is being defined, produced and used in their business unit.

• This requires that the domains of data are defined and documented to the level of detail that will enable the Data Steward Coordinator to complete this task.

21


22



Twitter at #RWDG 22



Twitter at #RWDG 22



22



• First Order of Business:

– Identify Data Stewards and Record Who They Are

– Identify When and How They Should Be Involved

– Follow Governed Process

Metadata & Data Governance Applying Governance to Metadata

22

23



Twitter at #RWDG 23



Twitter at #RWDG 23



23



• Pro-Active Data Governance

– Build application of stewards into existing project management methodology

• Reactive Data Governance

– Build application of stewards into data quality methodology

– Build application of stewards into issue resolution process

• Triggers

– Using Stewards & Recorded Steward Metadata to Demonstrate Communications Improvement

• Escalation & Resolution

– Using Stewards & Recorded Steward Metadata to Get … the “Right” People Involved in the “Right” Decisions at the “Right” Time.

23


24



Twitter at #RWDG 24



Twitter at #RWDG 24



24



• Pro-Active Data Governance – Build Into Methodology

DATA DEFINERDATA

PRODUCER

DATA STEWARD

COORDINATOR

DATA GOVERNANCE ACTIVITY MATRIX

DATA

DEVELOPMENT

LIFE CYCLE

(DDLC)

INFORMATION

GATHERING

(DOMAIN, SYSTEM,

STEWARDS)

OPERATIONAL DATA STEWARDS

DATA USER

DATA DOMAIN

STEWARD

(or designee)

DATA DOMAIN / LOB/FUNCTIONAL AREA

ASSESSMENT &

REQUIREMENTS

PLANNING &

ANALYSIS

SOLUTION DESIGN

SOLUTION

DEVELOPMENT

SOLUTION TESTING

SOLUTION

IMPLEMENTATION

SOLUTION

MONITORING &

MAINTENANCE

Activity initiated re: this domain,

Data Domain Steward is involved

in identifying and recording info

related Domains, Systems,

Stewards per issue or task.

Activity initiated re: this domain,

Steward Coordinator is involved in

identifying Operational Stewards

in this LOB/FA that should

participate in this work flow.

Assure appropriate business

meta-data is recorded.

Propose alternatives

for data definition

solution that best fits

with defined

requirements.

Provide input to the

development of the

data production

solution.

Coordinate tasks associated

conducting the assessment and

requirements steps.

Provide definition

requirements &

gathering document.

Define data needed to

operate business &

report results.

Test data solution

from a definition

perspective. Assure

that appropriate

business meta-data is

recorded.

Provide production

requirements per

definition. Produce

data needed to

operate business &

report results.

Produce user

requirements. Use

data needed to

operate business &

report results.

Coordinate activities of

Operational Stewards including

project timelines, status reporting,

tactical decision making. Assure

appropriate business meta-data is

recorded.



project timelines, status reporting,

tactical decision making.

Provide data

definition guidance to

build the appropriate

solution.

Provide data

production guidance

to build the

appropriate solution.

Provide data usage

guidance to build the

appropriate solution.


conducting planning and analysis

steps.


for data production

that best fits with the

data definition

solution and defined

requirements.


for data usage

solution that best fits

with defined

requirements.



timelines, reporting. Propose

solution to Data Domain Steward.

Assure appropriate business



conducting planning and analysis

steps. Accept or Resolve solution

from the Steward Coordinator.

Coordinate activities of all

individuals related to development

work including timelines, status,

tactical decision making.

SYSTEM SMEs

IT

DATA SMEs

Test data solution

from a production

perspective. Assure

that appropriate


recorded.

Test data solution

from a usage

perspective. Assure

that appropriate


recorded.

Coordinate activities of the

Operational Stewards related to

testing work including timelines,

status, tactical decision making.



solution implementation including

timelines, status, tactical decision

making.



solution monitoring &

maintenance including timelines,

status, tactical decision making.

Perform EIS system testing.

Assure that appropriate technical


Perform EIS data testing. Assure

that appropriate technical meta-

data is recorded.

Coordinate and manage all

technical aspects of data solution

development. Assure that

appropriate technical meta-data is

recorded.


technical aspects of system

solution development. Assure

that appropriate technical meta-

data is recorded.

Coordinate system design with

Data Domain Stewards and

Steward Coordinators.

Coordinate data design with Data

Domain Stewards and Steward

Coordinators.



planning and analysis with Data


Coordinators.


technical aspects of data planning

and analysis with Data Domain

Stewards and Steward

Coordinators.



assessment & requirements

gathering with Data Domain


Coordinators.


technical aspects of data

assessment & requirements

gathering with Data Domain


Coordinators.


technical aspects of data

information gathering with Data


Coordinators. Assure appropriate

technical meta-data is recorded.



information gathering with Data


Coordinators. Assure appropriate

technical meta-data is recorded.

Participate in data

definition information

gathering as needed.

Participate in data

production

information gathering

as needed.

Participate in data

usage information

gathering as needed.



solution implementation.



solution monitoring &

maintenance.



implementation.



monitoring & maintenance.

Coordinate business tasks

associated with solution testing

steps.


associated with solution

implementation.


associated with solution

monitoring & maintenance.

As part of daily job,

identify operation

data issues pertaining

to their domain of

data.


identify operation


to their domain of

data.


identify operation


to their domain of

data.

24


25



Twitter at #RWDG 25



Twitter at #RWDG 25



25



• Reactive Data Governance – Build Into Response

• Data Quality Methodology – Qualify & Prioritize Data Issue – Identify Affected Data Domain – Identify Affected Data Stewards – Conduct Data Systems & Data Resource Discovery – Conduct Root Cause Analysis – Conduct Cost-Benefit Analysis – Analyze & Recommend Resolution – Gain Approval, Funding, Resources – Resolve Data Issue

• Cross Reference DQ Methodology & Resources – Who does What and When?

25


26



Twitter at #RWDG 26



Twitter at #RWDG 26



26



DATA GOVERNANCE & STEWARDSHIP

META-DATA MANAGEMENT

Metadata is a by-product and an enabler to improved Data Governance.

Governing Through Metadata

Metadata Governance

Governance must be applied to meta-data as the discipline of managing meta-data.

26

Metadata & Data Governance The Relationship – The Other Way

27



Twitter at #RWDG 27



Twitter at #RWDG 27



27



Metadata & Data Governance Governing Business & Technology Metadata

• Traditional Metadata Classifications: – Data Definition Metadata

• Data Modeling Tools • Database Catalogs • Data Dictionaries • Data Standards • Data Quality Tools • Business Rules

– Compliance Rules – Classification Rules – Privacy Rules – Security Rules

27

28



Twitter at #RWDG 28



Twitter at #RWDG 28



28




• Traditional Metadata Classifications: – Data Production Metadata

• Data Mappings Spreadsheets • Extract Transformation Load Tools

– Data Usage Metadata • Reporting Tools • Scheduling Tools • Report Catalog Tools • Ad-Hoc Reporting Tools

28

29



Twitter at #RWDG 29



Twitter at #RWDG 29



29



There are

a lot of

different

types of

meta-data.

Need people

to define,

produce, use

the meta-data.

Need

process

to manage

the meta-

data.

Need discipline

to maintain the

meta-data.

29


IT ASSETS

SYSTEM

DATA

NON-SYSTEM

DATA

IT ASSET MANAGEMENTMETA-DATA FRAMEWORK

STRUCTURED

DATA

UNSTRUCTURED

DATA

System Asset Data

Applications

Jobs/Procs

Programs/Scripts

Copybooks, ...

Database

Table Space

Table/View

Column

Index, …

Data Model

Entity

Attribute/Key

Domain

Valid Value, ...

Reporting Tool

Report/Query

Data/Logic

Distribution

Relationships between System

Infrastruct Data specified above.

Example: Database to Table to

Column

more … Inventory & Audit

Non-System Asset Data

Mainframe Hardware

Mainframe Software

Networks

Printers

Telephone

PC Hardware/Software

Technical Architecture

Mission/Vision

Best Practices

Policies

Standards

Procedures

Methodology

Configuration

People/Stewards

Locations

Timing/Dependencies

Business Rules

Metrics/Measurements

Relationships between Non-

System Infrastructure Data

specified above. Example: Method

to Procedure to Steward

more … Inventory & Audit

Structured Data

Resides in … “Data”

Databases/Tables/Columns

IT Data Management Tools

Business Technology Tools

Spreadsheets/Desktop Tools

Other

Unstructured Data

Resides in … “Artifacts”

Documents (Non Web-Based)

Content (Web-Based)

Desktop Tools

Video/Graphics/Video

Other

Relationships

Resides in … “Artifacts” if at all

Between Assets & the Data

Between System & Non-Sys Data

Within System & Non-System Data

Between Structured & Unstructured Data

Example: Applications (System Asset) to

Hardware (Non-System Asset),

Hardware to Software (Non-System Asset)

DATA GOVERNANCE FRAMEWORK

DATA GOVERNANCE FRAMEWORK

DA

TA

GO

VE

RN

AN

CE

FR

AM

EW

OR

K

DA

TA

GO

VE

RN

AN

CE

FR

AM

EW

OR

KRELATIONSHIPS

30



Twitter at #RWDG 30



Twitter at #RWDG 30



30



Metadata & Data Governance The Role / Tool of Data Stewards

• The Role of Metadata Data Stewards:

The Definition Metadata will not manage itself.

Metadata Definers: Responsible for Data Definition Metadata 2 Perspectives: 1. Someone has to Identify What Definition Metadata is Needed 2. Someone has to Provide the Definition Metadata Operational Data Stewards

The Definition of Metadata will not manage itself.

30

31



Twitter at #RWDG 31



Twitter at #RWDG 31



31




The Production Metadata will not manage itself.

Metadata Producers: Responsible for Data Production Metadata 2 Perspectives: 1. Someone has to Identify What Production Metadata is Needed 2. Someone has to Provide the Production Metadata Operational Data Stewards

The Production of Metadata will not manage itself.

31


32



Twitter at #RWDG 32



Twitter at #RWDG 32



32




The Usage Metadata will not manage itself.

Metadata Users: Responsible for Usage Data Metadata 2 Perspectives: 1. Someone has to Identify What Usage Metadata is Needed 2. Someone has to Provide the Usage Metadata Operational Data Stewards

The Usage of Metadata will not manage itself.

32


33



Twitter at #RWDG 33



Twitter at #RWDG 33



33



• Second Order of Business:

– Identify Metadata Stewards and Record Who They Are

– Identify When and How They Should Be Involved

– Follow Governed Process

Metadata & Data Governance Applying Metadata Stewards to Metadata Process

33

34



Twitter at #RWDG 34



Twitter at #RWDG 34



34



34


35



Twitter at #RWDG 35



Twitter at #RWDG 35



35



• Pro-Active Metadata Governance

– Build application of meta-data stewards into existing meta-data project management methodology

• Reactive Metadata Governance

– Build application of meta-data stewards into meta-data quality methodology

– Build application of meta-data stewards into meta-data issue resolution process

35


36



Twitter at #RWDG 36



Twitter at #RWDG 36



36



Metadata & Data Governance Revisiting the Common Data Matrix

36

37



Twitter at #RWDG 37



Twitter at #RWDG 37



37



Metadata & Data Governance Revisiting the Data Governance Framework

37

Operational Level

Operational Data Stewards (existing)

Data Definers, Producers, Users

These people are presently defining,

producing and using data as part of their

jobs. Recording of the Operational Data

Stewards will be an important enabler of

improved communications, coordination

and cooperation among stewards.

Tactical Level

Data Domain Stewards

Per assigned Subject Areas

Data Steward Coordinators

One per Business Unit

Strategic Level

Data Governance CouncilData Governance Sponsors Group

or Group of similar participation. One person, plus

alternate, for each Business Unit represented & IT.

Consider financial services & human resources.

Executive Level

Data Steering CommitteeSenior-most level knowledge of the program.

Leverage existing business structure as possible.

If no structure exists, utilize an IT Steering Committee

or an executive founded board or council.

Operational Level - Business Unit Specific

Strategic -

Enterprise

Tactical Level - Cross Business Unit

Executive

Non-Invasive Data Governance™ Operating Modelof Roles & Responsibilities

Escalation / A

pproval Path

Dat

a G

ove

rnan

ce P

rogra

m T

eam

(D

GPT)

IT S

ubje

ct R

esourc

e Exp

erts

Data Governance Program Team

Data Governance Team ManagerResponsible for Administering the Program,

facilitating use of the Data Governance Council,

communicating program components and value to the Organization.

Advisory assistance from other levels.

IT Subject Resource Experts

System/Data Resource ExpertsIT Staff including Application

Development, Data Design,

Security, and other Data

Resource Management.

Com

munication

38



Twitter at #RWDG 38



Twitter at #RWDG 38



38



Legend: Gray Block w/Bold X = Active Participant, Block w/Dull X = Optional Participant, * See Appendix for Template

Outcome / DeliverablesProcess Step

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

Me

ta-D

ata

Do

ma

in S

tew

ard

s

Me

ta-D

ata

Da

ta S

tew

ard

Co

ord

ina

tors

Me

ta-D

ata

Sy

sS

ME

s &

Da

taS

ME

s

Me

ta-D

ata

De

fine

rs

Me

ta-D

ata

Pro

du

ce

rs

Me

ta-D

ata

Us

ers

Meta-Data Stewards

Mapped to Meta-Data

Processes

Conceptual Modelof Taxonomy

Data Analysis for Data Listed inStep 3

Mapping of Source Data toData

Change Control, Versioning &Security Requirements

Documentation Validating“Best” Source

Data Movement, User Interface& Functional Development

Data List PerBusiness Requirements

Attributed Logical Model ofTaxonomy

XX X X X X Sign Off of Data Validationin the Repository

X

X X

X

1. Develop Conceptual Model /Data Taxonomy

4. Conduct Data Analysis of Attributes UsingData Analysis Template

5. Map Sources of Source Data toRepository Data Structures

6. Assess Change Control, Versioning, Security

7. Selection of the “Best” Sourcefor the Data

8. Design and Develop theData “Engine” and User Interface

2. Further Develop Logical ModelIncluding Attribution of Entities

9. Validate and Test Data

3. Specify Which Taxonomy Attributes Will BeIncluded in the Repository

38


39



Twitter at #RWDG 39



Twitter at #RWDG 39



39



Metadata & Data Governance Governing Metadata Through PMM

Fill in With Metadata Definition

Fill in With Metadata Location

Fill in With Domain Specs

Metadata

Fill in With Steward

Responsibility

39

40



Twitter at #RWDG 40



Twitter at #RWDG 40



40



Metadata & Data Governance Crossing the 2-Way Street

• Metadata & Data Governance are like “Love & Marriage”

“You can’t have one without the other!”

• Metadata is a By-Product of Governing & Stewarding Data.

• The Metadata Needs to be Governed Just Like Business Data.

40

41



Twitter at #RWDG 41



Twitter at #RWDG 41



41



Metadata & Data Governance Metadata Will Not Govern Itself

• Follow a Non-Invasive Metadata Governance™ Approach:

– Identifying rather than assigning meta-data stewards.

– Applying roles and responsibilities to meta-data processes.

– Providing formality and structure to what has always been informal.

• Thank you for attending my session!

41

42



Twitter at #RWDG 42



Twitter at #RWDG 42



42



• Robert S. Seiner

KIK Consulting & Educational Services – KIKconsulting.com

The Data Administration Newsletter – TDAN.com

Post Office Box 112571, Upper St. Clair, Pennsylvania 15241

412.220.9643, 412.220.9644 (Fax)

[email protected]

[email protected]

Real-World Data Governance Contact Information

real-world data governance: metadata & data governance

Technology

management of data

data stewardswriting

metadata data governancedont

seiner kik consulting

seiner kik consulting

seiner kik consultingtwitter

trademark of robert

pm est