I’m working on a system in Ignition that pulls order confirmations from an API. The API stores all confirmations in UTC, which is ideal. The challenge I’m facing is that these confirmations originate from multiple plants, each in different time zones and operating on different shifts. The shift sta…

So for the shift start and end time if I store that data in a tag as a string the client can make it's own determination on what the UTC value of that is when it evaluates that? So for example i have 2 tags StartTime 8:00am EndTime 4:30pm Because my client is timezone aware and my start and end …

Under no circumstances are you to use the built-in date/time functions to manipulate dates and times in different time zones. Use the ZoneId, LocalDateTime, ZonedDateTime, and DateTimeFormatter for all manipulation, parsing, and stringification.

So how should I best store and retrieve shift data like ShiftStart and ShiftEnd? If my ShiftStart is 8:00am in Daylights Saving, I need it to still be 8:00am outside of Daylights Savings. My UTC time range I pull would change by an hour. My shift times are the constant in the local times. Some how…

Parse to a LocalDateTime, actual date + shift start/end time. Convert to a ZonedDateTime by applying the ZoneId. That can be converted to the UTC-under-the-hood java.util.Date that Ignition uses everywhere when sending timestamps to tag history or other Ignition APIs. Just don't print those anywh…

Local Time to UTC Shift Start Times across timezones

Ignition

pturmel May 29, 2026, 1:26pm 2

I would store just the relevant ZoneId in the tag, and do everything else in the UI. See these topics for references to using java's more capable date/time classes: