Industry Insights

Not only Smart but Active – Distributed Intelligence for IoT

November 12, 2015

In the developing age of the Internet of Things (IoT), we must stay attune to emerging technologies and industry transformations. What if real IoT value comes not from the ability to connect devices, but from taking action with little human intervention? How will we harness IoT technology to better overcome the challenges of tomorrow? The possibilities surrounding the future of connected communities may very well require reworking, rethinking and re-imaging technology. By enabling devices to take action in the field in real time, IoT transforms smart grid and smart distribution systems into an active system for energy, water and beyond.



The utility sector is no stranger to IoT technologies and architecture. Already connecting millions of smart devices, energy and water utilities are poised to make the IoT a reality with distributed intelligence. Distributing intelligence across utility systems allows utilities to capitalize on connected devices, leveraging computing power to not only communicate and measure, but to act and solve problems in real-time. Instead of collecting quantitative data for the utility back office to decipher, active grids and systems make decisions in real time and utilize data to create value independently and make changes intelligently.

This evolution in intelligence can be attributed to specific technological characteristics, all of which work to maximize the value potential in meters, grid sensors and other types of connected devices. These characteristics include in-field processing power with the computing equivalent of a smart phone, locational awareness in relation to other devices, and multilingual devices that simultaneously speak the language. When many types of sensors, including electricity, gas or water meters; pressure, temperature or leak sensors; streetlights or solar panels are interconnected that is where the promise of IoT can be delivered. Bringing together datasets from the different sensors in a central area will enable correlations that were not previously possible because of the siloed data approach. This is being done in the utility industry today.

In the age of IoT, it’s time to rethink the possibilities of connection and enable optimal intelligence. Learning from an existing, successful IoT vertical like smart energy and water can help speed up the reality of IoT for everyone.

By Roberto Aiello, New Business Innovation, New Models, Itron CTO Office

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>