Different objects interact in an Optimal Start application. The following figure illustrates a sample Optimal Start application. The table describes the objects and their role in an Optimal Start application.
|
# |
Object or Attribute |
Role |
|---|---|---|
|
1 |
Optimal Start (OST) Object |
Receives temperature, setpoint, and scheduling data to determine optimal start and optimal stop times for the building zone. |
|
2 |
Schedule Object |
Provides occupied and unoccupied times for the building zone. |
|
3 |
Zone Occupancy Mode |
Refers to the binary or multi-state output and value objects that command a zone to occupied or unoccupied. It is commanded by the Schedule object to occupied and by the Optimal Start to unoccupied, possibly earlier than scheduled if the Maximum Prestop Time attribute is non-zero. |
|
4 |
Zone Warmup or Cooldown Mode |
Refers to the binary or multi-state output and value objects that command the zone to warm up or cool down. It is commanded by the Optimal Start object at the optimal start time and released at the occupied time. It will not be released if the Zone Warmup or Cooldown (WC) Mode and the Zone Occupancy Mode objects are the same. |
|
5-8 |
Zone Temperature, Cooling Setpoint, Heating Setpoint, Outdoor Air Temperature |
Refers to the analog attributes (within Analog Input objects, Analog Value objects, for example) that are referenced by the Optimal Start object and provide the temperatures and setpoints for use in calculations. |