Industry Insights

IoT for Impact: How Smart Devices are Preparing Communities to Respond to Disasters and Save Lives

June 11, 2019

Smart metering networks can be leveraged to support a host of complimentary Industrial IoT applications to improve the performance, reliability and resilience of other critical infrastructure systems. On an average day, meters act as IoT sensors to provide utilities with high-resolution data from the edge of their network to precisely monitor energy usage, but when disaster strikes, they could truly save lives.

Increasingly, utilities are deploying multiple types of sensors on their networks such as methane detectors, pole tilt sensors, power line sensors and air quality devices. The data these sensors generate enables utilities to predict imminent danger, respond and recover quicker and more precisely, or, in some cases, even predict and prevent dangerous conditions all together. For example, by using methane detectors, utilities can sense the buildup of the dangerous gas at levels below the explosive limit, identify the location of potential risk of a gas explosion, turn off the gas and alert first responders to clear the area—all before an explosion occurs. When wildfires threaten regional air quality, utilities and communities can use distributed sensors to predict which areas will be most impacted and alert nearby populations.

What about less predictable disasters? Experts predict that a major earthquake is due to hit the state of California, but without knowledge of when or what its impact will be. IoT sensors such as pole tilt, electric distribution line, leak detection, air quality, and methane sensors among others enable a more resilient electric grid and can be leveraged to mitigate risk, minimize damage, and respond more effectively to save lives and speed recovery in the aftermath.

In a recent demonstration at IoT World created with our partner, RWI Synthetics, Itron showed the impact of an earthquake in Santa Clara, California. We were able to demonstrate how sensors working in tandem with predictive modeling were able to detect and impact outcomes during and after the quake, such as:

  • Detecting leaks and remotely shutting off gas and water lines;
  • Detecting if a pole is down to prevent safety risks and promote quicker recovery efforts;
  • Push out alerts to communicate quickly with citizens, providing the most up-to-date information to ensure their safety; and
  • Utilize intelligent evacuation planning to best direct traffic and get people out of harm’s way quickly.

Beyond how infrastructure might react, we were also able to demonstrate how people might react to disasters—and the still standing or crumbling infrastructure around them—through the creation of synthetic environments like those created by RWI Synthetics. RWI combines data analytics with extensive behavioral research to create details down to the stress levels and biometric responses of each synthetic individual.

By designing and trialing critical infrastructure systems, cities and utilities can use this information to help prepare for the unpredictable, improve system resilience and mitigate risk—while taking special consideration for citizen well-being. Doing so can effectively save countless lives and billions of dollars in avoided infrastructure repairs following a disaster.

Though these advances make a major impact on public safety, network resiliency and critical infrastructure for cities, big ideas and innovation are still needed to continue rapid improvement—and we at Itron are always looking to engage new great ideas and applications. To learn more, click here.

Learn more about our partner network here.

Se ha producido un error al procesar la plantilla.
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>