Hotel demand register versus capacity tag

The utility invoice shows a hotel maximum in kW, while a supplier worksheet lists PLC and NSPL values. The numbers differ, and the owner asks which is wrong. They may all be valid if they describe different periods and methods. The first task is to identify each determinant rather than force them to match.

The bills hub connects these records with the invoice. This guide builds a register-to-tag comparison for an account question, not a universal formula for every capacity or transmission charge.

What does the monthly demand register represent?

Read the actual tariff class and billing provisions. Identify the measured interval, qualifying period, any ratchet or adjustment, and the determinant shown on the statement. A local meter maximum and billed demand can differ under the applicable schedule.

Ohio Power’s October 2026 tariff book provides current class-specific provisions in its territory. Use the hotel’s actual eligible schedule; the document does not establish a national hotel demand rule.

The demand-charge guide provides the broader concepts. For reconciliation, preserve the exact determinant and source period rather than using a chart’s largest point as a substitute.

Where do capacity and transmission tag methods come from?

PJM’s PLC and NSPL methodology collection points to utility-specific approaches. Use the relevant utility document and actual account record rather than applying another territory’s method.

Identify the reference year or period, relevant coincident measures, adjustments, and accepted customer quantity. A tag can represent a different boundary from the month’s local maximum. Keep any methodology terminology unchanged in the source file.

The capacity-tag definition explains the vocabulary. Labels such as PLC or related capacity terms should still be reconciled with the actual provider’s definition and units instead of treated as mechanically interchangeable fields.

What does the capacity-market framework add?

PJM’s Manual 18 describes the capacity-market framework and relevant load obligations. It supplies market context, not a hotel-specific supplier invoice or confirmation of the account’s accepted tag.

Keep wholesale or load-serving obligations separate from the actual retail agreement. A supplier can package or pass through components according to its product terms. The presence of a capacity-related line does not establish the formula without the governing agreement.

Use the capacity-charge guide for the broader expense explanation. Here the narrower question is whether the source tag, invoice determinant, period, and commercial component are being compared correctly.

How are units reconciled without changing definitions?

EIA’s electricity measurement explanation distinguishes power and energy. kW and MW are power units, while kWh represents accumulated energy. A monthly kWh total cannot replace a capacity-related power value.

Convert power units explicitly when needed and preserve the original quantity. One MW equals 1,000 kW. That arithmetic makes labels comparable but does not change the method, reference period, or adjustments behind them.

Ask the provider to explain unfamiliar fields. A worksheet can include several accepted quantities with similar abbreviations. The analyst should not select the smallest number simply because it produces a preferred cost scenario.

What does an assumed comparison show?

Assume a teaching example has a billed monthly demand of 400 kW, a capacity-related record of 250 kW, and another record shown as 0.25 MW for the same defined capacity quantity. The last two are numerically equivalent after conversion.

The 400 kW monthly determinant need not be wrong merely because it differs. Its tariff period and measurement basis may be different. These inputs are invented examples, not hotel records, tag calculations, or a cost forecast.

Now assume a transmission-related record is 270 kW under its own stated methodology. Its difference from 250 kW requires the appropriate method and period explanation, not an automatic correction to make every field equal.

Which dates should be preserved?

Record the meter service period, billed month, tag reference year, applicable capacity or transmission period, supplier effective date, and source retrieval date where relevant. A current invoice can use a determinant developed from an earlier reference period.

Do not compare an old utility tag with a refreshed supplier field without identifying the change. Ask which record supersedes which and when it applies. Preserve the provider’s response and actual accepted value.

A hotel operational change can occur after the reference period. It may affect future measurements or current utility demand differently. The existence of new equipment does not independently revise an already established tag or the supplier’s commercial treatment.

How is the supplier’s charge traced?

Identify whether the component is included, fixed, variable, or passed through under the actual agreement. Obtain the determinant, unit, price basis, period, and formula used in the invoice. Keep supply and delivery labels traceable.

A headline energy rate does not explain every capacity-related charge. Conversely, a separate worksheet tag does not mean every supplier product bills that value directly. The contract and statement need to establish the relationship.

Disclose broker compensation within the relevant comparison: payer, formula, unit basis, and embedded or separate presentation. Count it once. A modeled component should not combine unrelated determinants or hide payments in an unexplained average.

How are discrepancies investigated?

State the exact disagreement: different unit, period, reference method, accepted account value, or invoice formula. Provide the source records to the relevant utility or supplier contact. A complaint about unequal numbers alone may not identify an error.

Check customer identity, service points, additions, removals, and replacement-meter history where relevant. A mismatched account can produce a genuine reconciliation issue without proving that the market methodology is wrong.

If a correction is accepted, trace its effective period and later billing implementation. Keep a revised tag, promised invoice adjustment, and received credit as separate statuses. Do not report a financial outcome before the supporting records exist.

How should engineering use the comparison?

Give the engineering team the relevant measurement and reference conditions if a qualified operating analysis is proposed. The team should know whether it is examining ordinary monthly demand, a coincident system measure, or another specific objective.

Avoid promising that reducing a visible local peak will change every charge. A useful operating project can have different physical and commercial consequences. Compare actual evidence under the relevant method before attributing a tag change.

If the data cannot support a model, state the limitation and identify the required source. A precise-looking future expense number should not be fabricated from one graph point and an unrelated capacity value.

What makes the determinant file complete?

1. Identify monthly meter and billed-demand definitions.
2. Obtain actual PLC/NSPL-related source records.
3. Preserve methodology, reference dates and units.
4. Convert units without changing quantity definitions.
5. Trace the actual supplier component and formula.
6. Resolve account or period mismatches with responsible providers.
7. Keep proposed actions separate from accepted revisions and credits.

The completed ledger explains why different power values can coexist and which one governs each actual charge. It supports a specific billing decision without turning a hotel’s monthly demand register into a universal capacity tag or a prediction of next year’s expense.