Description
Calculate added usage falling inside one supplied tariff block.
Energy prices and charges depend on energy units, demand units, standing-charge days, tariff periods and settlement sign conventions. Purchased-energy losses differ from delivered-energy fractions, and signed prices can produce negative monetary terms. Nominal battery cost allocations are supplied scenarios rather than physical aging forecasts.
Calculate added usage falling inside one supplied tariff block.
When to use this tool
Use Tariff Block Marginal Charge when you already have usageBefore, addedUsage, blockLower, blockUpper, pricePerUnit and need to calculate added usage falling inside one supplied tariff block.
How to use the tool and how it works
- Enter usageBefore, addedUsage, blockLower, blockUpper, pricePerUnit. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read addedUsageInBlock, blockCharge. Use the output convention below.
Require nonnegative usageBefore/addedUsage/blockLower/price and blockUpper>blockLower; overlap=max(0,min(before+added,upper)-max(before,lower)), charge=overlap*price.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| usageBefore | Usage Before | Required. Finite number; minimum 0. |
| addedUsage | Added Usage | Required. Finite number; minimum 0. |
| blockLower | Block Lower | Required. Finite number; minimum 0. |
| blockUpper | Block Upper | Required. Finite number. |
| pricePerUnit | Price Per Unit | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| addedUsageInBlock | Incremental cumulative-usage interval overlapping this one tariff block, not total usage in all blocks. | Required. Finite number. |
| blockCharge | Block Charge | Required. Finite number. |
{
"input": {
"usageBefore": 90,
"addedUsage": 30,
"blockLower": 100,
"blockUpper": 200,
"pricePerUnit": 0.2
},
"output": {
"addedUsageInBlock": 20,
"blockCharge": 4
}
}Limitations and assumptions
- This covers one block's incremental usage, not the complete bill. Block units, accumulation period and tariff order are supplied; extreme arithmetic can lose precision.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Reconcile the actual meter series, tariff, contract and billing definitions for an account or market question. Use a complete cash-flow or physical-energy model when needed; a single block overlap, index ratio or supplied settlement term cannot establish actual charges or performance.
References
Similar or alternative tools
- Energy Tariff Time Band Boundary
Check a clock minute against a supplied daily tariff band.
- Demand Charge Peak Interval Cost
Calculate a supplied demand-charge term above a billed floor.