Data Quality Management

Revision as of 20:27, 3 March 2018

Abstract

Data quality has a significant impact on both the efficiency and effectiveness of organisations^[1]. As part of the digital transformation, data has become more readily available and more important than ever before. Project teams are performing data analytics to leverage key resources and optimise processes to gain insight and make informed decisions. As such, data is becoming increasingly valuable to project managers who are driving decision making based on high-quality data insight. However, if data quality is poor, project managers risk taking misguided decisions based on unreliable data. DQM can be utilised as a tool to ensure communication and decisions are being driven based on high-quality data.

Data quality management (DQM) serves the objective of continuously improving the quality of data relevant to a project or program^[2]. It is important to understand that the end goal of DQM is not about simply improving data quality in the interest of having high-quality data, but rather to achieve desired outcomes that rely on high-quality data^[3]. DQM revolves around the management of people, processes, technology and data through coordinated activities aimed at improving data quality^[4]. The article explores DQM as a tool that can be applied by project managers, the article delves deeper into the meaning behind the term data quality and investigates the process for DQM as reflected by the ISO 8000-61 framework.

Overview

Importance of DQM in PMBOK®

One can argue that data quality has the ability to impact stakeholders involved in each knowledge area of project management. For example, a supply chain planner may expect a given material to be received based on data for a vendor lead time, however if the data quality is highly inaccurate, then the supply chain planner may be misguided in terms of project time management through inaccurate schedule development and planning. Similarly, a project cost controller overseeing a construction project may provide inaccurate input for project cost management if the data quality for different cost parameters is inaccurate. Likewise, a risk consultant using master data for risk quantification may provide managers with an inaccurate risk assessment which could detrimentally influence a project through poor project risk management due to low-quality data. As data is used everywhere and within each area of project management, data quality can have an enormous influence on project execution and outcomes.

However, some areas of project management are more reliant on high quality data than other areas to successfully function. Data is defined as "reinterpretable representation of information in a formalised manner suitable for communication, interpretation, or processing" (ISO 8000-2)^[5] while quality is defined as "the degree to which a set of inherent characteristics fulfil requirements" (ISO 9000)^[6]. The key words in these definitions being: information, communication, degree and requirements. Based on these definitions and for the sake of clarity, the importance of data quality within project communications management and project quality management of the PMBOK® is discussed.

According to the PMBOK® guidelines, project communications management refers to the processes that are necessary for the timely planning, creation, collection, distribution, control, monitoring, and disposition of project information^[7]. Various project information is stored and handled as data and therefore if data quality is not high, project communication may also falter. Data influences communication activities on many dimensions between various stakeholders, these include^[8]:

• Internally: data within project
• Externally: data between project stakeholders, vendors, customers, contractors, etc.
• Vertically: data communication vertically in terms of hierarchy within organisation
• Horizontally: data communication between project members
• Officially: data used within newsletters, annual reports, audits, etc.
• Unofficially: data used when communicating off the record

Data Quality

An important element of DQM is understanding the dimensions and complexity of the term data quality. As per ISO 8000-2 guidelines, data quality is defined as the "degree to which a set of inherent characteristics of data fulfils requirements"^[9]. However, data quality is a multifaceted concept which considers various dimensions^[10] and it can therefore be difficult to define in one sentence, let alone measure. Data quality dimensions in literature consider accuracy, completeness, consistency, integrity, representation, timeliness, uniqueness and validity. The ISO 8000-8 guidelines divide data quality into three categories based on semiotic theory. Semiotic theory concerns the usage of symbols such as letters and numbers to communicate information^[11]. The three semiotic categories that are relevant in regard to discussing data quality are; syntactic quality, semantic quality, and pragmatic quality^[12]. As illustrated in figure 2.A, these categories provide a base for measuring data quality and are important terms to recognize for understanding DQM.

Syntactic Data Quality

Figure 2.A: Overall data quality, inspired from Moody, et al. n.d, Evaluating the quality of process models: empirical analysis of a quality framework

Figure 2.B: Semiotic categories for data quality, inspired from Shanks, G and Darke, P. 1998, Understanding data quality in a data warehouse: a semiotic approach

The goal of syntactic data quality is consistency. Consistency concerns the use of consistent syntax and symbolic representation for particular data. Syntactic quality can be measured based on percentage of inconsistencies in data values. Consistency is often developed through a set of rules concerning syntax for data input^[13].

Semantic Data Quality

The goal of semantic data quality is accuracy and comprehensiveness. Accuracy can be defined as the degree of conformity a data element holds compared to the truth of the real world. Comprehensiveness can be understood as the extent to which relevant states in the real world system are represented in a data warehouse^[14]. Properties that fall under semantic quality are completeness, unambiguity, meaningfulness and correctness^[15].

Pragmatic Data Quality

The goal of pragmatic data quality concerns usability and usefulness. Usability refers to how easy it is for a stakeholder to be able to effectively interact and access the data while usefulness refers to the ability of the data to support a stakeholder in accomplishing tasks and aid decision-making. Data may be more useful/usable for some stakeholders than others, depending on their ability to interpret the data and the context of their tasks. Pragmatic data quality involves the properties of timeliness, conciseness, accessibility, reputability and understood^[16].

Figure 2.B highlights the various categories addressed above and summarises each quality category goal, properties and example methods for measuring empirically. There are various empirical models that build on the semiotic theory for categorizing data quality, some of which use different regression and weighting models to empirically measure data quality. These can be studied further in Moody, et al's paper: Evaluating the quality of process models: empirical analysis of a quality framework.

Fundamental Principles of DQM

Figure 3.A: Functions of a data governance program, inspired from Knowledgent: Building a successful DQM program

It is important to recognize that DQM often functions as one of many building blocks of a larger data governance project or program^[17]. Figure 3.A highlights the various tools and building blocks which make up a data governance project/program, these include; DQM, data architecture, metadata management, master data management, data distribution, data security, and information lifecycle management. Therefore, DQM does not touch upon these other building blocks of data governance, however, there is often a strong interplay between the different functions. The ISO 8000-61 guidelines define the three fundamentals of a DQM as: process approach, continuous improvement, and involvement of people. The three fundamental principles of DQM act as pillars in building and managing a program for the assurance of high-quality data.

ISO 8000-61 Principles of DQM

Process Approach

Figure 3.B: The fundamental principles of DQM, inspired from ISO 8000-61

The first fundamental principle is the process approach, this principle concerns defining and operating the processes that use, create and update relevant data^[18]. This principle states that a successful DQM program requires a process approach to managing key process activities. The process approach involves defining and operating recurring and reliable processes to support DQM.

Continuous Improvement

The principle of continuous improvement forms the second fundamental, this principle establishes the idea that data most be constantly improved through effective measurement, remediation and corrective action of data nonconformities. As stated by the ISO 8000-61 guidelines, continuous improvement depends on "analysing, tracing and removing the root causes of poor data quality" which may require adjustments to faulty processes^[19]. This fundamental is closely linked to the concept of Kaizen.

Involvement of People

The third fundamental principle highlights the importance of people to DQM. This principle states that different responsibilities are allocated to individuals at different levels within a program or organisation. Top level management provide necessary and sufficient resources and direct the program towards achieving specific goals in regard to data quality. Data specialist perform activities such as implementation of processes, intervention, control and the embedding of future processes for continuous improvement. While end users perform direct data processing activities such as input of data and analysis. End users typically have the greatest direct influence on actual data quality as these are also the individuals in closest contact to the data itself^[20].

ISO 8000-61 Framework for the DQM Process

The Basic Structure of the DQM Process

Figure 4.A: Basic DQM structure, inspired from ISO 8000-61

The basic structure of the DQM process is illustrated in figure 4.A. The structure is illustrated by three overarching and interlinked processes; implementation, data-related support, and resource provision.^[21].

• Implementation Process: this stage is aimed at achieving continual improvement of data quality using a systematic and cyclic plan-do-check-act process. The cycle involves planning (plan), control (do), assurance (control), and improvement (act).

• Data-Related Support: this stage enables the implementation process by providing information and technology related to data management. As the figure 4.A highlights, it provides an input to the implementation stage.

• Resource Provision: this stage involves training of individuals performing data related tasks and providing sufficient resources to effectively and efficiently manage the implementation and data-related support processes.

The Plan-Do-Check-Act (PDCA) cycle of the implementation stage is a process promoting more effective and efficient data quality through continuous improvement. The PDCA cycle can be briefly described as follows:^[22].

• Plan: developing strategic plans of action for implementation and delivery of results in regard to data quality requirements. Plan to enhance quality.
• Do: implement and conduct plan for data quality control.
• Check: monitor, measure and compare results against data requirements. Conduct performance reporting.
• Act: remediate for continuous improvement of process. Also concerns preventing and reducing undesired effects monitored in the check stage.

The Detailed Structure of the DQM Process

Figure 4.B: Detailed DQM structure, inspired from ISO 8000-61

Figure 4.B reveals the lower levels of the DQM process. These are explained accordingly: EXPLAIN CONCEPTS OF DETAILED STRUCTURE

Implementation

Data-Related Support

Resource Provision

Benefits and Difficulties of DQM

Glossary

• DQM: Data Quality Management
• ISO: International Organisation for Standardization
• PDCA: Plan-Do-Check-Act
• PMBOK: Project Management Body of Knowledge

Bibliography

Batini, C. and Scannapieco, M. (2006): Data Quality: Concepts, Methodologies and Techniques. Berlin: Springer. This book explores various concepts, methodologies and techniques involving data quality processes. It provides a solid introduction to the topic of data quality.

ISO 8000-2. (2017): Data Quality - Part 2: Vocabulary. International Organisation for Standardisation. Ref: ISO 8000-2:2017(E). This is the ISO standard for data quality vocabulary. It provides clear and authoritative definitions of data quality terms.

ISO 8000-61. (2016): Data Quality - Part 61: Data Quality Management: Process Reference Model. International Organisation for Standardisation. Ref: ISO 8000-61:2016(E). This is the ISO standard for data quality management processes. It provides an excellent and concise overview of the industry best practices regarding DQM processes, explaining the fundamental principles behind DQM and elaborating on process procedures through a framework guide.

ISO 8000-8. (2015): Data Quality - Part 8: Information and Data Quality: Concepts and Measuring. International Organisation for Standardisation. Ref: ISO 8000-2:2017(E). This is the ISO standard data quality concepts and measuring theory. It introduces the semiotic theories for data quality.

Knowledgent. (2014): Building a Successful DQM Program. Knowledgent White Paper Series. This paper provides an introduction to DQM within enterprise information management, explaining the basic concepts behind DQM and also explaining the data quality cycle framework.

PMI. (2013): A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 5th ed. Pennsylvania USA. The PMBOK® guide provides a wealth of knowledge regarding the different knowledge bodies of project management. In this article, the guide was particularly useful in identifying and understanding how data quality may influence different project management areas. This article primarily referenced chapter 8 and 10 of the PMBOK®, communications and quality management respectively.

Shanks, G. and Darke, P. (1998): Understanding Data Quality in a Data Warehouse: A Semiotic Approach. Massachusetts USA: University of Massachusetts Lowell, pg. 292-309. This paper provided an overview of data quality measures using a semiotic approach, explaining each semiotic level and how they are interlinked to data quality. The semiotic theory discussed is similar to the one later adopted by the ISO 8000-8 standard for data quality.

References

1. ↑ Pg. 2, 2006 ed. Data Quality: Concepts, methodologies and Techniques, Carlo Batini & Monica Scannapieca
2. ↑ Pg. 3, 2014 ed. Building a Successful Data Quality Management Program, Knowledgent
3. ↑ Pg. 3, 2014 ed. Building a Successful Data Quality Management Program, Knowledgent
4. ↑ 2017 ed. ISO 8000-2: Data Quality - Part 2: Vocabulary, ISO
5. ↑ 2017 ed. ISO 8000-2: Data Quality - Part 2: Vocabulary, ISO
6. ↑ Chapter 8. 2013 ed. A Guide to Project Management Body of Knowledge (PMBOK®): Project Communications Management. ed 5. PMI
7. ↑ Chapter 10. 2013 ed. A Guide to Project Management Body of Knowledge (PMBOK®): Project Communications Management. ed 5. PMI
8. ↑ Chapter 10. 2013 ed. A Guide to Project Management Body of Knowledge (PMBOK®): Project Communications Management. ed 5. PMI
9. ↑ 2017 ed. ISO 8000-2: Data Quality - Part 2: Vocabulary, ISO
10. ↑ Pg. 6, 2006 ed. Data Quality: Concepts, methodologies and Techniques, Carlo Batini & Monica Scannapieca
11. ↑ Pg. 298, 1998. Understanding Data Quality in a Data Warehouse: A Semiotic Approach, Shanks, G and Darke, P.
12. ↑ 2015 ed. ISO 8000-8: Data Quality - Part 8: Information and data quality: Concepts and measuring, ISO
13. ↑ Pg. 303, 1998. Understanding Data Quality in a Data Warehouse: A Semiotic Approach, Shanks, G and Darke, P.
14. ↑ Pg. 301, 1998. Understanding Data Quality in a Data Warehouse: A Semiotic Approach, Shanks, G and Darke, P.
15. ↑ Pg. 303, 1998. Understanding Data Quality in a Data Warehouse: A Semiotic Approach, Shanks, G and Darke, P.
16. ↑ Pg. 302, 1998. Understanding Data Quality in a Data Warehouse: A Semiotic Approach, Shanks, G and Darke, P.
17. ↑ Pg. 3, 2014 ed. Building a Successful Data Quality Management Program, Knowledgent
18. ↑ Pg. 2, 2015 ed. ISO 8000-61: Data quality management: Process reference model, ISO
19. ↑ Pg. 2, 2015 ed. ISO 8000-61: Data quality management: Process reference model, ISO
20. ↑ Pg. 2, 2015 ed. ISO 8000-61: Data quality management: Process reference model, ISO
21. ↑ Pg. 2, 2015 ed. ISO 8000-61: Data quality management: Process reference model, ISO
22. ↑ Pg. 3, 2015 ed. ISO 8000-61: Data quality management: Process reference model, ISO