This document discusses data governance at Fifth Third Bank and how the Vice President of Enterprise Data, Greg Swygart, is working to improve it. It notes that previously the bank did not have a strong data culture or data literacy. Greg is implementing a centralized data management program to develop these areas using best practices. He is focusing on adoption of the Alation data catalog to help formalize data stewardship and accountability. The document emphasizes that human management and changing behaviors and mindsets is key to successful data governance, and that words used are important to avoid making it feel like a burden.
4. 4
Classification: Confidential
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
Who Am I
Greg Swygart, Vice President of Enterprise Data at Fifth Third Bank.
Greg is passionate about creating data-driven cultures within complex working environments. He has lived in
Cincinnati since he graduated from Xavier University and spends most of his free time trying to convince his
wife to go on hikes and watching Disney movies with his two daughters. Greg has spent the last 8 years
working in Data and Analytics in various industries including Customer Service, Retail, and Banking.
5. 5
Classification: Confidential
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
Agenda
• Intro to Fifth Third Bank + Greg
• The Fifth Third Data Landscape [problem]
• What is Greg’s role in that landscape? [solution]
• What big obstacles has Greg faced?
• How has he overcome those obstacles?
• Words Matter for Data Governance
• How do you get people to change?
• ADKAR
7. 7
Classification: Confidential
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
Data Platform Ecosystem
Move
Abstract
Interact
Locate Data Explore / Discover / Engineer / Modeling Report & Visualize Integrate
Process
Store
Distributed/Processing Semi/Structured Unstructured
* Future State
redis
Manage
Data Warehouse Relational MPP ODS
IBM IDAA
[& OR]
Watson Studio
Data Classification
Data Quality
Data Catalog Lineage & Metadata Glossary
Batch ETL Extract/Load
Mainframe
Aurora DynamoDB S3 Store EMR
Non-EDO Managed
Deploy
Scheduling Provision
Tokenization
Obfuscation
Data
Capabilities
Axiom
Software Version Orchestration Artifacts
Virtualize Caching
Enrich
*
Mastering Data
*
Stream
*
*
Change-Data-Capture
Enrich
ETL DevOps
*
Secure File Transfer
On-Premise Cloud
8. 8
Classification: Confidential
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
Why Data Management
The Basel Committee - initially named the Committee on Banking Regulations and Supervisory Practices - was
established to enhance financial stability by improving the quality of banking supervision worldwide, and to
serve as a forum for regular cooperation between its member countries on banking supervisory matters.
The EDM Council is the Global Association created to elevate the practice of Data Management as a business
and operational priority. The Council is the leading advocate for the development and implementation of Data
Standards, Best Practices and comprehensive Training and Certification programs.
9. 9
Classification: Confidential
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
9
Current Landscape
DCAM Scoring Model
Not Initiated
Conceptual
Developmental
Achieved
Enhanced
Defined
3.5
3.3
3.2
3.3
3.3
3.4
3.1
4.3
3.8
3.5
3.9
3.7
3.9
3.7
0
1
2
3
4
5
6
1.0 Strategy and Business Case
2.0 Data Program and Funding Model
3.0 Business and Data Architecture
4.0 Data and Technology Architecture
5.0 Data Quality Management
6.0 Data Governance
7.0 Data Control Environment
EDMC 2020 Benchmark Component Scores
All Financial Services Financial Services Tier 2 & 3
10. 10
Classification: Confidential
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
10
Crossing the Capability Chasm
DCAM Scoring Model
Not Initiated
Conceptual
Developmental
Achieved
Enhanced
Defined
• Awareness: The Bank did not know how well we were performing with
Data Management best practices
• Strategy: Create a centralized Data Management Program to develop the
organization’s data literacy based on DCAM (People, Process, & tools)
• Desire: The Bank did not have a data driven culture
• Strategy: Make data fun and focus on Alation adoption and curation
• Knowledge: Many data consumers have not had the formal training
required to unleash analytical capabilities
• Strategy: Develop Data Management training curriculum and provide the
right processes and tools (no/low code options)
• Ability: Data consumers do not have the skills required to leverage data
• Strategy: Create scalable framework (Bei Dati) to execute Data
Management best practices across the Bank
• Reinforcement: Data consumers do not understand the value of
adopting new tools and technologies to leverage data.
• Strategy: Consistently drive business value & leverage Change
Management techniques
11. 11
Classification: Confidential
FOR INTERNAL USE ONLY
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
11
Enterprise Data Designations
Risk Aggregation Data (BCBS 239)
Policy and Standards
Execution Operational
Progress Measurement and
Quality Assessment
EDO Change Management &
Priority Data
Change Management and Priority
Existing data sets
Robust Data Management
integration with Table Top
Reviews
Measurement of Existing/ New
and Enterprise Data sets.
Agility IT Release
Data Management Operational
Bank wide
Data Management engrained in
LOB
DM Cube expanded and
available for self service to
consumers.
Phase Phase Phase
Create a scalable and efficient approach for the implementation of Data
Management Best Practices
Enterprise Data Designations
• Risk Aggregation Data (BCBS 239)
• Centralized DM Program
• Policy and Standards
• Progress Measurement and Quality
Assessment
EDO Change Management & Existing Data
• Change Management and Priority
Existing data sets
• Robust Data Management integration
with Tabletop Reviews
• Measurement of Existing/ New and
Enterprise Data sets.
Agility IT Release
• Data Management Operational Bank
wide
• Data Management engrained in LOB
• DM as an accelerator
Ideate Scale Federate
D
o
n
e
N
o
w
L
a
t
e
r
Customer Feedback
& Outcome Validation
Customer Feedback
& Outcome Validation
• Integration of Data Management into Engineering DNA
• Reduce Data Management Risk
• Drive accountability and ownership of data
• Improve value of data
12. 12
Classification: Confidential
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
Data Management – Standard of Care
DCAM guidance is at the core of our Data Tech Strategy
-
+
-
+
C
o
n
t
r
o
l
s
B
u
s
i
n
e
s
s
I
m
p
a
c
t
Access
Permissions
Service
Agreements
Data
Dictionary
Data
Quality
Business
Glossary
Technical
Lineage
Consumption
Lineage
Business
Process
Lineage
13. 13
Classification: Confidential
FOR INTERNAL USE ONLY
F
I
F
T
H
T
H
I
R
D
|
2
0
2
1
Create something Delicious
13
Plain……………..When your data set is not designated as
Enterprise Data or on the roadmap for designation and
already exists in the data environment.
Specialty………. When your data set is not designated as
Enterprise Data or on the roadmap for designation and is
being newly created or modified in the data environment.
Supreme…………When your data set is designated as
Enterprise Data or on the roadmap for designation OR when
your stakeholders/ business partners have communicated
material impact of data quality to the data set.
Menu
Bei Dati
14. 14
Classification: Confidential
Plain
(Existing Data)
Crust – Access Permissions
Document IT Role access information in the "Access Permissions"
section in Alation at the level (Schema/Table).
Sauce – Service Agreements
Document the data availability information in the "Service
Agreement" section of the catalog page for the level
(Schema/Table) necessary.
Cheese – Data Dictionary
Document Titles and Descriptions for Schemas/Tables/Columns
Titles should be a direct "English" translation of the table/ column
Descriptions should be of technical nature and contain
information regarding the purpose and use
200 Calories
Flavorable for age:
Existing
EDO Change
Enterprise Data
15. 15
Classification: Confidential
Specialty
(Newly created
or modified data)
400 Calories
Flavorable for age:
Existing
EDO Change
Enterprise Data
Crust – Access Permissions
Document IT Role access information in the "Access Permissions"
section in Alation at the level (Schema/Table).
Sauce – Service Agreements
Document the data availability information in the "Service
Agreement" section of the catalog page for the level
(Schema/Table) necessary.
Cheese – Data Dictionary
Document Titles and Descriptions for Schemas/Tables/Columns
Titles should be a direct "English" translation of the table/ column
Descriptions should be of technical nature and contain information
regarding the purpose and use
Meat – Data Quality
Identify current table level Data Movement controls and implement
monitoring where necessary.
Profiling Data Quality rules.
Veggies – Technical Lineage
Document Source(s) for table and columns in Alation
16. 16
Classification: Confidential
800 Calories
Crust – Access Permissions
Document IT Role access information in the "Access Permissions"
section in Alation at the level (Schema/Table).
Sauce – Service Agreements
Document the data availability information in the "Service
Agreement" section of the catalog page for the level
(Schema/Table) necessary.
Cheese – Data Dictionary
Document Titles and Descriptions for Schemas/Tables/Columns
Identify Critical Data Asset, Element criticality, Data Steward
Meat – Data Quality
Identify current table level Data Movement controls and
implement monitoring where necessary.
Profile Critical Data Elements and utilize Ataccama to write
necessary Data Quality Rules
Veggies –Lineage
Business Process – Align to business processes
Tech - Document Source(s) for table and columns in Alation and submit
manual template for system level hops of Critical Data Elements.
Consumption – Manually document the consumption of critical data
assets and critical data elements
Extra Cheese – Business Glossary
Create a Business Glossary in Alation documenting
Business Terms and align to Critical Data Elements
Well Done
Certification and QA
Flavorable for age:
Existing
EDO Change
Enterprise Data
Supreme
(Enterprise Data/
Business Critical Data)