Back to Blog

Itron Inspire

Private LTE Today & Tomorrow The Right Technology at the Right Time

November 12, 2021

Guest blog contributed by Ryan Gerbrandt, Chief Operating Officer, Anterix

Creating a more resilient grid requires data driven intelligence in a more secure, accessible and interoperable landscape. This was a common theme throughout Itron Inspire, Itron’s customer focused event that we were proud to participate in as a gold sponsor. The underpinnings of this ever-expanding, ubiquitously connected ecosystem of devices, sensors and more is a solid communications network. This network will support diverse capabilities, from distributed intelligence to outcome-based solutions and analytics.

As a network operator, engineering technologist with a focus on utilities, I have had the opportunity to understand and embrace the critical importance of the emerging capabilities of connectivity, data and control, all of which are at the heart of grid modernization. Today, we operate at the intersection of the “mega sectors” of telecom and utilities, and this offers us the opportunity to unify the immense capabilities of both for the betterment of the grid.

The last time I saw this type of industry-wide opportunity was at a fast-growing Silicon Valley IIoT start-up, Trilliant Networks, where we were developing disruptive innovations and emerging communications technologies, and applying them to the modern energy challenges. That experience revolved around the adoption of smart meters which moved into the early stages of the smart grid. That technology, and the potential for connected devices and solutions, blossomed. As an extension of that work, today we know that every asset in the modern grid is inherently digitized. These sensors or control points are all assets that can be connected to share data. But all of this is only possible with a robust and secure broadband communications network.

Utilities understand this. They've been building and using private networks for a long time, so there's a history and a legacy that underpins the future path of private networks in general. What utilities get with a private LTE (PLTE) broadband network is greater performance AND greater control. Utilities depend on these networks, and they need to be reliable. They need visibility into what's happening in the transmission and distribution grid so they can better understand, manage and build upon the system's capabilities. They also need visibility so they can be proactive in preventing outages and responding quickly and precisely to dispatch crews to bring the system back online when they do happen.

With a PLTE broadband network, utilities also have full control over the design of their network and are able to architect not only the basic capabilities of coverage and Radio Frequency design, but also the resiliency, reliability and cyber security that are necessary as part of the electric grid. They can really adapt it to their design requirements that are quite specific and unique to supporting their services.

And, when you think of the grid five years from now, you must factor in the ability to support distributed renewables, microgrids and the electrification of transportation with EVs. That is a very different environment, so the private communications network of the future must be more interactive to support a multi-directional energy flow. The way to manage that future grid and all these distributed and connected devices is going to be rooted in data, visibility, real-time control and being able to monitor and understand what's going on. Those capabilities highlight the point of how critical security is in both the cyber and the physical realms. PLTE empowers utilities to build robust security models right within the technology stack itself.

We are at a point in time where the right technology is in front of us at exactly the right time. By leveraging foundational PLTE broadband networks, utilities can build the communications platform they need to improve visibility onto the grid, improve efficiencies, gain greater control, strengthen security and create a stronger brighter future.

If you missed Itron Inspire, you can still register to watch all sessions on-demand through Nov. 19, 2021, including my conversation with former Department of Energy CTO Peter Tseronis about the utility sector’s movement toward the adoption of private LTE.

Si è verificato un errore nell'elaborarazione del modello. 
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>