Issue
Is it necessary to create a separate Continuum network for a site located in a different time zone, even if it's the only one outside the Time Zone?
Product Line
Andover Continuum
Environment
- Continuum system with sites across multiple time zones
- UTC time zone configuration
- Continuum Networks
Cause
The site in question operates in a different time zone than the rest of the sites being integrated into the Continuum system. This discrepancy can lead to complications in data logging, scheduling, and alarm management.
Resolution
While it is technically possible to manage schedules locally and have alarms timestamped according to the local time zone, these approaches are not optimal for system-wide operations in Continuum.
Extended logs become difficult to manage when data points are logged by a controller in Time Zone A and then accessed by a CyberStation in Time Zone B. This mismatch can lead to confusion and inefficiencies in interpreting historical data.
For this reason, it is not advisable to place controllers from different time zones under a single Continuum Network.
Extended logs are stored in the database using UTC timestamps. CyberStation interprets these logs through reports or groups, which can lead to inconsistencies if time zones are not aligned across the network.
Recommendation
To ensure consistent data logging and system behavior, create separate Continuum networks for sites operating in different time zones.
