Canonical time model

A canonical time model is a standardized way of representing time-related data so different systems, applications, and records use the same structure and meaning. It commonly defines how timestamps, time zones, offsets, durations, intervals, and calendar references are formatted and interpreted when data moves between systems.

In manufacturing and regulated operations, a canonical time model is used to reduce ambiguity when MES, ERP, historians, quality systems, equipment data sources, and reporting tools exchange time-based information. The goal is not to create a new clock source, but to create a common representation of time so events can be compared, sequenced, and traced reliably across systems.

What it includes

• Timestamp format, such as a consistent date-time pattern

• Time zone handling, including whether times are stored in UTC, local time, or both

• Offset rules, daylight saving treatment, and normalization conventions

• Definitions for durations, elapsed time, shift time, and effective time windows

• Business rules for event time, record creation time, update time, and system processing time

What it does not mean

A canonical time model is not the same as time synchronization itself. It does not guarantee that devices or applications are set to the same clock, and it does not replace protocols such as NTP or PTP. It also is not just a display format for dashboards. It is a data model and interpretation standard used so time values remain consistent across integrations and records.

How it appears in operations

Operationally, a canonical time model often appears in integration mappings, event schemas, data lake models, API contracts, historian connectors, and traceability records. For example, a machine event may be generated in local controller time, converted by an edge or middleware layer, and stored in a canonical format so MES, analytics, and quality systems all interpret the event consistently.

This matters where sequence and timing affect production history, exception review, electronic records, downtime analysis, alarm handling, and genealogy. Common examples include aligning batch events, reconciling operator actions with equipment states, and comparing production timestamps across plants or regions.

Common confusion

Canonical time model is often confused with time synchronization. Time synchronization keeps clocks aligned. A canonical time model keeps time data represented consistently.

It can also be confused with a data model more generally. A canonical data model may include many entities such as materials, orders, and equipment. A canonical time model is the part that standardizes time semantics within or across those entities.

In analytics contexts, some teams use the term loosely to mean a standard reporting calendar. That is related, but narrower. A canonical time model usually covers machine-readable timestamps and event timing rules, not only fiscal or reporting periods.