Industry Insights
Distributed Energy Resources for a Better Today and Tomorrow
February 09, 2023
The growing importance and role of distributed energy resources (DERs) is top of mind for most utilities, and we continued the conversation at this year’s DISTRIBUTECH. As reported in a recent Utility Dive study, “a whopping 84% of utilities predict that DERs will also increase as part of their overall fuel mix.” Technology evolution and catalysts like environmental regulations and severe weather patterns are inevitably pushing the landscape of the electricity industry toward a more distributed future.
Although consumer-driven sustainability efforts like electric vehicles, solar electric, battery storage and more are encouraged and becoming increasingly necessary to navigate the evolving DER landscape, utilities need to actively prepare for their impact on the grid.
A great starting point for utilities is demand response (DR). Itron’s demand response management system, IntelliSOURCE, has redefined the industry’s expectations by providing extensive additional capabilities such as integrated modules to manage energy efficiency programs and distributed energy resources for over 20 years. DR programs are important in that they allow utilities to incentivize and empower their consumers to reduce energy consumption during times of peak stress on the grid. An easy entry point for DR programs has emerged as an increasing number of consumers install Wi-Fi thermostats in their homes and commercial buildings, enabling “bring your own device” programs. These consumers provide utilities with a very inexpensive resource for demand response, and, by providing these customers with value-added services, utilities can increase customer satisfaction. Our partners, GridPoint and Encycle, offer two real-time examples of DR programs in action. Using OpenADR technology, these partners are integrating their energy management systems with Itron’s Distributed Energy Management System (DERMS) to conserve HVAC energy consumption and provide load reduction during times of peak demand.
Although DR programs are highly encouraged, alone, they are no longer enough for utilities to effectively manage the grid.
The time for active grid management is now. Itron’s DERMS can help cities and utilities actively manage all of the new flexible loads that are entering the grid. To take grid management to the next level, utilities can leverage Itron’s DER Optimizer solution (DERO). This enables utilities to expand their legacy DR programs to include a wide range of DERs, including electric vehicles, smart inverters, battery storage systems and other flexible loads. DERO’s real-time analytics and optimization engine allow utilities to strategically grow their program portfolio to a wide range of DER-based grid services, and can improve grid stabilization and reliability, power quality, pipeline management and conservation efforts.
By integrating open standards into a platform that automates every phase of DER management and active load management programs, while also providing utilities a single operational view into all of their residential, small business and commercial and industrial energy management initiatives, Itron enables utilities to leverage more types of DERs and devices to assist with grid balancing, stabilization and reliability. With DERO, utilities can manage solar power, energy storage and electric vehicles in addition to other traditional grid-connected flexible loads such as water heaters, pool pumps, thermostats and HVAC systems – all via open standards. This reduces the risk of stranded assets for the utility while driving the adoption of grid-connected smart energy products and more cost-effective programs. Our DERO is also leveraging the existing metering infrastructure, enabling distributed intelligence and leaning on DER gateways to leverage the flexibility of customer energy resources in concert with the conditions of the grid.
Stay tuned for more highlights from our time at DISTRIBUTECH 2023!
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>
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>