Documentation for All Versions

Download a PDF Version

Current Documentation for EnergyCAP Online

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Overlapping bills and multi-account meters will NOT inflate the number of days since we you are always dealing with only ONE bill

...

Front-end - displays what is given to it; we get the per-day benchmark value direct is obtained directly from the API

Back-end - Place group digest relies on data contained in BAM, with day values. Unlike the meter digest, this appears to use a simple SUM(days) to get the number of days in a period. The "n/day" values are then calculated by calculating value/days (e.g. totalCost / daySum). The max of the day counts is returned in the data transfer object (DTO); should be 365, but may hide meters which have less than 365 days, making it hard to reconcile by hand using just the data in the DTO.

...

Front-end - displays what is given to it; we get the  the per-day benchmark value direct is obtained directly from the API

Back-end - Meter group digest relies on data contained in BAM, with day values. The "days" calculation is MAX(endDate) - MIN(beginDate). The "n/day" values are then calculated by calculating value/days (e.g. totalCost / daySum).

...

Back-end - Place digest relies on data contained in staging tables (e.g. BillSummaryPlaceCommodityRollupCP) which DO NOT contain "per day" values... as such, I conclude that all the staging table views calculate "simple" per day values on the front-end.

...