DG FRAMEWORK AND MATURITY STAGES

I. OVERALL FRAMEWORK

The overall DG framework implemented at VPBank consists of 3 main pillars: People, Process, and Technology spanning across all stages of the data life cycle:

Creation  Conversion  Conservation  Consumption

Pillars Components Status assessment Challenges Proposed solutions

- Large scope of DG which
requires additional human
resource
- Recruit 1 more
- Do not have full-time data
person for Data
steward position
Governance
- High personnel turnover in
- Data Committee was set up in 2013. DC is chaired by Department as per
- Data Data steward position
CEO and includes BICC head and other division heads. approved head count
Committee - Data steward does not have a
- 13 Data Committee meetings have been held since 2014 in 2018
- Working team full knowledge about DG,
- Working team includes Data Governance Department in - Enhance
includes: database and system
BICC; Data steward of each Division; Data custodians communication and
+ Data - Data steward is not active in
(IT) and Data users training for Data
Governance supporting DGD in
People - Data Governance Department was set up in 2014. steward on role,
Department communicating and fixing
Currently DGD includes 2 main components: 1. Data responsibility, and
+ Data steward of data issue
policy & Standard; 2. Data Quality data knowledge. Commented [DLT(1]: DGD plays the role as secretary for
each Division - Difficult to define data DC and is a bank-wide and centralize team to implement DG
- Data Steward positions have been appointed at 5 main - Set up full-time
+ Data custodians ownership for a lot of in VPBank
divisions: Retail, SME, Finance, Ops, Risk Data steward
(IT) historical data fields
- Multiple monthly Data steward meetings and trainings positions in 2019
+ Data users - Currently there is no Data
have been organized - Set up a full-time
Steward position for IT
Data steward position
division. In some cases, IT
in IT division in 2019
AM of BICC plays this role
but is too busy with other IT
tasks
 - There are still several
- Issued 5 policies, 3 procedures, 3 guidelines related to outdated information in
data governance customer service guidelines
- Review and
- Data - Implemented Customer information capture guidelines which affects data capture
update/request related
governance in T24 system activities
parties to update data
documents, - Operationalize data stewardship model since 2015 - There isn’t a formal guiding
capture documents on
processes and - Conducted multiple trainings to data stewards documents for when there is a
Process a regular basis
guidelines - Set up cooperation mechanism with branch service request to update data in
- Need to address
- Data department (Ops) to fix data issues more effectively source systems not from
data ownership
stewardship - Implemented a clear process to analyze, resolve, and customer but from VPB
identification issues
model monitor data issues internal units. This is partly
soon
- Implemented online training for CSRs because of complication in
data ownership identification

- Set up and updated data quality rules in source systems - Bank-wide business glossary is
(T24, RLOS, CLOS, Ebank Util): excel file which makes it difficult
+ Set up and updated DQ rules for data fields in customer to maintain, update, track history
- Data quality - Study and utilize
information modules in T24 system since 2015 and is not user-friendly
rules in source IBM tools to review
+ Set up rules for data fields in application forms in RLOS - DQ rules can’t sync between
systems and improve business
since March, 2018 different source systems which
- DQ tools glossary, improve
+ Set up rules for data fields in CLOS and integrated data cost more time and resource to
- Data issues data issue tracking,
Technology from CLOS to T24 since January, 2018 manual set up the same DQ rules
tracking tool DQ rules set up and
- Used SSIS, SQL, excel to generate and automate DQ in multiple systems
- Develop a tool synchronization, and
reports - Data issue tracking tool is a
to maintain data ownership
- Implemented data issues tracking tool in BIC portal in web-based tool and can’t perform
business tracking Commented [DLT(2]: Anh nghĩ phần này nên mention về
April, 2018 and granted user for data stewards to follow data more complex functions such as việc minh đang doing data quality/data steward một cách
glossary
issues in this portal monitoring data linage or manually. Sau đó đưa ra challenge là cần leverage nền tảng
cong nghiệ hiện hữu trong bank để automate các tasks này
- Implemented code management function in customer 360 tracking data issues history in
tool systems

II. Maturity stages

 1. Review of DG maturity stages created by I-CREATE (VPBank’s consulting partner for DG framework in 2014)

In 2014, as per this framework, VPBank is between “Informed” and “Initiated” stage.
Currently, as per our assessment, VPBank is at “Implemented” stage.

VPBank status
Maturity stage Criteria Commented [DLT(3]: Cần state clearly đây là maturity
People Process Technology curve based on Icreate consultants nhé.
- Lack of business ownership, Stewards and Và hiện minh cần revise và xây dựng kế hoạch hành động
theo đúng thực tế hiện hành của VPBank
custodians not yet identified
- No clear policies on ownership, quality and
Informed access
- Technology is used in ad-hoc manner at a very
late stage in the data lifecycle resulting in
tremendous overhead
- Stewards and custodians identified but still no
ownership from business yet
- Policies in access exist and basic guidelines to
Initiated
deal with quality exists
- Some automation in place in integration tool to
reduce ad-hoc fixes
- Lack of clear data ownership but -Had clear policies and - Both human and
- Business ownership exists at BU level
main businesses are aware of their processes in data technological
- Clearly defined policies exist for a subset of
responsibility to make decision quality, data access, and solutions are used to
data or for a BU with strong guidelines for
regarding their subset of data data issue remediation fix data issues
Implemented monitoring as well
- Already stewards for Finance, - DQ rules are set up at
- Technology used not only to fix but also to
Risk, Ops, Retail, SME and source systems to
prevent data quality issues at points of
involved other Divisions prevent data issues at
creation
point of creation
- Enterprise level business ownership with
Evolved strong prioritization and remediation
capabilities
 - Self-sustaining policies are in place with
coordination and collaboration across Bus for
information needs
- Technology used consistently and in the most
efficient manner allowing everyone across the
enterprise to monitor and report

III. How to get to “Evolved” stage

1. People:
- Need to have a clear data ownership identification mechanism and implement relevant processes
 Need top-down agreement
- Need to have full-time data steward positions
 Need top-down agreement (2019)
2. Process:
- Review and update all data governance documents to make sure policies are updated and processes are practical and easy to implement
 Already in progress
- Enhance bank-wide communication on data governance and training for stewards
 Already in progress
3. Technology
- Use smart tools to log, prioritize, assign, resolve and monitor data issues in combination with data issue remediation proces s
 Researching IBM tools
- Develop a comprehensive business glossary using user-friendly tools which allow for ease of access, maintain, and update across different BUs/SUs
 Researching IBM tools
- Implement master data management to resolve data consistency issues and provide a single view of customer and product data
 MDM project is in PIR phase
Implement data quality tools to better monitor data quality (through automated DQ dashboards with self-service capability) and set up DQ rules to
prevent data issues at all stages in data life cycle
 Will research IBM tools and international best practices? Commented [DLT(4]: Cái này thì minh cứ tạm propose
thôi. Vì chưa chắc Iggy đã ok với maturity curve này.
Mình sẽ work với Iggy revise this maturity curve và xây dựng
action plan tương ứng nhé.