Semantic KPI layer

A semantic KPI layer is a business-facing definition layer that gives key performance indicators (KPIs) consistent meaning across data sources, applications, dashboards, and reports. It commonly defines how a KPI should be interpreted, calculated, named, filtered, and grouped so different users and systems refer to the same metric in the same way.

In manufacturing and regulated operations, this layer often sits above raw data from MES, ERP, quality systems, historians, and other operational sources. It does not replace those source systems or the underlying transactional data. Instead, it organizes metric logic and business context so measures such as yield, scrap, downtime, first pass quality, or schedule adherence are calculated consistently.

What it includes

• Standard KPI definitions and naming conventions

• Calculation logic, units, time windows, and aggregation rules

• Business context such as plant, line, work center, product, shift, lot, or order dimensions

• Data mappings that connect operational data fields to business terms

• Governance elements such as ownership, approved formulas, and versioned changes

What it does not mean

A semantic KPI layer is not just a dashboard, a data warehouse, or a list of KPI names in a slide deck. Those may consume or display the layer, but the layer itself is the shared meaning and metric logic. It is also not the same as a general semantic data model for all enterprise data, although it may be implemented as part of one.

Operational meaning

Operationally, a semantic KPI layer helps align reporting between systems that track the same process differently. For example, an MES may record machine states, an ERP may record order completions, and a quality system may record nonconformances. The semantic KPI layer can define how those records contribute to metrics like OEE, throughput, rework rate, or right-first-time so downstream analytics use a common interpretation.

This is especially relevant where KPI disputes arise from different formulas, timing assumptions, or data filters. A governed layer can document whether planned downtime is excluded, whether partial completions are counted, or which event codes roll up into a downtime category.

Common confusion

Semantic KPI layer vs. KPI dashboard: a dashboard presents metrics; the semantic layer defines what those metrics mean.

Semantic KPI layer vs. data model: a data model structures data entities and relationships; a semantic KPI layer focuses on business meaning and reusable metric definitions, though the two often overlap.

Semantic KPI layer vs. master data: master data manages core reference entities such as products or equipment; the semantic KPI layer uses those entities to define and contextualize performance measures.