This factsheet describes knowledge about Data Issues in a nutshell. Data Issues are highlighted in this factsheet from different angles in a structured way.
A Data Issue is a non-fulfilment of a requirement regarding data quality.
A Correction is an action to eliminate a Data Issue. A Corrective Action is an action to eliminate the cause of a Data Issue. A Preventive Action is an action to the eliminate the cause of a potential Data Issue.
Note: Generally, a data issue concerns an incorrect data value, but it can be applied to any other data quality dimensions, e.g., completeness and timeliness.
|Plan|| * To detect or identify Data Issues
* To determine if similar Data Issues exist
* To register Data Issues
* To count the number of Data Issues
* To categorize or classify Data Issues
* To diagnose Data Issues (‘root cause analysis’)
* To formulate options for remediation of Data Issues.
* To assess the business impact of Data Issues (‘severity’)
* To prioritize Data Issues based on business impact (by data owners and data stewards)
* To eventually escalate Data Issues. See figure.
|Do|| * To eliminate or resolve a Data Issue (‘correction’, ‘remediation’, ‘scrubbing’ or ‘cleansing’)
* To eliminate the cause of a Data Issue to prevent recurring (‘corrective action’)
* To eliminate the cause of a potential Data Issue (‘preventive action’)
* To deal with the consequences of the Data Issue, e.g., to report Data Issues to data consumers
* To document actions taken.
|Check|| * To monitor the status of Data Issues and their resolutions.
* To review the effectiveness of corrective and preventive action.
|Act||* To adapt corrective and preventive action.|
|Severity||Data Issues are resolved in order of severity.|
Attributes of a Data Issue are:
The figure shows a possible escalation path of data issues. Figure 2: Data Issue escalation path.
A customer of the TradeAll trade company complained that he had been delivered an incorrect item. The sales department reported this incident in the Incident Tracking System, which was assigned to the Data Steward. The Data Steward then went to see how this could have happened. He found that the item number did not match the item description and suspected that this was due to a data entry error. Based on the item number, the products were taken from the warehouse.
He corrected the item number (Correction), but to prevent this kind of error, he took the measure that the entry of items was checked by a second person to prevent more incidents (Corrective Action). He also made sure to check for duplicate item numbers in the database (Corrective Action).. The customer was apologised for the error and the correct article was delivered as soon as possible.
DAMA (2017). DAMA-DMBOK. Data Management Body of Knowledge. 2nd Edition. Technics Publications Llc. August 2017. Chapter 13 Data Quality, section 2.7.3 Develop Operational Procedures for Managing Data Issues.
DAMA Dictionary of Data Management. 2nd Edition 2011. Technics Publications, LLC, New Jersey.
ISO 9000:2015. Quality Management Systems – Requirements.
ISO 9001:2015. Quality Management Systems – Fundamentals and vocabulary.