Industry Insights
Harnessing the Power of Distributed Intelligence
As utilities and cities continue to face challenges related to cybersecurity, outdated infrastructure, severe weather patterns and more, it is critical to proactively address and adapt to the increasing demand on the electric grid. Itron’s distributed intelligence (DI) platform is helping utilities do just that. At DISTRIBUTECH 2023, we look forward to pushing the boundaries with DI and showcasing how we are enabling utilities and cities to achieve levels of distribution system visibility unlike ever before.
Simply put: DI is an investment worth making and will continue to grow in value over time. Real-time data and visibility at the edge are critical as the grid becomes inundated with electric vehicles (EVs), solar, wind and new types of energy-efficient devices. Itron’s DI solutions address this by combining granular, real-time data from the grid’s edge with a secure, open-enterprise application platform. With edge computing capability, DI makes distribution-level decisions real time, efficiently and effectively, where those decisions – and actions – need to take place.
Itron’s DI platform focuses on utility customers and management of the electric grid, with applications for grid optimization, asset management, distributed energy resource (DER) integration and consumer engagement. Additionally, DI leverages an open platform that supports third-party innovation with an API development kit, enabling an ever-increasing ecosystem of partners to create their own value-driven, custom applications. DI effectively moves grid analysis, decision-making and control to the grid’s edge, resulting in a significant reduction in latency of action, greatly improved situational awareness, more accurate analysis and advanced event detection.
Our DI platform also leverages applications to address common utility challenges and use cases. Each app has its own value proposition and is purpose-built to solve a specific problem—such as improving customer safety, reducing operating expenses, increasing capital asset lifespan and enhancing operational efficiency. At DISTRIBUTECH, attendees are invited to Itron booth 2514 to see interactive demonstrations that will dive into each of these key components of Itron’s DI platform and how they bring visibility to the distribution system from day one.
Here are a few of the DI applications we’ll be showcasing:
Location Awareness
Function: provides the electrical location of every meter on the distribution grid, including transformer, phase and feeder and can group meters by phase and feeder for reports.
Benefits: maintains up-to-date grid topology awareness for DI and back-office utility systems, including active transformer management, storm simulation and outage detection and response, DER analytics and management and accurate asset loading and planning, including phase balancing and load studies with a 99.2% accuracy rate
Meter Bypass Detection
Function: provides detection of bypass tampering at the electricity revenue meter where jumpers are placed around the meter to bypass collection of some consumption so that the consumer’s bill is reduced.
Benefits: revenue assurance and addresses potential safety concerns
Active Temperature Monitoring
Function: uses high-resolution temperature readings to detect meter socket problems before they create a safety hazard or interrupt service and provides historical trends
Benefits: fewer customer interruptions, lower O&M costs with proactive maintenance and increased safety for customers and utility personnel
High Impedance Detection
Function: detects and locates poor electrical (high impedance) connections in low-voltage secondaries and shows historical impedance for a meter
Benefits: operational benefits in decreasing customer outages and complaints through proactive resolution, also limiting safety concerns; planning benefits through identifying patterns for capital project justification
EV Awareness
Function: provides detection of electric vehicle charging at a premise and calculation of time-series usage profiles using real-time data
Benefits: EV models for ‘offline’ applications such as utility planning and EV program customer engagements and inputs for real-time controls (e.g., DERMS, ADMS) for applications such as distribution transformer protection and Volt/VAR Optimization
The future of our modern grid is dependent on leveraging more DI at the grid edge to help manage growth, stability and safety. Connect with us in booth 2514 at DISTRIBUTECH to learn more about the breadth of capabilities our DI platform has to offer.
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>
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>