< All Topics
Print

Master Data Quality Dimensions

Master Data Quality Dimensions: Data Quality Dimensions are not just frameworks—they are the heartbeat of enterprise decision-making. According to Gartner, poor data quality costs organizations an average of $12.9 million annually, while IBM reports that bad data affects over 30% of business revenues. Despite these facts, only 16% of organizations have a mature data quality program in place.

This article breaks down the five critical dimensions of data quality, explains how they’re implemented, and demonstrates how ServiceNow and Data Trust tools can elevate your organization’s data maturity through metadata-driven rules and conditional logic.


🧠 Why It Matters

  • Decision-making depends on data accuracy
  • AI models rely on consistent and clean data
  • Regulations like GDPR and HIPAA demand traceability and data lineage
  • Enterprise automation fails without timely and complete data

Now, let’s examine each dimension in depth and how they’re put into action.


✅ Five Dimensions of Data Quality

DimensionDescriptionKey Components
AccuracyReflects the real-world truthReference validation, correct values, business rule checks
CompletenessMeasures how much data is presentRequired fields, fill rates, null checks
ConsistencyUniformity across systemsReferential integrity, business logic alignment
TimelinessData’s freshness and update recencyTimestamps, sync intervals, latency
UniquenessEnsures no duplicates existKey constraints, match rules, deduplication

🧱 Constructing the Dimensions

Each dimension is powered by:

  • Rules & Thresholds (e.g., Accuracy ≥ 95%)
  • Query Logic (SQL or GlideRecord)
  • Metadata Profiles (column type, requirement level)
  • Ownership Models (defined stewards and systems of record)

These pieces ensure not only quality measurement—but also actionability.


🔍 Building the Queries: Conditions, Checks, Subselects

Standard SQL Subselect Pattern:

sqlCopyEditSELECT col1, col2
FROM table
WHERE condition
AND NOT EXISTS (
  SELECT 1 FROM other_table WHERE table.id = other_table.ref_id
)

Example: Null Value Check for Completeness

sqlCopyEditSELECT employee_id, last_name
FROM hr_profile
WHERE last_name IS NULL;

GlideRecord in ServiceNow:

javascriptCopyEditvar gr = new GlideRecord('cmdb_ci');
gr.addNullQuery('serial_number');
gr.query();
while (gr.next()) {
  gs.info(gr.name);
}

🧾 Using Metadata and Column Queries

PurposeMetadata Used
Identify Required Fieldssys_dictionary.mandatory=true
Validate Data Typeselement.column_type=string/date
Track Data Freshnesssys_audit.timestamp
Define Relationshipssys_db_object, sys_dictionary

Sample Metadata Query:

sqlCopyEditSELECT name, column_label, mandatory
FROM sys_dictionary
WHERE name = 'incident';

⚙️ Conditional Builder in ServiceNow

The Conditional Builder empowers users to build complex logic with ease—no code needed.

Key Features:

  • Drag-and-drop conditions
  • Field/operator/value pairing
  • Logical AND/OR combinations
  • Real-time rule preview

Used For:

  • SLA start/stop rules
  • Incident resolution criteria
  • Data validation checks
  • Metadata-triggered automation

🔐 Metadata in Data Trust

In ServiceNow’s Data Trust, metadata governs:

Metadata TypeUsage
Column AttributesData validation and expectations
Update HistoryTrack freshness and audit trail
Ownership AnnotationsAssign accountability
Trust ScoresEvaluate field reliability over time

This metadata isn’t passive—it actively powers governance, quality scoring, and confidence reporting.


📚 Where to Learn More

Other Master Data Quality Dimensions

Digital Center of Excellence: Business Process, COE, Digital Transformation, AI Workflow Reengineering Requirements. https://www.linkedin.com/groups/14470145/
Digital Center of Excellence: Business Process, COE, Digital Transformation, AI Workflow Reengineering Requirements. https://www.linkedin.com/groups/14470145/

Table of Contents