Study guide
4.5 DQ Metrics, Tools, and Reporting
DAMA Certified Data Management Professional CDMP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & DMBoK Framework
1.1 CDMP Exam Details & Strategy 1.2 The DMBoK Framework 1.3 Data Management Organization & Roles
2 Chapter 2: Data Governance (Part A)
2.1 Data Governance Principles & Drivers 2.2 Operating Models & Structures 2.3 Policies, Standards, and Procedures
3 Chapter 2: Data Governance (Part B)
2.4 Data Stewardship 2.5 Governance Metrics & Implementation
4 Chapter 3: Data Modeling and Design (Part A)
Section 3.1: Conceptual, Logical, and Physical Models Section 3.2: ERD Notations & Relational Modeling Section 3.3: Normalization
5 Chapter 3: Data Modeling and Design (Part B)
3.4 Dimensional Modeling 3.5 Naming Standards & Modeling Best Practices
6 Chapter 4: Data Quality (Part A)
Section 4.1: Data Quality Dimensions Section 4.2: Data Quality Policy & Rules Section 4.3: DMAIC & DQ Improvement Lifecycle
7 Chapter 4: Data Quality (Part B)
4.4 Root-Cause Analysis & Remediation 4.5 DQ Metrics, Tools, and Reporting
8 Chapter 5: Metadata Management (Part A)
5.1 Business, Technical, and Operational Metadata 5.2 Metadata Lineage & Impact Analysis 5.3 Repository Architectures
9 Chapter 5: Metadata Management (Part B)
5.4 Standards and Semantics 5.5 Metadata Governance & Integration
10 Chapter 6: Master and Reference Data Management
6.1 Master vs Reference Data 6.2 MDM Repository Architectures 6.3 Match-Merge & Identity Resolution 6.4 Reference Data Governance & Standards
11 Chapter 7: Data Warehousing and Business Intelligence
7.1 DW Architectures: Inmon vs Kimball 7.2 Data Warehousing Storage & Load Patterns 7.3 BI Delivery & OLAP 7.4 Data Marts & Enterprise Data Warehouses
12 Chapter 8: Data Architecture
8.1 Enterprise Data Architecture & Zachman Framework 8.2 Data Flow Diagrams & Value Chains 8.3 Architecture Frameworks & Standards
13 Chapter 9: Document and Content Management
9.1 Records Management & ECM 9.2 Retention, Disposal, and E-Discovery 9.3 ARMA GARP Principles & Taxonomies
14 Chapter 10: Data Integration and Interoperability
Section 10.1: Integration Patterns & Technologies Section 10.2: Replication & Virtualization Section 10.3: Canonical Models & Integration Standards
15 Chapter 11: Data Security
Section 11.1: Security Principles: CIA Triad & Privacy Section 11.2: Access Control & Encryption Section 11.3: Security Regulations & Standards
16 Chapter 12: Data Storage and Operations
Section 12.1: Database Technologies & DBA Roles Section 12.2: Backup, Recovery, and High Availability Section 12.3: Performance Tuning & Operations
17 Chapter 13: Big Data and Data Science
13.1 Big Data V's & Technologies
18 Chapter 14: Data Ethics
14.1 DMBoK Data Ethics Framework
19 Chapter 15: Data Management Process and Maturity
15.1 Maturity Assessment Frameworks
4.5 DQ Metrics, Tools, and Reporting
Key Takeaways Explain This Topic AI
Data quality scorecards provide strategic, high-level business compliance tracking, whereas dashboards deliver operational, real-time alerts.
Statistical Process Control (SPC) uses statistical boundaries (control limits at +/- 3 standard deviations) to monitor data flow stability.
Data profiling tools automate the inspection of data structures, distributions, patterns, and relationship dependencies.
Data cleansing processes standardization, parsing, enrichment, deduplication, and verification, but must be accompanied by source-level remediation.
Last updated: July 2026
Defining Data Quality Metrics
To effectively manage data quality, an organization must define and measure quantitative metrics. Data Quality (DQ) Metrics translate abstract quality dimensions into measurable performance indicators. Defining these metrics requires establishing clear mathematical formulas, measurement points in the data flow, and target thresholds.
Metrics are prioritized for Critical Data Elements (CDEs) —data fields most vital to business operations, regulatory reporting, or decision-making.
Common DQ metric formulations include:
Completeness : Completeness Rate = (Count of Records with Non-Null CDE / Total Count of Ingested Records) * 100
Validity : Validity Rate = (Count of Records Conforming to Domain Rules / Total Count of Records) * 100
Timeliness : Timeliness Latency = Data Available Timestamp - Business Event Occurrence Timestamp (measured in minutes, hours, or days against a Service Level Agreement (SLA)).
Metrics must have defined thresholds :
Target (Green) : The ideal state representing high data quality (e.g., >= 99.5%).
Warning (Yellow) : A marginal level indicating emerging quality issues that require investigation (e.g., 95.0% - 99.4%).
Critical (Red) : Unacceptable quality levels that trigger automated alerts and incident management workflows (e.g., < 95.0%).
Data Quality Scorecards vs. Dashboards
Reporting data quality requires tailoring the delivery format to the target audience. The two primary reporting mechanisms are Data Quality Scorecards and Data Quality Dashboards .
Data Quality Scorecards
A scorecard is a strategic, high-level reporting tool designed for business leaders, executive sponsors, and the Data Governance Steering Committee. It focuses on long-term trends and compliance against organizational SLAs.
Key Traits : Monthly or quarterly release cycle; aggregated scores mapped to business units or critical data domains; and visual red/yellow/green indicators showing alignment with business goals.
Objective : Demonstrate the business value of data quality initiatives and hold data owners accountable for their domains.
Data Quality Dashboards
A dashboard is an operational, tactical monitoring tool designed for Data Stewards , data engineers, and system administrators. It provides a real-time or near-real-time view of data quality as data flows through system pipelines.
Key Traits : High-frequency updates (hourly or daily); granular visualization of technical errors, null rates, data volume spikes, and pipeline latency; interactive filtering options.
Objective : Enable rapid troubleshooting and operational incident response to prevent bad data from propagating downstream.
- Attribute Data Quality Scorecard Data Quality Dashboard
- Primary Audience Executives, Data Governance Board, business owners Data Stewards, Data Engineers, DBAs
- Update Frequency Monthly or Quarterly Real-time, Daily, or Batch Run Cycle
Level of Detail Aggregated, high-level (business units, domains) Detailed, granular (tables, columns, system pipelines)
- Focus SLA compliance, trend analysis, maturity tracking Active alerts, defect counts, pipeline run status
- Statistical Process Control (SPC) for Data Quality
Statistical Process Control (SPC) is the application of statistical methods to monitor and control a process. Originating in manufacturing under Walter Shewhart and W. Edwards Deming, SPC is applied in data management to monitor data pipelines and quality metrics. It helps distinguish between normal, inherent system variation and genuine data anomalies.
Control Limits vs. Specification Limits
A common exam trap is confusing control limits with specification limits:
Specification Limits : Predefined thresholds set by the business or regulatory requirements (e.g., "Customer phone number must contain 10 digits"). These are external requirements.
Control Limits : Statistically calculated boundaries derived from historical process performance, typically set at three standard deviations (+/- 3-sigma) from the historical mean. These represent what the process is actually capable of producing under normal conditions.
Upper Control Limit (UCL) : The maximum value expected under normal variations (Mean + 3*sigma).
Lower Control Limit (LCL) : The minimum value expected under normal variations (Mean - 3*sigma).
Control Chart Interpretation
A Control Chart plots data quality measurements chronologically.
Common Cause Variation : Normal, random fluctuations within the control limits (e.g., small daily variances in transaction volumes). No action is taken.
Special Cause Variation : Non-random patterns or data points falling outside the control limits (e.g., a massive spike in null values, or daily record volumes dropping below the LCL). This indicates that the data pipeline is "out of control" due to a system or upstream change, triggering immediate investigation.
Data Profiling Tools
Data Profiling is the automated analysis of data to understand its structure, content, and quality characteristics. Profiling tools scan physical databases to extract metadata and identify anomalies. Key capabilities include:
Column Analysis : Examining individual columns to determine data types, frequency distributions, value ranges, cardinality, and null counts.
Pattern and Format Extraction : Identifying character patterns within fields (e.g., verifying if all values in an SSN field conform to the pattern 999-99-9999 ).
Dependency Analysis : Discovering functional dependencies between columns within a table (e.g., verifying if the Postal Code uniquely determines the City and State).
Cross-Table / Referential Integrity Analysis : Examining foreign key relationships to verify if child tables contain orphaned records that do not link to parent tables.
Data Cleansing Techniques
Data Cleansing (or Data Scrubbing ) is the process of altering data to bring it into compliance with business rules and standards. Cleansing is a necessary reactive step to prepare data for operational use or analytics, but it must be paired with root-cause remediation to prevent errors from recurring.
Common operations in data cleansing include:
Standardization : Converting data to a consistent canonical representation. Example: converting variations of state names ("California", "Calif.", "ca") to the postal standard "CA".
Parsing : Splitting unified data fields into distinct logical elements. Example: parsing "123 Main St Apt 4B" into Street Number (123), Street Name (Main), Street Type (ST), and Unit (APT 4B).
Enrichment : Appending third-party or reference data to enhance value. Example: validating mailing addresses and appending geospatial coordinates (latitude/longitude) or postal barcodes.
Deduplication (Matching & Merging) : Identifying duplicate records using deterministic rules (exact match) or probabilistic rules (fuzzy matching scores) and merging them into a single, master golden record.
Verification : Validating data against authoritative internal or external registries (e.g., checking credit card numbers against bank networks or emails via SMTP pinging).