reference data

Reference data commonly refers to relatively stable, shared data sets used by systems and people to classify, describe, validate, or standardize operational records and transactions. It provides the agreed values that other data depends on, such as codes, lists, categories, units of measure, status values, site identifiers, supplier IDs, defect codes, and reason codes.

In manufacturing and regulated operations, reference data appears across MES, ERP, QMS, LIMS, CMMS, and integration layers. It helps ensure that transactions are recorded using consistent terms and identifiers so records can be compared, exchanged, reported, and audited more reliably. Examples include approved material groups, equipment classes, production line names, shift codes, country codes, test method lists, and nonconformance disposition codes.

Reference data is not the same as transactional data. A work order, inspection result, batch record, or inventory movement is transactional data. The status codes, product family values, defect categories, or unit codes used inside those transactions are reference data. It also differs from master data, which usually identifies core business entities such as a material, customer, supplier, asset, or employee. Reference data often supports master and transactional data by providing controlled attributes and lookup values.

Operational meaning

Operationally, reference data is often maintained in one or more source systems and then synchronized to connected applications. For example, an ERP may hold plant codes and units of measure, while a QMS maintains defect classifications and an MES consumes both for production and quality recording. Poorly aligned reference data can cause interface failures, duplicate meanings, reporting inconsistencies, or invalid entries.

• Examples of reference data include controlled code lists, enumerations, taxonomies, status values, and standardized lookup tables.

• It may be enterprise-wide, site-specific, or process-specific depending on governance and system design.

• It is usually more stable than transactional data, but it still changes through review, versioning, and controlled updates.

Common confusion

Reference data vs. master data: master data describes key business objects such as products, suppliers, assets, or bills of material. Reference data provides the allowed values and classifications used around those objects.

Reference data vs. metadata: metadata describes the structure, format, lineage, or meaning of data fields and records. Reference data is the actual set of allowed business values used by those fields.

Reference data vs. configuration data: configuration data controls how a system behaves, such as routing logic, thresholds, or workflow settings. Some organizations manage these together, but they are not always the same thing.

Why it matters in connected manufacturing systems

When systems exchange production, quality, maintenance, or supply chain data, consistent reference data helps prevent mismatches such as one system using a defect code that another system does not recognize. In regulated environments, this is relevant to data consistency and traceability of records, but the term itself does not imply any specific compliance status or control level.