Industry Insights
Smart Grid Technology Applied to Industrial IoT
July 10, 2014
Over the past few years there has been increased interest in using technologies currently deployed in smart grids for Internet of Things (IoT) infrastructure. The combination of the technology’s high performance, low cost and high level of security and the use of standards makes it an excellent option for expanding IoT infrastructure. There is a great opportunity here to draw on existing smart grid technologies, but it must be done correctly. In order to help business leaders understand how advanced metering infrastructure (AMI) technologies can be modified to support multiple IoT applications, I will be leading a session with the presentation of my paper, “Smart Grid Technology Applied to Industrial IoT,” at Internet of Things (IoT) West 2014.
My session at IoT West will explore my recent paper which describes how AMI technologies have been modified to support multiple IoT applications. The technologies are now non-application specific, open, available, and still meet the same stringent smart grid requirements, making these technologies an interesting option for business and civic leaders looking to increase IoT infrastructure.
AMI systems enable the measurement, configuration, and control of energy, gas and water consumption and distribution, through two-way scheduled and on-demand communication. AMI networks are composed of millions of nodes that are inter-connected in a multi-hop mesh network using some combination of wireless and power-line communications. These networks form the so-called Neighbor Area Network (NAN), along with a backhaul network providing connectivity to "command-and-control" management software applications at the utility company back office.
Each node is resource-constrained in terms of processing power, storage capabilities, and communication bandwidth, due to a combination of regulatory and engineering factors such as heat emissions, form factor and cost, but still has to be reachable through its IPv6 address. In addition, battery powered devices must be deployed in harsh environments for over 20 years without an opportunity to replace the batteries.
In a typical AMI deployment, groups of meters within physical proximity form routing domains, which can vary in size from 1,000 to 10,000 meters. Node density can vary significantly. For example, apartment buildings in urban centers may have hundreds of meters in close proximity, whereas rural areas may have sparse node distributions and include nodes that only have a small number of network neighbors.
All of these characteristics make AMI technologies very desirable for IoT infrastructure. The main challenge is how to apply these technologies to the broad Industrial IoT. My paper and presentation at IoT West will explore these challenges and opportunities in greater detail, drawing on examples of successful implementation around the world.
IoT West is a new event covering advanced connectivity and cloud-based control of devices, equipment, facilities and enterprise operations. The conference is taking place in Las Vegas, Nevada November 6 - 7, 2014, and will feature educational sessions showcasing solutions in mobile to mobile and machine intelligence, big data, facility and enterprise wide connectivity, wearables, IoT security, communications networks, cloud-based monitoring and control of equipment, assets, facilities & operations and smart service management.
I hope you will consider joining me at this exciting event!
Learn more by following @IoTShow on Twitter.
My session at IoT West will explore my recent paper which describes how AMI technologies have been modified to support multiple IoT applications. The technologies are now non-application specific, open, available, and still meet the same stringent smart grid requirements, making these technologies an interesting option for business and civic leaders looking to increase IoT infrastructure.
AMI systems enable the measurement, configuration, and control of energy, gas and water consumption and distribution, through two-way scheduled and on-demand communication. AMI networks are composed of millions of nodes that are inter-connected in a multi-hop mesh network using some combination of wireless and power-line communications. These networks form the so-called Neighbor Area Network (NAN), along with a backhaul network providing connectivity to "command-and-control" management software applications at the utility company back office.
Each node is resource-constrained in terms of processing power, storage capabilities, and communication bandwidth, due to a combination of regulatory and engineering factors such as heat emissions, form factor and cost, but still has to be reachable through its IPv6 address. In addition, battery powered devices must be deployed in harsh environments for over 20 years without an opportunity to replace the batteries.
In a typical AMI deployment, groups of meters within physical proximity form routing domains, which can vary in size from 1,000 to 10,000 meters. Node density can vary significantly. For example, apartment buildings in urban centers may have hundreds of meters in close proximity, whereas rural areas may have sparse node distributions and include nodes that only have a small number of network neighbors.
All of these characteristics make AMI technologies very desirable for IoT infrastructure. The main challenge is how to apply these technologies to the broad Industrial IoT. My paper and presentation at IoT West will explore these challenges and opportunities in greater detail, drawing on examples of successful implementation around the world.
IoT West is a new event covering advanced connectivity and cloud-based control of devices, equipment, facilities and enterprise operations. The conference is taking place in Las Vegas, Nevada November 6 - 7, 2014, and will feature educational sessions showcasing solutions in mobile to mobile and machine intelligence, big data, facility and enterprise wide connectivity, wearables, IoT security, communications networks, cloud-based monitoring and control of equipment, assets, facilities & operations and smart service management.
I hope you will consider joining me at this exciting event!
Learn more by following @IoTShow on Twitter.
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>