📊Computational Reference Data

NEW

Also known as: Dynamic Reference Data, Calculated Reference Data

Frequently updated reference values, such as rates and indices, used in business calculations and analytics across systems.

DESCRIPTION

Computational reference data includes values like FX rates, benchmark interest rates, CPI, and index weights. Though reference-like in use, they change regularly and demand time-based governance. They drive consistent calculations for pricing, risk, and KPIs. Stewardship covers sourcing, validation, timeliness SLAs, and lineage. Systems should store effective dating and handle late or revised values. Clear definitions and documentation reduce reconciliation issues.

ALTERNATIVE DEFINITIONS

IBM

Reference data is a class of data used to categorize other data.

Computational reference data is a frequently changing subset used in calculations and time-sensitive categorization.

Source

Wikipedia

A price index is a normalized average of price relatives for a given class of goods or services in a given region, during a given interval of time.

Provides an example of indices commonly used as computational reference data.

Source

RELATED TERMS

Reference Data Temporal Data Index Exchange Rates Benchmark Rates Business Rules Data Quality SLA

COMPETING TERMS

Static Reference Data Master Data

RELATIONS

• Broader: Reference Data

KNOWLEDGE AREAS

Reference & Master Data Data Management Data Science

TARGET AUDIENCE

Data Steward Data Analyst Data Engineer BI Specialist Chief Data Officer

EXTERNAL SOURCES

• Wikipedia - Index (economics)
• U.S. Bureau of Labor Statistics - Consumer Price Index data
• IMF - FX rates and macro data
• Bank for International Settlements - Benchmark rates reform

TOP QUESTIONS

How is Computational Reference Data different from Master Data?

Master data changes slowly and describes core entities; computational reference data are time-varying values used in calculations.

Category: Comparison

What governance is required for Computational Reference Data?

Source validation, timeliness SLAs, effective dating, lineage, and audit trails are essential.

Category: Governance

How do I handle late or revised values?

Implement backfill and reprocessing strategies, and track correction flags for transparency.

Category: Guidance

What are examples of Computational Reference Data?

FX rates, interest benchmarks, CPI, index weights, and tax rates are common examples.

Category: Examples

What risks are associated with poor management?

Mispricing, regulatory breaches, and inconsistent KPIs can occur, impacting financials and trust.

Category: Risks

How often should Computational Reference Data update?

Cadence varies by source, from daily FX rates to monthly CPI; align ingestion with source schedules.

Category: Lifecycle

How to model effective dating?

Use valid-from/valid-to fields or bitemporal schemas to manage historical corrections and as-of queries.

Category: Implementation

What quality checks are important?

Range checks, outlier detection, cross-source reconciliation, and completeness checks are vital.

Category: Testing

Where should these data be stored?

In curated, versioned stores (e.g., feature stores or reference hubs) with downstream distribution via APIs.

Category: Architecture