Forecasting

Real-time AMI Data Helps Utilities Anticipate Power Needs

April 01, 2021

COVID-19 has changed the way people around the world live and work. As a result of shelter in place mandates, office buildings closed, and homes quickly became makeshift offices. This shift resulted in considerable changes to both commercial and residential power consumption. With Advanced Metering Infrastructure (AMI) data, utilities can monitor and measure how much and energy is used. Itron’s Forecasting team has been closely monitoring the load impacts of COVID-19 mitigation strategies and I recently contributed the following article to RTInsights.

COVID-19 stay-at-home mandates and the shift toward a remote-work lifestyle have led thousands of office and municipal buildings across the country to remain closed for the majority of 2020. While some businesses started to reopen late-summer 2020, spikes in cases in November and December once again prompted stricter community restrictions and business closures. Real-time data from Advanced Metering Infrastructure (AMI) can help.

The COVID-19 pandemic has led to significant fluctuations in commercial power consumption. Although the end is finally in sight, the impact of COVID-19 will affect the way we live and work moving forward. With more citizens staying at home, potentially long-term, it is more important than ever for utility providers to adjust operations to meet an offsetting increase in residential power demand.

How does the shift toward a remote workforce affect power consumption and demand?

During a typical workday before the COVID-19 pandemic, businesses and homes begin to turn the lights on and consume power around 5 a.m. With stay-in-place policies, more people started working from home, eliminating their daily commute, with some using that time to start their morning routines later. This causes the aggregate system load of utilities to begin ramping up later in the morning. Not only does this result in utility providers having to adjust power supply operations to meet a shift in demand, but it can also lead to a shift in consumers’ peak load hours.

Peak load hours are the points in the day at which a city and its residents are consuming the most electrical power. According to energy usage data prior to broad stay-at-home policies and COVID-19, peak load hours tended to be late afternoon when the combination of residential and non-residential air conditioning loads were running at maximum power to cool down homes and workplaces. As a result of the pandemic, commercial buildings that are largely unoccupied have lower air conditioning loads, leading to a shift in peak load hours to earlier in the day as residential homes cool throughout the day.

As utility providers produce more power during these peak load hours, there is typically a higher billing rate associated with power consumption during these peak hours. This could result in higher than expected end-of-month energy bills for consumers working from home.

Read the full article to learn how utility providers monitor power consumption and can leverage post-COVID-19 AMI data moving forward.

Si è verificato un errore nell'elaborarazione del modello.
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> 

Related Articles