Depending on the device interfaces in use, you have the option to push occupancy schedules down to the controllers instead of occupancy state. This has many advantages including:
•Schedules are pushed down to controllers allowing more reliable control closer to the end devices instead of being held on another server.
•HVAC users can view the schedules in their native environment instead seeing only the current state of the zone.
•Schedule control relieves loading on the Events2HVAC command queue since individual state changes are handled by the controllers. Events2HVAC only pushes the schedules down when the schedules have changed from the last schedule push.
•Local schedules can be used to perform optimal start and stop at the controllers.
•In the case of an interruption between Events2HVAC and the controllers, the controllers can run off the last downloaded schedules until the connection is restored again.
Events2HVAC will process any pre-start, post-stop, or min stop gap times the same way as occupancy state control, but the resulting calculated start/stop commands are converted into schedules for the next 24 hrs. that can be dumped to the native controller schedule object.
On the HVAC side, occupancy schedule control requires a unique schedule object to be created or exposed to Events2HVAC.