Itron News
Managing Energy and Water Resources to Shape Cities of the Future
April 30, 2014
In a trend of ever-expanding urban centers, more than half of the world’s population now lives in towns and cities for the first time in history. As city populations grow, the demand for city services increases, putting a particular strain on energy and water. Energy and water resources are foundational to a city’s prosperity and sustainability. Managing their future will require more creative thinking and collaboration than ever. Technology and citizen engagement will play an important role in the responsible management of energy and water.
If you think about utilities and their role within a city, they power our businesses, homes and gadgets, as well as deliver fresh water so we can comfortably live our lives. However, most citizens do not think about their utility until they see their bill or they are out of power or water. At that point, they feel helpless to act. There is a growing desire to get more information so citizens have the facts in the palms of their hands. Citizens want the kind of service and real-time pricing information they get from other service providers. From the utility perspective, the entire industry has an opportunity to be more efficient for its customers. The utility industry is hungry for technology development and implementation to better manage energy and water. The question remains: how do we get there? Where are utilities investing?
In order to help understand how Itron can help utilities shape cities of the future, we commissioned a study of the global utility industry. The Itron Resourcefulness Index is a unique study that is one of the first to examine both executive and consumer attitudes within the utility industry, surveying more than 1,400 informed consumers and utility executives in 14 countries in every region of the world. It provides key insights about the utility industry, which is at a tipping point. Building smarter cities, engaging consumers in a meaningful way and resourcefully using our limited gas, water and electric resources requires innovative technology and a new way of thinking.
This month I shared findings from the Itron Resourcefulness Index, as well as what this means for cities, on the Meetings of the Minds Blog.
Click here to read my blog post highlighting our findings in the 2013 Itron Resourcefulness Index.
Itron is proud to support Meeting of the Minds 2014, taking place in Detroit September 30 - October 3. I encourage anyone interested in shaping our future cities to join Itron at this exciting event.
If you think about utilities and their role within a city, they power our businesses, homes and gadgets, as well as deliver fresh water so we can comfortably live our lives. However, most citizens do not think about their utility until they see their bill or they are out of power or water. At that point, they feel helpless to act. There is a growing desire to get more information so citizens have the facts in the palms of their hands. Citizens want the kind of service and real-time pricing information they get from other service providers. From the utility perspective, the entire industry has an opportunity to be more efficient for its customers. The utility industry is hungry for technology development and implementation to better manage energy and water. The question remains: how do we get there? Where are utilities investing?
In order to help understand how Itron can help utilities shape cities of the future, we commissioned a study of the global utility industry. The Itron Resourcefulness Index is a unique study that is one of the first to examine both executive and consumer attitudes within the utility industry, surveying more than 1,400 informed consumers and utility executives in 14 countries in every region of the world. It provides key insights about the utility industry, which is at a tipping point. Building smarter cities, engaging consumers in a meaningful way and resourcefully using our limited gas, water and electric resources requires innovative technology and a new way of thinking.
This month I shared findings from the Itron Resourcefulness Index, as well as what this means for cities, on the Meetings of the Minds Blog.
Click here to read my blog post highlighting our findings in the 2013 Itron Resourcefulness Index.
Itron is proud to support Meeting of the Minds 2014, taking place in Detroit September 30 - October 3. I encourage anyone interested in shaping our future cities to join Itron at this exciting event.
Wystąpił błąd podczas przetwarzania szablonu.
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>