Understanding edge architecture through an IIoT lens
As automation and IT converge, industry-driving operations must meet the specific needs of real-time management, execution data requirements, and enterprise systems. Even a quick glance at a short list of things to consider in almost every industry can be daunting. The irresistible train that is technology has no plans to slow down, so it is important to strategize on how best to empower them for your company. Businesses changing many of their datacenter operations and IT support need to understand the relationship between applications, compute, and devices (edge architecture) in order to design, build, and maintain a better solution and provide easy-to-use performance and security.
In a typical three-tier IoT architecture, the lower layer,
or machine layer, accommodates both simple and complex sensors. These sensors
collected data and send it to the gateway system at the middle property level.
The data is then processed and sent to the upper layer of the cloud for storage
and analysis.
Here are some examples of some of the capabilities and
problems found in four common application architectures.
Edge Architecture
Edge Architecture Use Case 1: Oil and Gas
By car: This layer places sensors in a hostile environment.
Sensors such as valves and pumps can be remote or in the field where they must
be battery operated and have limited connectivity to the outside world.
Onsite: This level often contains many legacy systems
and equipment that will be or have been “in place” for extended periods of
time. As a result, meanwhile it is unlikely that such equipment will need to be
replaced, proper planning is important in determining how new IoT systems
should be adapted.
Cloud: At the top level, the focus is on efficiency
and security. It is vital to have an overview of the entire distribution system
in order to use it as efficiently as possible.
Edge architecture use case 2: life sciences
By car: This is a clean laboratory with a lot of energy
available to the sensors. Depending on the location of the room, a combination
of ready-to-use and custom-made sensors can be used. In addition, sensors are
less likely to be powered by a battery.
Property: On this layer, everything revolves around a
custom process control. It is very important that all items are stored at the
correct temperature, correct time, and accurate measurements.
Cloud: In the cloud, this is very similar to what
happens on the gateway. Regulatory requirements and traceability of all process
controls must be met. At this stage, you are less likely to face difficulties
in communication or energy level, for example, with the situation in the oil
and gas sector.
Edge Use Case 3: Utilities
By Machine: This harsh environment uses both old and new
technologies, from smart meters to fail-safe load (occupancy) sensors, designed
to measure usage and reduce waste.
Cloud: In a utility project, the emphasis on
improving efficiency to properly load balance, reduce environmental impact, and
validate network health remains at the cloud level.
Edge use case 4: transport
By car: Since transportation includes age-old technologies
used by cars, trains and air, sensors need to be developed to extract
information on a case-by-case basis. This exacerbates problems in this often
extremely large and hostile environment. These sensors can include cameras,
smart roads, GPS, LIDAR, and more. And, as with life science projects, there is
a lot of energy available for sensors in transportation environments.
On property: In this layer, you will find the vehicles
themselves, from cars and trucks to trains and planes. Unlike the first three
use cases, at this level the device (or vehicle) must remain fully operational
without being connected to the cloud.
Cloud: In transportation, the cloud provides asset
tracking, weather and traffic monitoring, vehicle health, and predictive
maintenance.
