Optimized start example

To optimize performance, the framework turns an air handling unit on and off based on a weekly schedule.

Figure 1. A simple OptimizedStartStop component wire sheet


In this example:

  • A weekly schedule specifies occupancy times and is linked to the component for calculations (1). The schedule is also linked directly (bypassing the component) to the In16 property (lowest priority in this case) of the occupancy control point (AhuOccCmd) (2).

  • The components Start Enable and Stop Enable properties (3) are both true. This means that both optimized starts and optimized stops are enabled.

  • The Start Time and Stop Time Commands (4) are linked to priority inputs In12 and In13 respectively of the occupancy control point (AhuOccCmd) (5). These commands are true when an optimal start or stop condition is required, otherwise the outputs are set to null, which relinquishes control to the next higher priority level.

Figure 2. Another OptimizedStartStop component wire sheet


Additional logic is linked into the occupancy command component (AhuOccCmd) to control which logic has priority on specifying the AhuOccCmd Boolean point status, as follows:

  • In9 temperature control overrides a demand limiting link from an EDL component to In10. This prevents a load shed if the comfort range that can be configured is exceeded.

  • In10 (demand limiting link from the EDL component) overrides an OptimizedStartStop component’s Stop link into In12.

  • In12 (OptimizedStartStop component’s Stop link) overrides a Start link into In13 (as described above).

  • In13 (optimal start) overrides the schedule link to In16 (lowest priority) (as described above).