Use Intelligent Baselining
Use Intelligent Baselining to interpolate hourly usage, extrapolate annual usage, and improve estimates from limited bill data.
Use Intelligent Baselining to interpolate hourly usage, extrapolate annual usage, and improve estimates from limited bill data.
What is Intelligent Baselining?
Intelligent Baselining is a Switch product capability available in account calculators and usage profile APIs. It lets you fill in gaps in usage data and move usage data from one time period to another. In this context, “move” means aligning usage from the dates you have to the dates required by the calculation, such as using historical bills to represent usage during a future savings analysis period.
Use Intelligent Baselining to construct a full year of usage data from one or more bills for forecasts and what-if calculations. You can run savings calculations without obtaining hourly meter data or 12 months of bills from customers.
There are two main aspects to Intelligent Baselining:
- Interpolating hourly usage from larger readings, such as daily or monthly readings.
- Extrapolating an annual usage total from less than 12 full months of bills.
When to use Intelligent Baselining
Use Intelligent Baselining when:
- You have fewer than 12 months of bills.
- You have monthly or billing-period usage but need hourly usage.
- You need to move historical usage into a future savings analysis period.
- You want better estimates than flat hourly proration for a TOU tariff.
Avoid Intelligent Baselining when:
- You have a full year of high-quality hourly or 15-minute meter data.
- You need an exact reconstruction of historical meter behavior.
Minimum data requirements
- With
autoBaseline=trueanduseIntelligentBaselining=true, you can use as little as one monthly bill. - Accuracy improves as more known bill data is supplied.
- With
autoBaseline=trueanduseIntelligentBaselining=false, you must provide at least 12 full months (1 year) of data. - If you have a full year of interval data, use that data directly instead of using Intelligent Baselining. Real-world meter data is more accurate than modeled assumptions.
Interpolate time-of-use
With Intelligent Baselining off, the calculation assumes an even usage rate: a monthly bill reading is divided by the number of hours in the interval, and each hour is assumed to have the same number of kWh. While this works well for most residential tariffs, residential time-of-use tariffs are becoming more popular. Intelligent Baselining uses Typical Baselines data to interpolate hourly use more realistically.
Extrapolate from less than 12 months of bills
Without Intelligent Baselining, running a Savings Analysis requires a full year of usage coverage for the first year of the analysis. With Intelligent Baselining on, you can use as little as one monthly bill to estimate usage, and it can be for a time period outside of year one of your analysis. Using two or more months of billing data, if available, will increase accuracy. Intelligent Baselining uses Typical Baselines to fill in gaps and provide seasonality for that location. Typical Baselines vary by Utility Climate Zone.
Enable Intelligent Baselining
Use autoBaseline to enable or disable moving usage data from one period to another. When autoBaseline is true, use useIntelligentBaselining to control how the API interpolates and extrapolates usage, as described in the next section.
autoBaseline | useIntelligentBaselining | Behavior |
|---|---|---|
false | Any value | Does not move usage data between periods. |
true | true | Interpolates and extrapolates usage using Typical Baselines. Use this for fewer than 12 months of usage. |
true | false | Uses simple time-weighted proration. Does not extrapolate, so you need at least 12 months of usage. |
Use the autoBaseline property to enable or disable this feature. The table below shows how it defaults when not explicitly passed in:
useIntelligentBaselining only affects behavior when autoBaseline is true.
| API | Default Value | Notes |
|---|---|---|
| Savings Analysis | true | Savings Analysis usually uses this feature. Pass autoBaseline=false only when you explicitly want it off. |
| Account Cost Calculation | false | Account Cost Calculation defaults to off, so explicitly switch it on when you need Intelligent Baselining. |
| Usage Profile | false | Usage Profile requests can also use Intelligent Baselining when requesting usage data from a profile. |
Intelligent Baselining is not currently a feature of the On Demand Cost Calculation or On Demand Mass Calculation endpoints. Read Estimate Consumption from a Bill for suggestions on how to perform your own baselining when using these calculators.
Choose the Intelligent Baselining method
Use useIntelligentBaselining to select how the API divides usage into intervals and fills gaps when autoBaseline is true. Set useIntelligentBaselining to true to interpolate and extrapolate usage into hourly intervals using Typical Baselines. Use this setting when you have fewer than 12 months of usage data.
Set useIntelligentBaselining to false to interpolate larger usage intervals using simple time-weighted proration. This method does not extrapolate usage data, so provide at least 12 months of historical usage data to move it between periods.
To change the organization-level default for useIntelligentBaselining for a given appId, contact support. The configured default applies to future requests that omit useIntelligentBaselining. You can still disable baselining for an individual request by setting autoBaseline to false.
Maximize Intelligent Baselining accuracy
Follow these practices to get the best results from the data you have.
-
Enter the dates with as much precision as you can. If you have a "July bill", don't just enter "2015-07-01" and "2015-08-01" for the
fromDateTimeand thetoDateTime. Most likely, the actual billing period is not the exact month; it might start on June 26th or July 8th, for example. Enter the correct billing dates.Note that Arcadia always treats the
toDateTimevalue as exclusive. For example, a range from2015-07-01T00:00:00to2015-08-01T00:00:00includes usage starting at July 1 midnight and excludes usage at or after August 1 midnight, using the tariff time zone of the invoked MTID. -
Some utilities, such as PG&E, represent billing periods differently from Arcadia. Check the Billing Period Representation object, returned when you retrieve the LSE object with extended fields, and account for this difference when entering billing dates.
-
Omit months with unknown usage so Intelligent Baselining can extrapolate them. For instance, if you have one bill from July 15th through August 15th, enter only that bill. Do not enter bills for August 15th through September 15th, or other unknown periods, with a value of zero kWh.
-
Non-contiguous months work as long as you enter the dates correctly. If you have an April bill and a June bill, enter them both to increase the accuracy. As above, leave May out instead of entering it with a value of zero.
-
If your customer is on a Time-of-Use (TOU) tariff, enter the bill's usage breakdown for peak and off-peak periods, as shown in the TOU example. Similarly, if the bill splits usage into periods because a season or tariff version changed, enter those periods too. Intelligent Baselining accounts for these breakdowns.
Intelligent Baselining is primarily designed for the types of usage data you get from a bill or a web form. If you have hourly or 15-minute meter data, it will still work and can be useful for filling in blanks. However, if you can get meter data, try to get a year's worth and don't use Intelligent Baselining; a full year of meter data will be a better estimate.
Check whether Intelligent Baselining was used
Include "fields": "ext" in your Savings Analysis request, then inspect each scenario's assumptions field. The intelligentBaselining assumption is true when Intelligent Baselining was used and false when it was not. If the assumption is absent, Intelligent Baselining was not relevant, for example, because a full year of hourly data was available.
When Intelligent Baselining is used, the additional typicalBaseline assumption contains a UUID string identifying the baselineId of the Typical Baseline used with your data.
Next steps
Updated about 22 hours ago
