time-series data

Time-series data is data collected and stored as a sequence of values, each explicitly associated with a point or interval in time. The core characteristic is that the time order of the data matters and is part of the meaning of the dataset.

In industrial and manufacturing environments, time-series data commonly refers to measurements and signals captured from equipment, sensors, control systems, and software applications at regular or event-driven intervals. Examples include temperature readings from an oven every second, pressure values from a reactor every 100 ms, or machine state changes recorded with precise timestamps.

Key characteristics

• Timestamped: Every record includes a timestamp (or time range) that defines when the measurement or event occurred.
• Ordered by time: The sequence in which data points occur is essential for interpretation, analysis, and modeling.
• Often high frequency: In OT and industrial control, data may be collected many times per second, resulting in large volumes.
• Typically numeric but not limited to it: Values are often numeric (e.g., flow rate, RPM, current) but can also be states or categorical events (e.g., “machine running”, alarm codes).
• Append-only in practice: Operationally, new measurements are continuously appended; historical values are rarely changed, except in data cleansing or backfill scenarios.

Where time-series data appears in manufacturing

• Control and automation systems: PLCs, DCS, and SCADA systems record process variables, setpoints, and alarms over time.
• Historian systems: OT data historians are specialized databases optimized for storing and querying time-series data from equipment and lines.
• MES and quality systems: Production counts, cycle times, and inline quality measurements can be stored as time-series for later OEE, NPT, and SPC analysis.
• IoT and condition monitoring: Vibration, temperature, and current draw data used for predictive maintenance is typically modeled as time-series.
• IT and infrastructure monitoring: Logs and performance metrics from servers, networks, and applications are also forms of time-series data.

Operational use

Operational teams and digital systems use time-series data to understand how processes behave over time, detect anomalies, correlate events, and reconstruct what happened during a batch, shift, or deviation. Common uses include trending key variables on an HMI, performing root cause analysis by aligning multiple signals on a time axis, and building analytics or models that depend on temporal patterns, such as predicting equipment failures or monitoring process stability.

Common confusion

• Time-series data vs. transactional data: Transactional data (such as work orders, material movements, or batch records) describes discrete business or production events, often with timestamps, but is organized primarily around the event or object rather than the continuous evolution of a variable. Time-series data is organized around how a signal or metric changes over time.
• Time-series data vs. event logs: Event logs are lists of discrete events with timestamps (for example, alarm raised, recipe started). They are technically a form of time-series data, but in industrial practice, “time-series” often implies continuous or periodic measurements, while “event log” implies sparse, irregular events.

Relation to digital technology in manufacturing

Digital manufacturing technologies, including data historians, IoT platforms, and operations intelligence tools, are designed to capture, store, and analyze time-series data from shop floor assets and systems. This data is often integrated with MES, ERP, and quality system data to provide time-aligned views of equipment performance, product quality, and process conditions across regulated production environments.