Note: This method has minimal impact to your existing HVAC system but requires more manual steps to revert back to backup scheduling.
Figure 3- Overriding Priorities
This example shows a BACnet schedule object that has a weekly schedule assigned to turn on AHU-1,2, and 3 from 8am to 8pm. This object sends start commands at a priority of 15. In Events2HVAC, you would create 3 equipment items: AHU-1, 2, and 3.
For each item, you would create an action that sends a command on the start/stop time of an event. This action should send the command at priority 14 (higher) so that it will override any command that is sent from the schedule object.
In this scenario, individual rooms can be assigned to each AHU in Events2HVAC, allowing individual room schedules to turn on/off each AHU. In this scenario, after the end of the event, the priority 14 commands are NOT released, and the object will not revert to the commands from the schedule object (at priority 15) unless the user manually releases the commands for each object.