Topics In Demand
Notification
New

No notification found.

Blog
Edge Control and Edge Virtualization: When?

October 22, 2019

458

0


Listen to this article



My day began by meeting with a couple of European ARC colleagues to discuss the emergence of “edge control” and ended with me seeing this article on sdxcentral about edge virtualization.  Whether your work is Edge virtualizationin telecommunications, automotive, IoT, medical technology, or industrial automation, today you’re hearing about The Edge.  All these fields have (for decades) deployed intelligent systems in their operations. But it seems clear to many folks in these businesses are poised for a major change in systems, the likes of which we haven’t seen (in industrial automation) since the 1970’s exploitation of microprocessors to create the PLC and the DCS.

What’s going to make these systems revolutionary is that they will combine the real-time functions of today’s industrial embedded systems (such as a PLC) with the software tech of cloud computing.  This sounds impossible and improbable.  It’s not.  There are several new industrial products on the market that do just this in some way.  The question  is can it be done in hardware that is both industrial grade and truly commoditized?  Product suppliers hate commoditization, but end users love it, because it simplifies substitution and reduces cost.  Industrial PCs are probably the best example in today’s market of the value commoditization brings.  ARC will be doing more research in this area.

Edge Virtualization

The article in sdxcentral was an interview with Said Ouissal, who is a Founder and CEO of Zededa, a venture stage firm developing virtualization solutions for edge systems, and the original developer of “Project EVE”, an open source edge virtualization project of the Linux Foundation.  Ouissal noted 5 areas where edge virtualization differs from that of the data center.  These are:

  1. Zero touch – You can’t reach or even log on to many edge systems
  2. Heterogeneous – Widely varying types of equipment, software, requirements, etc.
  3. Cloud native – You can’t economically support a distributed app across dozens or hundreds of remote devices unless it is cloud native – unless the app can be maintained centrally and delivered automatically.
  4. Security – In a data center there is at least physical security.  At the edge there’s often not even that.  It’s a zero-trust zone.
  5. Scale – The edge will feature large numbers of nodes, each running very few apps (perhaps only one).  Incremental costs must be very low or growth will be impossible to fund.

IMHO these 5 points are spot on.  I would add a double dose of heterogeneity, because of the real-time and reliability requirements of many industrial automation and OT systems.  But I’m convinced that the way forward involves virtualizing and containerizing many applications that today run as embedded systems.  I don’t see another way to achieve these goals.  Do you?  Please let me know what you think.

“Reprinted with permission, original blog was posted here”. You may also visit here for more such insights on the digital transformation of industry.

About ARC Advisory Group (www.arcweb.com): Founded in 1986, ARC Advisory Group is a Boston based leading technology research and advisory firm for industry and infrastructure.

For further information or to provide feedback on this article, please contact RPaira@arcweb.com

About the Author:

Harry Forbes

Harry is ARC’s lead analyst for the Distributed Control System (DCS) market. In addition, ARC leverages Harry’s utility expertise in its coverage of Smart Grid, industrial networking, networking and communication standards, and the electric power vertical industry. His research topics include the DCS integration and architecture, Smart Grid, Smart Metering, energy storage, industrial wireless, industrial Ethernet and emerging network technologies.


That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.


© Copyright nasscom. All Rights Reserved.