Aggregation Level

Aggregation level commonly refers to the degree of detail or summarization applied to data when it is collected, stored, analyzed, or reported. In industrial and manufacturing environments, it describes how information is grouped, such as per unit, batch, work order, shift, production line, plant, or enterprise.

Core meaning

An aggregation level is a defined layer of granularity at which data points are combined into a single record or metric. It determines:

• What each record represents (for example, one sensor reading vs. one batch)
• How many raw events are rolled up into that record
• Which questions can be answered from the dataset or report

Common aggregation levels in manufacturing and regulated operations include, for example:

• Event or sample level: individual sensor readings, operator entries, or quality measurements
• Unit or device level: all records tied to a specific serial number or equipment item
• Batch or lot level: data grouped by batch ID, lot number, or work order
• Shift or time period level: data grouped by shift, hour, day, week, or month
• Line, area, or site level: data summarized by production line, cell, area, or plant
• Enterprise level: consolidated data across multiple plants or business units

How aggregation level is used in operations

In OT, MES, ERP, and quality systems, aggregation level influences how information is:

• Stored: time-series historians may keep fine-grained data (per second), while data warehouses store hourly or daily summaries.
• Displayed: dashboards may present OEE per line per shift, while traceability tools retain unit- or batch-level records.
• Integrated: interfaces between MES and ERP often define alignment by order, batch, or period-level aggregates.
• Used for compliance: regulated environments may require specific aggregation levels (for example, batch-level records for release decisions) while still retaining underlying detailed data for investigations.

Choosing an aggregation level is typically a trade-off between data volume, performance, and the need for detailed traceability or root-cause analysis.

What aggregation level does not mean

• It is not the calculation method itself (for example, average vs. maximum) but the grouping to which that method is applied.
• It is not the data model or schema, although aggregation levels are usually embedded in those designs.
• It is not limited to time; it can be based on product, batch, equipment, or organization hierarchy.

Common confusion

• Aggregation level vs. aggregation function: The level describes the grouping (per batch, per day). The function describes how values are combined within that group (sum, average, minimum, count).
• Aggregation level vs. data resolution: Resolution usually refers to how frequently data is sampled (for example, every second). Aggregation level describes how those samples are grouped for storage or reporting (for example, one value per minute or per batch).

Context in manufacturing systems

Standards and reference models for manufacturing operations and integration often assume multiple aggregation levels across system layers, such as detailed event data at equipment level and aggregated production data at site or enterprise level. When designing KPIs, reports, or interfaces between OT, MES, and ERP, the required aggregation levels need to be explicitly defined to support traceability, quality investigations, and management reporting.