• Embed Doc
  • Readcast
  • Collections
  • CommentGo Back
Download
 
Leader in Data Qualityand Data Integration
www.datafux.com
 877–846–FLUXInternational+44 (0) 1753 272 020
A DataFlux White Paper
Prepared by:
David Loshin
Data Quality Remediation
 
 
1
Introduction
The policies and procedures of data governance are valuable within the organizationbecause they ensure that the quality of enterprise data is maintained at the levels tosupport successful business activities. The operational procedures are often spelled outwithin a
data quality service level agreement 
(DQ SLA), which is an agreement betweendata providers and data consumers about the expected performance levels for dataquality. The DQ SLA details the business data quality requirements along all theprocessing stages in a business process flow, and assertions that can be used to validatethe data.However, when errors in the data are identified, the data stewards responsible for thedata must take action. This paper reviews the pieces of that immediate action plan: thetriage and analysis tasks performed by data quality analysts or data stewards when anissue is identified and logged in the data quality incident tracking system. This includes:
 
Evaluating and assessing the issue and determining the scope and extent of theproblem from both a business impact perspective and from an operationalperspective
 
Reviewing the information process map to determine the likely locations for thesource of introduction of the problem
 
Determining strategies for correcting the problem
 
Researching strategies for eliminating its root cause
 
Planning and applying operational aspects, including data correction, monitoring,and preventionEvaluating criticality, assessing the frequency and severity of discovered issues, andprioritizing tasks for remediation are all part of the data steward’s role. Formalizing thedifferent tasks to perform when issues of different levels of criticality occur will reducethe effort for remediation while speeding the time to resolution.
The Data Quality Service Level Agreement
An emerging trend in the data quality arena is the concept of a DQ SLA, which provides avaluable link between the IT and business sides throughout a data quality or datagovernance effort. A DQ SLA is a contract between a data provider and a data consumerthat specifies the data provider’s responsibilities with respect to different measurableaspects of what is being provided, such as availability, performance, response time forproblems, as well as reasonable expectations for response and remediation when dataerrors and flaws are identified.
 
 
2
What Composes the DQ SLA?
Within any business process, the DQ SLA lists the expectations regarding measurableaspects relating to one or more dimensions of data quality (such as accuracy,completeness, consistency, timeliness, etc.), along with the specifications regardingconformance to those expectations. The DQ SLA also describes the processes to beinitiated when those expectations are not met, especially those related to evaluating theissue, diagnosing its cause, and determining how to solve the problem.Using a DQ SLA is valuable because it formalizes the processes that are put into place formanaging the way that the organization deals with emerging data issues. Theseagreements also suggest ways to track the data issue resolution progress as a way ofinternalizing lessons learned. If it is determined that data instances do not meet thedefined expectations, a data quality incident event is generated, and the appropriate staffmembers are notified to diagnose and mitigate the issues.
DQ SLAs and Data Issue Severity
One aspect of using a DQ SLA is the fact that the data quality expectations are defined inthe context of business impacts, and this can provide guidance to the data steward whendata issues are reported. Acceptability levels for measured data quality rules can bebased on the corresponding financial impacts and the organization’s degree of toleranceto the errors causing those impacts. Acceptability thresholds become the barometer bywhich severity of issues is measured, and the process of determining those thresholdsalso contributes the basis for determining severity during issue evaluation andassessment.
Triage: Evaluation and Assessment of the Data Quality Issue
There will always be a backlog of issues for review and consideration, created as abyproduct of weighing feasibility and cost effectiveness of a solution against therecognized business impact of the issue. When a data issue has been identified, theevaluation process will take into account these aspects of the identified issue:
 
Criticality
– the degree to which the business processes are impaired by theexistence of the issue
 
Frequency
how often the issue has appeared
 
Feasibility
 
of correction
the likelihood of expending the effort to correct theresults of the failure
 
Feasibility
 
of prevention
the likelihood of expending the effort to eliminate theroot cause or institute continuous monitoring to detect the issuesThe triage process is performed to understand these aspects in terms of the businessimpact, the size of the problem, as well as the number of individuals or systems affected.Triage enables the data steward to review the general characteristics of the problem andbusiness impacts in preparation for assigning a level of severity and priority.
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...