The hotel hosts a large meeting, and engineering’s interval chart shows a pronounced afternoon rise. The sales team asks what the event cost in electricity. Before attaching a dollar amount, the hotel must determine what was measured, which operation contributed, and which tariff components actually changed.
Use the bills hub to connect the graph with invoice evidence. This guide examines a particular event’s observed profile, rather than assuming every conference produces the same peak or cost effect.
Which event phases should be mapped?
Record setup, conditioning, kitchen preparation, attendee operation, teardown, cleaning, and any recovery sequence that applies. Obtain actual times where available and distinguish them from the planned schedule.
Identify rooms, banquet areas, equipment, and central systems involved. A ballroom schedule can omit preparation in the kitchen or later ventilation and plant operation. Keep the event’s physical scope separate from the hotel’s entire account.
Ask operations which records can support the timeline: banquet orders, kitchen schedules, space opening, or relevant control logs. A sales booking alone does not establish the equipment sequence or prove that every operating hour occurred as planned.
| Event phase | Operating evidence | Meter question |
|---|---|---|
| Setup and conditioning | Actual space and equipment schedule | Which early intervals changed? |
| Kitchen and banquet preparation | Service activity and relevant plant operation | Which shared loads overlap? |
| Attendee operation | Opened spaces and timing | What quantity was recorded? |
| Teardown and recovery | Cleaning and approved system sequence | Does the load continue after departure? |
| Whole-account peak | Other hotel activity and tariff | Did billed demand actually change? |
Are the intervals in energy or power units?
EIA’s electricity measurement explanation distinguishes power and energy. Confirm the export’s interval length, units, scaling, timestamp convention, and service-point coverage before interpreting the spike.
The interval-data guide supports missing-record and timing checks. A field called load can contain interval kWh rather than kW. Its plotted magnitude cannot be compared with billing demand until the quantity is understood.
Preserve the raw export and any transformed analysis. Identify daylight-saving or duplicated timestamp issues where relevant. A time shift can place the observed rise in the wrong event phase without any physical change at the hotel.
What does an assumed interval calculation show?
Assume a teaching example records 220 kWh over one quarter-hour and a comparison interval records 150 kWh over the same duration. Dividing by 0.25 hour gives assumed average powers of 880 kW and 600 kW respectively.
The difference is 70 kWh in energy or 280 kW in average interval power. These figures are invented demonstration inputs, not a hotel reading, engineering prediction, or event benchmark.
The calculation does not establish that the event caused the difference or that the difference became billable demand. It only demonstrates the unit conversion. The actual tariff, account peak history, and suitable operating comparison are still needed.
Which other loads coincided with the event?
Review guestroom occupancy, laundry, kitchen service unrelated to the event, pool or other amenities, charging, maintenance, and central plant where those loads exist. Record weather and operating changes relevant to the period.
DOE’s EMIS capabilities guidance describes interval analytics and operational investigation. Its methods help organize the evidence; an analytical platform does not assign causation merely because it overlays two timelines.
If there is a dedicated event-space submeter, identify its boundary. It may omit central cooling, heating, or kitchen preparation. A smaller measured subset can be useful without representing complete event energy.
Did the interval determine a billed demand charge?
Read the actual tariff class and relevant demand provisions. Determine the measurement interval, qualifying window, monthly maximum, ratchet, or other applicable determinant. Keep the recorded bill beside the graph.
DOE’s utility rate evaluation guidance explains why complete rate structure matters. It does not establish the hotel’s charge or a universal conference peak window.
The demand-charge guide develops the broader concepts. For this event, the specific question is whether the observed quantity affected the actual billed determinant. Another day’s higher demand or a tariff provision can change the answer.
What baseline could support attribution?
Identify what comparable operation would look like without the event. A suitable comparison may require weather, occupied rooms, equipment, hours, and other relevant activity. A random quiet day can differ in several ways besides the conference.
DOE’s M&V Guidelines version 5.0 provides a framework for boundaries, baselines, and operating changes. Use those principles with the actual hotel evidence rather than claiming the federal project guide supplies a specific event-cost formula.
State the method’s limitation when a counterfactual is weak or unavailable. The hotel can report observed event-period energy and the unresolved attribution question without inventing a precise incremental load.
How should incremental dollars be modeled?
Identify the commercial components the assumed incremental activity could affect. Separate energy, demand, fixed charges, and other actual terms. A whole-bill average can contain items that did not change because of the event.
Use the actual agreement and tariff in any modeled calculation, and preserve the assumptions. A reduction in one event-period energy segment does not automatically lower the monthly maximum or a future capacity allocation.
Where an energy price includes broker compensation, retain the payer, calculation, unit basis, and embedded or separate treatment in the relevant commercial record. Count it once. Do not add an embedded payment again when valuing event energy.
How can the investigation inform operations?
Share the specific findings with the responsible engineering and event teams. Identify which schedule, equipment boundary, or data issue deserves review. Procurement and finance should not prescribe technical shutdowns solely to flatten an interval chart.
If a qualified operating change is approved, compare actual subsequent operation using consistent evidence. Preserve guest-service, system, and event requirements. A proposed sequence remains an operating plan until relevant observed results support its effect.
The bill-increase guide helps connect a changed monthly bill with the event investigation. Keep the event’s contribution qualified instead of using it as a convenient explanation for every charge increase.
What if the event repeats next month?
Retain the original timeline, meter boundary, weather context, and unresolved issues. Ask whether the next event has the same spaces, food service, attendees, equipment, and schedule before treating the previous profile as representative.
A repeated booking can support a planned comparison if operating conditions are suitably documented. It does not establish an identical load curve. Give the forecast owner the evidence and uncertainty needed for the next budget or supplier request.
Check whether the recurring event changes the commercial forecast materially. Ask the provider about actual volume or shape provisions where relevant rather than assuming the account can absorb any event pattern without review.
What makes the event analysis complete?
- Map actual event phases and physical scope.
- Validate meter units, duration, timestamps and coverage.
- Identify concurrent hotel operations and weather.
- Check the actual billed demand determinant.
- Use a suitable baseline for any attribution.
- Label modeled cost and its excluded components.
- Assign qualified operational follow-up and future comparison.
The final report should state what the hotel measured, what the tariff charged, and what the analysis inferred. It can identify a useful operating question without turning a visually striking interval into a fabricated event expense or claimed project outcome.
Retain the event analysis with its supporting dates so later staff can distinguish a one-off operating condition from a representative recurring load. That distinction matters when the next forecast uses the previous month’s history.