Forecasting

2019 Benchmarking Survey

October 30, 2019

The end of October brings something for everyone. Fall foliage for adults, Halloween candy for children and Itron’s Annual Benchmarking Survey results for energy forecasters. While not as colorful as changing leaves or as sweet as candy corn, I believe that the survey is the best part of fall.

Since 2012, Itron has been surveying electric and gas utilities about system growth, forecast accuracy and forecasting characteristics. This year’s survey consists of 73 companies representing almost 2,067 billion kWh of annual electric sales and 1.8 BCF of annual natural gas sales across North America.

While many of this year’s findings continue patterns identified from prior years, three new findings stand out:

  • Residential Average Use. Since Itron’s first survey in 2012, residential average usage has been declining. The decline is supported by energy efficiency standards and continues to be forecasted by most utilities. This year, however, residential customer growth is 1.12% and sales growth is 1.19% resulting in an increase in average usage. While average use growth is close to zero, this first “increase” data point is either an outlier or the beginning of a new trend. Most importantly, this curious result is something to watch in the coming years.
  • Peak Growth. Unlike prior years, peak results are separated between summer peaking and winter peaking utilities. The separation shows that summer peaks are growing faster than winter peaks. Summer peak growth is 1.93% and winter peak growth is 1.12%. In one sense, the growth differential is not surprising since seasonal peaks occur at different times of the day and are driven by different end uses. However, the result underscores the need to capture differing growth rates in our peak models.
  • Prevalence of AMI Data. While forecasting is not the primary use case for installing and collecting AMI data, the data is useful for several forecasting applications. This year, 63% of companies reported access to AMI data with two-thirds of those companies using it for forecasting applications. Among the most significant AMI forecasting applications are sales calendarization, unbilled sales calculation and daily class energy and peak modelling. As more utilities gain access to AMI data, expect to see applications in the areas of daily variance tracking, improved weather response modelling and daily models for budgets.

The 2019 Benchmarking Survey full report was just distributed and is only available to Itron’s Energy Forecast Group members and survey participants. If you want to watch these developing trends and obtain the benchmarking results firsthand, be sure to participate in the survey next year.

The survey will open for responses in February 2020. Contact Paige Schaefer at paige.schaefer@itron.com if you would like to be added to the list to participate. Preliminary results will be presented at the Annual Energy Forecasting Meeting on April 22 – 24 in New Orleans.

Kesalahan terjadi ketika Memproses Template.
The following has evaluated to null or missing:
==> authorContent.contentFields  [in template "44616#44647#114455" at line 9, column 17]

----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----

----
FTL stack trace ("~" means nesting-related):
	- Failed at: contentFields = authorContent.content...  [in template "44616#44647#114455" at line 9, column 1]
----
1<#assign 
2	webContentData = jsonFactoryUtil.createJSONObject(author.getData()) 
3	classPK = webContentData.classPK 
4/> 
5 
6<#assign 
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs") 
8contentFields = authorContent.contentFields 
9categories=authorContent.taxonomyCategoryBriefs 
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent) 
11friendlyURL = authorContentData.friendlyUrlPath 
12authorCategoryId = "0" 
13/> 
14 
15<#list contentFields as contentField > 
16   <#assign  
17	 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)  
18	 name = contentField.name 
19	 /> 
20	 <#if name == 'authorImage'> 
21	    <#if (contentField.contentFieldValue.image)??> 
22	        <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />	 
23			</#if> 
24	 </#if> 
25	 <#if name == 'authorName'> 
26	    <#assign authorName = contentField.contentFieldValue.data /> 
27			<#list categories as category > 
28         <#if authorName == category.taxonomyCategoryName> 
29				     <#assign authorCategoryId = category.taxonomyCategoryId /> 
30				 </#if> 
31      </#list> 
32	 </#if> 
33	 <#if name == 'authorDescription'> 
34	    <#assign authorDescription = contentField.contentFieldValue.data /> 
35			 
36	 </#if> 
37	  
38	 <#if name == 'authorJobTitle'> 
39	    <#assign authorJobTitle = contentField.contentFieldValue.data /> 
40			 
41	 </#if> 
42 
43</#list> 
44 
45<div class="blog-author-info"> 
46	<#if authorImageURL??> 
47		<img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" /> 
48	</#if> 
49	<#if authorName??> 
50		<#if authorName != ""> 
51			<p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p> 
52			<hr /> 
53		</#if> 
54	</#if> 
55	<#if authorJobTitle??> 
56		<#if authorJobTitle != ""> 
57			<p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p> 
58			<hr /> 
59		</#if> 
60	</#if> 
61	<#if authorDescription??> 
62		<#if authorDescription != "" && authorDescription != "null" > 
63			<p class="blog-author-desc" id="author-job-desc">${authorDescription}</p> 
64			<hr /> 
65		</#if> 
66	</#if> 
67</div>