National Data Management Office

*Data Catalog Implementation Guidelines

Version 1
June 2020

*This is Draft Document and it's not a mandatory to be used by entities

Table of content
1. Data Catalog Guidelines Overview............................................................................................................................ 3
2. Develop Data Catalog.................................................................................................................................................. 3
3. Populate Technical Metadata ................................................................................................................................... 10
4. Populate Business Metadata .................................................................................................................................... 13
5. Annotate metadata ..................................................................................................................................................... 17
6. Update Metadata ........................................................................................................................................................ 20
7. Request Data Quality support .................................................................................................................................. 23
8. Publish metadata to the National Data Catalog..................................................................................................... 26
 1. Data Catalog Guidelines Overview
The Data Catalog Guidelines document has been created to guide the Entities in implementation of the Data
Catalog processes required by NDMO’s Data Management & Personal Protection Standards. The list of key data
catalog processes includes:

 Develop Data Catalog – the overall approach for development of the Entity’s Data Catalog
 Populate Technical Metadata – registration of technical metadata in the Entity’s Data Catalog
 Populate Business Metadata – registration of Business metadata in the Entity’s Data Catalog
 Annotate Metadata – management of annotations to metadata added by users in Data Catalog
 Update Metadata – change management of metadata in Data Catalog
 Request Data Quality Support – raising data quality issues via Data Catalog
 Publish Metadata to the National Data Catalog – publishing metadata to be shared across Entities within
National Data Catalog

For all the processes presented in this document relevant diagrams have been created to illustrate necessary
steps to be taken by the Entity’s data governance roles. Additionally, RACI matrix presenting in detail
responsibilities of all required data governance roles has been defined for each of the processes. ‘Develop Data
Catalog’ and ‘Populate Technical/Business Metadata’ processes require usage of templates which are available
in the Artifacts subsections.

2. Develop Data Catalog

Overview
Data Catalog Development process has been designed to help government Entities start their Data Catalog
development and support them in ongoing Data Catalog development. The process should be initiated by
activating Data Operating Model roles described in Organizational manual and Operational Model for the
National Data Management Office.
The Entity shall develop their Prioritized Attributes Inventory consisting of the list of prioritized attributes to be
included in the Data Catalog. This will enable the Entity to have an overview of the crucial data it possesses and
to identify which data assets should have their business and technical metadata populated first. For all the
prioritized data attributes the Entity shall build their metadata structure which comprises business and technical
metadata. Business metadata focuses on the content and condition of the data and includes the non-technical
names and definitions while technical metadata focuses on the technical details of data, the systems storing the
data and movement of data between systems. the Entity shall collect business metadata according to the
metadata structure defined in provided Business Glossary template. Technical and business metadata shall be
populated, and Data Stewards shall be assigned to them.

The populated Entity’s Data Catalog shall be reviewed by Business Data Executives and Chief Data Officer
(CDO). If any issue is identified during the reviews, Data Stewards shall be delegated to perform necessary
updates. Data Catalog Development process is concluded by accepting by Chief Data Officer (CDO) and
provisioning of Data Catalog access to data users.
Process

Activities
1 – Initiate data cataloging exercise – Chief Data Officer (CDO)
 Activate operating model roles required to develop and maintain the Entity’s Data Catalog including:
Business Data Executives, Data Management Officer, Business Data Stewards and IT Data Stewards
 Get to know National Data Management & Personal Data Protection Standards (including standards for
Metadata and Catalog data management domain) provided by National Data Management Office
 Delegate Data Management Officer to plan data cataloging exercise

2 – Plan data cataloging exercise – Data Management Officer

 Based on the Data Management and Privacy Strategy and Plan, create a Data Catalog Plan including a
roadmap with the activities and key milestones for the implementation of the Data Catalog automated tool
according to the steps described in the Data Catalog Development process

3 – Initiate Prioritized Attributes Inventory exercise – Data Management Officer

 Initiate an identification and a documentation of prioritized attributes as part of the Data Catalog Plan
 Meet with relevant stakeholders and assign to Business Data Stewards and Business Data Executives
responsibilities required for prioritization of the Entity’s data attributes

4 – Prioritize data attributes – Business Data Steward

 Identify key data domains that describe the Entity’s core operations (main activities). Selected domains
should be mutually exclusive and cover the Entity’s main activities
 Prioritize identified data domains in the context of inclusion in data catalog development. Factors to be taken
into account for prioritization:
 o Importance of the data domain within sector
o Importance of the data domain for other Entities across government
o Readiness of business stakeholders (to provide business metadata details) within the domain
o Maturity of data management within the domain
o Previous attempts to define metadata within domain
 Within each of prioritized domains determine prioritized attributes:
o Determine the Entity’s key strategic and operational reports and data attributes that are required
to supply them
o Determine the Entity’s master data (core data which is created and owned by the Entity, critical
to the Entity’s operations and analytics) attributes
o In case the specific domain is of high importance for the Entity, additional prioritized attributes
from this domain can be provided
 Consolidate the identified data attributes
 Create a prioritization list of consolidated data attributes using Prioritized Data Attributes Inventory template
(available in the Artifacts subsection). For each prioritized data attribute fill in the following information:
o Attribute ID – The unique identifier of data attribute that starts with "ATR" prefix followed by
number of data attribute
o Business Domain Name - The business domain of the attribute defined based on the Entity's
main activities
o Data Source - Name of the data source where attribute is physically stored in
o Schema Name - Name of the schema in database that the attribute is stored in
o Table Name - Name of the physical table/data set where the attribute is stored in
o Data Attribute Name - Physical name of the attribute in data source
o Rationale - Reason why the data attribute has been added to the inventory (e.g. attribute is
included in a key strategic/operational report, master data attribute or part of problematic data
domain)
o Name of Business Data Executive/Steward - Name of the business data executive/steward who
identified the prioritized attribute
o Notes (optionally) - Additional comments on the attribute

5 – Review the prioritized data attributes - Business Data Executive

 Review if all the identified key data attributes have been correctly added to Prioritized Data Attributes
Inventory template and there are no missing attributes which should be added to the inventory
 Review if there are incomplete fields for the attributes listed in the Prioritized Data Attributes Inventory
template
 Review information provided for each identified attribute in the Prioritized Data Attributes Inventory template
 Share completed Prioritized Data Attributes Inventory template with Business Data Stewards to build
business glossary as a part of metadata population process

6 – Assign Data Stewards to build and populate the metadata – Business Data Executive
 Assign Business and IT Data Stewards to the Prioritized Data Attributes. Assignment to metadata should
reflect the current data stewardship within the Entity.
7 – Populate technical metadata – IT Data Steward
 Register technical metadata for prioritized data attributes in the Data Catalog automated tool
 Refer to Populate technical metadata section of this document for detailed activities (this step has been
developed as a separate process).

8 – Populate business metadata – Business Data Steward

 Create business glossary for prioritized data attributes in the Data Catalog automated tool
Refer to Populate business metadata section of this document for detailed activities (this step has been
developed as a separate process).

9 – Review the Data Catalog – Data Management Officer

 Review the Entity’s Data Catalog including:
o Alignment of business metadata in the Entity’s Data Catalog with the metadata structure defined in
Business Glossary template.
o Assignment of Business and IT Data Stewards to all metadata registered within the Entity’s Data
Catalog
o Quality of metadata stored in the Entity’s Data Catalog including the following dimensions:
- Completeness - degree to which business glossaries and data dictionaries are completed.
Example metric: a number of missing data attributes descriptions
- Accuracy - degree to which definitions and descriptions align to a business context.
Example metric: a number of data attributes whose logical names present their precise
business friendly semantic names
- Consistency - degree to which definitions of metadata are consistent across Entity.
Example metric: a number of data attributes in the same table that are assigned to different
Business Domains

10 – Delegate to a relevant Data Steward – Data Management Officer

 Perform a root cause analysis on the received issue and develop a resolution of the issue’s root cause
 Delegate to relevant data steward to fix the issue

11 – Perform necessary updates – Business/IT Data Steward

 Based on the Data Management Officer’s assessment, take necessary actions to resolve the identified issue
 Once the update or fix is done and approved by Data Management Officer, inform Data Business Executive

12 – Review the Data Catalog – Business Data Executive

 Review the Entity’s Data Catalog including:
o Alignment of business metadata in the Entity’s Data Catalog with the metadata structure defined in
Business Glossary template.
o Assignment of Business and IT Data Stewards to all metadata registered within the Entity’s Data
Catalog
o Quality of metadata stored in the Entity’s Data Catalog including the following dimensions:
- Completeness - degree to which business glossaries and data dictionaries are completed.
Example metric: a number of missing data attributes descriptions
 - Accuracy - degree to which definitions and descriptions align to a business context. Example
metric: a number of data attributes whose logical names present their precise business
friendly semantic names
- Consistency - degree to which definitions of metadata are consistent across Entity. Example
metric: a number of data attributes in the same table are assigned to different Business
Domains
 In case an issue is detected, report it to Data Management Officer.

13 – Accept the Data Catalog – Chief Data Officer (CDO)

 Approve the completion of milestone of the Entity’s Data Catalog development
 Notify National Data Management Office that the Entity’s Data Catalog has been accepted
 Delegate IT Data Stewards to provide the Entity’s data users an access to the Data Catalog

14 – Provide access to Data Catalog – IT Data Steward

 Create access groups (groups of users with the same level of access to metadata) in the Data Catalog (if
not already created)
 Assign Data Catalog users to created access groups (if not already assigned)
 Assign permissions to access newly added data assets (business and technical metadata) for data catalog
user groups
Governance

Roles

Data Management
Chief Data Officer

IT Data Steward
Business Data
Business Data
Executive

Steward
Officer
(CDO)
NDMO

Activities
sties

1 - Initiate data cataloging exercise I A I I I I

2 – Plan data cataloging exercise A C R C C

3 – Initiate Prioritized Attributes Inventory

exercise A C R I I

4 – Prioritize data attributes A I R I

5 – Review the prioritized data attributes A R C C I

6 – Assign Data Stewards to build and

populate the metadata
R I I

7 – Populate technical metadata A I R R

8 – Populate business metadata A I R R

 9 - Review the Data Catalog (Data Management
Officer)
R C C

10 - Delegate to a relevant Data Steward C R I I

11 - Perform necessary updates C I R R

12 – Review the Data Catalog (Business Data

Executive)
R I C C

13 – Accept the Data Catalog I R I I I I

14 – Provide an access to the Data Catalog I I I C R

R: Responsible – Person who does the task

A: Accountable – Person who delegates work and provides final review on a task or deliverable before it is
deemed complete
C: Consulted – Person who provides input on a task or deliverable based on the impact on their work or their
domain of expertise
I: Informed – Person who needs to be kept in the look on task or deliverable progress
Artifacts
Prioritized Data Attributes Inventory template

Business Data
Data Schema Table Name of business data
Attribute ID Domain Attribute Rationale Notes
Source Name Name executive/steward
Name Name
 3. Populate Technical Metadata
Overview
The purpose of Populate Technical Metadata process is to register technical metadata in Automated Data
Catalog Tool. It can be done by batch upload of the defined template files or by direct connecting of data catalog
to data sources.

Process
Activities
1 – Initiate metadata population exercise – Data Management Officer
 Initiate technical metadata population exercise as a part of Data Catalog development process
 Meet with IT Data Stewards to assign them responsibilities related to the population of technical metadata
for Prioritized Data Attributes

2 – Verify existence of technical metadata in Data Catalog – IT Data Steward

 Verify if required technical metadata already exists within Data Catalog tool (it could be registered before
e.g. by connecting entire data source to Data Catalog tool)

3 – Prepare for technical metadata ingestion – IT Data Steward

 In case of online integration - connect the key data sources to the Data Catalog automated tool to enable an
ingestion of technical metadata for Prioritized Data Attributes
 In case of offline integration - prepare Technical Metadata Inventory templates with technical metadata
definition for Prioritized Data Attributes (See Artifacts). Populated templates should be transformed in the
next step to the format required for upload to the Data Catalog tool

4 – Ingest technical metadata to Data Catalog – IT Data Steward

 Ingest technical metadata through a connection of the data sources to the Data Catalog automated tool or
by uploading prepared file templates

5 – Review populated technical metadata – Data Management Officer

 Review completeness of technical metadata population for Prioritized Data Attributes:
o All prioritized data attributes should have technical metadata registered within data catalog

6 – Perform necessary updates – IT Data Steward

 Based on the Data Management Officer’s assessment, take necessary actions to resolve the identified issue
 Once the update or fix is done inform Data Management Officer
Governance

Roles

Data Management
Chief Data Officer

IT Data Steward
Business Data
Business Data
Executive

Steward
Officer
Activities
sties

1 - Initiate metadata population exercise C I R I I

2 - Verify existence of technical metadata in

Data Catalog
I A I R

3 - Prepare for technical metadata ingestion I A I R

4 - Ingest technical metadata to Data Catalog I I I R

5 – Review populated technical metadata A R I I

6 – Perform necessary updates I A I R

R: Responsible – Person who does the task

A: Accountable – Person who delegates work and provides final review on a task or deliverable before it is
deemed complete
C: Consulted – Person who provides input on a task or deliverable based on the impact on their work or their
domain of expertise
I: Informed – Person who needs to be kept in the look on task or deliverable progress

Artifacts
Technical Metadata Inventory template
Data Data
Entity Data Schema Schema Table Table Data Data Primary
Attribute ID Source Attribute Data Type Data Scale Nullability
Name Source Name Description Name Description Length Format Key
Technology Name
 4. Populate Business Metadata
Overview
The purpose of Populate Business Metadata process is to create Business Glossary in Automated Data Catalog
Tool. It can be done by batch upload of the defined template files or directly in the tool.

Process
Activities
1 – Initiate metadata population exercise – Data Management Officer
 Initiate business glossary population exercise as a part of Data Catalog development process
 Meet with Business Data Stewards and Business Data Executives to assign them responsibilities related to
the population of metadata

2 – Build a business glossary f or the prioritized data attributes – Business Data Steward
 Build business glossary using Business Glossary template to document and collect business metadata for
prioritized data attributes. A business glossary is a repository of business metadata that adds semantic
context to data. It enables an organization to build trust and create accountability through common business
terminologies. It defines the business terms and definitions related to physical assets so that users can
easily collaborate, understand the semantics behind data and how it is being used.
 Include in Business Glossary template all the attributes listed in Prioritized Data Attributes Inventory
template.
 For each attribute included in the Business Glossary template fill in the following information:
o Attribute ID - The unique identifier of data attribute that starts with "ATR" prefix followed by number
of the attribute. This is a reference to the attribute identifier from Prioritized Attributes Inventory.
o Sector Name - Describes an area of the economy in which government entities share common or a
related services or operating characteristics. Different sectors allow for a categorized analysis of the
state of the nation
o Government Entity - Describes any governmental body, agency, or authority in any KSA jurisdiction
exercising executive, legislative, regulatory or administrative functions related to the Saudi
Government
o Business Domain Name - The business domain of the attribute defined based on the entity's main
activities
o Business Sub-Domain Name - The business sub-domain of the attribute defined based on the
entity's sub-activities
o Attribute Logical Name (English) - The logical, or business friendly semantic name of the attribute
(column)
o Attribute Logical Name (Arabic) - The logical, or business friendly semantic name of the attribute
(column)
o Attribute Description (English) - A description written in basic, interpretable English language
detailing the purpose and function of the data attribute
o Attribute Description (Arabic) - A description written in basic, interpretable Arabic language detailing
the purpose and function of the data attribute. Descriptions help to provide context and clues to
where the attribute is being used
o Null Applicability - Nulls are attribute columns containing no values (empty cells). By default, a
column can hold NULL values. If an attribute contains a NOT NULL constraint, it forces the column
to NOT accept empty values in the cell
o Sample Values - Presents a sample output of the data value (dummy data) if queried to illustrate
how format of the data type would show to end data consumers
o Values From Lookup / Reference Table - Indicates whether the data field has a list of pre-defined
values that it can take
 o Lookup / Reference Table Name - Indicates what is the source of the reference / lookup table. It
could either be defined by the entity or it could follow international standard
o Attribute Business Rules - Describes business statements that declare or constrain data values in
relation to the business use of data. It is intended to assert business friendly structure and influence
over the behavior of the business processes and operations
o Update Frequency - Indicates how often is an attribute value updated based on a pre-defined
business rule. It could be: Daily, Weekly, Monthly, Yearly
o Business Data Executive Name - The name of an executive/manager accountable for the
development, usage, and maintenance of the business and technical metadata of the data domain
where the the attribute is located
o Business Data Executive Email - The email of an executive/manager accountable for the
development, usage, and maintenance of the business and technical metadata of the data domain
where the the attribute is located
o Business Data Steward Name - The name of the business professional recognized as subject matter
experts who defines and controls business metadata of the attribute
o Business Data Steward Email - The email of the business professional recognized as subject matter
experts who defines and controls business metadata of the attribute
o Create Responsibility - Indicates the entity that is responsible to create this data attribute. This
implies no other entity shall create another version of this data attribute value
o Read Responsibility - Indicates the entities that are allowed to read the data attribute
o Update Responsibility - Indicates the entity/entities that are allowed to update this data attribute.
o Delete Responsibility - Indicates the entity that is responsible to delete (which includes archiving and
retention) this data attribute. This implies no other entity shall delete this data attribute value
o Notes (optionally) - Additional comments on the attribute
 If the Entity’s business glossary already exists, verify its consistency with a metadata structure defined in the
Business Glossary template and convert existing business terms to the Business Glossary template
requirements. The Entity can augment the mandated metadata structure with additional elements based on
the Entity’s requirements.

3 – Review the business glossary – Business Data Executive

 Review the Business Glossary template filled in by Business Data Steward including:
o Verification if all data attributes included in Prioritized Data Attributes Inventory template have been
added to the Business Glossary template
o Alignment of business metadata structure included in the created business glossary with the
metadata structure required by Business Glossary template
o Quality of metadata in business glossary including the following dimensions:
- Completeness - degree to which business glossaries and data dictionaries are completed.
Example: missing data attributes descriptions
- Accuracy - degree to which definitions and descriptions align to business context. Example:
data attributes with logical names that don’t reflect their business meaning
- Consistency - degree to which definitions of metadata are consistent across Entity. Example:
data attributes from the same table that are assigned to different Business Domains

4 – Perform necessary updates – Business Data Steward

 Based on the Business Data Executive’s assessment, take necessary actions to resolve the identified issue
 Once the update or fix is done inform Business Data Executive
5 – Ingest Business Glossary to Data Catalog – IT Data Steward
 Ingest the prepared business glossary for the prioritized data attributes into the Data Catalog automated tool
 batch upload of the defined template files
 In case of batch upload of the Business Glossary to the tool:
o Prepare Business Glossary template to be uploaded in the format required by the Data Catalog
tool
o Execute batch upload of Business Glossary to the Data Catalog tool
 In case of direct creation of the Business Glossary in the tool:
o Develop Business Glossary for Prioritized Data Attributes directly in the Data Catalog Tool

6 – Review populated business metadata – Data Management Officer

 Review completeness of business metadata population for Prioritized Data Attributes
o All prioritized data attributes should have business metadata registered within data catalog

7 – Perform necessary updates – IT Data Steward

 Based on the Data Management Officer’s assessment, take necessary actions to resolve the identified issue
 Once the update or fix is done inform Data Management Officer

Governance

Roles
Data Management
Chief Data Officer

IT Data Steward
Business Data
Business Data
Executive

Steward
Officer

Activities
sties

1 - Initiate metadata population exercise C I R I I

2 - Build a business glossary for the prioritized

data attributes
A I R I

3 – Review the business glossary R C I I

4 – Perform necessary updates A I R I

5 – Ingest Business Glossary to Data Catalog A I I R

6 – Review populated business metadata C R I I

7 – Perform necessary updates I A I R

R: Responsible – Person who does the task
A: Accountable – Person who delegates work and provides final review on a task or deliverable before it is
deemed complete
C: Consulted – Person who provides input on a task or deliverable based on the impact on their work or their
domain of expertise
I: Informed – Person who needs to be kept in the look on task or deliverable progress

Artifacts
Business Glossary template

Values
Busines Business Attribute Attribute Business Business Business Business
Attribute Attribute Nulls From Lookup / Attribute Create Read Update Delete
Attribute Sector Government s Sub- Logical Logical Sample Update Data Data Data Data
Description Description Applicabili Lookup / Reference Business Responsibili Responsibili Responsibili Responsibili Notes
ID Name Entity Domain Domain Name Name Values Frequency Executive Executive Steward Steward
(English) (Arabic) ty Referenc Table Name Rules ty ty ty ty
Name Name (English) (Arabic) Name Email Name Email
e Table

5. Annotate metadata
Overview
The Data Catalog automated tool enables data users to add tags, comments and ratings to metadata. The
annotation added to metadata shall be reviewed by Business Data Stewards and approved in the Data Catalog
automated tool in case of Business Data Steward’s annotation approval. Business Data Steward shall send a
notification to data user who added the annotation if the annotation was rejected.
NOTE: The Data Catalog tool can also propose annotations to metadata automatically (e.g. assignment of data
assets with business terms). Business Data Steward should verify and accept/reject these annotations as well.
The process is the same with an exception that no data consumer is notified.

Process
Activities
1 – Create an annotation – Data User
 Add a tag or comment to metadata to provide the Entity’s data users additional context on business
meaning and provide useful information on the data assets included in the Data Catalog

2 – Review the annotation – Business Data Steward

 Verify if the annotation created by a data user:
o provides accurate information on data assets
o is up to date
o is not spam
 Approve annotation if all requirements above are fulfilled
 Reject annotation and send notification to data user if any of requirements above is not fulfilled

3 – Accept the annotation – Business Data Steward

 Accept the annotation in the Data Catalog automated tool

4 – Receive a notification– Data User

 Receive information concerning created annotation

Governance

Roles
Data Management

IT Data Steward
Business Data

Business Data

Data User
Executive

Steward
Officer

Activities
sties

1 – Create a annotation R

2 – Review the annotation A R C

3 – Publish the annotation A R I

4 – Receive a notification I R

R: Responsible – Person who does the task

A: Accountable – Person who delegates work and provides final review on a task or deliverable before it is
deemed complete
C: Consulted – Person who provides input on a task or deliverable based on the impact on their work or their
domain of expertise
I: Informed – Person who needs to be kept in the look on task or deliverable progress
 6. Update Metadata
Overview
Metadata registered in the Data Catalog needs to be updated when issues concerning quality of metadata have
been identified. Process of metadata update is initiated by data user who reported identified metadata quality
issue.

Process

Activities
1 – Report an identified metadata quality issue – Data User
 Report metadata quality issues identified when using the Entity’s Data Catalog automated tool to Business
or IT Data Steward assigned to the metadata
 Specify for each identified metadata quality issue a rationale explaining why the metadata quality is low
including, but not limited to:
o Name of data source, data asset and data attribute concerned by the issue
 o Dimension/s of the metadata quality issue among:
- Completeness (degree to which business glossaries and data dictionaries are complete)
- Accuracy (degree to which definitions and descriptions align to business context)
- Consistency (degree to which definitions of Metadata are consistent across the Entity)

2 – Develop a remediation plan of the metadata quality issue – Business Data Steward/IT
Data Steward
 Develop a remediation plan of the reported metadata quality issue, including:
o Root cause analysis to determine the cause of the identified metadata quality issue
o Impact analysis to assess negative consequences and level (local, enterprise-wide) of the issue
o Definition of the options for resolving the issue's root cause, including a feasibility analysis of each
option to assess its pros and cons
o Recommended option for resolving the issue’s root cause
o Specification of manual correction of the low quality metadata in the Data Catalog automated tool if
the issue resolution does not correct quality errors in the tool

3 – Review the remediation plan of the metadata quality iss ue – Business Data Executive
 Review the developed remediation plan of the metadata quality issue including: root cause analysis, impact
analysis, definition of the options of resolving the issue’s root cause and specification of manual correction
of low quality metadata
 Select the resolution of the metadata quality issue’s root cause among options included in the remediation
plan
 If the remediation plan is approved, delegate Business and IT Data Stewards to implement the plan
 If the remediation plan is rejected send a feedback to Business and IT Data Stewards to enable them to
update the plan

4 – Implement the remediation plan of the metadata quality issue – Business Data
Steward/IT Data Steward
 Implement the resolution of the metadata quality issue’s root cause selected by Business Data Executive
amongst the options included in the remediation plan
 Collect documentation regarding the implemented remediation plan

5 – Review the implementation of the remediation plan – Data Management Officer

 Verify if the metadata quality resolution was implemented according to the developed remediation plan
 Verify if the reported metadata quality issue has been successfully resolved

6 – Receive a notification – Data User

 Receive information regarding correction of reported metadata quality issue
Governance

Roles

Data Management

IT Data Steward
Business Data

Business Data

Data User
Executive

Steward
Officer
Activities
sties

1 – Report an identified metadata quality issue R

2 – Develop a remediation plan of the metadata

quality issue
C A R R

3 – Review the remediation plan of the

metadata quality issue
R C I I

4 – Implement the remediation plan of the

metadata quality issue
C A R R

5 – Review the implementation of the

remediation plan C R I I

6 – Receive a notification R

R: Responsible – Person who does the task

A: Accountable – Person who delegates work and provides final review on a task or deliverable before it is
deemed complete
C: Consulted – Person who provides input on a task or deliverable based on the impact on their work or their
domain of expertise
I: Informed – Person who needs to be kept in the look on task or deliverable progress
 7. Request Data Quality support
Overview
Data quality support is the process used to report and track resolution the Entity’s data quality issues via the
Data Catalog tool. Process of data quality support is initiated by data user who report identified data quality issue
for given data asset.

Process

Activities
1 – Report identified data quality issue – Data User
 Report an identified data quality issue to Business and IT Data Stewards using the Entity’s Data Catalog
automated tool
 Specify for each identified quality issue a rationale explaining why the data quality is low including:
o Name of data source, data asset and data attribute concerned by the issue
o Affected dimension/s of the data quality issue among:
- Completeness (a degree to which data records are complete)
 - Uniqueness (a degree to which records are duplicates)
- Timeliness (how recent was the data collected)
- Validity (a degree of records' conformance to format, type and range)
- Accuracy (a degree to which data values align to real values)
- Consistency (a degree to which data is consistent across the Entity)

2 – Develop a remediation plan of the data quality issue – Business Data Steward/IT
Data Steward
 Develop a remediation plan of the reported data quality issue including:
o Root cause analysis to determine the cause of the identified Data Quality issue
o Impact analysis to assess negative consequences and level (local, enterprise-wide) of the issue
o Definition of the options for resolving the issue's root cause, including a feasibility analysis of each
option to assess its pros and cons
o Specification of data cleansing to be performed if a Data Quality issue resolution does not correct
data errors in the source system

3 – Review the remediation plan of the data quality issue – Business Data Executive
 Review the developed remediation plan of the data quality issue including: root cause analysis, impact
analysis, definition of the options of resolving the issue’s root cause and specification of data cleansing
 Select the resolution of the data quality issue’s root cause amongst options included in the remediation
plan
 If the remediation plan is approved, delegate Business and IT Data Stewards to implement the plan
 If the remediation plan is rejected send a feedback to Business and IT Data Stewards to enable them to
update the plan

4 – Implement the remediation plan of the data quality issue – Business Data Steward/IT
Data Steward
 Implement the resolution of the data quality issue’s root cause selected by Business Data Executive
amongst the options included in the remediation plan
 Collect documentation regarding the implemented remediation plan

5 – Review the implementation of the remediation plan – Data Management Officer

 Verify if the data quality resolution was implemented according to the developed remediation plan
 Verify if the reported data quality issue has been successfully resolved

6 – Receive a notification – Data User

 Receive information concerning reported data quality issue
 Get to know when the data quality issue is resolved
Governance

Roles

Data Management

IT Data Steward
Business Data

Business Data

Data User
Executive

Steward
Officer
Activities
sties

1 – Report an identified data quality issue R

2 – Develop a remediation plan of the data

quality issue
C A R R

3 – Review the remediation plan of the data

quality issue
R C I I

4 – Implement the remediation plan of the data

quality issue
C A R R

5 – Review the implementation of the

remediation plan
C R I I

6 – Receive a notification R

R: Responsible – Person who does the task

A: Accountable – Person who delegates work and provides final review on a task or deliverable before it is
deemed complete
C: Consulted – Person who provides input on a task or deliverable based on the impact on their work or their
domain of expertise
I: Informed – Person who needs to be kept in the look on task or deliverable progress
 8. Publish metadata to the National Data Catalog
Overview
Process of publishing of the Entity’s metadata to the National Data Catalog is conducted to enable the insight
into government data on the national level and enhance data sharing across government.
The process of publishing of metadata to the National Data Catalog is initiated by Data Management Officer who
assigns responsibilities to the relevant roles. Business Data Steward identifies metadata to be published to the
National Data Catalog which is then reviewed in turn by Business Data Executive, Chief Data Officer and NDMO
If metadata to be published is approved by NDMO, IT Business Data Steward publishes metadata to the National
Data Catalog by using Data Catalog automated tool.

Process
Activities
1 – Initiate metadata publishing exercise – Data Management Officer
 Inform Data Management and Privacy Team in the entity that the process of publishing of metadata to the
National Data Catalog has started.
 Meet with Chief Data Officer, Business Data Executive, Business Data Steward and IT Data Steward to
assign them responsibilities related to publishing of the Entity’s metadata to the National Data Catalog

2 – Identify metadata to be published – Business Data Steward

 Review metadata available in the Entity’s Data Catalog and identify data assets for which metadata should
be published to the National Data Catalog based on:
o Classification of data
o Potential threats of disclosure of metadata to individuals, organizations, the environment or the
nation
o Potential national and social benefits of publishing the metadata
o Data and metadata quality which influences data value and usability
 Tag all the data assets identified to be published to the National Data Catalog in the Entity’s Data Catalog
automated tool. Tagging of the metadata enables Business Data Executives and CDO to review the
identified metadata

3 – Review the metadata identified to be published – Business Data Executive

 Review the metadata identified by Business Data Steward to be published to the National Data Catalog
based on:
o Classification of data
o Potential threats of disclosure of metadata to individuals, organizations, the environment or the
nation
o Potential national and social benefits of publishing the metadata
o Data and metadata quality which influences data value and usability
 Identify metadata tagged by Business Data Steward that should not be published to the National Data
Catalog and remove the tags for them
 Verify if any of metadata that was not tagged by Business Data Steward should be published to the
National Data Catalog and tag the metadata
 If major changes are required report it to Data Management Officer

4 – Delegate relevant Business Data Steward – Data Management Officer

 Receive an issue detected during review of metadata to be published to the National Data Catalog
 Delegate relevant Business Data Steward to perform updates

5 – Perform necessary updates – Business Data Steward

 Perform necessary updates by tagging or removing the tags for the metadata
 Once the update is done inform Data Business Executive

6 – Review metadata accepted by Business Data Executive – Chief Data Officer (CDO)
 Review the metadata identified by Business Data Steward to be published to the National Data Catalog
based on:
o Classification of data
 o Potential threats of disclosure of metadata to individuals, organizations, the environment or the
nation
o Potential national and social benefits of publishing the metadata
o Data and metadata quality which influences data value and usability
 If major changes are required report it to Data Management Officer

7 – Review the Entity’s metadata to be published –NDMO

 Review the Entity’s metadata to be published to the National Data Catalog based on:
o Classification of data
o Potential threats of disclosure of metadata to individuals, organizations, the environment or the
nation
o Potential national and social benefits of publishing the metadata
o Data and metadata quality which influences data value and usability
 If any changes are required report it to the Entity’s Data Management Officer

8 – Publish metadata to the National Data Catalog – IT Data Steward

 If metadata identified to be published are accepted by Business Data Executive, Chief Data Officer and
NDMO publish them to the National Data Catalog

Governance

Roles

Data Management
Chief Data Officer

IT Data Steward
Business Data

Business Data
Executive

Steward
NDMO

Officer
(CDO)

Activities
sties

1 – Initiate metadata publishing exercise I A I R I I

2 – Identify metadata to be published I C I R

3 – Review the metadata identified to be

published
I R I C

4 – Delegate relevant Business Data Steward I R

5 – Perform necessary updates I I R

6 – Review metadata accepted by Business

Data Executive R I I I

7 - Review the Entity’s metadata to be published R I I I I I

8 - Publish metadata to the National Data

Catalog
I I I I I R
R: Responsible – Person who does the task
A: Accountable – Person who delegates work and provides final review on a task or deliverable before it is
deemed complete
C: Consulted – Person who provides input on a task or deliverable based on the impact on their work or their
domain of expertise
I: Informed – Person who needs to be kept in the look on task or deliverable progress