Calculator Inputs
Formula Used
- Baseline usage depends on the method:
Average: baseline = Σ usage / n · Median: middle value after sorting · Weighted: higher weights for recent months · Trend-adjusted: linear regression forecast for next month.
- Degree-day normalization (optional):
adjusted_usageᵢ = usageᵢ × (target_DD / DDᵢ) when degree days are provided.
- Monthly bill:
energy = usage × rate
subtotal = energy + fixed + other + (demand_kW × demand_rate)
tax = subtotal × tax%
total = subtotal + tax - NPV (optional):
Annual savings escalate by the entered rate: savings_t = savings₁ × (1+g)^(t−1)
NPV = −cost + Σ [ savings_t / (1+r)^t ]
How to Use
- Enter baseline months from bills (usage, and rate if available).
- Pick a baseline method that matches your data stability.
- Optionally add degree days to normalize weather effects.
- Fill the scenario fields to model expected future usage and rates.
- Add project cost and financial settings to estimate payback and NPV.
- Click Calculate. Export CSV or PDF if needed.
Baseline selection improves forecasting accuracy
Using 12 months of bills, the average method smooths noise and gives a stable monthly baseline. Median is useful when one or two months include outages or unusual occupancy. Weighted recent months helps when usage drifts; trend-adjusted forecasts the next period. A coefficient of variation below 10% typically signals a dependable baseline, while 20% or higher suggests operational changes worth investigating.
Weather normalization reduces seasonal distortion
When heating or cooling dominates, degree-day normalization aligns each month to a common weather target. For example, 820 kWh at 210 degree days scaled to a 120 target becomes 468 kWh. This makes shoulder-season comparisons fairer and highlights non-weather loads such as lighting, servers, or process equipment. If degree days are missing, the calculator keeps raw usage.
Tariff structure changes total cost drivers
Energy charges scale with usage, but fixed fees and demand charges can dominate small facilities. A 0.19 rate on 650 units produces 123.50 of energy cost, yet a 15 demand charge at 12.00 per kW adds 180.00 before tax. Demand inputs are optional, but they matter for many commercial tariffs. Modeling these components separately improves contract evaluation and rate plan selection. Taxes apply as a percent of subtotal, so policy shifts are easy to test.
Variance tracking supports budget controls
Once a baseline is set, the monthly variance equals baseline total minus scenario total. Finance teams can set triggers, such as a 5% unfavorable swing, to review schedules, setpoints, or maintenance actions. Tracking annualized variance also helps quantify persistent drift versus one-time events. Pair variance with usage delta to separate volume from price effects.
Cash-flow metrics translate savings into value
Annual savings are the monthly difference multiplied by 12, then escalated by expected price growth. Discounting future savings converts them to present value for capital planning. Sensitivity tests at 6% and 12% show how valuation changes. Projects with positive NPV and payback under the asset life are generally easier to approve, especially when variability remains low.
FAQs
1) How many baseline rows do I need for a reliable result?
Enter at least 3 months, but 12 months is best. More rows reduce noise, improve trend detection, and make the variability metric meaningful, especially when seasons or tariffs change.
2) When should I use Median instead of Average?
Use Median when one or two months are abnormal due to outages, renovations, vacancy, or extreme weather. It ignores outliers better than an average and often matches “typical” billing behavior.
3) My utility has tiers or time-based pricing. What rate should I enter?
Use a blended rate: total energy charges divided by total usage for the month. If you have a consistent tariff, enter monthly blended rates in the baseline table for a more accurate baseline rate.
4) What happens if I enable degree-day normalization?
The calculator scales each month’s usage to a common degree-day target. This reduces seasonal distortion for heating or cooling loads. If degree days are missing or zero, that month stays unadjusted.
5) Do I need to fill demand charges?
Only if your bill includes demand. Demand charges can outweigh energy charges for some commercial sites, so adding kW and $/kW helps the scenario reflect peak-management measures accurately.
6) How should I interpret NPV and payback results?
Payback estimates how quickly savings recover project cost. NPV discounts future savings to today’s value. Positive NPV usually supports investment, but confirm assumptions for escalation, discount rate, and expected savings stability.
Example Data Table
Sample baseline rows and typical bill terms. Use your own utility details for accuracy.
| Period | Usage (kWh) | Rate ($/kWh) | Degree days |
|---|---|---|---|
| Jan | 820 | 0.17 | 210 |
| Apr | 690 | 0.18 | 90 |
| Jul | 620 | 0.19 | 10 |
| Oct | 710 | 0.18 | 85 |