UTC

UTC (Coordinated Universal Time) is the primary international time standard used to measure and synchronize time across different regions and systems. It does not observe local time zones or daylight saving rules. In industrial and manufacturing environments, UTC is commonly used for system clocks, event timestamps, and cross-site data integration so that time-based data from different plants can be compared and analyzed consistently.

Key characteristics

• Time standard, not a time zone: UTC is a reference time scale that remains constant worldwide. Local time zones are defined as offsets from UTC (for example, UTC+2 or UTC-5).
• No daylight saving changes: UTC does not shift forward or backward seasonally, which avoids ambiguity and gaps in time-series data.
• Basis for offsets: All civil time zones and many industrial scheduling and logging systems are defined using an offset from UTC.
• System-level usage: Many OT, MES, historian, and ERP systems internally store timestamps in UTC, even if they display local time to users.

Use in manufacturing and regulated environments

In manufacturing operations, UTC is commonly used to:

• Normalize event logs, alarms, batch records, and production data from multiple sites that operate in different time zones.
• Support consistent calculation of time-based KPIs such as OEE, NPT, and on-time delivery across plants.
• Improve traceability and auditability by providing unambiguous timestamps for quality records, electronic batch records, and equipment logs.
• Align data integration between OT systems (for example, historians, PLC logs) and IT systems (for example, MES, ERP, LIMS) using a common time reference.

Operational considerations

Although systems may store data in UTC, operators usually work with local time for shifts, plant calendars, and work schedules. Practically, this often means:

• System clocks are configured in UTC, with user interfaces converting to and from local time zones for display.
• Shift definitions and plant calendars are defined in local time, while underlying timestamps remain in UTC for cross-site reporting.
• Data warehouses and analytics platforms convert local timestamps to UTC to combine and compare data from different locations.

Common confusion

• UTC vs GMT: GMT (Greenwich Mean Time) is a historical time standard and sometimes used informally as a time zone. UTC is the modern, precise standard used in computing and industrial systems. For most operational uses in manufacturing, UTC is the relevant term.
• UTC vs local time zone: UTC does not include a geographic or political region. A local time zone (for example, Central European Time) is defined as UTC plus or minus an offset and may include daylight saving rules.

Link to cross-site KPI and calendar alignment

When plants are in different time zones or follow different shift models and holidays, using UTC for underlying timestamps allows KPI calculations and reports to be normalized. Local definitions for runtime, downtime, or backlog can then be consistently aligned by converting each plant's local time data to UTC before aggregation or comparison.