Skip to main content

Zoned Timestamp

A semantic Value Type for a local date and time in a named timezone, used when the local clock time is the business intent.

type: data-model · status: draft · abstraction: instance

What it is​

Zoned Timestamp represents a local date and time together with an IANA timezone identifier, such as 06:00 at a factory in Europe/London. Use it when the stated local clock time matters, particularly for future shifts, maintenance, collections and delivery windows.

IMOS stores the local date-time, IANA zone, resolved UTC instant and the timezone-database version used for that resolution. The resolved instant gives automations and integrations a stable execution target, while the other fields preserve the user's original intent and make the calculation explainable.

Ordinary daylight-saving transitions are handled by the timezone rules and require no user action. IMOS deliberately resolves the value again when its local time or zone is edited, or when updated timezone rules would change a future instant. It updates affected execution timers and records the change. Any approval or notification requirement belongs to the consuming Module, Business Flow or Capability; users are not asked to manage timezone-database details.

Why it exists​

Many manufacturing commitments are expressed in local operational time: a shift starts at 06:00 at its site, regardless of what that means in UTC. Storing only an instant loses that intent and makes later timezone-rule changes difficult to detect or explain.

Zoned Timestamp preserves both the local commitment and how IMOS resolved it. This lets the platform handle normal daylight-saving transitions automatically, identify future schedules affected by new timezone rules and update execution behaviour through an auditable process. It keeps technical timezone decisions out of ordinary data entry while allowing governed workflows to decide whether a material change needs notification or approval.

Relationships​

Outgoing

  • is an instance of → Value Type (many-to-one)
  • is distinct from → Timestamp — Zoned Timestamp preserves local clock intent and its timezone; Timestamp stores only the resolved instant.

Neighbourhood​

Stakeholder summaries​

  • Product — Lets users schedule work in the local time of a site without managing UTC or timezone-database details. IMOS preserves that intent and handles relevant rule changes through governed workflows.
  • Investor — Provides controlled, auditable handling of future local schedules across jurisdictions without burdening SME users with timezone mechanics.
  • Marketing — Schedule shifts, maintenance and deliveries using the local time that the operation actually follows. IMOS keeps timezone handling out of ordinary data entry and records any rule-driven adjustment.
  • Engineering — Store the local date-time, IANA timezone, resolved UTC instant and timezone-database version. Re-resolve deliberately when the value, zone or applicable rules change; never mutate scheduling behaviour merely because a value is rendered or read.