How do kW and kWh answer different questions?
Kilowatts describe the rate of electricity use; kilowatt-hours describe accumulated energy. A 20-kW load operating for three hours uses 60 kWh in a simplified constant-load example. Two hotels can have the same monthly kWh while one has a much larger peak because its equipment operates together.
That distinction changes the cost-control decision. Reducing operating hours can lower energy. Spreading necessary tasks across the day may reduce a qualifying peak while leaving energy similar. Neither outcome should be assumed from the other, and neither establishes the exact invoice effect without the tariff.
The hotel bills hub puts demand alongside other components. Demand is not a generic surcharge for being busy. It is a defined calculation that management can investigate through bills, interval data, and equipment schedules.
A demand ratchet is a tariff look-back rule that uses specified earlier demand measurements when establishing the current billing demand.
Which peak does the utility charge for?
Read the complete demand section of the current rate schedule, including referenced riders. Determine the measurement interval, applicable hours, seasonal differences, minimum demand, and separate demand components. An invoice can contain more than one demand calculation, so reducing one peak may not reduce every line.
The DOE rate-options guide distinguishes noncoincident demand, time-of-use demand, system-peak charges, and look-back rules. These categories provide a reading framework; the hotel’s tariff supplies the actual rule. Ask the utility for the calculation if its billed quantity cannot be reproduced from available records.
Compare the bill’s measured and billing demand. If they differ, identify why before designing a controls project. Engineering may successfully reduce this month’s measured peak while accounting still sees a historical floor. That can be correct tariff operation rather than evidence that the meter missed the improvement.
| Mechanism | Quantity that matters | Operational implication |
|---|---|---|
| Noncoincident monthly peak | Highest qualifying account interval | Any included interval can establish the charge |
| Time-of-use demand | Highest interval within designated windows | Move controllable overlap outside the relevant window where practical |
| Ratchet | Current demand compared with a historical floor | Benefits may be delayed until earlier peaks leave the calculation |
| System-related allocation | Account contribution during specified system peaks | Track the applicable allocation method and effective period |
What does a hypothetical ratchet calculation show?
Assume an illustrative tariff bills the greater of current demand or 80% of the highest qualifying peak in its stated prior period. A hotel previously reached 250 kW and now measures 170 kW. The historical floor is 250 × 0.80 = 200 kW, so assumed billing demand is 200 kW.
At a hypothetical demand price of $14/kW, the component costs 200 × $14 = $2,800. Reducing current demand from 170 to 160 kW would not lower that component under the assumed rule because both remain below the floor. These inputs illustrate a mechanism; they are not the hotel’s tariff or a current utility price.
If the earlier 250-kW peak later leaves the look-back calculation, the floor may change, but check for other historical peaks and any minimums. Model the actual sequence month by month. Do not promise immediate savings from a demand project when the tariff creates a delay.
Where do hotel peaks usually need investigation?
Start with the actual highest qualifying intervals. Compare them with cooling plant stages, guest-room recovery, laundry runs, kitchen preparation, water heating, and chargers. The relevant issue is coincidence: individually reasonable loads can create a costly overlap when several systems recover or start together.
For a full-service hotel, event setup may overlap daytime laundry and cooling. A limited-service property may have room-conditioning recovery and laundry clustered before check-in. These are investigative examples, not findings about any particular hotel. Equipment and meter records must show whether the proposed cause occurred.
Use why electric bills rise with flat occupancy to separate activity from pricing and historical billing effects. The peak day need not be the highest occupancy day, and the highest hourly quantity in an exported file may not match a tariff using a different interval.
How can load factor help prioritize the question?
Load factor compares average power with peak power for a consistent period. It can indicate whether a large peak is supported by continuing load or represents relatively concentrated use. Use measured peak and period hours consistently; a ratcheted billing quantity answers a different question from actual peak operation.
In a hypothetical 30-day period, 72,000 kWh divided by 720 hours produces 100 kW average power. Against an actual peak of 250 kW, load factor is 100 ÷ 250 = 40%. If peak falls to 200 kW at the same energy volume, the ratio becomes 50%.
The ratio is an analytical indicator, not a universal hotel target or proof of a fault. A property’s climate, systems, and service obligations affect its load shape. Use it to ask where peaks concentrate, then evaluate specific changes against the actual tariff and operating limits.
What can engineering change safely?
Look first for unnecessary simultaneous startup and scheduling flexibility. Test laundry staggering, plant sequencing, charger power limits, and recovery schedules with qualified staff. Confirm that the revised sequence still delivers clean linen, kitchen readiness, room comfort, and essential services when needed.
Do not shut off critical systems or alter water hygiene, ventilation, food safety, or humidity safeguards to meet a financial target. Document acceptable control limits and a manual override. Observe the recovery period: a rebound can create a new qualifying peak or simply move the same problem later.
Use an operational pilot with interval monitoring before rolling a change across every hotel. Separate actual measured reductions from simulated ones. If staff cannot maintain the schedule during busy events or weather extremes, include that constraint in the budget rather than describe the best test day as an annual result.
How does demand response differ from ordinary peak control?
The DOE demand-response guidance describes programs that compensate qualifying reductions during events. Those programs can have separate eligibility, notice, baseline, testing, and performance requirements. A reduction in billed utility demand does not automatically earn program compensation.
Check interactions with other arrangements and have staff know which signal governs a response. A hotel’s internal peak alert, a utility event notice, and a grid capacity peak forecast can arrive for different reasons. Define the objective and measurement for each rather than treat every hot-day alert as the same purchasing opportunity.
Capacity allocation is a separate subject in PLC tags and capacity charges. Read it before assuming a lower monthly demand line also reduces next year’s supplier capacity cost. The relevant hours, adjustments, and effective periods can differ.
How should accounting verify the result?
- Obtain the applicable demand tariff and calculation rules.
- Reconcile measured and billing demand on recent invoices.
- Inspect qualifying interval timestamps and operating records.
- Test a feasible schedule within engineering limits.
- Measure current peak changes and any rebound.
- Recalculate the component including ratchets and minimums.
- Track subsequent bills before claiming realized benefits.
The Pennsylvania bill resource also reinforces separating supplier and utility components. If procurement accompanies the project, request broker compensation details, including any embedded adder or direct fee, and include them once in comparisons. A useful demand program ends with a defensible operational change and a reconciled invoice, not merely a lower point on a monitoring chart.