Unlocking Potential in Rural Areas

Industry Insights

Unlocking Potential in Rural Areas

March 5, 2024

I recently had a wonderful opportunity to get into the backcountry and saw a quieter side of life where people lead a seemingly laid-back, low-stress lifestyle but still were enjoying all the modern amenities, including the electricity grid. 

It struck me that in these rural environments, it would be really beneficial for the utility to have more information about the grid, how it is loaded, when it is down and if it is being used efficiently or abused. Distances between dwellings and communities are far, it takes time and costs a lot to carry out physical audits on a regular basis.  It would also be useful for the consumers to have more visibility about how much energy they are using and when they are using it. 

Everybody in the area uses prepay electricity, but it is the old one-way STS format where there is no feedback from the meter and the local utility is pretty much blind beyond the regional substation. 

With this older STS system, the consumer is better off than the utility because they can look at the meter display to see how much credit they still have available – but they must be at home to see what is going on because that is where the meter is. Some of the farmers and seasonal workers told me they often forget to look at the meter when they get back home and only remember to recharge the meter credit when they are disconnected. It’s irritating when it happens while watching sports or preparing dinner. They would love some kind of early warning. 

Statistics show that losses from 10% to 25% are not uncommon in the local distribution network, some of it is due to fraud. These losses can have a significant impact on the utility’s ability to properly service its customers. 

What to do? Dropping prepayment and deploying AMI is one option, but consumers are used to the flexibility prepayment offers. They pay when they have money available, as much as they want or can afford, and don’t have to try to save until the end of the month. 

The solution is to deploy AMI but keep prepayment as the billing option. There are 2 ways of doing this, both supported by Itron. The most flexible option is to deploy a thin prepayment where the prepayment functionality is orchestrated from the system. Another option is to use a hybrid method where the meter retains its prepayment capability and control but the credit tokens are delivered over the air via the AMI system. 

In either case, the payback for the utility is immediate. The utility gets real-time data about grid activities, enabling them to promptly identify issues and take whatever necessary corrective action is required to ensure optimal grid performance. Additionally, thin prepayment systems empower utilities to design intricate time-varying tariffs allowing them to better manage the varying demand patterns throughout the day, week, or even season and utilize the benefit of distributed generation often found in diverse energy landscapes like rural communities.  

For both the thin prepayment and hybrid prepayment, the consumer now has an app that can show them how they are using energy, warns them when they have limited credit left and they can recharge their prepay account directly from the app, eliminating the need to rush home to type in tokens. Management and control of their energy use becomes so much easier. 

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>