Issue
Intermittent master / slave calendar and schedule operation between I/A Series R2 Enterprise Server and UNC. Schedules do not appear follow or recalculate during holiday override conditions.
Environment
I/A Series R2, Enterprise Server, UNC
Cause
Master/slave schedule objects were used however the calendar object only links to the local schedule.
Resolution
Proper implementation of Enterprise Server to UNC master/slave calendar and schedule objects.
Schedule:
- Master schedule objects reside in the Enterprise Server and slave schedule objects reside in UNC controller.
- Link the masterOut from a Enterprise Server Schedule object to the masterIn input of one or more UNC Schedule objects. In case of a communications failure between devices, each UNC retains schedule configurations, as this data is persistently stored in all Schedule objects.
Calendar:
- Master calendar objects reside in the Enterprise Server and slave calendar objects reside in UNC controller.
- Link the masterOut from a Enterprise Server calendar object to the masterIn input of one or more UNC calendar objects. In case of a communications failure between devices, each UNC retains calendar configurations, as this data is persistently stored in all calendar objects.
Linking:
- Linking of calendar to schedule ... link the local calendar's output to the local schedule's holiday override input (e.g. master calendar to master schedule or slave calendar to slave schedule). The holiday override should not externally link across the network.
- In addition, a holiday schedule must not be left blank (no events), “assuming” inactive. Otherwise, an output that is active upon transition to the holiday day will remain active.
