©2025 Copeland LP.
026-1803 R13 Supervisor I&O User Guide 9 - 28
There are several factors that affect the order of how the loads
are shed and restored:
• Minimum shed time - the minimum time that a shed
load must stay in shed
• Minimum restore time - the minimum time that a shed
load must stay in restore (not shed)
• Maximum shed time - the maximum time that a shed
load may remain actively shed
Another load is not shed to replace a load that is restored due
to the maximum shed time expiring unless the power level is
still above setpoint.
If a shed level is in restore mode but its minimum restore time
is not met, levels in the next higher category will not be shed.
For instance, if all the first sheds are shed and one of the first
sheds times out due to max shed time, rotate and last shed
loads will not continue to shed until all first shed loads are
shed again.
Multiple loads can be assigned to each shed level, but a user
should assign the same KW to each shed level. The KW
assigned to a shed level is used by the application in
determining how many shed requests should be shed at one
time. However, since the application doesn't know the On/Off
status of the loads assigned to a shed level and since the total
KW that can be shed is usually only a portion of the total
electrical power used, the application cannot accurately
predict the actual results of a shed request. To compensate
for this, the application assumes only 75% of the reported
load being On. Additionally, the application is always taking
immediate action when the power level is exceeding the KW
Demand setpoint and it can bring the power level under
control without a new demand level being recorded by the
power company.
9.15.4 Application Alarms
The Demand Control an application provides application
alarm to signal a high demand. The demand alarm limit and
alarm delay should be configurable.
9.15.5 KW Load Specification
The application allows the user to specify the KW rating for
each load connected to the Demand Control application. The
application uses this information to help determine how
many loads to shed at one time to prevent exceeding the
demand setpoint.
9.15.6 Performance Requirements
KWH Pulse Input
1. When configured for KWH pulse input, the Demand
Control application must detect 100% of all pulses
present on the input, as long as the pulses occur no faster
than 50 pulses/second (PPS) and have pulse width of at
least 20ms.
2. The local digital inputs on the controller are able to
support 50 PPS. Digital inputs located on expansion
modules (such as IPX60) do not support KWH pulse
inputs.
9.16 Utility Monitoring
The Utility Monitoring application tracks the consumption of
metered services (such as electricity, gas, or water) and
monitors the consumption in four separate time intervals:
Daily, Weekly, Monthly, and a user defined interval.
The number of Utility Monitoring applications allowed is
based on the total number of applications allowed in the
controller. Additional applications may be added with a
separate license key.
9.16.1 Utility Usage Calculation
9.16.1.1 Utility Type
The user can specify the type of utility to monitor by selecting
either Electricity, Gas, or Water via the Usage Type parameter.
The appropriate engineering units will be automatically
configured based on this selection. For example, if Water is
selected, the rate outputs (Present and Average) will be
shown in the active user’s selected water rate units, such as
Liters/Min or Gallon/Min. Also, the periodic totalizer outputs
will be shown in the active user’s selected water volume units,
such as Liters or Gallons. Likewise, if Electricity is selected, the
Present and Average outputs will be shown in power units
such as kW or watts and the periodic totalizer outputs will be
shown in the energy units of kWh or watt-hours. The default
units shown are dependent on the location settings
configured on the controller.
To Next Page
Loading...